[CT-2171] [Feature] Add adapter(s) version(s) to the log

It would make things much easier when debugging a dbt invocation, if the adapter version were present.
Right now we get (below for a dbt debug)
============================== 2023-02-22 23:21:37.421632 | d8954cb4-b0c3-461a-a0f1-68c918c2fe23 ==============================
23:21:37.421632 [info ] [MainThread]: Running with dbt=1.4.1
23:21:37.422456 [debug] [MainThread]: running dbt with arguments {'write_json': True, 'use_colors': True, 'printer_width': 80, 'version_check': True, 'partial_parse': True, 'static_parser': True, 'profiles_dir': '/Users/fleide/.dbt', 'send_anonymous_usage_stats': True, 'quiet': False, 'no_print': False, 'cache_selected_only': False, 'config_dir': False, 'which': 'debug', 'indirect_selection': 'eager'}
...
23:21:38.799040 [debug] [MainThread]: Flushing usage events
23:21:39.154756 [debug] [MainThread]: Connection 'debug' was properly closed.

But I could be running that with dbt-bigquery 1.4.0, 1.4.1 or 1.4.2!
If we could get that info logeed (anywhere practical, it doesn't need to be at the top):
============================== 2023-02-22 23:21:37.421632 | d8954cb4-b0c3-461a-a0f1-68c918c2fe23 ==============================
23:21:37.421632 [info ] [MainThread]: Running with dbt=1.4.1
23:21:37.422456 [debug] [MainThread]: running dbt with arguments {'write_json': True, 'use_colors': True, 'printer_width': 80, 'version_check': True, 'partial_parse': True, 'static_parser': True, 'profiles_dir': '/Users/fleide/.dbt', 'send_anonymous_usage_stats': True, 'quiet': False, 'no_print': False, 'cache_selected_only': False, 'config_dir': False, 'which': 'debug', 'indirect_selection': 'eager'}
...
23:21:38.122456 [info ] [MainThread]: Running with dbt-bigquery=1.4.0
...
23:21:38.799040 [debug] [MainThread]: Flushing usage events
23:21:39.154756 [debug] [MainThread]: Connection 'debug' was properly closed.

@VersusFacit that's one you may be interested in contributing, even though that's pretty core ;)

➕

yes! related older issue: https://github.com/dbt-labs/dbt-core/issues/5124

Love me some tooling. And I certainly enjoy working on the tasks/ dir in core! 🍵

@jtcohen6 and I did search for an earlier issue, but couldn't find one.
You're good (or you've been around these parts for too long, up to you to decide which one :D)

Also related!

https://github.com/dbt-labs/dbt-core/issues/6097

To @Fleid's point in the issue description ("anywhere practical, it doesn't need to be at the top") — we actually load the adapter a little ways in, so the point where we can know the "active" adapter version is certainly later than when we can know the installed version of dbt-core.
We need to add back telemetry for the "active" adapter's adapter_type and adapter_unique_id. We could also include the adapter_version in that telemetry, and at the same point, fire an event / log message containing any/all of those bits of info.

I think #7741 fixes this!

Nice @VersusFacit 🤩
If possible, we'd be looking for the adapter version to be added to all tasks.


Update quickstart-terraform.md

Removing the hacky way to create a cluster since Terraform now supports vCore.

@gahl-levy
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

#sign-off

#sign-off


Add port 9072 everywhere (via ranges)

I'm actually working on removing this port altogether. This http endpoint is being merged with 9070.

OK, I can update to have the range only be 9070-9071

@jackkleeman Yes.


Get NotSupportedException for a non-seekable stream when ResumeAsync is called after previous call on ResumeAsync timeout

Not sure if this is a real issue.
When the resumable sync  is used with a non-seekable stream, we got the NotSupportedException sometimes. We went through the codes and found there may be something wrong in the ResumableUpload.cs.

At the 374th line (StreamLength = ContentStream.CanSeek ? ContentStream.Length : UnknownSize;).  the StreamLength is the UnknownSize if the stream is non-seekable.

So at the 517th-527th lines, it seems correct to use StreamLength to check if the stream is seekable. When it is seekable, it calls PrepareNextChunkKnownSize which calls set positions at 652th.
if (StreamLength != UnknownSize)
{
PrepareNextChunkKnownSize(request, stream, cancellationToken);
}
else
{
PrepareNextChunkUnknownSize(request, stream, cancellationToken);
}

However at the 627th (StreamLength = LastMediaLength + BytesServerReceived;), the StreamLength is assigned always even though it is non-seekable. So it could be wrong to use the StreamLength to check if it is seekable if the previous upload timeout and one retry is done on the same ResumableUpload instance.

Here are the pseudo-codes to reproduce this issue when the uploaded file size is less than chunk size and the 1st call on ResumeAsync timeouts.
create an object of ResumableUpload.InsertMediaUpload
retry  the below operations if timeout
calls ResumeAsync
return if complete

Sorry for the late response....

So, your stream is non-seekable, right? So, StreamLength is set to unknown size.
https://github.com/google/google-api-dotnet-client/blob/master/Src/GoogleApis/Apis/[Media]/Upload/ResumableUpload.cs#L374

Why do you care about seekable in this case, I thought we said that the stream is NOT seekable. So, I would expect a call to PrepareNextChunkUnknownSize,
https://github.com/google/google-api-dotnet-client/blob/master/Src/GoogleApis/Apis/[Media]/Upload/ResumableUpload.cs#L523

PrepareNextChunkUnknownSize is defined in https://github.com/google/google-api-dotnet-client/blob/master/Src/GoogleApis/Apis/[Media]/Upload/ResumableUpload.cs#L571.
Are you suggesting that there is a bug in this function?

In your last comment you said that the file size is less than chunk size (but it's unknown, right?)
So is it the use case where we have a unknown size stream and the first request fails?

Thanks,
Eyal

I'm fairly sure I've reproduced this bug in a test. I hope to have the new test-cases and a fix ready in the next few days.
It occurs, as you say, when the last chunk of a non-seekable stream fails to upload.

Finally fixed :)


⚠ Bofrost.lu has degraded performance

In b7c22d6, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1265 ms

Resolved: Bofrost.lu performance has improved in 14d8cd6.


F-Droid instructions / artifact

Discussed in person, finished by midday Wednesday

With the new build steps completed (https://github.com/lbryio/lbry-react-native/blob/master/README.md), building for F-Droid would require:

Remove the Google Analytics and Firebase messaging dependencies from build.gradle.

implementation 'com.google.firebase:firebase-analytics:17.2.1'
implementation 'com.google.android.gms:play-services-base:17.1.0'
implementation 'com.google.firebase:firebase-messaging:20.1.0'

Replace the constructor and the @ReactMethod-annotated methods in io.lbry.browser.reactmodules.FirebaseModules with empty placeholders, or stub in cases where a Promise is used.
Remove io.lbry.browser.LbrynetMessagingService.
Update AndroidManifest.xml to remove the Firebase references.
Follow the necessary steps to request for F-Droid packaging.


Update from LTS version to LTS version

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request

Command (mark with an x)
- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [x] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Desired functionality
At our company we want to be able update our Angular apps from LTS version to LTS version.
As it currently stands, this doesn't seem to be possible with ng update, as it will always update to the latest available (stable) version of Angular.
It would be great if you could add this functionality in the form of a new option --lts (so this will update to the latest available LTS version) or something like that, so that one will be able to update an Angular app from version 5 to version 6 even though version 7 (or later) got already released. :)

In the latest versions of the CLI you can specify the npm tag, however I doubt this works in Angular CLI version 1.
Example
ng update @angular/cli@v6-lts
ng update @angular/cli@next

That said we strongly encourage you to update to the latest stable version instead of the LTS, so you can benefit from performance improvements, bug fixes and new features.

It is also important to note that all major versions will receive long term support.  Please see the following for further details: https://angular.io/guide/releases#support-policy-and-schedule


LRP: Terminate connections to deleted LRP backends

When socket-lb is enabled, client applications can continue
to connect to deleted LRP backends. Handle these connections
so that applications can connect to active LRP backends.
Fixes: https://github.com/cilium/cilium/issues/31012
Signed-off-by: Aditi Ghag<EMAIL_ADDRESS>Forcefully terminate stale sockets in the host netns connected to deleted LRP backends when socket-lb is enabled, and allow applications to re-connect to active LRP backends.

/test

/test

/test


Error when running the script

Hi there,
I've followed to instructions to the best of my knowledge, but it didn't work. Any idea what I did wrong?

E:\Console Games\Utilities\MiSTer-N64-Save-Utility-main>python convert_n64_savedata.py -ini
Traceback (most recent call last):
File "E:\Console Games\Utilities\MiSTer-N64-Save-Utility-main\convert_n64_savedata.py", line 343, in
N64Database = populateN64Database()
^^^^^^^^^^^^^^^^^^^^^
File "E:\Console Games\Utilities\MiSTer-N64-Save-Utility-main\convert_n64_savedata.py", line 37, in populateN64Database
romName = line.split('#')[1].strip()
~~~~~~~~~~~~~~~^^^
IndexError: list index out of range
E:\Console Games\Utilities\MiSTer-N64-Save-Utility-main>pause
Press any key to continue . . .

Here's my INI file:

[PATHS]
InputN64SavePath = Before\Pokemon Stadium 1.sav  ; Specify the input N64 save path, before the tool modifies the save file.
OutputSavePath = After\Pokemon Stadium 1.sav     ; Specify the output save path, after the save has been modified with this tool.
; Specify the N64 Save's Cart ID or MD5 checksum, as it appears in N64-database.txt
; If you do not already have N64-database.txt, please download it:
; https://raw.githubusercontent.com/MiSTer-devel/N64_ROM_Database/main/N64-database.txt
[CART_ID]
CartID = NPO___
[OPTIONS]
DumpSaves = F        ; Specify whether or not we should dump the CPak/TPak (and Gameboy) Save from the N64 Save File. Gets dumped to [OutputSavePath]
; If we are not dumping saves, specify the path for all TPaks, including any GB/GameBoy save files.
; If you are not using one, remove ALL text after the "=", like I did for TPak4 below.
; If you are using ANY CPaks, all of these fields must be blank.
; If the bytes are already in the correct format + don't need to be endian-flipped, add a * to the very beginning of your path like I did for TPak3.
;    ^^^^If you do not understand what this means, you likely don't need to add the *: Gameboy .savs always
;           need to be flipped, and unless you manually ripped the save yourself, you do not need to add the *
[TPAKS]
TPak1 = Before\Pokemon - Red Version Gen II GFX.sav
TPak2 =
TPak3 =
TPak4 =
; In port order, specify the path for all your CPaks.
; If you are not using one, remove ALL text after the "=", like I did for CPak4 below.
; If you are using ANY TPaks (Including any GB saves), all of these fields must be blank.
; If the bytes are already in the correct format + don't need to be endian-flipped, add a * to the very beginning of your path like I did for CPak3.
;    ^^^^If you do not understand what this means, you likely don't need to flip them: .mpk files do not need the *
; Please remember to convert any of your CPak saves (e.g. DexDrive format) to the proper .mpk format prior to injection.
;       I recommend this web-based tool to do the conversion: https://savefileconverter.com/#/n64/dexdrive   (Make sure "Controller Pak" is highlighted when downloading the save.)
[CPAKS]
CPak1 =
CPak2 =
CPak3 =
CPak4 =

It looks like the syntax for N64-database.txt had changed between the time I released this tool and this issue got created... The up-to-date tool should now account for the syntax change: can you re-download the .py script from GitHub and test it out again?

Owner

Hi there, I forgot I posted this here. The issue was fixed in this topic: https://misterfpga.org/viewtopic.php?t=7297

Oh, that's very similar to the fix that was pushed to the repo... I'm glad to know that it ended up fixing + working for you!


Fixes various typos in docs

@Saurabh7019 found 1 issue in flow enable command. Kudos to him!
I hope you don't mind that I included it in this PR where I found other issues.
IMPORTANT
environment becomes environmentName in the v7 branch which can be included in this commit: https://github.com/pnp/cli-microsoft365/pull/5225

Closes #5343


Create feature: add new comment

In this PR, the "add new comment" form on the Comments pop up is implemented according to the wireframe:

When the user clicks on the "Comment" button, the data is recorded in the Involvement API.
Demo link

🤸♀🤸🥳🥳
PR is ready for the merge


Question about using AsyncProducerConsumerQueue

I'm new to using Nito.AsyncEx, and I've implemented a MessageQueue class that stores messages in a AsyncProducerConsumerQueue. I have messages (they are a reference type) added like this:
        public void AddMessage(MyMessage message)
        {
            _queue.EnqueueAsync(message);
            _queue.CompleteAdding();
        }

I consume messages asynchronous using this method:
        public async Task ConsumeMessages(CancellationToken cancellationToken)
        {
            while( await _queue.OutputAvailableAsync(cancellationToken))
            {
                var notificationMessage = _queue.Dequeue();
                foreach(var observer in _observers)
                {
                    observer.OnNext(notificationMessage);
                }
            }
        }

I have multiple producers (all within the same process, but could be on any thread) and a single consumer. What I've seen is that the while loop exits after the first message. I thought that this might be because of the _queue.CompleteAdding(); call in AddMessage, so I commented that out. Then I don't see ANY messages get through to the consumer.
Can you please explain how I should be using AsyncProducerConsumerQueue? I think I've got it wrong.
Thanks,
Bob

There's a couple things that jump out to me.
First, AddMessage is calling EnqueueAsync without awaiting the result; it's almost always wrong to ignore tasks returned from async methods. AddMessage should either use await or call the synchronous Enqueue instead.
Second, in a manner similar to BlockingCollection and TPL Dataflow, AsyncProducerConsumerQueue uses the term "complete" to mean "done". As in, that queue will never get another item. Once CompleteAdding is called, any further Enqueue (or EnqueueAsync) calls will fail (and this will cause OutputAvailableAsync to return false).

Then I don't see ANY messages get through to the consumer.

I'm not sure why this would be. There's a basic single-producer, single-consumer test case in this project. Can you provide a minimal reproduction of the problem?

Thanks Stephen. I had been using await inside of AddMessage but took it out probably because I had a problem elsewhere. It's working now -- the messages are all getting through. Thanks for your help!


Include response output: tenant commands

Related to #3754

Add the response output for all the commands under the service:

tenant documentation location

You can reference the commands planner plan and planner bucket. They are already contain the Response heading in their documentation.
For more information what guidelines to follow, be sure to check out the epic issue #3754

@Jwaegebaert I would like to pick it up!

All yours!


Added functionality for flaky tests, more granular step definitions and upload of evidence

This PR introduces the ability to choose what evidence is to be uploaded due to Xrays 100MiB limit. It also adds the possibility to detect flaky tests and it removes failed reruns from  the json import file (also because of the 100MiB limit) When debug option is enabled there will be a new file created, xray-payload-debug.json that contains the report file before duplicates has been removed and flaky tests has been detected. I also added the option to set summary

Did it via my other github account Niklas-Back


add manual page for flux

Problem: A user noted that mpibind options are not documented outside of tutorial information.
It may be helpful for mpibind to provide a flux-mpibind(1) man page that contains

SYNOPSIS showing various flux run -o mpibind=... options
DESCRIPTION describing  mpibind's role
SHELL OPTIONS section describing options in detail, following a similar pattern to flux-shell(1)
SEE ALSO referring to flux-shell(1), flux-run(1).

The options of mpibind for Flux have been documented via 27d7fe5fe4d1efb610a85494d3030cc349a0b4df


Blank page when using command - phonegap run android

Hello,
Phonegap 8.2.2
Android platform 7.1.1
When running the command phonegap run android -d I receive this error in the Chrome inspector console:
Uncaught SyntaxError: Unexpected token )
/* harmony default export */ __webpack_exports__["a"] = ({
    data() { <----this line
        return {
            clipped: false,
            drawer: true,
            fixed: false,
            items: [{ icon: 'home', title: 'Home', linkpath: '/' }, { icon: 'star', title: 'Hello Vue', linkpath: '/helloworld' }],
            miniVariant: false,
            right: true,
            rightDrawer: false,
            title: 'Vuetify.js'
        };
    },
    methods: {
        linkto(pathname) {
            this.$router.push({ path: pathname });
        }
    }
});

When in the browser, everything works fine.
I have also tried the --lr command but no luck.
Any idea why please?
Thank you.

suspect Android env. issue?
How about to lauch android app from Phonegap GUI application?

I had to remove the android platform and re-add it, weird but it worked.


409 conflict on a new Github workspace

If I create an empty GitHub repository and try to add it as a workspace, I get "409 conflict" message.
Looking into my network tab, this is the response to the API call stackedit must be making

Hi. I faced the same issue. It happens when you create a new workspace without having a file or sth in it. I added a readme file and it started to sync. I suppose it is sth related with the remote repository folder structure or initialization of the remote repository itself.

Hi. I faced the same issue and managed to solve it. It happens when you create a new workspace without having a file or sth in it. I added a readme file and it started to sync. I suppose it is sth related with the remote repository folder structure or initialization of the remote repository itself.

This fixed it for me :)


Installation of kernel locally to home

Hello,
I'd like to know if it is possible to somehow install IHaskell kernel locally to my home folder, since I don't enjoy installing packages system wide. Even though it is quite easy since I am on Arch Linux, I would appreciate a way to install this locally to e.g. my home folder.
Thank you

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/27970484-installation-of-kernel-locally-to-home?utm_campaign=plugin&utm_content=tracker%2F332399&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F332399&utm_medium=issues&utm_source=github).

Yup, the standard stack-based installation described on the README installs locally.

Thank you. Maybe it would be nice to mention explicitly, but never mind.
Great work!


About Apple Silicon

I think nni needs to support apple silicon , coz Apple silicon is cool machine for ML/Deep learning jobs

Could you give a detailed error message to show that NNI does NOT support Apple Silicon?

Two error about that :

error: The 'websockets' distribution was not found and is required by nni

I think apple silicon devices need arm64 arch support ,  tf for apple silicon was pubished ,  I think nni  can release version to support these devices.


DOC: Ophyd Doc Improvements

I saw in https://github.com/NSLS-II/ophyd/issues/467 there will be a documentation effort for ophyd and wanted to add my two cents. I really liked how bluesky had a user and developer sections and always wanted the same for ophyd. I think this a) helped users get used to using bluesky very quickly b) promoted standards for developers creating scans. A lot of this is based on what we at SLAC originally struggled with when trying to create our own ophyd devices. Here is a little outline I wrote about what I feel is missing:

User Guide

Basic functionality

read, set, trigger e.t.c

How to use status objects
How to use Subscriptions

Developers Guide

Device Creation

Component types
- DynamicDeviceComponent especially
Signal types
- AttributeSignal, DerivedSignal especially

Positioners
- Be explicit about requirements for creating custom Positioner objects
How to create subscriptions
How to create useful status objects

I was going to try and write some of this up myself. For SLAC I wanted to create a style guide kind of thing so that we are at least internally consistent about how we create our objects. I figured it might be useful to the community as well.

Yeah, the bluesky documentation got at least three rewrites and informal word-by-word reviews with users from various perspectives. These suggestions from you are super useful as I begin that process for ophyd.
I think I might try organizing the docs along the lines of what I did with caproto -- a clear split between teaching-by-narrative-and-example and straight API docs. I'll push early and solicit some feedback/contributions if you have time to collaborate on it. I really like the idea of a style guide.

Noting this here so it doesn't get lost: we should link to the experimetnal project https://github.com/klauer/recordwhat to make it a bit more discoverable. (h/t @prjemian)


add (un)install functionality to Makefile

This PR adds the enhancement proposed in #251. The user is now able to clone or download the repo and use $ make install to install everything to get z up and running. It is also possible to uninstall using $ make uninstall. The readme option is still available.

True, especially since z can be found in package managers like brew now.


Update App.js

@IniyalPalanisamy , As I can see, you've created a PR without any meaningful contributions or description. I would kindly request you to avoid creating spam PRs. If you genuinely want to contribute, please create an issue or work on an existing one, and then proceed to submit your work after making real improvements.


flavors not existing in OS but associated with a vm are marked as ina…

Flavors that exist in cloud but are used by a running vm are marked as inactive.
Close #286

:+1:


rexray/ebs on AWS and docker swarm, problem with device discovery

Summary
When creating a container with an EBS volume docker returns with an error "problem with device discovery".
Bug Reports
Version
rexray/ebs:latest
Expected Behavior

EBS Volume Created in AWS
Volume attaches to instance.
Docker mounts volume into container.
Container starts.

Actual Behavior

EBS Volume Created in AWS
Volume attaches to instance
Docker errors out with error docker: Error response from daemon: error while mounting volume '': VolumeDriver.Mount: docker-legacy: Mount: test: failed: problem with device discovery.

Steps To Reproduce

Create AWS instances using latest Amazon Linux AMI
Install docker
Set up swarm
Install rexray/ebs following guide on each instance
Create test container using rexray/ebs

See below for a full console output. Interestingly, in my troubleshooting the volume will not delete either until I manually detach it from the instance in AWS.
[ec2-user@xxxxxxx]$ sudo docker plugin install rexray/ebs REXRAY_PREEMPT=true EBS_REGION=ap-southeast-2 EBS_ACCESSKEY=AKIAJJEZLCOGWWU2S26Q EBS_SECRETKEY=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
Plugin "rexray/ebs" is requesting the following privileges:
 - network: [host]
 - mount: [/dev]
 - allow-all-devices: [true]
 - capabilities: [CAP_SYS_ADMIN]
Do you grant the above permissions? [y/N] y
latest: Pulling from rexray/ebs
d726edfb6c8d: Download complete
Digest: sha256:b5b0680b6dd53a4c61bac21942738a69edfe3d6a6516acc13045d257889c9213
Status: Downloaded newer image for rexray/ebs:latest
Installed plugin rexray/ebs
[ec2-user@xxxxxxx]$ docker run -ti --volume-driver=rexray/ebs -v test:/test busybox
docker: Error response from daemon: error while mounting volume '': VolumeDriver.Mount: docker-legacy: Mount: test: failed: problem with device discovery.
[ec2-user@xxxxxxx]$ docker run -ti --volume-driver=rexray/ebs -v test:/test busybox
docker: Error response from daemon: error while mounting volume '/var/lib/docker/plugins/1b5875fe11fd6f46eebb647c4b7986039a7d2955f341f69561e0080ae9f2fa80/rootfs': VolumeDriver.Mount: docker-legacy: Mount: test: failed: no device name returned.
[ec2-user@xxxxxxx]$ docker volume inspect test
[
    {
        "CreatedAt": "0001-01-01T00:00:00Z",
        "Driver": "rexray/ebs:latest",
        "Labels": null,
        "Mountpoint": "",
        "Name": "test",
        "Options": null,
        "Scope": "global",
        "Status": {
            "availabilityZone": "ap-southeast-2c",
            "fields": null,
            "iops": 0,
            "name": "test",
            "server": "ebs",
            "service": "ebs",
            "size": 16,
            "type": "standard"
        }
    }
]
[ec2-user@xxxxxxx]$ docker volume rm test
Error response from daemon: remove test: volume is in use - [314b5a64875451191fb9dd52bca19d073a858a567d244a733e222f5c7763c208, c319647db5a63e139be2c0a1481054765a730aa025c8955d6d7194e28a3d2d88]
[ec2-user@xxxxxxx]$ docker container rm 314b5a64875451191fb9dd52bca19d073a858a567d244a733e222f5c7763c208 c319647db5a63e139be2c0a1481054765a730aa025c8955d6d7194e28a3d2d88
314b5a64875451191fb9dd52bca19d073a858a567d244a733e222f5c7763c208
c319647db5a63e139be2c0a1481054765a730aa025c8955d6d7194e28a3d2d88
[ec2-user@xxxxxxx]$ docker volume rm test
Error response from daemon: remove test: VolumeDriver.Remove: docker-legacy: Remove: test: failed: error deleting volume

here's where I detach the volume in the EC2 console
[ec2-user@xxxxxxx]$ docker volume rm test
test

Configuration Files
No applicable, using the docker plugin.  But here's the output of docker plugin inspect
[
    {
        "Config": {
            "Args": {
                "Description": "",
                "Name": "",
                "Settable": null,
                "Value": null
            },
            "Description": "REX-Ray for Amazon EBS",
            "DockerVersion": "18.05.0-ce",
            "Documentation": "https://github.com/thecodeteam/rexray/.docker/plugins/ebs",
            "Entrypoint": [
                "/rexray.sh",
                "rexray",
                "start",
                "-f",
                "--nopid"
            ],
            "Env": [
                {
                    "Description": "",
                    "Name": "DOCKER_LEGACY",
                    "Settable": [
                        "value"
                    ],
                    "Value": "true"
                },
                {
                    "Description": "",
                    "Name": "REXRAY_FSTYPE",
                    "Settable": [
                        "value"
                    ],
                    "Value": "ext4"
                },
                {
                    "Description": "",
                    "Name": "REXRAY_LOGLEVEL",
                    "Settable": [
                        "value"
                    ],
                    "Value": "warn"
                },
                {
                    "Description": "",
                    "Name": "REXRAY_PREEMPT",
                    "Settable": [
                        "value"
                    ],
                    "Value": "false"
                },
                {
                    "Description": "",
                    "Name": "HTTP_PROXY",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "LIBSTORAGE_INTEGRATION_VOLUME_OPERATIONS_MOUNT_ROOTPATH",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "LINUX_VOLUME_ROOTPATH",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "LINUX_VOLUME_FILEMODE",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "EBS_ACCESSKEY",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "EBS_ENDPOINT",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "EBS_KMSKEYID",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "EBS_MAXRETRIES",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "EBS_REGION",
                    "Settable": [
                        "value"
                    ],
                    "Value": "us-east-1"
                },
                {
                    "Description": "",
                    "Name": "EBS_SECRETKEY",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "EBS_STATUSINITIALDELAY",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "EBS_STATUSMAXATTEMPTS",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "EBS_STATUSTIMEOUT",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "EBS_USELARGEDEVICERANGE",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "CSI_ENDPOINT",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "The name of the CSI plug-in used by the CSI module.",
                    "Name": "X_CSI_DRIVER",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "A flag that disables the CSI to libStorage bridge.",
                    "Name": "X_CSI_NATIVE",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                }
            ],
            "Interface": {
                "Socket": "rexray.sock",
                "Types": [
                    "docker.volumedriver/1.0"
                ]
            },
            "IpcHost": false,
            "Linux": {
                "AllowAllDevices": true,
                "Capabilities": [
                    "CAP_SYS_ADMIN"
                ],
                "Devices": null
            },
            "Mounts": [
                {
                    "Description": "",
                    "Destination": "/dev",
                    "Name": "",
                    "Options": [
                        "rbind"
                    ],
                    "Settable": null,
                    "Source": "/dev",
                    "Type": "bind"
                }
            ],
            "Network": {
                "Type": "host"
            },
            "PidHost": false,
            "PropagatedMount": "/var/lib/rexray",
            "User": {},
            "WorkDir": "",
            "rootfs": {
                "diff_ids": [
                    "sha256:3e6c5310eb0c1fcbe49312bae86e363bf7ef7be4dd9e0dcd2206200b265a0693"
                ],
                "type": "layers"
            }
        },
        "Enabled": true,
        "Id": "1b5875fe11fd6f46eebb647c4b7986039a7d2955f341f69561e0080ae9f2fa80",
        "Name": "rexray/ebs:latest",
        "PluginReference": "docker.io/rexray/ebs:latest",
        "Settings": {
            "Args": [],
            "Devices": [],
            "Env": [
                "DOCKER_LEGACY=true",
                "REXRAY_FSTYPE=ext4",
                "REXRAY_LOGLEVEL=warn",
                "REXRAY_PREEMPT=true",
                "HTTP_PROXY=",
                "LIBSTORAGE_INTEGRATION_VOLUME_OPERATIONS_MOUNT_ROOTPATH=",
                "LINUX_VOLUME_ROOTPATH=",
                "LINUX_VOLUME_FILEMODE=",
                "EBS_ACCESSKEY=ABC",
                "EBS_ENDPOINT=",
                "EBS_KMSKEYID=",
                "EBS_MAXRETRIES=",
                "EBS_REGION=ap-southeast-2",
                "EBS_SECRETKEY=123",
                "EBS_STATUSINITIALDELAY=",
                "EBS_STATUSMAXATTEMPTS=",
                "EBS_STATUSTIMEOUT=",
                "EBS_USELARGEDEVICERANGE=",
                "CSI_ENDPOINT=",
                "X_CSI_DRIVER=",
                "X_CSI_NATIVE="
            ],
            "Mounts": [
                {
                    "Description": "",
                    "Destination": "/dev",
                    "Name": "",
                    "Options": [
                        "rbind"
                    ],
                    "Settable": null,
                    "Source": "/dev",
                    "Type": "bind"
                }
            ]
        }
    }
]

Logs
I'd love to provide this, but I can't for the life of me find any logs output by the docker plugin, happy to run commands though.
Edit: Formatting

I'm having the exact same problem. @voney, when installing rexray as a docker plugin, the logs will appear on /var/log/docker. Hopefully, mine could help: https://gist.github.com/fabiob/a318bc24b6e96f9ae34c28af53409f61

I too have this issue with 0.11.3. I'm starting to wonder if anyone is successfully using the EBS plugin on a swarm deployment...

I've fixed the problem by switching out of the t3.* instances. Looks like their storage drivers aren't compatible with rexray's.

Another me too.
Switching from M5 to M4 instances solved this for me. No errors in the log apart from the ones listed above.
The EBS device is attached to the instance correctly, but rexray can't see the attachment for some reason.

Switching from a t3.* to t2.* instance type resolved this for me too.

I've wasted like a week XD, I was using t3a.*, moved to t2, and it's working

It's a complete shambles. How can such brilliant stuff fall so low. AWS is a costly mess sometimes.

This is seems not supported any more, what is the migration tool of this project?

I have only started to have this problem today in one of my environments.... Am I the only one?

Same for us since yesterday arround 12h00 UTC-4 in  euw1-az1 and today this morning with euw1-az2 (two AZ in eu-west-1, AWS).

Same here, same AMI image as before but today it is not working anymore.

On some newer systems nvme id-ctrl /dev/nvme1n1 --raw-binary (used inside rexray) is returning different (unexpected) private metadata - this is why the volume isn't found.
Hopefully we can make it use ebsnvme-id instead.

Same here, critical issue from my point of view.

Wouldn't expect it to be fixed though. But I don't know if there are any alternatives. I use it with ECS and cloud formation but maybe I can do it without?

Do you know any alternative to mount EBS on ECS containers automatically?

For all those struggling with this we have a patch to fix the EBS related issue, I do not believe this will help anyone with issues on Docker Swarm (unless they're using EBS underneath).

For all those struggling with this we have a patch to fix the EBS related issue, I do not believe this will help anyone with issues on Docker Swarm (unless they're using EBS underneath). This is the patch It is a small patch on top of @nbryant42 's most recent work: https://github.com/nbryant42/rexray/tree/revert-1345

:eyes: I might be willing to merge this, but I may need a bit of context. How reproducible is this issue? The only issues I've seen in my environment (I do not need the fix for issue 1345) are intermittent.
Recently I noticed that upgrading the image to Alpine 3.18 causes problems, so I am a bit worried by your use of FROM python:3-alpine which could move at any time

FROM python:3-alpine3.18 might be preferable.

For all those struggling with this we have a patch to fix the EBS related issue, I do not believe this will help anyone with issues on Docker Swarm (unless they're using EBS underneath). This is the patch It is a small patch on top of @nbryant42 's most recent work: https://github.com/nbryant42/rexray/tree/revert-1345

eyes I might be willing to merge this, but I may need a bit of context. How reproducible is this issue? The only issues I've seen in my environment (I do not need the fix for issue 1345) are intermittent.
Recently I noticed that upgrading the image to Alpine 3.18 causes problems (edit: probably my mistake, I neglected to update the final plugin image version), so I am a bit worried by your use of FROM python:3-alpine which could move at any time
@bdellegrazie, is this specific to particular instance types? I am only using c6a.*, m6*, and t3a.*
Sounds like I haven't seen any problems because I haven't attempted to mount any volumes today?

We also started seeing this issue as of today across every node where we still rely on rexray to mount EBS volumes for ECS workloads. In our case it is consistent, 100% reproducible with the ami-03a0a389761973845 AMI.

We also started seeing this issue from today on r5.* instance types. Moved to r4 types and it started working!

I also have the similar issues, tried t2.* instead of t3.* works for me.

@bdellegrazie, is this specific to particular instance types? I am only using c6a., m6, and t3a.*
@nbryant42 , @ScOut3R and everyone else.
The root cause of this is a change in the underlying physical infrastructure used by AWS to service various instance types. Newer EBS volumes use a different vendor device block with a different structure. It's absolutely repeatable - as soon as the nvme storage starts reporting what looks like v2 of the vendor block structure, rexray without the patch will fail.

The patch works because we use AWS's own tool (ebsnvme-id) to get the configured symlink name rather than relying on the older nvme tool and trying to decode the vendor block directly.
You might get lucky by choosing a different instance type but it's not predictable.

All: commit updated to fixate the Python container as recommended by @nbryant42 :
https://github.com/joan-s-molas/rexray/commit/2cd528233ec263c40298c93909e25e7c7fb1f6bc

@nbryant42 rased https://github.com/nbryant42/rexray/pull/1 target branch revert-1345

Hi, sorry for my ignorance... how can I apply this patch in my environment? currently I am installing the rexray plugin via
docker plugin install rexray/ebs

@cballesteros-sistrol at the moment you need to build the plugin locally and push it to your own docker repository somewhere.
To build the plugin, clone joan's repo, master branch and follow the documented build steps - once the PR above is merged, we can track nbryant42's one.
The one complication is that docker doesn't allow you to rename a plugin once built but you can set the root name of this plugin via DOCKER_PLUGIN_ROOT so it's easy to push with docker plugin push as follows
DRIVER=ebs make
DRIVER=ebs DOCKER_PLUGIN_ROOT=example.docker.registry/rexray make build-docker-plugin
docker plugin push

the above example assumes you have a docker registry called example.docker.registry and a repository there called rexray

Thank you very much for your  @bdellegrazie.
I'm waiting for @nbryant42 to merge the fix.
Thank you very much to all of you.

@cballesteros-sistrol at the moment you need to build the plugin locally and push it to your own docker repository somewhere.
To build the plugin, clone joan's repo, master branch and follow the documented build steps - once the PR above is merged, we can track nbryant42's one.
The one complication is that docker doesn't allow you to rename a plugin once built but you can set the root name of this plugin via DOCKER_PLUGIN_ROOT so it's easy to push with docker plugin push as follows
DRIVER=ebs make
DRIVER=ebs DOCKER_PLUGIN_ROOT=example.docker.registry/rexray make build-docker-plugin
docker plugin push

the above example assumes you have a docker registry called example.docker.registry and a repository there called rexray

Thank you for the steps @bdellegrazie. I'm trying to build joan's repo's master branch, however the go generate command returns a git related error: fatal: No names found, cannot describe anything. I don't have much experience building go applications, any help would be greatly appreciated.

To build the plugin, clone joan's repo, master branch and follow the documented build steps - once the PR above is merged, we can track nbryant42's one.
The one complication is that docker doesn't allow you to rename a plugin once built but you can set the root name of this plugin via DOCKER_PLUGIN_ROOT so it's easy to push with docker plugin push as follows
DRIVER=ebs make
DRIVER=ebs DOCKER_PLUGIN_ROOT=example.docker.registry/rexray make build-docker-plugin
docker plugin push

the above example assumes you have a docker registry called example.docker.registry and a repository there called rexray

Thank you for the steps @bdellegrazie. I'm trying to build joan's repo's master branch, however the go generate command returns a git related error: fatal: No names found, cannot describe anything. I don't have much experience building go applications, any help would be greatly appreciated.
Full output:
❯ DRIVER=ebs make
docker run -it --rm \
  -v "[...]":"/go/src/github.com/joan-s-molas/rexray" golang:1.20.5-alpine3.17 \
  sh -cx "apk add git && \
  git config --global --add safe.directory /go/src/github.com/joan-s-molas/rexray && \
  cd \"src/github.com/joan-s-molas/rexray\" && \
  XGOOS= XGOARCH= GOOS= GOARCH= go generate && \
  GOOS= GOARCH= go build -tags 'ebs' -o \"rexray\""
+ apk add git
fetch https://dl-cdn.alpinelinux.org/alpine/v3.17/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.17/community/x86_64/APKINDEX.tar.gz
(1/6) Installing brotli-libs (1.0.9-r9)
(2/6) Installing nghttp2-libs (1.51.0-r0)
(3/6) Installing libcurl (8.1.2-r0)
(4/6) Installing libexpat (2.5.0-r0)
(5/6) Installing pcre2 (10.42-r0)
(6/6) Installing git (2.38.5-r0)
Executing busybox-1.35.0-r29.trigger
OK: 16 MiB in 22 packages
+ git config --global --add safe.directory /go/src/github.com/joan-s-molas/rexray
+ cd src/github.com/joan-s-molas/rexray
+ XGOOS= XGOARCH= GOOS= GOARCH= go generate
fatal: No names found, cannot describe anything.
exit status 128
core/core.go:1: running "go": exit status 1
rexray.go:1: running "go": exit status 1
make: *** [Makefile:55: rexray] Error 1

@ScOut3R you can fix that issue by creating an artificial tag like this:
git tag v420.0.0 -m "rexray nvme fix"

Thank you @a-nych, worked like a charm.

@nbryant42 rased nbryant42#1 target branch revert-1345

I've built and published the rex-ray EBS plugin for linux/amd64 here, based on this repository https://github.com/joan-s-molas/rexray/tree/fix/rexray
https://hub.docker.com/r/umsp/rexray-ebs
Tested on my workloads and it's working. Make sure to install it with an alias like this:
EBS_USELARGEDEVICERANGE=true docker plugin install umsp/rexray-ebs:nvme-fix --alias rexray/ebs REXRAY_PREEMPT=true EBS_REGION=${aws_region} --grant-all-permissions

This has worked perfectly!

Thanks for the fix. Merged into my personal fork at https://github.com/nbryant42/rexray/tree/revert-1345
This branch will likely receive occasional dependency version updates going forward, at least as long as I'm at my current employer and continuing to use rexray.

Hi, thanks for all the work.
I uninstalled the existing plugin with docker plugin rm rexray/ebs and tried to install both @a-nych and @nbryant42 images but I get layers from manifest don't match image configuration. Does anyone know what's up with that?

Yes, upgrading Docker worked, thanks.

I used this for m5.large instance with ebs io2 and data size 10GB region us-east-2 and still getting problem with service discovery i am using docker swarm.
I am using aws instance profile with all allow ec2 permissions.
EBS_USELARGEDEVICERANGE=true docker plugin install umsp/rexray-ebs:nvme-fix --alias rexray/ebs REXRAY_PREEMPT=true --grant-all-permissions

So, I don't test the image I publish on RHEL9, nor with io2 volumes. I don't use Swarm either, but it should't make a difference.
I test on ECS-Optimized Amazon Linux 2023 and gp3. That means Docker 25.0.3 at the moment I think. Some people with older Docker may have compatibility problems, as I'm building from Docker 26.
Also, I'm on vacation this week and more generally don't have a lot of time to devote to this.
All that being said, you haven't included any information from the logs.  What happens is it makes the request to attach the EBS volume to the instance, then sits there waiting, checking and rechecking until the device shows up in /dev. This can take several minutes, and on ECS, it can cause task launch to time out and fail once or twice before it eventually succeeds. I'm not familiar with Swam, but something similar might happen in that environment.
If the volume is already attached to some other EC2 node, it may help to manually detach it from there.

Actually I create the ebs volume using terraform and then wants rexray/ebs to mount the container to it.

So there are a few different links in the chain of events, and if you've got Terraform set up to do more than just create a blank volume, it spends some time attached to the Terraform machine for formatting and initialization.
Either way, need to confirm whether (a) the request to attach the volume to the Swarm instance is failing or (b) request succeeds, but the plugin's polling loop fails to detect the right device in /dev. Can confirm this with the AWS console and/or command-line tools.


Implement VGA driver

Current status: this has been implemented, but not yet written about in the book.

Now that https://github.com/intermezzOS/rfcs/pull/8 has been merged, the current implementation in console/ is likely to be replaced, right? Are we envisioning that the new driver will in any way be related to https://github.com/intermezzOS/vga?

Yes, it's going to be replaced. I know it's at the 11th hour, but I think it'll be better for it. 😄

Are we envisioning that the new driver will in any way be related to https://github.com/intermezzOS/vga?

IIRC they're basically copies of each other right now, so I expect that one to update in sync with this one.

Should one be deleted and made to simply point to the other?

The idea of that repo is to provide a stand-alone project to get your feet wet; the README and such doesn't do a very good job of explaining that at the moment :(


Date Picker Pager: Option to stay compact

I think it's great that you made the picker filling the max width. This may be truly what in most of the cases is the expected behavior.
In my case I would like to have either an option to stay in the fixed size width to have it centered or to introduce a width constant I could use to constrain it's size with an outer box.
At this time I need to do the math myself to see what width it needs.
That's not too hard, but for convenience I think you should offer that option.
Currently the "natural" width is 7x42+8x2 dp.

It fills width because it uses lazy row under the hood.
This will happen otherwise:

Okay, I understand.
So my suggestion is to have optionally a Box around it that constraints the width to 310.dp - the natural width the component has with no additional paddings.
Or put the 310.dp as an public constant somewhere.


⚠ TorrentLeech has degraded performance

In d94b200, TorrentLeech ($TL) experienced degraded performance:

HTTP code: 200
Response time: 2818 ms

Resolved: TorrentLeech performance has improved in 27fa2a4 after 8 minutes.


Version 2025.0.3 is not open source?

I was planning to do a PR and noticed the version difference from the nuget and this repository.
I wonder the reason of that, and what changed between version 2025.0.2 and 2025.0.3.

https://github.com/Nice3point/RevitToolkit/blob/main/Changelog.md#release-202503
2025.0.3 Minor fix related to removal of unused dependency. The develop branch is usually up to date always
The release will be published in the main branch in a few minutes, sorry for its unavailability

I didn't do automatic publishing on Nuget because of high risks of invalid versions or accidental pushes to the main branch. And not wanting to frequently update token in Github secrets for all Open source projects.  Nuget package cannot be removed, only hidden, so it is much more convenient and reliable to build and remove outdated versions locally. If the project becomes more global, I will reconsider this behavior

I didn't do automatic publishing on Nuget because of high risks of invalid versions or accidental pushes to the main branch. And not wanting to frequently update token in Github secrets for all Open source projects. Nuget package cannot be removed, only hidden, so it is much more convenient and reliable to build and remove outdated versions locally. If the project becomes more global, I will reconsider this behavior

I found out recently you can remove from the Nuget, but you cannot replace the version if you remove. Go in the Contact Support in your package and there is a option for that.
In my case I can only update the main branch by creating a PR and approving, after the Github action build everything with tests in some cases.


Collimator feature (b-camera) on 20240223 sframesky images

on 20240223, the collimator feature in the b-camera of the sframesky images are clearly visible (I didn t see any obvious effect on the redshifts, so I ve QA-validated the tiles): https://data.desi.lbl.gov/desi/spectro/redux/daily/nightqa/20240223/sframesky-20240223.pdf.
e.g. for expid=226845:

the amplitude of the effect varies through the exposures, but is overall quite high.
also I notice that the effect is strong for 226840, but almost disappears on the next exposure 226841 (and then comes back); I report just in case.

gathering here elements from the slack discussion (https://desisurvey.slack.com/archives/C01HNN87Y7J/p1708883336494629 and after):

@djschlegel : "I’m concerned that we might not be running with the correct calibration vectors and are seeing the collimator absorption dips."
@akremin : "I can confirm that the calibrations were processed first, all dependencies were followed, and the calibrations were used correctly by the science exposure scripts; Looking at the humidities, there was a shift from when the science exposures were taken with ~25% humidity and when the cals were taken with ~13% humidity. But I don’t think that level of variation is unheard of or should cause these issues."

@julienguy , sorry, I think you're the best person to debug this and to declare if we're fine or if something's up with the fiberflat humidity correction.  It does look especially poor on this night.  Sky level was ~13---high but not exceptionally so.


Hyphen marked as incorrect after case difference ignored

Describe the bug
I often see - characters coloured red when they are correct. This only happens when there is another character which is the wrong case.
Input and Answer
a-bc
↓
A-bc
Expected Result
Input is marked as correct. All green
Actual Result
a is marked as correct (desired behaviour) but - is marked as red (incorrect), which is not the desired behaviour.
Screenshots

Note that if the A at the start is the right case, then the - is marked correct. (So it's not the case that I'm typing - and the correct answer is a different unicode character that looks similar.)

I've tried a simplified version. It happens with just a-->A-. And also -a->-A
Desktop (please complete the following information):

Anki Version :
Version 2.1.61 (0c1eaf4c)
Python 3.9.15 Qt 6.4.2 PyQt 6.4.0

I'm just modifying my cards with <script src="https://derdemystifier.github.io/AnkiIgnoreCase/ignoreCase.min.js"></script>

Done! I fixed this a couple of weeks ago but forgot to compile the src files. Finally done in cfa9862.
Since you use <script src="https://derdemystifier.github.io/AnkiIgnoreCase/ignoreCase.min.js"></script>, it will work fine. No changes needed on your end.


Can't cast functions | GUI Code

At first the only way where you can view important messages, is opening a issue, because everyone is spamming you @ Twitter.
So, my problem is that i can't cast functions and it's important for some GUI Code for me.
I think you know casting.
Button btn = (Button) findViewById(R.id.btn);
The '(Button)' is the cast and if you cast a function, the error says that a ';' isn't there where it should be, but the error just says that because casting isn't implented.
Could you please add it

Ummm its JavaSCRIPT not Java

That code is in Java, so Zhuowei can't really add it, as he didn't code the JavaScript parser ModPE uses. You might be able to find a way to cast functions in JS.

I said a perfectly fine comment. If you're going to snap at me because I stated that the thing you're requesting might be possible already, you need to grow up.

@Black-DeathPE It's not working!

I think youre 12-13 years old and say you need to grow up

You don't need to cast in JavaScript

@Godsoft029 Please stop spamming me with your comments you don't need to cast in JavaScript, are your behind brain won't get it?
I need it for GUI Code, but you guys seem like noobs.
Please stop with that spam:

Nobody asked you guys
You guys spam
Your comments are useless
Just stop.

I don't see how saying that how this suggestion would be hard to add is "useless." However, I've been put off by your immaturity, so I'll stop talking to you now.

Oh yeah also, don't call me a noob. You have no evidence. If you went and saw what mods I've made you'd not believe that.
Google "ZOMWar mcpe mod," look at the code and then tell me that I'm a noob. Then you'd definitely be making false accusations.
Don't call me a spammer when you see people on this issue tracker making issues with no content or purpose.

I don't care in your skills or mods.

And please tell me how you would force to soft keyboard to open, if you aren't able to cast something.

Android:
InputMethodManager imm = (InputMethodManager) getSystemService(Context.INPUT_METHOD_SERVICE);
imm.showSoftInput(getWindow().getDecorView(), InputMethodManager.SHOW_FORCED);

That's awkward since this works: getWindow().setSoftInputMode(WindowManager.LayoutParams.SOFT_INPUT_STATE_VISIBLE);
No casting needed.

And also nobody works with me, I work solo :)

Well, @Black-DeathPE you've made it, well im sorry, but for some things casting is needed.
Well im closing this issue


ROS completely stops network traffic

ROS 1.4.2 running in VMWare (DHCP with reservations)
We occasionally get nodes that randomly completely stop passing traffic.  In this latest case, I added two worker nodes to an existing cluster.  They came up fine, registered with K8S, a few node dependent pods were even created just fine.  Then all of a sudden, no communication.  I can't ping the node, the node can't ping anything else.

Something I do notice that is strange, the initial DHCP request is for a hostname of rancher.  Then it changes to the hostname, then back to rancher.
Sorry for the screen shots - we can't copy/paste from our VMWare console sessions.
During boot

It's so strange.
Is there any special configuration for your DHCP server?
Which VMWare version？
We will try to reproduce.

No special DHCP config.  Running vSphere 6.5.0 build 9451637
We don't have this issue on any of our other 200 VM's running in this cluster, only K8S servers and only randomly.
Turns out that when it won't get a DHCP IP, I can restore network traffic by disabling/enabling the vNIC in vSphere, or physically powering down the VM and restarting it.  A reboot doesn't resolve the issue.

Just had another node stop passing traffic. These messages just repeat in the logs.  No other errors or anything that I can see in any of the logs.


Fix iOS text wrap bug

Why these changes are being introduced:
SwiftUI/iOS has some unusual behavior for list markers. It adds line height to them, such that when we increase the font size for a marker, the line height is dramatically increased. This is particularly visible when the text next to the marker wraps, which is common for TIMDEX UI record titles.
Relevant ticket(s):

GDT-246

How this addresses that need:
This implements a CSS workaround. First, we reset the line height to 0 on .result, enforcing no line height for markers. Then, we add a div to wrap the rest of the result (.result-content), with a rule that sets the line height to 1.2.
Side effects of this change:
I don't forsee any, but it's a pretty ugly workaround to accommodate a minor bug in a weird OS.
Developer
Accessibility

[x] ANDI or WAVE has been run in accordance to our guide.
[ ] This PR contains no changes to the view layer.
[ ] New issues flagged by ANDI or WAVE have been resolved.
[ ] New issues flagged by ANDI or WAVE have been ticketed (link in the Pull Request details above).
[x] No new accessibility issues have been flagged.

New ENV

[ ] All new ENV is documented in README.
[ ] All new ENV has been added to Heroku Pipeline, Staging and Prod.
[x] ENV has not changed.

Approval beyond code review

[ ] UXWS/stakeholder approval has been confirmed.
[ ] UXWS/stakeholder review will be completed retroactively.
[ ] UXWS/stakeholder review is not needed.

Additional context needed to review
This will get UXWS review, but if the code reviewer would like to do QA as well, it would be useful to confirm the changes on a few browsers on desktop and on an iOS device.
Code Reviewer
Code

[ ] I have confirmed that the code works as intended.
[ ] Any CodeClimate issues have been fixed or confirmed as
added technical debt.

Documentation

[ ] The commit message is clear and follows our guidelines
(not just this pull request message).
[ ] The documentation has been updated or is unnecessary.
[ ] New dependencies are appropriate or there were no changes.

Testing

[ ] There are appropriate tests covering any new functionality.
[ ] No additional test coverage is required.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.653%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
586

Relevant Lines:
594

💛  - Coveralls

Interesting... I wonder if our "CSS reset" settings might be expanded to cover things like this without breaking things badly:
https://github.com/MITLibraries/mitlib-style/blob/master/_assets/sass/global/_unsets.scss

Interesting... I wonder if our "CSS reset" settings might be expanded to cover things like this without breaking things badly: https://github.com/MITLibraries/mitlib-style/blob/master/_assets/sass/global/_unsets.scss

It would take some creativity. We might be able to do something like this:
li::before {
  line-height: 0
}
li::after {
  line-height: 1 /* or whatever */
}

@JPrevost Could you confirm that the two recently pushed commits address the issue? I'd moved the padding down a level in the markup so the hover/focus rule would include it, but in retrospect I should've just moved the hover/focus rule up a level.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.653%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
586

Relevant Lines:
594

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.653%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
586

Relevant Lines:
594

💛  - Coveralls

Approved by UXWS this morning. Merging now.


Not getting a short-code email?

Was learning to code on FCC a few years ago, liked it. Been on the mailing list ever since, too. Trying to login again and I'm not getting an email with a short code. It's not in the spam folder, I've checked. Any suggestions?
Thanks in advance!

Can you check if you are getting any errors on your browser's dev console? You can look up the instructions to do so on Google based on the OS and the browser that you have.


Language localStorage support and new UI

[ ] Support saving language selection to localStorage.
[ ] Implement new design.
[ ] Compare and complete new translations for both Chinese files.
[ ] Add simple onMissingTranslation fallback.
[ ] Add help and lang switcher to all login/recover pages (when user is not logged in).

2 features need other solutions which we can do in future version:

Parcel doesn't support Dynamic Imports with variables which should be supported to enable loading translation files dynamically. One solution is switching to Webpack.

For onMissingTranslation, because the translations will be loaded dynamically, it might make the logic complex to load different translations multiple times even users don't change languages. For now, the missing translations will just show translationID, e.g. setupLedgerSteps.header which is better than translations for xxx in Chinese not found.

One possible solution is using a build script to copy missing translations from English to other languages to make sure all strings have at least one translation.

Parcel doesn't support Dynamic Imports with variables which should be supported to enable loading translation files dynamically. One solution is switching to Webpack.

There are few different ways to workaround, let's not switch to webpack.

There can be wrapper which is something like this:

function getTranslations(lang) {
   switch(lang) {
   case 'en': return import('translations/en.json');
   case 'ru': return import('translations/ru.json');
   ...
   }
}

Nothing prevents us from doing explicit HTTP fetch to load translations instead of relying on bundler.

For onMissingTranslation, because the translations will be loaded dynamically, it might make the logic complex to load different translations multiple times even users don't change languages. For now, the missing translations will just show translationID, e.g. setupLedgerSteps.header which is better than translations for xxx in Chinese not found.

I think it's best to show English translation for missing translations.

Ok. I will try in another PR. At least this PR is feature and design completed, also translations completed. 🤗

@picturepan2 these changes look great! A few notes:

Can you remove the <select> focus outline color (white and blue)?
I like that you're showing the lang switcher in guest mode on desktop. Can you add it for mobile too? You can place it in the same spot (since there's no hamburger menu in guest mode).
Can you add a cursor: pointer to the lang switcher?
On mobile, can you please make the chevron icon on the right-side of the switcher a bit bigger? Please see design for reference.


Does not respect my target OS

I don't select any IOS related target but my build still fail saying I don't have the correct IOS sdk. Even if I remove them from the supported platform in the project. How can I skip that damn IOS compilation step?

I'm using unreal 5.3

Hi is there any news on this?

Although I have not yet determined the definite cause, I have corrected the formatting of the UAT argument as it may be incorrect.
It would be helpful if you could check if it works correctly in your environment as well.


Proposal: Dragonfly supports P2P based on Streaming to reduce disk IO

Backgrounds
Now the client of Dragonfly will random read and write disk multiple times during the downloading process.
For directly using dfget to download a file:

dfget random writes a piece into disk after downloading it
dfget server random reads the piece from disk to share it
dfget sequential reads the file from disk after downloading to do checksum

And for using dfdaemon to pull images, there're extra disk IO by Dragonfly:

dfdaemon sequential reads the file from disk to send it to dockerd

It's not a problem when the host has a local disk. But it will be a potential
bottleneck when the Dragonfly client runs on a virtual machine with a cloud disk, all the disk IO will become network IO which has a bad performance when read/write at the same time.
So a solution is needed to reduce the IO times generated by Dragonfly.
Idea
P2P Streaming is a P2P based on Streaming, which sends the data downloaded by using p2p pattern to the user directly, in order to achieve the purpose of reading and writing to disk as few as possible.
P2P Streaming Data Flow
This diagram describes the p2p streaming data flow.

Piece Data Cache stores the pieces' data in memory that can be shared to the other peers. A piece's data should be putted into this cache after downloading, and be evicted according to the LRU strategy when the cache is full.
StreamIO sends pieces' data to callers in ascending order of piece's number.
In the scenario of using dfdaemon to pulling images and others , the dfdaemon and dfget should be merged into one process that can reduce the time of starting dfget process.
Also dfget can be as an individual process to download files directly.

P2P Streaming Sliding Window
The P2P Streaming Sliding Window is designed to control the number of pieces of a file that can be scheduled and downloaded to avoid unlimited memory usage. This idea comes from tcp sliding window, but its minimal transmission unit is a piece not a byte.

Memory Cache is the Piece Data Cache to share pieces in the p2p network. The larger the cache, the higher the p2p transmission efficiency.

Great job! I am willing to help.

[ ]  start long live peerserver in dfdaemon
[ ]  move download logic in DownloadContext, change result type to http.Resonse
[ ]  use library to download piece instead of dfget binary
[ ]  supernode support generate taskID with http header range
[ ]  extract new Writer interface for ClientWriter
[ ]  new ClientStreamWriter that implement Writer to write download piece to stream instead of file
[ ]  ClientStreamWriter implement both io.ReaderCloser and io.Writer
[ ]  when register task to supernode，return file metadata, eg: file length, dfdaemon should request source directly

Hello @lowzj! I'd like to pick this up as part of GSoC.

Hi, @lowzj I would like to work on this as a part of ASoC2020. Could you guide with what is the current state of development since it appears it has been worked on by others as well?

Hi, @lowzj I would like to work on this as a part of ASoC2020. Could you guide with what is the current state of development since it appears it has been worked on by others as well?

It has multiple tasks. We provide one task of it for ASoC2020: optimizing the scheduling algorithm of supernode for p2p-streaming. You can work on it.

@lowzj
when this feature（p2p-streaming） will be ready，thx！


Add reporter compatible with CucumberStudio

First of all, thank you! In my opinion this is the best package for writing widget tests as well as integration tests using BDD in terms of organization, ease of use and speed. Great work!
I think a great improvement would be added support for cucumber compatible Reporters so we can upload the test results to CucumberStudio using scripts. Other similar packages have that, but they are not as organized or easy to work with in my opinion.

Thank you for the kind words!
I reviewed some of the popular BDD packages. It is easy for them to implement this reporting as they run tests themselves. The idea behind bdd_widget_test is to keep it just a "dumb" converter from Gherkin to Dart, so that the Dart lang ecosystem will take care of the rest (run tests, collect reports, etc).
I don't see a way to make bdd_widget_test generate such reports, but it may generate code that generates them. I see the value in such reports, but I need to investigate a bit more.
Thanks for the proposition!

I found an alternative, I will leave it here in case anyone else is searching for something similar.
I managed to get the desired behaviour by using this package along with junitreport and hiptest-publisher and a shell script.
The script does the following:

adds required permissions before executing the tests using adb shell pm grant APP_ID PERMISSION
exports the feature files from CucumberStudio into our project hiptest-publisher --config-file=integration_test/report/cucumber.conf --output-directory='integration_test/features' --test-run-id=TEST_RUN_ID --without=actionwords
runs the tests and writes the xml report with the command flutter test -d DEVIDE_ID --flavor FLAVOR integration_test/features/app_test.dart --reporter json | tojunit >integration_test/report/TEST-report.xml
pushes the report to CucumberStudio hiptest-publisher --config-file=integration_test/report/cucumber.conf --push integration_test/report/TEST-report.xml --test-run-id=TEST_RUN_ID --push-format junit


[WIP][Release] Verify 1.0.1 release candidate RC0

@github-actions crossbow submit verify-rc-source-* verify-rc-binaries-* verify-rc-wheels-*

Closing since 1.0.1 has been released.


r.exe

explore including r.exe or Rterm.exe or RScript.exe to do some simple excel imports/exports (and maybe more?)
we can wrap the syntax in PS heroes = read_excel("data/heroes_information.xlsx", skip = 2)
No excel required.

maybe in v3


The install tip will show again after reload window

VSCode Version: Code 1.15.1 (41abd21afdf7424c89319ee7cb0445cc6f376959, 2017-08-16T17:15:57.756Z)
OS Version: Darwin x64 16.6.0
Extensions:

Extension
Author (truncated)
Version

EditorConfig
Edi
0.9.4

vscode-docker
Pet
0.0.16

code-settings-sync
Sha
2.8.3

Angular2
UVB
0.4.1

string-converter
ada
0.0.9

Bookmarks
ale
0.16.0

markdown-preview-github-styles
bie
0.0.2

npm-intellisense
chr
1.3.0

open-html-in-browser
cod
0.1.21

gitignore
cod
0.5.0

vscode-eslint
dba
1.2.11

vscode-dash
dee
1.7.0

githistory
don
0.2.3

python
don
0.7.0

es7-react-js-snippets
dsz
1.1.0

gitlens
eam
4.4.3

tslint
eg2
0.17.0

vscode-npm-script
eg2
0.2.1

vscode-great-icons
emm
2.1.15

prettier-vscode
esb
0.23.1

vsc-travis-ci-status
fel
1.1.0

vscode-npm
fkn
3.3.0

vscode-auto-open-markdown-preview
hnw
0.0.4

webpack
jer
2.0.2

sublime-babel-vscode
jos
0.2.8

Go
luk
0.6.63

sublime-keybindings
ms-
2.9.1

debugger-for-chrome
msj
3.2.1

vscode-icons
rob
7.12.0

markdown-preview-enhanced
shd
0.2.8

sync-rsync
vsc
0.18.0

vscode-todo-highlight
way
0.5.11

webpack-progress
wk-
0.0.8

JavaScriptSnippets
xab
1.4.1

(7 theme extensions excluded)

Steps to Reproduce:

click install button on the store page, like https://marketplace.visualstudio.com/items?itemName=joshpeng.theme-charcoal-oceanicnext
back to vscode will see the tip of install the plugin and the store page
close the tips and the page, reload the window, or just click the install button then reload, the tip and the store page will show again

Reproduces without extensions: Yes

@ZxBing0066
Can you share screenshot of the tips and the store page you are seeing in vscode?

I have clicked the install button, and close the store page, but when I reload the window, this will show again.

Do you see this with other extensions as well?
Try installing any other extension.

Open marketplace

Click install

Show tips in the vscode

Close the tips

Reload windows

The tips show again

This is very easy to Reproduce

Thanks @ZxBing0066
I kept installing the extension and so couldn't repro.

The root cause for this is same as that for #34404
Closing this in favor of #34404


Matching Two Fields from examples is not working as expected

Here is my code: https://stackblitz.com/edit/angular-n6foes-jwpy5g
It's modified from sample code (https://formly.dev/examples/validation/matching-two-fields).  I made the modification to get rid of fieldGroup and the resulting nesting object.  However, the expected error msg 'These fields must match' was never triggered.  Although debugging indicates that the custom validator code passwordFieldMatch runs without any issue, the error was set properly.
Of course, when I used fieldGroup and nesting object, it's working: https://stackblitz.com/edit/angular-n6foes-cprrrs.  But I don't really want a fieldGroup.

duplicate of #2255

This issue has been fixed and released as part of v5.7 release. Check our demo example https://formly.dev/examples/validation/matching-two-fields
Please let us know, in case you are still encountering a similar issue/problem.
Thank you!


Publish to helm repo?

Is it on the roadmap to publish this chart to https://github.com/helm/charts? So far I have been installing my charts using requirements.yaml, but there doesn't currently seem to be a way to do that with this repo.

We haven't thought about it yet. Can you briefly explain what you mean with that you install your charts using requirements.yaml and what are the advantages of doing so?

You may refer to Helm documentation on this
https://helm.sh/docs/developing_charts/#chart-dependencies
Helm recommendation is to use dynamically linked subchart dependencies if possible through requirements.yaml. It's a little more declarative about what your chart is depending on. This is similar to other package management systems like npm or maven.
Also, it makes this chart a little more discoverable, as it will show up in the helm chart repo browser over at https://hub.helm.sh/

Got it, thanks! Yeah, I think it might be a good idea. Would you like to contribute?

I have published the repo in https://github.com/prometheus-msteams/helm-chart.
helm repo add prometheus-msteams https://prometheus-msteams.github.io/helm-chart/


Fix reporting typo/bug when all subjects have no sex or age

During @coltonlw's testing he unearthed a typo here:
https://github.com/scitran/core/blob/master/api/handlers/reporthandler.py#L61
Also, if all the subjects that have an _id do not have the sex or age field, the aggregations will fail.

hello, i'm new to open source, can i solve this? could you guide me?

This was fixed as part of the integration testing overhaul.


Positional and Spatial Mapping Python

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues.
[X] This issue is not a question, bug report, or anything other than a feature request directly related to this project.

Proposal
Is there any tutorial or example, or has anyone already done a project in python capable of doing exactly what is in the SLAM video of the zed2i stereolabs page? Thanks!
https://cdn2.stereolabs.com/assets/video/zed-spatial-mapping-point-cloud.mp4
Use-Case
Positional and Spatial Mapping in python to do a slam. Not just a mesh
Anything else?
No response

Please refer to the Spatial Mapping examples in this repository:
https://github.com/stereolabs/zed-sdk/tree/master/spatial mapping


Docker compose: add MariaDB & minio images

This is required for dev as we currently can't even load fixtures in dev env :/

Thanks ! :)


Don't support << or >> shift operations in move language.

public fun wrapping_add(num1: I32, num2: I32): I32 {

    let sum = num1.bits ^ num2.bits;
    let carry = (num1.bits & num2.bits) << 1;
    while (carry != 0) {
        let a = sum;
        let b = carry;
        sum = a ^ b;
        carry = (a & b) << 1;
    };
    I32 {
        bits: sum
    }
}

test with
move prove will generate the following errors, which block the whole test...
[internal] boogie exited with compilation errors:
output.bpl(20982,4): Error: call to undeclared procedure: $ShlBvBv32From8
output.bpl(21106,4): Error: call to undeclared procedure: $ShlBvBv32From8
output.bpl(22201,4): Error: call to undeclared procedure: $ShlBvBv128From8
output.bpl(22241,4): Error: call to undeclared procedure: $ShrBvBv128From8
output.bpl(22274,4): Error: call to undeclared procedure: $ShrBvBv128From8
output.bpl(22591,4): Error: call to undeclared procedure: $ShlBvBv128From8
output.bpl(22715,4): Error: call to undeclared procedure: $ShlBvBv128From8
output.bpl(26766,4): Error: call to undeclared procedure: $ShlBvBv8From8
output.bpl(26786,4): Error: call to undeclared procedure: $ShrBvBv128From8
output.bpl(26819,4): Error: call to undeclared procedure: $ShlBvBv8From8
output.bpl(26839,4): Error: call to undeclared procedure: $ShrBvBv128From8
output.bpl(26872,4): Error: call to undeclared procedure: $ShlBvBv8From8

maybe, do not dive deep to check this, I found  pragma opaque; can skip this functions, so just skip first.


Would it be easy/possible to include faster than x2?

@RyanGaudion Yes, certainly. I'll need someone to get to it though. Can't devote time at the moment.

@RemLampa Can you review on this PR https://github.com/RemLampa/facebook-video-speed-control/pull/22

@RyanGaudion Feature is available now on Chrome Web Store as version 0.2.1!
@lawdalana Thanks so much for your help!


Update quick_settings.dart

Fix poweroff issue from developer.dart, but put it in quicksettings.

Why not merge it?
On Sat, Sep 19, 2020, 4:32 PM Lucas Puntillo<EMAIL_ADDRESS>wrote:

Closed #100 https://github.com/dahlia-os/pangolin-desktop/pull/100.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dahlia-os/pangolin-desktop/pull/100#event-3785600202,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEOTEHEYPTT326G7TE5VMODSGU5STANCNFSM4QU3XKGQ
.

Hm, i was just clearing out old prs and i accidentally closed this one, so i made a new one.

I will reopen and close the new one.

wait, not needed

Already implemented, ill close now.


DSL for creating request / response mappings dynamically

Sometimes you may not want to import service data, and instead might want to be able to create it programatically.  This could be done by a DSL which lets you build expected requests and responses.

There's actually a few things to consider when designing this DSL.
Do we want to retain the separation between URL components?  So for example, when building we could have something along these lines:
get("https://www.host.com/path?queryParam=foo").willReturn(...)
But this abstracts away the separation of url components as stored in the JSON:
{
    "scheme" : "http",
    "destination" : "www.host.com",
    "path" : "/path",
    "query" : "?queryParam=foo"
}

But maybe this makes sense as it's quite expressive, so internally we could transform things but expose a method which let's us supply things as a full URL.

I also think the DSL should follow what people would generally do, so @tommysitu idea of starting with a verb, followed by URL makes sense:
verb(url)
Then you can optionally do:
verb(url).withBody(body).withHeader(key, value)

@danielbryantuk @tommysitu @benjih

@mogronalol some good comments there. The design choice to have service("host.com") as a top element is to make it more microservices testing oriented, and be able to chain multiple services to build simulation data:
hoverflyRule.simulate(
     service("foo.com")
          .get(path("/firstPath?query=foo")).willReturn(...)
          .post(path("/secondPath").body(body)).willReturn(...)
     .anotherService("bar.com")
           .get(path("/firstPath?query=bar")).willReturn(...)
)

We've gone done this route:
The rule is fluent and hierarchical, allowing you to define multiple service endpoints as follows:
hoverflyRule.setSimulation(
    service("www.my-test.com")

        .post("/api/bookings").body("{\"flightId\": \"1\"}")
        .willReturn(created("http://localhost/api/bookings/1"))

        .get("/api/bookings/1")
        .willReturn(success("{\"bookingId\":\"1\"\}", "application/json"))

    .anotherService("www.other-anotherService.com")

        .put("/api/bookings/1").body("{\"flightId\": \"1\"\"}")
        .willReturn(success())

        .delete("/api/bookings/1")
        .willReturn(noContent())

The entrypoint for the DSL is HoverflyDSL.service.  After calling this you can provide a method and path, followed by optional request components.
You can then use willReturn to state which response you want when there is a match, which takes responseBuilder object that you can instantiate directly,
or via the helper class responseCreators.


Difficult to see trip pattern stops as they can be hidden by unselected stop layer

(when there are duplicate stops)

Unfortunately leaflet layer ordering is not well defined, so this will be difficult to fix. The smaller icons may have helped though.


Versions page does not link back to versioned docs

🐛 Bug Report
The /versions page shows a list of versions, but "Documentation" and "Release Notes" links are not working. On the browser, they are linking back to the same page (/versions).
Also, the documentation does not have any reference to where "Release Notes" are stored. Are they expected to be a tag in Github or can we have an actual doc published elsewhere or another static page/doc within docusaurus.
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce

Run the following script to generate a starter versions page listing all the site versions: yarn examples versions
This creates the pages/en/versions.js file.
Run the script with a command line argument of the version you wish to create. e.g.: yarn run version 1.0.0
Start the server: yarn start
Visit the site on your local host: http://localhost:3000/en/versions
Try the "Documentation" and "Release Notes" link

Expected behavior

Clicking on the "Documentation" link would take me to the pages that are created when clicking on the Docs link from the top navigation bar.
Not sure what to expect from the "Release Notes" link because I can't find any related configurations in previous steps or in siteConfig.js
Actual Behavior

Neither links (Documentation, Release Notes) are valid. They refer to the same page (/versions). I did notice that the generated /pages/en/versions.js file contains empty href attribute. Am I expected to manually fill-in this information? If yes, that is okay with me, but I didn't see it mentioned anywhere in the docs.

Current version (Stable)

                {latestVersion}

                  Documentation

                  Release Notes

Reproducible Demo
(Paste the link to an example repo, including a siteConfig.js, and exact instructions to reproduce the issue.)
I'm sorry I don't have an example repo to share with you as I'm working with an internal/private repo. Here's a copy of the siteConfig.js. I followed the steps in the docs to prepare the site.
/**
 * Copyright (c) 2017-present, Facebook, Inc.
 *
 * This source code is licensed under the MIT license found in the
 * LICENSE file in the root directory of this source tree.
 */

// See https://docusaurus.io/docs/site-config for all the possible
// site configuration options.

// List of projects/orgs using your project for the users page.
const users = [
  // You will need to prepend the image path with your baseUrl
  // if it is not '/', like: '/test-site/img/docusaurus.svg'.
  {
    caption: 'Garmin',
    image: '/img/customers/garmin_logo.png',
    infoLink: 'https://www.garmin.com/en-CA',
    pinned: true,
  },
  {
    caption: 'Herschel',
    image: '/img/customers/herschel-logo.png',
    infoLink: 'http://www.herschelsupply.ca/',
    pinned: true,
  }
];

const siteConfig = {
  title: 'Developer Center', // Title for your website.
  tagline: 'Documentation for Elastic Path Commerce',
  url: 'https://your-docusaurus-test-site.com', // Your website URL
  baseUrl: '/', // Base URL for your project */
  // For github.io type URLs, you would set the url and baseUrl like:
  //   url: 'https://facebook.github.io',
  //   baseUrl: '/test-site/',

  // Used for publishing and more
  projectName: 'test-site',
  organizationName: 'ep',
  // For top-level user or org sites, the organization is still the same.
  // e.g., for the https://JoelMarcey.github.io site, it would be set like...
  //   organizationName: 'JoelMarcey'

  // For no header links in the top nav bar -> headerLinks: [],
  headerLinks: [
    {doc: 'setup/index', label: 'Docs'},
    {doc: 'ref-exp-vestri/overview', label: 'Reference Experience'},
    {page: 'help', label: 'Help'},
    // {blog: false},
    // {search: true},
    //link to elastic path home page
    // { href: 'https://www.elasticpath.com/', label: 'Elastic Path'},
    //link to elastic path gitlab
    // { href: 'https://code.elasticpath.com/', label: 'GitLab' },
  ],

  // If you have users set above, you add it here:
  //users,

  /* path to images for header/footer */
  headerIcon: 'img/elastic-path-logo.svg',
  footerIcon: 'img/elastic-path-logo.svg',
  favicon: 'img/favicon/ep.ico',

  /* Colors for website */
  colors: {
    primaryColor: '#00A3DD', //'#2E8555',
    secondaryColor: '#0718c2', //'#205C3B',
  },

  /* Custom fonts for website */
  /*
  fonts: {
    myFont: [
      "Times New Roman",
      "Serif"
    ],
    myOtherFont: [
      "-apple-system",
      "system-ui"
    ]
  },
  */

  // This copyright info is used in /core/Footer.js and blog RSS/Atom feeds.
  copyright: `Copyright © ${new Date().getFullYear()} Elastic Path`,

  highlight: {
    // Highlight.js theme to use for syntax highlighting in code blocks.
    theme: 'default',
  },

  // Add custom scripts here that would be placed in