14th of June Updates

Evaluation metrics

Embeddings

1.1 Question ID = 1 (6,231 questions)

Model
Question ID
Correct matches
Accuracy (%)

Mixtral
1
333
5.3

Llama3
1
398
6.4

all-mpnet-base-v2
1
4425
71.0

multi-qa-MiniLM-L6-cos-v1
1
4260
68.4

multi-qa-mpnet-base-cos-v1
1
4858
78.0

all-MiniLM-L12-v2
1
4027
64.6

1.2 Question ID = 2 (46,872 questions)

Fine-tuned Model

Wrapper + ApiBuilder

ApiBuilder

Fine-tuning model:
Trained 2 two models using small_corpus dataset on Unsloth in Google colab:

First model used 50k question and answer pairs trained one epoch on tinyLlama 1.1 B (Llama2 small version)
Second model trained for 5 epochs one same data same model
Manual evaluation of subset of (50) questions randomly selected from the training set:
Model 1: did follow the answering-question structure, but it repeated itself. No number was accurate.
Model 2: Answer structure improves, but numbers are still off.

Next steps:
Since increasing the data size only increases the task complexity, increasing epochs seems to be the way to go, at least for this testing stage.
Also, training a bigger model (Llama2 7B Mistral 7B)
Move training to Caleuche (Free Colab resources are exhausted) and train 2 versions:

TinyLlama 10 epoch
Llama2/Mistral 7B 5 epoch
Evaluate them using the RAG framework to compare metrics.

Agreed next steps:
@alebjanes will work on finalizing the evaluation with the additional questions. If there are too many combinations of questions she will do a random sampling. She will post results next wednesday as she will be out for a week afterwards.
@pippo-sci's next steps written above ☝ , once we evaluate these results with RAG framework we will determine next steps


Couchbase container does work as expected when using it with JUnit 5

I tried to use @TestContainers and @Container to bootstrap a Couchbase in a docker for testing purpose.
@SpringBootTest
@Testcontainers
@ActiveProfiles("test")
class PostRepositoryWithDynamicPropertiesTest {
    private static final String COUCHBASE_IMAGE_NAME = "couchbase";
    private static final String DEFAULT_IMAGE_NAME = "couchbase/server";
    private static final DockerImageName DEFAULT_IMAGE = DockerImageName.parse(COUCHBASE_IMAGE_NAME)
            .asCompatibleSubstituteFor(DEFAULT_IMAGE_NAME);

    @Container
    final static CouchbaseContainer couchbaseContainer = new CouchbaseContainer(DEFAULT_IMAGE)
            .withCredentials("Administrator", "password")
            .withBucket(new BucketDefinition("demo").withPrimaryIndex(true))
            .withStartupTimeout(Duration.ofSeconds(60));

    @DynamicPropertySource
    static void bindCouchbaseProperties(DynamicPropertyRegistry registry) {
        registry.add("spring.couchbase.connection-string", couchbaseContainer::getConnectionString);
        registry.add("spring.couchbase.username", couchbaseContainer::getUsername);
        registry.add("spring.couchbase.password", couchbaseContainer::getPassword);
        registry.add("spring.data.couchbase.bucket-name", () -> "demo");
    }

}

When running the application it always refused to connect.
com.couchbase.client.core.deps.io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: no further information: localhost/<IP_ADDRESS>:50392

I also used other database with testcontainers, others are not problematic.
And I use an Spring Boot initializer class to bootstrap it manually, it works.
@SpringBootTest
@ContextConfiguration(initializers = PostRepositoryTest.TestContainerInitializer.class)
@ActiveProfiles("test")
class PostRepositoryTest {

    static class TestContainerInitializer implements ApplicationContextInitializer<ConfigurableApplicationContext> {
        private static final String COUCHBASE_IMAGE_NAME = "couchbase";
        private static final String DEFAULT_IMAGE_NAME = "couchbase/server";
        private static final DockerImageName DEFAULT_IMAGE = DockerImageName.parse(COUCHBASE_IMAGE_NAME)
                .asCompatibleSubstituteFor(DEFAULT_IMAGE_NAME);

        @Override
        public void initialize(ConfigurableApplicationContext configurableApplicationContext) {
            final CouchbaseContainer couchbaseContainer = new CouchbaseContainer(DEFAULT_IMAGE)
                    .withCredentials("Administrator", "password")
                    .withBucket(new BucketDefinition("demo").withPrimaryIndex(true))
                    .withStartupTimeout(Duration.ofSeconds(60));

            couchbaseContainer.start();

            configurableApplicationContext
                    .addApplicationListener((ApplicationListener<ContextClosedEvent>) event -> couchbaseContainer.stop());
            TestPropertyValues.of(
                            "spring.couchbase.connection-string=" + couchbaseContainer.getConnectionString(),
                            "spring.couchbase.username=" + couchbaseContainer.getUsername(),
                            "spring.couchbase.password=" + couchbaseContainer.getPassword(),
                            "spring.data.couchbase.bucket-name=demo"
                    )
                    .applyTo(configurableApplicationContext.getEnvironment());
        }
    }

}

Update: I found on the Github actions, sometime the later failed. And always one of them failed. I am not sure the reason. See the github actions log: https://github.com/hantsy/spring-reactive-sample/runs/4199996412?check_suite_focus=true
If I ran the tests one by one, it worked well.  I guess there are some clean work not performed in the running tests that affects the further tests.
On Github actions, I have to add scripts to clean the Docker data and run them one by one to make sure it working. see: https://github.com/hantsy/spring-reactive-sample/blob/master/.github/workflows/boot-data-couchbase.yml#L31
  cd boot-data-couchbase
  mvn -q clean test -Dtest=PostRepositoryWithDynamicPropertiesTest
  docker rm $(docker ps -aq) -f
  mvn -q clean test -Dtest=PostRepositoryTest

Originally posted by @hantsy in https://github.com/testcontainers/testcontainers-java/discussions/4676

Hi @hantsy, thanks for reporting.
Can you share the logs of the CouchbaseContainer in case of a failing connection?
cc @daschl

@hantsy thanks for raising the issue. Can you tell us more about the tests you are performing? If you say one-by-one they work, then at least the initialization of the container must be working fine. To be clear - the testcontainers lib is not performing any clean-up between the runs, so you have to clean up the state (i.e. clearing data) on your own. Or are you seeing a different issue? From the CI logs above somehow it seems that the SDK cannot connect to the port that is offered.

@daschl I am not sure the exact reason of this.  To produce it, checkout my examples: https://github.com/hantsy/spring-reactive-sample/blob/master/boot-data-couchbase  and run mvn clean test in the project root.
It will run all the tests and will fail in the second test.

Still encountered issue in the latest testcontainers 1.17.6 and Spring Boot 30.
See: https://github.com/hantsy/spring-reactive-sample/actions/runs/3589943257/jobs/6042847518#step:4:2133

I've been taking a look at this and something it can be noticed among the test execution is some ports provided by testcontainers are being used in both tests. Some of them are 51700, 51696, 51722 which can be found in the logs attached. So, looks like the client is using ports provided during the test execution in both test classes.
log1.txt
log2.txt

@hantsy, In order to do not have troubles with the containers as mentioned before. I had to add @DirtiesContext(classMode = DirtiesContext.ClassMode.AFTER_CLASS) to both test classes. After that the only issue I have is when retrieving information. I'm not a Couchbase expert so not sure what could I miss.
In the log attached. I have enabled the couchbase client logs and if we see the connectionString and the port 64724 used in the first tests is also used in the second one.
Do you mind opening a ticket in spring-data-couchbase? I think that would be the best place to tackle this issue.
couchbase-log.txt


Performance Metrics for Zuul/Eureka

Is there a way to collect performance metric for Zuul and Eureka related to : throughput, response time, overhead (chaining requests) and error rate.

Do the registered routes not show up in /metrics?

I do not see the registered routes showing up in /metrics.
I do see metrics information on the hystrix ribbon commands which wraps the calls to downstream clients from zuul, on /metrics endpoint of zuul.
For Example,,
gauge.servo.hystrix.hystrixcommand.ribboncommand..rollingcountfallbackemit:
gauge.servo.hystrix.hystrixcommand.ribboncommand..requestcount:
But, I do not see any info on throughput, responsetime or errorrate.
Do we have to add any beans to generate the metrics info accordingly

We have the following metrics registered by default for any route:
route metrics.
We also enabled hystrix and are using Turbine for aggregating hystix streams:


refactor(localization_component_launch): rename lidar topic

Description

rename lidar topic.
/sensing/lidar/<lidar name>/outlier_filtered/pointcloud --> /sensing/lidar/<lidar name>/pointcloud
Related PRs
Merge all Related PRs at the same time.
https://github.com/autowarefoundation/autoware-documentation/pull/491
https://github.com/autowarefoundation/autoware.universe/pull/5781
https://github.com/autowarefoundation/sample_sensor_kit_launch/pull/82
https://github.com/autowarefoundation/autoware_launch/pull/722
https://github.com/RobotecAI/awsim_sensor_kit_launch/pull/12
https://github.com/autowarefoundation/awf_reference_sensor_kit_launch/pull/7
Tests performed

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@YamatoAndo The file change seems fine to me, but the DCO workflow isn't passed since your commit is not signed up with your e-mail address. Could you check this out?


Chrome urls support

What chrome urls are supported in Electron?
chrome://gpu works, but I tried some others and noting else seems to work.

which url are you interested in ? chrome://serviceworker-internals, chrome://webrtc-* chrome://tracing can be used.

Thanks @deepak1556 :)
I was just wondering what is available and didn't find any reference to it in Electron's code. Where did you find it?

https://github.com/atom/brightray/pull/95

Not every chrome:// url is supported, usually only the ones belong to the content module are.

Not every chrome:// urls are supported in Electron.
Basicly, only the ones that has no dependency on Chromium browser' resources are supported. The other ones which relies on Chromium browser related part are not supported, e.g. chrome://extensions, chrome://apps, chrome://history.
The only way to test it is trying to load the chrome urls in Electron to see whether it works.

Thanks :)


⚠ Bofrost.at has degraded performance

In a62028f, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 3408 ms

Resolved: Bofrost.at performance has improved in 1198329.


Starter Gear

Seems like every single class starts with Barbarian Helmet and Weapon not suitable for all classes.

Will be fixed when #72 is merged.


fix Issue#465

Hey I changed the link 'https://github.com/Blocship/star_book/blob/dev/PRIVACY%26POLICY.md' to this 'https://qurantalk.notion.site/Privacy-Policy-for-Starbook-Mobile-App-a8fb153c39dd45dfa5b2cb9a945e3c84?pvs=4' in the links.dart folder.
Let me know if this is Good!

@ayushsingh01042003, You changed the url launcher link, that was not the issue, you have to copy the content from this link https://qurantalk.notion.site/Privacy-Policy-for-Starbook-Mobile-App-a8fb153c39dd45dfa5b2cb9a945e3c84?pvs=4 and paste that content here https://github.com/Blocship/star_book/blob/dev/PRIVACY%26POLICY.md and use this link in url launcher. And feel free to ask for more information if the issue is still not clear to you.

@ayushsingh01042003 Please go through Contributing.md because your Pull request is not meeting the requirements

@AbdullahAhmedSoomro  so what I understand is that i need to copy the contents of this link https://qurantalk.notion.site/Privacy-Policy-for-Starbook-Mobile-App-a8fb153c39dd45dfa5b2cb9a945e3c84?pvs=4 and paste it in the PRIVACY&POLICY.md file of the project and nothing else. Is that correct?

@ayushsingh01042003 yes


nmichaels.org

This PR is:

[x] Adding a new domain

[ ] Updating existing domain size

[ ] Changing domain name

[ ] Removing existing domain from list

[ ] Website code changes (512kb.club site)

[ ] Other not listed

[x] I used the uncompressed size of the site

[x] I have included a link to the GTMetrix report

[x] This site is not an ultra lightweight site

[x] The following information is filled identical to the data file

I confirm that I have read the FAQ section, particularly the two red items around minimal pages and inappropriate content and I attest that this site is neither of these things.

[x] Check to confirm

- domain: www.nmichaels.org
  url: https://www.nmichaels.org
  size: 6.45
  last_checked: 2023-12-22

GTMetrix Report: https://gtmetrix.com/reports/www.nmichaels.org/u7puBs7p/
Note: I linked to the front page, but most useful stuff is on /scripts.py. That page is 6.64 k (https://gtmetrix.com/compare/u7puBs7p/fBBEBtN6), and links to around 86 k of other pages.

Thanks!


STDUNIX_HEADERS not set on Debian?

Hi,
I tried ustl v2.2 on Debian (8.0). ./configure ran fine, but make got me this error:
ustl-2.2$ make
    Compiling sostream.cc ...
In file included from uutility.h:10:0,
                 from ualgobase.h:7,
                 from cmemlink.h:7,
                 from memlink.h:7,
                 from mistream.h:7,
                 from sostream.cc:6:
utypes.h:12:6: error: #error "This library compiles only on UNIX systems."
     #error "This library compiles only on UNIX systems."
      ^
Makefile:48: recipe for target '.o/sostream.o' failed
make: *** [.o/sostream.o] Error 1

Ok, to define HAVE_SYS_STAT_H in config.h did the job.
But I wonder why the configure script does not see that  <sys/types.h> exists (/usr/include/linux/types.h).

HAVE_SYS_STAT_H is defined for /usr/include/sys/stat.h, which contains definitions for fstat and friends. Please check that you have that header. If not, perhaps you should check if your glibc package is correctly installed. apt should have some means of verifying a package ( I've never used a Debian-type distribution, so I just don't know)

/usr/include/sys/stat.h does not exist.
But the file is included is /usr/include/x86_64-linux-gnu/sys/stat.h.
gcc -xc++ -E -v - gives me:
/usr/include/c++/4.9
/usr/include/x86_64-linux-gnu/c++/4.9
/usr/include/c++/4.9/backward
/usr/lib/gcc/x86_64-linux-gnu/4.9/include
/usr/local/include
/usr/lib/gcc/x86_64-linux-gnu/4.9/include-fixed
/usr/include/x86_64-linux-gnu
/usr/include
There is the same problem on a fresh Debian (7.7) install.
I think I need to figure out how the paths are aquired by configure.

Ok, then this is definitely a won't fix. I am frankly appalled by the disrespect some of these Debian derivatives show to the UNIX philosophy. Headers must be in /usr/include somewhere, and system headers must be in there. If you want platform-specific stuff for the non-native platform (the native platform being that for which your distribution is built), put it in /usr/platform. In this case, however, x86_64 is the native platform, and your distribution is engaging in 64-bit hate, pretending that x86_64 is just some addon to i386 that will hopefully go away soon. I absolutely refuse to pander to this abomination, and my only reply to people having problems with these distributions is to use another distribution. My projects are only for UNIX-based systems.
That said, you can specify ./configure --includedir=/usr/include/x86_64-linux-gnu , or --oldincludedir to work around this problem.

./configure --includedir=/usr/include/x86_64-linux-gnu did work, thanks.

Ok, one more comment is needed. After finally succumbing to the pressure of adding the platform directories by default in configure, I'm reverting the change because it is inconsistent with system policy; libustl and the headers are still installed in /usr/lib and /usr/include. There is no way to reliably detect that the /usr/lib/platform scheme is being used, so configure can not automatically do this. So the final official fix is that configure must be run with --includedir=/usr/include/x86_64-linux-gnu --libdir=/usr/lib/x86_64-linux-gnu so that the dependencies are found and uSTL is also installed where the system expects libs and headers to be.


Cannot play newer content, error parsing global option

Running into this issue on playback.

Regular perhaps less demanding TV Series seem to be playing correctly, but larger new release films are throwing this error.

HDR content is currently only supported using HLS Direct streaming mode. For other updates, see https://github.com/ErsatzTV/ErsatzTV/issues/1297

To be clear, this is a duplicate of #1297 - and it is planned to support HDR to SDR transcoding.

Already tried HLS Direct and this behavior is absolutely still occurring regardless of selected streaming mode including HLS Direct, even after restarting ErstatzTV as well as clients.

Which client are you using? If Plex, it only supports MPEG-TS and ignores the streaming mode setting. Other clients need to refresh the M3U to use the newly configured streaming mode.

Appears to be happening on both Jellyfin and TiviMate after deleting and re-adding. Adding as a HDHomeRun in Jellyfin will display SDR content but adding the M3U link just encounters an error.

+1 for this and definitely looking for the day this HDR->SDR arrived so I don't have to chance if it is a HDR movie playing on a channel right now and render this error. Usually I have to quit Kodi entirely instead of waiting it to timeout and remember NOT to switch back to that channel.
Jellyfin seems to have HDR->SDR tonemapping done right in their ffmpeg build. Not sure how they built it but I think the ffmpeg in jellyfin work. Too bad it's dynamically link so there is no way to test it on ErsatzTV container


feat: release version in html meta

Asana Task: Other basic backend infrastructure required to build a basic HR Glides app
Pulled this piece out of #25 so that PR can be smaller. That PR is blocked on infra changes but this one isn't.
Adds the RELEASE env var and application config, and puts it in the HTML meta. The motivation to do this is cuz we need the release for Sentry, but we'll probably want it on the frontend, too, and by putting it in the frontend, it's testable.
 They used to be a mix of Page, Frontend, FrontendPage, and home, and are now consistently ReactApp. I got confused by this when looking for where to put the new test, so I figured I should fix it.
Checklist

Tests:

(x) Has tests
( ) Doesn't need tests
( ) Tests deferred (with justification)

Product/Design sign off:

( ) Okayed the plan for the feature (e.g. the design files, or the Asana task)
( ) Reviewed the feature as implemented (e.g. on dev-green, or saw screenshots)
(x) No review needed

It worked.


Why not Docker for the playground?

Describe the feature you'd like
I'm wondering why there is no dockerfile or a docker-compose.yml for this repo.
It would be nice to allow more new comers to hit one command and start the playground.
Describe alternatives you've considered
create a Dockerfile to host playground:
# Use the official Haskell image as the base image
FROM haskell:8.10

# Set the working directory
WORKDIR /app

# Clone the Plutus repository
RUN git clone https://github.com/input-output-hk/plutus.git /app/plutus

# Change the working directory to the Plutus repository
WORKDIR /app/plutus

# Checkout the specific commit or branch if necessary
# Replace "COMMIT_HASH" with the specific commit hash or "BRANCH_NAME" with the specific branch name
# RUN git checkout COMMIT_HASH
# RUN git checkout BRANCH_NAME

# Update Cabal
RUN cabal update

# Build the Plutus Playground server
RUN cabal build plutus-playground-server

# Build the Plutus Playground client
RUN cd plutus-playground-client \
    && npm install \
    && npm run build

# Expose the server port
EXPOSE 8080

# Start the Plutus Playground server
CMD ["cabal", "run", "plutus-playground-server", "--", "--node-server", "${CARDANO_NODE_HOST_URL}"]

create a docker-compose.yml to handle the playground and cardano-node:
version: "3.8"
services:
  cardano-node:
    container_name: cardano-node-${NETWORK:-preview}
    image: inputoutput/cardano-node:${CARDANO_NODE_VERSION:-latest}
    ports:
      - ${CARDANO_NODE_PORT:-3001}:3001
    volumes:
      - node-db:/data/db
      - node-ipc:/ipc
    logging:
      driver: "json-file"
      options:
        max-size: "200k"
        max-file: "10"
    networks:
      - playground-network

  plutus-playground:
    build:
      context: .
      dockerfile: Dockerfile
    ports:
      - 8080:8080
    volumes:
      - "plutus-data:/app/plutus"
    environment:
          - CARDANO_NODE_HOST_URL=http://cardano-node-${NETWORK:-preview}:${CARDANO_NODE_PORT:-3001}
    networks:
      - playground-network

volumes:
  node-db:
  node-ipc:
  plutus-data:

networks:
  playground-network:

wrong repo


Communication channel for the team

It is kind of hard to get people notified and involved in communication - especially those requiring real-time answers.

GitHub - We all drown in issues and notifications
Slack - We have the CNCF Slack channel but cannot use @here or @channel to notify people.

What should we use going forward?

The CNCF Slack Channel and email have been the preferred way to communicate.


Multi-line object expression parsing problems.

During development I like to write some longer ng-class expressions multi-line. The current regex doesn't support that.
What I mean is:
This works -

      {{:refresh:test}}

This doesn't -

      {{:refresh:test}}

jsbin demo

Closed by #38


Updated User Guide and Developer Guide

User Guide

Corrected the title from "Developer Guide" to "User Guide"
Changed "Example(s)" to "Examples" in Notes Management section to be consistent with the other features
Added notes management feature in command summary section

Developer Guide

Added one user story and one use case for notes management feature (Finding notes)

Coverage remained the same at 92.811% when pulling 15d43d3444bfa05ca664e8a5b9feaba66beeffc5 on jomcruz93:master into 7668f6ddc2ec5bc83727d0b755f369462922f05d on CS2113-AY1819S1-T16-1:master.


Line Decoration Width setting not working properly

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.56.2
OS Version: Linux x64 5.4.0-73-generic (Mint distro)

Steps to Reproduce:

Open VSCode with default settings and without extensions
Open settings.json
Add "editor.lineDecorationsWidth": 0 into it.
Notice that VSCode marks it as Unknown Configuration Setting
Save the file
See the line numbers on the file change its width
Remove the line you've added
Save the file
See that it doesn't turn back to default, leaving your VSCode bugged
Reload the window
See that the error persists

Please if possible I would like to know the default value of it to  update my settings with the default value, since it doesn't make it by itself.
Thanks

editor.lineDecorationsWidth is an internal setting so that is why it shows "Unknown Configuration Setting" and commenting it out in settings.json results in no change. But internal settings pass through (so the behavior you are seeing is intentional). The default value is 10.

I'm sorry, I didn't know it. I found this here. Changing it to the default value fixed it. Thanks


Access/set Row's div's scrollTop?

I want to modify the scrollTop on (the div underlying) a Row, in order to set its scroll position back to the top when the contained content changes.
This is the closest I can get:
<script>
export let content;

let ContentRow;
$: if (content.id && ContentRow) ContentRow.scrollTop = 0; // no good
</script>

<Row class="flex-fill mh-100 scroll" bind:this={ContentRow}>
...
</Row>

but that's no good since ContentRow doesn't have a scrollTop (until I create it there) - the one I want is, I think, the <div>'s in Row.svelte. But as far as I can see that's not accessible from binding to Row?

Hi @OJFord , yes it's a limitation with Svelte, you can'd bind this to custom components..
I could expose the inner div though with a new prop, will take a look

Hi @OJFord , yes it's a limitation with Svelte, you can'd bind this to custom components..
I could expose the inner div though with a new prop, will take a look


[DO NOT MERGE] Add priorities and last modified dates to sitemap

This merges the entire feature branch into master.
The individual changes have already been reviewed separately: #840 #841 #842 #846 #856
https://trello.com/c/I4eQeGus/199-deploy-sitemap-changes
Marked as DO NOT MERGE until we've finished making the pre-deployment measurements.

Oh, I see what you mean. I'm not sure I can squash those commits without changing the commit hashes for the later commits, though. I'd quite like to preserve the history for the feature branch so that the individual PRs still link to the right commits (i.e. the commits which will end up in the history for master after this PR is merged).
Does that seem OK in this case? Or do you know of a better way to do the merge?

Yes, that's fine then!


Support custom exceptions

Only strings are allowed to be thrown right now. This is generally frowned upon in TS world so it would be nice to have support for the expression, even if internally in Lua only the exception's toString() is used.

Resolved in #724.


APICallError [AI_APICallError]: x-api-key header is required

Describe the bug
bolt.new-any-llm> pnpm run dev

bolt@ dev I:\Ai_Lab2\bolt.new-any-llm
remix vite:dev

➜  Local:   http://localhost:5173/
➜  Network: use --host to expose
➜  press h + enter to show help
APICallError [AI_APICallError]: x-api-key header is required
at file:///I:/Ai_Lab2/bolt.new-any-llm/node_modules/.pnpm/@ai-sdk+provider-utils@1.0.9_zod@3.23.8/node_modules/@ai-sdk/provider-utils/dist/index.mjs:405:14
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async postToApi (file:///I:/Ai_Lab2/bolt.new-any-llm/node_modules/.pnpm/@ai-sdk+provider-utils@1.0.9_zod@3.23.8/node_modules/@ai-sdk/provider-utils/dist/index.mjs:310:28)
at async AnthropicMessagesLanguageModel.doStream (file:///I:/Ai_Lab2/bolt.new-any-llm/node_modules/.pnpm/@ai-sdk+anthropic@0.0.39_zod@3.23.8/node_modules/@ai-sdk/anthropic/dist/index.mjs:357:50)
at async fn (file:///I:/Ai_Lab2/bolt.new-any-llm/node_modules/.pnpm/ai@3.4.9_react@18.3.1_sswr@2.1.0_svelte@4.2.18__svelte@4.2.18_vue@3.4.30_typescript@5.5.2__zod@3.23.8/node_modules/ai/dist/index.mjs:3938:23)
at async file:///I:/Ai_Lab2/bolt.new-any-llm/node_modules/.pnpm/ai@3.4.9_react@18.3.1_sswr@2.1.0_svelte@4.2.18__svelte@4.2.18_vue@3.4.30_typescript@5.5.2__zod@3.23.8/node_modules/ai/dist/index.mjs:256:22
at async retryWithExponentialBackoff (file:///I:/Ai_Lab2/bolt.new-any-llm/node_modules/.pnpm/ai@3.4.9_react@18.3.1_sswr@2.1.0_svelte@4.2.18__svelte@4.2.18_vue@3.4.30_typescript@5.5.2__zod@3.23.8/node_modules/ai/dist/index.mjs:86:12)
at async startStep (file:///I:/Ai_Lab2/bolt.new-any-llm/node_modules/.pnpm/ai@3.4.9_react@18.3.1_sswr@2.1.0_svelte@4.2.18__svelte@4.2.18_vue@3.4.30_typescript@5.5.2__zod@3.23.8/node_modules/ai/dist/index.mjs:3903:13)
at async fn (file:///I:/Ai_Lab2/bolt.new-any-llm/node_modules/.pnpm/ai@3.4.9_react@18.3.1_sswr@2.1.0_svelte@4.2.18__svelte@4.2.18_vue@3.4.30_typescript@5.5.2__zod@3.23.8/node_modules/ai/dist/index.mjs:3977:11)
at async file:///I:/Ai_Lab2/bolt.new-any-llm/node_modules/.pnpm/ai@3.4.9_react@18.3.1_sswr@2.1.0_svelte@4.2.18__svelte@4.2.18_vue@3.4.30_typescript@5.5.2__zod@3.23.8/node_modules/ai/dist/index.mjs:256:22
at async chatAction (I:/Ai_Lab2/bolt.new-any-llm/app/routes/api.chat.ts:48:20)
at async Object.callRouteAction (I:\Ai_Lab2\bolt.new-any-llm\node_modules.pnpm@remix-run+server-runtime@2.10.0_typescript@5.5.2\node_modules@remix-run\server-runtime\dist\data.js:37:16)
at async I:\Ai_Lab2\bolt.new-any-llm\node_modules.pnpm@remix-run+router@1.17.0\node_modules@remix-run\router\dist\router.cjs.js:4612:21
at async callLoaderOrAction (I:\Ai_Lab2\bolt.new-any-llm\node_modules.pnpm@remix-run+router@1.17.0\node_modules@remix-run\router\dist\router.cjs.js:4677:16)
at async Promise.all (index 1)
at async callDataStrategyImpl (I:\Ai_Lab2\bolt.new-any-llm\node_modules.pnpm@remix-run+router@1.17.0\node_modules@remix-run\router\dist\router.cjs.js:4552:17)
at async callDataStrategy (I:\Ai_Lab2\bolt.new-any-llm\node_modules.pnpm@remix-run+router@1.17.0\node_modules@remix-run\router\dist\router.cjs.js:4041:19)
at async submit (I:\Ai_Lab2\bolt.new-any-llm\node_modules.pnpm@remix-run+router@1.17.0\node_modules@remix-run\router\dist\router.cjs.js:3900:21)
at async queryImpl (I:\Ai_Lab2\bolt.new-any-llm\node_modules.pnpm@remix-run+router@1.17.0\node_modules@remix-run\router\dist\router.cjs.js:3858:22)
at async Object.queryRoute (I:\Ai_Lab2\bolt.new-any-llm\node_modules.pnpm@remix-run+router@1.17.0\node_modules@remix-run\router\dist\router.cjs.js:3827:18)
at async handleResourceRequest (I:\Ai_Lab2\bolt.new-any-llm\node_modules.pnpm@remix-run+server-runtime@2.10.0_typescript@5.5.2\node_modules@remix-run\server-runtime\dist\server.js:413:20)
at async requestHandler (I:\Ai_Lab2\bolt.new-any-llm\node_modules.pnpm@remix-run+server-runtime@2.10.0_typescript@5.5.2\node_modules@remix-run\server-runtime\dist\server.js:156:18)
at async I:\Ai_Lab2\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.10.0@remix-run+react@2.10.2_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_qwyxqdhnwp3srgtibfrlais3ge\node_modules@remix-run\dev\dist\vite\cloudflare-proxy-plugin.js:70:25 {
cause: undefined,
url: 'https://api.anthropic.com/v1/messages',
requestBodyValues: {
model: 'claude-3-5-sonnet-20240620',
top_k: undefined,
max_tokens: 8000,
temperature: 0,
top_p: undefined,
stop_sequences: undefined,
system: '\n' +
'You are Bolt, an expert AI assistant and exceptional senior software developer with vast knowledge across multiple programming languages, frameworks, and best practices.\n' +
'\n' +
'<system_constraints>\n' +
"  You are operating in an environment called WebContainer, an in-browser Node.js runtime that emulates a Linux system to some degree. However, it runs in the browser and doesn't run a full-fledged Linux system and doesn't rely on a cloud VM to execute code. All code is executed in the browser. It does come with a shell that emulates zsh. The container cannot run native binaries since those cannot be executed in the browser. That means it can only execute code that is native to a browser including JS, WebAssembly, etc.\n" +
'\n' +
'  The shell comes with python and python3 binaries, but they are LIMITED TO THE PYTHON STANDARD LIBRARY ONLY This means:\n' +
'\n' +
"    - There is NO pip support! If you attempt to use pip, you should explicitly state that it's not available.\n" +
'    - CRITICAL: Third-party libraries cannot be installed or imported.\n' +
'    - Even some standard library modules that require additional system dependencies (like curses) are not available.\n' +
'    - Only modules from the core Python standard library can be used.\n' +
'\n' +
'  Additionally, there is no g++ or any C/C++ compiler available. WebContainer CANNOT run native binaries or compile C/C++ code!\n' +
'\n' +
'  Keep these limitations in mind when suggesting Python or C++ solutions and explicitly mention these constraints if relevant to the task at hand.\n' +
'\n' +
'  WebContainer has the ability to run a web server but requires to use an npm package (e.g., Vite, servor, serve, http-server) or use the Node.js APIs to implement a web server.\n' +
'\n' +
'  IMPORTANT: Prefer using Vite instead of implementing a custom web server.\n' +
'\n' +
'  IMPORTANT: Git is NOT available.\n' +
'\n' +
"  IMPORTANT: Prefer writing Node.js scripts instead of shell scripts. The environment doesn't fully support shell scripts, so use Node.js for scripting tasks whenever possible!\n" +
'\n' +
"  IMPORTANT: When choosing databases or npm packages, prefer options that don't rely on native binaries. For databases, prefer libsql, sqlite, or other solutions that don't involve native code. WebContainer CANNOT execute arbitrary native binaries.\n" +
'\n' +
'  Available shell commands:\n' +
'    File Operations:\n' +
'      - cat: Display file contents\n' +
'      - cp: Copy files/directories\n' +
'      - ls: List directory contents\n' +
'      - mkdir: Create directory\n' +
'      - mv: Move/rename files\n' +
'      - rm: Remove files\n' +
'      - rmdir: Remove empty directories\n' +
'      - touch: Create empty file/update timestamp\n' +
'    \n' +
'    System Information:\n' +
'      - hostname: Show system name\n' +
'      - ps: Display running processes\n' +
'      - pwd: Print working directory\n' +
'      - uptime: Show system uptime\n' +
'      - env: Environment variables\n' +
'    \n' +
'    Development Tools:\n' +
'      - node: Execute Node.js code\n' +
'      - python3: Run Python scripts\n' +
'      - code: VSCode operations\n' +
'      - jq: Process JSON\n' +
'    \n' +
'    Other Utilities:\n' +
'      - curl, head, sort, tail, clear, which, export, chmod, scho, hostname, kill, ln, xxd, alias, false,  getconf, true, loadenv, wasm, xdg-open, command, exit, source\n' +
'</system_constraints>\n' +
'\n' +
'<code_formatting_info>\n' +
'  Use 2 spaces for code indentation\n' +
'</code_formatting_info>\n' +
'\n' +
'<message_formatting_info>\n' +
'  You can make the output pretty by using only the following available HTML elements: , , , , , , , , , , , , , , , , , , , , , , , , , , ,
Link to the Bolt URL that caused the error
https://github.com/coleam00/bolt.new-any-llm
Steps to reproduce
pnpm run dev and then i choose ollama and then the model I give the prompt and then this nonsense error comes
Expected behavior
just can't understand why this is happening
Screen Recording / Screenshot
No response
Platform

OS: Windows 11,
Browser: Chrome canary
Version: [e.g. 91.1]

Additional context
No response

same.. im encountering this.. im using ollama on my mac

same here, on the request I specify the model ollama but the server still makes the request to Claude...

if using Ollama 3.2B
go to app/utils/constant.ts
and edit this
export const DEFAULT_MODEL = 'llama3.2:latest';
export const DEFAULT_PROVIDER = 'Ollama';

if using Ollama 3.2B
go to app/utils/constant.ts and edit this
export const DEFAULT_MODEL = 'llama3.2:latest'; export const DEFAULT_PROVIDER = 'Ollama';

it did work but now it returns an api error 500 in this endpoint http://localhost:5173/api/chat

by doing so it now try to reach  url: 'http://localhost:11434/api/chat' which throw an error. This path doesn't exist on ollama

by doing so it now try to reach  url: 'http://localhost:11434/api/chat' which throw an error. This path doesn't exist on ollama

Yeah.. i thought it will automatically use the endpoint of llama. So what is the correct endpoint for llama?

damned, it should be /api/chat, don't know why I get a connection refused while everything is fine on my localhost

Just make sure you started ollama before opening, cuz 500 means bad or
failed connection
On Sat, Nov 2, 2024, 7:38 PM lapiequichante @.***>
wrote:

damned, it should be /api/chat, don't know why I get a connection refused
while everything is fine on my localhost
—
Reply to this email directly, view it on GitHub
https://github.com/coleam00/bolt.new-any-llm/issues/156#issuecomment-2453058180,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUIU7K6XUCTFJHUCSBM6G4LZ6UEZRAVCNFSM6AAAAABRBUDIYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJTGA2TQMJYGA
.
You are receiving this because you commented.Message ID: <coleam00/bolt.
@.***>

I think the issue is that I'm using docker, and port 11434 isn't reachable from the docker itself. But I can't put anything else because the same variable is also used by the FE to get tags (and in that case the request to tags works, but server can't reach ollama). I guess I'll have to try to run it without docker.

Made it work with docker by setting the Ollama base url to "http://host.docker.internal:11434" in app/lib/server/llm/api-keys.ts
and "http://localhost:11434" in app/utils/constants.ts
No idea of what's the cleanest way to solve this.

Made it work with docker by setting the Ollama base url to "http://host.docker.internal:11434" in app/lib/server/llm/api-keys.ts and "http://localhost:11434" in app/utils/constants.ts No idea of what's the cleanest way to solve this.

this means that we will use local for getting tags and host.docker.internal for chat api

so the next problem is that ollama doesn't use editor since the prompt is for claude..

Same problem, ollama cant use editor
On Sat, Nov 2, 2024, 9:31 PM khalidmaquilang @.***>
wrote:

so the next problem is that ollama doesn't use editor since the prompt is
for claude..
—
Reply to this email directly, view it on GitHub
https://github.com/coleam00/bolt.new-any-llm/issues/156#issuecomment-2453104802,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUIU7K4BKGAVQXMI7VRBREDZ6USBTAVCNFSM6AAAAABRBUDIYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJTGEYDIOBQGI
.
You are receiving this because you commented.Message ID: <coleam00/bolt.
@.***>

export const DEFAULT_MODEL = 'llama3.2:latest';
export const DEFAULT_PROVIDER = 'Ollama';

it just simply won't work I did everything by the repo instructions many times

Using docker ?
On Sat, Nov 2, 2024, 10:05 PM bitsentinel-cell @.***>
wrote:

export const DEFAULT_MODEL = 'llama3.2:latest';
export const DEFAULT_PROVIDER = 'Ollama';
it just simply won't work I did everything by the repo instructions many
times
—
Reply to this email directly, view it on GitHub
https://github.com/coleam00/bolt.new-any-llm/issues/156#issuecomment-2453113157,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUIU7K4UC2RMDHCVOZ6ILDTZ6UWBFAVCNFSM6AAAAABRBUDIYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJTGEYTGMJVG4
.
You are receiving this because you commented.Message ID: <coleam00/bolt.
@.***>

export const DEFAULT_MODEL = 'llama3.2:latest';
export const DEFAULT_PROVIDER = 'Ollama';

it just simply won't work I did everything by the repo instructions many times

this is working.. whats the error you are receiving?

i was using chrome canary and that was the problem switched to classic chrome now its working but the editor does not work

export const DEFAULT_MODEL = 'llama3.2:latest';
export const DEFAULT_PROVIDER = 'Ollama';

it just simply won't work I did everything by the repo instructions many times

this is working.. whats the error you are receiving?

it was because of the Chrome canary on classic Chrome it's now ok but the editor somehow won't work now

Make sure you have set the API key correctly in your project. Usually, you can set the API key in the configuration file of your project (such as .env file or other configuration files). For example:
API_KEY=your_actual_api_key_here
In the code, make sure to include this key when sending API requests. The sample code may be as follows:
const response = await fetch('https://api.anthropic.com/v1/messages', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'x-api-key': process.env.API_KEY, // Get the API key from the environment variable
},
body: JSON.stringify(requestBody),
});
Also, seeing that you are using docker, I would like to recommend Servbay to you, which is more professional and easy to use than docker on mac

I am getting errors with Ollama running in docker too. I has worked before though.. not sure whats changed.
I have set http://host.docker.internal:11434 in constant.ts and .env and still not working.
Can confirm all available models are working correctly in Open WebUI.
2024-11-04 23:39:04 bolt-ai-dev-1  |         at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)
2024-11-04 23:39:04 bolt-ai-dev-1  |         at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
2024-11-04 23:39:04 bolt-ai-dev-1  |       errno: -111,
2024-11-04 23:39:04 bolt-ai-dev-1  |       code: 'ECONNREFUSED',
2024-11-04 23:39:04 bolt-ai-dev-1  |       syscall: 'connect',
2024-11-04 23:39:04 bolt-ai-dev-1  |       address: '<IP_ADDRESS>',
2024-11-04 23:39:04 bolt-ai-dev-1  |       port: 11434
2024-11-04 23:39:04 bolt-ai-dev-1  |     },
2024-11-04 23:39:04 bolt-ai-dev-1  |     url: 'http://localhost:11434/api/chat',
2024-11-04 23:39:04 bolt-ai-dev-1  |     requestBodyValues: {
2024-11-04 23:39:04 bolt-ai-dev-1  |       format: undefined,
2024-11-04 23:39:04 bolt-ai-dev-1  |       model: 'llama3.1:latest',
2024-11-04 23:39:04 bolt-ai-dev-1  |       options: [Object],
2024-11-04 23:39:04 bolt-ai-dev-1  |       messages: [Array],
2024-11-04 23:39:04 bolt-ai-dev-1  |       tools: undefined
2024-11-04 23:39:04 bolt-ai-dev-1  |     },
2024-11-04 23:39:04 bolt-ai-dev-1  |     statusCode: undefined,
2024-11-04 23:39:04 bolt-ai-dev-1  |     responseHeaders: undefined,
2024-11-04 23:39:04 bolt-ai-dev-1  |     responseBody: undefined,
2024-11-04 23:39:04 bolt-ai-dev-1  |     isRetryable: true,
2024-11-04 23:39:04 bolt-ai-dev-1  |     data: undefined,
2024-11-04 23:39:04 bolt-ai-dev-1  |     [Symbol(vercel.ai.error)]: true,
2024-11-04 23:39:04 bolt-ai-dev-1  |     [Symbol(vercel.ai.error.AI_APICallError)]: true
2024-11-04 23:39:04 bolt-ai-dev-1  |   },
2024-11-04 23:39:04 bolt-ai-dev-1  |   [Symbol(vercel.ai.error)]: true,
2024-11-04 23:39:04 bolt-ai-dev-1  |   [Symbol(vercel.ai.error.AI_RetryError)]: true
2024-11-04 23:39:04 bolt-ai-dev-1  | }

I am getting errors with Ollama running in docker too. I has worked before though.. not sure whats changed. I have set http://host.docker.internal:11434 in constant.ts and .env and still not working.
Can confirm all available models are working correctly in Open WebUI.
2024-11-04 23:39:04 bolt-ai-dev-1  |         at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)
2024-11-04 23:39:04 bolt-ai-dev-1  |         at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
2024-11-04 23:39:04 bolt-ai-dev-1  |       errno: -111,
2024-11-04 23:39:04 bolt-ai-dev-1  |       code: 'ECONNREFUSED',
2024-11-04 23:39:04 bolt-ai-dev-1  |       syscall: 'connect',
2024-11-04 23:39:04 bolt-ai-dev-1  |       address: '<IP_ADDRESS>',
2024-11-04 23:39:04 bolt-ai-dev-1  |       port: 11434
2024-11-04 23:39:04 bolt-ai-dev-1  |     },
2024-11-04 23:39:04 bolt-ai-dev-1  |     url: 'http://localhost:11434/api/chat',
2024-11-04 23:39:04 bolt-ai-dev-1  |     requestBodyValues: {
2024-11-04 23:39:04 bolt-ai-dev-1  |       format: undefined,
2024-11-04 23:39:04 bolt-ai-dev-1  |       model: 'llama3.1:latest',
2024-11-04 23:39:04 bolt-ai-dev-1  |       options: [Object],
2024-11-04 23:39:04 bolt-ai-dev-1  |       messages: [Array],
2024-11-04 23:39:04 bolt-ai-dev-1  |       tools: undefined
2024-11-04 23:39:04 bolt-ai-dev-1  |     },
2024-11-04 23:39:04 bolt-ai-dev-1  |     statusCode: undefined,
2024-11-04 23:39:04 bolt-ai-dev-1  |     responseHeaders: undefined,
2024-11-04 23:39:04 bolt-ai-dev-1  |     responseBody: undefined,
2024-11-04 23:39:04 bolt-ai-dev-1  |     isRetryable: true,
2024-11-04 23:39:04 bolt-ai-dev-1  |     data: undefined,
2024-11-04 23:39:04 bolt-ai-dev-1  |     [Symbol(vercel.ai.error)]: true,
2024-11-04 23:39:04 bolt-ai-dev-1  |     [Symbol(vercel.ai.error.AI_APICallError)]: true
2024-11-04 23:39:04 bolt-ai-dev-1  |   },
2024-11-04 23:39:04 bolt-ai-dev-1  |   [Symbol(vercel.ai.error)]: true,
2024-11-04 23:39:04 bolt-ai-dev-1  |   [Symbol(vercel.ai.error.AI_RetryError)]: true
2024-11-04 23:39:04 bolt-ai-dev-1  | }

follow this

if using Ollama 3.2B
go to app/utils/constant.ts and edit this
export const DEFAULT_MODEL = 'llama3.2:latest'; export const DEFAULT_PROVIDER = 'Ollama';

then this

Made it work with docker by setting the Ollama base url to "http://host.docker.internal:11434" in app/lib/server/llm/api-keys.ts and "http://localhost:11434" in app/utils/constants.ts No idea of what's the cleanest way to solve this.

Ah nice one! Got it going, i had missed setting the Ollama base url to "http://host.docker.internal:11434/" in app/lib/server/llm/api-keys.ts. Thanks for the assistance.

This only works on linux
If you are running the project with docker compose and have locally ollama service y resolve this by editing the docker compose file and add:
network_mode: "host"


Event-based integration

Hi!
Does odeint support event-based integration?
Sometimes it is useful to stop not on specific finish time, but discrete event, when stop condition of the integrator is not defined by the time t but by a target condition on state y (say y[0]=1.0 for example).
Some open-source libraries provide this functionality, like hipparchus(Java): https://www.hipparchus.org/hipparchus-ode/#Discrete_Events_Handling

odeint Is there a way to implement matlab's ode45 event mechanism such as the following code:
tspan=[0 t_max]; %Time span of simulation in sec
Opt = odeset('Events', @myevent);
[t,x]=ode45(@EOM,tspan,x0,Opt); function [value, isterminal]; %Time span of simulation in sec
function [value, isterminal, direction] = myEvent(t, y)
%value = (y(11) < 0);
value = y(11); isterminal = 1; % myEvent(t, y)
isterminal = 1; % Stop the integration
direction = -1; end
end
Translated with DeepL.com (free version)


Fix render method docblock on facade

The render method can take an array or an Arrayable.
This inconsistency was introduced when #353 was merged.
If we're unhappy with this due to union types, I would suggest we look at merging #377

@hailwood Hey thanks!


Add update subscription permissions card to topic details page

What does this PR do?
Allow developers to update the subscription permissions on a topic.
Test Plan
Manual
Related PRs and Issues
None
Have you read the Contributing Guidelines on issues?
Yes

Draft until console SDK is updated with the required API updates.


Update Licences at Notice.txt to reflect dependency changes.

@M-ZubairAhmed I think this is good to merge? Will let you be the judge :)


refactor(core): no need to await for publish as it can be done asynchronously

So the current situation wasn't good.
If there is a problem with the network connection client would got error (despite proper save).
After the change we get:
Save will happen and user will get a positive result but subscriptions might not get it.
I think this is good behavior/improvement. Verifying to be sure

Current situation
If there is a problem with the network connection to queue client would got an error (despite proper save to db) client cannot react or handle this error (as it is related to server side problem).

Exactly. Any publish error would have resulted in failure of the whole request even if the save / update / delete operations went well.

After the change we get:
Save will happen and user will get a positive result but subscriptions might not get it.
Logging should be improved (but that is actually an template side code.

+1. I think a .then() and .catch() as we can have appropriate logs for each case but went with .finally() and we can add a log message here. I can create a "good first issue" for that.

I think this is good behavior/improvement. Verifying to be sure

Thanks.

Approved and then seen your comment.

+1. I think a .then() and .catch() as we can have appropriate logs for each case but went with .finally() and we can add a log message here. I can create a "good first issue" for that.

Is there any problem with logging that prevents us from this

All good for me


fix: add config and options

:tada: This PR is included in version 1.0.0-alpha.10 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


MoBu 2020 support

Hi,
please could it be possible to get the plugin updated for Windows MoBu 2020 as well?
Thank You so much in advance!

Hi,
Check https://github.com/ue4plugins/MobuLiveLink/pull/18 out for MotionBuilder 2020 support.

,I need the older version livelink  for mobu2015 ,need your help ,you are our technoledge leader ,thanks

Support for MotionBuilder 2020 and 2022 was added in 0762b9a7c8af90c5aa41f3a5e7f02eaa41ec4256, which was released with version 2.5.0.
Thanks!


Add unit test and fix golint issues

Codecov Report

Merging #2 (10a3ce8) into master (df2b290) will increase coverage by 41.88%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           master       #2       +/-   ##
===========================================
+ Coverage   30.15%   72.03%   +41.88%
===========================================
  Files          23       26        +3
  Lines        2484     2650      +166
===========================================
+ Hits          749     1909     +1160
+ Misses       1685      657     -1028
- Partials       50       84       +34

Impacted Files
Coverage Δ

boot/grpc_entry.go
8.42% <ø> (+7.33%)
:arrow_up:

boot/gw_entry.go
36.67% <ø> (+4.24%)
:arrow_up:

boot/gw_server_options.go
72.54% <ø> (+72.54%)
:arrow_up:

boot/prom_entry.go
69.23% <ø> (+20.51%)
:arrow_up:

boot/sw_entry.go
68.10% <ø> (+5.94%)
:arrow_up:

boot/tv_entry.go
88.34% <ø> (+69.93%)
:arrow_up:

interceptor/auth/client_interceptor.go
100.00% <ø> (+100.00%)
:arrow_up:

interceptor/auth/options.go
100.00% <ø> (+60.86%)
:arrow_up:

interceptor/auth/server_interceptor.go
92.15% <ø> (+92.15%)
:arrow_up:

interceptor/context/context.go
98.85% <ø> (+98.85%)
:arrow_up:

... and 39 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update df2b290...10a3ce8. Read the comment docs.


Revert "Updated the Fleet Xfer Docs"

Reverts balena-io/docs#2352 with the comment https://github.com/balena-io/docs/pull/2352#issuecomment-1197253421

@balena-ci I self-certify!


Refactor Chimoney Payment Form

This PR includes several improvements to the Chimoney payment form, such as enhanced validation, better error handling, a loading state during form submission, and disabled button state to prevent multiple submissions.

Hi @uchibeke, I’ve added this PR. Please check and review.


[Discussion] choose appropriate tool for WCAG auto testing / visual regression tests

Problem:

Wagtail need a tool for auto frontend tests
wagtail need auto testing for wcag

Here is the cypress test for wagtail - https://github.com/davojta/test-cypress-for-wagtail
There are several solutions for wcag testing:

pa11yjs
axe-core

There also some options for visual regression testing

cypress
web driver
puppeteer

To be updated later )

To add a bit more context, here are the things we want to test accessibility-wise at the moment:

Icon font replacement to SVG, https://github.com/wagtail/wagtail/issues/4199#issuecomment-358640129, #4821
Document outline & landmarks,  https://github.com/wagtail/wagtail/issues/4199#issuecomment-358640129
Textual labels to icon-only elements, https://github.com/wagtail/wagtail/issues/4199#issuecomment-358640129
Focus management, https://github.com/wagtail/wagtail/issues/4199#issuecomment-358640129
Contrast ratio (WCAG 2.0 AA level), #2224, #4788

For the actual accessibility tester, I feel pretty strongly about picking aXe since it's battle-tested, and is know to have a "no false positives" policy for use in automated tests.

Looking into this further, I see the need for at least two tools / sets of tools, for two separate scenarios:

Dev-time "static analysis" / linting, that can give developers some feedback as they work on their change (e.g. a PR to add a new view in the admin). And can also run through the source code in CI.
Automated E2E integration testing, with browser automation tools, that runs a more comprehensive set of checks.

For the E2E accessibility tests, the most mature is pa11y, already mentioned above. They are working on an Axe integration that would make it perfect (https://github.com/pa11y/pa11y/pull/408). If this doesn't work out, I think the next best would be to have our own Puppeteer + Axe integration (pa11y is an abstraction layer for Puppeteer interactions).
For the dev-time static analysis, I haven't found that many options. Common HTML linting tools do not have good support for fragments, or templating syntax, and do not have mature rules ecosystems like ESLint/stylelint/flake8.
That said jinjalint looks promising. It works out of the box, and finds issues in Wagtail's codebase already (16). In the React world, there's https://github.com/evcohen/eslint-plugin-jsx-a11y, which I think is already used in Wagtail's React linting.
Finally, there is a third category of tools which seem useful during development: runtime analysers that seem like they could be hooked into the dev environment, as well as unit or integration tests:

https://github.com/dequelabs/react-axe for React code
https://github.com/peterbe/django-html-validator for Django templates. See also https://stackoverflow.com/questions/3086637/how-should-i-validate-html-in-django-templates-during-the-development-process.

Feedback most welcome!

Relevant PR: #5245. This does not contain automated integration tests running in CI, because we first need to decide what would be a proper testing environment for those (bakerydemo, a demo site within the Wagtail repository, or something else entirely).
Current progress for the automated integration testing with Pa11y / Puppeteer / jest / Axe is over at https://github.com/thibaudcolas/wagtail-tooling.

@Scotchester interested in looking into this if others want to join forces.

From @allcaps – we can use django-html-validator with an official validator image, which makes the setup much simpler:
docker run -d -p 8888:8888 validator/validator:latest

Image: https://hub.docker.com/r/validator/validator/


Generated infrastructure model

DESCRIPTION
This pull request was automatically generated and adds a UML-deployment diagram to your
documentation. Let me know what you think in the comments.
The diagram can be easily edited, extended or updated using text and code, here
Feedback
Infragenie (www.infragenie.eu) is a free-to-use application, currently in early-preview.
Whether you decide on accepting or rejecting this pull request, we would like to invite you to answer a 5min improvement
survey. This will help us to plan future features and improve the application.
Please answer our survey, here.
Thank you.

Hi, @ukutaht, seeing that you have closed the PR. Can you at least leave a comment about your thoughts about the tool? Also, if you could answer the survey, that would be helpful. Thank you for your time. cc: @DavidS


[bug] bad completion for partial code

Strange // chars
Press enter

// was returned by openai api, something like this may happen depending of context


fix: fix nightwatch cli option (--url) handling

fixes #4619
What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Docs
[ ] Underlying tools
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

Other information:

Oops, wrong issue link. This closes #4618, not #4619


Possible to get contents of tag as string?

I am attempting to make a custom tag that has a toggle to display node/tags as they render  and to view the raw source without transformations. Tried playing around with process and content annotations but they seem to only work with fences. Is there a way to get raw content from tag without using fence?

If you still have the original source string, you can use the node.lines property to get the starting and ending line numbers of the corresponding content from the source. Note that this really only works for block-level elements, we don't currently expose the index within the line of inline elements.
You could also try using the experimental Markdoc formatter to programmatically generate Markdoc source for an individual document node. You can use this by calling Markdoc. __EXPERIMENTAL__format(node). This feature is still under active development and we don't recommend using it in production quite yet (hence the unusual method name) but it might be appropriate for your use case.

Awesome, I can make it work with those for now! At this point I'm only interested in block-level elements so that limitation doesn't matter.
That format function seems neat. Looking forward to it being stable. 👍


pyTransition : SSLError when creating instance

I am using the Python library and trying to create a Transition instance from connection credentials. Here is what I use:
transition_instance = Transition("https://instancename.transition.city", "email", "password")
And here is the result I get every time:
SSLError: HTTPSConnectionPool(host='stm.transition.city', port=443): Max retries exceeded with url: /token (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1006)')))

@tibobliss , the first theory would be a lack on update on the operating system side.

Closing as this is a system issue, not due to the library

@greenscientist maybe an explanation of how it was solved could help people hitting this

People need to make sure they have the latest Root certificate list on their system to ensure that SSL works with every site.
(I will not post here some work around, there's plenty on the rest of the internet :) )


Resize handlers position is wrong for more than 2 panels in one branch

Describe the bug
Having a gap between groups and visible resize handlers (replit theme e.g.), the position of these handlers is wrong if there is more than 2 panels in one direction
To Reproduce
Steps to reproduce the behavior:

Go to https://dockview.dev/demo/?theme=dockview-theme-replit
Set the gap to 20px
Move panels so there is more than 2 in one direction (within the same branch)
See that resize handlers are off

Expected behavior
Handlers position is correct for any amount of panels in one branch
Screenshots
8 panels

3 panels

Desktop (please complete the following information):

Browser: Chrome
Version: Version 127.0.6533.89 (Official Build) (arm64)

Additional context
Add any other context about the problem here.

Seems to be issues with the position of the first and last resize handle containers when gap > 0. Additionally there are some issues with gaps when some panels are hidden using setVisible(false) which @RayJason has raised partial PR fix.
I will combine both issues into a fix for the branch assoicated with this issue.

Fixed in 1.16.0


Generate Reservation CRD

Issue #, if available: https://github.com/aws-controllers-k8s/community/issues/1196
Description of changes:

Allows the creation and termination of multiple instances by defining a Reservation resource backed by RunInstances , DescribeInstances, and TerminateInstances apis

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

kubectl describe reservations sample output: https://gist.github.com/brycahta/66b1bea8c6f8810996344cc0bc0f0fee
This was a reservation for 2 instances and note the Status section contains all instance details so kinda beefy.

/approve

Discussed offline; renaming the resource to Instance and hard-coding min/max count to 1, so a single instance is created and can be managed/modified by the controller (i.e. able add volume to instance). If we proceed with Reservation, then there is no way to update the reservation/collection of instances in this way.

Stale; re-genning as Instance once https://github.com/aws-controllers-k8s/community/issues/1285 is resolved


"implementation of std::marker::Send is not general enough" when using join_all

I'm trying to use join_all to parallelize some async work.
Because my stub function returns a non-Send error type, I consume the error before passing it to join_all using a .map combinator (I have also tried map_err(|e| ())).
The join_all result is then dispatched to tokio:
#![feature(await_macro, async_await, futures_api)]
use futures::future::{FutureExt, TryFutureExt};

/* Cargo.toml dependencies:
tokio = {version = "0.1", features = ["async-await-preview"]}
futures-preview = { version = "0.3.0-alpha" }
*/

async fn stub() -> Result<(), Box<dyn std::error::Error + 'static>> { Ok(()) }

fn main() {
    tokio::run_async(async {
        tokio::await!(futures::future::join_all((1..10).map(|n| {
            stub().map(|r| r.is_ok()).boxed()
        })));
    });
}

This fails badly, with rustc trying to teach me type theory:
error: implementation of `std::marker::Send` is not general enough
  --> src/main.rs:12:5
   |
12 |     tokio::run_async(async {
   |     ^^^^^^^^^^^^^^^^
   |
   = note: `std::marker::Send` would have to be implemented for the type `std::ptr::Unique<futures_util::future::join_all::ElemState<std::pin::Pin<std::boxed::Box<futures_util::try_future::map_err::MapErr<impl core::future::future::Future, [closure@src/main.rs:14:28: 14:34]>>>>>`, for any lifetime `'0`
   = note: but `std::marker::Send` is actually implemented for the type `std::ptr::Unique<futures_util::future::join_all::ElemState<std::pin::Pin<std::boxed::Box<futures_util::try_future::map_err::MapErr<impl core::future::future::Future, [closure@src/main.rs:14:28: 14:34]>>>>>`, for some specific lifetime `'1`

However I eventually figured out that if I replace the call to .map(|r| r.is_ok()) by this fut_is_ok wrapper function, everything is fine:
// [...]

async fn fut_is_ok(f: impl std::future::Future<Output=Result<(), Box<dyn std::error::Error + 'static>>>) -> bool {
    await!(f).is_ok()
}

fn main() {
    tokio::run_async(async {
        tokio::await!(futures::future::join_all((1..10).map(|n| {
            fut_is_ok(stub()).boxed()
        })));
    });
}

At this point I am already thoroughly confused, but to add to the fun the following things also make the error go away:

Making stub return Result<(), ()> (without removing the map call)
Making stub return a Send error, but only if the map call is removed
Awaiting only one future instead of doing a join_all

I suspect that somewhere deep in its type parameters the combinator version is still somehow keeping track of the non-Send type I'm trying to  map away, whereas the free function does not.
Is this error about std::marker::Send expected behavior, and is there some core async/await concept I'm grossly misunderstanding here?

Here's a slightly changed example, dropping the Tokio dependency and using current master of futures to avoid needing the extra Box:
#![feature(await_macro, async_await, futures_api)]
use futures::future::{FutureExt};

async fn stub() -> Result<(), Box<dyn std::error::Error + 'static>> { Ok(()) }

fn assert_send<T: Send>(_: T) {}

fn main() {
    assert_send(async {
        await!(futures::future::join_all((1..10).map(|n| {
            stub().map(|r| r.is_ok())
        })));
    });
}

Then, casting the inner closure into a function pointer gives a more useful error message:
stub().map((|r| r.is_ok()) as fn(Result<(), Box<dyn Error + 'static>>) -> bool)

   = note: `std::marker::Send` would have to be implemented for the type `std::ptr::Unique<[futures_util::future::join_all::ElemState<futures_util::future::map::Map<impl core::future::future::Future, fn(std::result::Result<(), std::boxed::Box<(dyn std::error::Error + '0)>>) -> bool>>]>`, for any lifetime `'0`
   = note: but `std::marker::Send` is actually implemented for the type `std::ptr::Unique<[futures_util::future::join_all::ElemState<futures_util::future::map::Map<impl core::future::future::Future, fn(std::result::Result<(), std::boxed::Box<(dyn std::error::Error + '1)>>) -> bool>>]>`, for some specific lifetime `'1`

So, the lifetime it is complaining about is the lifetime of the input parameter of the closure. Swapping the closure for an identical actual function compiles fine.
No idea where the actual issue is, but it seems likely to be a bug related to rustc's handling of lifetimes on trait object inputs to closures inside async blocks.

I think this is https://github.com/rust-lang/rust/issues/64552


Add disconnected cluster best practices guide

Description
This came out of a collaboration with SUSE Support (@gboriso, @axeal) to give customer guidance when it comes to disconnected clusters.

The new disconnected-clusters.md file needs a sidebar entry:
* /docs: [`main`/sidebars.js#L844-L848](https://github.com/rancher/rancher-docs/blob/main/sidebars.js?rgh-link-date=2024-11-05T23%3A12%3A03Z#L844-L848)

* /version-2.9: [`main`/versioned_sidebars/version-2.9-sidebars.json#L809-L812](https://github.com/rancher/rancher-docs/blob/main/versioned_sidebars/version-2.9-sidebars.json?rgh-link-date=2024-11-05T23%3A12%3A03Z#L809-L812)

Done


BitemporalPostgres repo transfer

Thanks. Sorry for hassle.

Not quite sure: is there anything left to do for me?
Regards Michael
Mosè Giordano @.***> schrieb am Di., 12. Juli 2022,
00:22:

Merged #64035 https://github.com/JuliaRegistries/General/pull/64035
into master.
—
Reply to this email directly, view it on GitHub
https://github.com/JuliaRegistries/General/pull/64035#event-6973092416,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC6Y2UR2VRTGFIST2ATAJMTVTSNCVANCNFSM53IQKE6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

No

Hello!
Registrator did not answer yet. Still an issue with this transfer?
regards Michael
On Tue, Jul 12, 2022 at 12:41 AM Mosè Giordano @.***>
wrote:

No
—
Reply to this email directly, view it on GitHub
https://github.com/JuliaRegistries/General/pull/64035#issuecomment-1180970632,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC6Y2UVB5Q4HDC47WGXWDW3VTSPITANCNFSM53IQKE6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

Did you activate it in the new repository? If it's under a new organisation which didn't have the app already enabled you may have to re-enable it. This is how github apps work

I succeeded in activating BitemporalPostgres and LifeInsuranceDataModel.
For BitemporalReactive I got this message
Changing package repo URL not allowed, please submit a pull request with
the URL change to the target registry and retry.
Can You help?
Regards Michael
Mosè Giordano @.***> schrieb am Di., 12. Juli 2022,
09:23:

Did you activate it in the new repository? If it's under a new
organisation which didn't have the app already enabled you may have to
re-enable it. This is how github apps work
—
Reply to this email directly, view it on GitHub
https://github.com/JuliaRegistries/General/pull/64035#issuecomment-1181410417,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC6Y2UR2K5C6PYIV4YQMH4LVTUMPJANCNFSM53IQKE6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

Now everything's fine
Michael Fliegner @.***> schrieb am Di., 12. Juli
2022, 13:53:

I succeeded in activating BitemporalPostgres and LifeInsuranceDataModel.
For BitemporalReactive I got this message
Changing package repo URL not allowed, please submit a pull request with
the URL change to the target registry and retry.
Can You help?
Regards Michael
Mosè Giordano @.***> schrieb am Di., 12. Juli 2022,
09:23:

Did you activate it in the new repository? If it's under a new
organisation which didn't have the app already enabled you may have to
re-enable it. This is how github apps work
—
Reply to this email directly, view it on GitHub
https://github.com/JuliaRegistries/General/pull/64035#issuecomment-1181410417,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC6Y2UR2K5C6PYIV4YQMH4LVTUMPJANCNFSM53IQKE6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>


Fix a few tests

We had a couple of tests that should have been erroring for months. This a disturbing part of Jasmine, but when you added an arbitrary number of tests to our testing suite, then suddenly some of our tests would fail with ObjectUnsubscribedError.
Work done:

Added about 100 tests that were just expect(1).toBe(1) inside of them until I saw the errors happening.
Verified, empirically, that there were no timing errors where the global rxTestScheduler was being used/trampled by multiple tests.
Removed unnecessary setTimeout calls from test helpers and added an additional assurance that rxTestScheduler was being cleared at the end of the test.
Fixed two tests that should have been throwing errors this entire time, to assert the expected errors rather than just throw.
Removed the 100 superfluous tests.

cc/ @staltz who hit this issue and mentioned it in Slack.

LGTM


gRPC calls from iOS app client crashing irohd

Irohad crash when called from a gRPC iOS client with the following error in the log:
terminate called after throwing an instance of 'std::invalid_argument'
  what():  blob_t: input string has incorrect length

Tested on iroha commit e96a186c36
Client side protopbuf and gPRC stub:
I have generated the protobuf objects and the gRPC client stub using https://github.com/grpc/grpc-swift and https://github.com/apple/swift-protobuf plugins for the protobuf compiler.
I'm then sending messages to the peer with:
 let queryServer = Iroha_Protocol_QueryServiceService(address: "\(ip):\(port)", secure: false)
        do {
            var message = createGetAccountInfoMessage()
            addSignatureTo(&message)
            print("============== TESTING QUERY SERVICE ================")
            print(message.textFormatString())
            let find = try queryServer.find(message)
            print(find.textFormatString())
        } catch {
            print(error)
        }
        print("============== END TESTING QUERY SERVICE ================")

Message signature
The message is signed using the iroha-ios cocoapod as:
private func addSignatureTo(_ query: inout Iroha_Protocol_Query) {
        let keypair = IrohaSwift.createKeyPair()
        var signature = Iroha_Protocol_Signature()
        signature.pubkey = keypair.publicKey.data(using: .utf8)!
        signature.signature = sign(publicKey: keypair.publicKey, privateKey: keypair.privateKey, message: try! query.payload.jsonString()).data(using: .utf8)!
        query.signature = signature
}

The signature validation should fail server side as the pub key is not registered on the network. but the daemon crash before outputting any validation error.
Irohad configuration
Genesys block as generated by cli with peer list as localhost:20000
../build/bin/irohad --config config.sample --genesis_block genesis.block --keypair_name node0
config file
{
  "block_store_path" : "/tmp/block_store/",
  "torii_port" : 50051,
  "internal_port" : 20000,
  "pg_opt" : "host=iroha501_postgres_1 port=5432 user=postgres password=mysecretpassword",
  "redis_host" : "iroha501_redis_1",
  "redis_port" : 6379,
  "max_proposal_size" : 10,
  "proposal_delay" : 5000,
  "vote_delay" : 5000,
  "load_delay" : 5000
}

irohad log

[18:19:42][th: 5383][info] [MAIN] << start
[18:19:42][th: 5383][info] [MAIN] << config initialized
[18:19:42][th: 5383][info] [IROHAD] << created
[18:19:42][th: 5383][info] [StorageImpl:initConnection] << Start storage creation
[18:19:42][th: 5383][info] [StorageImpl:initConnection] << block store created
[18:19:42][th: 5383][info] [StorageImpl:initConnection] << connection to Redis completed
[18:19:42][th: 5383][info] [StorageImpl:initConnection] << connection to PostgreSQL completed
[18:19:42][th: 5383][info] [StorageImpl:initConnection] << transaction to PostgreSQL initialized
[18:19:42][th: 5383][info] [IROHAD] << [Init] => storage
[18:19:42][th: 5383][info] [StorageImpl] << Drop ledger
[18:19:42][th: 5383][info] [StorageImpl] << drop dp
[18:19:42][th: 5383][info] [StorageImpl] << drop redis
[18:19:42][th: 5383][info] [StorageImpl] << drop block store
[18:19:42][th: 5383][info] [MAIN] << Block is parsed
[18:19:42][th: 5383][info] [MAIN] << Genesis block inserted, number of transactions: 1
[18:19:42][th: 5383][info] [IROHAD] << [Init] => converters
[18:19:42][th: 5383][info] [IROHAD] << [Init] => peer query
[18:19:42][th: 5383][info] [IROHAD] << [Init] => crypto provider
[18:19:42][th: 5383][info] [IROHAD] << [Init] => validators
[18:19:42][th: 5383][info] [OrderingGate] << Subscribe
[18:19:42][th: 5383][info] [IROHAD] << [Init] => init ordering gate - [true]
[18:19:42][th: 5383][info] [IROHAD] << [Init] => init simulator
[18:19:42][th: 5383][info] [IROHAD] << [Init] => block loader
[18:19:42][th: 5383][info] [IROHAD] << [Init] => consensus gate
[18:19:42][th: 5383][info] [IROHAD] << [Init] => synchronizer
[18:19:42][th: 5383][info] [IROHAD] << [Init] => pcs
[18:19:42][th: 5383][info] [IROHAD] << [Init] => command service
[18:19:42][th: 5383][info] [IROHAD] << [Init] => query service
[18:19:42][th: 5383][info] [MAIN] << Running iroha
[18:19:42][th: 5383][info] [IROHAD] << ===> iroha initialized

as shared model is not used in tori, the problem remains. However, we will migrate to shared model in this sprint :)

Migrated to the new model, that should be stable for now. Feel free to write here if you still have a similar issue


Fine tuning the model

Hello! First, thanks a lot for all your work !
Quick question, I tried to fine-tune the v2.0 of the model on new images using the same scripts I was using for the v1.4 v1.5 (dreambooth and textual inversion), but the results are very bad (almost only noise).
1/ Is it normal ? (what is different about the model architecture / training that makes the training scripts not working well with v2.0?
2/ What should I look into to adapt the fine tuning scripts to work with v2.0 ?
Thanks a lot for your answers!

Yeah trying 768x768 will work I think. V2.0 is better for fine-tuning afaIk!


progress bar doesn't update in place

I just installed pytest-sugar, and the progress bar doesn't get updated in-place for failures. Is this by design? it looks like it works with passing tests. Any ideas?
Also, the progress bar doesn't go to 100% for very very short tests.
(venv)  ~/dev/personal/swarmci   prototyping ●✚  python -m pytest -s --tb=no tests/
Test session starts (platform: darwin, Python 3.5.1, pytest 2.9.2, pytest-sugar 0.7.1)
rootdir: /Users/WesM/dev/personal/swarmci/tests, inifile:
plugins: sugar-0.7.1

 unit/test_job.py ✓✓✓                                                                                14% █▍
 unit/agents/build/test_init.py ✓                                                                                18% █▊

 unit/agents/build/test_stage_runner.py ⨯                                                                                23% ██▍
 unit/agents/build/test_stage_runner.py ⨯⨯                                                                                27% ██▊
 unit/agents/build/test_stage_runner.py ⨯⨯⨯                                                                                32% ███▎
 unit/agents/build/test_stage_runner.py ⨯⨯⨯⨯                                                                               36% ███▋
 unit/agents/build/test_stage_runner.py ⨯⨯⨯⨯⨯                                                                              41% ████▏

 unit/agents/execution/test_job_flow.py ⨯                                                                                45% ████▋
 unit/agents/execution/test_job_flow.py ⨯⨯                                                                                50% █████
 unit/agents/execution/test_job_flow.py ⨯⨯⨯                                                                                55% █████▌
 unit/agents/execution/test_job_flow.py ⨯⨯⨯⨯                                                                               59% █████▉
 unit/agents/execution/test_job_flow.py ⨯⨯⨯⨯⨯                                                                              64% ██████▍
 unit/agents/execution/test_job_flow.py ⨯⨯⨯⨯⨯⨯                                                                             68% ██████▊
 unit/agents/execution/test_job_flow.py ⨯⨯⨯⨯⨯⨯⨯                                                                            73% ███████▍
 unit/agents/execution/test_job_flow.py ⨯⨯⨯⨯⨯⨯⨯⨯                                                                           77% ███████▊
 unit/agents/execution/test_job_flow.py ⨯⨯⨯⨯⨯⨯⨯⨯⨯                                                                          82% ████████▎
 unit/agents/execution/test_job_flow.py ⨯⨯⨯⨯⨯⨯⨯⨯⨯⨯                                                                         86% ████████▋
 unit/agents/execution/test_job_flow.py ⨯⨯⨯⨯⨯⨯⨯⨯⨯⨯⨯                                                                        91% █████████▏
 unit/agents/execution/test_job_flow.py ⨯⨯⨯⨯⨯⨯⨯⨯⨯⨯⨯⨯                                                                       95% █████████▋
 unit/agents/execution/test_job_flow.py ⨯⨯⨯⨯⨯⨯⨯⨯⨯⨯⨯⨯⨯                                                                     100% ██████████

Results (0.16s):
       4 passed
      18 failed

Pytest-sugar has poor support when it comes to supporting all different flags pytest has, such as --tb=no.

I can investigate this issue and maybe submit a PR

Closing an old issue. Feel free to open a new issue if issue still persists.


removed zoom from join + news

I think it is in line what we are planning elsewhere

We could have the most of the email formulated there also but that's peanuts. We include the email anyway in communications-section.


Use asciicast image link

You may be interested in embedding asciicast as image link.

Coverage remained the same at 48.37% when pulling 7be47188630b424ddc9f3fd27dadfe34fbca5fff on sickill:patch-1 into 230cf011c0bb79a39f3984903ade87d8eff1384b on what-studio:master.

Coverage remained the same at 48.37% when pulling 7be47188630b424ddc9f3fd27dadfe34fbca5fff on sickill:patch-1 into 230cf011c0bb79a39f3984903ade87d8eff1384b on what-studio:master.

Coverage remained the same at 48.37% when pulling 7be47188630b424ddc9f3fd27dadfe34fbca5fff on sickill:patch-1 into 230cf011c0bb79a39f3984903ade87d8eff1384b on what-studio:master.

Coverage remained the same at 48.37% when pulling 7be47188630b424ddc9f3fd27dadfe34fbca5fff on sickill:patch-1 into 230cf011c0bb79a39f3984903ade87d8eff1384b on what-studio:master.

Cool!


PageWrapper component (was: MainWrapper and WidthContainer)

Tracking
https://github.com/alphagov/govuk-frontend/blob/master/src/objects/_main-wrapper.scss
and
https://github.com/alphagov/govuk-frontend/blob/master/src/objects/_width-container.scss

Maybe these should just be atoms of PageWrapper #426

https://design-system.service.gov.uk/styles/layout/#page-wrappers

Doing this as part of #427, discussion continued there


BarChart: Ability to style each part of Stack

In stacked bar charts, the entire bar is represented by a single <rect>, making it impossible to style each of them individually. It would be nice to have stacked bars render a rect per part of the stack so that we can style them differently.
Here's an example of what a stacked Bar Chart currently looks like:

And here's what we'd like it to look like:

Notice between the stack we want to be able to set a 0 radius for a more seamless transition between the two and avoid the gap.

Hey @huntabyte , each of these segments is a separate <rect>, but exposing the styling for each rect is not convenient yet, but on my TODO (supporting exactly what you have shown, as well as a flat bottom and rounded top)

one thing that is confusing and like tripped you up is there are a set of transparent <rect>s for each band that are used as tooltip triggers when using <Chart tooltip={{ mode: 'band' }}> (which <BarChart> uses by default.


Beer icon

Icon Request

Icon name: Beer Icon
Tags of this icon: beer, drink, alcohol
Use case: student societies
Screenshots of similar icons:

https://remixicon.com/icon/beer-line
https://remixicon.com/icon/beer-fill


Application of network-delay-with-target-example.yaml file causes crashloopbackoff in controller-manager in chaosmesh

The first step is to apply the network network-delay-with-target-example.yaml file
apiVersion: pingcap.com/v1alpha1
kind: NetworkChaos
metadata:
  name: network-delay-example
  namespace: test
spec:
  action: delay
  mode: one
  selector:
    labelSelectors:
      "app.kubernetes.io/component": "cockroachdb"
    delay:
      latency: "90ms"
      correlation: "25"
      jitter: "90ms"
    direction: to
    target:
      selector:
        labelSelectors:
          "app.kubernetes.io/component": "cockroachdb"
        mode: one
    duration: "10s"
    scheduler:
      cron: "@every 15s"

kubectl apply -f network-delay-with-target-example.yaml
The second step did not produce any chaotic action
Spec:
  Action:     delay
  Direction:  to
  Mode:       one
  Selector:
    Label Selectors:
      App . Kubernetes . Io / Component:  cockroachdb
    Namespaces:
      test
  Value:
Status:
  Experiment:
  Phase:
  Scheduler:
Events:  <none>

The log information of controller-manager is as follows
"/var/run/secrets/kubernetes.io/serviceaccount"}],"livenessProbe":{"httpGet":{"path":"/health","port":"http","scheme":"HTTP"},"initialDelaySeconds":30,"timeoutSeconds":1,"periodSeconds":5,"successThreshold":1,"failureThreshold":3},"readinessProbe":{"httpGet":{"path":"/health?ready=1","port":"http","scheme":"HTTP"},"initialDelaySeconds":10,"timeoutSeconds":1,"periodSeconds":5,"successThreshold":1,"failureThreshold":2},"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","imagePullPolicy":"IfNotPresent"}],"restartPolicy":"Always","terminationGracePeriodSeconds":60,"dnsPolicy":"ClusterFirst","serviceAccountName":"default","serviceAccount":"default","nodeName":"slave2","securityContext":{},"hostname":"my-release-cockroachdb-1","subdomain":"my-release-cockroachdb","affinity":{"podAntiAffinity":{"preferredDuringSchedulingIgnoredDuringExecution":[{"weight":100,"podAffinityTerm":{"labelSelector":{"matchLabels":{"app.kubernetes.io/component":"cockroachdb","app.kubernetes.io/instance":"my-release","app.kubernetes.io/name":"cockroachdb"}},"topologyKey":"kubernetes.io/hostname"}}]}},"schedulerName":"default-scheduler","tolerations":[{"key":"node.kubernetes.io/not-ready","operator":"Exists","effect":"NoExecute","tolerationSeconds":300},{"key":"node.kubernetes.io/unreachable","operator":"Exists","effect":"NoExecute","tolerationSeconds":300}],"priority":0,"enableServiceLinks":true},"status":{"phase":"Running","conditions":[{"type":"Initialized","status":"True","lastProbeTime":null,"lastTransitionTime":"2020-06-09T02:34:35Z"},{"type":"Ready","status":"True","lastProbeTime":null,"lastTransitionTime":"2020-06-09T02:34:49Z"},{"type":"ContainersReady","status":"True","lastProbeTime":null,"lastTransitionTime":"2020-06-09T02:34:49Z"},{"type":"PodScheduled","status":"True","lastProbeTime":null,"lastTransitionTime":"2020-06-09T02:34:35Z"}],"hostIP":"<IP_ADDRESS>","podIP":"<IP_ADDRESS>","startTime":"2020-06-09T02:34:35Z","containerStatuses":[{"name":"db","state":{"running":{"startedAt":"2020-06-09T02:34:36Z"}},"lastState":{},"ready":true,"restartCount":0,"image":"cockroachdb/cockroach:v19.2.5","imageID":"docker-pullable://cockroachdb/cockroach@sha256:9abfdb8fa63d67b15c5cf11628259c8217c4651fd841666a559438aa76fa6912","containerID":"docker://d7ba96b9736ba58a2394953f31f3c77111c529169d4be32d77d88b8ac7abf042"}],"qosClass":"BestEffort"}}]}
2020-06-09T03:00:08.503Z	INFO	controllers.NetworkChaos	Try to apply netem on pod	{"reconciler": "networkchaos", "action": "netem", "namespace": "test", "name": "my-release-cockroachdb-1"}
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x132b0c6]

goroutine 476 [running]:
github.com/pingcap/chaos-mesh/api/v1alpha1.(*DelaySpec).ToNetem(0x0, 0x15561e0, 0x0, 0x18d5e20)
	/src/api/v1alpha1/networkchaos_types.go:307 +0x26
github.com/pingcap/chaos-mesh/controllers/networkchaos/netem.(*Reconciler).applyPod(0xc000370ed0, 0x190dce0, 0xc00020e000, 0xc000c65000, 0xc0001fcc80, 0xc0009471a0, 0xc0009471d0, 0x0, 0x0)
	/src/controllers/networkchaos/netem/types.go:270 +0x2f5
github.com/pingcap/chaos-mesh/controllers/networkchaos/netem.(*Reconciler).applyNetem.func1(0x482774, 0xc00050a040)
	/src/controllers/networkchaos/netem/types.go:367 +0xd0
golang.org/x/sync/errgroup.(*Group).Go.func1(0xc0003f48a0, 0xc000947170)

I cannot reproduce this bug.
Is this the yaml you are using? Looks like there is an indentation problem. Could you please check it with the example here https://github.com/pingcap/chaos-mesh/blob/master/examples/network-delay-with-target-example.yaml?
apiVersion: pingcap.com/v1alpha1
kind: NetworkChaos
metadata:
  name: network-delay-example
  namespace: test
spec:
  action: delay
  mode: one
  selector:
    labelSelectors:
      "app.kubernetes.io/component": "cockroachdb"
    delay:
      latency: "90ms"
      correlation: "25"
      jitter: "90ms"
    direction: to
    target:
      selector:
        labelSelectors:
          "app.kubernetes.io/component": "cockroachdb"
        mode: one
    duration: "10s"
    scheduler:
      cron: "@every 15s"

I cannot reproduce this bug.
Is this the yaml you are using? Looks like there is an indentation problem. Could you please check it with the example here https://github.com/pingcap/chaos-mesh/blob/master/examples/network-delay-with-target-example.yaml?
apiVersion: pingcap.com/v1alpha1
kind: NetworkChaos
metadata:
  name: network-delay-example
  namespace: test
spec:
  action: delay
  mode: one
  selector:
    labelSelectors:
      "app.kubernetes.io/component": "cockroachdb"
    delay:
      latency: "90ms"
      correlation: "25"
      jitter: "90ms"
    direction: to
    target:
      selector:
        labelSelectors:
          "app.kubernetes.io/component": "cockroachdb"
        mode: one
    duration: "10s"
    scheduler:
      cron: "@every 15s"

I can reproduce this bug with that bad yaml now. Seems there are some problems in our validating webhook, bad yaml file like this shouldn't be created at all.

I can reproduce this bug with that bad yaml now. Seems there are some problems in our validating webhook, bad yaml file like this shouldn't be created at all.

That bad yaml is indented incorrectly? @yeya24
Maybe the CRD's controlling-pruning feature can fix this. But that's not enough. We need to define which fields are required.

I used the new yaml file again, it has been successful, but the previous yaml can not be applied successfully in the unaligned format, it is recommended to optimize it


scp: Host does not exist: "C"

Hi guys, I'm facing an issue running the scp command on docker machine for windows.
Machine version (Windows 7):
$ docker-machine version
docker-machine.exe version 0.6.0, build e27fb87

Command:
$ docker-machine scp ~/myfile.txt local-swarm-node-1:~/
Error loading host: Error loading host: Host does not exist: "C"

My guess is machine thinks the path /c/ is a machine instead of a path on the host machine.  Is this supported on windows?
Are only relative paths supported on windows?

Probably a colon : present in Windows paths like C:\Documents\myfile.txt disturbs the scp clients, that expect a colon : is used to separate host from path.

Yes, for scp you are forced into Unix-style filepaths for the time being.  Try using the Toolbox quickstart (or MYSYS_NO_PATHCONV=1 in Git for Windows) and using the Unix notation:
$ docker-machine scp /c/users/rob/myfile.txt local-swarm-node-1:/home/docker`

Tried in git-bash and docker quickstart terminal - same error though
pradeep@seleniumframework ~
$ export MYSYS_NO_PATHCONV=1

pradeep@seleniumframework ~
$ docker-machine scp /c/Users/pradeep/.docker/machine/machines/default/ca.pem default:/home/docker/.docker/
Error loading host: Error loading host: Host does not exist: "C"

It looks a lot like it's still attempt path translation.  Make sure you're using Git for Windows as it's only a specific version that supports MSYS_NO_PATHCONV.

@nathanleclaire I was using another console when I reported this, let me test with the quickstart one and see.

Nope same error with the quickstart terminal:
$ docker-machine scp /c/Users/rvelasquez/myfile.txt local-swarm-node-1:~/
Error loading host: Error loading host: Host does not exist: "C"

Take the slash out before the drive letter of your windows machine.  This worked for me a few days ago, when I experienced the same issue.

I just tried this and it worked... localhost:/c/some-path

Need to specify in docs? @nathanleclaire

I just bumped into the same problem, and indeed the solution is to:

Make sure you specify localhost: at the beginning (there is some specific code in the go implementation around localhost:)
Use "mounted" path, according to cygwin or whichever shell you are using on your windows machine.

This makes it hard to script docker-machine from the outside. I've just put in a fix for machinery around this. What I do is to call mount (which exists in most NIX-like environments on Windows) to list out where c: (or whichever the windows drive letter was) is mounted onto the shell file system. I then cache this for the life-time of the program. It works, but it's kind of clumsy.
Maybe should this (or similar) be done in docker-machine instead. Note that the scp.go implementation workaround using localhost: will have to be modded as it does a split on :, which obviously isn't doing a proper job when the file path contains a : itself. What do you think @nathanleclaire ?

Dears ,please let me know what to do!!
I am not able to copy from my local windows8 machine to the remote ubuntu machine I am using GITbash..The below is sample from my Gitbash output
Maha.Sallam@Maha MINGW64 ~/.ssh
$ MYSYS_NO_PATHCONV=1
Maha.Sallam@Maha MINGW64 ~/.ssh
$ docker-machine scp -r /C/Users/Maha.Sallam/.ssh default:~/.ssh
Error loading host: Error loading host: Host does not exist: "C"
Maha.Sallam@Maha MINGW64 ~/.ssh
$ docker-machine scp -r ~/.ssh default:~/.ssh
Error loading host: Error loading host: Host does not exist: "C"
Maha.Sallam@Maha MINGW64 ~/.ssh
$ docker-machine scp -r localhost:/C/Users/Maha.Sallam/.ssh default:~/.ssh
id_rsa                                                                                100% 1675   428.6KB/s   00:00
id_rsa.pub                                                                                100%  398   128.1KB/s   00:00

@nathanleclaire  please advise ..

I don't understand, @Mhussein27 the last line in your output examples seems to have performed well?

We couldn't get it working even with localhost: prepended, but there's a quick workaround with cat if you want to transfer just one file:
docker-machine ssh machine_name "cat > /destination/file" < /c/source/path/file

and to add another weird version of the problem to the stack:
$ docker-machine -D scp gitlab:~/test .
Docker Machine Version:  0.13.0, build 9ba6da9
Found binary path at C:\Program Files\Docker\Docker\Resources\bin\docker-machine.exe
Launching plugin server for driver openstack
Plugin server listening at address <IP_ADDRESS>:64527
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(sima-gitlab) Calling .GetSSHPort
(sima-gitlab) Calling .GetSSHKeyPath
(sima-gitlab) Calling .GetSSHKeyPath
(sima-gitlab) Calling .GetSSHKeyPath
(sima-gitlab) Calling .GetSSHHostname
(sima-gitlab) Calling .GetSSHUsername
{C:\Program Files\Git\usr\bin\scp.exe [C:\Program Files\Git\usr\bin\scp.exe -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -3 -o IdentitiesOnly=yes -o Port=22 -o IdentityFile="C:\\Users\\dow184\\.docker\\machine\\machines\\gitlab\\id_rsa" debian@<IP_ADDRESS>:~/test .] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> <nil> false [] [] [] [] <nil> <nil>}
usage: scp [-346BCpqrv] [-c cipher] [-F ssh_config] [-i identity_file]
           [-l limit] [-o ssh_option] [-P port] [-S program]
           [[user@]host1:]file1 ... [[user@]host2:]file2
exit status 1

dow184@TOWER-SL MINGW64 ~/src/deployment (master)
$ uname -a
MINGW64_NT-10.0 TOWER-SL 2.9.0(0.318/5/3) 2018-01-12 23:37 x86_64 Msys

dow184@TOWER-SL MINGW64 ~/src/deployment (master)
$ scp  -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -3 -o IdentitiesOnly=yes -o Port=22 -o IdentityFile="C:\\Users\\dow184\\.docker\\machine\\machines\\gitlab\\id_rsa" debian@<IP_ADDRESS>:~/test .
test

I faced same problem. (windows10 home, docker toolbox)
I tried to test scp command, but it failed.
$ docker version
Client:
 Version:       18.02.0-ce
 API version:   1.35 (downgraded from 1.36)
 Go version:    go1.9.4
 Git commit:    fc4de447b5
 Built: Mon Feb 12 19:03:38 2018
 OS/Arch:       windows/amd64
 Experimental:  false
 Orchestrator:  swarm

Server:
 Engine:
  Version:      17.12.1-ce
  API version:  1.35 (minimum version 1.12)
  Go version:   go1.9.4
  Git commit:   7390fc6
  Built:        Tue Feb 27 22:20:43 2018
  OS/Arch:      linux/amd64
  Experimental: false

$ pwd
/c/Users/Jungho/dockerws

$ ls -al
total 30
drwxr-xr-x 1 Jungho 197121    0 3월  12 21:46 ./
drwxr-xr-x 1 Jungho 197121    0 3월  12 21:42 ../
-rw-r--r-- 1 Jungho 197121  390 3월  12 21:17 docker.cow
-rw-r--r-- 1 Jungho 197121  511 3월  12 21:34 Dockerfile
-rw-r--r-- 1 Jungho 197121  569 3월  12 22:00 nginx.conf
-rw-r--r-- 1 Jungho<PHONE_NUMBER> 3월  12 21:46 nginx.conf.invalid

$ docker-machine scp /c/Users/Jungho/dockerws/nginx.conf default:/home/docker
Error loading host: Error loading host: Docker machine "C" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.

How should I get solved??

@SvenDowideit Your log shows that Machine is passing C:\Program Files\Git\usr\bin\scp.exe as the first argument to scp. I see the same, and confirmed it with Process Monitor:

$ docker-machine --version
docker-machine.exe version 0.14.0, build 89b8332

This happens with and without localhost:.

Same problem. Windows 10 using docker quick start terminal
Jason@Forge MINGW64 /d/Minikube/code
$ docker-machine --version
docker-machine.exe version 0.14.0, build 89b8332

$ docker-machine scp docker-media:/home/docker/plexserver.log localhost:/d/Minikube/.
cp: cannot stat 'Files\Git\usr\bin\scp.exe': No such file or directory
ssh: Could not resolve hostname c: Name or service not known
cp: cannot stat 'Files\Git\usr\bin\scp.exe': No such file or directory
cp: cannot stat '-o': No such file or directory
cp: cannot stat 'StrictHostKeyChecking=no': No such file or directory
cp: cannot stat '-o': No such file or directory
cp: cannot stat 'UserKnownHostsFile=/dev/null': No such file or directory
cp: cannot stat '-o': No such file or directory
cp: cannot stat 'LogLevel=quiet': No such file or directory
cp: cannot stat '-3': No such file or directory
cp: cannot stat '-o': No such file or directory
cp: cannot stat 'IdentitiesOnly=yes': No such file or directory
cp: cannot stat '-o': No such file or directory
cp: cannot stat 'Port=63735': No such file or directory
cp: cannot stat '-o': No such file or directory
ssh: Could not resolve hostname identityfile=d: Name or service not known
ssh: connect to host <IP_ADDRESS> port 22: Connection refused
exit status 1

Over a year later this is still broken today.

Well, as nobody seems to be putting some effort into docker-machine, this is not likely to be fixed any time soon.

Still broken as of version 0.16.1, build cce350d7.
However, a kludge of a workaround:
dm -D scp app.jar docker@default:/home/docker/app.jar
...
{C:\cygwin64\bin\scp.exe [C:\cygwin64\bin\scp.exe -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -3 -o IdentitiesOnly=yes -o Port=55718 -o IdentityFile="C:\\Users\\.docker\\machine\\machines\\default\\id_rsa" app.jar docker@<IP_ADDRESS>:/home/docker/app.jar] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> <nil> false [] [] [] [] <nil> <nil>}
ssh: Could not resolve hostname c: Name or service not known
...

Copy the command inside of the square brackets, then paste it to your command-line and run. This works in cygwin's terminal window. I can't vouch for other terminals/setups.
There is obviously quite a bit of confusion as to how to make this work properly.  Since I don't know Go, I don't have much to contribute other than this interim solution.

As a workaround, you can run a scp command and providing the Docker machine's ip and private key, like so:
MYSYS_NO_PATHCONV=1 scp -i $MACHINE_STORAGE_PATH/machines/$DOCKER_MACHINE_NAME/id_rsa \
root@$(docker-machine $DOCKER_MACHINE_NAME ip):/tmp/my-backup.zip \
/S/data/backup/backup_$(date +%Y%m%d_%H%M%S).zip

Works using git bash's scp command.

If you want to cope files from container to local (in Windows), you can

share /d with vm
docker-machine ssh;  then copy files to /d/xxx
exit; then you can see files in Windows /d/xxx


yarn run build:test fails on linux

I am quite new to react on rails, so user error is a great possibility...
When running 'yarn run build:test' on windows it works.
When running the build on linux:
[INFO] Running: yarn run build:test
[INFO] yarn run v0.24.5
[INFO] $ webpack --config webpack.config.js
[INFO] /app/jenkins/jobs/prisme_log_event/workspace/client/webpack.config.js:6
[INFO] const { resolve } = require('path');
[INFO]       ^
[INFO] SyntaxError: Unexpected token {
[INFO]     at exports.runInThisContext (vm.js:53:16)
[INFO]     at Module._compile (module.js:374:25)
[INFO]     at Object.Module._extensions..js (module.js:417:10)
[INFO]     at Module.load (module.js:344:32)
[INFO]     at Function.Module._load (module.js:301:12)
[INFO]     at Module.require (module.js:354:17)
[INFO]     at require (internal/module.js:12:17)
[INFO]     at requireConfig (/app/jenkins/jobs/prisme_log_event/workspace/client/node_modules/webpack/bin/convert-argv.js:96:18)
[INFO]     at /app/jenkins/jobs/prisme_log_event/workspace/client/node_modules/webpack/bin/convert-argv.js:109:17
[INFO]     at Array.forEach (native)
[INFO] error Command failed with exit code 1.
[INFO] rake aborted!
[INFO] Command failed with status (1): [yarn run build:test...]
[INFO] /app/jenkins/jobs/prisme_log_event/workspace/lib/rails_common/tasks/build_helper.rake:40:in `block in (root)'
[INFO] /app/jenkins/jobs/prisme_log_event/workspace/lib/rails_common/tasks/build_helper.rake:39:in `block in (root)'

I am unsure how to handle this.  Any ideas?  It appears I really need to do this before running my tests.
Thanks,
Cris

@cshupp1 you probably don't have babel correctly configured. We'd have to debug this.
If you want personalized help on this, please consider our Coaching Plan.


React 15.0.1

Adaptation of https://github.com/casesandberg/react-color/pull/132 with fixes for failing tests and warnings.

:exclamation: Opened against wrong repo. Sorry!  Going to try this out in our own fork first, then hopefully push upstream to jaeh/react-color.

Tests passed though :smiley:


Remove top-level _static

Top level _static directory is not referenced by docs

will manually delete it once #3239 is landed