K8SPXC-522 feature: Add support for runtimeClassName

 ❨?❩
Added runtimeClassName field, rerun types code generation and extended e2e tests

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Test name
Status

storage
passed

big-data
passed

upgrade-haproxy
passed

recreate
passed

haproxy
passed

scaling
passed

scaling-proxysql
passed

init-deploy
passed

self-healing
failed

security-context
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

limits
failed

monitoring-2-0
passed

self-healing-advanced
passed

demand-backup
passed

smart-update
passed

affinity
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

pitr
passed

users
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

scheduled-backup
failed

Test name
Status

storage
passed

big-data
passed

upgrade-haproxy
passed

recreate
passed

haproxy
passed

scaling
passed

scaling-proxysql
passed

init-deploy
passed

self-healing
failed

security-context
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

limits
failed

monitoring-2-0
passed

self-healing-advanced
passed

demand-backup
passed

smart-update
passed

affinity
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

pitr
passed

users
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

scheduled-backup
failed

Test name
Status

recreate
passed

haproxy
passed

storage
passed

upgrade-haproxy
passed

scaling
passed

big-data
passed

init-deploy
passed

scaling-proxysql
passed

self-healing
failed

security-context
passed

limits
passed

monitoring-2-0
passed

affinity
passed

restore-to-encrypted-cluster
passed

one-pod
passed

auto-tuning
passed

self-healing-advanced
passed

demand-backup
passed

proxysql-sidecar-res-limits
failed

operator-self-healing
passed

users
passed

upgrade-proxysql
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

smart-update
failed

pitr
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup-encrypted-with-tls
passed

upgrade-consistency
passed

scheduled-backup
passed

Test name
Status

recreate
passed

haproxy
passed

storage
passed

upgrade-haproxy
passed

scaling
passed

big-data
passed

init-deploy
passed

scaling-proxysql
passed

self-healing
failed

security-context
passed

limits
passed

monitoring-2-0
passed

affinity
passed

restore-to-encrypted-cluster
passed

one-pod
passed

auto-tuning
passed

self-healing-advanced
passed

demand-backup
passed

proxysql-sidecar-res-limits
failed

operator-self-healing
passed

users
passed

upgrade-proxysql
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

smart-update
failed

pitr
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup-encrypted-with-tls
passed

upgrade-consistency
passed

scheduled-backup
passed

Test name
Status

storage
passed

haproxy
passed

self-healing
failed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

upgrade-haproxy
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

scaling
passed

recreate
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
passed

demand-backup
passed

pitr
passed

demand-backup-encrypted-with-tls
passed

big-data
passed

scheduled-backup
passed

upgrade-proxysql
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

smart-update
passed

self-healing-advanced
passed

operator-self-healing
passed

upgrade-consistency
passed

Test name
Status

storage
passed

haproxy
passed

self-healing
failed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

upgrade-haproxy
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

scaling
passed

recreate
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
passed

demand-backup
passed

pitr
passed

demand-backup-encrypted-with-tls
passed

big-data
passed

scheduled-backup
passed

upgrade-proxysql
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

smart-update
passed

self-healing-advanced
passed

operator-self-healing
passed

upgrade-consistency
passed

Test name
Status

scaling
passed

big-data
passed

storage
passed

haproxy
failed

upgrade-haproxy
passed

recreate
passed

init-deploy
passed

self-healing
failed

scaling-proxysql
passed

security-context
passed

restore-to-encrypted-cluster
passed

limits
passed

upgrade-proxysql
passed

monitoring-2-0
passed

affinity
passed

demand-backup
passed

smart-update
passed

one-pod
passed

self-healing-advanced
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

operator-self-healing
passed

pitr
passed

users
passed

tls-issue-self
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
failed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

Test name
Status

scaling
passed

big-data
passed

storage
passed

haproxy
failed

upgrade-haproxy
passed

recreate
passed

init-deploy
passed

self-healing
failed

scaling-proxysql
passed

security-context
passed

restore-to-encrypted-cluster
passed

limits
passed

upgrade-proxysql
passed

monitoring-2-0
passed

affinity
passed

demand-backup
passed

smart-update
passed

one-pod
passed

self-healing-advanced
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

operator-self-healing
passed

pitr
passed

users
passed

tls-issue-self
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
failed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

Hi @ollevche
Is this code works well on low k8s versions?
By saying well i mean all works well, even without implemented functionality to k8s
Like minishift 3.11/openshift 3.11?

Hi @ollevche
Is this code works well on low k8s versions?
By saying well i mean all works well, even without implemented functionality to k8s
Like minishift 3.11/openshift 3.11?

Test name
Status

upgrade-haproxy
passed

scaling
passed

haproxy
failed

storage
passed

recreate
passed

big-data
passed

init-deploy
passed

self-healing
passed

scaling-proxysql
passed

limits
passed

security-context
passed

upgrade-proxysql
passed

restore-to-encrypted-cluster
passed

monitoring-2-0
passed

self-healing-advanced
passed

affinity
passed

smart-update
passed

demand-backup
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

pitr
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

scheduled-backup
failed

Test name
Status

upgrade-haproxy
passed

scaling
passed

haproxy
failed

storage
passed

recreate
passed

big-data
passed

init-deploy
passed

self-healing
passed

scaling-proxysql
passed

limits
passed

security-context
passed

upgrade-proxysql
passed

restore-to-encrypted-cluster
passed

monitoring-2-0
passed

self-healing-advanced
passed

affinity
passed

smart-update
passed

demand-backup
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

pitr
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

scheduled-backup
failed

Hi @ollevche
Is this code works well on low k8s versions?
By saying well i mean all works well, even without implemented functionality to k8s
Like minishift 3.11/openshift 3.11?

Hi, @qJkee
minishift 3.11/openshift 3.11 ignores runtimeClassName field so it's safe to use

Hi @ollevche
Is this code works well on low k8s versions?
By saying well i mean all works well, even without implemented functionality to k8s
Like minishift 3.11/openshift 3.11?

Hi, @qJkee
minishift 3.11/openshift 3.11 ignores runtimeClassName field so it's safe to use

Test name
Status

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

scaling
passed

scaling-proxysql
passed

security-context
passed

haproxy
failed

big-data
passed

upgrade-haproxy
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

pitr
passed

demand-backup-encrypted-with-tls
passed

scheduled-backup
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

Test name
Status

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

scaling
passed

scaling-proxysql
passed

security-context
passed

haproxy
failed

big-data
passed

upgrade-haproxy
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

pitr
passed

demand-backup-encrypted-with-tls
passed

scheduled-backup
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

Test name
Status

big-data
passed

scaling
passed

storage
passed

recreate
passed

haproxy
passed

upgrade-haproxy
passed

self-healing
passed

scaling-proxysql
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

security-context
passed

limits
passed

monitoring-2-0
passed

smart-update
passed

self-healing-advanced
passed

affinity
passed

one-pod
passed

auto-tuning
passed

operator-self-healing
passed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

pitr
passed

validation-hook
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

big-data
passed

scaling
passed

storage
passed

recreate
passed

haproxy
passed

upgrade-haproxy
passed

self-healing
passed

scaling-proxysql
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

security-context
passed

limits
passed

monitoring-2-0
passed

smart-update
passed

self-healing-advanced
passed

affinity
passed

one-pod
passed

auto-tuning
passed

operator-self-healing
passed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

pitr
passed

validation-hook
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

haproxy
passed

storage
passed

recreate
passed

big-data
passed

upgrade-haproxy
passed

scaling
passed

init-deploy
passed

self-healing
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
passed

limits
passed

upgrade-proxysql
passed

self-healing-advanced
passed

monitoring-2-0
passed

demand-backup
passed

affinity
passed

smart-update
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

pitr
failed

Test name
Status

haproxy
passed

storage
passed

recreate
passed

big-data
passed

upgrade-haproxy
passed

scaling
passed

init-deploy
passed

self-healing
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
passed

limits
passed

upgrade-proxysql
passed

self-healing-advanced
passed

monitoring-2-0
passed

demand-backup
passed

affinity
passed

smart-update
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

pitr
failed

Test name
Status

big-data
passed

haproxy
passed

scaling
passed

storage
passed

upgrade-haproxy
passed

self-healing
passed

scaling-proxysql
passed

init-deploy
passed

security-context
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

self-healing-advanced
passed

tls-issue-cert-manager
passed

operator-self-healing
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

Test name
Status

big-data
passed

haproxy
passed

scaling
passed

storage
passed

upgrade-haproxy
passed

self-healing
passed

scaling-proxysql
passed

init-deploy
passed

security-context
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

self-healing-advanced
passed

tls-issue-cert-manager
passed

operator-self-healing
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

Test name
Status

storage
passed

self-healing
passed

self-healing-advanced
passed

big-data
passed

upgrade-haproxy
passed

operator-self-healing
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

pitr
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

scaling
passed

scaling-proxysql
passed

security-context
passed

demand-backup-encrypted-with-tls
passed

scheduled-backup
passed

Test name
Status

storage
passed

self-healing
passed

self-healing-advanced
passed

big-data
passed

upgrade-haproxy
passed

operator-self-healing
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

pitr
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

scaling
passed

scaling-proxysql
passed

security-context
passed

demand-backup-encrypted-with-tls
passed

scheduled-backup
passed

PXC operator docker - perconalab/percona-xtradb-cluster-operator:PR-746-5fcd7bba

PXC operator docker - perconalab/percona-xtradb-cluster-operator:PR-746-5fcd7bba

Test name
Status

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

upgrade-haproxy
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

scaling
passed

tls-issue-self
passed

scaling-proxysql
passed

tls-issue-cert-manager
passed

recreate
passed

security-context
passed

tls-issue-cert-manager-ref
passed

restore-to-encrypted-cluster
passed

validation-hook
passed

demand-backup
passed

pitr
passed

demand-backup-encrypted-with-tls
passed

scheduled-backup
passed

big-data
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

Test name
Status

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

upgrade-haproxy
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

scaling
passed

tls-issue-self
passed

scaling-proxysql
passed

tls-issue-cert-manager
passed

recreate
passed

security-context
passed

tls-issue-cert-manager-ref
passed

restore-to-encrypted-cluster
passed

validation-hook
passed

demand-backup
passed

pitr
passed

demand-backup-encrypted-with-tls
passed

scheduled-backup
passed

big-data
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed


Add text classification feature to ML Job

Overview
In the most successful ML projects, you will often build an ensemble of models. The results can be combined differently or even used as a feature in another model. This task here is to look into building a new feature for our existing model to label documents based on the text content.
Hypothesis
Favorite resumes are more likely to have similar terms and archived resumes are more likely to have similar terms.
Implementation Strategies
There are a number of ways to do this in increasing order of complexity. Start with the first one and go on to others only if necessary.
1.) Simple Bayes classifier. Similar to a spam filter. Looking for common words that are in your two labels and giving the likelihood of it being a class. Example of doing this can be found here: https://github.com/dataworks/internship-2015/tree/master/etl/Cleanser
2.) Paragraph vectors - Using dl4j/deep learning to classify. Example can be found here: https://github.com/kogecoo/dl4j-0.4-examples-scala/blob/master/src/main/scala/org/deeplearning4j/examples/nlp/paragraphvectors/ParagraphVectorsClassifierExample.scala
3.) Word2VecRNN - Combine word vectors and a recurrent neural network. Would be a project within itself. Example can be found here: https://github.com/kogecoo/dl4j-0.4-examples-scala/tree/master/src/main/scala/org/deeplearning4j/examples/recurrent/word2vecsentiment

A naive bayes model trained against term frequencies now works as a feature.


Tutorial: Structural connectivity (dMRI)

This tutorial briefly explains how to construct the structural connectivity for a single subject using diffusion MRI and neurodesk.

Thanks @Joanone :)
Great addition to the tutorials

Great work :)

Thanks everyone :).


Add service.omitClusterIP parameter

Hey I noticed you could not issue a helm upgrade with this chart if clusterIP was left to the default value of "". This should fix it.
Ref: https://github.com/helm/helm/issues/6378#issuecomment-557746499

Hi Thanks for the PR !
I was actually working on a refractor of the service.
Feel free to review the last commit on the master branch.
Basically i drop the ClusterIP value and let Kubernetes managed it


Make "Edit/delete file" clickable on compare page

Example URL:
https://github.com/Cog-Creators/Red-DiscordBot/compare/V3/develop...jack1142:pr/ghactions?expand=1
"Edit/delete file" links are already there, but they're not active, IMO it would be useful to be able to quickly edit files from there if you notice some error in files:

Of course that link should only be active when you can edit the head branch.
Edit: I also noticed that "View file" link there doesn't link you to branch but to commit so that makes it take even longer to edit a file.

@fregante and @jack1142
Have this done in https://github.com/yakov116/refined-github/tree/enable-file-links-in-compare-view
But I need to wait for #3138 to be merged first.

@fregante and @jack1142
Have this done in https://github.com/yakov116/refined-github/tree/enable-file-links-in-compare-view
But I need to wait for #3138 to be merged first.

I remember trying to also “fix” the edit link in that view but it didn’t make sense (I don’t remember why)

I think I remember now. The link only makes sense if the version on the right points to a branch and not a permalink (commit, tag), and this information might not be available on compare views.
If you compare 2 commits, the edit and delete links don’t make sense.
@yakov116 can you reliably detect whether the head branch (right) points to a permalink? If not, this feature should probably be scrapped.

Yes I can except for one case. (I wish I had a fork of your's I can give you a link to test on)
https://github.com/yakov116/refined-github/compare/upstream...FloEdelmann:faster-reviews
In this case I am comparing a fork to my own repo and I don't have rights to edit the forked repo. Clicking edit/delete will not lead to a 404 rather to the page offering me to fork the repo.
Github gives us an easy detection for permalink's, since it will not give you an option to create a PR if you are comparing a permalink. In that case I only enabled the feature for the view and not the edit/delete. (Link to the branch/tag instead of a commit)

I wish I had a fork of your's I can give you a link to test on

I just made this: https://github.com/fregante/refined-github

This is the one case
https://github.com/fregante/refined-github/compare/a@b...FloEdelmann:faster-reviews
Permalink
https://github.com/fregante/refined-github/compare/20.5.27...FloEdelmann:faster-reviews
Where you should be able to edit
https://github.com/fregante/refined-github/compare/a@b...sindresorhus:incremental-tag-changelog-link

A suggestion: the button text could be changed to "Edit latest file" to make it clear that it edits the latest file on that branch.
Or to make it clearer which branch it would edit on:

The above screenshot requires the  to be changed to , otherwise the menu will be too thin:

Good point. I wonder if that can be displayed any other way since it applies to all of the 3 links.

Dropdown header

Not a great default style though

I like that idea.
What about the "View file" button? i.e. in the case of https://github.com/fregante/refined-github/compare/a@b...FloEdelmann:faster-reviews, "View file" always views at point of 1ab3f6f and not the latest.
Maybe something like this?

(The first "View file" button is GitHub's original button.)

If branch name was shown in the dropdown, this is another edge case to consider: a user might be confused about whether it shows the latest file the left branch vs. the right branch.
i.e. this case, where the base branch name matches the compare branch name.

I suppose in that case you could show this (if repo names are different)

(if repo names are the same)

p.s. the width: initial thing is applied here, but it seems that only the buttons themselves can widen the dropdown, and not the headers. Can't figure out the CSS fix here.

Definitely interesting, but I wonder if it’s useful to ever link to the commit from that dropdown. If you can open the branch link, why would you ever open the commit link?


fix: typescript declarations for import.meta.glob

📑 Description
Typescript declaration for the import of markdown files in index.ts file.
Status

[ ] Not Completed
[x] Completed

✅ Checks

[x] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] I have checked the page with https://validator.unl.edu/
[x] All the tests have passed
[x] My pull request is based on the latest commit (not the npm version).

ℹ Additional Information

What are you trying to solve with this PR?

npm run check

There are 32 errors. Which one, may I ask?

All of those:
Error: Property 'metadata' does not exist on type 'unknown'.
    iterableExampleFiles.map(async ([path, resolver]) => {
      const { metadata } = await resolver();
      return {


Allow opt-in tree-shaking of class properties

Feature request
Disclaimer: I assume this is not possible, and has already been discussed and rejected many times – but I couldn't find any previous discussion, so I thought I'd raise the topic in case there have been any advances in tree-shaking that could allow this.
What is the expected behavior?
Given a library that exposes an instance with methods for most operations (real-world example):
import Completions from './completions'
import Images from './images'

export default class OpenAI extends APIClient {
  completions: Completions = new Completions(this);
  images: Images = new Images(this);
}

which is used like so:
import OpenAI from 'openai'

const client = new OpenAI()

const result = await client.completions.create()

It would be nice to have a way to tree-shake away the images API in the above example.
Of course, this would have the dangerous result of changing the structure of the OpenAI class, here, in such a way that properties which are supposed to be a certain type would throw at runtime – eg, client[calculateService()] would either have to disable tree-shaking or throw.
What is motivation or use case for adding/changing the behavior?
There is a tension between those who want efficient builds (e.g., for fast boots on edge runtimes), and developers who like fluent APIs.
For example, AWS had to fully rewrite their SDK to allow modularity, but this unfortunately hurts discoverability – per one developer I know, "I've used the new version of the AWS SDK and it is completely terrible when it comes to being able to actually find what you need".
Devlopers would ideally like to see bundlers improve their ability to handle patterns like this, to dodge the tradeoff entirely.
How should this be implemented in your opinion?
Perhaps like so:
import Completions from './completions'
import Images from './images'

export default class OpenAI extends APIClient {
  /** webpackTreeShakeableProperty: true */
  get completions(): Completions {
    return this._completions ??= new Completions(this);
  }

  /** webpackTreeShakeableProperty: true */
  get files(): Files {
    return this._files ??= new Files(this);
  }
}

which, with the above usage, would get transpiled to this:
import Completions from './completions'
export default class OpenAI extends APIClient {
  get completions() {
    return this._completions ??= new Completions(this);
  }

  get files() {
    throw new Error('property `files` on class `OpenAI` removed by webpack tree-shaking; see https://some.url/with-docs')
  }
}

Even better if the library author can use normal properties instead of getter methods.
Are you willing to work on this yourself?
I'd be willing to fund this work, depending on the scope.

Thank you very much for your detailed feedback. After testing with webpack 5.88.2, I also noticed the issue you mentioned: Unused class properties were not removed. Inspired by your suggestion, I created a simple demo based on AST to address this problem.
The main steps are as follows:

Use @babel/parser to parse the code into an AST (Abstract Syntax Tree).
Traverse the AST with @babel/traverse, noting class method definitions and invocations.
Determine the class methods that have not been called based on the records.
Traverse the AST again, removing nodes for unused class methods.
Use @babel/generator to produce new code from the optimized AST.

Original Code:
class OpenAI {
    constructor() {
   }

    completions() {
        console.log("Completion result from OpenAI.")
    }

    images() {
        console.log("Generating images...");
    }
}

const client = new OpenAI()
const result = client.completions()
console.log(result);

Trimmed Code:
class OpenAI {
  constructor() {}
  completions() {
    console.log("Completion result from OpenAI.");
  }
}
const client = new OpenAI();
const result = client.completions();
console.log(result);

Implementation Code:
const parser = require("@babel/parser");
const traverse = require("@babel/traverse").default;
const generator = require("@babel/generator").default;
// This class represents a study session a student might have.
const code = `
class OpenAI {
    constructor() {
   }

    completions() {
        console.log("Completion result from OpenAI.")
    }

    images() {
        console.log("Generating images...");
    }
}

const client = new OpenAI()
const result = client.completions()
console.log(result);
`;

// Parse the code to generate AST
const ast = parser.parse(code, {
    sourceType: "module",
    plugins: ["jsx", "classProperties"],
});

// Store the methods from the classes and track if they've been called
const methods = new Map();

// Map variables to their class names for reference
const variableToClassMap = new Map();

traverse(ast, {
    ClassMethod(path) {
        const className = path.findParent((p) => p.isClassDeclaration()).node.id.name;
        const methodName = path.node.key.name;
        methods.set(`${className}.${methodName}`, false);
    },
    VariableDeclarator(path) {
        if (path.node.init.type === "NewExpression") {
            variableToClassMap.set(path.node.id.name, path.node.init.callee.name);
        }
    },
    CallExpression(path) {
        const callee = path.node.callee;

        if (callee.type === "MemberExpression") {
            const className = variableToClassMap.get(callee.object.name) || (callee.object.type === "ThisExpression" ? "this" : null);
            const methodName = callee.property.name;

            if (methods.has(`${className}.${methodName}`)) {
                methods.set(`${className}.${methodName}`, true);
            }
        }
    },
});
const unusedMethods = [...methods.entries()]
    .filter(([method, used]) =>
        !used &&
        !method.endsWith('.constructor')
    )
    .map(([method]) => method);

console.log("Unused methods:", unusedMethods);

// Traverse the AST again to remove the unused methods
traverse(ast, {
    ClassMethod(path) {
        const className = path.findParent((p) => p.isClassDeclaration()).node.id.name;
        const methodName = path.node.key.name;

        const methodKey = `${className}.${methodName}`;

        if (unusedMethods.includes(methodKey)) {
            path.remove(); // This deletes the node representing the method from the AST.
        }
    },
});

// Generate the optimized code and output it
const output = generator(ast).code;
console.log(output);

This method still has its limitations. It might not cover all scenarios and may not be fully compatible with webpack. If you have better suggestions or any other points for discussion, please share. I look forward to engaging in a deeper dialogue with you and collectively refining this solution.

This would still be really helpful!

Technically, I think you can setup terser to do it without webpackTreeShakeableProperty, but yeah, terser doesn't build a graph so you need manually provide values, and yes, it is a hard tasks, you can try to implement your own plugin to make such things, we have an API for it


min_zoom and max_zoom are not optional

If you omit them, they're both set to 0 in the tilejson. This seems to break the preview viewer and, at least with MapBox GL, results in only the 0 zoom level being rendered, which results in some interestingly abstract maps.
Either the docs/config parser need changing to make these required, or we need some sensible defaults...

@russss interesting bug. Just so I understand your config, you want every layer to render at every zoom so therefore you did not set a min_zoom and max_zoom for the layers?

Yeah, the docs say those config directives aren't required so I didn't include them!  In this case my data matches the OSM zoom ranges, and I was auto-generating the tegola configuration, so I didn't have any zoom range numbers to hand.
I think the simplest fix is just to make max_zoom default to something like 17 instead of 0.

I could also potentially remove max_zoom if it's not set.

Well, we already have a hard-coded MaxZ of 22. So, if it's not there, I think it should default to this constant. With MinZ defaulting to 0.

@gdey I like that idea. Let's go with it.


Add Notation data support in subpackets

see https://github.com/ProtonMail/crypto/issues/27

Dear maintainers, will this get reviewed?

Hi folks! :wave:
Some people brought it to my attention that notation support is critical to their use case, e.g. writing Keyoxide-compatible tools (Keybase-like decentralized bidirectional proof systems) in Go.
If conflicts are the only thing preventing the merge I know some people even have fixed that in their forks (@omz13) and could raise a fix-up PR if that's the only concern.
Would that be an acceptable resolution? Thanks for your time! CC: @twiss, @wussler.
(I'll use this occasion to plug an ad that Sequoia PGP has a nice and full support for notations! :sweat_smile: haha)

Hi @wiktor-k, thank you for your interest.
We've seen there is quite some push for this feature, and will take care of merging this PR!

Thank you, very, very much! :bow: Have a nice day!

Good point @twiss, I should have remembered that! :sweat_smile:

Right :D Thanks for pushing this forward in all our implementations ^.^

The Notations structure does not contain any exportable fields... should they be exported? Just thinking about this because I'm dumping some entities as JSON data and the Notations entry is there but an empty object because nothing to export (even though there's some notation data present).

IsHumanReadable?

Critical      bool

IsCritical?

Yeah, maybe that's better :+1:

I just noticed (for the record) that my old commit contains quite a few examples that could be used in unit tests for critical notations here:
https://github.com/openpgpjs/openpgpjs/commit/82799390ded7bd023555f481fc6992a560e7924b#diff-c789f741e120e8bd74404f74450907c81bcc9918eb3de78037b04b15552290e7R470-R637

I've added config.KnownNotations, a map[string]bool indicating which notation names are known (i.e. allowed for critical notations). This is then checked when reading a message / verifying a signature, both for the signature itself and all relevant key binding signatures. Let me know if anyone sees an issue with this API!
@wiktor-k thanks for the link to the test case, I've added it here as well :)

Thanks everyone! 👏 Great to see this finally being in! 👍
Have a great evening! 👋

Thanks, you too :)

Many many many thanks!


Support extra bundles with modules inside Array(N).concat([])

Normally, a chunk starts with something like this:
webpackJsonp_adhaghasd([0,2],[ /* modules here */ ])

..or like this:
!function(e){/* webpack bootstrap */}([ /* modules here */])

But at least in @matteoantoci's case in https://github.com/th0r/webpack-bundle-analyzer/issues/29#issuecomment-276680137, the troublesome chunk starts like this:
webpackJsonplmn_ui_obe__name_Init([0],Array(104).concat([ /* modules here */]))

This case was not handled by the utility parsing the module object back from the compiled source using AST parser, parseUtils.js
That module template comes from this line in the webpack source code: https://github.com/webpack/webpack/blob/v1.14.0/lib/Template.js#L91
It seems like this is some sort of an optimization inside webpack that allows the modules to be listed in chunks without having to specify hundreds of "empty" elements before.
This PR should hopefully fix #29 with a proper solution (unlike the quickfix done in #42).
I'm asking all that had the TypeError over at #29 to test this out!
Check out CONTRIBUTING.md on how to test-drive a development version of this plugin.
Just run it from my fork instead:
git clone git://github.com/valscion/webpack-bundle-analyzer.git
git checkout support-array-concat-bundles

Confirmed to work:

[x] @matteoantoci https://github.com/th0r/webpack-bundle-analyzer/issues/29#issuecomment-277523357
[x] @Koslun https://github.com/th0r/webpack-bundle-analyzer/issues/29#issuecomment-277669582
[ ] @jovinbm
[x] @InSuperposition https://github.com/th0r/webpack-bundle-analyzer/issues/29#issuecomment-277892333
[x] @frankleng
[ ] @christianalfoni
[ ] @eshion
[x] @unsafecode
[ ] @drcmda

Confirm to work for me too (was having the error since migrating to webpack2 with code splitting and use of commonschunkplugin)

@valscion thanks for the fix. worked for me!

Thanks a lot @valscion! Merged.

Published in v2.2.2

Thanks @valscion for making the PR and @th0r for publishing the new version.
Unfortunately it looks like the lib directory didn't get updated for version 2.2.2 on npm for some reason :-(
https://github.com/th0r/webpack-bundle-analyzer/issues/46

Sorry about that, fixed in v2.2.3

Hi there!
Sorry for my late reply, been home sick a few days.
I am sorry to say it did not work on our project.
Couldn't parse bundle asset "/62a7049a30026325725d.js".
Analyzer will use module sizes from stats file.

Versions:
webpack 2.2.1
webpack-bundle-analyzer 2.2.3

That seems to be a separate problem, @christianalfoni. Care to open an issue with more details? Could you maybe post some 500 first and 10 last chars of your bundled files + stats.json file to the new issue?

@valscion Eyh, what do you know, now it works. Not sure what was changed here. We did a pretty huge refactor on our project though, but also the fact thatI changed some webpack config as well made have affected it. Anyways, it works :)

Ok great to hear! :smile:

@valscion I still getting the error with webpack 2.2.1
webpack-bundle-analyzer 2.3.0.
Do you want the bundled files to take a look?

Yes please, and please open a new issue :)


Duplicate Open Remote Repository

🤔 how did you get this? I only see one on latest Insiders (vscode.dev and desktop)


Html to Latex regression 1.1.56

I noticed a regression when upgrading from 1.1.55 to 1.1.56, in that now the HTML output in notebooks no longer renders.

$ myst -v
v1.1.56
Description
myst build --tex now throws these errors whereas in 1.1.55 this worked fine
⛔ Unhandled LaTeX conversion for node of "div"
⛔ Unhandled LaTeX conversion for node of "span"

The HTML conversion was put in I think by @rowanc1 to support html output from code in roboticsbook.org, in the conversion to latex. But I guess it broke here :-)
Proposed solution
I'll revert to 1.1.55 for now. I believe @rowanc1 will probably know exactlhy what happened and how to fix.
Additional notes

@dellaert Rowan will likely know the context of this, but could you share a reproducer so that I might take a look?

We did change the HTML parsing to now preserve divs, but potentially there is something else going on. I will get the latex parsing back up and working with these changes shortly!

Thanks @rowanc1
@agoose77 A full repro is hard for me but an example is https://github.com/gtbook/robotics/blob/main/S31_vacuum_state.ipynb. The output of pretty. (Rowan has access to a repo in which the entire book is rendered, which he helped set up).

I will take a look now @dellaert!

This will be released tomorrow!


Re-run the black formatter

Fixes small formatting issues.
Code Quality

[X] I have read the Contribution Guide
[X] My code follows the code style of this project
[X] My code builds (or compiles) cleanly without any errors or warnings
[X] My code contains relevant comments and necessary documentation

The one failing test is a code coverage diff goal. Since this only modifies the formatting, I will continue with the merge.


feat(open-api): get authorized apps

What's the purpose of this PR
Let open api know that which applications it can operate.
Which issue(s) this PR fixes:
Relate to #3607
Brief changelog
Add a new controller in portal
Add a new method in ApolloOpenApiClient
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Read the Contributing Guide before making this pull request.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit tests to verify the code.
[x] Run mvn clean test to make sure this pull request doesn't break anything.

Codecov Report

Merging #3647 (ecda570) into master (b0173d7) will decrease coverage by 0.09%.
The diff coverage is 17.24%.

@@             Coverage Diff              @@
##             master    #3647      +/-   ##
============================================
- Coverage     50.98%   50.88%   -0.10%
- Complexity     2329     2332       +3
============================================
  Files           449      451       +2
  Lines         14026    14055      +29
  Branches       1426     1428       +2
============================================
+ Hits           7151     7152       +1
- Misses         6388     6416      +28
  Partials        487      487

Impacted Files
Coverage Δ
Complexity Δ

...ork/apollo/openapi/client/ApolloOpenApiClient.java
47.45% <0.00%> (-0.82%)
5.00 <0.00> (ø)

...ollo/openapi/client/service/AppOpenApiService.java
48.00% <0.00%> (-12.00%)
3.00 <0.00> (ø)

...k/apollo/openapi/service/AuthorizationService.java
19.04% <19.04%> (ø)
1.00 <1.00> (?)

...openapi/v1/controller/AuthorizationController.java
50.00% <50.00%> (ø)
1.00 <1.00> (?)

...mework/apollo/portal/component/PortalSettings.java
57.81% <0.00%> (-7.82%)
5.00% <0.00%> (ø%)

...ervice/service/ReleaseMessageServiceWithCache.java
85.88% <0.00%> (+1.17%)
24.00% <0.00%> (+1.00%)

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 b0173d7...ecda570. Read the comment docs.

as https://github.com/ctripcorp/apollo/pull/3747 merged, please update changs log. :-)

@Anilople any update on this?

besides, it's better to add necessary unit tests for the new logic

Is there a better way to test it? It is a little hard, I don't know how to write test for it.

besides, it's better to add necessary unit tests for the new logic

Is there a better way to test it? It is a little hard, I don't know how to write test for it.

I notice you added an integration test in com.ctrip.framework.apollo.openapi.v1.controller.AppControllerTest, this looks okay to me. However, in integration test, normally we wouldn't mock the main logic and would set up the data instead, you may refer the example com.ctrip.framework.apollo.configservice.integration.ConfigControllerIntegrationTest for more details.
And in this case, I think a simple unit test is also okay, e.g. after mocking the necessary dependencies, we simple call appController.findAppsAuthorized and verify the execution logic and result. There is also an example for your reference: com.ctrip.framework.apollo.configservice.controller.ConfigControllerTest.
BTW, as @JaredTan95 mentioned, please also update the CHANGES.md.


Effect applied for specified window types

Just wanted to see if this was possible.
Thanks

Yes it is possible. You have to match the criteria of the window in the option to enable decorations.


Rename symbol (F2) to rename one variable name fully mess your whole script

Behaviour
Expected vs. Actual
Expected : using F2 does allow to JUST rename variable names
Actual : using F2 to rename variable names and ADD blank lines to your script (or mess it up completely if you do it twice)
Steps to reproduce:

declare a variable in a script
click on the variable name
use 'F2' key to rename
rename the variable
press enter
your script is now messy

Python extension v2022.0.1814523869
Python version installed 3.10.0
VS Code 1.64.1
Example :
Before renaming anything:

After renaming the "white" variable to "wwhite":

Then after renaming again a variable name (here "blue" to "bllue"):

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.10.0
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Global
Value of the python.languageServer setting: Default

User Settings

defaultLS: {"defaultLSType":"Pylance"}

downloadLanguageServer: true

envFile: "<placeholder>"

venvPath: "<placeholder>"

venvFolders: "<placeholder>"

condaPath: "<placeholder>"

pipenvPath: "<placeholder>"

poetryPath: "<placeholder>"

languageServer: "Pylance"

linting
• enabled: true
• cwd: "<placeholder>"
• Flake8Args: "<placeholder>"
• flake8Enabled: false
• flake8Path: "<placeholder>"
• lintOnSave: true
• banditArgs: "<placeholder>"
• banditEnabled: false
• banditPath: "<placeholder>"
• mypyArgs: "<placeholder>"
• mypyEnabled: false
• mypyPath: "<placeholder>"
• pycodestyleArgs: "<placeholder>"
• pycodestyleEnabled: false
• pycodestylePath: "<placeholder>"
• prospectorArgs: "<placeholder>"
• prospectorEnabled: false
• prospectorPath: "<placeholder>"
• pydocstyleArgs: "<placeholder>"
• pydocstyleEnabled: false
• pydocstylePath: "<placeholder>"
• pylamaArgs: "<placeholder>"
• pylamaEnabled: false
• pylamaPath: "<placeholder>"
• pylintArgs: "<placeholder>"
• pylintPath: "<placeholder>"

sortImports
• args: "<placeholder>"
• path: "<placeholder>"

formatting
• autopep8Args: "<placeholder>"
• autopep8Path: "<placeholder>"
• provider: "autopep8"
• blackArgs: "<placeholder>"
• blackPath: "<placeholder>"
• yapfArgs: "<placeholder>"
• yapfPath: "<placeholder>"

testing
• cwd: "<placeholder>"
• debugPort: 3000
• nosetestArgs: "<placeholder>"
• nosetestsEnabled: undefined
• nosetestPath: "<placeholder>"
• promptToConfigure: true
• pytestArgs: "<placeholder>"
• pytestEnabled: false
• pytestPath: "<placeholder>"
• unittestArgs: "<placeholder>"
• unittestEnabled: false
• autoTestDiscoverOnSaveEnabled: true

terminal
• activateEnvironment: true
• executeInFileDir: "<placeholder>"
• launchArgs: "<placeholder>"

experiments
• enabled: true
• optInto: []
• optOutFrom: []

insidersChannel: "off"

tensorBoard
• logDirectory: "<placeholder>"

@neuf-de-pixel I can't repro the issue. can you provide a log for us to take a look? here are instructions on how to get logs - https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue
also, it would be nice if you can share the file that showing the issue (especially if it is line ending or char code issue)

@neuf-de-pixel I kind of repro this today, for me, it was due to multiple extensions (Pylance and other python tool) trying to do rename that messed up the file.
once I disable/uninstall those conflicting extensions and leave only Pylance in vscode, it worked as expected. have you checked if you uninstall/disable all other extensions and leave pylance only, this still repro?

I will close this issue. please re-open if it repro with latest pylance.

Hi, If someone is looking for a solution please check this other issue: https://github.com/microsoft/vscode-python/issues/17123

Install Pylance extension.
change your vscode setting to use pylance "python.languageServer": "Pylance"


fix: include nodemon dep in the image

Closes #1  😄  Is there any step for pushing to docker hub?

I can't merge it :sweat_smile:


Consider refactoring/renaming items for consistency

With the potential inclusion of QList and CopQ, we will have:
Cop
CopK
CopQ
TList
KList
QList
What about refactoring this into to:
Cop
CopK
CopQ
TList
TListK
TListQ
This simplifies names, IMHO, because the suffix always indicate the kindness. This is in alignment with other libs like cats.
/cc @raulraja @peterneyens @juanpedromoreno @diesalbla

Makes sense.
The suffixes beyond TList and TListK are not as easy though.
I see educational purposes for coproducts for F[_[_], _] and F[_, _[_], _[_], _] (which I dubbed Q).
I have seen the first described as KA (if we follow the same convention, Q would be AKKA :smile:).


Blog Post on When Car Prices will Drop

Codecov Report
Patch and project coverage have no change.

Comparison is base (262da53) 54.95% compared to head (ac4400e) 54.95%.

:exclamation: Current head ac4400e differs from pull request most recent head 535ebde. Consider uploading reports for the commit 535ebde to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##              dev      #41   +/-   ##
=======================================
  Coverage   54.95%   54.95%
=======================================
  Files          16       16
  Lines         555      555
=======================================
  Hits          305      305
  Misses        250      250

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Update Set-CsCallQueue.md

Updating to remove "end of 2023" comment as TAC work has been delayed and will not land by end of year.

@get-itips @msbemba Please and thanks!

@tiburd Please merge this PR. Thanks


Numpy binary format to point cloud formats?

Thanks for providing the tools to convert this into a point cloud but it's limited to really only python programmers or Open3D.  I use a free tool CloudCompare https://www.danielgm.net/cc/ or Meshlab to work with my point clouds.  Is their any chance to convert to .ply format or any of the ones listed in this screen shot?

Any chance to get request/feature tags ?

@gateway Did you manage to save the point cloud data in a file?

Unfortunately no 😕

hello Can now be stored in the point cloud data

抱歉不行😕
newtxt = np.hstack((pts,RGB))
np.savetxt("depth.txt",newtxt);


Re-design constant pools

This is an open-ended issue for re-designing Cranelift's constant pools. In #1377 I added the ability to calculate the address of constants using const_addr and to declare constants in function preambles (e..g const42 = [0 1 2...]). Constant pools are still implemented at the function level, though, so there is no coalescing of constant values across functions.
I added the function-level ConstantPool implementation in order to support SIMD constants (which don't fit in the immediate fields of Cranelift's IR). This is not a pressing issue yet, but before other components start using constants, it might be good to discuss:

should we implement constant pools at the global level and what would this look like?
what should the relocation hooks look like for a more general constant pool implementation? Currently the interface looks like RelocSink::reloc_constant(&mut self, CodeOffset, Reloc, ConstantOffset) and this may need to change.

@cfallin, now that I think I understand the new backend better, I think this issue can be moved a bit further:
How things currently work in the new backend:

at the emission level, MachBuffer::pending_constants is the vector containing the constant values; eventually these get emitted into the buffer and the MachLabels are fixed up
MachBuffer::defer_constant(label, align, data, max_distance) is the user-accessible way to add a constant during emission (e.g. see uses of sink.defer_constant... in emit.rs)
Inst::gen_constant is the user-accessible way to create constant-generating instructions during lowering, but it only accepts values up to u64 in size
so there are problems:

Inst::gen_constant cannot be used to generate vector values
MachBuffer::defer_constant will duplicate constant values
const_addr (a way to retrieve the address of constants for read-only table lookups) does not know which MachLabel to use in MachBuffer; to implement this instruction, we would have to search through MachBuffer::pending_constantsto find a value that matched theConstantDatabehind itsconst_addr's Constant` handle

To simplify the creation of vector constants (all constants, really):

[ ] change the signature of MachInst::gen_constant to accept a DataValue instead of a u64 (involves fixing up 9 uses of this method)
[ ] search through lower.rs to see other places that should be using gen_constant but are not (e.g. using PXOR directly)
[ ] add a way for gen_constant to generate vectors of all 0s (PXOR/XORPS/XORPD) and all 1s (CMPPS/PCMPEQ)
[ ] modify Inst::XmmLoadConstSeq to become XmmLoadConst--instead of emitting the vector inline with the function code it would use sink.defer_constant
all of this suggests some related refactoring:

remove LowerCtx::get_constant: LowerCtx::get_constant and LowerCtx::get_immediate are doing the same thing except that get_constant returns a u64 instead of the larger DataValue
this affects LowerCtx::get_input, which returns a LowerInput with a constant: Option<u64> field--this field could go away (12 uses), replaced by ctx.get_immediate(...)

To keep ConstantPool's de-duplicated values AND allow const_addr to retrieve the address of a constant:

MachBuffer::defer_constant should keep a mapping of constant values to MachLabels (e.g. a HashMap?) and only return the MachLabel for a given value, de-duplicating them
this is redundant work since ConstantPool has already done this, but it is necessary work because lowering could introduce new constant values
I struggle with how to approach this inefficiency (suggestions?): this approach would mean that entire values would have to hashed/compared every time they are used (unlike ConstantPool, which uses Constant(u32) handles)... but perhaps this could be optimized in the future
perhaps we can even genericize the ConstantPool and reuse it?

When the old backend goes away:

ConstantPool can be simplified: ConstantPool::get_offset, ConstantPool::set_offset, binemit::const_disp4 can all go away since they are only necessary to work around old backend quirks.

Hi @abrown -- thanks for the detailed look into this!
MachBuffer::defer_constant is indeed the way forward here; the infra is built to emit constant pools, but just isn't wired up yet.
The API expects the client (so, the lowering code) to allocate its own labels, and specify the label for each constant. So the most straightforward thing to do here would be, for constants in the ConstantPool, make an initial pass over them and allocate labels, keeping them in a table. Then the lookup from constant-pool handle to MachLabel is just an array access. Or, slightly better, we lazily emit deferred constants, and the lookup table holds Option<MachLabel>.
I think we should probably build that first before deduplication at the MachInst-lowering level; I'm not fully convinced that the overhead of a hashmap lookup on every new constant generation is worth the potential code-size reduction (but we should measure).
So I would say we should:

Clean up the constant-related APIs on x64::MachInst and LowerCtx, as you suggest
Add a table to the LowerCtx tracking labels for every constant, emitting on first request. Then we have something like LowerCtx::constant_pool_label(...).
Eventually, deduplicate inside LowerCtx if we find it to be worthwhile.

Yeah, I like this better. I'll try it out and see what happens!


Partial slip boundary conditions

Description of the problem

Either slip or noslip boundary conditions return a way thick boundary layer in coarse mesh simulations such as in unresolved CFD-DEM

Description of the solution

This new boundary condition allows for an intermediary approach, in which you can set a penalty coefficient beta to the normal component and a boundary layer thickness to find the tangential component of the velocity at the boundaries.

How Has This Been Tested?

Fluid passing a cylinder in 2D.
Liquid Fluidized Bed in 3d (first 100 timesteps).

Documentation

Not changed

Future changes

Add this future to the documentation.

Comments

CI is failing :). Can you also add the boundary condition to the Lethe documentation (modifying the rst files)


Cannot include URL query in basename

I have a use case where my react app can be accessed using a URL that contains query parameters, e.g. http://example.com/index.html?foo. I create the history with createBrowserHistory({basename:'/index.html?foo'}). This produces warnings and I believe the path matching will not work. The root cause of the problem is that PathUtils.hasBasename does not escape special characters in prefix to create its regular expression.

The basename does not support query parameters. It's a segment of the pathname.


Timestamp

Is it possible to add timestamp when sending data?

If you have an RTC then yes. I think you need an NTP Server that could send out timestamps to the Arduino which will sync the time and then use them to send the timestamps back to InfluxDB. I think the RTC library from Adafruit can do some lifting.

I have DS3231 clock connected to ESP. So how to send timestamp from DS3231 to Influx? :)


manifest: Explicitly make 'layers' optional

Most folks will distribute images containing layers, but the specified behavior applies cleanly to the layer-less case too.  The unpacked rootfs will just be an empty directory with unspecified attributes.
Folks might want to use that sort of thing for namespace pinning, distributing configs, setting up containers that mount the meat from the host, etc.
Spun off from #318 to focus on a single point.

+1 from me.
I realise there were other issues/PRs trying to make layers list optional that are now closed. What is the main argument against this change?

LGTM. What do you think about adding some language to one of the documents describing the use cases?

On Fri, Oct 21, 2016 at 03:45:12AM -0700, George Lestaris wrote:

What is the main argument against this change?

As far as I can tell, just uncertainty about the usefulness.  I agree that there aren't extremely convincing use cases, but there are a few (referenced in the topic post here).  And in the absence of a good reason to impose the current restriction, I think we should lift it.
On Fri, Oct 21, 2016 at 03:54:58AM -0700, Jonathan Boulle wrote:

LGTM. What do you think about adding some language to one of the documents describing the use cases?

I can do that if you like.  But I imagine folks who want to make images without layers will already have a use case in mind, and folks who want to make images with layers won't care about layer-less use cases, so I'm also fine leaving it as it stands (with some use cases in the commit message to motivate the change, but none in the diff itself).

On Fri, Oct 21, 2016 at 03:54:58AM -0700, Jonathan Boulle wrote:

LGTM. What do you think about adding some language to one of the
documents describing the use cases?

I can do that if you like.  But I imagine folks who want to make
images without layers will already have a use case in mind, and folks
who want to make images with layers won't care about layer-less use
cases, so I'm also fine leaving it as it stands (with some use cases
in the commit message to motivate the change, but none in the diff
itself).

@wking the reason I asked that is because given the countner-argument is
about usefulness, it might be better to clearly justify the usefulness ;-)
On 21 October 2016 at 16:47, W. Trevor King<EMAIL_ADDRESS>wrote:

On Fri, Oct 21, 2016 at 03:45:12AM -0700, George Lestaris wrote:
What is the main argument against this change?
As far as I can tell, just uncertainty about
https://github.com/opencontainers/image-spec/pull/313#pullrequestreview-33010 the
usefulness
https://github.com/opencontainers/image-spec/pull/318#issuecomment-255177345.
I agree that there aren't extremely convincing use cases, but there are a
few (referenced in the topic post here). And in the absence of a good
reason to impose the current restriction
https://github.com/opencontainers/image-spec/pull/313#issuecomment-247624565,
I think we should lift it.
On Fri, Oct 21, 2016 at 03:54:58AM -0700, Jonathan Boulle wrote:
LGTM. What do you think about adding some language to one of the documents
describing the use cases?
I can do that if you like. But I imagine folks who want to make images
without layers will already have a use case in mind, and folks who want to
make images with layers won't care about layer-less use cases, so I'm also
fine leaving it as it stands (with some use cases in the commit message to
motivate the change, but none in the diff itself).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/opencontainers/image-spec/pull/407#issuecomment-255397214,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACewNw1iKSXinSdIN5Eg3g-NR1sW56hKks5q2NCAgaJpZM4KcbbA
.

Lots of earlier discussion in #313, and also around the end of #318.

@wking Could you sum those up into a cohesive argument, rather than linking us to 30 scattered comments?

On Tue, Oct 25, 2016 at 11:32:59AM -0700, Stephen Day wrote:

@wking Could you sum those up into a cohesive argument, rather than
linking us to 30 scattered comments?

My cohesive argument is in the topic post here.

On Tue, Oct 25, 2016 at 11:25:31AM -0700, Jonathan Boulle wrote:

@wking the reason I asked that is because given the countner-argument is
about usefulness, it might be better to clearly justify the usefulness ;-)

I agree that it is good to justify the usefulness in this PR and
commit message to motivate the change in the spec.  I'm just not
clear that it's worth justifying the lack of restriction in the spec
itself.  For many optional settings we don't have in-spec wording
justifying the optionallity.
If we're going to add it, we probably have to go into more details
about the use cases I float in the topic post than I do there (linking
to GitHub comments is fine for commit messages and PR discussion, but
seems less appropriate in the spec itself ;).  If you find my “I don't
think we want the use-cases in the spec” arguments unconvincing, would
you like me to unpack all of that in the ‘layers’ entry itself, or do
you want me to put them somewhere else where they're less distracting
to folks who care more about the normative spec than the informative
background?

@wking Ok, so you ship a container without a filesystem. In docker parlance, we run the following:
$ docker run -it scratch

What could this actually do?
Following from that, let's assume you convinced me the above is not silly:
docker run -it -v /usr/bin:/usr/bin scratch sh

What did we gain versus an empty tar file that makes the empty layers explicit?

On Thu, Oct 27, 2016 at 02:33:59PM -0700, Stephen Day wrote:

@wking Ok, so you ship a container without a filesystem. In docker
parlance, we run the following:
$ docker run -it scratch

What could this actually do?

Probably nothing, although there are currently gaping holes in the
image → runtime-config translation (1 and #87).  If those holes are
filled with something that configures linux.namespaces to create new
namespaces (for all known namespace types?), then the container you
create above would pin its mount namespace 2.  You could launch a
sub-container joining that pinned mount namespace, have the
subcontainer do something interesting, and collect the results from
the pinned mount namespace after the subcontainer died.  Without
namespace pinning, the interesting results might get removed when the
kernel reaped the mount namespace.
Or maybe the scratch config sets up networking and a volume mount to
bind the host's BusyBox and a home directory, and uses BusyBox's httpd
command to serve that bind-mounted home directory.
And if/when the image spec starts distributing runtime-spec configs
instead of the current image-spec configs, this sort of thing will no
longer need to rely on unpack-time namespace injection or run-time
volume-mount completion.

Following from that, let's assume you convinced me the above is not
silly:
docker run -it -v /usr/bin:/usr/bin scratch sh

What did we gain versus an empty tar file that makes the empty
layers explicit?

I can create a manifest that contains no layers using jq.  I'd need to
also pull in tar or dd if I wanted to make an empty tarball.  And gzip
unless something like #332 or #388 lands.  And that layer blob is one
extra round-trip when pushing or pulling from the registry.  So
including an empty layer is not the end of the world, but it seems
like a silly hoop to jump through to satisfy a “must contain at least
one layer” constraint that has no known purpose.

If layers is optional, is rootfs optional, as well?

On Wed, Nov 16, 2016 at 02:54:10PM -0800, Stephen Day wrote:

If layers is optional, is rootfs optional, as well?

I am in favor of an optional ‘rootfs’ 1, but I see that as an
orthogonal issue.  With an empty layers, the unpacked bundle would
have a rootfs directory attributes are unspecified 2.  The
currently-required root.path would point at that directory 3, which
must sit next to the config.json 4.
What the runtime does with that root.path is not an image-spec
concern, but if you're creating a new mount namespace (most likely for
configs unpacked from images), the runtime will pivot into that empty
directory.  If you're joining an existing mount namespace or leaving
the container process in the host mount namespace, the runtime will
presumably ignore root.path 5 (although “not creating a new mount
namespace” is not a concept that the current runtime-spec addresses
clearly).
 Subject: Dropping the rootfs requirement and restoring arbitrary bundle
  content
 Date: Wed, 26 Aug 2015 12:54:47 -0700
 Message-ID<EMAIL_ADDRESS>

From your response, it looks like you have no clue what field I'm talking about. Apologies for not being more precise.
I'm referring to the rootfs field on image config.

On Wed, Nov 16, 2016 at 06:19:15PM -0800, Stephen Day wrote:

I'm referring to the rootfs field on image config.

Ah, thanks for clarifying.  I see a few possible approaches.  In order
of decreasing preference:
a. Land #451.  Freeze application/vnd.oci.image.config.v1+json (which
currently requires rootfs, rootfs.type, and rootfs.diff_ids.  After
a few years, remove the requirement that runtimes support
application/vnd.oci.image.config.v1+json and drop it from the spec.
b. Drop rootfs.type (#224).  Make rootfs and rootfs.diff_ids optional,
regardless of whether layers is set.  When both layers and
rootfs.diff_ids are set, require a one-to-one mapping between
entries.
c. Keep rootfs and rootfs.type required (the current spec).  Make
rootfs.diff_ids optional, regardless of whether layers is set.
When both layers and rootfs.diff_ids are set, require a one-to-one
mapping between entries.
d. Keep rootfs, rootfs.type, and rootfs.diff_ids required (the current
spec).  Require a one-to-one mapping between entries in
rootfs.diff_ids and layers.  When layers is not set, require an
empty array for rootfs.diff_ids.
(d) is pretty much where this PR stands now, although I can add
clarification wording to the diff_ids docs if that's the approach we
want to take.
Personally I don't have a strong opinion on the future of
application/vnd.oci.image.config.v1+json (since I see it being
replaced by the runtime config, #451).  Do you have a preference among
those approaches?

Rejected.
Since this clearly hasn't been thought through, I propose that we close this PR.
@wking How can you possibly propose that runtime config could be a viable replacement for image config? Runtime config is for runtime.

On Thu, Nov 17, 2016 at 02:26:50PM -0800, Stephen Day wrote:

Since this clearly hasn't been thought through, I propose that we
close this PR.

What is the missing piece?  If it is config rootfs handling, are none
of the options I lay out in 1 acceptable?  (a) and (b) have separate
PRs, and the (b) PR has already been rejected, but can you explain
your concerns with (c) and (d)?

@wking How can you possibly propose that runtime config could be a
viable replacement for image config?  Runtime config is for runtime.

This is #451.  I think that's a solid proposal, but for the purpose of
this PR lets say it's not on the table.  That still leaves (c) and (d)
on the table 1, and those both sound like reasonable ways forward to
me.

@wking Do you even have an analysis of doing nothing? That seems like the option with the smallest impact. It seems that you've only suggested options which you possibly agree with. If (c) or (d) are an option, we may be under-specified. The spec should read towards (d), but requires due diligence before doing so.

This is #451.  I think that's a solid proposal, but for the purpose of
this PR lets say it's not on the table.  That still leaves (c) and (d)
on the table [1], and those both sound like reasonable ways forward to
me.

#451 continues to propagate the fallacy that image config and runtime config are equivalent entities and that having them be so tightly related leads to solid design. I have left a rejection message on the issue outlining the main problems with the proposal.

On Mon, Nov 21, 2016 at 12:24:14PM -0800, Stephen Day wrote:

@wking Do you even have an analysis of doing nothing?

As in “closing this PR”?  That just means folks who want an empty
rootfs need to jump through some extra hoops 1.  I agree that it has
low impact on the spec (tautologically?), but I see no reason to
require that hoop jumping.

If (c) or (d) are an option, we may be under-specified. The spec
should read towards (d), but requires due diligence before doing so.

I think the current spec is clear enough on this point, requiring both
rootfs.diff_ids (in the config) and layers (in the manifest).  This PR
is interested in making layers optional.  I don't really care if
rootfs.diff_ids becomes optional or not (which is why (c) and (d) are
both on the table).  As this PR stands, rootfs.diff_ids is still
clearly required 2.  If you like (d) better than (c), I can add
wording like:
If the manifest's layers is empty or unset, diff_ids MUST be an
empty array.
But that's mostly to help orient people.  I think the spec would be
unambigous (but with slightly less context) without such an addition.

@wking What can you exec in the container if there is no rootfs?

On Wed, Jan 18, 2017 at 04:16:06PM -0800, Stephen Day wrote:

@wking What can you exec in the container if there is no rootfs?

You could exec in that container with execveat(2), although there's
not a convenient runtime-spec syntax to invoke that (ccon supports it
1).
However, I expect a more common use-case will be for a wrapping
container that has a nested container launched inside it 2 (although
#492 currently has nothing to say about which namespaces get setup in
the generated runtime-spec config).  In this case, you are unlikely to
ever call ‘start’ on the wrapper container.
Or the meat of the filesystem might be provided by a volume mount 2,
in which case you can exec anything you mounted in.

@wking I don't see the value in rehashing this pre-1.0.
Let's revisit this after a release.

On Fri, Jan 20, 2017 at 03:48:55PM -0800, Stephen Day wrote:

@wking I don't see the value in rehashing this pre-1.0.
Let's revisit this after a release.

Then maybe leave this PR open, milestone it post-v1.0.0, and tag it
priority/Pmaybe?

I feel that this should not be explicitly called out. If a use-case is binding mounting root from the host, then they can use a 512byte+1024byte empty tar archive (header + nil bytes).

On Wed, Mar 08, 2017 at 03:00:58PM -0800, Vincent Batts wrote:

I feel that this should not be explicitly called out.

Explicitly called out by using OPTIONAL 1?  That's not shining a
particularly large spotlight.

If a use-case is binding mounting root from the host, then they can
use a 512byte+1024byte empty tar archive (header + nil bytes).

You don't even need the record, you can just use 1024 zero bytes (‘dd’
invocation for creating that in 2).  I just think that's a pretty
silly hoop to make folks jump through, and @glestaris 3, @jonboulle
4, @runcom (#308), and @coolljt0725 (#313) all at one point seemed
in favor of dropping the hoop.  @runcom seems to have made the change
in favor of consistency 5, and I expect doesn't really care whether
‘layers’ is optional as long as everyone's consistent.
But whatever, if that's a hoop you want to make layer-less folks jump
through, it's not a huge hoop.

@vbatts workaround seems viable TBH. It's a bit of an ugly workaround but I don't have a real use case that opposes it right now.

@glestaris good to hear


deeplearning.net is down; datasets unreachable

The website http://deeplearning.net has been down for a while, meaning it has been impossible for several days to download some of the datasets in the tutorial (MNIST for example) through the provided download links.

+1

+1

Here is a workaround using Torchvision's dataset for MNIST:
import os
import torchvision.datasets as datasets
root = '../data'
if not os.path.exists(root):
    os.mkdir(root)

# if not exist, download mnist dataset
train_set = datasets.MNIST(root=root, train=True, download=True)
test_set = datasets.MNIST(root=root, train=False, download=True)

x_train, x_valid = train_set.train_data.split([50000, 10000])
y_train, y_valid = train_set.train_labels.split([50000, 10000])

Note that x_train, x_valid etc. are already tensors now (no need to map them) and they are already shaped like (50000, 28, 28). The unit tests are changed to following:
assert x_train.shape == (50000, 28, 28)
assert m == y_train.shape[0] == 50000
test_eq(y_train.min(),0)
test_eq(y_train.max(),9)

This should work (at least x_train[0] give me the same image of the handwritten 5).

Here is a workaround using Torchvision's dataset for MNIST:
import os
import torchvision.datasets as datasets
root = '../data'
if not os.path.exists(root):
    os.mkdir(root)

# if not exist, download mnist dataset
train_set = datasets.MNIST(root=root, train=True, download=True)
test_set = datasets.MNIST(root=root, train=False, download=True)

x_train, x_valid = train_set.train_data.split([50000, 10000])
y_train, y_valid = train_set.train_labels.split([50000, 10000])

Note that x_train, x_valid etc. are already tensors now (no need to map them) and they are already shaped like (50000, 28, 28). The unit tests are changed to following:
assert x_train.shape == (50000, 28, 28)
assert m == y_train.shape[0] == 50000
test_eq(y_train.min(),0)
test_eq(y_train.max(),9)

This should work (at least x_train[0] give me the same image of the handwritten 5).


com.twitter.finatra.utils.ResponseUtils for 2.0.0.M2 missing functions used in examples

Released util jar contains is5xxResponse, is4xxOr5xxResponse, and errorClass while main contains many more https://github.com/twitter/finatra/blob/0235a81bd81bc6118f9533e69a948312604f8afc/utils/src/main/scala/com/twitter/finatra/utils/ResponseUtils.scala

@schrepfler the next release is coming very soon. Thanks!


empty version (or project (?)) cause regex matching crash

Found what I think is a bug in the header parsing.  This project commented out their version number resulting in an empty Version in the header to the objects.inv:
sven:/tmp> wget https://bootstrap-datepicker.readthedocs.io/en/master/objects.inv
sven:/tmp> head -4 objects.inv
# Sphinx inventory version 2
# Project: bootstrap-datepicker
# Version:
# The remainder of this file is compressed using zlib.
sven:/tmp> sphobjinv convert plain objects.inv

Error: Unrecognized file format

If you do it directly, you get information that seems to mean that you assume Version and Project actually have values after them (and apparently they don't need to):
>>> import sphobjinv as soi
>>> inv = soi.Inventory('objects.inv')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<attrs generated init d264050f79466679381c6c61e7053ac5e806eac0>", line 16, in __init__
  File "/usr/local/lib/python3.6/site-packages/sphobjinv/inventory.py", line 365, in __attrs_post_init__
    self._general_import()
  File "/usr/local/lib/python3.6/site-packages/sphobjinv/inventory.py", line 598, in _general_import
    import_errors[st]):
  File "/usr/local/lib/python3.6/site-packages/sphobjinv/inventory.py", line 612, in _try_import
    p, v, o = import_fxn(src)
  File "/usr/local/lib/python3.6/site-packages/sphobjinv/inventory.py", line 659, in _import_plaintext_fname
    return self._import_plaintext_bytes(b_plain)
  File "/usr/local/lib/python3.6/site-packages/sphobjinv/inventory.py", line 629, in _import_plaintext_bytes
    b_res = pb_version.search(b_str).group(HeaderFields.Version.value)
AttributeError: 'NoneType' object has no attribute 'group'

I think you want to change .+ to be .*?
https://github.com/bskinn/sphobjinv/blob/11db748f5e31145ee7ec97d5436ee50aeadc0bc4/sphobjinv/re.py#L42
https://github.com/bskinn/sphobjinv/blob/11db748f5e31145ee7ec97d5436ee50aeadc0bc4/sphobjinv/re.py#L51
And then it will return you empty strings?

Keep an eye out for a v2.0.1rc1 release here soon, it'll get this fix out there before I take care of the stdio-mgr problem.  pip install -U --pre sphobjinv should grab it once I get it up to PyPI.

v2.0.1rc1 is published, @svenevs


table component filter autofocus

First of all, thanks for this nice component!
How is it possible to add autofocus to input filter of table?
And one more question, how can I select the string automatically after enter something to filter?
Thanks a lot

Autofocus isn't possible out of the box. You could achieve it by writing some custom JavaScript outside of the component.
What do you mean by selecting the string? If you mean highlighting the result, that's outside of the scope of this package.


BR (Bayerischer Rundfunk Mediathek) extractor broken after site redesign

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.11.15. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2017.11.15

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[x] Site support request (request for adding support for a new site)
[x] Feature request (request for a new functionality)
[ ] Question
[ ] Other

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
[zlatko@disclosure:~]$ youtube-dl -v -F "https://www.br.de/mediathek/video/dokthema-gegen-die-marihuana-mafia-wo-cannabis-und-kriminalitaet-bluehen-av:59d4b52750223b0012a19718"
[debug] System config: []
[debug] User config: [u'--proxy', u'', u'--rate-limit', u'20M']
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'-F', u'https://www.br.de/mediathek/video/dokthema-gegen-die-marihuana-mafia-wo-cannabis-und-kriminalitaet-bluehen-av:59d4b52750223b0012a19718']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.11.15
[debug] Python version 2.7.14 -<EMAIL_ADDRESS>[debug] exe versions: ffmpeg 3.4, ffprobe 3.4, rtmpdump 2.4
[debug] Proxy map: {}
[generic] dokthema-gegen-die-marihuana-mafia-wo-cannabis-und-kriminalitaet-bluehen-av:59d4b52750223b0012a19718: Requesting header
WARNING: Falling back on generic information extractor.
[generic] dokthema-gegen-die-marihuana-mafia-wo-cannabis-und-kriminalitaet-bluehen-av:59d4b52750223b0012a19718: Downloading webpage
[generic] dokthema-gegen-die-marihuana-mafia-wo-cannabis-und-kriminalitaet-bluehen-av:59d4b52750223b0012a19718: Extracting information
ERROR: Unsupported URL: https://www.br.de/mediathek/video/dokthema-gegen-die-marihuana-mafia-wo-cannabis-und-kriminalitaet-bluehen-av:59d4b52750223b0012a19718
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 2170, in _real_extract
    doc = compat_etree_fromstring(webpage.encode('utf-8'))
  File "/usr/local/bin/youtube-dl/youtube_dl/compat.py", line 2539, in compat_etree_fromstring
    doc = _XML(text, parser=etree.XMLParser(target=_TreeBuilder(element_factory=_element_factory)))
  File "/usr/local/bin/youtube-dl/youtube_dl/compat.py", line 2528, in _XML
    parser.feed(text)
  File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1659, in feed
    self._raiseerror(v)
  File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1523, in _raiseerror
    raise err
ParseError: syntax error: line 1, column 0
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 784, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 437, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 3075, in _real_extract
    raise UnsupportedError(url)
UnsupportedError: Unsupported URL: https://www.br.de/mediathek/video/dokthema-gegen-die-marihuana-mafia-wo-cannabis-und-kriminalitaet-bluehen-av:59d4b52750223b0012a19718

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://www.br.de/mediathek/video/dokthema-gegen-die-marihuana-mafia-wo-cannabis-und-kriminalitaet-bluehen-av:59d4b52750223b0012a19718
Single video: https://www.br.de/mediathek/video/monaco-110-die-wildsau-av:59d4b655293bac0012535043
Single video: https://www.br.de/mediathek/video/hubert-und-staller-rutschpartie-av:59d4b655293bac0012535035

More videos at https://www.br.de/mediathek/.

Description of your issue, suggested solution and other information
The "br.py" extractor doesn't feel responsible anymore because the video URL schema has changed with the site redesign, and the fallback generic extractor can't make any sense of it, either.

Already reported in #14560


Feature/attach to unnamed buffer

Resolves #1926
This adds a boolean option to the config: unnamed_buffer_support with default of false that allows spawning the LSP server with vim.fn.cwd() so that we have linting and diagnostics even though we are in an unnamed buffer.
Relevant only if single_file_support is true

why make this optional? If we know the filetype that's all that matters.

unnamed_buffer_support
When working with restFull API its a common practice to copy the JSON returned from the server and paste it in the editor for a quick analysis and editing if required. Having the ability to format without saving the file is useful as the file is temporary.

This use case is well supported in VSCode and having the same in neovim would avoid having to switch editors just to format a temporary file.

@mosheavni  ci failed because you used the util.path.dirname in root_dir most information check .
https://github.com/neovim/nvim-lspconfig/blob/master/CONTRIBUTING.md#adding-a-server-to-lspconfig.

@mosheavni ci failed because you used the util.path.dirname in root_dir most information check . https://github.com/neovim/nvim-lspconfig/blob/master/CONTRIBUTING.md#adding-a-server-to-lspconfig.

I can see that :) however. that doesn't make a lot of sense.

This was not the case for example on coc.nvim.
It's mind-boggling why this is still unanswered.


BottomNavBar padding and borderRadius

for BottomNavBar I have a few customItems, like for messages, whenever you've unread messages, it shows text above the icon, that's why icons feel like attached to the bottom of the screen. That's why I need to add padding. Also, need to add borderRadius

borderRadius like this

@vusters @sharjeelyunus
PR - https://github.com/EnsembleUI/ensemble/pull/873


Parameterise OpenAIToken, Timeout and RetryConfig

In previous work we had a need to influence the configuration of our retry methods and timeouts since sometimes for long or complex tasks the reply from the LLM can take quite some time to solve.
So we need to be able to configure the CoreAIScope  to take into account custom configurations.
In addition we don't want to force library authors, or end-users to setup environment configurations for the OpenAIToken so we should also parameterise this in a Config class rather than the current hard-coded environment variable.  https://github.com/xebia-functional/xef/blob/6831f30d6440138bd873bf446a2b67929556bc44/openai/src/commonMain/kotlin/com/xebia/functional/xef/auto/llm/openai/OpenAI.kt#L47

With the changes that we planning to do maybe this issue pass to be obsolete... What do you think @anamariamv , can we close?


Fix generator spec failure

Summary
Remove this paragraph and describe the code changes in your pull request... were there any bugs you had fixed? If so, mention them. If these bugs have open GitHub issues, tag them here as well to keep the conversation linked.
Pull Request checklist
Remove this line after checking all the items here. If the item does not apply to the PR, both check it out and wrap it by ~.

[ ] Add/update test to cover these changes
[ ] Update documentation
[ ] Update CHANGELOG file

Other Information
Closes #395

Thank you @ahangarha


Processing properties are not required on providers #8

Attempt to clarify requirements, fixes #8. @l0b0

Merging for now. Additional changes (e.g. https://github.com/stac-extensions/processing/pull/13#discussion_r774127591) can be added in a new PR.


In case no rule id exists, log file name & line number in debug log

Fixes several NULL pointers use.
In case no rule id exists, log file name & line number in debug log.
Obsoletes https://github.com/owasp-modsecurity/ModSecurity/pull/2950 (corrupted).

Unclean PR, to be replaced by another one


jinja2 template support with django-jinja help

What is the reason to have jinja2 support for django-material?
I made django-material for projects with complex forms like http://forms.viewflow.io/demo/bank/
The time required to fill the form is much greater than time to render. There is no reason to speed up template rendering.
Is there any advantages in template syntax that could be implemented with jinja2? Could we simplify {% parts %} redefinition somehow?

not fully sure about all your queries right now, but django 1.10 will ship the template based form rendering mechanism where jinja2 and dtl both will be supported.

So, what? Supporting jinja2 in django-material doubles amount of work required. What is the reason to do that?

https://github.com/niwinz/django-jinja/blob/strip/doc/content.adoc#rationale
I will be helping you to get that completed.

Still see no reasons


Limited migration from OMIVV to OMEVV

Requirement Breakdown
Details

Objective

Authentication/Authorization

List of the tasks in the workflow (in   order)

Module type: Library and/or executable

Input and format

Expected output and format   Export required

Concurrency requirement.

Execution model: synchronous or   asynchronous

Applicable timeouts and retries

Expected error handing

Expected domain specific validation

https://github.com/dell/omivv/pull/54


[UX-006] - Account selection in menu

What happened?
Since the latest updates, the account selection functionality in the Pali Wallet menu has changed, negatively impacting the user experience.
Previously, when selecting an account, the menu would automatically close, and the selected account would immediately display in the interface. However, now, when the user selects an account, it is only marked with a green icon, but the menu does not close automatically.
https://github.com/user-attachments/assets/0c6bed80-d5c0-422a-b14e-7cfc4d641fda
This forces the user to take an additional step: manually clicking outside the menu to close it.

This is inconvenient, as the only available area to close the menu is a small space marked in red, which is uncomfortable and unintuitive. Moreover, if the user clicks outside the Pali Wallet window, the app closes in the background, causing even more friction.
To enhance the user experience, it is suggested that once the user selects an account, the menu should close automatically, allowing immediate interaction with the interface without unnecessary steps.
Version
v3.0.0 QA
What platform are you using?
macOS
What browser are you using?
Brave
Is this a trezor issue?
No
Relevant log output
No response

✅ Solved in v<IP_ADDRESS>


Update upload-pages-artifact to v1.0.9

  - name: Upload GitHub Pages artifact
    uses<EMAIL_ADDRESS>

#62 closes #61


Add docs for custom http header

docs for commit 850c1c4f55ea02c56f8b7c1cd12e9431e9919ac6

Hmm. I would like to support it, but I'm not thrilled about the naming presently (and kind of forgot about that change). Could you describe how you are using it to provide some context? Thanks!

but I'm not thrilled about the naming presently

yea me too :P
I'm using a custom header for client authorization, the header's name is something like X-AppName-Api-Key.
how about ? "http_header": { "X-App-Api-Key": "abcdef" }

Yeah. I guess that seems like it might be kind of limiting. Also the http part seems redundant.
My gut feeling would be to just use a headers key and expect that the value was a schema. So the actual keys would be nested under a properties key and could have format info, description, etc. It also opens up the possibility of using required and similar things to specify which headers must be included.
What do you think?

@geemus
I totally agree with you. Actually when I first tried to write the definitions for custom headers, I expected that kind of implementation.
But I guess those updates will break backward compatibility so I guess the steps will be

Add docs for the current implementation(this PR)
Update the implementation(like the design you posted above)
Update the docs

wdyt? :o

Sounds reasonable. Once we have made the changes I guess we can then just allow the old way to work, but maybe print a deprecation warning or something?

Would you be up for working on the updates?

Once we have made the changes I guess we can then just allow the old way to work, but maybe print a deprecation warning or something?

Sounds nice :)

Would you be up for working on the updates?

Yea sure! Think I'll be able to create the PR this weekend :)

Awesome, thanks for working through the ideas with me. I look forward to the PR and just let me know if you have further questions or concerns. Thanks!

np thank you too! :D


Auto-unzipping of cbcollects doesn't work in Python 3.7 and earlier

Because the unzipping code uses ZipFile.Path which was only introduced in 3.8. It should be relatively easy to remove this dependency on Path if we find the time to get around to it.

Have decided that Python 3.8 or later is needed


Support for kv backend version 2

I'd love to see support for version 2 of the kv backend, I'd really like to use the versioning functionality that it added.

Hi @andrewl3wis,
I'll release an update at the end of the weekend.
Cheers,
Björn

Hi @andrewl3wis,
I've implemented the versioned kv 2 engine support.
If you are upgrading to the new version 1.2.0 please also reapply the custom resource definition.
For more information please see https://vault.koudingspawn.de/supported-secret-types/secret-type-keyvaluev2
Cheers,
Björn


Safari Database Enumeration

SwiftBelt does not enumerate the Safari database when /Applications/Safari.app/Contents/MacOS/Safari is not running on macOS 10.15.5.
zeroCool$ ps aux | grep -i safari
zeroCool          1228   0.0  0.8  4341064  17736   ??  S     7:25AM   0:01.67 /System/Library/PrivateFrameworks/SafariSafeBrowsing.framework/com.apple.Safari.SafeBrowsing.Service
zeroCool          1224   0.0  0.5  4317712   9848   ??  S     7:25AM   0:00.07 /Library/Apple/System/Library/CoreServices/SafariSupport.bundle/Contents/MacOS/SafariLaunchAgent
zeroCool          1216   0.0  0.5  4314568   9624   ??  S     7:25AM   0:00.14 /System/Library/PrivateFrameworks/SafariShared.framework/Versions/A/XPCServices/com.apple.Safari.History.xpc/Contents/MacOS/com.apple.Safari.History
zeroCool           825   0.0  0.6  4315148  12048   ??   Does not use any command line utilities
author: @cedowens
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

##########################################
==>Browser History Info:

***************Quarantine History Results for user zeroCool***************
Date: 1989-06-05 14:26:31 | App: com.apple.Safari | File: https://raw.githubusercontent.com/cedowens/SwiftBelt/master/SwiftBelt | OriginURL:
Date: 1989-06-05 14:31:55 | App: com.google.Chrome | File: https://raw.githubusercontent.com/cedowens/SwiftBelt/master/SwiftBelt | OriginURL: https://github.com/cedowens/SwiftBelt/blob/master/SwiftBelt
Date: 1989-06-05 15:00:49 | App: com.apple.Safari | File: https://raw.githubusercontent.com/cedowens/SwiftBelt/master/SwiftBelt | OriginURL: https://github.com/cedowens/SwiftBelt/blob/master/SwiftBelt

***************Safari history results for user zeroCool***************
[-] Could not open the Safari History.db file for user zeroCool

I killed all of the running processes one by one and the results stayed the same:
zeroCool$ ps aux | grep -i safari
zeroCool          1432   0.0  0.0  4278064    284 s001  R+    8:05AM   0:00.00 grep -i safari
zeroCool$ ./SwiftBelt -BrowserHistory
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 _______  _     _  ___   _______  _______  _______  _______  ___      _______
|       || | _ | ||   | |       ||       ||  _    ||       ||   |    |       |
|  _____|| || || ||   | |    ___||_     _|| |_|   ||    ___||   |    |_     _|
| |_____ |       ||   | |   |___   |   |  |       ||   |___ |   |      |   |
|_____  ||       ||   | |    ___|  |   |  |  _   | |    ___||   |___   |   |
 _____| ||   _   ||   | |   |      |   |  | |_|   ||   |___ |       |  |   |
|_______||__| |__||___| |___|      |___|  |_______||_______||_______|  |___|

SwiftBelt: A MacOS enumerator similar to @harmjoy's Seatbelt. Does not use any command line utilities
author: @cedowens
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

##########################################
==>Browser History Info:

***************Quarantine History Results for user zeroCool***************
Date: 1989-06-05 14:26:31 | App: com.apple.Safari | File: https://raw.githubusercontent.com/cedowens/SwiftBelt/master/SwiftBelt | OriginURL:
Date: 1989-06-05 14:31:55 | App: com.google.Chrome | File: https://raw.githubusercontent.com/cedowens/SwiftBelt/master/SwiftBelt | OriginURL: https://github.com/cedowens/SwiftBelt/blob/master/SwiftBelt
Date: 1989-06-05 15:00:49 | App: com.apple.Safari | File: https://raw.githubusercontent.com/cedowens/SwiftBelt/master/SwiftBelt | OriginURL: https://github.com/cedowens/SwiftBelt/blob/master/SwiftBelt

***************Safari history results for user zeroCool***************
[-] Could not open the Safari History.db file for user zeroCool

Thanks for reporting. I have not been able to replicate this issue...on my test systems I have been able to pull Safari history even when it is running. I will continue to investigate and test on more systems to see if I can troubleshoot the issue you encountered.


ssl issues

Hello, I am not an expert programmer, but recently having SSL issues using mapa. Could it be that it needs some update here? Thank you! "URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:997)>"

Hi @winroger 👋
thanks for bringing this to my attention. Even though the error appeared slightly different on my end [1] I guess it stems from the same root cause. Turns out the planetary computer requires to sign the stac catalogue items. Not sure when this changed, but I implemented the required changes to make it work again. Please try v0.13.0 that I just released and let me know your findings 🙂
[1]
HTTP Error: Public access is not permitted on this storage account


Fix ActOnEveryObject missing changes when SuppressChangeNotifications is used

Copied from PR #1685, this is the same PR but against the master branch instead of develop.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix.
What is the current behavior? (You can also link to an open issue here)
Previously ActOnEveryObject() would not handle list changes correctly if the changes were made while SuppressChangeNotifications() was used. This is because SuppressChangeNotifications() currently publishes a reset Changing notification after the changes have been made. See issue #1675.
What is the new behavior (if this is a feature change)?
SuppressChangeNotifications() now publishes the reset Changing notification before the changes are made, when the suppression is first enabled.
What might this PR break?
Protected virtual method publishResetNotification() is removed. It is not used in the class anymore and current subclasses might be overriding it because it affects Reset() and SuppressChangeNotifications(), which it doesn't anymore.
Please check if the PR fulfills these requirements

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Other information:

To pass the failing test you'll need to remove line 601 where it references publishResetNotification
We have API checker that confirms the API hasn't changed, and since you have a potentially breaking change we'll have to update the approved API.
https://github.com/reactiveui/ReactiveUI/blob/master/src/ReactiveUI.Tests/API/ApiApprovalTests.ReactiveUI.approved.txt

To echo what @glennawatson has said, if you run the tests locally, you'll get an "actual" output and an "approved" if you update the approved with the actual, it should make the test happier :)

I removed the line, but the error seems to persist. I'm not sure what the problem is...

I'll grab your branch today and see what's going on.

When I run build.cmd it shows the following error message:
Failed Approval: Received file C:\OpenSource\branch\ReactiveUI\src\ReactiveUI.Tests\API\ApiApprovalTests.ReactiveUI.received.txt does not match approved file C:\OpenSource\branch\ReactiveUI\src\ReactiveUI.Tests\API\ApiApprovalTests.ReactiveUI.approved.txt.
The files have to byte match. Changed it for you.

Thank you!


Add namespace to CSS styles

So we don't conflict with other page styles
I couldn't find any refrence to color-x classes. Probably safe to remove. I think it should've been removed here:
https://github.com/toggl/toggl-button/commit/f46081443e82ee87713b72b85b12987907693d4e
Thoughts?
Closes #779

As per discussed, probably some other extension interfering with Toggl Button.
Seems to be working.
I also removed the unused CSS classes. Made a reference to that on the commit.