First release candidate

[waralex]

Candidate for first release with reverse dependencies

[alexcjohnson]

All these extra timeouts are awkward - we already wait for the server to report it's accessible and then wait for the page to have some dash content - is there something else we need to wait for after those two?

Not an issue to be solved in this repo, the fix needs to be in dash.testing, just curious if you have any insight about what's going on.

[waralex]

@alexcjohnson In fact, here we are waiting for the first callback (i.e. _dash_update_component) to be executed. Since the Julia is JIT compiler, the corresponding code is compiled at this moment. After the release, I plan to do optimization on this side - see where I can more accurately define the types and add the ability to precompile when installing the package.

[alexcjohnson]

OK cool - I suspect it'll be relatively important to get this right for the developer experience, but fine to omit for now. Is there an issue for this in which we can mention the goal to remove all these extra test timeouts?

[alexcjohnson]

💃 🥇 🚀

[waralex]

Candidate for first release with reverse dependencies

[alexcjohnson]

All these extra timeouts are awkward - we already wait for the server to report it's accessible and then wait for the page to have some dash content - is there something else we need to wait for after those two?

Not an issue to be solved in this repo, the fix needs to be in dash.testing, just curious if you have any insight about what's going on.

[waralex]

@alexcjohnson In fact, here we are waiting for the first callback (i.e. _dash_update_component) to be executed. Since the Julia is JIT compiler, the corresponding code is compiled at this moment. After the release, I plan to do optimization on this side - see where I can more accurately define the types and add the ability to precompile when installing the package.

[alexcjohnson]

OK cool - I suspect it'll be relatively important to get this right for the developer experience, but fine to omit for now. Is there an issue for this in which we can mention the goal to remove all these extra test timeouts?

[alexcjohnson]

💃 🥇 🚀

[waralex]

Candidate for first release with reverse dependencies

[alexcjohnson]

All these extra timeouts are awkward - we already wait for the server to report it's accessible and then wait for the page to have some dash content - is there something else we need to wait for after those two?

Not an issue to be solved in this repo, the fix needs to be in dash.testing, just curious if you have any insight about what's going on.

[waralex]

@alexcjohnson In fact, here we are waiting for the first callback (i.e. _dash_update_component) to be executed. Since the Julia is JIT compiler, the corresponding code is compiled at this moment. After the release, I plan to do optimization on this side - see where I can more accurately define the types and add the ability to precompile when installing the package.

[alexcjohnson]

OK cool - I suspect it'll be relatively important to get this right for the developer experience, but fine to omit for now. Is there an issue for this in which we can mention the goal to remove all these extra test timeouts?

[alexcjohnson]

💃 🥇 🚀

[waralex]

Candidate for first release with reverse dependencies

[alexcjohnson]

All these extra timeouts are awkward - we already wait for the server to report it's accessible and then wait for the page to have some dash content - is there something else we need to wait for after those two?

Not an issue to be solved in this repo, the fix needs to be in dash.testing, just curious if you have any insight about what's going on.

[waralex]

@alexcjohnson In fact, here we are waiting for the first callback (i.e. _dash_update_component) to be executed. Since the Julia is JIT compiler, the corresponding code is compiled at this moment. After the release, I plan to do optimization on this side - see where I can more accurately define the types and add the ability to precompile when installing the package.

[alexcjohnson]

OK cool - I suspect it'll be relatively important to get this right for the developer experience, but fine to omit for now. Is there an issue for this in which we can mention the goal to remove all these extra test timeouts?

[alexcjohnson]

💃 🥇 🚀

[waralex]

Candidate for first release with reverse dependencies

[alexcjohnson]

All these extra timeouts are awkward - we already wait for the server to report it's accessible and then wait for the page to have some dash content - is there something else we need to wait for after those two?

Not an issue to be solved in this repo, the fix needs to be in dash.testing, just curious if you have any insight about what's going on.

[waralex]

@alexcjohnson In fact, here we are waiting for the first callback (i.e. _dash_update_component) to be executed. Since the Julia is JIT compiler, the corresponding code is compiled at this moment. After the release, I plan to do optimization on this side - see where I can more accurately define the types and add the ability to precompile when installing the package.

[alexcjohnson]

OK cool - I suspect it'll be relatively important to get this right for the developer experience, but fine to omit for now. Is there an issue for this in which we can mention the goal to remove all these extra test timeouts?

[alexcjohnson]

💃 🥇 🚀

[waralex]

Candidate for first release with reverse dependencies

[alexcjohnson]

All these extra timeouts are awkward - we already wait for the server to report it's accessible and then wait for the page to have some dash content - is there something else we need to wait for after those two?

Not an issue to be solved in this repo, the fix needs to be in dash.testing, just curious if you have any insight about what's going on.

[waralex]

@alexcjohnson In fact, here we are waiting for the first callback (i.e. _dash_update_component) to be executed. Since the Julia is JIT compiler, the corresponding code is compiled at this moment. After the release, I plan to do optimization on this side - see where I can more accurately define the types and add the ability to precompile when installing the package.

[alexcjohnson]

OK cool - I suspect it'll be relatively important to get this right for the developer experience, but fine to omit for now. Is there an issue for this in which we can mention the goal to remove all these extra test timeouts?

[alexcjohnson]

💃 🥇 🚀

[waralex]

Candidate for first release with reverse dependencies

[alexcjohnson]

All these extra timeouts are awkward - we already wait for the server to report it's accessible and then wait for the page to have some dash content - is there something else we need to wait for after those two?

Not an issue to be solved in this repo, the fix needs to be in dash.testing, just curious if you have any insight about what's going on.

[waralex]

@alexcjohnson In fact, here we are waiting for the first callback (i.e. _dash_update_component) to be executed. Since the Julia is JIT compiler, the corresponding code is compiled at this moment. After the release, I plan to do optimization on this side - see where I can more accurately define the types and add the ability to precompile when installing the package.

[alexcjohnson]

OK cool - I suspect it'll be relatively important to get this right for the developer experience, but fine to omit for now. Is there an issue for this in which we can mention the goal to remove all these extra test timeouts?

[alexcjohnson]

💃 🥇 🚀

[waralex]

Candidate for first release with reverse dependencies

[alexcjohnson]

All these extra timeouts are awkward - we already wait for the server to report it's accessible and then wait for the page to have some dash content - is there something else we need to wait for after those two?

Not an issue to be solved in this repo, the fix needs to be in dash.testing, just curious if you have any insight about what's going on.

[waralex]

@alexcjohnson In fact, here we are waiting for the first callback (i.e. _dash_update_component) to be executed. Since the Julia is JIT compiler, the corresponding code is compiled at this moment. After the release, I plan to do optimization on this side - see where I can more accurately define the types and add the ability to precompile when installing the package.

[alexcjohnson]

OK cool - I suspect it'll be relatively important to get this right for the developer experience, but fine to omit for now. Is there an issue for this in which we can mention the goal to remove all these extra test timeouts?

[alexcjohnson]

💃 🥇 🚀