Standalone SHORELine motion correction

Hi @mattcieslak,
I'm working on a mouse brain dataset that has some substantial motion issues related to scanner bed vibration. So far eddy works on the data but doesn't mitigate all of the motion corruption. I'm curious if SHORELine based motion correction would improve outcomes above and beyond what I've been able to accomplish so far.
I've tried running QSIPrep using the --dwi-only flag for these mouse brains but, unsurprisingly, the data do not produce outputs. I'm curious if the SHORELine HMC workflow would somehow be accessible as a stand-alone call.
Just musing and brainstorming what to do with these data while we try to address the motion at the scanner.
Thanks

We don't have a standalone cli tool for shoreline, but if you've worked with nipype before you should be able to get shoreline run on your mouse data. Let me know if you're up for trying this out and I can point you to the relevant functions


Is there an IN operation like SQL does?

This'll make a lot of query much simpler.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0b938908-1b0f-63e4-6e17-bccd57f8d3e8
Version Independent ID: 7edcd9e5-13ba-f7e4-f7cd-92412a28001f
Content: SQL to Azure Log Analytics query language cheat sheet
Content Source: articles/log-analytics/query-language/sql-cheatsheet.md
Service: log-analytics
GitHub Login: @bwren
Microsoft Alias: bwren

@ronaldvanrij
Thanks for your feedback! We will investigate and update as appropriate.

Thanks for the feedback! Can you post this as a feedback @Log Analytics User Voice.This will allow the community to upvote and for the product team to include into their plans.
We also have the "Give Product Feedback" button in our documents now to take you directly to the appropriate feedback page.
We will now proceed to close this thread. If there are any questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Module 'ngMockE2E' is not available!

I am new to angular, and I am following this tutorial.
Here is my login.test.js
describe ('Clicking on the login button', function()
{
var mockModule;

	beforeEach(function(){
		browser.get('#/loginPage');
		mockModule = require('./mock');
	});

	//check if the api is working and returns the correct value
	it('should check if the api is working and returns correct credentials',function()
	{
		browser.addMockModule('httpBackendMock', mockModule.signin_request);
		expect<EMAIL_ADDRESS>
	})

	it('another it', function()
	{

	})
})

and here is my mock.js file
exports.signin_request = function(){
    var expected_response = ('1 -<EMAIL_ADDRESS>	angular.module('httpBackendMock', ['app', 'ngMockE2E'])
        .run(function ($httpBackend) {
            $httpBackend.whenGET('http://website.com/api/login?email=user@gmail.com&password=123456').respond(function(){
                return [200, expected_response];
            });
            // $httpBackend.whenPost(/.*/).passThrough();
    });
}

I don't understand why I get this error

Error: [$injector:modulerr] Failed to instantiate module ngMockE2E due to:
Error: [$injector:nomod] Module 'ngMockE2E' is not available!

Hi there!
Your question is better suited for StackOverflow or Gitter. Please ask a question there with the 'protractor' tag or post in the Gitter Channel to get help.
From the the getting help section of the README:

Please ask usage and debugging questions on StackOverflow (use the "protractor" tag) or in the Angular discussion group. (Please do not ask support questions here on Github.)

That said, maybe there's a problem with the tutorial? You're getting that error because, at least in the code you posted, you never defined an ngMockE2E module. I tried looking into the tutorial, but the link you posted appears to be a site selling bowls for toddlers.
Thanks!

thank you for letting me know. I posted it on SO but it got no answer so i thought I'd ask on here, but i'll try Gitter. Sorry for that, this is the correct link http://prashantsahni.in/blog/2014/09/28/mocking-apis-integration-testing-with-protractor.html


🚀 - Add support for multiple tabs

Which @codeimage/* package(s) are relevant/releated to the feature request?
codeimage
Description
As the title says, it would be nice to have multiple tabs, be able to switch between them and maybe be able to generate multiple images.

Hi @micnic, thanks for your proposal!
Just to let me understand correctly, your idea is to handle multiple workspaces with his own configuration? I've made a quick mockup as example

Here is a representation of what I have in mind:

In this way it's possible to display a little project and have a context of what files are available and what is the link between them. Tabs would be clickable and have their own code content.
Generating multiple images would be an optional feature, maybe to export them as an .zip archive, but generating for the current active tab is totally fine in my humble opinion.

Ok 👍
This could be the style when the "tab accent" is disabled, what do you think?

A possible issue could be handle the style when there is no much space left

I like this design for disabled "tab accent", would just remove the background of the + (new tab) button

One of the possible issue with this could be handling the style when there is no much space left. Do you think it is better to manage it with overflow-scroll or with an "Other" tab (maybe with the ellipsis-h icon) which show dinamically?

I am a fan of firefox's solution with tabs that do not fit in the width, but it would be a bit more work to implement and might be not that adequate for the minimalistic design of codeimage.

Hi @micnic, I just wanted to inform you that your issue is currently in progress.
There are several things to fix, like some missing data synchronization reloading the page,  themissing theme switcher header and the style of tab accent which is currently in progress
https://codeimage-dhywm38yd-riccardoperra.vercel.app/

In my opinion theming or other visual customization should not be set for each tab independently. What I was expected is that only the content of the tab changes when I switch to another tab, visuals should remain the same.
The solution that you implemented for overflowing tabs seems pretty good (similar to chrome behavior), nice job.
While testing the current version another feature idea came into my mind: to implement the possibility to move the tabs by dragging them around.
Either way I like the current progress on this feature. Will follow the changes you are doing in the feature branch, I'm a react dev, just recently discovered solid and I really like it, will check and see if I can give any advice about implementation details.

In my opinion theming or other visual customization should not be set for each tab independently. What I was expected is that only the content of the tab changes when I switch to another tab, visuals should remain the same.

You’re right, this doesn’t make so much sense right now. I handled them separately in the case I need it for future integrations, but handling a global shared state instead of forwarding all theme options changes through all tabs is much easier to maintain. I’ll refactor the state later 😄

While testing the current version another feature idea came into my mind: to implement the possibility to move the tabs by dragging them around.

I thought the same thing. Hoping that I don’t have to refactor again the tabs styles, I’ll try solid-dnd which could fit in this case
Thanks for your feedback and your time!

Hi @micnic, the https://github.com/riccardoperra/codeimage/pull/265 is almost done.
I'm planning to clean-up the code and release it in a few days. Any feedback is welcome 😄
Demo (you probably need to Ctrl+Shift+R to get the latest version)
https://codeimage-git-257-add-support-for-multiple-tabs-riccardoperra.vercel.app/
Here's a small changelog compared to a few days ago:

Styling options are now shared. Only the language will be custom for each tab and automatically change also in base of the extension used on the tab name
Add drag and drop. The y-axis is locked and it has boundary parent (you can only move it inside the container wrapper)
Tabs are limited to a max of 6
Close icon will not show up if there is not enough space
Multi-tabs is available for windows terminal theme
Theme switcher will now show an example code with highlighing

Looks great! The functionality and UI are really good.
Just observed the "New Tab" button icon is not centered, would be nice to have it in the middle of the button:

Also some dark themes (including the one in the upper screenshot) have low contrast between active and inactive tabs which makes a little difficult to understand what tab is being edited. Is it possible to improve tab colors?

Also some dark themes (including the one in the upper screenshot) have low contrast between active and inactive tabs which makes a little difficult to understand what tab is being edited. Is it possible to improve tab colors?

Thank you for this feedback! Anyway, I probably will have to recalibrate my monitor 😄
I've opened this #271 with a preview https://codeimage-git-fixeditortabcolors-riccardoperra.vercel.app/
Here's the theme that I've fixed:

NightOwl
Material Ocean
Synthwave'84
Material Volcano
One Light
Coldark Cold
MaterialLight

I think I found a small bug, steps to reproduce:

Open a new "Untitled" tab
Close the old tab

Observed:
The editor window shrinks and only if you try to edit the tab name the content of the tab appears back.

Oh yes, I was trying to fix a render issue while removing the current active tab and I had forgotten to set there the right fallback 😄 https://github.com/riccardoperra/codeimage/pull/271/commits/7d118e0f719072f36d35866a5006da6096206fbc#diff-8eb4581d578ae507dae5bd6e6e9edaa5421632b1fe29929207d6a7a23a0fc839R104-R108
Thanks again

From my side it's ready to be merged, LGTM!

Released 😄


Implement advice for no implicit typeclass found requested in issue #27

Resolves https://github.com/softwaremill/scala-clippy/issues/27

Released in 0.3.3.


Split registry build tools into two scripts

Splits the registry build tools into two scripts, build.sh and build_image.sh

build.sh runs the index generator and creates an archive.tar for each stack (if needed), and outputs to a given output directory
build_image.sh calls build.sh, then builds the stack artifacts into the devfile index image

@johnmcollier The PR looks good to me, I just left one nit comment.

@GeekArthur Thanks, updated.


RISC-V Build Requires libstdc++/libsupc++

Trying to build for RISC-V but I keep getting this error at link time:
/usr/lib/riscv64-unknown-elf/bin/ld: cannot find -lstdc++
/usr/lib/riscv64-unknown-elf/bin/ld: cannot find -lsupc++

In other words, my build environment does not contain copies of libstdc++ or libsupc++ for RISC-V.
I followed the instructions to install newlib using the prebuilt .deb package. Is there perhaps another similar step I can follow to get a copy of these C++ libs?
Also interesting: I removed the flags from this line in Configuration.mk and my build was successful. Perhaps these libs aren't needed for a simple C application?
@bradjc it looks like you're heavily involved with RISC-V support. Is this perhaps something you have context on?

You're right that libstdc++ and libsupc++ are not needed to compile c apps.
What I don't know is why even though those libraries have been included in the compilation for years now you don't have them. Getting a riscv toolchain is a mess.
You have done the easiest fix. Maybe we should have some way to only include them for c++ app builds.

Out of curiosity, why do these libs need to be explicitly listed for riscv but not for other platforms?
Happy to submit a patch. What do you think about gating them behind RISCV_CPP=1?

Hey, so this is a little more complicated
Your build probably doesn't need those libs. But the ble_passive_scanning example needs -lstdc++ for example. It's also entirely possible that someone's out of tree app needs those libs. By including them in the default Makefile we can allow a greater range of compatibility.
As for installing a libc. It's best to try and get one from your distro. Distros have slowly been improving their embedded libc support for RISC-V. An Arch distro is your best bet for that type of thing.
It sounds like you are using a Debian based distro though. Debian stable has support for picolibc which you should be able to use instead of newlib. It's well maintained and will contain bug and security fixes not found in older newlib packages.
picolibc seems to have made it to Ubuntu as well. So hopefully someone with a Debian machine can test with it and update the README as required

I'm not having any trouble with my libc installation. I am able to compile C apps just fine using the prebuilt .deb described in the README.
The core issue is that "C++ on RISC-V" seems to be broken for a number of reasons. In fact, if I try to compile ble_passive_scanning for RISC-V according to the README, I don't even make it to the linker step; compilation fails on #include <cstring>.
Lack of decent C++ support is definitely an ecosystem issue, not a Tock-specific problem. However, the presence of these C++ flags (-lstdc++ -lsupc++) in the Tock makefiles is preventing me from compiling plain C apps for RISC-V. This is why I suggested making "C++ on RISC-V" an opt-in feature via RISCV_CPP=1.
Alternatively, do you have any suggestions on where I can get a hold of C++ libraries for RISC-V?
(Aside - I love the idea of using picolibc from my distro instead of using Tock's vendored libc. But seem to be lots of hardcoded paths in Configuration.mk that would need to be reconciled.)

Yeah, so it seems like you are having libc issues, specifically with the C++ libraries. You would expect to get that from newlib or picolib in this case. You might need some different arguments when you build newlib

Alternatively, do you have any suggestions on where I can get a hold of C++ libraries for RISC-V?

I gave some suggestions in my previous comment.

(Aside - I love the idea of using picolibc from my distro instead of using Tock's vendored libc. But seem to be lots of hardcoded paths in Configuration.mk that would need to be reconciled.)

Ah, those hardcoded paths are a pain. A simple revert of 00037a844c64ee2b0c4f664aff704a0a4cc4cb30 should be what you want though

You would expect to get that from newlib or picolib...

Been digging a little more. libstdc++ is a component of GCC itself, not newlib/picolib. It is GNU's implementation of the C++ standard library.
https://gcc.gnu.org/onlinedocs/libstdc++/faq.html
My distro (Debian Bullseye) delivers libstdc++ as a separate package from the core GCC toolchain. But as far as I can tell, a packaged version is not available for riscv64-unknown-elf.
I can try building my own version locally. If that works, maybe it should be added to the README as a requirement for RISC-V?

Good catch! I didn't bother to check if the library was actually in picolib/newlib!
If you build it locally and get it to work a README update would be great

I am having the same issue when building on the mac (M1). Interestingly the error is only popping up when building for the rv32i platform. Commenting out https://github.com/tock/libtock-c/blob/14b0118654ddc09d55b704c825c5d685261b38b1/Configuration.mk#L80 solves the problem.

Interestingly the error is only popping up when building for the rv32i platform.

This is an interesting obversation, given that rv32i really should not be of any influence w.r.t. the C and C++ libraries used. One key difference with rv32i is that it does not have multiplication support, which might potentially result in linker errors complaining about linking to muldiv.o from libgcc, but nothing else (see NixOS/nixpkgs#178140). I don't have an M1 Mac but would like to see rv32i working (it's a popular target for smaller FPGAs). Perhaps we can debug this over a call @alexandruradovici?

Interestingly the error is only popping up when building for the rv32i platform.

This is an interesting obversation, given that rv32i really should not be of any influence w.r.t. the C and C++ libraries used. One key difference with rv32i is that it does not have multiplication support, which might potentially result in linker errors complaining about linking to muldiv.o from libgcc, but nothing else (see NixOS/nixpkgs#178140). I don't have an M1 Mac but would like to see rv32i working (it's a popular target for smaller FPGAs). Perhaps we can debug this over a call @alexandruradovici?

Yes, sure. When are you available?

Okay, @alexandruradovici and I debugged this today and it appears that the prebuilt RISC-V toolchain Alex and possibly others are using (if I recall correctly, this was provided by SiFive?) does not support the rv32imc target. This is unfortunate, as rv32i, being a minimal target, is somewhat popular amongst smaller FPGA designs (think FOMU), as well as an interesting target when experimenting with softcores or even writing your own. However, supporting such a target by default makes the libtock-c build experience miserable, given the prevalence of toolchains which do not have prebuilt support for it.
Fortunately, tock/tock#2860 actually changed the LiteX simulation target to use a rv32imc-enabled VexRiscv softcore CPU. Hence, we can "fix" this issue for now by changing this particular target to use rv32imc instead, and everything will work just fine. That said, this "fix" does feel more like a workaround and (again) exposes some major usability issues in the RISC-V toolchain ecosystem (for now). It means that people wanting to build for rv32i, for some exotic hardware, small softcore, or to experimen/debug will be on their own for now, given we'd be explicitly dropping upstream support for such a CPU.


Update CHANGES.rst for release 1.4.0

Figure it's time to prepare a release, and so updating the changelog.  I think this covers all the things that have changed since 1.3.3.
Normally I'd think this should be a breaking 2.0 change since we're dropping support for a few Django versions but it appears that hasn't been the pattern in this project so just going with 1.4.0.

@hramezani Did I miss anything in the changelog?  You good with doing a release now?  Have you done one, or does @aleksihakli need to do it?

Hey @mgrdcm! You can see the people who can do the releases at the project Jazzband page:
https://jazzband.co/projects/django-embed-video
You @mgrdcm and me @aleksihakli can push the releases from the Jazzband page to PyPI at the current moment.

I reviewed and upstreamed the changes, but the rST file had a formatting error it needs fixed for upstreaming. I opened a PR for those, as soon as we get that merged we can bake the 1.4.0 release :)

I reviewed and upstreamed the changes, but the rST file had a formatting error it needs fixed for upstreaming. I opened a PR for those, as soon as we get that merged we can bake the 1.4.0 release :)

Ahh yes, sorry I didn't mean for that PR to get merged yet was just trying to see if we had everything in there before finalizing the date and whatnot.  I had it as a Draft but apparently that can be overridden!  :)

Hey @mgrdcm! You can see the people who can do the releases at the project Jazzband page:
https://jazzband.co/projects/django-embed-video
You @mgrdcm and me @aleksihakli can push the releases from the Jazzband page to PyPI at the current moment.

Great, thanks!  Sorry I haven't actually handled a release yet since being designated a lead.


Documentation is down

Your documentation site is down... and it makes me a sad panda.

@ScottDLance Looks like the service is back online http://www.newtonsoft.com/json/help/html/Introduction.htm
This issue can now be safely closed.


Clarify Docs for building, to indicate location of pkg script

https://traffic-control-cdn.readthedocs.io/en/latest/development/building.html says to use the "pkg script", but it doesn't say where it is. The docs should note it's in the root of the repo, and possibly include a link to Github or instructions to checkout and run it.
I know that might seem obvious, but I'm making this case because we actually had someone asking where to find it.
Relatedly, the docker-compose instructions on the same page have the same problem. Might be worth adding to the instructions, a section on how go get the code and navigate to it, i.e.
mkdir -p $GOPATH/src/github.com/apache/
cd $GOPATH/src/github.com/apache/
git clone https://github.com/apache/incubator-trafficcontrol
cd incubator-trafficcontrol

Looks like the docker compose instructions have been updated.  I will submit a PR to add the pkg location.


Setup Production And Staging Apps for GitHub and Slack

GitHub

Production: https://github.com/apps/hello-slack/
Staging: https://github.com/apps/hello-slack-staging/

Slack

Production: https://api.slack.com/apps/A07D8UUML2H (private)
Staging: https://api.slack.com/apps/A07D8UQ4TK7 (private)

I configured the respective credentials in Netlify. I disabled pull request previews. Instead, I enabled branch deployments for the staging branch.

I also set AWS_LAMBDA_JS_RUNTIME to nodejs20.x as it defaults to Node 18


chore(package): restore babel option modules: false for ESM builds

Fixes #2661.

Thanks :+1:

Released in<EMAIL_ADDRESS>


15 Test accounts for testing CRA list Upload [jp-bugfix-0009]

Per FMO request, additional 15 test user accounts added into the existing seeder file, and migrate to region.
Deployment instruction
php artisan db:seed --class=UserTableSeeder

Per FMO request, additional 15 test user accounts added into the existing seeder file, and migrate to region.
Deployment instruction php artisan db:seed --class=UserTableSeeder

Are the id's not auto incremented? Will you have conflicts in different environments if the ID is already in use?

Per FMO request, additional 15 test user accounts added into the existing seeder file, and migrate to region.
Deployment instruction php artisan db:seed --class=UserTableSeeder

Are the id's not auto incremented? Will you have conflicts in different environments if the ID is already in use?

We want to have exactly the same set of ids on all envrionments for testing purpose.


70 custom model converters

PR that implements #70.

Thanks for the PR, this is a great addition to the project


recalculate method?

Hi, thank you so much for the great project.
I was wondering if there was a recalculate/refresh list method for the dynamic lists? It would be to support updating the height of the row once edited.

I have the same use case.
Added PR #55 to manually trigger measure when a row is changing height.

It seems internally it re-calculates on every 'estimateSize' update.
Below is my temporary workaround
const [ignored, forceUpdate] = useReducer(x => x + 1, 0);

const rowVirtualizer = useVirtual({
    ...
    estimateSize: React.useCallback(() => 100, [ignored]);
  });

and then call forceUpdate() to manually update measurements

This issue has been automatically closed due to inactivity. If this issue represented an unfulfilled feature request, please start a new discussion instead of an issue. If this issue needs more attention despite its age, please comment to reopen, or open a new issue with updated information. Thanks!

Any progress on a fix here?

@austincondiff rowVirtualizer.measure();, see PR above #55


prefer uint8array

The PR replaces instanceof Buffer with instanceof Uint8Array.
Non-ECMA-262 standard Node.js Buffer is a subclass of Uint8Array (an ECMA-262 spec-defined built-in Object). The PR removes the necessary buffer polyfill in the browser.
The upstream dependency bencode has also dropped Buffer and replaced it with Uint8Array a year ago: https://github.com/webtorrent/node-bencode/pull/139

Thank you very much for helping optimize the code! I don't know much about Buffer, so I've learned something new!


Add signal in fetch options

Allow to pass a signal in fetch options. Same as in ndaidong/feed-reader/pull/60
const article = await extract(url, undefined, {
    signal: AbortSignal.timeout(10_000)
})

Or, even better, just pass entire fetchOptions to fetch. And check for proxy property,
export type FetchOptions = ProxyFetchOptions | RequestInit

interface ProxyFetchOptions {
  /**
   * the values to configure proxy
   * default: null
   */
  proxy?: ProxyConfig;
}

And in code in the utils/retrieve.js would look like
const defaultHeaders = {
  'user-agent': 'Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0'
}

export default async (url, options = {}) => {
  const { proxy } = options
  const res = proxy ? await profetch(url, proxy) : await fetch(url, {
    ...options,
    headers: options.headers || defaultHeaders
  })

@mcrozz thank you for your contribution. As I've checked, AbortSignal is a quite new feature, only supported by some recent versions of our target platforms. Certainly the tests will fail with Node < 17.3, while there are still some slow-to-update environments where article-parser is running on. I think we should wait a little longer.
Similar to ndaidong/feed-reader#60

Coverage remained the same at 100.0% when pulling 93de55d04122ef65d9cfa53b34c14c910d85ca35 on mcrozz:main into 8acc3d3890198c3eea93c09fe54b61bb1c12dde4 on ndaidong:review-pr319.

Ah, yes, forgot to check compatibility. Yeah, PR can wait


Ct unstable

:tada: This PR is included in version 1.6.1 :tada:
Your semantic-release bot :package::rocket:


[ci skip] adding user @xhochy

Hi! This is the friendly automated conda-forge-webservice.
I've added user @xhochy as instructed in #6.
Merge this PR to add the user. Please do not rerender this PR or change it in any way. It has [ci skip] in the commit message to avoid pushing a new build and so the build configuration in the feedstock should not be changed.
Please contact conda-forge/core to have this PR merged, if the maintainer is unresponsive.
Fixes #6

@pavelzw It would be a great pleasure to work with you on this feedstock!


Marimo plot does not respect altair opacity parameter

Describe the bug
When plotting bar charts with Altair that have an opacity parameter, the altair_chart UI element seems to reset the opacity parameter.
Showing the Altair chart directly displays the correct figure.
chart = alt.Chart(data).mark_bar(opacity=0.5).encode(
    x='x',
    y=alt.Y('value').stack(None),
    color="distribution")
chart = mo.ui.altair_chart(chart)
chart

Version
0.1.39
Code to reproduce
No response

hey @echu, we override the opacity since this is how we signify selection. e.g. items within the selection have opacity 1, and items outside have a smaller opacity (0.2).
for your use case, do you just want to change the selection opacity? or do you want to keep the opacity at 0.5 all the time, regardless of selection?
it is also possible to turn off selection completely, which will prevent mo.ui.altair_chart from changing your opacity

hey @echu, just wanted to bump this thread, would making the selection opacity a ratio of the opacity you pass a viable solution to your issue?

Yeah. I think making it a ratio would be viable for me. Thank you!
I tend not to know, visually, what the alpha is (except for 1 and 0), so
making them relative would do the trick.
On Mon, Nov 13, 2023 at 10:29 AM Myles Scolnick @.***>
wrote:

hey @echu https://github.com/echu, just wanted to bump this thread,
would making the selection opacity a ratio of the opacity you pass a viable
solution to your issue?
—
Reply to this email directly, view it on GitHub
https://github.com/marimo-team/marimo/issues/287#issuecomment-1808763275,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAM3UMIJUWRUOKMUEBRMEDYEJRHZAVCNFSM6AAAAAA6Y3ZPASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBYG43DGMRXGU
.
You are receiving this because you were mentioned.Message ID:
@.***>


fix typo: remove extra "

remove redundant " suffix
Signed-off-by: tianyang ni<EMAIL_ADDRESS>
current: autoscaling
preview: https://deploy-preview-35785--kubernetes-io-main-staging.netlify.app/docs/reference/kubernetes-api/workload-resources/horizontal-pod-autoscaler-v2beta2/#HorizontalPodAutoscalerSpec

Hey @t1anz0ng,
Thanks for contributing k8s website! In this repo, we limited to one language for each PR.
Please just update the en content and leave the zh-cn one to native speakers to change after this PR merged.

Hey @t1anz0ng,
Thanks for contributing k8s website! In this repo, we limited to one language for each PR. Please just update the en content and leave the zh-cn one to native speakers to change after this PR merged.

Hi @Sea-n  Thanks for helping!
Sure, I can split this PR.
But I was wondering if that's necessary while this change is all about URL (which is irrelevant to language).

I've split zh-cn part of this pr into: https://github.com/kubernetes/website/pull/35801  😄 @Sea-n

/assign @divya-mohan0209


Use fixed width types consistently

int32_t* functions were being called with int* arguments. This works on most compilers, but some implementations of stdint.h define int32_t as long since long is at least 32-bits, and technically int is at least 16 bits.
This is a portability issue. I have fixed all of the cases that fail with a toolchain that uses long, but I have not exhaustively gone through the codebase for this consistency in order to keep this PR as atomic as possible.

I should handle these by the weekend

I am guessing the bot is having issues because of Github site-wide problems.
Let me know if you think I need to take any action on the CLA front.

You have commits under 2 different email addresses. Both need to sign the CLA

Also, apologies for the delay in reviewing the PR, it has slipped through the cracks

@googlebot I fixed it.

@googlebot I fixed it.

@googlebot I fixed it.

That was a treasure hunt. I enjoy seeing the daylight between 'git' and 'github' once in a while.
Not sure how my changes could have caused the two failing checks.

Any chance we could re-try those Windows builds?

Sure, retriggered them.


Fix Windows CI Builds

Windows CI builds are currently failing on AppVeyor with:
"C:\projects\nas2d-core\proj\vc14\NAS2D.sln" (default target) (1) ->
"C:\projects\nas2d-core\proj\vc14\NAS2D.vcxproj" (default target) (2) ->
(ClCompile target) ->
  ..\..\src\Filesystem.cpp(226): error C3861: 'PHYSFS_readBytes': identifier not found [C:\projects\nas2d-core\proj\vc14\NAS2D.vcxproj]
  ..\..\src\Filesystem.cpp(267): error C2065: 'PHYSFS_Stat': undeclared identifier [C:\projects\nas2d-core\proj\vc14\NAS2D.vcxproj]
  ..\..\src\Filesystem.cpp(267): error C2146: syntax error: missing ';' before identifier 'stat' [C:\projects\nas2d-core\proj\vc14\NAS2D.vcxproj]
  ..\..\src\Filesystem.cpp(268): error C3861: 'PHYSFS_stat': identifier not found [C:\projects\nas2d-core\proj\vc14\NAS2D.vcxproj]
  ..\..\src\Filesystem.cpp(268): error C2228: left of '.filetype' must have class/struct/union [C:\projects\nas2d-core\proj\vc14\NAS2D.vcxproj]
  ..\..\src\Filesystem.cpp(268): error C2065: 'PHYSFS_FILETYPE_DIRECTORY': undeclared identifier [C:\projects\nas2d-core\proj\vc14\NAS2D.vcxproj]
  ..\..\src\Filesystem.cpp(349): error C3861: 'PHYSFS_writeBytes': identifier not found [C:\projects\nas2d-core\proj\vc14\NAS2D.vcxproj]
  ..\..\src\Filesystem.cpp(434): error C3861: 'PHYSFS_getLastErrorCode': identifier not found [C:\projects\nas2d-core\proj\vc14\NAS2D.vcxproj]
  ..\..\src\Filesystem.cpp(434): error C3861: 'PHYSFS_getErrorByCode': identifier not found [C:\projects\nas2d-core\proj\vc14\NAS2D.vcxproj]
    4 Warning(s)
    9 Error(s)

This is caused by the recent PhysFS upgrade. The methods are available in the PhysFS 3.0.1 release which the code is now targetting. These methods are not available in the old PhysFS 2.0.3 package, which the CI build is still installing.
The changes were introduced during an AppVeyor service interruption due to a configuration problem on our end.

Long term, there seems to be some desire to move away from PhysFS, and towards the new native C++17 <filesystem> library. Due to slow adoption and old tools on some CI providers, such an upgrade is currently blocked.
For now, I think we should try to update the build dependencies on the AppVeyor build to use PhysFS 3.0.1.
The current config uses NuGet packages to install the dependencies. Currently NuGet repositories offer a PhysFS 2.0.3 package, but have no available PhysFS 3.0.1 package.
We could potentially try to put together a NuGet package for PhysFS 3.0.1. I believe the source code licensing should allow use to create such a package ourselves. It might also be of interest to the PhysFS author. Microsoft has documentation on Creating NuGet packages.
Failing that, we could create a script to download the package on the AppVeyor build.
Alternatively, we could potentially rollback the changes for the PhysFS 3.0.1 upgrade. That may be difficult to undo the piecemeal updates though. There are likely quite a few dependent changes already merged on top of them by now.

The proposed changes in the vc17 project PR branch fix these issues. Both Linux and Windows compile clean with Windows only taking 45 seconds each on AppVeyor and Linux a little over 3 minutes for GCC and a little under 3 minutes for Clang on TravisCI. Apple doesn't play well with others and is the only hold out.

PR #120 fixes the Windows build, but it breaks the MacOS build. As such, there's a blocking problem that prevents us from merging it in.
Additionally, PR #120 contained some big behavioural changes that are likely to break downstream projects, such as OPHD. Namely, handling of platform specific write folders. To complicate things, we have no testing in place to verify behavior before and after the changes.
To complicate things further, we can't really get proper before and after testing in place because as this Issue mentions, the Windows CI build is currently broken.
Additionally, PR #120 has grown rather large and hard to review. It's unlikely we'll be able to just merge it in with it's current form.

In terms of the proposal above, updating the PhysFS package (assuming an updated package exists or were created), would be about a 1 line source change, and very easy to verify. It would also only impact the Windows platform, so no chance of breaking builds on other platforms.
It would also unstick development of unit tests that could be used to verify the changes you are proposing in #120.


Disable within a request using modules

I might be missing something, but I don't see a way to use environment variables to disable sending to honeycomb (e.g. for a dev environment).
const honeycombConfig: HoneycombConfig = {}

const module = {
  async fetch(request: Request, env: any, context: ExecutionContext) {
    return await handleRequest(request, env);
  },
};

export default wrapModule(honeycombConfig, module);

As I undestand it, modules put environment variables in the env argument, so they're not accessible at the time of wrapModule().  The ability to specify HONEYCOMB_DATASET and HONEYCOMB_API_KEY as env vars means we don't end up adding data, but we do still end up making requests to honeycomb.
A couple possibilities:

add an env var to disable
add a config key to disable and
-- merge env with HoneycombConfig as we resolve configs, or
-- make more config keys overridable with env vars

Here's what I'm doing (feedback welcome!)
const module = {
  async fetch(request: Request, env: any, context: ExecutionContext) {
    request.tracer.addData({ env: env.ENVIRONMENT })
    return await handleRequest(request, env);
  },
};

const honeycombConfig: Partial<ResolvedConfig> = {
  dataset: 'main',
  sampleRates(data: any): number {
    if (data.response.ok === true) {
      // `request.tracer.addData` provides `data.env`
      return data.env === 'production' ? 4 : 1
    } else {
      return 1
    }
  },
}
export default wrapModule(honeycombConfig, handler)

wrangler.toml:
# ...
[env.staging.vars]
ENVIRONMENT = "staging"

(alternatively, you could inject env vars using esbuild / webpack, etc)

That is a very smart and ugly hack @ptim.. and I am sorry for you having to type that :)
I will change the behaviour so that if no api key or dataset is provided, it just won't send..


Initial commit of twitter processing pipeline sample using python-sdk

This is the initial commit of twitter processing pipeline sample using python-sdk.
Closes #36

I can't speak to the Python code but the readme needs some more work. Please address the references to Spring Boot, Azure service names are inconsistencies, and general grammar issues.

Thanks for the review :) I fixed all comments. initially, I ported your pipeline demo and then realized that sample pipeline app is different from your repo's one.
Anyhow, this is really good sample app :)


[MB-15314] Update the caniuse-lite version

Jira ticket for this change
Summary
I saw this while doing a make client_build:
$ react-app-rewired build
Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run:
  npx update-browserslist-db@latest
  Why you should do it regularly: https://github.com/browserslist/update-db#readme

This PR runs that command to update caniuse-lite.
NOTE: I see that #10286 also did this update (with a slightly older version) a few days ago, but it appears that it got accidentally reverted while resolving a merge conflict.
Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Start the Storybook locally.
make storybook

Terminal 2
Start the UI locally.
make client_run

Terminal 3
Start the Go server locally.
make server_run

Verification Steps for Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Backend

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

Screenshots

Messages

:book:
:link: MB-15314

  Generated by :no_entry_sign: dangerJS against 58a3a5cf47b4386e9cc27bb38018cf61eb907155


Unity

Get the kargo-demo repo wired up into Unity
Use the holos show buildplans command, which doesn't need to execute Helm or
Kustomize but does spin up go routines to execute CUE concurrently (with
different cue contexts in each routine).

mvdan is going to look into this.  The test case is failing properly for both holos and cue in the kargo-demo main branch.
❯ go test
--- FAIL: TestUnity (0.00s)
    --- FAIL: TestUnity/httproutes-cue (3.51s)
        testscript.go:584: WORK=/Users/jeff/Holos/kargo-demo/script-httproutes-cue
            # TODO fix this hack needed to execute from the root (0.000s)
            # Works, but slowly with evalv3=0 (2.557s)
            # Does not work with evalv3=1 (0.948s)
            > env CUE_EXPERIMENT=embed,evalv3=1
            > exec cue export --out yaml -e holos --inject ProjectName=network --inject holos_component_name=httproutes --inject holos_component_path=projects/network/components/httproutes --inject holos_component_labels={"component":"httproutes"} ./projects/network/components/httproutes
            [stderr]
            Component.BuildPlan.spec.artifacts.0.generators.0.resources.HTTPRoute.argocd.spec.rules.0.backendRefs: field not allowed:
                ./httproutes.cue:36:5
            Component.BuildPlan.spec.artifacts.0.generators.0.resources.HTTPRoute.kargo.spec.rules.0.backendRefs: field not allowed:
                ./httproutes.cue:36:5
            [exit status 1]
            FAIL: tests/unity/httproutes-cue.txt:10: unexpected command failure

    --- FAIL: TestUnity/httproutes (4.32s)
        testscript.go:584: WORK=/Users/jeff/Holos/kargo-demo/script-httproutes
            # Works, but slowly with evalv3=0 (2.226s)
            # Does not work with evalv3=1 (2.097s)
            > env CUE_EXPERIMENT=evalv3=1
            > exec holos show buildplans --selector component=httproutes
            [stderr]
            could not run: Component.BuildPlan.spec.artifacts.0.generators.0.resources.HTTPRoute.argocd.spec.rules.0.backendRefs: field not allowed (and 1 more errors) at builder/v1alpha5/builder.go:517
            Component.BuildPlan.spec.artifacts.0.generators.0.resources.HTTPRoute.argocd.spec.rules.0.backendRefs: field not allowed:
                /Users/jeff/Holos/kargo-demo/httproutes.cue:36:5
            [exit status 1]
            FAIL: tests/unity/httproutes.txt:8: unexpected command failure

FAIL
exit status 1
FAIL    github.com/holos-run/kargo-demo 5.212s


What is exact process of new block update process and Why share just saved on the DB?

Dears,
Just I wonder why pool saves a shares on the DB and when does it uses a try to find a new block?
and what is exact process of new block found?
Regards,
John Ahn

Try this article since this exceeds the use case of an issue tracker: https://www.grewe.ca/crypto-currency-mining/


Enhanced Font Management with Local and Google Fonts In the shell component

Pull Request Summary: Enhanced Font Management with Local and Google Fonts
Description
This pull request enhances the font management capabilities by refining the handling of the font variable to support both local fonts and Google Fonts seamlessly. It ensures backward compatibility with existing configurations while offering enhanced flexibility in font selection.
Key Changes

Unified Font Variable:

Consolidated font management under the font variable, supporting both single fonts and lists.
Automatically wraps single font strings in an array to simplify configuration.

Local Font Support:

Introduced support for local fonts by detecting paths starting with /.
Dynamically generates @font-face rules for each local font in various formats (WOFF2, WOFF, TTF, OTF, EOT, SVG).

Google Fonts Integration:

Continued seamless integration with Google Fonts.
Generated <link> tags to import specified Google Fonts into the project.

CSS Variable Enhancements:

Created CSS variables for each custom font to facilitate consistent and flexible font styling across the application.
Appended _custom to the names of local fonts in CSS variables to distinguish them from Google Fonts.

Detailed Changes

Font Variable Handling:

Ensured font is always treated as an array, accommodating both single font strings and lists without breaking existing setups.

Font Loading Strategy:

Conditionally processed fonts based on whether their paths start with /, distinguishing between local and Google Fonts.

Enhanced Flexibility:

Expanded the range of font options available to users, from single local fonts to multiple Google Fonts, all managed through a unified configuration.

Example Usage
Single Font (Backward Compatible):
{{!-- Existing usage, no changes needed --}}
{{set "font" "Roboto"}}

Multiple Fonts with Local and Google Fonts:
{{!-- New usage, specifying multiple fonts including local --}}
{{set "font" (array "Roboto" "/path/to/local/font" "Open+Sans")}}

Benefits

Simplified Configuration: Users can specify fonts with ease using a unified approach.
Expanded Font Options: Supports a wide range of fonts, including local and Google Fonts, enhancing design flexibility.
Improved Styling Consistency: CSS variables ensure consistent font styling throughout the application.

Impact

No Breaking Changes: Existing configurations using font will continue to function as expected.
Enhanced Font Management: Provides users with greater control over typography choices, catering to diverse design needs.

This pull request significantly improves font management capabilities, offering users more flexibility and control while maintaining compatibility with existing configurations. It enhances the ability to incorporate both local and Google Fonts seamlessly into projects, ensuring consistent and appealing typography.

please take a look if you like it then I can update the docs.
for the font property it will be:
Specifies the font or fonts to be used for text display. This can be a valid font name from Google Fonts (e.g., 'Roboto', 'Open Sans') or a path to a local font file starting with '/'. Multiple fonts can be specified as an array, allowing for flexible typography options.

This actually completely broke SQLPage, because the startsWith handlebars helper does not exist. I'll fix it, but it is a sign that I really need to add better CI tests.
and @amrutadotorg , you should probably test your changes before proposing them ;)

Thank you, will do that next time.


[GUI] Displayed feerate is underestimated for primary path spends

This issue arises from the improvement in size estimation from #1125. It only affects the value displayed and not how the underlying transaction is created.
The displayed feerate for new spends & PSBTs is underestimated:

Note that when viewing the transaction itself, the exact feerate is shown:

See https://github.com/wizardsardine/liana/pull/1150#discussion_r1658663088 and subsequent discussion for possible fixes.

The above screenshots were produced by refreshing a single coin with target feerate 1 sat/vb. The same should happen with any feerate, as long as primary path spends are smaller than recovery spends.
I think the GUI can use logic similar to the following to determine which path to use for the size estimate:
https://github.com/wizardsardine/liana/blob/1f86504bdcd789031a8ffea627dd219316414072/src/spend.rs#L670-L673


dev/IPv6: DHCPv6 repaired and tested

Description
The DHCPv6 module was developed but rarely used and tested in real hardware.
It is now tested with a protocol tester, and also we have simulated a situation in which packets get lost.
Also added the possibility to store multiple DNS entries.
Earlier initialisation of IP-address of endpoints: in FreeRTOS_Routing.c, the IP-address will be initialised in case DHCP or RA are not used:
/* IPv4 */
if( pxEndPoint->bits.bWantDHCP == 0U )
{
    pxEndPoint->ipv4_settings.ulIPAddress = ulIPAddress;
}

/* IPv6 */
if( ( pxEndPoint->bits.bWantDHCP == 0 ) && ( pxEndPoint->bits.bWantRA == 0 ) )
{
    /* Using a static IP-address. */
    memcpy( pxEndPoint->ipv6_settings.xIPAddress.ucBytes, pxIPAddress->ucBytes, ipSIZE_OF_IPv6_ADDRESS );
}

The above is necessary because DHCPv6 wants to use a local-link IP-adddress.
Test Steps
Start a DHCPv6 server and activate DHCP:
/* In FreeRTOSIPConfig.h */
#define ipconfigUSE_DHCP    1
#define ipconfigUSE_DHCPv6  1
/* In main.c: */
pxEndPoint->bits.bWantDHCP = pdTRUE;

Checklist:

[x] I have tested my changes. No regression in existing tests.
[ ] I have modified and/or added unit-tests to cover the code changes in this Pull Request.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks Hein and Actory. Now the change looks good.


Update descriptions of New-GcsObject and Write-GcsObject to mention warnings

Fixes issue #228. I'll review examples later.

@ILMTitan FYI. Submitting without a review since it is a trivial change.

LGTM


Adding abi_stable support for tremor-runtime, v4

Pull request
Description
Based on the work at https://github.com/tremor-rs/tremor-runtime/pull/1317, this adds support for the PDK in tremor-runtime. This is the fourth attempt because I had some issues with the branches and because I had to start from scratch as indicated in #1317
Related

RFC
Related Issues: #791 #1077
Related docs: https://nullderef.com/series/rust-plugins/

Checklist

[x] The RFC, if required, has been submitted and approved
[ ] Any user-facing impact of the changes is reflected in docs.tremor.rs
[ ] The code is tested
[ ] Use of unsafe code is reasoned about in a comment
[ ] Update CHANGELOG.md appropriately, recording any changes, bug fixes, or other observable changes in behavior
[ ] The performance impact of the change is measured (see below)

TODO list:

[x] QuiescenceBeacon in ConnectorContext and SourceContext
[x] reconnect::ConnectionLostNotifier in ConnectorContext
[x] No ROption::as_deref: https://github.com/rodrimati1992/abi_stable_crates/pull/68
[ ] Merge with upstream connectors branch
[ ] Restore plugin files to avoid conflicts and too many changes
[ ] Implement the plugin loading
[x] Write a basic metronome plugin
[ ] Figure out config for connectors
[ ] Get rid of builtin/non-builtin plugins with the help of Matthias
[ ] Discuss best way to load plugins:

Recursively from TREMOR_PATH (would require adding a new directory in the default value)
Non-recursively from TREMOR_PATH (would require adding a new directory in the default value)
Configured in the YAML

[ ] Async support (with https://docs.rs/async-ffi/)
[ ] No simd_json_derive::Serialize impl for any abi_stable types
[ ] Clean up the warnings (first run cargo fix)
[ ] Make clippy happy
[ ] Get tests working
[ ] Take care of the remaining FIXMEs and TODOs
[ ] Figure out how to show librdkafka's version or if it's even necessary

After this is merged:

[ ] Move interface into a separate crate from tremor-runtime (later on to avoid conflicts). Perhaps called tremor-pdk or tremor-plugin.
[ ] Figure out how to make plugin development easier: macros? templates?

Performance

Believe it or not, everything compiles now!! That doesn't mean it works by any means, but I've already spent a lot of time just trying to get it to compile (mainly using repr(C) everywhere without issues)

Closing in favor of #7


Homebrewery Saving Issue

Error Code
Error: Too Many Requests

require<.superagent</Request/<@https://homebrewery.naturalcrit.com/homebrew/bundle.js:78380:21
require<[9]</Emitter.prototype.emit@https://homebrewery.naturalcrit.com/homebrew/bundle.js:1954:20
require<.superagent</Request.prototype._end/<@https://homebrewery.naturalcrit.com/homebrew/bundle.js:78674:10

{
  "status": 429,
  "method": "PUT",
  "url": "/api/update/DdTxNO4gMjzA"
}

### Your description of what happened:

I cannot save my creations on homebrewery

It's being looked at, thanks for the report. Will update you once it's fixed.

This problem should be resolved now.  If it persists for you, please followup in this thread.
Closing this comment as a duplicate.


pythonPackages: ensure all derivations provide python modules

This adds a test to ensure no new uses of buildPythonApplication can be added to python-packages.nix.
Python packages can be grouped into two groups: 1) applications and 2) packages providing importable modules. In python-packages.nix we only want to have 2). 1) should be in the top-level package set.
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Ha, no, this test fails because I forgot about setuphooks. In this case the wrapPython hook:
error: wrapPython should use `buildPythonPackage` or `toPythonModule` if it is to be part of the Python packages set.

Is there an eval penalty to this? and if so how high would it be?

Is there an eval penalty to this? and if so how high would it be?

Additional eval load is negligible for this.

We really need types in Nixpkgs so we can check them and filter based on them.

Other solutions:

whitelist
mark setup hooks as such and allow hooks

Some packages to consider as well:

python (the interpreter), I think we could use toPythonModule on it.
recursivePthLoader. Should get rid of this.

Cross is broken with this change.

Everything seems to be OK now. I am surprised to see rebuilds though.

Some packages now get a duplicate package in a closure. I guess an incorrect hook is being used.

Bytecode has differences in filenames, but that would be fixed if we would build wheels as intermediate step and use CA then.

This seems to have broken neovim-remote on the stdenv call in doCheck.

This seems to have broken neovim-remote on the stdenv call in doCheck.

https://github.com/NixOS/nixpkgs/issues/198281

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/i-cant-update-my-system-due-to-buildpythonpackage/22886/7

this broke the fix i did in https://github.com/NixOS/nixpkgs/pull/196052#issuecomment-1279615337
before 33d12e5f0bcc61d8e12d07fd73ad981f0d42ab59:
nix-repl> pkgsCross.aarch64-multiplatform.python3Packages.xpybutil.nativeBuildInputs
[ «derivation /nix/store/hvb9yxgv1133cfhxxd869sibldvv2vdx-python3-3.10.7.drv» «derivation /nix/store/v880cnh4ml7czmivfbk3cdh93hz9yvbn-hook.drv» «derivation /nix/store/f243ab7wv92gqsmc9h7gr0qcnj0xcgdb-hook.drv» «derivation /nix/store/880lf8895bzn8d94lrr2y7ilgkxq0lc4-python-remove-tests-dir-hook.drv» «derivation /nix/store/fzjnhawfs1wpw58hcd1vxd9y750dc08y-python-remove-bin-bytecode-hook.drv» «derivation /nix/store/n8l59iparx98yfw8g5ydqmzmk3fdic75-setuptools-setup-hook.drv» «derivation /nix/store/7vyhynlaxlva1rpvfl0hpdl3qywi9qmc-pip-install-hook.drv» «derivation /nix/store/0l76r5pf69smrl631qa801sjkyb8isk6-python-namespaces-hook.sh.drv» «derivation /nix/store/zipz2sj6ncyllb2z53p0fmsirq601rj7-python-output-dist-hook.drv» ]

after 33d12e5f0bcc61d8e12d07fd73ad981f0d42ab59:
nix-repl> pkgsCross.aarch64-multiplatform.python3Packages.xpybutil.nativeBuildInputs
[ «derivation /nix/store/bhz39ds4v02hn6x4py4mzjyilw4a589h-python3-aarch64-unknown-linux-gnu-3.10.7.drv» «derivation /nix/store/q0pdz5z18bfra7841qwdqq9i3g5na3w7-hook.drv» «derivation /nix/store/f243ab7wv92gqsmc9h7gr0qcnj0xcgdb-hook.drv» «derivation /nix/store/880lf8895bzn8d94lrr2y7ilgkxq0lc4-python-remove-tests-dir-hook.drv» «derivation /nix/store/fzjnhawfs1wpw58hcd1vxd9y750dc08y-python-remove-bin-bytecode-hook.drv» «derivation /nix/store/x9b2q51spifxvzsxj90if1h4nb617pys-setuptools-setup-hook.drv» «derivation /nix/store/zsh90vnqf3zblmrlyh8py5hxky2bk78a-pip-install-hook.drv» «derivation /nix/store/a4cyp1fcsnlppzrwwbk1ka5xhbj52hnm-python-namespaces-hook.sh.drv» «derivation /nix/store/2hc97nsdi375cv13014c4lardpxk2mgw-python-output-dist-hook.drv» ]


"We are sorry for the inconvenience! Please restart Visual Studio Code." pop out every time when I open VSC

We are sorry for the inconvenience! Please restart Visual Studio Code.

Look here, you might be having this issue:
https://github.com/Microsoft/vscode/issues/1463

@bgse  Thanks.

Closing as duplicate of #1463


C++ binary compiled with -m32 doesn't run outside build environment

Describe the bug
C++ code compiled on x86-64 with -m32 flag (in multiStdenv) runs in the build environment but not when installed. C code (with -m32 flag) on the other hand does run in both environments.
To Reproduce
Steps to reproduce the behavior:

Create mwe.nix

with import <nixpkgs> {};

multiStdenv.mkDerivation {
  name = "mwe";
  unpackPhase = "true";
  buildPhase =
    ''
      mkdir logs
      echo "int main() {}" > tst.cc
      $CXX -m32 -o tst-cxx tst.cc &> logs/cxx.txt
      $CC -m32 -o tst-cc tst.cc &> logs/cc.txt
    '';
  checkPhase =
    ''(
      set -ex
      ./tst-cc
      ./tst-cxx
      )
    '';
  doCheck = true;
  installPhase =
    ''
      mkdir -p $out/
      cp tst-* $out/
      cp -r logs $out/
    '';
}

Build with nix-build mwe.nix (same issue when adding -I nixpkgs=https://github.com/NixOS/nixpkgs/archive/19.09-beta.tar.gz). Output:
these derivations will be built:
 /nix/store/1b7pfm9znmrnjcyk78d8083kghxpxlql-mwe.drv
building '/nix/store/1b7pfm9znmrnjcyk78d8083kghxpxlql-mwe.drv'...
unpacking sources
patching sources
configuring
no configure script, doing nothing
building
running tests
++ ./tst-cc
++ ./tst-cxx
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/8cjp4a90w6mxb2f0wx44cwk0rfkah3rw-mwe
shrinking /nix/store/8cjp4a90w6mxb2f0wx44cwk0rfkah3rw-mwe/tst-cc
shrinking /nix/store/8cjp4a90w6mxb2f0wx44cwk0rfkah3rw-mwe/tst-cxx
strip is /nix/store/0y7jmqnj48ikjh37n3dl9kqw9hnn68nq-binutils-2.31.1/bin/strip
patching script interpreter paths in /nix/store/8cjp4a90w6mxb2f0wx44cwk0rfkah3rw-mwe
checking for references to /build/ in /nix/store/8cjp4a90w6mxb2f0wx44cwk0rfkah3rw-mwe...
/nix/store/8cjp4a90w6mxb2f0wx44cwk0rfkah3rw-mwe

Run (set -x; ./result/tst-cc; ./result/tst-cxx ). Output:
+ ./result/tst-cc
+ ./result/tst-cxx
./result/tst-cxx: error while loading shared libraries: libstdc++.so.6: wrong ELF class: ELFCLASS64

Expected behavior
Successful build and run of the two executables.
Additional context
This is a Minimal Working Example, the issue arises for me with a large codebase which must be compiled with -m32
Metadata
Result of nix run nixpkgs.nix-info -c nix-info -m:

system: "x86_64-linux"
host os: Linux 5.2.14, NixOS, 19.03.173481.8a30e242181 (Koi)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.2.2
channels(musteresel): ""
channels(root): "nixos-19.03.173481.8a30e242181"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

result/logs/cc.txt
result/logs/cxx.txt

Adding dontPatchELF = true; to the mwe.nix "fixes" this issue; thus this is seems to be a problem with patchelf.
Manually running patchelf --debug --shrink-rpath tst-cxx with both the ${pkgs.patchelf} and ${pkgsi686Linux.patchelf} shows the same result; it shrinks the rpath and removes the required path for libstdc++.so.6:
# executed during nix-build buildPhase
$ ldd tst-cxx
        linux-gate.so.1 (0xf7fd4000)
        libstdc++.so.6 => /nix/store/yfcj76xvkmzxd5jri3l76n4a5gc93xwp-gcc-7.4.0-lib/lib/libstdc++.so.6 (0xf7e49000)
        libm.so.6 => /nix/store/v1dks37jzwmy7r7sfd1famp99508sln6-glibc-multi-2.27/lib/32/libm.so.6 (0xf7d46000)
        libgcc_s.so.1 => /nix/store/yfcj76xvkmzxd5jri3l76n4a5gc93xwp-gcc-7.4.0-lib/lib/libgcc_s.so.1 (0xf7d28000)
        libc.so.6 => /nix/store/v1dks37jzwmy7r7sfd1famp99508sln6-glibc-multi-2.27/lib/32/libc.so.6 (0xf7b54000)
        /nix/store/v1dks37jzwmy7r7sfd1famp99508sln6-glibc-multi-2.27/lib/32/ld-linux.so.2 (0xf7fd5000)

$ patchelf --debug --shrink-rpath tst-cxx
patching ELF file `tst-cxx'
Kernel page size is 4096 bytes
removing directory `/nix/store/x11ar1k58y1m5zkddwa48mpd788p0jzb-mwe2/lib64' from RPATH
removing directory `/nix/store/x11ar1k58y1m5zkddwa48mpd788p0jzb-mwe2/lib' from RPATH
removing directory `/nix/store/yfcj76xvkmzxd5jri3l76n4a5gc93xwp-gcc-7.4.0-lib/lib' from RPATH
removing directory `/nix/store/v1dks37jzwmy7r7sfd1famp99508sln6-glibc-multi-2.27/lib/32' from RPATH
new rpath is `/nix/store/v1dks37jzwmy7r7sfd1famp99508sln6-glibc-multi-2.27/lib:/nix/store/yfcj76xvkmzxd5jri3l76n4a5gc93xwp-gcc-7.4.0-lib/lib64'

$ ldd tst-cxx
        linux-gate.so.1 (0xf7fd4000)
        libstdc++.so.6 => not found
        libm.so.6 => /nix/store/sjsvwd9sqxjflmslnf8xs48aqpkb2sjy-glibc-2.27/lib/libm.so.6 (0xf7ecc000)
        libgcc_s.so.1 => /nix/store/sjsvwd9sqxjflmslnf8xs48aqpkb2sjy-glibc-2.27/lib/libgcc_s.so.1 (0xf7eaf000)
        libc.so.6 => /nix/store/sjsvwd9sqxjflmslnf8xs48aqpkb2sjy-glibc-2.27/lib/libc.so.6 (0xf7cdb000)
        /nix/store/v1dks37jzwmy7r7sfd1famp99508sln6-glibc-multi-2.27/lib/32/ld-linux.so.2 (0xf7fd5000)

I'm using patchelf 0.9, this is fixed in at least patchelf 0.10-pre-20180509 ... so this should be fixed as soon as patchelf 0.10 hits the repo (I guess that's a massive rebuild, though, so probably only for the next release?)

Leaving a note if someone stumbles over this and tries to create a 32 bit C++ binary:
pkgsi686Linux.stdenv doesn't even add 64 bit library directories to the rpath, thus when using this instead of stdenvMulti the issue with patchelf is circumvented


Default robots setting generate noindex nofollow meta tag

Package version: 4.0.2
So the issue is that the docs don't give any valid config for include every site page. I've tried just adding the module to the modules array to see if that works by default.
modules: [
    '@nuxtjs/tailwindcss',
    '@nuxt/content',
    '@pinia/nuxt',
    '@nuxt/image',
    '@nuxtjs/sitemap',
    '@nuxtjs/google-fonts',
    '@vite-pwa/nuxt',
    '@nuxtjs/robots'
  ],

So no that fives me noindex nofollow meta tag
I tried adding a config like this
robots: {
    groups: [
      {
        userAgent: '*',
        allow: ['/'],
        disallow: []
      }
    ]
  },

If I look into the nuxt dev tools it is ok. An my robots meta tag is as follows:
<meta name="robots" content="noindex, nofollow" data-hint="disabled in development">

If I run production build my tag is
<meta name="robots" content="noindex, nofollow">
I've also tried:

routeRules

routeRules: {
    '/': { robots: 'index, follow' }
  },

routeRules: {
    '/': { robots: true }
  },

routeRules: {
    '/**': { robots: true }
  },

having metaTag: false, but I guess it's a bad idea

My question is how do I just have my pages crawled by robots?

Are you able to provide a minimal reproduction? It seems like you're not deploying your site using a production environment (the default)

I got the same issue and searched for two hours, why it didn't work and if I made a configuration error.
What I found out is that this issue relates with #137. When downgrading only the robots package to v4.0.2 the meta tag works again.
see: https://github.com/nuxt-modules/robots/issues/137#issuecomment-2299684308
{
  "devDependencies": {
    "@nuxtjs/seo": "^2.0.0-rc.18",
  },
  "overrides": {
    "@nuxtjs/robots": "4.0.2"
  }
}

Are you able to provide a minimal reproduction? It seems like you're not deploying your site using a production NODE_ENV (the default)

Unfortunately I don't, but I've resolved the issue by downgrading the robots package to version to ^3.0.0
In this version everything works by default without extra steps
It seems like the documentation lack some step or one can skip it by selecting nuxt config option for example

Regarding a possible reproduction.
I use Vercel as my hoster and use the default deployment process.
Maybe this helps 👍
This is my config:
  site: {
    indexable: process.env.VERCEL_ENV === 'production',
    redirectToCanonicalSiteUrl: true,
    url: 'https://www.domain.com',
    name: 'My project name',
    description: 'My project description',
    defaultLocale: 'en',
  }

Please try the latest version, there was a bug in one of the patch versions. Otherwise, please provide a reproduction.

redirectToCanonicalSiteUrl: true,

I'm a bit confused
What issue is fixed? I've tried updating version to 4.1.3 but still no fix for my issue

As you stated in your issue, the <meta> robots tag was always the following:
<meta name="robots" content="noindex, nofollow">

The issue for that was because of a new release of @nuxtjs/robots. @harlan-zw pushed a bugfix and new release to @nuxtjs/robots and also @nuxtjs/seo that fixes the issue.
At least on my project, everything works fine now using routeRules to disable some pages from indexing.

Thanks I'll try via routeRules

If you still have issues with the latest release please provide a minimal reproduction and I'll do my best to help.


Create User APIs with Unit tests

Purpose

The purpose of this PR is to fix #36
The purpose of this PR is to fix #37
Goals

Create an API for users to apply as a mentor
Create an API for users to apply as a mentee
Approach

Created the requested APIs
Used hardcoded data for profile Ids
Checklist

[x] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[x] I have read and understood the development best practices guidelines ( http://bit.ly/sef-best-practices )
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

Related PRs

N/A
Test environment

Ubuntu 19.04
OpenJDK 1.8
IntelliJ IDEA
Learning

N/A

PS: I haven't added the unit tests for the APIs.
Please review and let me know whether the directory structure and the controller names are correct or not.

Updated with the requested changes

@YohanAvishke i updated the PR with requested changes.
Btw, the unit tests i wrote for the service layer are kind of hard coded.

Updated with the changes


backend (auth): Remove Session usage, add JWT bearer auth logic, dynamically set router dependencies

Removes previous SessionMiddleware usage, and get_session endpoint
Fixes the GET /auth_strategies endpoint
Modifies /login and /auth to return a JWT token on successful authentication
Adds config/routers.py file to define default or auth dependencies. These dependencies are set during app creation time
Adds unit tests

Codecov Report
Attention: Patch coverage is 90.14085% with 21 lines in your changes missing coverage. Please review.

Please upload report for BASE (main@17a67df). Learn more about missing BASE report.

Files
Patch %
Lines

...c/backend/services/auth/strategies/google_oauth.py
75.00%
7 Missing :warning:

src/backend/routers/auth.py
53.84%
6 Missing :warning:

src/backend/services/auth/utils.py
63.63%
4 Missing :warning:

src/backend/main.py
83.33%
2 Missing :warning:

src/backend/config/auth.py
75.00%
1 Missing :warning:

src/backend/services/auth/jwt.py
96.77%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #163   +/-   ##
=======================================
  Coverage        ?   87.48%
=======================================
  Files           ?      119
  Lines           ?     3812
  Branches        ?        0
=======================================
  Hits            ?     3335
  Misses          ?      477
  Partials        ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Presentation of information about archive collections

What is it and who's it for?
Researchers using archive collections
Problems to solve:

Prioritising information about archive on a /works page
https://alistapart.com/article/priority-guides-a-content-first-alternative-to-wireframes/
Answer the user question: what will I find here?
Adapt /works template to accommodate all archive catalogue information

User story
As a new researcher
I need clear and understandable information about the archive
So that I can understand what I’m looking at
As a researcher
I need information about the archive collection
So I can understand the context of what I’m looking at
As an experienced researcher
I would like more detailed information about the collection
So that I can build connections with other material, here or elsewhere

Whimsical board of content you'll find at each level of an archive. Includes examples of how the level of content varies: https://whimsical.com/4jnDSBCY5taaVnKxD1Gf8U

28 May 2020:

improve breadcrumbs, incl. don't highlight the final thing on the breadcrumb, move breadcrumbs above title, have everything inside central dropdown if needed
changes to siblings
put the above behind a toggle

Then can start showing to colleagues (Dom & Alice)

Consolidation of Slack discussions regarding breadcrumbs:
zpl://screen?pid=5aab926b4b6efde01259e959&sid=5ed6793a2f84953e0064550a
https://zpl.io/2GJqYKj

In prep for round 2 of testing with external users:
Breadcrumbs: leave as is, retest
Works page

Clarify Identifiers section and language

Hold off until round 2 testing completed:

Confirm arrangement of notes; set arrangement of data in API
Labelling CTA for tree navigation


Handling values from/to server improvement

Fix on handling values from/to server :
- Replace usage of unsafe eval() by a simple formula parser (fix security hole by removing code execution from remote server)
- Apply bytemask supplied by registry map to values read : fix incoherent data for at least "ENABLE" type items.

Nice catch on the eval()


Limit doesn't work how it does in re.FindAllIndex

The way you stop searching when limit is reached:
https://github.com/boyter/go-string/blob/2ecd9cca2b2d28df28fd5f4f3609f4acaee8ce53/index.go#L182
...means that you can't return the same results as re.FindAllIndex(), because it will return the first N matches and you'll return the first N matches over the first set of case permutations.
You need to search for upto limit results for each case permutation and then return the first N matches from that set of results.

Hah I had a feeling this would have an issue, when I refactored it way back in the day.
I tend to use -1 most of the time so I never actually ran into this. Ill have to ensure a test is added for it.

Resolved with https://github.com/boyter/go-string/pull/2 and new tag v1.0.1 for you to use.
Thanks for reporting.


Fix aesni_xts compile error

Block copy bug..

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

That was a painfully easy fix...  yup, it builds perfectly.

Thanks RIchard. Merged to master.


Unable to log out from Fauxton when setting cookie_domain

Description
When the cookie_domain is set to mydomain.com the logout button in Fauxton shows a message that the logout was successful but it actually doesn't logout.
Steps to Reproduce

Add the cookie domain setting to CouchDB (explained here) to your domain
Login as admin through Fauxton and try to logout

Expected Behaviour
Should logout and display the login page
Your Environment

CouchDB version used: 3.0
Browser name and version: Chrome 80
Operating system and version: CentOS 8

Additional Context

This may be related to my issue  https://github.com/apache/couchdb/issues/2655

same cause as https://github.com/apache/couchdb/issues/2655, yup. A PR is up for it.

Thanks!


function build should use the same --no-pull strategy as function create

As a developer i would like the same behavior from both function build and function create
E.g. when the image names for the builder and run-image use dev.local, this should trigger --no-pull for local-path builds.

per #964 function build is now renamed to function update


Bug: Error in hlexists

Started getting this error recently, not sure what is wrong.  Happens even when I only do
require 'cokeline' .setup {}

for the config.

Thanks for reporting, I'll look into this today.

I'm not able to reproduce this, and in the defaults there should never be a dict passed to hlexists. What version of nvim are you using?

This error has noting to do with cokeline.  Apologies for the noise!


Add Foldable and Traversable instance to List (fixes #65)

For some reason I don't get notification about PRs. So perhaps ping me when creating one.


Add "NieR: Automata" units.

Added max stats and pot stats for 21O, 9S, Eve, Adam, A2, and 2B. Added event recipe equipment for NieR event, as well as TMR rewards for new NieR: Automata units.

Thanks a lot for the pull request ! I'm having a very busy week-end, and was wondering when I'd have the time to do that, your help was godsent !
Just a small remark, you changed the format of all data.json, and used an old version (missing item from last week), so it was impossible to automatically merge the pull request. Awesome job nonetheless !

Ah, my bad! I thought I had fetched from origin before starting on it, but I guess not. Either way, I'm glad the help was useful, happy to contribute what I can, when I can!
I used jsonpp to pretty-print and then minify data.json once the data had been input. Is there a particular method of minifying JSON that you can recommend, to avoid future formatting issues?

You're right in that data.json should be minified. At the moment, it is not, to allow for easier (manual) modification. So it is your good thinking (and my lack of minification) that made it hard for me to merge them.
I think about it. I'll probably minify it, it is a good principle. And then the future pull request you may send won't cause problem.
Anyway, thanks a lot again !


nest_1_reservoir_195ml_bugfix

Closes issue #15949.
well "A1" coordinates needs to match that of nest_12_reservoir_15ml so tips don't crash into the divider between wells for liquid aspirations.

After discussing internally, we think the better approach for now is for the protocol to add an explicit offset. Details here: https://github.com/Opentrons/opentrons/issues/15949#issuecomment-2289094399
Thank you again for bringing this to our attention!


fixes plural for multiple word model name translation

since plural_resource_name uses the .downcase method when using i18n keys, it breaks translation when pluralizing a multiple word model.
for example, when translating a model named BlogPost, it searches for a yaml key such as:
activerecord.models.blogpost

instead of:
activerecord.models.blog_post

as rails does.
By using i18n_key instead of downcase the problem is fixed.

Hey @mtylty,
I'm working on registering simple pages to active admin. Doing so, I refactored the Naming methods. I discovered that #i18n_key is not available in all versions of rails (3.0.0 does not implement it for instance).
See https://github.com/rails/rails/commit/4f90b28e06589a51f4655e38e94c948aaf02d05f
Thanks for your contribution anyway!


Corrected branch name in link to Swift repository

Corrected branch in link to Swift repository to main (renamed from master)

Thank you @csknns! Looking at the raw text of the README.md file, I see two other references to master which can probably be updated as well—would you like to fix those also?

@stephentyrone I missed those! Now all three references are corrected

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test


Introduce a python async reading for files

Tell us more about this new feature.
As expected using aiofiles to read from mountpoints3 provides a pretty good speed up.
from time import time
import os
from tqdm import tqdm
import asyncio
import aiofiles

folder = "imagenet/train/n02837789"

paths = [os.path.join(folder, f) for f in os.listdir(folder)]

t0 = time()
for path in tqdm(paths, total=len(paths)):
    with open(path, "rb") as f:
        data = f.read()
print(time() - t0)
# out:<PHONE_NUMBER>922577

t0 = time()
async def read_file(path):
    async with aiofiles.open(path, mode='rb') as f:
        contents = await f.read()

coros = []
for path in paths:
    coros.append(read_file(path))
loop = asyncio.new_event_loop()
asyncio.set_event_loop(loop)
results = loop.run_until_complete(asyncio.gather(*coros))
print(time() - t0)
# out: 67.671071767807

I believe it could be possible to get even faster with a custom aofiles library that supports multi part download over the await f.read()
from mountpoints3 import aiofiles

async def read_file(path):
    async with aiofiles.open(path, mode='rb') as f:
        contents = await f.read(part_size=1 << 22) # trigger multi part download and store the data into an ordered buffer while flushing to python

Hey @tchaton, what's the challenge we want to solve with this feature? Are we trying to maximize single file throughput by opening a file multiple times?
Instead, can this issue be solved by parallelizing reads over multiple files (so long as the workload plans to process the files concurrently)?

Internally, Mountpoint is already triggering a multi-part download when you call await f.read(). It won't matter in this case because imagenet images are so small that one request per file is the right answer, but for larger files, Mountpoint will use a prefetcher and will automate the multi-part download for you already.

Hey @dannycjones @jamesbornholt, you are right. The challenge I am trying to solve is the slowness from reading from a s3 mount using synchronous code. However, this is something I can enforce on my side. So nothing to be added on your end.


Add script to initialize an oasis-node client

Pulls and compares the genesis file from a provided URL. If a new genesis file is pulled, wipe state.
Starts oasis-node client from provided config file.
Adds script to deployment Docker image.

I'd consider prefixing the script name with unsafe or debug to make it clear that this script will fetch arbitrary genesis data from the network and may wipe state.

Please explain why this needs to be in oasis-core?

Good point. What is the workflow that will use this script? Can that script/job implement this logic independently?

Please explain why this needs to be in oasis-core?

Good point. What is the workflow that will use this script? Can that script/job implement this logic independently?

^ @david-yan, @ravenac95 ?

@kostko you're right, there's no reason for this script to exist in oasis-core. I've moved this to a new repo. The new PR can be found here https://github.com/oasislabs/dockerfiles/pull/1


InternalLifecycleIntegration memory leak on P emulator

In co.recharge.consumer.debug:1.15.2:96.
* flow.InternalLifecycleIntegration has leaked:
* static FontsContract.sContext
* ↳ DebugConsumerApp.injectedAuthenticatedStuff
* ↳ ConsumerApp$InjectedAuthenticatedStuff.onSignedInHelper
* ↳ OnSignedInHelper.signInHooks
* ↳ array OnSignedIn[].[4]
* ↳ PlaceDirections.placeIDToDirectionsRelays
* ↳ LinkedHashMap.tail
* ↳ LinkedHashMap$LinkedHashMapEntry.value
* ↳ BehaviorRelay.state
* ↳ RelaySubscriptionManager.value
* ↳ RelaySubscriptionManager$State.observers
* ↳ array RelaySubscriptionManager$RelayObserver[].[0]
* ↳ RelaySubscriptionManager$RelayObserver.actual
* ↳ OperatorObserveOn$ObserveOnSubscriber.child
* ↳ OnSubscribeOnAssembly$OnAssemblySubscriber.actual
* ↳ SafeSubscriber.actual
* ↳ ActionSubscriber.onNext
* ↳ WalkingTimeView$setPlace$1.this$0 (anonymous implementation of rx.functions.Action1)
* ↳ WalkingTimeView.!(mContext)!
* ↳ FlowContextWrapper.!(mBase)!
* ↳ MainActivity.mFragments
* ↳ FragmentController.mHost
* ↳ Activity$HostCallbacks.mFragmentManager
* ↳ FragmentManagerImpl.mAdded
* ↳ ArrayList.elementData
* ↳ array Object[].[0]
* ↳ InternalLifecycleIntegration

A fun thing I learned today is that Flow uses Fragments for some reason?  I'm looking at the InternalLifecycleIntegration code and I'm pretty much baffled by what's going on.  Looks like it attaches a fragment to the Activity in onCreate, but then somehow FragmentManager is keeping a reference to it even after the activity has been destroyed?

You need to unsubscribe your lambdas. Use composite disposables.