deanrad / antares-ts Goto Github PK
View Code? Open in Web Editor NEWAntares is an Architecture for making real-time applications with confidence.
Home Page: https://deanius.github.io/antares/
License: MIT License
Antares is an Architecture for making real-time applications with confidence.
Home Page: https://deanius.github.io/antares/
License: MIT License
This requires being able to mix in agent properties in at construction time, and having a filter that can mix those properties in to the meta of an action.
With blessed https://github.com/chjj/blessed?
A game should be created which demos Antares triggers, and renderers:
Introduce "muted" concurrency mode where future renders are silently not run while another render is in progress.... Justification: command is running in terminal, you type and hit Enter, should that take effect? Or should it be silently dropped since you didn't know the output of the previous command
The problem was NPM had expired all tokens.
This new one (62b77770-02d7-4d48-bb9f-54398009b5aa) was created and set for Travis CI, and a new build published.
With blessed
https://github.com/chjj/blessed
after
rxjs utilityWorking on demos, I've realized that people need to feel ergonomically what its like to do stuff with Antares (much like DHH did in his demo).
Bottom line is that batching-type transforms (bufferCount, etc) will not yield asi's into renderers, but rather batchesof ASIs.. Either way that kinda makes it unclear how to track completed for a given action. So we silently don't. For now.
def8e99 introduces short-circuits
So - the Fruit Game - if driven by a deterministic observable - its output on multiple platforms could be compared, creating a sort of 'hash' of all its behavior in the event of:
This can ensure that any platform specific changes can be picked up on / guaranteed.
As a by-product of complex async behavior, let me assert on whole tons of conditions without arduously specifying in the language of test assertions.
Since an Observable of input is the abstraction that drives the test processing and assertions, it's easy-peasy to swap out a user-driven one for a scripted one. #winning
ack
Renderers to create an ever-more elaborate chain of logic
Made static images for modes serial, parallel, cutoff
master
branch failed. π¨I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. Iβm sure you can resolve this πͺ.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master
branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:
If those donβt help, or if this issue is reporting something you think isnβt right, you can always ask the humans behind semantic-release.
The npm token configured in the NPM_TOKEN
environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/
.
If you are using Two-Factor Authentication, make configure the auth-only
level is supported. semantic-release cannot publish with the default auth-and-writes
level.
Please make sure to set the NPM_TOKEN
environment variable in your CI with the exact value of the npm token.
Good luck with your project β¨
Your semantic-release bot π¦π
master
branch failed. π¨I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. Iβm sure you can resolve this πͺ.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master
branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:
If those donβt help, or if this issue is reporting something you think isnβt right, you can always ask the humans behind semantic-release.
semantic-release cannot push the version tag to the branch master
on remote Git repository.
Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment.
Good luck with your project β¨
Your semantic-release bot π¦π
Will require addition of { context }
to an ActionStreamItem
and a 2nd argument to agent.process
to become that context.
A blog post can focus on a trivial problem like this, but a demo should use something closer to real life.
master
branch failed. π¨I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. Iβm sure you can resolve this πͺ.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master
branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:
If those donβt help, or if this issue is reporting something you think isnβt right, you can always ask the humans behind semantic-release.
The npm token configured in the NPM_TOKEN
environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/
.
If you are using Two-Factor Authentication, make configure the auth-only
level is supported. semantic-release cannot publish with the default auth-and-writes
level.
Please make sure to set the NPM_TOKEN
environment variable in your CI with the exact value of the npm token.
Good luck with your project β¨
Your semantic-release bot π¦π
@rematch/core has an example like this to check out
action: agent/p/subscribe
Flesh out with tests what it means for 2 agents (in one process) to publish/subscribe observables
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.