Create directory in database root fails with "Directory is read-only"

Expected Result
When attempting to create a directory in the database root, Datakit should respond to without error.
Actual Result
Datakit responds with Rerror, Directory is read-only
Information
Discovered this while writing C# bindings for Datakit.
When you attempt to create a directory in the database root, branch in this example, Datakit will respond with an Rerror message claiming that the Directory is read-only
+4968us Datakit     Starting com.docker.db...
+5041us Datakit    [DEBUG] Using Git-format store "/data"
+5516us irmin-io   [DEBUG] mkdir /data/.git
+5727us irmin-io   [DEBUG] mkdir /data/.git/tmp
+6009us irmin-io   [INFO] Writing /data/.git/HEAD (/data/.git/tmp/HEADd54231write)
+6405us vgithub    [DEBUG] Datakit does not use the Github bindings
+6580us Datakit    [DEBUG] Waiting for connections on socket "tcp://<IP_ADDRESS>:5640"
+101477671us Datakit    [DEBUG] New unix client
+101477709us ivfs-remote [DEBUG] create
+101485531us fs9p       [DEBUG] C ((tag (0))
                                    (payload
                                     (Version
                                      ((msize 16384) (version TwoThousand)))))
+101485591us fs9p       [DEBUG] S ((tag (0))
                                    (payload
                                     (Version
                                      ((msize 16384) (version TwoThousand)))))
+101485685us fs9p       [INFO] Using protocol TwoThousand msize 16384
+101490338us fs9p       [DEBUG] C ((tag (1))
                                    (payload
                                     (Attach
                                      ((fid 1) (afid 0) (uname Dave)
                                       (aname /) (n_uname ())))))
+101490396us fs9p       [DEBUG] S ((tag (1))
                                    (payload
                                     (Attach
                                      ((qid
                                        ((flags (Directory)) (version 0)
                                         (id 5)))))))
+101494532us fs9p       [DEBUG] C ((tag (2))
                                    (payload
                                     (Walk ((fid 1) (newfid 2) (wnames ())))))
+101494581us fs9p       [DEBUG] S ((tag (2)) (payload (Walk ((wqids ())))))
+101495497us fs9p       [DEBUG] C ((tag (3))
                                    (payload
                                     (Walk ((fid 2) (newfid 3) (wnames ())))))
+101495527us fs9p       [DEBUG] S ((tag (3)) (payload (Walk ((wqids ())))))
+101497487us fs9p       [DEBUG] C ((tag (4))
                                    (payload
                                     (Create
                                      ((fid 3) (name branch)
                                       (perm
                                        ((owner (Read Write Execute))
                                         (group (Read Execute))
                                         (other (Read)) (is_directory true)
                                         (append_only false)
                                         (exclusive false) (is_mount false)
                                         (is_auth false) (temporary false)
                                         (is_device false) (is_symlink false)
                                         (is_hardlink false)
                                         (is_namedpipe false)
                                         (is_socket false) (is_setuid false)
                                         (is_setgid false) (is_any false)))
                                       (mode
                                        ((io Read) (truncate false)
                                         (rclose false) (append false)))
                                       (extension ())))))
+101497586us fs9p       [DEBUG] S ((tag (4))
                                    (payload
                                     (Err
                                      ((ename "Directory is read-only")
                                       (errno ())))))

As you can see, a subsequent Walk and Create operations within the branch directory DO succeed...
+101515630us fs9p       [DEBUG] C ((tag (5)) (payload (Clunk ((fid 3)))))
+101515671us fs9p       [DEBUG] S ((tag (5)) (payload (Clunk ())))
+101516094us fs9p       [DEBUG] C ((tag (6))
                                    (payload
                                     (Walk
                                      ((fid 2) (newfid 2) (wnames (branch))))))
+101516133us fs9p       [DEBUG] S ((tag (6))
                                    (payload
                                     (Walk
                                      ((wqids
                                        (((flags (Directory)) (version 0)
                                          (id 4))))))))
+101516351us fs9p       [DEBUG] C ((tag (7))
                                    (payload
                                     (Walk ((fid 2) (newfid 4) (wnames ())))))
+101516386us fs9p       [DEBUG] S ((tag (7)) (payload (Walk ((wqids ())))))
+101516688us fs9p       [DEBUG] C ((tag (8))
                                    (payload
                                     (Create
                                      ((fid 4) (name master)
                                       (perm
                                        ((owner (Read Write Execute))
                                         (group (Read Execute))
                                         (other (Read)) (is_directory true)
                                         (append_only false)
                                         (exclusive false) (is_mount false)
                                         (is_auth false) (temporary false)
                                         (is_device false) (is_symlink false)
                                         (is_hardlink false)
                                         (is_namedpipe false)
                                         (is_socket false) (is_setuid false)
                                         (is_setgid false) (is_any false)))
                                       (mode
                                        ((io Read) (truncate false)
                                         (rclose false) (append false)))
                                       (extension ())))))
+101516792us fs9p       [DEBUG] S ((tag (8))
                                    (payload
                                     (Create
                                      ((qid
                                        ((flags (Directory)) (version 0)
                                         (id 13)))
                                       (iounit 0)))))

I've verified the same behaviour with @djs55's Go bindings so I think this is likely a problem with Datakit...
This is the same whether running over a named pipe (on Windows) or over TCP to Datakit running in a Linux container.

Isn't this correct? The root is read-only, and /branch already exists. Is the bug that we should return File exists rather than Directory is read-only?

Maybe? It wasn't clear to me that the root was RO, but now I know! Thanks!
It didn't help matters that from the filesystem, ls didin't show a branch directory and that mkdir branch would also complete without error.
As for the error message, yes I'd expect File Exists before Directory is read-only.
What I'd like is a safe way for a client to handle certain types of error.
In the mkdir -p example. it's okay if part of the path exists and I can safely ignore the error.
It is however, not ok to ignore other errors e.g No space left on device for example.
It seems the documentation is scare for error strings... I'm not really fond of pattern matching error strings to determine the "kind" of error either :sob: but I think it's the best we can do with the protocol as it stands. Open to other ideas though...

Why didn't ls show it? It does with the Linux and OCaml clients, at least:
/Database # ls
branch     remotes    snapshots  trees
/Database # mkdir branch
mkdir: can't create directory 'branch': File exists

I guess Linux is adding the File exists here because ocaml9p shows the protocol message:
tal@Thomass-MacBook-Pro ~> ocaml9p shell
9P > ls
drwxrwxr-x ? root root 0 Jan 1 1970 branch
drwxrwxr-x ? root root 0 Jan 1 1970 trees
drwxrwxr-x ? root root 0 Jan 1 1970 snapshots
drwxrwxr-x ? root root 0 Jan 1 1970 remotes
9P > mkdir branch
Directory is read-only

BTW, this is the best documentation I could find for the 9p protocol's errors:
http://lxr.free-electrons.com/source/net/9p/error.c

Closing, as I don't think there's anything to fix here. Linux reports "file exists" rather than "read only" because it checks whether the directory exists before calling mkdir, and you can do that too if you want. Please reopen if you disagree.

Nope, I think this was probably user error ;)
The mkdir thing I mentioned was user error - I was using the host filesystem.
Happy to help adding some docs :D

More docs are always welcome :-)


chore: 🤖 use respective language code for each book

The search functionality didn't change with this implementation so closing it.


defineProps seems to ignore props marked as optional and requires them anyway when using TypeScript tooling

Version
3.2.31
Reproduction link
stackblitz.com
Steps to reproduce
Create a new project using the following command:
$ npm create vite@latest
$ npm install

Use Vue and TypeScript.
Then, create a new component CustomComponent.vue (the name doesn't really matter) with the following content:
<script setup lang="ts">
const $props = defineProps({
  text: {
    type: String,
    required: true,
  },
  optional: {
    type: String,
    required: false,
    default: 'this is not required'
  },
});
</script>

<template>
  {{ $props.text }}
</template>

Now, when importing the component into another component, omitting the non-required prop will cause a type error.

Notice that this doesn't happen when using the Options API, only when using script-setup:
<script lang="ts">
import { defineComponent } from 'vue';

export default defineComponent({
  name: 'CustomComponent',
  props: {
    text: {
      type: String,
      required: true,
    },
    optional: {
      type: String,
      required: false,
      default: 'this is not required'
    },
  },
});
</script>

<template>
  {{ text }}
</template>

What is expected?
The TypeScript tooling should recognize that the optional prop is not required.
What is actually happening?
The TypeScript tooling seems to think that the optional prop is required.

This doesn't seem to be an issue when defining props with the interface syntax:
<script setup lang="ts">
const $props = defineProps<{
  text: string,
  optional?: string,
}>();
</script>

<template>
  {{ $props.text }}
</template>

However, when using the withDefaults compiler macro with the interface syntax, the exposed interface once again seems to ignore some values are marked as optional:
<script setup lang="ts">
const $props = withDefaults(defineProps<{
  text: string,
  optional?: string,
}>(), {
  optional: 'this is optional',
});
</script>

<template>
  {{ $props.text }}
</template>

I should point out that the compilation process itself works fine. It just seems to be the tooling that's failing randomly.

Hm, this seems to be related to the variable name you chose. $props is a Vue component instance property, and it seems it's somehow confusing Volar. Changing it to const props fixed the issues, changing it back made them reappear.
this issue should likely be moved to the Volar repo: https://github.com/johnsoncodehk/volar


Add benchmark on collection load time

Add new column collection_load_time_ms to benchmark table
Introduce BENCHMARK_STRATEGY variable to control the flow of the workflow (default | tenants | collection-load)
Only push telemetry data into Postgres if BENCHMARK_STRATEGY is set to collection-load

Right now the dataset under test is random-768-100-tenants

I updated Grafana dashboard:

Example run: https://github.com/qdrant/vector-db-benchmark/actions/runs/10898524497

Let's have this benchmark in a separate repo.


Fix a logic-changing typo in getRecursionIdentity

There is currently a typo bug in the getRecursionIdentity function that changes the logic of the function in an unexpected way. This PR fixes that bug.
Please verify that:

[x] There is an associated issue in the Backlog milestone (required)
[x] Code is up-to-date with the main branch
[x] You've successfully run hereby runtests locally
[ ] There are new or updated unit tests validating the change - there is no new functionality added, this PR fixes a small (1 character) logic mistake in the existing code

Fixes #54320

@typescript-bot test this
@typescript-bot test top100
@typescript-bot user test this
@typescript-bot run dt
@typescript-bot perf test this faster

There are new or updated unit tests validating the change - there is no new functionality added, this PR fixes a small (1 character) logic mistake in the existing code

Of course this is a bug either way, but ideally there would be a regression test… does this observably change the behavior of any TS code?

There are new or updated unit tests validating the change - there is no new functionality added, this PR fixes a small (1 character) logic mistake in the existing code

Of course this is a bug either way, but ideally there would be a regression test… does this observably change the behavior of any TS code?

The problem is that I stumbled upon this completely by accident while reading the source trying to understand how the infinite recursion prevention mechanism works (because my fork was infinitely recursing :sweat_smile:). In other words I currently do not understand this part of the code base well enough to know with certainty what functionality this bug may affect. If there is a noticeable effect for the end user then it was in any case not covered by existing unit tests as these pass without any modification.
I can tell you however that the bug is currently mostly masked by the additional condition right after it: && (type as TypeReference).node. This extra check significantly narrows down the types that could end up in this conditional branch. After looking at the existing Type classes there are only 3 that include this property and thus could possibly end up in this branch:

TypeReference
DeferredTypeReference
InstantiationExpressionType

The first 2 are obviously fine as they are the types that are supposed to end up in that branch, just the last one needs to be verified.


Handle errors in loadData method

Avoid crashing the app if the json file doesn't load via the loadData method.
If we don't get a 200 status, we return with a app.loader.error.
This way we don't parse something nonexistent.

On a sidenote,
I couldn't create the zip files with the build.
Can you help me with the build process @rezoner.
I guess that you're on a mac because I couldn't find a zip command for windows.
Awesome framework :+1:

Thanks for your quick answer.
For the contribution, it wasn't about adding new features, I totally agree with you on the plugin's architecture, the simpler it stays, the better it will be.
The plugin API is simple and easy enough. Don't really need more.
I've already made one. To allow persistence.
It's AMD and global wise. I was about to publish it on bower.
Are you ok if I proceed like that ?

I haven't yet decided what's the most optimal way to avoid conflicts in plugin ecosystem and how to share them with public - but bower looks to be widely used solution. And THREE.js which is a reference for me also supports it.
I would appreciate if you could post your plugin somewhere, so I could examine how it looks from the end-user point of view.
Sorry for my ignorance, I am a bit lost in this endless jungle of precompilers and packagers - npm, babelify, browserify, bower, yeoman.....

There is no problem. I'll share with you a link soon enough.
It'll be on github, and published on bower and probably on npm too.
I think you should maybe consider doing the same for your framework.
If you need I can prepare it for you (in a PR), and you'll just have to launch the publish command to auth them with your name.

here is the plugin https://github.com/yoannmoinet/playground.memorycard
It's published on npm and bower.


[Bug] NgDocTypeAlias doesn't work as described in the docs

Is this a regression?
I don't know
Description
In the docs there is example of a custom list type usign NgDocTypeAlias
color: {
  type: 'NgDocTypeAlias',
  options: ['primary', 'secondary', 'success', 'danger']
},

which doesn't render any options when you try to open the dropdown with the options.
After a couple of hours of investigation it seems like here is the problem. A string passed in NgDocExtractValuePipe which then passed it into extractValue which returns an empty string because
new Function('return danger')()

throws an error. If the option strings passed with quotes
options: ["'primary'", "'secondary'", "'success'", "'danger'"],

then it starts working.
Please provide the exception or error you saw
No exceptions. The dropdown list doesn't open quietly. I mean, it opens but without options which turns out it to be empty.

OS
Unix (Linux, macOS, etc.)
Browser
Chrome
Node version
20
Anything else?
No response

Thanks for the ticket! Yep this is a regression of NgDoc18.
The documentation is correct, and you should not use quotation marks. They are necessary only to resolve simple types, but when you specify values for the control yourself, everything should work as usual.

:tada: This issue has been resolved in version 19.1.0 :tada:
The release is available on:

v19.1.0
GitHub release

Your semantic-release bot :package::rocket:


Render multiple newlines

If the text contains multiple newlines
Hello\n\n\nThere

then only one newline was rendered. So I tried this approach to solve this
var converter = new showdown.Converter(),
  description = data.description.replace(/\n{2,}/g, m => m.replace(/\n/g, "
"));
description = description.replace(/
([^<])/g, "
\n\n$1");
var html = converter.makeHtml(description);

But the problem with the above solution is if the markdown contains codeblock then
 tags get render inside the codeblock is there better a way to solve this?

This is definitely a major bug in showdown, since it really messes up Markdown input with its aggressive removal of blank lines.
Even though this issue is a few years old, I'll share my workaround, since I'm sure others will run into this issue even if it's too late for the OP. I haven't tested this extensively yet and adjustments may be needed depending on your particular use case and what flavor of markdown you're using, but I ended up using this regex replacement:
markdown.replace(/(?<=\n)\n/g, '  \n').replace(/(?<= {2})\n(?=---)/g, '\n\n');

The first replacement value is a soft hyphen (U+00AD) followed by two spaces and a newline. You might be able to use a nonbreaking space instead of the soft hyphen, but in my case it was getting converted to   and then getting rendered as &nbsp;, possibly due to the showdown-htmlescape extension or possibly from the application where the HTML is being rendered.
Basically, it replaces all blank lines with a line containing a soft hyphen, so it will visually appear like a blank line. One issue this causes is that if you copy from a code block and paste, the soft hyphen will be copied. To fix this, assuming there's no reason for a soft hyphen to appear in your input Markdown, you can just remove them from the HTML after converting (and I suppose at that point you can substitute any unicode string you don't think would appear in the input).
html.replace(/ ? ?/g, ''); // First character of the RegExp is a soft hyphen

The second replace on the markdown input (in the first code sample) handles the edge case of a
 made up of hyphens (like ----). If you have text on a line before a horizontal rule, it gets rendered as a heading, so instead of a horizontal rule, I was getting headings containing a soft hyphen. This solves the problem by looking at all non-first newlines prior to a row of three or more hyphens (now identifiable by the soft hyphen we inserted) and replacing them with a double newline. Showdown will use the double newline to recognize it as a horizontal rule instead of a title, then reduce it to one line, leaving us with the original number of lines.
In my limited testing, I've found this to give the results I want.


Look into minimizing issues arising from different settings in launch.json compared to settings.json

We have a number of issues arising from users setting different python path values in settings.json and launch.json

Explore possibility of displaying a warning indicating the values are different
Same could apply to environment file and others

This warning message could be turned off (do not show again).
Would help people changing paths in launch.json in repos or code samples and trying to figure why things don't work out why a different interpret if used).
Avoids confusions (amongst novice users).
@brettcannon @qubitron

Duplicate of #2929


How about not tracking dist in VCS?

I feel against tracking build artifacts in VCS.

prepublishOnly npm event is probably the right place to generate the dist directory


test: oci package

Description
Unit testing OCI
Related Issue
Fixes #2332
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[X] Other (security config, docs update, etc)

Checklist before merging

[ ] Test, docs, adr added or updated as needed
[ ] Contributor Guide Steps followed

note for myself to remember to make sure is here:
when publishing, ensure that pkg.Build.Metadata.Architecture == platform.Architecture

Closed as the unit tests were implemented at https://github.com/defenseunicorns/pkg


Documentation site does not load properly when baseUrl is "/"

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
Hi,
When baseUrl is set to "/", and I'm building the website on gh-pages, the CSS does not load properly and an error message suggests that I use /docs/ as baseURL.
Reproducible demo
No response
Steps to reproduce
This does not happen in a local environment.
See this commit for more details
https://github.com/doc4d/docs/commit/aeb0799eff7b5b92c409839b18de3e607537c015
Expected behavior
The site builds correctly
Actual behavior
The site displays an error message

I have to use /docs/ as baseURL to get the site to load properly, but I shouldn't have to (URLs become doc4d.github.io/docs/docs, not an efficient URL).
Your environment

Public source code:
Public site URL:
Docusaurus version used:
Environment name and version (e.g. Chrome 89, Node.js 16.4):
Operating system and version (e.g. Ubuntu 20.04.2 LTS):

Self-service

[ ] I'd be willing to fix this bug myself.

I have to use /docs/ as baseURL to get the site to load properly, but I shouldn't have to

Yes you should
The site is hosted on /docs/ baseurl, so as documented in the gitHub deployment doc, and as the error message suggest, you raally have to use that baseUrl in your site config.

(URLs become doc4d.github.io/docs/docs, not an efficient URL).

I don't know what you mean by "not efficient URL, but /docs/docs is a perfectly fine URL:

GitHub pages uses /repoName/ by default as a baseUrl (unless you use an organization): you can name your repo something else than "docs" if you want something else
Docusaurus docs use /docs/ as prefix for all docs, but you can rename or replace it by /

Note: In theory, /docs/docs is perfectly valid. In practice we have a bug with /docs/docs, and so you should avoid that, see https://github.com/facebook/docusaurus/issues/6294
I'd advise you to name your github repo something else than "docs", or using a better host like Vercel/Netlify.


Misleading status "Certificate is Valid" when country has no rules

Avoid duplicates

[X] Bug is not mentioned in the FAQ
[ ] Bug is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
[ ] Bug is not already reported in another issue
Bug has been reported for a specific case (Italy) in https://github.com/corona-warn-app/cwa-app-android/issues/3922

Technical details

Device name: Samsung Galaxy A5 (2017) SM-A520F
Android version: 8.0.0
App version: 2.6.1

Describe the bug
If there are no Business Rules defined for a certain Country of Arrival and any certificate is stored in CWA then "CHECK VALIDITY" always succeeds with the message:
"Your certificate is valid in the selected country"
(validation_rules_result_valid_result_title)
Although this is followed by the text
"There are currently no entry rules for the selected country and selected time for this certificate type. Please note the following:"
validation_no_rules_available_valid_text
the title is in bold case and larger case than the following text, so the title may be wrongly interpreted that the certificates were validated successfully, even though there was nothing to validate them against.
Steps to reproduce the issue

Tap the Certificates tab, tap "+ CERTIFICATE"
Scan in a valid 1/2 vaccination certificate (i.e. for a vaccination of an incomplete series)
Tap "CHECK VALIDITY"
Select a country which does not yet have Business Rules defined, e.g. Italy
Tap "CHECK"
Note the message "Your certificate is valid in the selected country" followed by "There are currently no entry rules for the selected country ..."

Expected behavior
If there are no Business Rules available for a Country of Arrival then the app should not claim that the certificate is valid, since there is no proof of this being the case.
Possible Fix
Output a different status message when checking certificate validity when no Business Rules are available for a certain Country of Arrival, such as:
"Your certificate could not be validated for the selected country"
Additional information
If this issue also occurs on iOS it should be transferred to the cwa-documentation repository.
Internal Tracking ID: EXPOSUREAPP-8826
Internal Tracking ID: EXPOSUREAPP-8785 related

Closely related to https://github.com/corona-warn-app/cwa-documentation/issues/678

@Ein-Tim
Not only closely related. It's a duplicate. Thanks for your input. Now closing!

This (duplicate) issue is resolved by CWA 2.8, see announcement https://www.coronawarn.app/en/blog/2021-08-25-cwa-version-2-8/
"... In addition, the project team has adapted the EU certificate check. If a country has not provided any entry rules that the Corona-Warn-App can use for checking, the certificate check will state that the certificate cannot be validated. The countries that are listed under the certificate check in the Corona-Warn-App generally recognize the certificates. However, depending on the country and the applicable rules, the relevant certificate (on its own) may not authorize entry.
Previously, the app indicated in this case that the certificate is valid in the selected country. In the text below, however, it was pointed out that there are currently no entry rules available for the selected country. With version 2.8, users can clearly see that the certificate's validity could not be checked because the relevant country has not defined any entry rules."

Indeed, this was fixed in 2.7.

Corona-Warn-App Open Source Team


make Request::rest public outside of the crate

closes #426

You can use app.all to match everything:
app.at("*").all(endpoint);

Is there still something missing?

This is a different concern.  Sorry I was unclear. Within a route handler with a "/nested/*" route, how do I get access to the entirety of the globbed part?

Haven't quite understood your problem, but maybe you're aiming for /nested/*path which will give you the rest of the request path under /nested/ in a path param. You can then get it as any other param with req.param("path")....

As I mentioned in the issue, the param parser supports unnamed star globs, and they’re also mentioned in the tide docs, and as far as I can tell, tide stores them and has a method that is unused within the crate which does exactly this, but is pub(crate).

Perhaps the solution is just to remove mention of unnamed globs from the docs, also the rest method and --tide-path-rest. It seems quite reasonable not to support them


CodeSignSummary.md

SQL Operations Studio Version: <IP_ADDRESS>

Steps to Reproduce:
Within the main build contains CodeSignSummary.md. Don't believe this should be in the program directory

@MattIrv perhaps you could take a look at this?

Thanks for reporting this. You're right that the file shouldn't be there, but we accidentally included it when signing the build.
I just updated our build process so that it won't include the file anymore, so I'll close this bug now. If it somehow returns in a future release, please feel free to reopen this issue.


Add prelude to lib.rs

Fixed at https://github.com/Perelyn-sama/airswap-rs/commit/f1028655f7df66cf6394c134f966fbb4a8b06a5a


GMP division is incorrect

It easily gets false results. We should use proper GMP functions for division too.

I am on it

Fixed via #296.


remove unused options argument

The options argument is not being used in the function, instead a different options variable is being created, no need to include it in the function signature.

Yep. Good one.


Determine way to find the healthist forks

Migrated from GitLab: https://gitlab.com/meltano/hub/-/issues/56
Originally created by @tayloramurphy on 2021-05-24 22:20:46

Currently we're only highlighting a few variants for a given tap, but we don't have all forks documented and we don't have a scalable way to identify the best forks for a given repo.

View 5 previous comments from the original issue on GitLab


fix(commit_policy): Calculate elapsed timerange correctly

The first argument to should_commit is a duration/timedelta, not an
absolute timestamp.
This might explain why we are seeing severe performance regression when
using commit policy.
Some tests are failing, but i wanted to open this PR early on to get
some validation that i'm not totally confused?

I guess the failing test locally was a fluke. I should add tests to this before merging.


Launch Multiple VMs from a datavolume [Windows]

Hi,
I create a datavolume and created a VM
apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
  name: mywindowsvm
spec:
  running: true
  template:
    metadata:
      labels:
        kubevirt.io/domain: mywindowsvm
    spec:
      domain:
        cpu:
          cores: 4
        features:
          acpi: {}
          apic: {}
          hyperv:
            relaxed: {}
            vapic: {}
            spinlocks:
              spinlocks: 8191
        clock:
          utc: {}
          timer:
            hpet:
              present: false
            pit:
              tickPolicy: delay
            rtc:
              tickPolicy: catchup
            hyperv: {}
        devices:
          blockMultiQueue: true
          disks:
            - bootOrder: 1
              disk:
                bus: sata
              name: cdromiso
            - bootOrder: 2
              disk:
                bus: virtio
              name: virtiocontainerdisk
        firmware:
          bootloader:
            efi:
              secureBoot: false
        machine:
          type: q35
        resources:
          requests:
            memory: 16G
      nodeSelector:
        beta.kubernetes.io/instance-type: m5.metal
      volumes:
      - name: cdromiso
        dataVolume:
          name: windowsvm
      - containerDisk:
          image: quay.io/kubevirt/virtio-container-disk
        name: virtiocontainerdisk

Now when i created another VM windowsvm2 using the same datavolume, i could see the files created by the windowsvm in windowsvm.
My question is how to create multiple isolated VMs using the same data volume.
My another question is even if i add another disk it is not visible in the Windows VM.

My another question is even if i add another disk it is not visible in the Windows VM.

How are you creating the additional disk? Does this help?
https://kubevirt.io/user-guide/virtual_machines/disks_and_volumes/#disk

My question is how to create multiple isolated VMs using the same data volume.

I think you need a data volume per VM. I don't think this is copied over when VM is created, it is mounted and used.
What you might want to do might be provided by CDI, but I don't remember testing that myself so I'll leave it open to someone to help.


Split off list item to separate file

This way it is easier to override just the list item.

Resolve conflicts first.

@Somrat37 I have resolved the conflicts. Can you check?


No {}-escaping within

This issue is not  a bug, more a finding, so feel free to close immediately. I mostly want to know if this behaviour is intended or a bug.
My motivation:
I wrote a component to integrate a Podlove Webplayer (audio player) component (working source here) and learned that ~F templates don't escape within

@haslinger  I had a similar problem, and solved it in the same way, but eventually ran into bugs where the  as they are not HTML/Surface code and the syntax of any of those languages may conflict with Surface's own language, e.g. using {...}.
We don't want Surface stepping on other languages toes. The reason HEEx accepts is just because it's an extension of EEx, that means if something is not in the node's attributes area, it will be handled by EEx, which accepts anything.
This is a bad approach IMO, mainly because:

It's too sensitive to language conflicts and those kind of conflicts are extremely hard to handle. Besides, we can't predict what will change in JS, CSS or any other possible embedded languages in the future.
It makes the embedded language's code invalid. That alone already brings terrible consequences for editors (syntax highlighting, code completing, etc), linters or any tool that requires valid code to properly work.

In order to be able to work safely and avoid any kind of conflict in the future we decided that the parser will never try to parse anything that's not Surface/HTML code.
In case users need to interpolate on non-surface code, they can still use ~E or ~H in a separate function or use hooks as described above.


Fix focus problems with add new cell buttons

For #7820
Add new cell at the bottom and top of the cells was not setting focus to the newly added cell.

Codecov Report

Merging #7827 into master will decrease coverage by 0.42%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #7827      +/-   ##
=========================================
- Coverage   58.93%   58.5%   -0.43%
=========================================
  Files         498     498
  Lines       22293   21932     -361
  Branches     3575    3575
=========================================
- Hits        13138   12832     -306
+ Misses       8333    8269      -64
- Partials      822     831       +9

Impacted Files
Coverage Δ

...nt/datascience/jupyter/invalidNotebookFileError.ts
0% <0%> (-75%)
:arrow_down:

.../client/datascience/jupyter/jupyterConnectError.ts
0% <0%> (-66.67%)
:arrow_down:

...science/jupyter/jupyterKernelPromiseFailedError.ts
0% <0%> (-50%)
:arrow_down:

...ent/datascience/jupyter/jupyterWaitForIdleError.ts
0% <0%> (-50%)
:arrow_down:

src/client/common/utils/platform.ts
64.7% <0%> (-23.53%)
:arrow_down:

src/client/language/characters.ts
12% <0%> (-18.77%)
:arrow_down:

src/client/common/platform/pathUtils.ts
66.66% <0%> (-5.56%)
:arrow_down:

src/client/linters/pydocstyle.ts
84.61% <0%> (-5.13%)
:arrow_down:

src/client/constants.ts
75% <0%> (-5%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
79.24% <0%> (-3.78%)
:arrow_down:

... and 33 more

Continue to review full report at Codecov.

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

Woops, need a test to ensure we don't regress
Considering the fact that we had to implement a hack, the need for a test became all the more important

We have no tests right now that verify 'focus'. Not sure this is possible with enzyme? I thought there were problems with document.activeElement
https://github.com/airbnb/enzyme/issues/393

Although I suppose I could write tests that verify the 'focus' state of the input cells, although in a test, the bug wouldn't occur so it seems like a silly test to write. (there's no clicking in the test to mess up the focus)

If you still think we need tests for this, I'll enter a separate issue. We need to fix this before our point release, and figuring out how to mimic 'focus' in our tests is going to take a while.


⚠ Mitsubishi has degraded performance

In ca3875f, Mitsubishi (https://mitsubishimotorsid-mobileapp.com/app/login) experienced degraded performance:

HTTP code: 200
Response time: 12194 ms

Resolved: Mitsubishi performance has improved in c448689 after 3 minutes.


[feat] Add onTap & onLongPress callback

Looks great to implement onTap & onLongPress to handle click action.
For example:
Bubble(
  onTap: () {
    print('Hello from onTap');
  },
  onLongPress: () {
    print('Hello from onLongPress');
  },
  // .. other properties
),

I'm not sure that's a good idea. Use GestureDetector!

@hsul4n did you resolve?

@hsul4n did you resolve?

as @vi-k says GestureDetector works like charm!


horizon binary always returns devel version

Hi.
I've just built latest branch v0.13.2 and horizon version returns devel instead of v0.13.2, how do you add the correct version there when building?
Also tried this:
build-xenial:~/.gvm/pkgsets/go1.10.3/global/src/github.com/stellar/go/services/horizon$ export VERSION=v0.13.2
build-xenial:~/.gvm/pkgsets/go1.10.3/global/src/github.com/stellar/go/services/horizon$ go build -ldflags "-X main.version=$VERSION"
build-xenial:~/.gvm/pkgsets/go1.10.3/global/src/github.com/stellar/go/services/horizon$ ./horizon version
devel

Can you share the build script you're using to get the same binaries as posted in downloads?
Thanks.

Builds for debian packages and GitHub releases are compiled using this script. If you want to set version you need to pass a special param like:
go build -v -X github.com/stellar/go/support/app.version={version} ./services/horizon

@bartekn doesn't work for me:
build-xenial:~/.gvm/pkgsets/go1.10.3/global/src/github.com/stellar/go$ go build -v "-X github.com/stellar/go/support/app.version=$VERSION" ./services/horizon
flag provided but not defined: -X github.com/stellar/go/support/app.version
usage: build [-o output] [-i] [build flags] [packages]
Run 'go help build' for details.

I updated the comment, please check it now.

ok, it works, thank you!


Enabling router image build in integration tests workflow

Purpose
Enabling router image build in integration tests workflow

Codecov Report
Patch coverage has no change and project coverage change: +55.44% :tada:

Comparison is base (76db7b9) 24.66% compared to head (a10d24f) 80.10%.
Report is 45 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1553       +/-   ##
===========================================
+ Coverage   24.66%   80.10%   +55.44%
===========================================
  Files         134        9      -125
  Lines       15689      548    -15141
  Branches     2434      246     -2188
===========================================
- Hits         3869      439     -3430
+ Misses      11685      109    -11576
+ Partials      135        0      -135

Flag
Coverage Δ

idp-domain-service
80.10% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 143 files with indirect coverage changes

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


Custom formatting via config.toml

This allows customizing the output of spotifatius using the config.toml.
Includes {status} var which will print a play/pause unicode character depending on if the track is playing or paused.
Open to any suggestions on how to make it better, just let me know.
Also address https://github.com/AndreasBackx/spotifatius/issues/5

I'll take a look at this today and see what I can come up with.

I've done a bit more work on this. If you like the direction it's going I can add tooltip customization, but would rather wait to see if you want it refactored at all first.

Thank you! I'll try to give this a review this evening after work.

Forgot to leave a final comment with the review.
While I think the config can be improved, this is an improvement and I'm happy to extend it so it's better for you to use. I left some suggestions and with those applied, I think we can merge this.
Also please add an "Added" section to the Unreleased section of CHANGELOG.md. I'll put up a new version once it's merged and handle it appropriately. See https://keepachangelog.com/en/1.1.0/ for more info.

Also please add an "Added" section to the Unreleased section of CHANGELOG.md. I'll put up a new version once it's merged and handle it appropriately. See keepachangelog.com/en/1.1.0 for more info.

Should be good to merge after this.

Still waiting on some feedback on the Added/Removed logic not triggering

@dotaxis I'm unsure if you're referring to feedback from me. You mentioned the below earlier but I'm not sure what you mean with that review.

I also started a review regarding the TrackStatus::Added/Removed triggers because I don't think they work.

@dotaxis I'm unsure if you're referring to feedback from me. You mentioned the below earlier but I'm not sure what you mean with that review.

I also started a review regarding the TrackStatus::Added/Removed triggers because I don't think they work.

Let me know if you need any of my help.

I forgot to submit my review so only I could see it. Oops.

Also please add an "Added" section to the Unreleased section of CHANGELOG.md. I'll put up a new version once it's merged and handle it appropriately. See keepachangelog.com/en/1.1.0 for more info.

Should be good to merge after this.

Sorry for the delay, been busy all week. Will get this done over the weekend.

No rush at all, take all the time you need.

Okay, I added a line in the changelog. Let me know if you need anything else done.

Thanks again! It might take me some time to create a new version however. You should be able to use it yourself in the meantime however.

Not sure where to ask, here or create a new issue but status icons don't display on my end. Do i need some font to display them or add something to config? Trying to use it with waybar and default module config


GCMBlockCipher dup nonce check should use Array.Copy.

https://github.com/bcgit/bc-csharp/blob/master/crypto/src/crypto/modes/GCMBlockCipher.cs
            if (forEncryption)
            {
                if (nonce != null && Arrays.AreEqual(nonce, newNonce))
                {
                    if (keyParam == null)
                    {
                        throw new ArgumentException("cannot reuse nonce for GCM encryption");
                    }
                    if (lastKey != null && Arrays.AreEqual(lastKey, keyParam.GetKey()))
                    {
                        throw new ArgumentException("cannot reuse nonce for GCM encryption");
                    }
                }
            }

            nonce = newNonce; //<--here, a deep copy will be better.

👍

This should be implemented as Arrays.AreEqual checks reference equality as well. If IV buffer is reused by the user, an exception will be thrown, which happened in my case.
@peterdettman


updates /assets/assets path resolution to /assets

Coverage remained the same at 0.0% when pulling a11e0ed05e32dee24dcd89fa30841f8b9c224b5a on theseyi:assets into 36e47cb62c80f3a056a996321c3f8f87e35dffd9 on linkedin:linkedin.


webpack-dev-middleware multiple compiles

What version of incept.js are you using?
0.0.22
What version of Node.js are you using?
16.9.1
What browser are you using?
Chrome
What operating system are you using?
macOS
Describe the Bug
For some reason webpack-dev-middleware is compiling for the regular build and another for cache. It makes it look like it's compiling the same thing twice and could be mistaken for a bug.
Expected Behavior
Just shows once
compiled in xxxx s
To Reproduce
$ npm run dev
.. or ..
$ incept dev

👋 @cblanquera
Thank you for raising an issue! Please understand that this
is an open source project looking for more contributors
therefore, it will take some time to get back to you. In the
meantime, please make sure you have given as much context
as possible.


fix the path to run download-tedlium-nnet2.sh

The script file (download-tedlium-nnet2.sh) is under test/models, not test/models/test/models.

Thanks!


Clara to lyra

What is Difference ?

directory architecture (Clara/include/clara.hpp -> Lyra/include/lyra/lyra.hpp)
namespace (clara to lyra)
coding rule (uppercase method name to lowercase name)

This PR is stale. I'll work it after improving code quality.


apidocs page points to localhost

The "try it now" links on the apidocs page fail because the url is localhost

this has been corrected


Train on top of WMT19 model

Hey guys,
on this documentation of translation there is a download for the wmt19 en-de model which contains 4 model files. On torch hub there is the transformer.wmt19.en-de.single_model which consists of one model file. I prepared some data which I wanted to train on top of the model. Training solely with those data worked. I didn't get it run with one of the models above. With the 4file model I do not know how to setup it at all and with the 1model file I had dimensions mismatches.
I put the model and everything into checkpoints and started training as follows:
DEST=data/extracted/data/bin
CUDA_VISIBLE_DEVICES=0 fairseq-train \
    $DEST \
    --arch transformer_wmt_en_de --share-decoder-input-output-embed \
    --optimizer adam --adam-betas '(0.9, 0.98)' --clip-norm 0.0 \
    --lr 5e-4 --lr-scheduler inverse_sqrt --warmup-updates 4000 \
    --dropout 0.3 --weight-decay 0.0001 \
    --criterion label_smoothed_cross_entropy --label-smoothing 0.1 \
    --max-tokens 4096 \
    --eval-bleu \
    --eval-bleu-args '{"beam": 5, "max_len_a": 1.2, "max_len_b": 10}' \
    --eval-bleu-detok moses \
    --eval-bleu-remove-bpe \
    --bpe fastbpe \
    --save-dir checkpoints \
    --eval-bleu-print-samples \
    --best-checkpoint-metric bleu --maximize-best-checkpoint-metric

I get this error:
RuntimeError: Error(s) in loading state_dict for TransformerModel:
        size mismatch for encoder.embed_tokens.weight: copying a param with shape torch.Size([42024, 1024]) from checkpoint, the shape in current model is torch.Size([4088, 512]).
        size mismatch for encoder.layers.0.self_attn.k_proj.weight: copying a param with shape torch.Size([1024, 1024]) from checkpoint, the shape in current model is torch.Size([512, 512]).
[...]
size mismatch for encoder.layers.0.fc1.weight: copying a param with shape torch.Size([8192, 1024]) from checkpoint, the shape in current model is torch.Size([2048, 512]).
        size mismatch for encoder.layers.0.fc1.bias: copying a param with shape torch.Size([8192]) from checkpoint, the shape in current model is torch.Size([2048]).
        size mismatch for encoder.layers.0.fc2.weight: copying a param with shape torch.Size([1024, 8192]) from checkpoint, the shape in current model is torch.Size([512, 2048]).
        size mismatch for encoder.layers.0.fc2.bias: copying a param with shape torch.Size([1024]) from checkpoint, the shape in current model is torch.Size([512]).
[...]
Exception: Cannot load model parameters from checkpoint checkpoints/checkpoint_last.pt; please ensure that the architectures match.

I also tried transformer_wmt_en_de_big, transformer_wmt_en_de_big_align, transformer_wmt_en_de_big_t2t and transformer.
So my questions are:

which architecture to choose?
what is the difference between the 1 model file WMT19 and the 4 model file WMT19?
would be possible to train on top of the 4 file model as well and if how would the setup look alike?

Thanks, in advance!

You can load the model instantiate the model this way:
en2de = torch.hub.load('pytorch/fairseq', 'transformer.wmt19.en-de',
                       checkpoint_file='model1.pt:model2.pt:model3.pt:model4.pt',
                       tokenizer='moses', bpe='fastbpe')

Furthermore, you can inspect the arguments used by printing en2de.args.  Printing en2de.args.arch shows transformer_wmt_en_de_big as the model architecture being used.  Hope this helps!

Thanks a lot. That helped me to resolve some issues except for one. When I start training now, It loads everything, but then crashes with the following error message:
2020-09-11 17:08:42 | INFO | fairseq_cli.train | task: translation (TranslationTask)
2020-09-11 17:08:42 | INFO | fairseq_cli.train | model: transformer_wmt_en_de_big (TransformerModel)
2020-09-11 17:08:42 | INFO | fairseq_cli.train | criterion: label_smoothed_cross_entropy (LabelSmoothedCrossEntropyCriterion)
2020-09-11 17:08:42 | INFO | fairseq_cli.train | num. model params: 355811328 (num. trained: 355811328
[..]
2020-09-11 17:08:43 | INFO | fairseq_cli.train | training on 1 devices (GPUs/TPUs)
2020-09-11 17:08:43 | INFO | fairseq_cli.train | max tokens per GPU = 4096 and max sentences per GPU = None
Traceback (most recent call last):
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq/trainer.py", line 279, in load_checkpoint
    state["model"], strict=True, args=self.args
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq/models/fairseq_model.py", line 93, in load_state_dict
    return super().load_state_dict(new_state_dict, strict)
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1045, in load_state_dict
    self.__class__.__name__, "\n\t".join(error_msgs)))
RuntimeError: Error(s) in loading state_dict for TransformerModel:
        Missing key(s) in state_dict: "decoder.output_projection.weight".

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/scheiblr/anaconda3/envs/translation/bin/fairseq-train", line 8, in <module>
    sys.exit(cli_main())
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq_cli/train.py", line 350, in cli_main
    distributed_utils.call_main(args, main)
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq/distributed_utils.py", line 254, in call_main
    main(args, **kwargs)
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq_cli/train.py", line 114, in main
    disable_iterator_cache=task.has_sharded_data("train"),
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq/checkpoint_utils.py", line 173, in load_checkpoint
    reset_meters=reset_meters,
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq/trainer.py", line 288, in load_checkpoint
    "please ensure that the architectures match.".format(filename)
Exception: Cannot load model parameters from checkpoint ./checkpoints/checkpoint_last.pt; please ensure that the architectures match.

Is it possible that this is due to unknowns when binarizing data?
2020-09-11 17:11:45 | INFO | fairseq_cli.preprocess | [en] Dictionary: 42024 types
2020-09-11 17:11:46 | INFO | fairseq_cli.preprocess | [en] data/train.en: 36140 sents, 402235 tokens, 0.00224% replaced by <unk>
2020-09-11 17:11:46 | INFO | fairseq_cli.preprocess | [en] Dictionary: 42024 types
2020-09-11 17:11:46 | INFO | fairseq_cli.preprocess | [en] data/valid.en: 4517 sents, 50159 tokens, 0.00199% replaced by <unk>
2020-09-11 17:11:46 | INFO | fairseq_cli.preprocess | [en] Dictionary: 42024 types
2020-09-11 17:11:47 | INFO | fairseq_cli.preprocess | [en] data/test.en: 4518 sents, 50652 tokens, 0.00395% replaced by <unk>
2020-09-11 17:11:47 | INFO | fairseq_cli.preprocess | [de] Dictionary: 42024 types
2020-09-11 17:11:48 | INFO | fairseq_cli.preprocess | [de] data/train.de: 36140 sents, 500162 tokens, 0.0032% replaced by <unk>
2020-09-11 17:11:48 | INFO | fairseq_cli.preprocess | [de] Dictionary: 42024 types
2020-09-11 17:11:48 | INFO | fairseq_cli.preprocess | [de] data/valid.de: 4517 sents, 62528 tokens, 0.0064% replaced by <unk>
2020-09-11 17:11:48 | INFO | fairseq_cli.preprocess | [de] Dictionary: 42024 types
2020-09-11 17:11:48 | INFO | fairseq_cli.preprocess | [de] data/test.de: 4518 sents, 62872 tokens, 0.00318% replaced by <unk>
2020-09-11 17:11:48 | INFO | fairseq_cli.preprocess | Wrote preprocessed data to data/bin

Can you provide the full command that you ran

I think you may be missing --share-decoder-input-output-embed

Thank you, that helped a step further. Still I get an error, though:
RuntimeError: The size of tensor a (269746176) must match the size of tensor b (312778752) at non-singleton dimension 0

I ran the entire stuff with the following settings this time:
2020-09-14 09:49:39 | INFO | fairseq_cli.train | Namespace(activation_dropout=0.0, activation_fn='relu', adam_betas='(0.9,0.98)', adam_eps=1e-08, adaptive_input=False, adaptive_softmax_cutoff=None, adaptive_softmax_dropout=0.0, all_gather_list_size=16384, arch='transformer_wmt_en_de_big', attention_dropout=0.1, best_checkpoint_metric='loss', bf16=False, bpe='fastbpe', bpe_codes='./checkpoints/bpecodes', broadcast_buffers=False, bucket_cap_mb=25, checkpoint_suffix='', clip_norm=0.0, cpu=False, criterion='label_smoothed_cross_entropy', cross_self_attention=False, curriculum=0, data='data/bin', data_buffer_size=10, dataset_impl=None, ddp_backend='c10d', decoder_attention_heads=16, decoder_embed_dim=1024, decoder_embed_path=None, decoder_ffn_embed_dim=4096, decoder_input_dim=1024, decoder_layerdrop=0.0, decoder_layers=6, decoder_layers_to_keep=None, decoder_learned_pos=False, decoder_normalize_before=False, decoder_output_dim=1024, device_id=0, disable_validation=False, distributed_backend='nccl', distributed_init_method=None, distributed_no_spawn=False, distributed_num_procs=1, distributed_port=-1, distributed_rank=0, distributed_world_size=1, distributed_wrapper='DDP', dropout=0.2, empty_cache_freq=0, encoder_attention_heads=16, encoder_embed_dim=1024, encoder_embed_path=None, encoder_ffn_embed_dim=8192, encoder_layerdrop=0.0, encoder_layers=6, encoder_layers_to_keep=None, encoder_learned_pos=False, encoder_normalize_before=False, eval_bleu=False, eval_bleu_args=None, eval_bleu_detok='space', eval_bleu_detok_args=None, eval_bleu_print_samples=False, eval_bleu_remove_bpe=None, eval_tokenized_bleu=False, fast_stat_sync=False, find_unused_parameters=False, finetune_from_model=None, fix_batches_to_gpus=False, fixed_validation_seed=None, fp16=True, fp16_init_scale=128, fp16_no_flatten_grads=False, fp16_scale_tolerance=0.0, fp16_scale_window=None, keep_best_checkpoints=-1, keep_interval_updates=-1, keep_last_epochs=-1, label_smoothing=0.1, layernorm_embedding=False, left_pad_source='True', left_pad_target='False', load_alignments=False, localsgd_frequency=3, log_format='simple', log_interval=100, lr=[0.0007], lr_scheduler='inverse_sqrt', max_epoch=0, max_sentences=None, max_sentences_valid=None, max_source_positions=1024, max_target_positions=1024, max_tokens=3584, max_tokens_valid=3584, max_update=201800, maximize_best_checkpoint_metric=False, memory_efficient_bf16=False, memory_efficient_fp16=False, min_loss_scale=0.0001, min_lr=1e-09, model_parallel_size=1, moses_no_dash_splits=False, moses_no_escape=False, moses_source_lang='en', moses_target_lang='de', no_cross_attention=False, no_epoch_checkpoints=True, no_last_checkpoints=False, no_progress_bar=True, no_save=False, no_save_optimizer_state=False, no_scale_embedding=False, no_seed_provided=False, no_token_positional_embeddings=False, nprocs_per_node=1, num_batch_buckets=0, num_workers=0, optimizer='adam', optimizer_overrides='{}', patience=-1, pipeline_balance=None, pipeline_checkpoint='never', pipeline_chunks=None, pipeline_devices=None, pipeline_model_parallel=False, profile=False, quant_noise_pq=0.0, quant_noise_pq_block_size=8, quant_noise_scalar=0.0, quantization_config_path=None, required_batch_size_multiple=8, reset_dataloader=False, reset_lr_scheduler=False, reset_meters=False, reset_optimizer=False, restore_file='checkpoint_last.pt', save_dir='./checkpoints', save_interval=1, save_interval_updates=200, scoring='bleu', seed=2, sentence_avg=False, share_all_embeddings=False, share_decoder_input_output_embed=True, skip_invalid_size_inputs_valid_test=False, slowmo_algorithm='LocalSGD', slowmo_momentum=None, source_lang='en', stop_time_hours=0, target_lang='de', task='translation', tensorboard_logdir='./logdir', threshold_loss_scale=None, tie_adaptive_weights=False, tokenizer='moses', tpu=False, train_subset='train', truncate_source=False, update_freq=[1], upsample_primary=1, use_bmuf=False, use_old_adam=False, user_dir=None, valid_subset='valid', validate_after_updates=0, validate_interval=1, validate_interval_updates=0, warmup_init_lr=1e-07, warmup_updates=4000, weight_decay=0.0, zero_sharding='none')

Can you provide a full traceback running with CUDA_LAUNCH_BLOCKING=1

2020-09-15 13:28:15 | INFO | fairseq_cli.train | task: translation (TranslationTask)
2020-09-15 13:28:15 | INFO | fairseq_cli.train | model: transformer_wmt_en_de_big (TransformerModel)
2020-09-15 13:28:15 | INFO | fairseq_cli.train | criterion: label_smoothed_cross_entropy (LabelSmoothedCrossEntropyCriterion)
2020-09-15 13:28:15 | INFO | fairseq_cli.train | num. model params: 312778752 (num. trained: 312778752)
2020-09-15 13:28:18 | INFO | fairseq.trainer | detected shared parameter: decoder.embed_tokens.weight <- decoder.output_projection.weight
2020-09-15 13:28:18 | INFO | fairseq.utils | ***********************CUDA enviroments for all 1 workers***********************
2020-09-15 13:28:18 | INFO | fairseq.utils | rank   0: capabilities =  7.5  ; total memory = 23.650 GB ; name = TITAN RTX
2020-09-15 13:28:18 | INFO | fairseq.utils | ***********************CUDA enviroments for all 1 workers***********************
2020-09-15 13:28:18 | INFO | fairseq_cli.train | training on 1 devices (GPUs/TPUs)
2020-09-15 13:28:18 | INFO | fairseq_cli.train | max tokens per GPU = 3584 and max sentences per GPU = None
2020-09-15 13:28:29 | INFO | fairseq.trainer | loaded checkpoint ./checkpoints/checkpoint_last.pt (epoch 20 @ 201800 updates)
2020-09-15 13:28:29 | INFO | fairseq.trainer | loading train data for epoch 20
2020-09-15 13:28:29 | INFO | fairseq.data.data_utils | loaded 36140 examples from: data/bin/train.en-de.en
2020-09-15 13:28:29 | INFO | fairseq.data.data_utils | loaded 36140 examples from: data/bin/train.en-de.de
2020-09-15 13:28:29 | INFO | fairseq.tasks.translation | data/bin train en-de 36140 examples
2020-09-15 13:28:29 | INFO | fairseq.trainer | begin training epoch 21
Traceback (most recent call last):
  File "/home/scheiblr/anaconda3/envs/translation/bin/fairseq-train", line 8, in <module>
    sys.exit(cli_main())
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq_cli/train.py", line 350, in cli_main
    distributed_utils.call_main(args, main)
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq/distributed_utils.py", line 254, in call_main
    main(args, **kwargs)
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq_cli/train.py", line 125, in main
    valid_losses, should_stop = train(args, trainer, task, epoch_itr)
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/contextlib.py", line 74, in inner
    return func(*args, **kwds)
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq_cli/train.py", line 207, in train
    log_output = trainer.train_step(samples)
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/contextlib.py", line 74, in inner
    return func(*args, **kwds)
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq/trainer.py", line 576, in train_step
    raise e
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq/trainer.py", line 557, in train_step
    self.optimizer.step()
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq/optim/fp16_optimizer.py", line 180, in step
    self.fp32_optimizer.step(closure)
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq/optim/fairseq_optimizer.py", line 111, in step
    self.optimizer.step(closure)
  File "/home/scheiblr/anaconda3/envs/translation/lib/python3.7/site-packages/fairseq/optim/adam.py", line 187, in step
    exp_avg.mul_(beta1).add_(grad, alpha=1 - beta1)
RuntimeError: The size of tensor a (269746176) must match the size of tensor b (312778752) at non-singleton dimension 0

It runs now. Thanks a lot!


Run airflow not form root

Hello!
Thank you for this template.
--
I try to run airflow not from the root user:
For this I change the dockerfile:
From
# Install Airflow and any additonal dependencies
WORKDIR /root

To
# Install Airflow and any additonal dependencies
WORKDIR /app

And then create user airflow and give him all the rights to the /app directory
After that I change all occurencies of /root in docker-compose file, so the volumes point to the /app dir now
--
I expect that when I boot up airflow I'd get my DAGs up and running, but instead it seems like DAGs have not been imported at all
Could you please point me in a way why this might happen? I did not find a way to specify DAGs loading folder in the code :(

Did you change the AIRFLOW_HOME environment variable here: https://github.com/soggycactus/airflow-repo-template/blob/master/docker-compose.yaml#L20

This seems to just be an issue with they way you're attempting to change permissions, and not anything wrong with this template repository. You likely need to use chown to have the airflow user be the new owner of the app directory.


Fixed FileListItem component

Proposed Changes
Please use the Jira Key followed by the changes

JIRAKEY-1234

Some change
Another change

Checklist

[ ] I have added or updated unit tests
[ ] I have added or updated integration tests (if appropriate)
[ ] I have added or updated documentation / readme (if appropriate)
[x] I have verified that my changes have not introduced new lint errors
[x] I have added a GitHub labels to the PR for either patch, minor, or major

Testing Instructions

@ntrevino-virtru can you merge this PR?


check ngModel is undefined

I had to upgrade ngAnnotate as well as it was breaking locally.

Great stuff! Merged and released as 1.4.1.
Thanks! :+1:


Strange behaviour with datetime axis

I am trying to achieve a stacked area chart with datetimes on the x axis.

As soon as I change the type of the x axis to datetime, the graph gets weird (see attached picture).

Code:
<ApexChart TItem="Course_UserData" Title="Basic Sample" Options="options">
    <ApexPointSeries TItem="Course_UserData"
                        Items="course1"
<EMAIL_ADDRESS>                        Name="Gross Value 1"
                        XValue="@(e => e.CreatedAt)"
                        YAggregate="@(e => e.Count())" />
    <ApexPointSeries TItem="Course_UserData"
                        Items="course2"
<EMAIL_ADDRESS>                        Name="Gross Value 2"
                         XValue="@(e => e.CreatedAt)"
                        YAggregate="@(e => e.Count())" />
    <ApexPointSeries TItem="Course_UserData"
                        Items="course3"
<EMAIL_ADDRESS>                        Name="Gross Value 3"
                         XValue="@(e => e.CreatedAt)"
                        YAggregate="@(e => e.Count())" />

</ApexChart>

@code{
   // Set chart options
   private ApexChartOptions<Course_UserData> options { get; set; } = new();
   options.Chart.Stacked = true;
   options.Xaxis = new XAxis {
      Type = XAxisType.Datetime,
   };
}

Hello,
What datatype has CreatedAt?
Does it work with one series?

Hi joadan,
Thanks for your reply. The datatype of CreatedAt is DateTime and it‘s the same behaviour with just one serie.

Ok,
Try to Order by the x value.
Good tip is to start just using on series and when that works add more.
Also if you set the Debug property on the char you can see in the browser console what options are send to js

please try to convert the Datetime with the method ToUnixTimeMilliseconds()
 <ApexPointSeries TItem="Course_UserData"
                        Items="course1"
<EMAIL_ADDRESS>                        Name="Gross Value 1"
                        XValue="@(e => e.CreatedAt.ToUnixTimeMilliseconds()"
                        YAggregate="@(e => e.Count())" />

Thanks for your quick reply. I tried both suggestions and the order by solved the problem. But the graph still has some akward behaviour as it doesn't stack properly (for example at October 14). Attached are two graphs, graph one has axis type DateTime and the second one has no defined axis type:

My code:
    <ApexChart TItem="Course_UserData" Title="Basic Sample" Options="options">
        <ApexPointSeries TItem="Course_UserData"
                            Items="course1"
<EMAIL_ADDRESS>                            Name="Gross Value 1"
                            XValue="@(e => e.CreatedAt.ToUnixTimeMilliseconds())"
                            YAggregate="@(e => e.Count())"
                            OrderBy="e=>e.X" />
        <ApexPointSeries TItem="Course_UserData"
                            Items="course2"
<EMAIL_ADDRESS>                            Name="Gross Value 2"
                            XValue="@(e => e.CreatedAt.ToUnixTimeMilliseconds())"
                            YAggregate="@(e => e.Count())"
                            OrderBy="e=>e.X" />
        <ApexPointSeries TItem="Course_UserData"
                            Items="course3"
<EMAIL_ADDRESS>                            Name="Gross Value 3"
                            XValue="@(e => e.CreatedAt.ToUnixTimeMilliseconds())"
                            YAggregate="@(e => e.Count())"
                            OrderBy="e=>e.X" />
    </ApexChart>
</div>
<div class="w-full md:w-1/2 lg:w-1/3 bg-white shadow-md p-4 m-4">
    <ApexChart TItem="Course_UserData" Title="Basic Sample" Options="options2">
        <ApexPointSeries TItem="Course_UserData"
                            Items="course1"
<EMAIL_ADDRESS>                            Name="Gross Value 1"
                            XValue="@(e => e.CreatedAt)"
                            YAggregate="@(e => e.Count())"
                            OrderBy="e=>e.X" />
        <ApexPointSeries TItem="Course_UserData"
                            Items="course2"
<EMAIL_ADDRESS>                            Name="Gross Value 2"
                            XValue="@(e => e.CreatedAt)"
                            YAggregate="@(e => e.Count())"
                            OrderBy="e=>e.X" />
        <ApexPointSeries TItem="Course_UserData"
                            Items="course3"
<EMAIL_ADDRESS>                            Name="Gross Value 3"
                            XValue="@(e => e.CreatedAt)"
                            YAggregate="@(e => e.Count())"
                            OrderBy="e=>e.X" />
    </ApexChart>

@code{

  // Set chart 1 options
  private ApexChartOptions<Course_UserData> options { get; set; } = new();
  options.Chart.Stacked = true;
  options.Xaxis = new XAxis {
      Type = XAxisType.Datetime,
  };

  // Set chart 2 options
  private ApexChartOptions<Course_UserData> options2 { get; set; } = new();
  options2.Chart.Stacked = true;

}

Maybe it is related to the following issue of the Apex JS library.

I found a solution to the problem. The DateTime must be the same instance for all datarows. I created a helper class where I create a instance for each day and then pass the values to the property Values.
public class DateTimeSeries {
    public DateTime DateTime { get; set; }
    public List<int> Values { get; set; } = new List<int>();
}

With this solution, the graph gets displayed correctly. And also the stacking is working as expected.


Does not work on Mac?

Is it correct that this task does not work on vmImage: 'macOS-10.13' and you can only use the already installed ruby version there?

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

ID: 02568f8b-6928-c8f1-178a-79e4cb0d93e2
Version Independent ID: 1107622c-4165-dcff-741a-279757b35323
Content: Use Ruby Version task - Azure Pipelines & TFS
Content Source: docs/pipelines/tasks/tool/use-ruby-version.md
Product: devops
GitHub Login: @erickson-doug
Microsoft Alias: dastahel

Assigned, but no progress or response yet.

Hello? Still getting errors here:
[command]/usr/bin/sudo ln -sf /Users/vsts/hostedtoolcache/Ruby/2.6.2/x64/bin/ruby /usr/bin/ruby
ln: /usr/bin/ruby: Operation not permitted
Prepending PATH environment variable with directory: /Users/vsts/hostedtoolcache/Ruby/2.6.2/x64/bin

Pool: Hosted macOS High Sierra


Qt: Do not require mkDerivation

Motivation for this change
This removes the need to use a custom mkDerivation with Qt applications. For compatibility, it remains, but it doesn't do much besides include wrapQtAppsHook.
See also: https://github.com/NixOS/nixpkgs/issues/65399#issuecomment-541076520
TODO:

[ ] Port #70691.
[ ] Update documentation to remove references to mkDerivation.

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @

@ttuegel By port https://github.com/NixOS/nixpkgs/pull/70691 you mean qtbase setup hook checks for the presence of wrapQtAppsHook?

By port #70691 you mean qtbase setup hook checks for the presence of wrapQtAppsHook?

@worldofpeace Something like that. I'm not sure what the best option is: check for presence, or include by default. I like the idea of doing the right thing by default (including wrapQtAppsHook), but I know that trying to be "magic" often makes things difficult to understand. On the other hand, it is always possible to set dontWrapQtApps to disable the magic.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/declarative-wrappers-another-idea/6661/1

How is the debug flag related to mkDerivation?

How is the debug flag related to mkDerivation?

We have to set certain CFLAGS in all dependencies, based on the debug flag.

I am closing this pull request because my branch is completely broken and I don't know why. I will re-open later.

I am closing this pull request because my branch is completely broken and I don't know why. I will re-open later.


reinit on window resize

How init again on window resize in nuxt app? does it has any method to call on resize event?
I use swiper with directive:
 <div v-swiper:mySwiper="swiperOption"></div>

I'm with the same problem here, the carousel breaks completely on resize


fatal error: EGL/egl.h: No such file or directory

Hi,
Thanks for sharing your really nice work!
When I run main.py, I met this error related to nvdiffrast. Please let me know if you have any ideas to address this problem. Many thanks.

Hi,
This seems to be an issue in setting up nvdiffrast. Here is a similar issue: https://github.com/NVlabs/nvdiffrast/issues/56. I would recommend taking a look at their docker file and checking if you're missing any required packages.


Reuse merkle trees in ef_tests

Currently we are calculating the state root recreating the merkle tree from scratch each time we require it. (ie. here and here).
We should keep the world state in memory and update only the state transitions.
Its a follow up on #45 and there is a TODO comment in code

I think this intermediate step is not needed, let's go directly for https://github.com/lambdaclass/ethereum_rust/issues/45


Display actual line numbers in View Source Code

Hi
Thanks for such a great tool. Just an idea to improve - if you view a method source line numbering for every method starts with 1..
Is it possible to display the actual line number for the method in View Source Code. In should be the same as in Visual studio

Thank you for the suggestion. We will take a look and see if that is something we can do.

We have added the ability to view the complete source for an object. This feature should enable you to view the actual line numbers so that they would match up with what Visual Studio has. This is included in 8<IP_ADDRESS>.


Change CI engine to GitHub Actions

Moving CI to GitHub Actions might make it easier for others to contribute, as their PR builds can be executed on GitHub Actions automatically, without having to register for CircleCI.
Something to think about.

Implemented with the help of #48 by @drakulavich and subsequently https://github.com/basdijkstra/rest-assured-net/commit/19d705d277d19d94ce63c8be78cbf8ef325c9948.


Hydrolocation Endpoint

Before making a pull request

[x] Make sure all tests run
[x] Update the changelog appropriately

Hydrolocation Endpoint
Endpoint to retrieve a hydrologic location using coordinates. JIRA ticket NHGF-169.
Description
The new /linked-data/hydrolocation endpoint accepts a coordinates parameter used to find a hydrologic location using pygeoapi's nldi-flowtrace endpoint. The response includes 2 POINT features. One feature is the coordinates provided by the user and the other is the result from the flowtrace.
After making a pull request

[x] If appropriate, put the link to the PR in the JIRA ticket
[x] Assign someone to review unless the change is trivial

I only see linty stuff:

hydro_1.json is missing a new line at the end.
import statements are using * a lot.  That used to come up in linters a lot and various coding standards recommended against it.  Maybe the importer is smarter these days?


Testing true ets

These changes have been made with the purpose to test the calculation of true event types and try to make it more realistic. While doing this, 2 things have been noticed:

The partition of true event types should be independent from the actual partition, as we want to use true event types to test the room for improvement of the whole process.
True event types are not correctly defined for the background. We know that the direction is never well reconstructed for the background, as the previous analysis only expects it to be good for gammas. This means that partitioning true event types for background (by true misdirection) always ends up sending most of the background to the worst type, which affects heavily to the event-type-wise sensitivity computation, among others.

Both things have been fixed. The first one by having two partition matrices, one for reco and one for true. The second one by assuming the reconstructed event types for the background are good enough to use them directly as true event types (it seems not optimal, but without a definition, this is the best we can do to be able to compute realistic IRFs with "almost" true event types).

I just wonder about the choice to not use true classification for background. I understand why the majority of events would go to the "worse" event type. However, I would expect that once the gamma/hadron cuts are applied, this bias would be "resolved" and the partition would be somewhat realistic. Is it not the case?

The difference between the true and reconstructed direction for a proton does not really make sense, no? Proton showers may look like gamma ones when there is a pion sub-shower that very likely will have a very different direction to the impinging proton. So ranking cosmic rays (even the gamma-like ones!) w.r.t. this difference we found does not make much sense...
Even for electrons, I'm not sure how strong is the effect, but the initial electron bending due to magnetic field will worsen the "true to reconstructed" distance. This is probably a very small effect... But again something its probably more realistic to evade.

OK, I am convinced, that makes sense!


Test netlify build

Description
This PR fixes #96
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

@chandrashritii Please close this PR if the deployement preview works file

Looking good. 👍

Works fine! :+1:


fix: add additional blob path validation

What type of PR is this?

Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:

Automation added to e2e:

Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:

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

https://github.com/project-zot/zot/pull/1223/files#diff-f0da7068358f30587e2628f244293247918e02939f1df8ccafc9bd89d25146cbR132
We already validate manifest layers in validateOCIManifest
We do it with GetBlobContent which is bad because it will 'download' content and we don't need it.
We can have a VerifyBlob() function with CheckBlob logic but without locks, and use locks in
func CheckBlob() {
  lock()
  defer unlock()
  return VerifyBlob()
}

Ok I see Sebi has the same concern as me.

warning: config sha256:205eed24cbec29ad9cb4593a73168ef1803402370a82f7d51ce25646fc2f943a has an unknown media type: com.artifact.test                                      warning: layer sha256:b8ef38a79a15865d2a635e90fead3da1d8adff96c56365397da07852fc3cbc99 has an unknown media type: application/octet-stream                                {"level":"error","error":"[config.mediaType: Does not match pattern '^[A-Za-z0-9][A-Za-z0-9!#$&-^_.+]{0,126}/[A-Za-z0-9][A-Za-z0-9!#$&-^_.+]{0,126}$']","goroutine":104,"caller":"/local/rchincha/go/src/github.com/project-zot/zot/pkg/storage/common.go:90","time":"2023-05-10T21:03:50.299060476Z","caller":"/local/rchincha/go/src/github.com/project-zot/zot/pkg/storage/common.go:90","message":"OCIv1 image manifest schema validation failed"}                                                                        {"level":"info","module":"http","clientIP":"<IP_ADDRESS>:32856","method":"PUT","path":"/v2/artifact-ref/manifests/sha256:b87cd2df7da8c4dbf32d5d8af838bc4b9513a1ede8727ba82e4376c0a12f0732","statusCode":400,"latency":"0s","bodySize":423,"headers":{"Accept":["application/vnd.oci.image.manifest.v1+json"],"Accept-Encoding":["gzip"],"Content-Length":["561"],"Content-Type":["application/vnd.oci.image.manifest.v1+json"],"User-Agent":["go-resty/1.12.0 (https://github.com/go-resty/resty)"]},"goroutine":104,"caller":"/local/rchincha/go/src/github.com/project-zot/zot/pkg/api/session.go:131","time":"2023-05-10T21:03:50.299152421Z","message":"HTTP API"}                                     ✘

                                                                                Failures:
                                                                                * /local/rchincha/go/src/github.com/project-zot/zot/pkg/extensions/search/search_test.go                                                                                Line 1140:                                                                                Expected: nil
  Actual:   'can't put blob'

go test -v -cover -run ^TestGetReferrersGQL -tags sync,search,scrub,metrics,lint,ui,mgmt,userprefs,containers_image_openpgp ./pkg/extensions/search/...

{"level":"error","error":"[layers.0.data: Invalid type. Expected: string, given: null]","goroutine":97,"caller":"zotregistry.io/zot/pkg/storage/common/common.go:79","time":"2023-06-12T21:54:52.824219066Z","caller":"zotregistry.io/zot/pkg/storage/common/common.go:79","message":"OCIv1 image manifest schema validation failed"}               {"level":"info","module":"http","clientIP":"<IP_ADDRESS>:54348","method":"PUT","path":"/v2/oci-conformance/distribution-test/manifests/tagtest0","statusCode":400,"latency":"0s","bodySize":360,"headers":{"Content-Length":["671"],"Content-Type":["application/vnd.oci.image.manifest.v1+json"],"User-Agent":["distribution-spec-conformance-tests"]},"goroutine":97,"caller":"zotregistry.io/zot/pkg/api/session.go:131","time":"2023-06-12T21:54:52.824392519Z","message":"HTTP API"}

Run a latest conformance test against zot with this PR, and understand why this is.
{"level":"error","error":"[layers.0.data: Invalid type. Expected: string, given: null]","goroutine":97,"caller":"zotregistry.io/zot/pkg/storage/common/common.go:79","time":"2023-06-12T21:54:52.824219066Z","caller":"zotregistry.io/zot/pkg/storage/common/common.go:79","message":"OCIv1 image manifest schema validation failed"}               {"level":"info","module":"http","clientIP":"<IP_ADDRESS>:54348","method":"PUT","path":"/v2/oci-conformance/distribution-test/manifests/tagtest0","statusCode":400,"latency":"0s","bodySize":360,"headers":{"Content-Length":["671"],"Content-Type":["application/vnd.oci.image.manifest.v1+json"],"User-Agent":["distribution-spec-conformance-tests"]},"goroutine":97,"caller":"zotregistry.io/zot/pkg/api/session.go:131","time":"2023-06-12T21:54:52.824392519Z","message":"HTTP API"}

Secondly, layers can be empty but upstream image-spec requires at least one layer, so maybe we cannot use this validation.

I can't fully grasp the validation code... I think it's because this config descriptor:
https://github.com/opencontainers/distribution-spec/blob/main/conformance/setup.go#L289
has 'Data' field and the layers don't have it which is null, and the library expects a string.

Superseded by https://github.com/project-zot/zot/pull/1609


⚠ WSINGRESOS - RECIBOPAGO has degraded performance

In c30f48e, WSINGRESOS - RECIBOPAGO (https://srvshyweb.yucatan.gob.mx/cgi-bin/wspd_cgi.sh/WService=wsingresos/internet/servicios/wsRecibosPagosWeb.r) experienced degraded performance:

HTTP code: 200
Response time: 2088 ms

Resolved: WSINGRESOS - RECIBOPAGO performance has improved in 9b9417a.


Fix/query parameters ignored for path composition

Uhm too many recursive calls? Ignorable?

This wont fix the recursive issue but I figured it was coherent with the rest of the code

Thank you for the pr. Looks good 👍
Imho, the detekt-warning can be ignored here.  Could we supress  it for the method so we have green checks ?


Upgrade Mutex to RWLock to enable ready(undefined, true); to mean blocking async operation

Specification
We can use RWLock so that when running certain ready operations, they actually block the start, stop, destroy.
To do this, we need to use read locks on all other operations, and write locks in start, stop, destroy.
It would only apply to async functions and async generators.
Releasing the lock would only happen at the end of the async generator.
async function* asyncGenerator() {
  let i = 0;
  while (i < 3) {
    yield i++;
  }
}

async function* testthis () {
  try {
    yield * asyncGenerator();
  } finally {
    console.log('done');
  }
}

async function main () {
  for await (const a of testthis()) {
    console.log(a);
  }
}

main();

We would take the RWLock from js-polykey. However we need to upgrade it. We need to use the acquire and release API as the functional API doesn't always work. Such as for the async generators.
Additional context

https://github.com/MatrixAI/js-polykey/pull/292 - The compose method can then use just use ready(..., true); to indicate blocking operation.

It seems by default blocking can be true, since this is usually what you want, but it does change the semantics of all ready uses. Maybe that's ok. This can be integration tested by using npm link.
Tasks

Upgrade RWLock with acquire and release API
Apply the block parameter instead of wait parameter
Test all decorators and decide whether it is block true or false by default

In the mean time, switch over the symbols to be in the common utilities and export them so that js-polykey can just import the symbols from one place if they want to access it.


On-premises data gateway on the public cloud

What does the license restriction in the article mean?
https://docs.microsoft.com/en-us/data-integration/gateway/service-gateway-onprem-faq#are-there-any-licensing-prerequisites-required-to-install-gateways---
But any cloud service might have licensing restrictions on how gateways are used within that service.
Our customers are considering to install the On-premises data gateway to Azure VM and AWS VM.
AWS has already guided "How to use AWS services with On-premises gateway" in their Japanese blog.
https://aws.amazon.com/jp/blogs/news/integrate-power-bi-with-amazon-redshift-for-insights-and-analytics/
The license term of On-premises data gateway includes below:
license.docx
a.	Installation and Use. You may install and use any number of copies of the software on your devices.
Does this "your devices" mean to restrict "On-premises data gateway on the public cloud" ?

Thanks @stakemu for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close


Update the website Documentation for releases

Can someone help update the website documentation to list 1.2.4 release? We need to update https://opensearch.org/docs/latest/opensearch/install/plugins/ page for 1.2.4 and other minor releases as well.
Enhancement
Can we automate this process for future releases? https://github.com/opensearch-project/documentation-website/issues/379
Acceptance Criteria

[ ] The website is up to date for all releases upto 1.2.4

Added back in here https://opensearch.org/docs/latest/opensearch/install/plugins/


Autocatcher not working because I don't have premium

Title: [Bug/Query/(leave empty)] ErrorName
There's no error
Body:
I have no clue how to work it I did everything it's told me to do.
Problem:
the autocatcher won't launch or work
Steps to Reproduce:
Nothing it just won't work
config.json:
{
"token": "MyToken",
"command_prefix": "P^",
"priority": [
"Groudon",
"Mew",
"Machop",
"Staryu"
],
"avoid": [],
"catch_rate": 90,
"delay": 3,
"delay_on_priority": false,
"restrict_duplicates": true,
"max_duplicates": 2,
"blacklists": [],
"whitelists": [<PHONE_NUMBER>41101315 ],
"blacklist_guilds": [<PHONE_NUMBER>94620938 ],
"whitelist_guilds": [<PHONE_NUMBER>08745985 ],
"autolog": true,
"update_checker": true,
"auto_update": true,
"autocatcher": false,
"priority_only": false
}
Traceback and Screenshots:

Specs.
OS:?
Bot Version:newest for free version
Python Version:newest

Lol why open an issue when you already know the solution?


Drop support for Django 3.2

Justified by https://www.djangoproject.com/download/:

Steps to drop support for 3.2:

Finalize the ArrayField support.
Write automated tests for the ArrayField support.
Write documentation about ArrayField.
Drop support removing from the workflow and other files and release it as 1.0.0


Update to gradle 3.2.1

Updated gradle to 3.2.1, build tool version to 28.0.3 and minimum sdk to 14

@EwoutH I'm having issues running my program bigtime, immediately I run it, it shows "Bluetooth chat has stopped" on my emulator

I am closing this issue/PR, as it has been migrated to the new repo linked above in the comments. Thank you!


Responsive Pagination

Hi,
I'm wondering if making the pagination control responsive to screen size is something that's on your plans. What I mean is making the number of pages visible adapt to the screen. For example, if I have 100 pages, show 50 at full resolution (with an ellipses to see the next 50) and show maybe 5 or 10 on a smart phone. Something similar to http://auxiliary.github.io/rpage/.

This is an incrediy difficult problem to solve because it relies on walking the DOM to see how much height is actually used so the remaining height can be calculated (and heights applied because overflow scroll doesn't work unless the parent has a fixed height).  Additionally, this is a problem best solved via a layout manager; something that is beyond the scope of the UI Bootstrap library - and really, angular as a whole since there's really no "data binding" that ever occurs.


[Backend] Image Autoupdate

We need a certain service which watches the given registry and image if there are new tags. And on each new tag it should deploy the new image when passing a given regex. This behaviour should be enabled when setting image to auto update.

This must be tested in a PoC

Also implement to create an webhook endpoint to trigger the auto update next to the interval pull


[New API] : Hospital API

Brief Description 🤓
An API for Hospital Management. The API will provide CRUD operations for-

Patient Management
Doctor Management
Appointment Management along with Bills Management

How will you develop it?🤩
I will use MongoDB as database and Node, Express and Mongoose in the backend. I will create appropriate routes and use controllers for the API. I will also use some seed data to populate the database. The seed file will also be included with other files.
Deployment
None
Select the open source program you are contributing to
Other
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINES of this project.

Greetings @Varad0014🎀 ! , We are excited to have you dive into another issue with us!🚀
Your involvement in our project has been invaluable, and we're confident that your skills and insights will help us conquer this challenge😇.  Use command /gssoc24 to self assign the issue.  This issue represents an exciting opportunity for us to improve and enhance our project, and we are thrilled to have you on board.
We request you to follow CONTRIBUTING GUIDELINES.
Looking for your PR soon!
In case of any issues, you can contact us on Discord.❣

/gssoc24

Hey @Varad0014 ! I wanted to inform you that we have closed issue.Thank you for your understanding, and we look forward to your continued engagement with our repository🤗.
In case of any issues, you can contact us on Discord.
Thank you! ❣
Happy Coding! ✨
Will See you soon❣


Allow configuration of self closing for tags

When using web components / custom elements the tag will always be marked as selfClosing=false and I can see no way of changing this

The parser already marks unknown (i.e. custom) tags as selfClosing if they are encountered as such in the input, but there is no such support for tags created programatically using Tag.valueOf.
I'm not sure whether it would make sense to just add an overload of valueOf that also takes a boolean for controlling the selfClosing field, or if it would be wiser to introduce a TagBuilder that would allow customising all aspects of the configurations affecting how the tag is output.

On the other hand, this might not make any sense at all since "html5" has no concept of self-closing tags as explained in e.g. http://stackoverflow.com/a/3558200 other than for "foreign" elements, i.e. MathML and SVG elements. The Custom Elements specification doesn't define such elements as "foreign" nor does it define any new syntax that would support self-closing tags.

Jsoup supports XML parsing and generation, not just HTML.  Support for non-HTML5 self-closing tags is mandatory for XML generation.  It would be much nicer to be able to either pass a flag to Tag#valueOf or modify the self-closing attribute.  I use the following utility method for creating self-closing elements in XML:
public static Element createVoidElement(String tagName, String baseUri) {

        Document document = Jsoup.parse("<" + tagName + "/>", baseUri, Parser.xmlParser());
        document.outputSettings().prettyPrint(false);
        document.outputSettings().escapeMode(Entities.EscapeMode.xhtml);

        return document.body() == null ? document.child(0) : document.body().child(0);
    }

The problem allowing for change the self-close property is that a developer can set it as true and the element having children, which would result to an incorrect xml. I think the model is fine, just add some static methods for allowing us to register our tags, because no body has dinamic tags, we all has specific tags for our project, that can be defined in developing time. If the needs increases, the tags increases or changes, and that's it.

Is there a way i can create  a tag   like this using jsoup?

For who needs to convert self closing tags to non-self closing tags, there is a tricky solution using PowerMock
 Document document = Jsoup.parse(...);
document.traverse(new NodeVisitor() {
            @Override
            public void head(Node node, int depth) {
                if (node instanceof Element) {
                    Element el = (Element) node;
                    Whitebox.setInternalState(el.tag(), "selfClosing", false);
                }
            }

            @Override
            public void tail(Node node, int depth) {
            }
        });


model(aria): do not restrict sdpa to MATH in prefill phase

We only enable SPDBackend.MATH during both the prefill and decode phases. An Out of Memory (OOM) error may occur if the prompt is very long. This PR enables more backends in prefill phase.

Thank you @xffxff !


DEV 8737. 30. Update azure-cli 0.2.8-1 to 0.10.15 in u16

https://github.com/Shippable/pm/issues/8737

this done. closing

updated azure to latest 2.0.12


Remove ISSUE_TEMPLATE in favor of .github one

relates to https://github.com/wuhan2020/.github/pull/1 https://github.com/wuhan2020/.github/pull/2

Already tested in the wuhan2020-test repo:


Add Multiple UnitTests

Added Multi drag on the window
and multiple tests selection from the dialog window

Looks great, thank you! I'll release this as 1.5 once I fix the regex's for googletest v1.8.1


Fixes typo

Updates lib.rs, example.rs, and readme.md to correct a typo with the
word failed.

Coverage increased (+0.01%) to 96.403% when pulling 739c052dcfcaf88804e89254e12845a842eb85b0 on del6597:TypoFix into 90719d3598d5a223245426c1fb5c0b702d70cbc2 on emoon:master.

Thanks!


Server crashes

At first, the server used to crash, because of a seemingly endless list of mobs of the same kind next to each other.
I deleted the mod, reinstalled it - now the list of mobs is empty, but the server still keeps crashing the same way [in the server terminal, on the left side there is an endless repeating row of numbers, and on the right side you have mods that contain mobs and their ids] - so I assume, it is trying to go through all the mods that have mobs available, but this inevitably overloads the server, and causes it to crash [Payload may not be larger than 1048576 bytes] and  [System.OverflowException: VarInt too big]

Please share the crash logs if possible so that I can help you out.