Adding always method to $q service.

The current implementation of $q doesn't support the always() method. This is a very useful method since it can avoid creating duplicate code when you do not care about the outcome of a promise. Here's some sample code:
// Cover the app with an overlay to disable user input. We
// want to remove it whether the initialization was successful
// or not.
LoadingOverlay.start();
Auth.initialize().then(function() {
	LoadingOverlay.stop();
}, function() {
	LoadingOverlay.stop(); // duplicate code!!
});

With an always method it could be simplified to just this:
LoadingOverlay.start();
Auth.initialize().always(function() {
	LoadingOverlay.stop();
});

The proposed implementation is to add an always() method to the promise object. This method simply re-uses the existing then() method, which means it won't bloat the $q implementation.
If there's any interest in this implementation, I'd be glad to add the tests for it.

"let's go with always. it reads better and is compatible with all browsers."
I can only find a reference to .finally in the docs, what happened?


Adjusted the alignment

Kudos!!
Don't forget to star the repo it will help to encourage other contributors as well.


Add new menu type field matrix

Proposed Changes
Create a new field type for 5x5 LED matrix displays.

Reason for Changes
For interacting with hardware devices that have programmable LED matrix displays (e.g. micro:bit).
Test Coverage
Built and run on latest develop branch using the micro:bit extension. An example block is included in vertical_playground.html

Thanks to @rachel-fenichel the colour scheme issue is fixed! The PR can now be reviewed.


feat: PURIS Kit Preview Refresh

Description

The PURIS team wants to update the content of their current preview Kit in anticipation of a 24.05 release.
The goal of this Pull Request is to:

Update content of the Kit
Fix broken linking on "Upcoming Kits" page for the resiliency domain page to the PURIS Kit page
Introduce current folder structure proposed by the wiki/tutorials

Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[ ] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[ ] Copyright and license header are present on all affected files

LGTM


Breadth-first behavior

How does this behave in a breadth-first scenario? Does it act like a depth-first pool? Does one VM start for each new connection until they are all started?

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

ID: 0b747100-a26b-56fb-54b2-4d2e39e19496
Version Independent ID: e91c7099-940f-7463-1a5e-58753afe456e
Content: Windows Virtual Desktop Start VM Connect FAQ - Azure
Content Source: articles/virtual-desktop/start-virtual-machine-connect-faq.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@mwsutherland We are checking this and will get back to you.

I am reaching out to the Product team to confirm on this.
In future, you can also connect with the Product team on TechCommunity for Windows Virtual Desktop.
Existing thread on this topic: https://techcommunity.microsoft.com/t5/windows-virtual-desktop/start-vm-on-connect-starts-public-preview/m-p/2247357/thread-id/6804

We will now close this issue. Please share the details when you get a chance and tag me in a comment. I will reopen it and we will gladly continue the discussion.


Maven Dependency

Could you please make A Maven Depedency & Repository for this!

yea the one in the readme doesn't work
> Could not resolve all files for configuration ':app:compileClasspath'.
   > Could not find dev.jaqobb:namemcapi:2.0.7.
     Searched in the following locations:
       - https://jcenter.bintray.com/dev/jaqobb/namemcapi/2.0.7/namemcapi-2.0.7.pom
       - https://repo.maven.apache.org/maven2/dev/jaqobb/namemcapi/2.0.7/namemcapi-2.0.7.
pom

did it get taken down or something? sorry i'm kinda new to gradle/maven setup stuff

yea the one in the readme doesn't work
> Could not resolve all files for configuration ':app:compileClasspath'.
   > Could not find dev.jaqobb:namemcapi:2.0.7.
     Searched in the following locations:
       - https://jcenter.bintray.com/dev/jaqobb/namemcapi/2.0.7/namemcapi-2.0.7.pom
       - https://repo.maven.apache.org/maven2/dev/jaqobb/namemcapi/2.0.7/namemcapi-2.0.7.
pom

did it get taken down or something? sorry i'm kinda new to gradle/maven setup stuff

Hey! IIt wasn't taken down per se but JCenter repository got closed a while back making it impossible to use the dependency. I no longer support this API so if you wish to use it, you would have to clone the repository and install the library to your local repository yourself. Running ./gradlew clean build shadowJar publishMavenPublicationToMavenLocal should do the job.

Java 11 with Gradle 5.6.2, though the Gradle part should not really matter as there is a bundled one inside.

I will be closing this issue. I have revamped the project and although the feature set is still the same given the small amount of exposed endpoints, the way the library is used was updated and streamlined for future potential updates.
I have also set up a personal repository and the newest version of Java wrapper for NameMC is included there, more info in the new and refreshed README.


[SPARK-42268][CONNECT][PYTHON] Add UserDefinedType in protos

What changes were proposed in this pull request?
Add UserDefinedType in protos, after this PR, df.schema will support UDT
note: UDT is still not supported in df.collect and session.createDataFrame, it needs changes in ArrowConverters
Why are the changes needed?
for parity
Does this PR introduce any user-facing change?
yes
How was this patch tested?
added tests

Merged to master and branch-3.4.


Figure out cross compiling aarch64-apple-darwin on GitHub actions

What new feature do you think would be cool to add to artemis?
Cross compiling using Rust is difficult. Trying to accomplish it on GitHub actions is even more difficult.
Currently aarch64-apple-darwin (ARM) builds on GitHub actions are failing. I am not 100% sure why, but it might be related to cross compiling Deno.
Artemis compiles natively on macOS ARM fine.
Describe the solution you'd like
Figure out how to get cross compiling working on GitHub actions
Additional context

This might be fixed now, since the deno_runtime dependency was removed


Add support for objects.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 97.33%. Comparing base (012044d) to head (928c284).

Additional details and impacted files
@@             Coverage Diff              @@
##               main      #71      +/-   ##
============================================
- Coverage     99.09%   97.33%   -1.77%
- Complexity       96       99       +3
============================================
  Files            11       11
  Lines           222      225       +3
============================================
- Hits            220      219       -1
- Misses            2        6       +4

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


Update coverage for nativelink-error

Coverage for nativelink-error has been updated.
Description
Coverage for nativelink-error has been updated,
Both bazel and cargo tests have passed.
Create new test file
Fixes #1401
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

How Has This Been Tested?
Bazel test, Cargo test, pre-commit
Checklist

[x] Updated documentation if needed
[x] Tests added/amended
[x] bazel test //...  passes locally

This change is

Hello
Please check my PR.
I know your reviews are always the best. That's why your reviews are precious to me.
@aaronmondal @MarcusSorealheis


bugfix: support copy dest with file name

Describe what this PR does / why we need it
Does this pull request fix one issue?

Describe how you did it
1, support copy dest with file name
2.not panic if decode line failed
Describe how to verify it
FROM kubernetes:v1.19.8
COPY cont/* contp
COPY a.txt pp/a.txt
COPY a.txt a.txt
COPY a/b.txt  etc/b.txt
COPY ptest .
COPY dashboard.yaml manifests
CMD kubectl apply -f manifests/dashboard.yaml

Special notes for reviews


Failed to destroy session when having multiple logout ( or login )

#14624
What steps will reproduce the problem?
Step to reproduce :
1 - add sleep(7) in before logout
2- login
3- duplicate tab ( open two tabs )
4- click logout in the first then logout in the second tab
What is the expected result?
What do you get instead?
session_regenerate_id(): Session object destruction failed. ID: files
Same as related issue
Additional info

Q
A

Yii version
2.0.x

PHP version
7.0.0

Operating system
Win 10

@mmezzawi having two separate IDs in cookies in this case is expected:

Login happened. First cookie was set.
Another login happened. ID was re-generated. Second cookie was set.

@samdark ,
Your are right but in the given scenario when both of the request are sent together, the second one response contain the multiple session id cookie.
Shouldn't the session id cookie be overridden by the second request ?
Thanks.

Another Scenario :
1- open two tabs
2- login in the first ,page will be redirected to profile page for example where user can logout
3- now click on login in the second and logout in the first
Result :
PHP Warning – yii\base\ErrorException
session_regenerate_id(): Session object destruction failed. ID: files

Yes. These are concurrency issues. We could handle it better.

@samdark look at the below code:
public function switchIdentity($identity, $duration = 0)
    {
        $this->setIdentity($identity);

        if (!$this->enableSession) {
            return;
        }

        /* Ensure any existing identity cookies are removed. */
        if ($this->enableAutoLogin) {
            $this->removeIdentityCookie();
        }

        $session = Yii::$app->getSession();
        if (!YII_ENV_TEST) {
            $session->regenerateID(true);
        }
        $session->remove($this->idParam);
        $session->remove($this->authTimeoutParam);

        if ($identity) {
            $session->set($this->idParam, $identity->getId());
            if ($this->authTimeout !== null) {
                $session->set($this->authTimeoutParam, time() + $this->authTimeout);
            }
            if ($this->absoluteAuthTimeout !== null) {
                $session->set($this->absoluteAuthTimeoutParam, time() + $this->absoluteAuthTimeout);
            }
            if ($duration > 0 && $this->enableAutoLogin) {
                $this->sendIdentityCookie($identity, $duration);
            }
        }
    }

can we cancel calling session's regenerateID when $identity is null?


Gearposition build error

Fix build error in VisClient.cpp

There is a misprint in the commit message - "buimd".
Also, I would suggest using '.' at the end of each line.
I have no comments regarding the functional part of commit - it needs review from @arminn.

There is a misprint in the commit message - "buimd". Also, I would suggest using '.' at the end of each line.
I have no comments regarding the functional part of commit - it needs review from @arminn.

resolved


Feature/android round icons

Fixes android round icon generation issue. https://github.com/martiliones/icon-set-creator/issues/7
I didn't implement AndroidManifes.xml file replacing functionality since it uses default names for icons (ic_launcher, ic_launcher_round) that's why I think no need to replace them.

Thanks for spending your time to contribute in this project!
Unfortunately, I can't merge your PR for several reasons:

Your code doesn't match the ESlint rules. You may have forgotten to disable the code formatter in your IDE.
I don't think removing the icon name choice is a good idea. The user may want to have multiple icons
The round icon should have circle shape to avoid this

Square icon
Circle icon

The project was recently rewritten in TypeScript.

Thanks again for the contributing!


Changed immutable/deepEqual to use ===

Fixes #3357.
Not the first time ignoring an eslint error created a bug. 🤦♂

Codecov Report

Merging #3479 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #3479   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          66      66
  Lines        1504    1504
======================================
  Hits         1504    1504

Impacted Files
Coverage Δ

src/structure/immutable/deepEqual.js
100% <100%> (ø)
:arrow_up:

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 a9f28ad...9ba0ed9. Read the comment docs.

Published in v7.1.0.


Add monospace toggle button to textarea

Add new button to textarea to switch font. State is persisted in localStorage.
Change markdown-switch-easymde button from <span> to <button>
Slightly increased monospace font globally by 5% as I think it fits better.

For hover effect on these buttons I'm deferring to https://github.com/go-gitea/gitea/pull/23896.

I guess I would prefer if we could use the server-side user settings storage for settings like these instead of volatile localStorage. Is there API available? If not, I guess we defer to migrating these localStorage settings there later.

I guess I would prefer if we could use the server-side user settings storage for settings like these instead of potentially volatile localStorage. Is there API available? If not, I guess we defer to migrating these localStorage settings there later.

There is https://github.com/go-gitea/gitea/blob/main/models/user/setting.go, but you would have to wire it up to that still.

I guess I would prefer if we could use the server-side user settings storage for settings like these instead of potentially volatile localStorage. Is there API available? If not, I guess we defer to migrating these localStorage settings there later.

~There is https://github.com/go-gitea/gitea/blob/main/models/user/setting.go, but you would have to wire it up to that still.~ I misread, you were asking about the Gitea API I think, in which case I don't believe there's an API for the K/V table afaik.

Should be an API to store per-user settings as K/V with value being arbitrary JSON. I guess I will defer that effort to later, but I do plan opening an issue describing what I want.

By the way, what's the benefit of adding this setting?
Why would you need to choose between mono-space fonts and non-mono-space fonts?

Monospace is nice when you write code and want to align the indendation properly. Some people even prefer monospace all the time. GitHub also has a setting for it at the bottom of https://github.com/settings/appearance.

Blocked by #23896.

https://github.com/go-gitea/gitea/pull/23896 was merged

.


[MSP430] User defined interrupt handlers should have correct CC.

Thanks @pftbest.
@homunkulus r+

:pushpin: Commit 7e34184 has been approved by japaric

:hourglass: Testing commit 7e34184 with merge 7e34184...

:broken_heart: Test failed - status-travis

Failure due to time limit but all tests passed.


destroy session on regenerate session when session is active

There is a use case when session already started before, and already set some value, eg: on csrf session data on a login form. When authenticate, it call the session regenerate, which session id changed, but left the old session not persisted (unset not applied as session id changed), so old session with the value remain in the disk.
To avoid it, I think we can apply session_destroy() before session_write_close() whenever session is active.

@michalbundyra I've added unit test for test old session destroyed first on regenerate session id on persist session.

hm..., the test is working locally, while in travis, it still failure, I even use @runInSeparateProcess

@michalbundyra travis green now with use custom session path in unit test, please check it.

This repository has been closed and moved to mezzio/mezzio-session-ext; a new issue has been opened at https://github.com/mezzio/mezzio-session-ext/issues/1.

This repository has been moved to mezzio/mezzio-session-ext. If you feel that this patch is still relevant, please re-open against that repository, and reference this issue. To re-open, we suggest the following workflow:

Squash all commits in your branch (git rebase -i origin/{branch})
Make a note of all changed files (`git diff --name-only origin/{branch}...HEAD
Run the laminas/laminas-migration tool on the code.
Clone mezzio/mezzio-session-ext to another directory.
Copy the files from the second bullet point to the clone of mezzio/mezzio-session-ext.
In your clone of mezzio/mezzio-session-ext, commit the files, push to your fork, and open the new PR.
We will be providing tooling via laminas/laminas-migration soon to help  automate the process.


Bug 333113:Failed to start DTAAgentExecutionService on Azure VM

Username checking should be only usename ( not domain) for azure machines.
Testing: Tested for azure and domain joined machines

update the version of the task

signed off


[Mobile] Attribute.justifyAlignment and Attribute.leftAlignment have problems in display

hello，I found that Attribute.justifyAlignment and Attribute.leftAlignment have problems in display，as this picture shows
https://i.loli.net/2021/08/04/B5jAJFDd8nkeslU.jpg

https://github.com/flutter/flutter/issues/35734


Add .area.geojson() method

This will be required for farmOS/farmOS-client#353. I considered just doing this manually from within Field Kit, but talking with @paul121 I realized it's still complicated enough—handing the OAuth tokens, adding them to the headers, refreshing them if necessary, error handling, etc—that it's just better to build it into farmOS.js.
Some consideration to the API: it'd be nice to accept parameters to only fetch an area type, such as fields, beds, etc. That'd be simple enough by appending it to the endpoint, but I don't need it for my immediate use case. I need all the areas, which is what you get when you append nothing to the main endpoint, so I'm not going to deal with any parameters now. Just do farm.area.geojson(), that's it. That should make it possible to add an options parameter in the future.

Resolved by #14.


Copy src to working directory on install

Add src to files array so that it's copied to the working directory before the postinstall transpile command runs.
I'm not sure it this is the best solution (obviously would probably be better to do this pre-publish and host the result on npm) - but until there's a better solution, I think this Closes #2 :smile:

Unfortunately, after fixing this issue, I'm still getting:
/home/jmarty/Projects/satorix-dashboard/node_modules/chai-webdriverio/build/index.js:3
import visible from './assertions/visible';
^^^^^^
SyntaxError: Unexpected token import

So maybe there's more that is required regarding this change (I'm new to Node so I'm not sure how to solve this)

master now transpiles properly @mltsy, so I think this PR might be obsolete.
You're right that it's best practice to host the transpiled source on NPM instead. Maybe it's worth raising a new PR to do that.

Yup!  I agree.  This was just necessary because of the way npm handles git hosted packages, soI'll close this.  Awesome!  I'm just about to try the npm-hosted package this morning :)


Fix shader incorrectly expects int on uint and vice-versa in cases

Closes https://github.com/godotengine/godot/issues/95453

This code will now compile correctly:
shader_type spatial;

const int iOne = 1;
const uint uOne = 1u;

void fragment() {

	int i; uint u;
	switch (i) {
		case iOne: break;
	}
	switch (u) {
		case uOne: break;
	}
}

Also, I've placed the case label duplication check code into case processing branch, the reason for that is that it will print an error at the case label itself:

Details

rather than

Details

Besides that, I've fixed a shader compiler failure when declaring a switch like this:
switch(1u) {
	default:
	break;

	case 1u:
	break;

	default:
	break;
}

Thanks!


Update CapacitorNativeSettings.podspec

Still getting the following errors when using this dependency with Capacitor 4 -- shouldn't the podspec also be bumped to target 13?
Thrown during build:
NativeSettingsPlugin.swift:2:8: compiling for iOS 12.0, but module 'Capacitor' has a minimum deployment target of iOS 13.0: /Users/ionic-cloud-team/Library/Developer/Xcode/DerivedData/App-bcnhnmaahexbnydurxfgfrwwvhxn/Build/Intermediates.noindex/ArchiveIntermediates/App/BuildProductsPath/Release-iphoneos/Capacitor/Capacitor.framework/Modules/Capacitor.swiftmodule/arm64-apple-ios.swiftmodule

Hi. It seems for me Xcode sets it to min deployment target 13 by default. So I don't get this error at all.
But we should probably bump this to 13. Thank you for your contribution!


added TSPOT travel site

Closes:  #755

Title :  TSPOT Travel App
Name: : Maheshwari Love
Idenitfy yourself: : GSSOC

Describe the add-ons or changes you've made 📃
Added new project
How Has This Been Tested? ⚙

Locally
Screenshots 📷

Type of change ☑

What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist: ☑

[x] My code follows the Contributing Guidelines & Code of Conduct of this project.
[x] This PR does not contain plagiarized content.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] My changes generate no new warnings.

Note to reviewers 📄

@Avdhesh-Varshney please review this PR


Is it possible to enlarge the preview panel?

I am using a large display and the text is too small to read. When I increase the font size, only the actual file font size changes. Is there a way to increase the font size on the preview panel? Thanks.
Ubuntu 16, Sublime 3

You can add some custom CSS. In the control panel, search up MarkdownLivePreview: Edit custom css file and paste this in:
body {
	font-size: 20px;
}

Adjust the 20px to what seems right to you.


Throwing 503 error while pushing the changes to github

Describe the bug
Whenever I try to push the changes done in my project in utopia app it is throwing 503 error for me.
To Reproduce

While pulling the changes from github it is working fine.
If I make any changes and while pushing and commiting those changes to the github connected project, it is throwing 503 error.

Expected behaviour
I should able to push those changes without 503 or any issue.
Screenshots

To be clear, if you wait a while, can you then later commit and push those changes back to github? Or does the pushing part never work for you?

Yes it is working sometimes, but pushing and commiting of 5 min work sometimes it take me whole day / half day to make those changes live. Due to the repeating 503 error.


DHCP (IPv4) seemingly dies by trying to assign an IP of <IP_ADDRESS>

Describe the bug
This strange issue leads to an ethernet device on a network being completely dead until it is restarted. A device gets a fixed IP from a DHCP server for 20 seconds, the server is changed to give a different fixed IP and the zephyr board renews the IP. Seemingly at this time, the DHCP client seems to think it has been assigned the IP <IP_ADDRESS> for whatever reason, this IP clearly is not valid, and the DHCP client fails to remove/add it, it then stays in this state of constantly trying to add the invalid IP. Rebooting the module allows it to get a DHCP lease.
To Reproduce
Needs a DHCP server - I used dhcpd, with this configuration:
default-lease-time 20;
max-lease-time 20;

authoritative;
server-name name;

host zephyr {
  hardware ethernet 68:27:19:CF:09:DD;
  fixed-address <IP_ADDRESS>;
}

subnet <IP_ADDRESS> netmask <IP_ADDRESS> {
  range <IP_ADDRESS> <IP_ADDRESS>;
}

Then just run the server, load the zephyr DHCP sample on a board and let it get an IP. Once it gets an IP, change the fixed address of the zephyr device to something else, e.g. .210, restart the dhcpd server, then watch as the DHCP client falls over.
Expected behavior
DHCP to continue working
Impact
Showstopper, device is dead, complexity to denial of service a device is 0
Logs and console output
Log: https://pastebin.com/WeHvD1pN
Environment (please complete the following information):

OS: Linux
Toolchain: Zephyr SDK 0.15.0
Commit SHA or Version used:<PHONE_NUMBER>c0c5e7039d80df5f0d463075a0a31a

Issue likely caused due to a number of factors, but essentially the code copies the new IP from the server over to a local variable, it then tries to remove and add this IP from an interface, it can only remove it if it was the previous IP (which is not always going to be the case) so this remove process is likely to fail, then due to the default maximum number of IPs being 1, it cannot add the new IP.


cannot unmarshal !!str FOO ---... into chartify.res]

I had a bug report here https://github.com/roboll/helmfile/issues/2086, but I think the problem is from our library
https://github.com/variantdev/chartify/blob/0b1378d379b91a5a1f60132ad80ff8dd3f91f447/patch.go#L210
Description
When transformers is used, and the helm value is cert-folded, as below
  FOO: |
    -----BEGIN CERTIFICATE-----
    FOO
    -----END CERTIFICATE-----

helmfile will raise an exception
err: [processing all.patched.yaml: parsing yaml doc from "    FOO\n    -----END CERTIFICATE--": yaml: unmarshal errors:
  line 1: cannot unmarshal !!str `FOO ---...` into chartify.res]
in ./helmfile.yaml: [processing all.patched.yaml: parsing yaml doc from "    FOO\n    -----END CERTIFICATE--": yaml: unmarshal errors:
  line 1: cannot unmarshal !!str `FOO ---...` into chartify.res]

Test code
$ git clone https://github.com/icy/helmfile-bug.git
$ cd helmfile-bug/one
$  helmfile  --version
helmfile version v0.143.0
$ helmfile template

Logs
The output of helmfile --debug template command is found here https://github.com/icy/helmfile-bug/blob/main/one/debug.log.txt
Generating /tmp/chartify3660731556/test/all.patched.yaml
running kustomize build /tmp/chartify3660731556/test --output /tmp/chartify3660731556/test/all.patched.yaml
Removed /tmp/helmfile1974484501/test-values-6c8cc986b7
err: [processing all.patched.yaml: parsing yaml doc from "    FOO\n    -----END CERTIFICATE--": yaml: unmarshal errors:
  line 1: cannot unmarshal !!str `FOO ---...` into chartify.res]
in ./helmfile.yaml: [processing all.patched.yaml: parsing yaml doc from "    FOO\n    -----END CERTIFICATE--": yaml: unmarshal errors:
  line 1: cannot unmarshal !!str `FOO ---...` into chartify.res]

The command kustomize runs well, but its output was trapping the next step processing all.patched.yaml

The bug may be coming from this https://github.com/variantdev/chartify/blob/0b1378d379b91a5a1f60132ad80ff8dd3f91f447/patch.go#L195

https://github.com/variantdev/chartify/blob/0b1378d379b91a5a1f60132ad80ff8dd3f91f447/patch.go#L195

I'd suggest the yaml document separator does match this regex ^---$, but in tersm of byte sequence I don't know how to give it a test. I've updated our test to reflect this case https://github.com/variantdev/chartify/pull/19 . Will continue tomorrow. It's late now :).

Okay I hope this works https://github.com/variantdev/chartify/pull/19/files.
@mumoshu  Can you please have a look?  Please let me know if there is anything I can help. Thanks


How to define custom map groups?

On old CS:GO it was possible to set GameMode_server.txt to define maxplayers and custom map groups. I am currently missing this inside the container. Is there anything new in this section? How can i achieve a custom mapgroup and where should I store this config?

i want to know too!

This is possible. I just tested it.
I'll write up some doc shortly.

gamemodes_server.txt
Here's an example map group config. I've updated https://github.com/joedwards32/CS2/raw/main/examples/cs2.cfg.tgz to include an example of this in action, for use with CS2_CFG_URL.
If you are using a persistent volume for the CS2 docker image, you can drop the file in /var/lib/docker/volumes/examples_cs2/_data/game/csgo/gamemodes_server.txt.
Once the file is in place, you can set CS2_MAPGROUP="mg_tournament"

Would this work for workshop maps mixed with official maps?
e.g.
host_workshop_map<PHONE_NUMBER> #  Agency (cs_agency)
map cs_office

For a dedicated server I look after, we only play workshop maps, and use the "workshop collection" method. In CS:GO they used to provide the "current" (and old) version of maps on the workshop as well, so I just included the official maps in the collection and we could have a mix...
If no one else responds, I'm sure I'll get a chance to test this myself at some point in the near future (and will report back )

I don't have much experience with workshop maps. If you figure this out @carsonl please let us know :)

Would this work for workshop maps mixed with official maps? e.g.
host_workshop_map<PHONE_NUMBER> #  Agency (cs_agency)
map cs_office

For a dedicated server I look after, we only play workshop maps, and use the "workshop collection" method. In CS:GO they used to provide the "current" (and old) version of maps on the workshop as well, so I just included the official maps in the collection and we could have a mix...
If no one else responds, I'm sure I'll get a chance to test this myself at some point in the near future (and will report back )

Please tag me if u find a solution! i want this too!

Yeah, I had a bit of a google to see if others are doing it, and then some naive entries in gamemodes_server.txt like the following, none of which worked: (I did test them one at a time)
                "3070584943" "1"
                "workshop/3070584943/cs_agency" "1"
                "cs_agency" "1"

I'll keep my eyes and ears open for any blogs/announcements


Update sample app deployments

Closes #8

Maybe update Grafana dashboards because of new Grafana version.

Update version of Helm Chart nginx-stable/nginx-ingress.


Add to cart notification is in the wrong language

Current behavior

When you add an product in the german store to the cart it shows an english message in the notification.

Expected behavior

Show german text in the notification.
Steps to reproduce the issue

got to here https://next.storefrontcloud.io/de/men/tops-men/tees-men/tees-16/balboa-persistence-tee-531.html?childSku=MS03-XS-Gray
Add the product to cart
See english message in the top right corner

Repository

Can you handle fixing this bug by yourself?

[ ] YES
[x] NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

[ ] This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[x] This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[ ] This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Environment details

Browser: Chrome 77.*
OS:
Node:
Code Version: 1.11 Release branch

Additional information

When you look into the core/modules/cart/helpers/notifications.ts file here the notifications are created and at the point of creation the language is english so the notification is english and not german.

It looks like it is not just a thing of notifications but maybe something more general? It looks like in some cases that $t() is not working as expected.
Attached image shows wrong translations for prices (bottom) account/cart stuff (top right).
The translations for top left are normally covered by this code:
  <button type="button" class="bg-cl-transparent header-btn brdr-none pl5" @click="logout" v-if="isUserAuthenticated">
    {{ $t('Logout') }}
  </button>
  <button type="button" class="bg-cl-transparent header-btn brdr-none pl5" @click="handleLogin" v-else>
    {{ $t('Login') }}
  </button>

For the topmost occurence (the cookie disclaimer within the grey box atop) we use this component code:

      {{ $t('We use cookies to give you the best shopping experience.') }}
        {{ $t('See details') }}
        OK

        X

</transition>

@andrzejewsky

@nhp Which version do you use? This can occur in version 1.10.3 if in particular storeView config there is disabled flag set on true.

@gibkigonzo He is part of the project so same version as the issue has in the description.


create_list with Traits

Tag.countable should not be deleted
Failure/Error: FactoryGirl.create_list(:tag, 3, :deleted, :inventory => onsite_inv)
ArgumentError:
wrong number of arguments (4 for 3)
./spec/models/tags_spec.rb:30:in `create_list'
./spec/models/tags_spec.rb:30

You know what I mean.

This was fixed in #291 and it will be available in the next release.
For now use
tags = 3.times.map { FactoryGirl.create(:tag, :deleted, :inventory => onsite_inv) }

Thanks, that's great!
On Sat, Feb 11, 2012 at 6:39 AM, Joshua Clayton <
<EMAIL_ADDRESS>
wrote:

@lewisou I just cut version 2.5.2 of the factory girl gem, which includes
this feature; thanks for your patience while we got a release out!

Reply to this email directly or view it on GitHub:
https://github.com/thoughtbot/factory_girl/issues/294#issuecomment-3915696


Rewrite parser/linter in JavaScript

This is a huge job, but I wanted to suggest it

Antlr can generate javascript parser code from an antlr grammar.
CFLint is built over
https://github.com/cfparser/cfparser/tree/master/cfml.parsing/src/main/antlr4/cfml.
I'm not planning on touching that one though :-)

@ryaneberly haha, I don't want to know how much time you put into rewriting the parser. Better man than I. That's for sure.

:)

@ryaneberly Cool! Thanks for that. The only reason behind this is that launching Java from Atom is slow and cumbersome. But, at the same time, Java makes a lot more sense for linting during things like a Gradle build. I'll have to really think about this.

Maybe the solution is less a JavaScript implementation and more finding a way to 'build' the JAR into an executable... just thinking out loud

It is slow every time, or just the first time you call from it from Atom?
You could have the java process startup once and keep listening for future requests.  And maybe auto-terminate after a period of time if no new lint requests arrive.
Then your integration package could be pure javascript, and make the request and process the response through some form of interprocess communication.  (named pipes, a local port, etc).
This is naturally a bit complex, but far simpler than re-writing the entire linter in a different language.  and you would eliminate the cost of the JVM startup.

CFLint is far too big and useful to recreate. This was sort of a pipe dream early on before I really dove in. Java as the language of choice makes sense when using Maven and Gradle, and I don't want to fork this. Instead I'll focus on performance improvements with the Java version.


AMPI support for non-commutative reduction operations

Original issue: https://charm.cs.illinois.edu/redmine/issues/1185

AMPI currently aborts if a user tries to create an Op that is non-commutative, and it doesn't keep track of the commutativity of Op's.
We should support non-commutative reduction operation functionality even though it is not recommended for performance.
Non-commutative operations can be implemented like a Gather operation where at the root we call MPI_Reduce_local over the resulting contributions in rank order rather than just sorting them by rank order.

Original date: 2016-08-28 15:01:01

For now we will assume all user-defined MPI_Ops are non-commutative, and we'll implement them like a gather where at the root instead of sorting contributions by rank order we apply the Op in rank order. Of course this will use extra memory at the root and it means that commutative user-defined operations will pay the cost of non-commutative ones.

Original date: 2016-08-28 19:39:55

Support non-commutative reduction op's and assume all user-defined op's are non-commutative: ~~https://charm.cs.illinois.edu/gerrit/#/c/1815/~~ https://github.com/UIUC-PPL/charm/commit/01139d7622ce9acd409a733fe5941fe1e006d9f5


most downloads time out

butler: v0.15.3, built on Jul 26 2016 @ 21:37:32
os x version: 10.12 beta 16A270f
Sometimes they complete but mostly they timeout before completion
$ butler -j dl URL
{"level":"debug","message":"HTTP 200 OK (no byte range support)","type":"log"}
{"level":"info","message":"Downloading 74 MB from UploadServer at commondatastorage.googleapis.com","type":"log"}
{"percentage":0.042417740181358285,"type":"progress"}
{"percentage":0.06453582220075213,"type":"progress"}
{"percentage":0.08665390422014599,"type":"progress"}
{"percentage":0.10875578647243578,"type":"progress"}
{"percentage":0.1308738684918296,"type":"progress"}
{"percentage":0.1529919505112235,"type":"progress"}
{"percentage":0.17511003253061733,"type":"progress"}
{"percentage":0.19722811455001119,"type":"progress"}
{"percentage":0.21934619656940502,"type":"progress"}
{"percentage":0.24146427858879888,"type":"progress"}
{"percentage":0.26358236060819273,"type":"progress"}
{"percentage":0.28570044262758654,"type":"progress"}
{"percentage":0.3078185246469804,"type":"progress"}
{"percentage":0.32993660666637425,"type":"progress"}
{"percentage":0.3520546886857681,"type":"progress"}
{"percentage":0.37417277070516197,"type":"progress"}
{"percentage":0.39629085272455583,"type":"progress"}
{"percentage":0.4184089347439497,"type":"progress"}
{"percentage":0.4405270167633435,"type":"progress"}
{"percentage":0.46264509878273735,"type":"progress"}
{"percentage":0.4847631808021312,"type":"progress"}
{"percentage":0.506881262821525,"type":"progress"}
{"percentage":0.5289993448409189,"type":"progress"}
{"percentage":0.5511174268603127,"type":"progress"}
{"percentage":0.5732355088797065,"type":"progress"}
{"percentage":0.5953535908991004,"type":"progress"}
{"percentage":0.6174716729184943,"type":"progress"}
{"percentage":0.6395897549378882,"type":"progress"}
{"percentage":0.661707836957282,"type":"progress"}
{"percentage":0.6838259189766758,"type":"progress"}
{"percentage":0.7059440009960697,"type":"progress"}
{"percentage":0.7280620830154635,"type":"progress"}
{"percentage":0.7501801650348573,"type":"progress"}
{"percentage":0.7722982470542512,"type":"progress"}
{"percentage":0.7944163290736451,"type":"progress"}
{"percentage":0.8165344110930389,"type":"progress"}
{"message":"read tcp <IP_ADDRESS>:58959-\u003e<IP_ADDRESS>:443: i/o timeout","type":"error"}

Well that doesn't sound good at all. Does it time out after a fixed length every time? might be Sierra behavior tripping up idletiming

I probably won't have time to take a serious look at this until tomorrow, if someone wants to help: looking for reports of this same message on macOS sierra for golang programs would be helpful. If it's not just us, there's bound to be some github threads about this already.

macOS Sierra is beta software. Please use go 1.7rc5 or later until the fix is backported to previous releases.

As soon as the first stable 1.7 golang is released, I'll upgrade our build servers and release a new butler binary that uses it. Thanks for the info @davecheney!

@michaelglass butler 0.16.0 is out and built with golang 1.7, please report back on success/failure :)

fixed! thanks!


Edge - Zoom

After zooming in/out, can't get to JavaScript.  Repro: Click zoom in/out button on toolbar, click JavaScript toggle.

Unable to go to typescript. Blocking bug in beta

Screencast?

Is this a zooming issue? I've fixed the bug to return to javascript.

It is the same issue. not a zooming issue.


Modal backdrop not showing when multiple modals are opened

I have modal in which you can open new modal on top of the existing one. The problem is when I open new modal, the backdrop does not switch in front of the first modal.
It should be like this:
-------------------------------------->
| View | Modal 1 | Backdrop | Modal 2 |
Instead it's like this:
-------------------------------------->
| View | Backdrop | Modal 1 | Modal 2 |

@SMarijic, I answered your post on StackOverflow where this type of question is better suited.  Please do not use the issues forum for support requests as it is reserved for bugs.  In the future, please follow the instructions here.
Finally, when asking for help, and this applies to both your SO post and this one, it is nearly always impossible to debug something without any code.  Please be respectful of both our time and the SO community by putting forth an effort to show that you you have attempted to both debug the problem on your own and to give us the information needed to assist you.


Publish first version of the crate

The next step for this library is to make it more generally available for people to try. In order to do this, the crate needs to be published properly.
Currently, the bevy_imgui crate name is reserved (see https://github.com/bevyengine/bevy-crate-reservations). Enquire about assuming ownership of this crate name...

I hope this repo publish to crate soon.

Me too! The main blocker on this currently is that the 'bevy_imgui' crate name is reserved by the Bevy project.
I did open up an issue to enquire about taking ownership of this crate name but I haven't had a reply yet... I'll chase it up
https://github.com/bevyengine/bevy-crate-reservations/issues/27

Some discussion with the Bevy team can be found here: https://github.com/bevyengine/bevy/discussions/9639.
Having read through the discussion on the Discord channel, and this discussion, the next step forward I think would be to rename this crate to bevy_mod_imgui and publish it under this new name

Version 0.1.0 of the crate has now been published!
https://crates.io/crates/bevy_mod_imgui


Virus detected

https://www.virustotal.com/gui/file/bd6aec747e686043c90209839cb82ae73de8ed2a3bcdf864237011ce2047ca90/details

its still the same

It is discontinued


Harvest PDFs as well

PDF is the worst kind of open data - 1-star open data.
Still, have the ability to optionally harvest PDFs.

That's not something that we'll be adding to our deployed version, but I can see how that would be useful for folks. That can be done trivially, by modifying constants.py to add pdf to the list of filenames.
@knowtheory, is there any reason why this list of suffixes couldn't be moved to the config file? Would just up and adding pdf make problems, such as with the code that tries to get the title of the file?

Nope, listing PDFs should function fine.  The reason we'd left them out of the list by default is just that there are so many possible non-data pdfs up on sites (reports, forms, all manner of things) that it'd be a pretty noisy signal.
And as for the list of suffixes... you mean moving them into the settings.py?  Could move them in there too yep.

And as for the list of suffixes... you mean moving them into the settings.py?

Yeah, it seems like that'd be a good way to let people control the kinds of files that they want to look for.

I'd like to set up some way that PDF metadata (using XMP) could catalog embedded or linked data, with the possibility of using annotations, bookmarks, form-data, and attached files.  With an explicit manifest, you'll get less "noisy signal".


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 985 ms

Resolved: Bofrost.at performance has improved in f939a81.


Nick: Watch thepsychguide.org

Nick requests the watch of the watch_keyword thepsychguide\.org. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

thepsychguide\.org has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Robert Longson in Charcoal HQ


ZeroDivisionError when computing Krippendorff's alpha

(1) Steps to reproduce:
    from nltk.metrics.agreement import AnnotationTask
    atask = AnnotationTask(data=[('c1', '1', 1),('c2', '1', 1)])
    atask.alpha()

(2) Error:
    Traceback (most recent call last):
      File "<stdin>", line 1, in <module>
      File "/home/sidorenko/.local/lib/python2.7/site-packages/nltk/metrics/agreement.py", line 316, in alpha
        ret = 1.0 - (self.Do_alpha() / De)
    ZeroDivisionError: float division by zero

(3) Expected return value:
    1.

(4) System information:
    nltk.__version__: '3.0.5'
    python --version: Python 2.7.6
    uname -srm: Linux 3.19.0-42-generic x86_64

Python 3.5.3 (v3.5.3:1880cb95a742, Jan 16 2017, 16:02:32) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import nltk
>>> nltk.__version__
'3.2.4'
>>> from nltk.metrics.agreement import AnnotationTask
>>> atask = AnnotationTask(data=[('c1', '1', 1),('c2', '1', 1)])
>>> atask.alpha()

no problem here

Yep. Checked it on my computer---no error with NLTK 3.2.5. Has apparently been fixed in the previous versions.


Expose rule stats in QueryStats

Currently we gather JMX stats for rule execution. However, we could also expose rule stats for particular query in QueryStats. This would simplify query debugging

Hello, I would love to try on this work. Thanks!

I am concerned this could significantly increase size of QueryStats. There are about 100 rules today, but this number is going to increase.

@findepi How about showing, say, top 20 rule stats by default? And other rules can be chosen to expose if the user sets the rule name by session property explicitly?
Just make sure I understand the issue correctly: the rules we mentioned here refer to the optimization rules for logical plan right?

Maybe there should be config switch for that, where user might want to enable it when debugging a query.

@findepi How about showing, say, top 20 rule stats by default? And other rules can be chosen to expose if the user sets the rule name by session property explicitly?

That seems like a good idea. It will enable us to debug planning latency. We could also have a session property that would make query json contain stats for all rules.


[has-rock] Rock NFT voting strategy

Changes proposed in this pull request:

Strategy to calculate scores for rock NFT holders, number 0-99.

The rock NFT contract is not compatible with ERC721 or ERC1155 and needs a unique strategy.
https://etherscan.io/address/0x37504ae0282f5f334ed29b4548646f887977b7cc

Strategy is live:  https://snapshot.org/#/strategy/has-rock


Check expire date of existing certs

Thanks, I was just thinking about implementing this myself.
IMHO the time to renew before expiry should be a config option!

You are totally right. PR now includes a config option.

merged, thanks


Migration example #512

As suggested in #512, this adds an example of how to use the DoctrineMigrationsBundle to apply database migrations.

having a migration starting from an unknown state is a bad idea. This is not the proper usage of the migration library. The first migration should migrate from an empty database so that migration commands are working for everyone.
If you require developers to start by using doctrine:schema:create for the initial setup, migrations are unusable as the dev also need to mark all existing migrations as already migrated at this point (as doctrine:schema:create creates the current schema, not the schema at the time before migrations started to be used)

@stof we may add an example of a migration ... but we don't want to force a useless migration. So we said, imagine that we have a time machine and can go back to the moment before #457 was merged. What will be the migration created for that change?
The idea is to create the migration that we should have done ... but never did. The migration will be only an example to see it but not to execute it. Nobody will have to execute that to make the app runnable.

@stof I agree the migrations should go from empty database to current state. However, I don't see reason why they should not be already applied when a developer clones this repo. List of applied migrations is in the database, so it should not cause any problem since the database is distributed with the source code.

@stof I added the migration number to the migration_versions table in both sqlite databases so that the command php bin/console doctrine:migrations:status shows that the database is already at the latest version. Therefore the migration does not need to be applied.

ping @stof @javiereguiluz what about this PR ?

I'm actually -1 on this PR, because it shows an invalid usage of doctrine/migrations.
The content of app/DoctrineMigrations assumes that you will do the initial database creation with doctrine:schema:create (or doctrine:schema:update) and then use migrations to apply later changes.
But this works only if you run the schema command with a codebase before the introduction of migrations (otherwise, the DB already has the changes performed by the migration, but the migration is not known as being executed). This makes it impossible to build the DB from an empty database properly.
The right usage of doctrine/migrations is to write the first migration as a migration from the empty database to the needed one (and then never using doctrine:schema:create or doctrine:schema:update to apply changes to the DB).
So either the demo switched to migrations fully, or it does not show them. But showing them the wrong way is the worst option.

Agree with stof

I'll wait for a final word from @javiereguiluz and then I'll close the PR

@apetitpa I can't really add anything here because I don't have much experience with migrations. But if Christophe and Tobias agree that this is the wrong way to use/teach this feature, we can't merge this.
It's sad because you spent some time preparing this pull request, but this is something that sometimes happen when contributing to open source projects. I'm sorry.

@javiereguiluz it's ok don't worry, as you said it happens sometimes but it is part of the game and it's for the greater good. Thanks to @stof and @Tobion Symfony beginners won't be confused about migrations and I think this is the most important. I close the PR since it won't be merged. Thank you for your time everyone.


I probably should've asked this one from the beginning lol

What is your question?
How do I make my own Note textures and implement them like how week 6 does it?

put your notes image and xml file in mods/images, then go into the chart editor, and type the note image name in the thing, i guess

Put your note textures inside mods/images/pixelUI/
Go to your stage .json file and isPixelStage to true


broken link

In read page there is a broken link on the  logo TravelTales:) if we click on it it say 404 site not found

In read page there is a broken link on the logo TravelTales:) if we click on it it say 404 site not found

Assigned.


Error message in init.sh due to using == instead of = in an if

🐛 Bug description
Running the install (init.sh), it printed an error message ("sh: 139: [: x86_64: unexpected operator").  The error message is caused because == is used instead of = in the if on line 139 of init.sh.
🤔 Expected Behavior
No error message from the if comparison.
👟 Steps to reproduce
$ curl https://rustwasm.github.io/wasm-pack/installer/init.sh -sSf | sh
sh: 139: [: x86_64: unexpected operator
info: downloading wasm-pack
info: successfully installed wasm-pack to `/home/cds/.cargo/bin/wasm-pack`

Here's my fix:
diff --git a/docs/_installer/init.sh b/docs/_installer/init.sh
index 91ec0af..6fb08c0 100644
--- a/docs/_installer/init.sh
+++ b/docs/_installer/init.sh
@@ -136,7 +136,7 @@ get_architecture() {
     esac

     # See https://github.com/rustwasm/wasm-pack/pull/1088
-    if [ "$_cputype" == "aarch64" ] && [ "$_ostype" == "apple-darwin" ]; then
+    if [ "$_cputype" = "aarch64" ] && [ "$_ostype" = "apple-darwin" ]; then
         _cputype="x86_64"
     fi

🌍 Your environment
I'm running on Pop!_OS 20.04 LTS on an x86 laptop.  The bash version is "5.0.17(1)-release".
wasm-pack version: wasm-pack 0.11.0.  The error is present in master (48177dc0d) as well.
rustc version: rustc 1.68.1 (8460ca823 2023-03-20)

Since init.sh uses bashisms, the installation instructions should instead be updated to pipe the script to bash instead of sh, e.g.:
$ curl https://rustwasm.github.io/wasm-pack/installer/init.sh -sSf | bash

Alternatively init.sh could be made compatible with POSIX sh and the installation instructions could remain as is.

The existing version has "#!/bin/bash" but the double equals is the only bashism I saw, so I agree that switching the instructions to use bash in the pipe will work fine, but moving the shebang to /bin/sh and fixing the double equals seems like the best way to maintain maximum portability, I'd think.

local is not POSIX.


got stuck when trying to follow the vs code container tutorial

I got stuck when trying the tutorial.
[108 ms] Remote-Containers 0.241.3 in VS Code 1.69.2 (3b889b090b5ad5793f524b5d1d39fda662b96a2a).
[107 ms] Start: Resolving Remote
[120 ms] Start: Check Docker is running
[120 ms] Start: Run: docker version --format {{.Server.APIVersion}}
[479 ms] Server API version: 1.41
[481 ms] Start: Run: docker volume ls -q
[817 ms] Start: Run: docker volume create --label vsch.local.repository=https://github.com/Microsoft/vscode-remote-try-python --label vsch.local.repository.unique=true vscode-remote-try-python-41cc2ee6f8cb6b0cee4c350f9a78ef53
[1137 ms] Start: Run: docker build -f C:\Users\Admin\AppData\Local\Temp\vsch\bootstrap-image\0.241.3\bootstrap.Dockerfile -t vsc-volume-bootstrap C:\Users\Admin\AppData\Local\Temp\vsch\bootstrap-image\0.241.3

[+] Building 0.7s (5/8)
[+] Building 0.9s (5/8)
[+] Building 1.0s (5/8)
[+] Building 1.2s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 1.3s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 1.5s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 1.6s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 1.8s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 1.9s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 2.1s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 2.2s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 2.4s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 2.6s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 2.7s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 2.9s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 3.0s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 3.2s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 3.3s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
 => [internal] load metadata for mcr.microsoft.com/vscode/devcontainers/b  0.5s
[+] Building 3.5s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 3.6s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 3.8s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 3.9s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 4.1s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 4.2s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 4.4s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 4.5s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 4.7s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 4.9s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 5.0s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 5.2s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 5.3s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 5.5s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 5.6s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 5.8s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 5.9s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 6.1s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 6.3s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 6.4s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
[+] Building 6.5s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 6.7s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 6.9s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 7.0s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 7.2s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 7.3s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 7.5s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 7.6s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 7.8s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 7.9s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 8.1s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 8.2s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 8.4s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 8.6s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 8.7s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 8.9s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 9.0s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 9.2s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 9.3s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 9.5s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 9.6s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 9.8s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 10.0s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 10.1s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 10.3s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 10.4s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 10.6s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 10.7s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 10.9s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 11.0s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 11.2s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 11.3s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 11.5s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 11.7s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 11.8s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 12.0s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 12.1s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 12.3s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 12.4s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 12.6s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 12.7s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 12.9s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 13.1s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 13.2s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 13.4s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 13.5s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 13.7s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 13.8s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 14.0s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 14.1s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 14.3s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 14.5s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 14.6s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 14.8s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 14.9s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 15.1s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 15.2s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 15.4s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 15.5s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 15.7s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 15.9s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 16.0s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 16.2s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 16.3s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 16.5s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 16.6s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 16.8s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 16.9s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 17.1s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 17.3s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 17.4s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 17.6s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 17.7s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 17.9s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 18.0s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 18.2s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 18.3s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 18.5s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 18.7s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 18.8s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 19.0s (5/8)
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
 => [internal] load build definition from bootstrap.Dockerfile             0.0s
 => => transferring dockerfile: 42B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
[+] Building 19.1s (5/8)
 => => transferring dockerfile: 42B                                                              0.0s
 => [internal] load .dockerignore                                                                0.0s
 => => transferring context: 2B                                                                  0.0s
 => [internal] load metadata for mcr.microsoft.com/vscode/devcontainers/base:0-alpine-3.14       0.5s
[+] Building 820.4s (5/8)
 => => transferring dockerfile: 42B                                                              0.0s
 => [internal] load .dockerignore                                                                0.0s
 => => transferring context: 2B                                                                  0.0s
 => [internal] load metadata for mcr.microsoft.com/vscode/devcontainers/base:0-alpine-3.14       0.5s
 => CACHED [1/4] FROM mcr.microsoft.com/vscode/devcontainers/base:0-alpine-3.14@sha256:8cd94bb5  0.0s
 => [internal] load build context                                                                0.0s
 => => transferring context: 5.90kB                                                              0.0s
 => [2/4] RUN apk add --no-cache  nodejs  npm  make  g++  docker-cli  docker-compose  ;        819.8s

// Update 'VARIANT' to pick a Python version: 3, 3.9, 3.8, 3.7, 3.6.
// Append -bullseye or -buster to pin to an OS version.
// Use -bullseye variants on local on arm64/Apple Silicon.
"VARIANT": "3.9-bullseye",
"VARIANT": "3.10-bullseye",
// Options
"NODE_VERSION": "lts/*"
}
Start from the file where you stuck,then approach the python coding program and accelerate on the platform.if this doesn't work please get to the container.#52


Failure to login through oAuth with Azure Static Web Apps

What is your Test Scenario?
The big goal is to do End to End testing on our applications, including login. The Test Scenario is attempting to login on a 3rd party oAuth System (FusionAuth) which is being ran and through Azure Static Web Apps Custom Authentication.
What is the Current behavior?
I am redirected back to the home page not logged in and no session cookie or data is saved.
What is the Expected behavior?
After login, we are successfully redirect to the call back URL OR we are successfully logged in then I can code the redirect to the next page myself. Either is fine.
What is your web application and your TestCafe test code?
Very small Sample Application for testing this: https://github.com/littlevahn/TestLoginSample/tree/dev

Test Login App
Code: https://github.com/littlevahn/TestLoginSample/tree/dev
URL of App: https://purple-pond-078e7901e.azurestaticapps.net/
Creds have been emailed to the desired email.

Your complete test code (or attach your test files):

 import { Selector, Role } from 'testcafe';

const testUser = Role('https://purple-pond-078e7901e.azurestaticapps.net/login', async t => {
	const username =<EMAIL_ADDRESS>	const password = 'Wl1Z!Yz#C6OKzOX%D6o1';
	await t
		.typeText('#loginId', username)
		.typeText('#password', password)
		.click('.submit');
}, { preserveUrl: true });

fixture
	.disablePageCaching`Dashboard Order Flyer NOW! - Integration Flow`
	.page`https://purple-pond-078e7901e.azurestaticapps.net/`;

test
	.disablePageCaching('Login to Test Users Account', async t => {

		await t.useRole(testUser);

		//const username =<EMAIL_ADDRESS>		//const password = 'Wl1Z!Yz#C6OKzOX%D6o1'
		/*await t
			.click('.MuiButtonBase-root-30')
			.typeText('#loginId', username)
			.typeText('#password', password)
			.click('.submit')
			.expect('#cardContentWrapper > div:nth-child(1) > div').exists;
			*/
	});

test
	('Select a listing and Purcahse a flyer', async t => {
		await t
			.navigateTo('https://purple-pond-078e7901e.azurestaticapps.net/ml/home')
			.expect('#cardContentWrapper > div:nth-child(1) > div').exists;
	});

Your complete configuration file (if any):

Your complete test report:

> testcafe chrome --max-http-header-size=2048000 --live tests\endToEnd\NowDashboard\OrderFlyer.spec.js

Live mode is enabled.
TestCafe now watches source files and reruns
the tests once the changes are saved.

You can use the following keys in the terminal:
'Ctrl+S' - stops the test run;
'Ctrl+R' - restarts the test run;
'Ctrl+W' - enables/disables watching files;
'Ctrl+C' - quits live mode and closes the browsers.

Watching the following files:
  C:\TF\Src\IntegrationTests2\tests\endToEnd\NOWDashboard\OrderFlyer.spec.js
 Running tests in:
 - Chrome 91.0.4472.164 / Windows 10

 Dashboard Order Flyer NOW! - Integration Flow
 √ Login to Test Users Account

 2 passed (6s)

Make changes to the source files or press Ctrl+R to restart the test run.

Stopping TestCafe live mode...
Terminate batch job (Y/N)? y
PS C:\TF\Src\IntegrationTests2> npm run testPOC

><EMAIL_ADDRESS>testPOC C:\TF\Src\IntegrationTests2
> testcafe chrome --max-http-header-size=2048000 --live tests\endToEnd\NowDashboard\OrderFlyer.spec.js

Live mode is enabled.
TestCafe now watches source files and reruns
the tests once the changes are saved.

You can use the following keys in the terminal:
'Ctrl+S' - stops the test run;
'Ctrl+R' - restarts the test run;
'Ctrl+W' - enables/disables watching files;
'Ctrl+C' - quits live mode and closes the browsers.

Watching the following files:
  C:\TF\Src\IntegrationTests2\tests\endToEnd\NOWDashboard\OrderFlyer.spec.js
 Running tests in:
 - Chrome 91.0.4472.164 / Windows 10

 Dashboard Order Flyer NOW! - Integration Flow
 √ Login to Test Users Account
 √ Select a listing and Purchase a flyer

 2 passed (6s)

Screenshots:

Steps to Reproduce:

What Success looks like through the UI none testcafe:

Go to https://purple-pond-078e7901e.azurestaticapps.net/
Click signin
Fill in Credentials (emailed)
Click submit
Get redirect to https://purple-pond-078e7901e.azurestaticapps.net/ml/home Logged in and see 'listing data'

Your Environment details:

testcafe version:                   1.15.0
node.js version:                    v12.18.0
command-line arguments:  testcafe chrome --max-http-header-size=2048000 --live tests\endToEnd\NowDashboard\OrderFlyer.spec.js
browser name and version:  Chrome 91
platform and version:          Windows 10

Hi @baguilar-work
Thank you for the shared information. I've reproduced the issue.

Hi @miherlosev
Is there an ETA for this fix? Maybe I'm having the same (or a similar) issue: I'm able to login with FusionAuth on my first test, but on the second one that login status is not preserved, and if I try to login again it's not possible.


Add non-doc resources

This adds another section with non-doc resources
cc @rust-embedded/resources

r? @jamesmunns
(rust_highfive has picked a reviewer for you, use r? to override)

(no bors, merging manually)


Replay mode with real-time timestamps

Can Replay mode produce data with the current time ? Supose my data is from a week ago, no matter how I modify the .conf file, the data eventgen generates is also from that same previous week. Is what I am asking achievable, or I have to change to sample mode ?
Thanks in advance

Replay mode was changed quite a bit in 6.1 and now can replay events in order with new time points.  Just make sure you set your timefield correct.


Font

Hello,
Could you provide the font used in the screenshot?
Furthermore, any special melange configurations you made to achieve the exact same aesthetics.

I'm guessing you found it, but just in case:
https://github.com/savq/melange/blob/78af754ad22828ea3558e2990326b8aa39730918/.logo/sketch.js#L27-L31


Add ability to specify --shm-size in docker run command

You can set shm-size via:
servers:
  web:
    options:
      shm_size: ...

Is this a recent update?


added rotation arg for labels

this allows to rotate barplot labels.

Hey, I think the rotation function is great, but I think at the same time you should be able to change the orientation/alignment. Maybe in the style of label_align = (:left, :center).
If the attribute is already there, sorry. :)

The align can probably be made automatic for most cases following the logic of Axis ticklabels.