Fix multiple issues of traffic_layout and add a readme

What is updated:

init can create certain directories if not found in the original installed location.
init --force can overwrite existing runroot.
verify do not stop upon finding non-existing directories.
verify can verify the permission of default installed location.
verify --fix can produce messages about what permission is fixed.
If hard-linking executable fails during creating runroot, init will fall back to a normal copy.
Add a README to traffic_layout.

Gotcha. I will fix it @zwoop


Component's name is not used when rendering the changelog

Use the following configuration

project_url = "https://github.com/informalsystems/ibc-rs"

[components]
general_entries_title = "General"
entry_indent = 2

    [components.all]
    ibc             = { name = "IBC Modules",     path = "modules" }
    ibc-relayer     = { name = "Relayer Library", path = "relayer" }
    ibc-relayer-cli = { name = "Relayer CLI",     path = "relayer-cli" }
    guide           = { name = "Guide",           path = "guide" }

Click to show full config
# The GitHub URL for your project.
#
# This is mainly necessary if you need to automatically generate changelog
# entries directly from the CLI. Right now we only support GitHub, but if
# anyone wants GitLab support please let us know and we'll try implement it
# too.
project_url = "https://github.com/informalsystems/ibc-rs"

# The file to use as a Handlebars template for changes added directly through
# the CLI.
#
# Assumes that relative paths are relative to the `.changelog` folder. If this
# file does not exist, a default template will be used.
change_template = "change-template.md"

# The number of characters at which to wrap entries automatically added from
# the CLI.
wrap = 80

# The heading right at the beginning of the changelog.
heading = "# CHANGELOG"

# What style of bullet to use for the instances where unclog has to generate
# bullets for you. Can be "-" or "*".
bullet_style = "-"

# The message to output when your changelog has no entries yet.
empty_msg = "Nothing to see here! Add some entries to get started."

# The name of the file (relative to the `.changelog` directory) to use as an
# epilogue for your changelog (will be appended as-is to the end of your
# generated changelog).
epilogue_filename = "epilogue.md"

# Settings relating to unreleased changelog entries.
[unreleased]

# The name of the folder containing unreleased entries, relative to the
# `.changelog` folder.
folder = "unreleased"

# The heading to use for the unreleased entries section.
heading = "## Unreleased"

# Settings relating to sets (groups) of changes in the changelog. For example,
# the "BREAKING CHANGES" section would be considered a change set.
[change_sets]

# The filename containing a summary of the intended changes. Relative to the
# change set folder (e.g. `.changelog/unreleased/breaking-changes/summary.md`).
summary_filename = "summary.md"

# The extension of files in a change set.
entry_ext = "md"

# Settings related to components/sub-modules. Only relevant if you make use of
# components/sub-modules.
[components]

# The title to use for the section of entries not relating to a specific
# component.
general_entries_title = "General"

# The number of spaces to inject before each component-related entry.
entry_indent = 2

    # The components themselves. Each component has a name (used when rendered
    # to Markdown) and a path relative to the project folder (i.e. relative to
    # the parent of the `.changelog` folder).
    [components.all]
    ibc             = { name = "IBC Modules",     path = "modules" }
    ibc-relayer     = { name = "Relayer Library", path = "relayer" }
    ibc-relayer-cli = { name = "Relayer CLI",     path = "relayer-cli" }
    guide           = { name = "Guide",           path = "guide" }

Add a new entry for the ibc-relayer component (or any other of the components listed above)

❯ unclog add -i some-new-feature \
>   -n 23 \
>   -c ibc-relayer \
>   -s breaking-changes \
>   -m "Some *new* feature"
15:47:31 [INFO] Attempting to load configuration file from: .changelog/config.toml
15:47:31 [INFO] Loading change template from: .changelog/change-template.md
15:47:31 [INFO] Created directory: .changelog/unreleased/breaking-changes
15:47:31 [INFO] Created directory: .changelog/unreleased/breaking-changes/ibc-relayer
15:47:31 [INFO] Wrote entry to: .changelog/unreleased/breaking-changes/ibc-relayer/23-some-new-feature.md

Build the changelog

❯ unclog build --unreleased
15:47:58 [INFO] Attempting to load configuration file from: .changelog/config.toml
15:47:58 [INFO] Attempting to load changelog from directory: .changelog
15:47:58 [INFO] Success!
## Unreleased

### BREAKING CHANGES

- [ibc-relayer](relayer)
  - Some *new* feature ([#23](https://github.com/informalsystems/ibc-
    rs/issues/23))

Notice that the top-level item for the ibc-relayer components does not use the name provided in the configuration (ibc-relayer instead of Relayer Library)

Thanks for reporting this! :pray: Please check if #20 resolves it for you?


feat(factories): add shorthand factory

/cc @jcarbo @layershifter
This PR refactors factories and updates all shorthand usages to use them.  We still have predefined factories as before:
createIcon()
createImage()
createHTMLImage()  // renamed from createImg
createLabel()

Our new createShorthand factory does the same thing as the previous Factory in createFactory did before.  It has just been refactored to allow standalone use.
createShorthand(Component, mapValueToProps, val, extraProps = {}) {...}

Our predefined factories are created by partially applying the new createShorthand factory:
function createShorthandFactory(Component, mapValueToProps) {
  return _.partial(createShorthand, Component, mapValueToProps)
}

const createIcon = createShorthandFactory(Icon, value => ({ name: value }))
// ...

This refactored factory makes it usable for previously non-reusable shorthand.  Specifically, where the component was not something that would be used elsewhere:
This...
{header && <DropdownHeader content={header} />}

Becomes...
{createShorthand(DropdownHeader, val => ({ content: val }), header)}

The Dropdown header shorthand now receives all the benefits of regular shorthand.  It can be created from a string, props object, or an element.
This shorthand factory can easily be extended later to handle arrays.  Then, it will also generate a key for each child.  If a key could not be generated, it will require the user to provide a childKey prop.  That is for another PR.

Current coverage is 98.75% (diff: 95.23%)

Merging #529 into master will increase coverage by 0.01%

@@             master       #529   diff @@
==========================================
  Files           107        108     +1
  Lines          1754       1769    +15
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1732       1747    +15
  Misses           22         22
  Partials          0          0

Powered by Codecov. Last update 916c9d6...dd4b247

Looks awesome :+1:

This is great! 😍


Simplify status handling and dropping of collections

Scope & Purpose
Enterprise companion PR: https://github.com/arangodb/enterprise/pull/1190
Simplify status handling and dropping of collections.
Previously, collections had statuses corrupted, loaded, and deleted. In addition there was an atomic boolean flag that indicated whether a collection was deleted or not.
This PR removes all the different collection status, and only keeps the deletion flag. A collection will report as being loaded in case it is not deleted, and deleted otherwise. The status corrupted is not necessary, and hasn't been effectively used before. It only played a role with MMFiles collections, which are not present anymore.
This also allowed removing functions for return the status of a collection. To keep things downwards-compatible, a few places that return a collection's status had to be hard-coded.
In addition, a collection's _useRevisionsAsDocumentIds flag was changed from an atomic boolean to a non-atomic boolean, because its value is only set in the constructor of LogicalCollection, and then never changed later.
The dropping of collections inside TRI_vocbase_t has also been simplified. Previously dropping was started in a dropCollection method, which called into a dropCollectionWorker() function. Both functions had internal loops to repeat the drop action in case it didn't succeed initially. This is now simplified, so that only dropCollectionWorker() retries until success.
The max timeout for dropping a collection has also been removed from the dropCollection() call, as dropping should always succeed eventually. If this is not the case, it indicates a bug or a resource leak (leaked collection object with the status lock still acquired).

[ ] :hankey: Bugfix
[ ] :pizza: New feature
[ ] :fire: Performance improvement
[x] :hammer: Refactoring/simplification

Checklist

[ ] Tests

[ ] Regression tests
[ ] C++ Unit tests
[ ] integration tests
[ ] resilience tests

[ ] :book: CHANGELOG entry made
[ ] :books: documentation written (release notes, API changes, ...)
[ ] Backports

[ ] Backport for 3.10: -
[ ] Backport for 3.9: -
[ ] Backport for 3.8: -

Related Information

[ ] Docs PR:
[x] Enterprise PR: https://github.com/arangodb/enterprise/pull/1190
[ ] GitHub issue / Jira ticket:
[ ] Design document:

In file included from /work/ArangoDB/arangod/VocBase/LogicalCollection.h:37,
                 from /work/ArangoDB/arangod/Utils/Events.h:32,
                 from /work/ArangoDB/arangod/VocBase/VocbaseInfo.cpp:36:
/work/ArangoDB/arangod/VocBase/LogicalDataSource.h:68:63: error: missing binary operator before token "("
   68 | #if defined(ARANGODB_ENABLE_MAINTAINER_MODE) && !__has_feature(thread_sanitizer)
      |

@MBkkt : I think we should not complicate it any further. This surroundings of setting the atomic boolean are a detail that doesn't affect behavior or performance.
I think the PR is ok as it is (provided Jenkins likes it too). My only goal now for be to land this PR.


Add example to Basic Usage in doc

@densmirn Maybe change description somehow to avoid words repetition?
The code below illustrates a typical ML workflow that consists of data pre-processing and predicting stages. Intel SDC is intended to compile data pre-processing stages that includes reading dataset from a csv file, data filtering and performing Pearson Correlation operation. The prediction based on   gradient boosting regression module is made using scikit-learn module.

@samaid Can we use your script based on "prices" dataset here as an example of SDC usage?

Tests failed.
When I tried to run it locally on pure pandas (0.25.3) it is also failed. Had to change columns=('symbol', 'volume') -> columns=['symbol', 'volume']

Tests failed.
When I tried to run it locally on pure pandas (0.25.3) it is also failed. Had to change columns=('symbol', 'volume') -> columns=['symbol', 'volume']

The example shouldn't be ran on pure Pandas. We need sklearn to run the example. So these are 2 options. First one is to skip the example somehow. Second one is to install sklearn to CI environment. @Vyacheslav-Smirnov what option is better to select and how to reach selected option?

Tests failed.
When I tried to run it locally on pure pandas (0.25.3) it is also failed. Had to change columns=('symbol', 'volume') -> columns=['symbol', 'volume']

The example shouldn't be ran on pure Pandas. We need sklearn to run the example. So these are 2 options. First one is to skip the example somehow. Second one is to install sklearn to CI environment. @Vyacheslav-Smirnov what option is better to select and how to reach selected option?

Exclude the example from common pipeline by skipping it.

@densmirn ,
I would prefer not to skip any example - they all should be executed and all should be passed.
To add sklearn (is it scikit-learn??) to CI for example build just add required package to https://github.com/IntelPython/sdc/pull/761/files#diff-12db1f3244c35f97542b6b38613320cfL82
sdc_utils.create_environment(['scipy'])

Also if this example requires additional package this package should be mentioned in the README.rst in sections related to examples.


Centralize the configuration of the OSDF client.

As we want to have the ability to stand up additional data federation instances (think: test directors), we should split out and centralize the defaults.
This introduces the use of viper for the process-wide configuration management.  This will allow the use of configuration files in the near future.

@djw8605 - ping on this PR review.

I think I'm fine with saving the overhaul of the README for later... probably a few more things to land first.


How to migrate PV，PVC created by different storageclasses

@Madhu-1 thank you very much for this issue. and i also have a problem,How to migrate PV，PVC created by different storageclasses，Details are as follows：
source storageclass
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
slow ceph.com/rbd Retain Immediate true 27d
destination storageclass
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
csi-rbd-sc rbd.csi.ceph.com Delete Immediate true 3d17h

@luhailiang0527 I don't think it's possible as the PV object is immutable you cannot edit the driver name and other details in PV object.

@Madhu-1  Is there a solution to such a problem，Is there any other way based on what you know

nothing am aware of, one thing I can thinkis using static PVC to mount older rbd images.

@Madhu-1  thank you  you can help me analysis this，Is it a solution to the problem https://github.com/redhat-cop/openshift-toolkit/tree/108586d05bf9e85854801509359e7b09dd05f08f/storage/pv-migrator

closing this one as this is outside of cephcsi.


fix: Add support for out-of-band Performance Insight's being added

If a customer enabled Performance Insights on the DB out of band, our module won't support enabling performance insights and reconciling tf state.
AWS recommends this: https://repost.aws/knowledge-center/update-encryption-key-rds
If we just allow user's to pass this out of band KMS key, we don't need to risk DB deletion or user error and can rectify the state.

This PR is included in version 1.16.9 :tada:


Please add a license file and a screen shot

I'd like to add this to awesome-zsh-plugins, but I prefer to add themes with screen shots in the readme so that users can see what they look like without having to install them.
Also, please add a license file, some people won't use any code that doesn't have an open source license. If you don't have one in mind, https://choosealicense.com is a good resource to help you select an appropriate one.
Thanks!

Hey @unixorn, I just did.
Thank you!


Bug: accountv2Client.List() always throws Error: Request failed with status code: 500, internal_error

Hello Team,
I'm attempting to retrieve a list of all accounts on my IBM Cloud using the List() API call from the accountv2 package. Unfortunately, I keep encountering the following error: Error: Request failed with status code: 500, internal_error.
Below is the source code I've been working with:
package main

import (
	"fmt"

	"github.com/IBM-Cloud/bluemix-go"
	"github.com/IBM-Cloud/bluemix-go/api/account/accountv2"
	"github.com/IBM-Cloud/bluemix-go/session"
)

func main() {
	conf := &bluemix.Config{
		BluemixAPIKey: "YOUR_IBMCLOUD_API_KEY",
	}

	s, err := session.New(conf)
	if err != nil {
		panic("Error in session creation: " + err.Error())
	}

	svc, err := accountv2.New(s)
	if err != nil {
		panic("Error in Account client: " + err.Error())
	}
	client := svc.Accounts()
	res, err := client.List()

	if err != nil {
		panic("Error in Account List API call: " + err.Error())
	}

	for _, acc := range res {
		fmt.Printf("Account Name: %s", acc.Name)
	}

}

If there are any corrections needed or best practices I might have overlooked, I'd greatly appreciate your guidance. This issue is currently a significant obstacle in our project's progress, so any expedited advice or solutions would be immensely valuable.
Thank you for your support!

The above is based on CF (MCCP) endpoint which is deprecated and stopped the service.
Added support to retrive accoutns without CF
https://github.com/IBM-Cloud/bluemix-go/pull/433


Output file name extension not replaced.

The script works fine.
Output file name now look like filename.heic.jpg.
On changing line 91-92 to the followings will solve the issue.
            $extension = $inputFile.FileType
            $outputFileName = $inputFile.Name -replace ($extension + "$"), `".jpg"`

The current naming of the output file is deliberate because it shows the file has been converted.


After reloading the home page options "Holiday allowance included", "66 years & older", "30% ruling" always change to Checked status

Possible solution:
In home.component.ts you can change
params['allowance'] && this.allowance.setValue(params['allowance']);
to
if (params['allowance']) {   this.allowance.setValue(params['allowance'] === 'true'); }
and also change other same code which gets boolean value from url parameters.

@artur-godunov good catch! thank you for reporting and suggesting the solution.
Maybe you can make a PR for it?

@artur-godunov should be fixed now.
one more time thank you for the finding!


Translate concepts/storage/persistent-volumes into Japanese

This is a Feature Request

What would you like to be added
Translate concepts/storage/persistent-volumes into Japanese
Why is this needed
This document is not translated in Japanese.
Comments

/language ja

/priority backlog

/milestone  1.17-ja.1

ありがとうございました！！
/close


Added Realtime Voice Call App

Closes: #925

Title: P2P Voice Call Application
Name: Sezal Lagwal
Idenitfy yourself:  Gssoc-ext, Hacktoberfest Contributer

Describe the add-ons or changes you've made 📃
Screenshots 📷

Type of change ☑

What sort of change have you made:

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

Checklist: ☑

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

Note to reviewers 📄

@Avdhesh-Varshney please review this pr thanks!

Looks good. But enlist your project in Nextjs readme file

okay

@Avdhesh-Varshney done :)


Convert some tests into subtests

Some tests were created before Go introduced support for subtests. It would be nice to convert some groups of small tests into a single test with subtests:

[x] TestRequest_BodyChunkedXxx => TestRequest_BodyChunked
[x] TestRequest_BodyBytesXxx => TestRequest_BodyBytes
[x] TestRequest_BodyFormXxx => TestRequest_BodyForm
[x] TestRequest_BodyMultipartXxx => TestRequest_BodyMultipart
[x] TestRequest_ErrorConflictXxx => TestRequest_Conflicts
[x] TestRequest_ErrorXxx => TestRequest_Errors
[x] TestResponse_Cookies, TestResponse_NoCookies => TestResponse_Cookies
[x] TestValue_CastXxx => TestValue_Casts
[x] TestValue_PathString, TestValue_PathNumber, TestValue_PathBoolean, TestValue_PathNull, TestValue_PathIntFloat => TestValue_PathTypes

Pull requests that address only part of this issue are welcome too!
Related: #283, #284.

Sure, thanks!

Landed!


PDF builds do not do enough pdflatex runs

Details

Project URL: http://readthedocs.org/projects/sphinx/
Build URL (if applicable): e.g. http://readthedocs.org/projects/sphinx/builds/5413951/

The issue shows for 1.6.1. The PDF is missing "Index" both in the PDF bookmarks and table of contents.  As explained below I will push (after posting this to get the reference of this issue) a workaround for 1.6.2.
Expected Result
PDF contains in its bookmarks an "index" entry and also in the Table of contents.
Actual Result
No  "index" entry in PDF bookmarks nor in PDF table of contents.
Analysis
RTD does only one pdflatex run after makeindex. This is not enough.
For Sphinx own docs I will push a commit with this in conf.py:
latex_elements = {
    'printindex': r'''
\IfFileExists{\jobname.ind}
             {\footnotesize\raggedright\printindex}
             {\begin{sphinxtheindex}\end{sphinxtheindex}}
''',
}

This malaxes LaTeX into inserting an "index" entry in the auxiliary .toc file on first run.
However, better solution would be for RTD builds to do pdflatex twice after makeindex. The more general  approach could be to use Latexmk.
Relates: #1583, https://github.com/sphinx-doc/sphinx/issues/3742

Why do you want me  to think by my self if I can work with you

Duplicate of #4454


SILGen: Fix crash when a closure captures two values with dynamic 'Self' type

We give special treatment to a capture of a value with dynamic 'Self'
type, by adding it at the end of the capture list. This ensures that
IRGen can recover the 'Self' metadata from this parameter if needed.
However, the code would crash with an assertion if there were multiple
captured values having the dynamic 'Self' type. This was slightly more
difficult to spell before SE-0068, but it was still possible if you
tried; now its completely trivial.
Fixes https://bugs.swift.org/browse/SR-11928, rdar://problem/57823886.

@swift-ci Please smoke test

@swift-ci Please smoke test Linux

@swift-ci Please smoke test


Change return type based on query

Hey, this LSP looks promising, thanks for creating it!
I was playing around with this:

And noticed there is no inference. Since this is an LSP I believe it should be possible to dynamically augment the return type based on the argument (query) given?
Right now, what would have to happen is, an import of the typed document generated, which is:
import * as Types from "../../__generated__/baseGraphQLSP"
import { TypedDocumentNode as DocumentNode } from '@graphql-typed-document-node/core';
export type FooQueryVariables = Types.Exact<{ [key: string]: never; }>;

export type FooQuery = { __typename: 'Query', workspace: { __typename: 'Workspace', id: string } };

export const FooDocument = {"kind":"Document","definitions":[{"kind":"OperationDefinition","operation":"query","name":{"kind":"Name","value":"foo"},"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"workspace"},"arguments":[{"kind":"Argument","name":{"kind":"Name","value":"id"},"value":{"kind":"StringValue","value":"abc","block":false}}],"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"id"}}]}}]}}]} as unknown as DocumentNode<FooQuery, FooQueryVariables>;

The FoodDocument is, IIUC, a duplication of what the gql template literal will produce.
There may be times when the current approach fits with established systems but it should not be the only way I think. Using this tool should make the DX on par with genql.
By having inference, it would also remove the need to name the queries, further simplifying things. Code would become simple like:

And noticed there is no inference. Since this is an LSP I believe it should be possible to dynamically augment the return type based on the argument (query) given?

This isn't possible in TypeScript. The type checking system is isolated and opaque to LSP plugins, even if the plugin system was interlinked with the compiler more closely, that'd still at most allow for build output transformations. And even still, if it was interlinked with the type checker, there isn't a prepared entry point to alter types and step into type checking phases.
I also don't think that this will change any time soon, or that it's reasonable for TS to change this necessarily

There may be times when the current approach fits with established systems but it should not be the only way I think. Using this tool should make the DX on par with genql.

Personally, and this may differ from other people's views, I find modelling DSLs into JS methods/objects/classes/etc horrendous.
It works out for CSS, and even then only to an extent, since it's dealing with declarations, i.e. properties and values. Even then there's conflicting views around how to deal with comma separated values vs repeated declarations.
Similar to this, GraphQL has a distinct query language that's purpose-built for its specific properties and that cannot reasonably be mapped to a JS/TS equivalent without making concessions and worsening the developer experience bit by bit with every language feature that's supported and mapped over
(directives in general, optionals like defer vs include/skip directives, arguments, aliases, etc all contribute to more obscure inputs having to be written)
There is a solution to this, and it's not exactly novel, but putting in the research into making it work reliably, performant, and comprehensively is taking some time.
But personally, imho, the answer will be this once it's done: https://github.com/0no-co/gql.tada
This is a project to infer GraphQL string literals directly to output types via parsing the queries in the type system from an input introspection type.
But it'll ultimately take a while to finish and stabilise due to performance considerations ✌

Exactly as Phil said, we aren't able to intercept the internal type nor can we alter it hence settling on the codegen + file transformation, which is actually also quite discouraged/unsupported 😅
I share the sentiment that the object-based syntax is limiting, you either complicate argument-variables, directives or fragments in some shape or form.
I would argue that the typed-document-node is quite settled on in terms of a GraphQL standard way to type document-nodes in TypeScript. If you don't want that, the GraphQL-code-generator client-preset is also well supported at the moment!
In the future we can indeed improve this with gql.tada where we would output an Introspection from the LSP so you can enjoy automatic typing everywhere 😅

Thanks for the sharing the thoughts. I understand better now the limitations of the LSP. The next idea that comes to mind is generated global types that can be matched to a callsite via a globally unique query name.
const { foo } = await query('abc', `
  query {
    foo {
      bar
    }
  }
`)

This would require coordination between a few bits, but generally should be straight forward. The hard work is already achieved by this tool.
Said coordination would be:

A global TS type
User needing to make sure said global TS type is included by their tsconfig
A function designed to work with said global type
User needing to import said function from somewhere

While simple, It would bring this tool toward aspects it does not currently cover. While it does generate runtime code, it is following an established idiom in the JS community. My proposal is not an established approach.

Regarding https://github.com/0no-co/gql.tada I'm not sure I follow. A usage example would help me.

Regarding merits of JS vs GraphQL syntax, there is a lot to discuss there. I think you're too dismissive and dogmatic, personally. How much do people give up when using Prisma instead of SQL? A lot. When they need SQL can they drop to it? Yes. There are tradeoffs, using GraphQL query syntax, instead of JS. Genql is missing features that are about its limitations, not JS. It could support streaming, defer, aliases, etc. but the author of that tool hasn't done so yet. Despite that, the straight forward toolchain, type checking of inputs and inference of outputs, is a productivity boost that outweighs the benefits of GraphQL syntax, due to the tooling issues. I did not come and make this issue because I wasn't interested in trying GraphQL syntax, after all. But without inference, it does not make sense to use in my current project, and I suspect other ones out there too.

What you mention about the coordination comes very close to what graphql-code-generator already does in their client-preset apart from the being indexed by name and being a global it already comes very close.
In your vision this would be generated by the LSP? Personally in my first line of thinking I didn't want to break the whole code-generation idiom as a lot of GraphQL users are subscribed to that so hence we support both tagged-template literals (we generate code and alias the type) like this or the client-preset approach where the generator is external and we facilitate the diagnostics/... like here.
Am I right in understanding that given your proposal these two approaches would get combined and we would generate the graphql() helper as part of the LSP process?

Regarding https://github.com/0no-co/gql.tada I'm not sure I follow. A usage example would help me.

This would be very similar to your approach where the requirements would be an introspection and a document, when combined with TypedDocument it would infer the types based on traversing the introspection with the document at hand.
Example can be found in the linked test-suite, ofcourse this is missing a public API like graphql().

I think you're too dismissive and dogmatic, personally.

You are very much free to think this, I have personally tried a lot of these tools like GraphQL Zeus and others, which may have been too early in their journey but I in fact did run into the limitations I mentioned quite often 😅 not saying that folks can't create a paradigm that fixes all of them but the GraphQL execution language is quite large. I don't want to open this discussion, I did want to "defend" myself from this accusation.

Hey @JoviDeCroock I think I have homework to do at this point in regards to the things you mentioned. Thanks for the response! What I am mostly trying to figure out next is what do the existing primitives/building blocks permit, and what is the necessary application level glue code. I'm still a bit hazy on that.
The ideal is to be able to write a GraphQL query and have inference without needing to think about anything else, such as deps or configuration. Editor integration, like an LSP, is uniquely positioned to deliver on this ideal since it can generate any necessary code for the user. From a developer point of view, writing a GraphQL query becomes as native as writing JSX feels nowadays (e.g. when using .tsx).
This degree of seamlessness and no-learning-curve is where GraphQL codegenerator and other tools in the ecosystem currently seem to fail.
Given that GenQL is, for almost no effort, solving 99% of my current use-case(s), I can't prioritize looking more into this proposal at present, but it would be generally great to return to, learn more, and share more thoughts at some point. Feel free to close though if this issue is creating noise, of course.

The ideal is to be able to write a GraphQL query and have inference without needing to think about anything else,

This is basically a goal we're very aligned on. I wrote some extensive notes to answer your questions, but, to be honest, I'll stash and discard them for now, for the sake of being clear and concise ✌
Basically, there's more to GraphQLSP than it seems, and it's neither finished or arrived at a major milestone past being usable today, nor is it the only part of the solution.
Today, GraphQLSP targets two use-cases:

Tagged template literals (it'll automatically use GCG to annotate them with as import(...).DocumentTypeExample and that'll add types
GraphQL Code Generator's client-preset, which basically opts out of the above in favour of manually running codegen via GCG

Apart from these, it obviously looks at the schema and provides auto-suggestions, diagnostics, and hints.
The missing piece here, as you said, are queries.
And that's bounded, in our view by the main problem: the GraphQL ecosystem’s tools are increasingly fragmented and their sheer amount if confusing to people.
In a typical GraphQL project, people already have to choose up to 5–8 tools, including things like GraphQL Code Generator (amongst clients, query builders/authoring tool, linting, codegen, schema builder, API gateway/server)
And basically; the query authoring experience should, in most cases be, basically zero-config.
The goal here is to combine GraphQLSP with gql.tada. The latter is an inference-based GraphQL builder, similar to GraphQL Code Generator but running mostly in the TypeScript type system.
It'll basically take this:
(The /* GraphQL */ comment is only needed for editors to add syntax highlighting)
gql(/* GraphQL */`
  { test }
`)

And type the return type automatically via TypeScript inference. GraphQLSP at that point will only provide:

writing schema introspection to a file as the schema changes
provide suggestions/diagnostics/etc as it does for GCG's client-preset

i.e. the goal here is to eliminate tools and processes for users to learn entirely.
That's also where our apprehension to non-DSL query authoring comes from. Tools like GraphQL Zeus or genql as posted are great initial experiences, but supporting all of these tools (there are tens of alternatives; as there usually are for many ideas in the GraphQL ecosystem) and we can't support them all for their fractional adoption (not throwing shade, I literally mean GCG or tagged template strings without types are vastly more popular, and these tools are further splitting adoption up into smaller segments)
So, i.e. we want a “native” GraphQL query language experience with minimal to no mental overhead and no tool should need configuring.
(For context, even if GCG is used independently with the client-preset — or other plugins — it still needs configuring for the query output types to be as one would expect)
So, that's basically where we're at; GraphQLSP is a stepping stone and supports the (de-facto) biggest tool that adds typegen to GraphQL query documents, and from there we can hopefully streamline this into one recommended setup.
Hope that makes sense ✌

@jasonkuhrt just echoing what the maintainers mentioned – client-preset from GraphQL Codegen is great and does exactly what you want. You can enable the codegen with a watchscript and get instant types as you save.
client-preset has a really nice type system for fragment masking. It's very powerful once you get used to it. I recommend this article.
And it'll work great with GraphQLSP (be sure to check the client-preset setup in its docs).

It'll basically take this:
(The /* GraphQL */ comment is only needed for editors to add syntax highlighting)

I actually have syntax highlighting working without even needing that comment when I use the graphql() function from client-preset.

Closing since this isn't relevant with gql.tada being a thing.


Singleton settings and fix UDEV setup

Summary by Sourcery
Implement a thread-safe singleton pattern for the ConfigurationManager to ensure consistent access across threads and refactor the code to utilize this singleton instance. Fix the UDEV setup script to correctly execute with the current user's privileges.
New Features:

Introduce a thread-safe singleton pattern for the ConfigurationManager class to ensure only one instance is created and accessed across threads.

Bug Fixes:

Fix the UDEV setup script to run with the current user's privileges by adding the '--user' flag to the pkexec command.

Enhancements:

Refactor the codebase to remove the need for passing ConfigurationManager instances to various components, instead using the singleton instance directly.

@sourcery-ai review


add dataSourcesList next to dataSourcesNum

With new API changes, if we don't provide no list of preferred datasources, we get only a bestResult.
There is no way to get ALL matches unless you explicit ALL datasources in a preferred list.
//<PHONE_NUMBER>3348
// https://verifier.globalnames.org/api/v0/verifications/Narcissus%20minor

{
  "metadata": {
    "namesNumber": 1
  },
  "names": [
    {
      "id": "e0942f50-d1d9-5f5d-b892-38972dff3e2e",
      "name": "Narcissus minor",
      "cardinality": 2,
      "matchType": "Exact",
      "bestResult": {
        "dataSourceId": 1,
        "dataSourceTitleShort": "Catalogue of Life",
        "curation": "Curated",
        "recordId": "45PDW",
        "outlink": "https://www.catalogueoflife.org/data/taxon/45PDW",
        "entryDate": "2021-11-20",
        "sortScore": 9.013153431111759,
        "matchedName": "Narcissus minor L.",
        "matchedCardinality": 2,
        "matchedCanonicalSimple": "Narcissus minor",
        "matchedCanonicalFull": "Narcissus minor",
        "currentRecordId": "45PDW",
        "currentName": "Narcissus minor L.",
        "currentCardinality": 2,
        "currentCanonicalSimple": "Narcissus minor",
        "currentCanonicalFull": "Narcissus minor",
        "isSynonym": false,
        "classificationPath": "Biota|Plantae|Tracheophyta|Liliopsida|Asparagales|Amaryllidaceae|Narcissus|Narcissus minor",
        "classificationRanks": "unranked|kingdom|phylum|class|order|family|genus|species",
        "classificationIds": "5T6MX|P|TP|L2L|SP|694|5XM5|45PDW",
        "editDistance": 0,
        "stemEditDistance": 0,
        "matchType": "Exact",
        "scoreDetails": {
          "infraSpecificRankScore": 0,
          "fuzzyLessScore": 1,
          "curatedDataScore": 1,
          "authorMatchScore": 0.2857143,
          "acceptedNameScore": 1,
          "parsingQualityScore": 1
        }
      },
      "dataSourcesNum": 15,
      "curation": "Curated"
    }
  ]
}

So for each requested name we get a "dataSourcesNum":15, but just one bestResult.
That's fine because it saves a lot of bandwith, but I would add just a bit more information here.
¿Could you include here also a dataSourceList of those 15 datasources? (just their ids)
Use case:
When I have only a small list of preferred datasources (i.e. less than 5) and no one of them matches a name, then I would be interested in using API to find out which other datasources include them. But as gnames has 200 datasources, it is much better that I have an ordered list of my secondary preferred lists and match them against the ids returned in dataSourcesList. Like this:

I have an ordered list of 3 preferred datasources, and a also ordered list of many other secondary datasources
None of my 3 preferred datasources matched, so ...
I ask gnames again to know bestResult and dataSourcesList
I check which of my secondary datasources is first in dataSourceList. If it is current bestResult, I just take it.
If not, I explicitly request gnames info from my preferred secondary datasource

Oups, sorry @abubelinha , somehow did not notice this issue until now
How about using all_matches=true?
https://verifier.globalnames.org/api/v0/verifications/Isoetes%20longissimum?&all_matches=true

I was thinking about adding data-source ids as well, but was waiting for someone to request it, so I do not create a feature just to create it.

Thanks for the solution, that works perfect !!


Add legacy option.

ping @kizu
Ref: https://github.com/ben-eb/cssnano/issues/41

@ben-eb Global instance do not seems good. Maybe somebody want in one file legacy, in the other modern.

@ben-eb Move conditions to selectorMerger scope


Add PaperColor theme

based on https://github.com/NLKNguyen/papercolor-theme
light:

dark:

Thank you


Changing shell to anything but /bin/sh and /bin/bash breaks SSH

The fish package doesn't add fish to /etc/shells which causes dropbear to reject new SSH sessions with "permission denied" because User 'root' has invalid shell, rejected. The package should add fish to /etc/shells.

We'll have to sort out how to add values to /etc/shells automatically for all the different shells in entware. That, or have something on startup that forces the shell for root to be /bin/sh and then makes sure to add code to launch the other shell to the user profile.


Draft specification

Write specifications based on what is on my mind

closing this issue, as it is already nicely broken up to sub-issues.


[Bug]-[19]:Intermittent

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When the user tries to fetch the response it is observed that the there is slow
Only after increasing the timer we could fetch response
Steps To Reproduce

Add Hubspot creds
Create a simple query of publish table
Click on RUN
and observe the response
Change timer
and re run the response appears

Public Sample App
No response
Issue video log
No response
Version
Release

6m usage of Hubspot: 19
Assuming 100% of users face this: 19
Stats

Stat
Values

Reach
19

Effort (months)
0.50

@prapullac can you please fix the title and description of this issue. Thanks


AES only supported by Android API 23+

AES only supported by Android API 23+
https://developer.android.com/training/articles/keystore.html

Hi @erlangp, thanks for the link. Sorry I don't quite understand, did you find a bug in my app?


[thread-cert] LowPower_5_3_01 failed when VIRTUAL_TIME=0

Describe the bug
When running the case v1_2_LowPower_5_3_01_SSEDAttachment.py with VIRTUAL_TIME=0 it fails. Currently the cases are all run with VIRTUAL_TIME=0. Currently our tests are all run with VIRTUAL_TIME=1.
To Reproduce Information to reproduce the behavior, including:
THREAD_VERSION=1.2 VIRTUAL_TIME=0 CSL_RECEIVER=1 ./script/test build cert tests/scripts/thread-cert/v1_2_LowPower_5_3_01_SSEDAttachment.py

Git commit id: f886f34d0
IEEE 802.15.4 hardware platform: simulation
Build steps: THREAD_VERSION=1.2 VIRTUAL_TIME=0 CSL_RECEIVER=1 ./script/test build

Is it a 100% chance fail?

Is it a 100% chance fail?

As I tried, yes.


add template printer flags

Release note:
NONE

WIP - starting point to get an overall gist of where it's going.
Next steps will update every file that relies on calling cmdutil.AddPrintFlags() and cmdutil.AddOutputFlags() to also instantiate template flags via NewTemplatePrintFlags().
For every affected command, it looks like we'll have to try calling the ToPrint() method on the
template print flags first, before attempting to default to PrinterForOptions to resume with old behavior when not attempting to print using a template.
This does not compile yet.
cc @deads2k @soltysh

Closing in favor of https://github.com/juanvallejo/kubernetes/pull/2


Implement Apogee Prediction

Major changes:

Implementation of vertical velocity using rotated acceleration in the earth's frame of reference. This is more accurate than our current magnitude approach. However it is still slightly inaccurate during free fall by about 2-5m/s (just eyeballing it v/s altitude).

Apogee Prediction using curve fitting. This runs only for the duration of CoastPhase. We converge to true apogee with an accuracy of +/- 10m within 5 seconds of coasting.

The apogee prediction process runs only every 10 packets.

WIP:

[x] Tests (verify that everything works as expected)
[x] multiprocessing
[ ] Review comments
~plot velocity calculated from rotated frame vs speed from accel~

last working commit before multiprocessing - https://github.com/NCSU-High-Powered-Rocketry-Club/AirbrakesV2/commit/0ac977ce9afd6469e94fc4832ad11a6759899414 (I think).

With the new and accurate CPU usage in the Flight Display, we can actually see how much CPU usage Apogee Prediction takes. And it's surprisingly the least amount of compute out of all the processes, averaging about 0.3% on PC during CoastState.

Velocity for purple nurple is very wrong during Free fall because we don't have accurate 3D data for the launch. That launch was missing Angular rate and quaternions, and scaledGyro isn't accurate enough for a 3D representation.
So once we are in free fall, the rocket is rotating a lot, and we can't accurately quantify it, because our rotation data is only accurate for 2D.

we so close

I know we purposely took out the airbrakes extension from the update() in coast phase, but I just added it back just so the test passes lol. We will obviously go back and change things once we do the control logic

I do
u gotta approve it


Image style for Infowindows show the url

STR

Create a new map with a dataset that contains a field with an image url
Apply the popup style with an image on the header
Put the image field as the first one to be used on the header

Expected result
The image is used on the header and the next field on the list is used as a title
Current result
The image url is used as a title

if I'm not wrong this belongs to carto.js

OK, sorry! :innocent:

noo prob, I'll discuss with @xavijam how to proceed with this, thanks for reporting!


Format

Where does this comes from?
I agree with needing a readOrder type of element, but I noticed that there's a Format element adjacent to the badly thought out Manga element, at least in the v2.1 schema - but it's undocumented as far as I can see.  Hoping this was meant as a Manga replacement which would cover the cases (at least):

left to right reading order
Right to left reading order
Vertical reading order (manwha/webtoons)
Horizontal reading order (uncommon, but I know I've read a few)
Free-form (some of the web-enhanced comic formats)

What is the rationale for adding support for this element?
These (especially the first 4) would allow a reader to automatically display the pages properly.  Currently, we have no way to know how to render the pages, and how page turns should work.  For example, Komga requires setting a flag to determine if it's a webtoon - otherwise it will try to display the images as ltr oriented pages.
Is the element already handled by any application or tool?
Not that I know of, but it certainly will be if this is formalized, as bigger companies start publishing multiple nationalities of comics.

We are covering that in #40 which I think would handle all of that

What I usually see in the freeform "format" field is close to "original binding information" or "original publication format" like "TBP, digital, HC"

What I usually see in the freeform "format" field is close to "original binding information" or "original publication format" like "TBP, digital, HC"

Maybe that's something we can add in the documentation in that case, if you're willing to open x PR for that?


feat: use iconify universal icon loader

This PR also includes:

updates all dependencies (taze -r -w)
updates some fixtures to fix some fw changes
these modules have been removed src/core/custom.ts, src/core/modern.ts and src/core/utils.ts, all stuff included on @iconify/utils, you can check it here: the universal icon loader https://github.com/iconify/iconify/tree/next/packages/utils/src/loader and here string variants (camelize, pascalize...) https://github.com/iconify/iconify/blob/next/packages/utils/src/misc/strings.ts

Tested all examples except nuxt, vue-cli and webpack.

Awesome! Thanks!


Understanding Multiclass classification problem

Here is the thing.
I have 3 class labels in my data. The predict function returns an array of shape (N, 3) where N is the size of the train set. Here is an example,
>>> prediction = model.predict(tokenizer.transform(test_text))
>>> prediction
    array([[ 0.99999995,  0.99998585,  0.99999268],
       [ 0.99999993,  0.99998351,  0.99999069],
       [ 0.9999999 ,  0.99997884,  0.99998756],
       [ 0.99999992,  0.99998125,  0.99998932],
       [ 0.99999988,  0.99997679,  0.99998638],
       [ 0.99999996,  0.99998655,  0.99999323],
       [ 0.99999942,  0.99992762,  0.99995597],
       [ 0.99999987,  0.99997481,  0.99998479],
       [ 0.99999995,  0.99998605,  0.99999269],
       [ 0.99999996,  0.99998733,  0.99999372]])

How to interpret the prediction. I have 3 class labels but the array is giving close to 1 in all the classes. The value don't even sum up to 1. I must be doing something wrong. Any suggestion is highly appreciated.
Thanks!

@naeemulhassan Mind posting your code so I can try to reproduce this error?
I turned the gender two class problem into a multiclass problem, by using replacing sigmoid with softmax and bce with cce.
Check out the gender_multiclass.py file in my PR: https://github.com/IndicoDataSolutions/Passage/pull/39


Garbage collect old comments

Comments that have not been accepted for a while should not be kept in the database. I would suggest not more than two weeks until old comments are removed.
I can see two ways to do this:

a regular cron job
something like hapi-cron

Absolutely. I have wanted to implement that for quite a while but never got around to that considering how annoying developing the lambdas was. This should not be an issue anymore.
Without putting too much thought into it, I would vote for hapi-cron. I would like to avoid external dependencies where possible, especially since we are running on an Uberspace.

Why aren't we introducing a "reject"-Button instead of not-accepting?

What happens if you two are too busy/unavailable for two weeks or simply forget too accept a comment? Then this would delete comments blindly, right?

* Why aren't we introducing a "reject"-Button instead of not-accepting?

We can do that as well.

* What happens if you two are too busy/unavailable for two weeks or simply forget too accept a comment? Then this would delete comments blindly, right?

I feel like that is pretty unlikely. :D But if push comes to shove, we will most likely not have deleted the confirmation email either. And that mail contains all the details, so we would be able to recreate the comment from that.
On the other hand, it is much more important to delete comments that we don't accept because some of them contain a worrying amount of personal data that we definitely don't want to keep around. Just relying on a 'reject' button isn't enough imho as that can be easily forgotten.

Right. The private data. I agree with auto-removing.

I'll also need garbage collection for old mollie_ids. I think in AWS we keep them 30 days.


Adding Some Unit Tests

Coverage increased (+5.5%) to 73.18% when pulling 4679e16bfd1c4d3cd24eb88fe1994425a02f3ce8 on npardington:master into 9a67a8984f6e192a2813f4527a53ff10c4d6c20e on worthwhile:master.

Coverage increased (+5.39%) to 73.07% when pulling 2112796c0dae4b5fbd2a5cd5e54e6cff1051f831 on npardington:master into 9a67a8984f6e192a2813f4527a53ff10c4d6c20e on worthwhile:master.

Coverage increased (+5.54%) to 73.22% when pulling c57dc5d7daabc0fd899191a1127f8d271fb89807 on npardington:master into 9a67a8984f6e192a2813f4527a53ff10c4d6c20e on worthwhile:master.

Coverage increased (+5.54%) to 73.22% when pulling c57dc5d7daabc0fd899191a1127f8d271fb89807 on npardington:master into 9a67a8984f6e192a2813f4527a53ff10c4d6c20e on worthwhile:master.


Anomaly Plot

Make a plot that is made to show anomalous sections on a TimeSeries

This issue is strongly linked to the functionality of the "anomaly detection"-models. To make this plot useful we first have to create them and they are projected in later releases.


Add package to maven central

I should really get this on maven central. I can use https://github.com/tlf30/jme-jfx as a reference.

This is a great idea: At the moment, I am struggling with a gradle error message JMonkey:main: Could not resolve io.tlf.monkeynetty:monkey-netty:0.1.0.

Hello @RaiNova,
I will see about getting this done on Monday. GitHub packages are painful for everyone to use.

@RaiNova I have published a snapshot for v0.1.2 on maven central with the new publishing config. Can you please test and let me know if it works for you?
No need for any of the github repo config.
implementation 'io.tlf.monkeynetty:monkey-netty:0.1.2-SNAPSHOT

Also, because this is a snapshot, you will need to add maven central snapshot repo to your gradle until I publish this version as an official release.
https://oss.sonatype.org/content/repositories/snapshots

Hello @tlf30,
thanks for your efforts. I am currently on a business trip, and will probably try it out on the weekend.
Cheers
Rai


Spright documentation and cleanup

🧹 Tech Debt

[ ] Ensure proper CODEOWNERS
[ ] Update repo-wide README and CONTRIBUTING (@rajsite addressing)
[ ] Update spec instructions and templates to consider Spright (e.g. annotate existing templates to say which sections are skippable for Spright contributions)
[x] Delete spright storybook
[x] Deprecate/delete spright repo and turn off Renovate
#1890 Tracked separately
Get Spright logo? No current or planned need

@rajsite

Update repo-wide README and CONTRIBUTING (@rajsite addressing)

The README has some Spright references, but CONTRIBUTING does not. Is there more to do for this?

Deprecate/delete spright repo

It has been deprecated, but shouldn't we just delete it? Can't think of any reason we'd want it anymore.

The README has some Spright references, but CONTRIBUTING does not. Is there more to do for this?

The top-level CONTRIBUTING doesn't discuss dev for the specific packages, it's Getting Started ends with "Now that you can build the monorepo see the CONTRIBUTING.md for the packages you would like to contribute to."
Nothing more to do for that.

It has been deprecated, but shouldn't we just delete it? Can't think of any reason we'd want it anymore.

Yep. Think @fredvisser was gonna reach out to RDSS to delete all of:
https://github.com/ni/nimble-angular/
https://github.com/ni/nimble-angular-schematics/
https://github.com/ni/nimble-blazor/
https://github.com/ni/nimble-tokens/
https://github.com/ni/spright

@m-akinc Taylor pointed out that it would be good to have some pointers about the purpose of Spright in Storybook now that its components are hosted there. Some ideas for this (just a brain dump, I don't feel strongly about doing all of them).

a brief blurb on Getting Started that links to a README / CONTRIBUTING / ADR describing Spright's purpose
a separate table in Component Status
A Docs page for the Spright section (and Nimble components section?) similar to what we have for the Incubating section

I'm going to add a new bullet to the checklist in this work item to cover this. I don't mind helping with it but probably won't have time today.


About pose：out_dim

i found the 'inference': 'oup_dim'  in config(pose.py) is 68,however the loss is put on the first 34-d of the output of the network? It would be appreciate that you could give me a reply about the use of the later 34d.

Sorry for the confusion about extra output dimensions, we only use 34. The additional output channels are leftover from an old idea but are not relevant to the current model.


Update ISA-Tab template dependency from cubi-tk to cubi-isa-templates

This will get us rid of dependency problems and enable updating to the latest and greatest templates

Done.


Version 1.4.4 crashing server

https://pastebin.com/XG0Fmfby
Strangely the server doesn't generate a crash report and just restarts.

I Got the same crash also with No crash Log, I had to remove the whole mod just to stop my server from crashing


Disable prover test which fails on smaller machines. (#114)_51

Motivation
Disable prover test which fails on smaller machines
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
CI/CD tests are covered.

:sunny: Canary successful

/land


Added ModelRetrainDays field to ServiceConfiguration get and update

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version: Note, PR for most of the new API content is here: https://github.com/Azure/azure-rest-api-specs/pull/19912. This is just a small addendum
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month. 9/01/2022
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month. 9/2022
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Please note that we have already been through breaking change approval for this unreleased API version, please refer to this pr: https://github.com/Azure/azure-rest-api-specs/pull/19912
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

@anuchandy
Did you link the wrong PR?
https://github.com/Azure/azure-rest-api-specs/pull/19912 is not private and it does not contain modelRetrainDays property?


PIN: Update nipype

Includes nipy/nipype#2198, nipy/nipype#2200, nipy/nipype#2205
Pending:

[x] FMRIPREP test
[ ] MRIQC test

Edit: Added a further pin. If that causes issues, I'll drop it.

@oesteban Does we need to include nipy/nipype#2209 to fix MRIQC?

No, I have to fix MRIQC first. Let me push some commits.

Okay. If it works for you, I'll push a commit here with the latest nipype PR and you can push your MRIQC fixes and pin in one shot.

It works :)

Sorry, I misread the thread. No, nipy/nipype#2209 is not necessary

Okay, I collapsed the pin to include all the updates. You can pin MRIQC to dafbfdaac1c4a4765f413812749a93992a1a37d5.

Sweet thanks

Updated the fmriprep test in the checklist. If you want to do the same when you push an mriqc branch, I'll merge when they both pass.

Done

Not causing a failure but it is a bit unsightly:
Error in atexit._run_exitfuncs:

Traceback (most recent call last):
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/utils/config.py", line 327, in free_display
    config.stop_display()
AttributeError: 'NipypeConfig' object has no attribute 'stop_display'

From: https://circleci.com/api/v1.1/project/github/effigies/fmriprep/861/output/31/0?file=true
I want to go ahead and merge to move forward, if MRIQC passes, but just so you're aware of the issue.

That is because of the absolute import of nipype in the atexit function. Not sure if that import could be relative, I guess so.

Yup. I'm submitting a patch. Also dropping the verbosity of multi-proc again...


Implement std::future::Future for the Server

It's more a discussion rather than an issue. What do you think about redesigning a library to be similar to the hyper::Server?
It will lead to the same experience with graceful_shutdown.
For example,
#[tokio::main]
async fn main() -> anyhow::Result<()> {

        ...

        let tls_config = ...;

        axum_server::bind_rustls(addr, tls_config)
            .handle(...)
            .serve(...)
            .await?;
       // vs
        axum::Server::bind(&addr)
            .serve(...)
            .with_graceful_shutdown(shutdown_signal())
            .await?;

    Ok(())
}

async fn shutdown_signal() {
    let ctrl_c = async {
        signal::ctrl_c()
            .await
            .expect("failed to install Ctrl+C handler");
    };

    #[cfg(unix)]
    let terminate = async {
        signal::unix::signal(signal::unix::SignalKind::terminate())
            .expect("failed to install signal handler")
            .recv()
            .await;
    };

    #[cfg(not(unix))]
    let terminate = std::future::pending::<()>();

    tokio::select! {
        _ = ctrl_c => {},
        _ = terminate => {},
    }
}

Now, I need to get an handle object and control it in a separate task. Is it worth changing it to the same behavior as in hyper::Server? What do you think?

I see no reason to implement Future for server type. There are at least two downsides which are rewriting async function manually(or boxing an async block) and possibly significantly changing codebase.
Handle is multipurpose so having graceful shutdown there isn't a problem in my opinion.
I'm closing this issue. I most likely won't make any significant changes in this library because with hyper 1.0 coming we will write a new server in hyper-util which will make this library obsolete.
This discussion should continue in hyper-util, thanks for bringing this up anyways.


Add Windows continuous integration through AppVeyor

Windows builds/tests activated on master branch only, badge added to README

+1

Travis tests are failing due to timeouts, is this a known issue?

This particular timeout isn't a regular issue and it happened only for one OTP release. I'd expect all tests to succeed if you force a retest.

Indeed they did


please bring back parse_reply_instantiate_data

hi.
somewhere along the way this function disappeared.
sadly the cw_nft's use this, and it makes it challenging to migrate to v2.0.0 there.
Thanks!

To parse the instantiate data, you should use https://docs.rs/cw-utils/latest/cw_utils/fn.parse_instantiate_response_data.html.

possibly.. but shouldn't you have waited a bit and marked it as deprecated first?
(and yes. I'm working with pre-2.0 chains)

Making the parse_reply_instantiate_data deprecated in cw-utils v2.0 instead of removing it would result in bugs. As @hashedone mentioned, since CosmWasm v2.0 there can be more than one response in the data field and parsing that with the removed method would occasionally return error.
The pub data: Option<Binary> field couldn't be marked as deprecated in CW v1.5.3 because there were no pub msg_responses: Vec<MsgResponse> back then. Therefore, the removed method couldn't be deprecated in the pre2.0 cw-utils version as well.


Diagnose CI build failures

🚀 Pull Request
Description

Testing the CI test failures against hypotheses of what might be wrong

I think that I've fixed the issue blocking #205 however I think it's important to be aware when reviewing that I don't fully understand the code I've changed. The tests pass now though?

I can't assign reviewers in this repo, so paging @bjlittle and @trexfeathers?


Error: AttributeError: 'NoneType' object has no attribute 'ndim'

I can open the Cellpose software window but couldn't drag-and-drop any image in it. Each time, I got the following error message in the anaconda terminal : "AttributeError: Nonetype object has no attribute ndim'.
The image type is jpg, coming from a export from Zeiss ZEN software.

I'm sorry I could not replicate this error with jpg or jpeg files, could you attach the file here?

Thank you Carsen, It seems that .tif files are doing all right instead of .jpg


Dodge the Creeps Example

New bevy_godot features:

fix(scene_tree): rework scene tree initialization to be correct for startup systems
feat: add Godot signals
feat(2d): add Transform2D and updating systems
fix: move post update godot transform systems to Last
feat(2d): removed additional check that prevented 2D collisions from working

TODO:

[ ] Add Game Over text like source
[ ] Add Get Ready text like source
[ ] Add Windows GDNativeLibrary path


Support formatting units, eg. secs, days

PR #254
Format units such as seconds, minutes, days, weeks, and everything else supported by CLDR.
Requires

#220 Plural

API
.formatUnit( value, unit [, options] );
Examples:
.formatUnit( 1, "month" ); // 1 month
.formatUnit( 5, "week" ); // 5 weeks
.formatUnit( 30, "day" ); // 30 days
.formatUnit( 30, "day", { form: "narrow" }); // 30d

Value: Number
Unit: String, eg. "month", "day", etc.
Options:

form ("long"|"short"|"narrow") used when tense = null to specify the unit form, eg. ("2 seconds", "2 secs", or "2s").

Specs

TR35 Unit Elements

CLDR
Units can be found on main//units.json.
--
Fore more background: see #391.

This is a must have as far as I'm concerned. Would be glad to help if needed.
What I tried to do a week ago before realizing I couldn't with the current version of globalize might help you get a clear use case:
Display week dates
function formatWeek(startDate, language) {
	var startDate = new Date(startDate);
	var i18nString = _('%s of %s to %s');
	var i18nWeek = Globalize.formatUnit( 1, "week" );
	var i18nFirstDay = Globalize.formatDate(startDate, {skeleton: 'yMd'});
	var i18nLastDay = Globalize.formatDate(startDate.setDate(startDate.getDate() + 6), language, {skeleton: 'yMd'});
	return util.format(i18nString, i18nWeek, i18nFirstDay, i18nLastDay);
}

It was not clear to me whether the API specified here (and partially implemented by #252) is sufficient for you? If it is, you can help me to finish #252, so we can land it. Right now, it misses functional tests and docs. It got stalled due to lack of time/resource to work on it.

#252 perfectly fits my needs. I'd be glad to help and will look into documenting it whenever I have free time.

Awesome, feel free to add comments needing help. As soon as we get those items tick, it should be good to land on master.

Ecma proposal

https://github.com/tc39/ecma402/issues/32


Feature/contributors add expand tree

Updating this PR https://github.com/CenterForOpenScience/osf.io/pull/5291
because of merge conflicts after 0.66
Tested on the project page treebeard that changes make public
Tested on the add contributor modal,
things seems to work fine but across these PR some context might be lost.

The two places that were not working are not @caner, Thanks!


Stdlib::IP::Address::V6::CIDR does not exist prior to stdlib 5.2.0

Describe the Bug
Module fails to compile with "parameter 'address' references an unresolved type 'Stdlib::IP::Address::V6::CIDR'" in installations were stdlib module < 5.2.0 is being used. Dependency in metadata.json still describes stdlib down to  4.13.1 to be acceptable
Expected Behavior
Catalog compilation with correct dependency parameters for other modules
Steps to Reproduce
Steps to reproduce the behavior:

Run module with stdlib module >=4.13.1 and < 5.2.0

Environment
Any
Additional Context

Hey @markasammut,
puppetlabs-postgresql v9.0.2 is now available on the forge with a fix in place for this.
Thanks for raising this.


Ground:db cause iron:router not working in Internet Explorer 10

When I added ground:db by "meteor add ground:db" and add a events collection into ground like this:
Ground.Collection(events);
It looks all right in localhost:3000, but when I deploy the codes into server by mup, my homepage turned into iron router error page and says I had not defined any route. And any of other routes broken.
Remove the package and ground collection line, deploy by same mup way will fix this.

I'm experiencing the same issue, as well. I get two errors in the console in IE10:

Unfortunately, it only throws this on production after it is mup deployed, so I don't get the "friendly" JavaScript line number it threw an error on. If there isn't already, an issue should probably be opened with @Raix (the error did say he would work his butt off to fix it. :smile: ). The second error is simply stating "Router" is undefined.
If it is helpful for anyone, I can provide the minified line that the error says it occurred on too. Just let me know.

bugger - what version of Meteor are you using?

I'm using<EMAIL_ADDRESS>currently.

I've released 2.0.0-alpha.1 Notes about the new version, migration and what it doesn't do - The issue might be resolved in that version, let me know what you think


Enhance unit-test: ensure that reconciling of a service-account won't create a new account instance

Description
The existing unit-tests for patching/replacing resources have to be enhanced to verify that a reconciliation of a service-account will not create another account instance in the ETCD.
AC:

Unit-test is reconciling a service-account multiple times but finally only 1 instance exists in ETCD

Reasons
Ensure reconciliation of service-account behaves idempotent and doesn't create new instances by automated testing.
Attachments

Part of #565


Multiple volumes

Is your feature request related to a problem? Please describe.
I am developing a pipeline which is similar to docker-swarm-php example. The difference is in volumes. In addition to docker socket I want to mount shared directory. With this I want to fix the next problem: I am unable to mount file/directory created inside of pipeline to docker container that I run inside of pipeline. For example a config file or .env file. I found this solution here. On my build server I have gitlab runner configured in similar way and I want to be able to duplicate this configuration in gitlab-ci-local:
...
volumes = ["/var/run/docker.sock:/var/run/docker.sock", "/shared:/shared"]
...

Describe the solution you'd like
It will be very cool to be able to mount multiple volumes to the gitlab-local-ci. For example to be able to specify them in .gitlab-ci-local-env as follows:
VOLUME="/var/run/docker.sock:/var/run/docker.sock, /shared:/shared"

or something like that.
Describe alternatives you've considered
I also think that my problem can be solved in different way. I am not good in making pipelines, so maybe I am missing something and I could solve this problem in different way.
Additional context
Add any other context or screenshots about the feature request here.

Try with spaces
VOLUME="/var/run/docker.sock:/var/run/docker.sock /something/:/app/"

@klimonoid Any luck?

I'll try this on monday. Thank you very much

I'm sure it will work. Just reopen if it doesn't.


Improve wemux support and clean up code

What is the state of our wemux support?
lib/templates/wemux_template.erb and lib/templates/template.erb have diverged quite a bit.  It would be nice to make the wemux template support the same features as tmux and then to pull everything that's common to a central place.
I've not used wemux much myself, I just don't like the duplication and divergence in the two templates.  If there are features wemux doesn't support this would be more difficult obviously.
Thoughts?

I absolutely agree. Since it's ERB, could we use partials for common features?

Exactly what I was thinking.  It almost feels like the example from chapter 1 of Fowlers Refactoring.  Form template method could work like Fowler used, but erb partials seems like a perfect solution.
Sent from my iPhone

On Jun 3, 2016, at 8:25 AM, Jonathan Arnett<EMAIL_ADDRESS>wrote:
I absolutely agree. Since it's ERB, could we use partials for common features?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


JavaScript Txn Processor Tutorial

Added code for JavaScript TP tutorial, added to JavaScript SDK
TOC, and removed old tutorial that is no longer needed.

@peterschwarz To answer your question on the versions of the languages supported: Yes, the "install guides" will have this. So far, this "install guide" exists only for Python:
app_developers_guide/python_sdk_install.html
This article explains the versions of Python supported.


Fix mysql connection string

This is a cherry-pick of https://github.com/Place1/wg-access-server/pull/135 fixing issue https://github.com/Place1/wg-access-server/issues/134
It has been slightly changed from @Nox-404's solution, using url.Host instead of url.Hostname() and url.Port() joined separately, as the second one would cause issues with raw IPv6 addresses (which url.Hostname() returns without enclosing brackets). url.Host returns host and port already combined, with brackets for IPv6 addresses.

LGTM!


Training with ResNet

Hi,
Can I please ask for the training details for training on the CUB dataset with ResNet?
I tried both the pytorch and tensorflow implementations. For pytorch, I got 51% accuracy for top-1 localisation. For tensorflow, the accuracy is even worse, even I have used the SE-ResNet50.
Can I please ask for the training details on how to get the localisation accuracy of 62.29% in your paper? For example, can you please provide the bash scripts that you have used?
Thanks!

Currently the PyTorch implementation is not stable, so I recommend you to use Tensorflow version for reproducing results.
You can use this script:
python CAM-resnet.py --gpu 0 --data $YOUR_DATASET_PATH --cub --base-lr 0.1 --logdir ResNet50SE_CUB --load ResNet --stepscale 5.0 --batch 128 --depth 50 --mode se --attdrop 31 41 5 --drop_rate 0.75 --threshold 0.90
If you have any further questions, please let me know.


Set deployment defaults to enable all components required to build the sample Media Insights web application

The deployment script for MIE is componentized so the stack can be deployed in layers.  This facilitates debugging and also allows you deploy only the parts of MIE that are needed for your application.
The current default settings for the deployment are set to build only the APIs.  The default should be changed to deploy everything needed for the demo application.

commit 3ce7c00da40aa5d58250cb0ebd50900b516bda37 (HEAD -> development, origin/development)
Author: Burkleaux<EMAIL_ADDRESS>Date:   Thu Oct 3 08:03:36 2019 -0700
Set deployment defaults to automatically build
MIE web application. #


[Feature request] Open current tab in external apps

When maintaining click on a link, there is an option to open it on an external app, I'd like that option to also be available for currently open tab.
It is especially necessary when a link isn't fired by href but JavaScript.

Hello, it's been some time. Any news on this ?

Hello, it's been some time. Any news on this ? An 'Open in App' option on the 3 Dot Menu like on Firefox would be awesome.

Hello, any news on this ? Thanks


fix: notifications

:tada: This PR is included in version 1.5.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Use correct libp2p library

Motivation
Only use the current libp2p core library and remove the archived version
Changes
Update import paths
Test Plan
Existing tests
TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[x] Update documentation as needed

DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

bors merge


LastFM Recommendations not working anymore

When running the recommendations script I now encounter the following error:
An error occurred: Message: element click intercepted: Element <button type="submit" name="submit" class="btn-primary">...</button> is not clickable at point (413, 446). Other element would receive the click:

   (Session info: chrome=114.0.5735.133)
I suppose last.fm changed their website...

I just ran it without any issue. Are you using the provided docker container? You can connect to the container at http://localhost:4444 and watch the session live.
What country are you in?

It didn't work multiple times, but when I tried it again now it worked. Maybe it was a short outtage on lastfms side.
Thanks for the tip to watch the session. If something like that happens again, I'll see if it'll help.
I'm from germany btw.


How to skip jobs based on a condition instead of failing?

Hi,
Is it possible to skip a job in a flow based on a condition? for ex: I have 2 jobs, JobA and JobB both of type command. In Job A , I check if certain data is present in our data store. This job always passes becauses it just checks if data is available or not and writes to JOB_PROP_FILE a boolean.
I want to run JobB only if the property written to JOB_PROP_FILE is true else skip running it. I don't want to fail the JobB if the boolean is false, just skip it coz job failures trigger a different workflow in our alerting system.
I could wrap the logic of the check job inside a shell script and have a if condition that will execute second statement if the check passes..but then the job will always pass. Which I dont want.
Is there a way to acheive this?

AFAIU, we have some of the infrastructure for conditionals such as these in place through the Trigger Manager but they are not fully exposed.

Hi,
is there a roadmap for that ?
Do you think it would be complex to do that ? (assuming it can be contributed)


“Unable to write program user data” when invoking VS Code as git editor

VSCode Version: 1.31.0
OS Version: Ubuntu 18.04.1 LTS

Steps to Reproduce:

Enter a git-tracked directory
Run GIT_EDITOR='code --wait' git commit --allow-empty
Observe an error dialog appears:

Unable to write program user data.

Please make sure the directory /home/mat/.config/Code is writeable

Just to make sure, I did recursively make that directory world-writable, but it didn’t help.
I tried it with today’s code-insiders build and the issue persists.

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

What happens when you run code?

@joaomoreno it opens VS Code as expected.

I use CentOS 7. get an error just by running code.
After a recent update VSCode have this issue.

@outoftime How about code --wait?

@joaomoreno invoking code --wait from the terminal opens VS Code as expected

Can you show me a screenshot of that error dialog?

I'm getting the same error:

I'm getting the same error:

Update: I no longer have this problem on VS Code 1.31.1:
$ code --version
1.31.1
1b8e8302e405050205e69b59abb3559592bb9e60
x64

I am encountering a different bug, which is that the commit editor always opens in a new window, even when the commit is initiated from the integrated terminal, and even when --reuse-window is supplied as an option. I will open a separate issue for that.

i got the same error as well.. on version 1.31.1.

if I run code it pops up the same message, but a manual open works. can confirm on the latest version

@bpasero Have you seen this?

This dialog is from us when we get an error of type EACCESS or EPERM on startup:
https://github.com/Microsoft/vscode/blob/ce073b0076ac2f69faf2c609af72f9b81506c791/src/vs/code/electron-main/main.ts#L215L222

@weichea @Technical27 Can you check permissions on that folder?

@joaomoreno I did note in the original bug report that I had tried recursively making the folder world-writable and it did not help.

Now code and code --wait works fine now after closing my terminal after using
chmod -R +rw ~/.config/Code
This will give everything in the folder write and read permissions

@bpasero That error message has a bug in it, the path its referring to is not the one that is generating the error.
This means people in this thread could be having a number of different issues.
My issue is potentially just a dupe of #3884 but I'm not sure.
I disable write access to my home dir specifically because of things like this so seeing this error and suspecting home dir access was probably the issue, I enabled writes and once again could start code without the error. Only now with a ~/.vscode-oss/extensions path being created.
Deleting the .vscode-oss directory and adding this env var lets me start code without the error and without the needless home dir pollution.
export VSCODE_EXTENSIONS="${XDG_DATA_HOME:-~/.local/share}/code-oss/extensions"

@lsl good catch. I pushed a change so that the error dialog talks about both the user data path as well as the extensions path. Both need to be writable for VSCode to startup properly.

@lsl unfortunatelly, I do not understand your solution. Could you please explain it to me?
where exatly did you add the env var? where is this document at all?
I have Ubuntu 18.04.
To be honest, I can't even find the files from vscode. Typing in the command "which code" returns "/usr/bin/code", but the directory usr/bin/ does not have the folder "code".
Could you please help me out?
Kind regards,
An Ubuntu noob.

Never mind. Solved the problem by deinstalling and manually deleting the directories home/.vscode and home/.config/Code. Then installing it again by downloading the .deb file from the official site and installing it using the command sudo install ./code_1.32.2-1552488294_amd64.deb

SOLVED by deleting the Code directory from /home/MyUserDirectory/.config and then re-starting VScode from the menu.
To be clear:
$ code
::Pop up with Unable to write program user data::
$ cd /home/YourUserDirectory/.config
$ sudo rm -rf Code
[enter your password as needed]
$
[no news is good news...so you should only get a prompt back - meaning, the directory and all its contents got deleted]
$ code
[or launch from the menu]
took an extra moment... and then VSCode came right up!
Before this I had tried installing with Anaconda-Navigator, which is where the 'cannot write' error started... uninstalled... re-installed Anaconda.. no improvement. Then manually uninstalled and re-installed. Still no help... Searched on the error message and found this article... scrolled all the way down... only to find @AHermann94 explaining that manually deleting the folders after uninstalling worked... so I thought I would see what would happen if I just deleted the offending folder... And it WORKED! I figured the program might re-create the folder if it couldn't find it... looks like it did.
Happy coding!

Curious. I also first installed it with anaconda (after installing anaconda, it asks you if you want to also install vscode). So probably an error in the way anaconda installs it.

@AHermann94 the error is caused by corrupted permissions/ownership in your config/data files.
You can either fix the permission/ownership issues or just delete everything and start fresh.
Check ownership / permissions: ls -al ~/.code ~/.vscode* ~/.config/Code*
Delete all config / extensions and start over:
rm -r ~/.code
rm -r ~/.vscode*
rm -r ~/.config/Code*

.code and .config/Code* are equivalent, .vscode is where extensions live. One or more of these may not exist, ignore the not found / no match errors. Use sudo if something can't be deleted.
For windows users you probably need to see #3884 for the APPDATA dirs.

I had this message pop up on my openSUSE Leap 15.0 installation until I granted group/world write permission to the /run/user directory so that VS Code could write "*.sock" files there.


Inbound audio as ffmpeg stream

I'm trying to implement 2-way audio for Eufy's Doorbells which support only P2P.
For that I would need to route the webrtc audio stream to an ffmpeg process that trancodes the audio and sends it to a tcp socket.
Is something like that possible with go2rtx?

Well. First. How do you plan to get video and audio from P2P?

I have a little process that provides audio and Video from the camera via 2 socket inputs which I defined in the go2rtc yaml. Works like charm

Do you have open example, how do you do it?

This is the project:
It's an HA addon based on your docker Container plus a python process to deal with the eufy camera via a websocket:
https://github.com/oischinger/eufyp2pstream

Well. WebRTC > go2rtc > ffmpeg > python > nodejs. Very complicated. Needs time to understand all of this :)

Yes, the stack is a bit crazy. The stack needs some work ;)
So far this is just a proof of concept. A/V worked fine. But I'm not sure if a backchannel is possible the way I think about it. Since my SDP from ffmpeg doesn't include the backchannel information I wonder if it's possible to establish a stream for it at all


Segfault when passing empty Tensor to cholesky_solve

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 18.04 (Linux 93fd36b9ffb5 4.9.125-linuxkit #1 SMP Fri Sep 7 08:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux)
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): Binary
TensorFlow version (use command below): v1.14.0-rc1-22-gaf24dc91b5 1.14.0
Python version: Python 3.6.8
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: N/A
GPU model and memory: N/A

Describe the current behavior
When passing an empty Tensor as the second argument to the tf.cholesky_solve function a segfault is encountered.
Valgrind reports the following:
==8399== Process terminating with default action of signal 11 (SIGSEGV)
==8399==  Access not within mapped region at address 0x0
==8399==    at 0x1896E2B0: tensorflow::MatrixTriangularSolveOp<double>::ComputeMatrix(tensorflow::OpKernelContext*, absl::InlinedVector<Eigen::Map<Eigen::Matrix<double, -1, -1, 1, -1, -1> const, 0, Eigen::Stride<0, 0> >, 4ul, std::allocator<Eigen::Map<Eigen::Matrix<double, -1, -1, 1, -1, -1> const, 0, Eigen::Stride<0, 0> > > > const&, absl::InlinedVector<Eigen::Map<Eigen::Matrix<double, -1, -1, 1, -1, -1>, 0, Eigen::Stride<0, 0> >, 4ul, std::allocator<Eigen::Map<Eigen::Matrix<double, -1, -1, 1, -1, -1>, 0, Eigen::Stride<0, 0> > > >*) (in /home/nferguson/venv_cholesky_segfault/lib/python3.6/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so)
==8399==    by 0x18A4A661: tensorflow::LinearAlgebraOp<double>::ComputeTensorSlice(tensorflow::OpKernelContext*, long long, absl::InlinedVector<tensorflow::Tensor const*, 4ul, std::allocator<tensorflow::Tensor const*> > const&, absl::InlinedVector<tensorflow::TensorShape, 4ul, std::allocator<tensorflow::TensorShape> > const&, absl::InlinedVector<tensorflow::Tensor*, 4ul, std::allocator<tensorflow::Tensor*> > const&, absl::InlinedVector<tensorflow::TensorShape, 4ul, std::allocator<tensorflow::TensorShape> > const&) (in /home/nferguson/venv_cholesky_segfault/lib/python3.6/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so)
==8399==    by 0x18A4A996: std::_Function_handler<void (long long, long long), tensorflow::LinearAlgebraOp<double>::Compute(tensorflow::OpKernelContext*)::{lambda(long long, long long)#1}>::_M_invoke(std::_Any_data const&, long long, long long) (in /home/nferguson/venv_cholesky_segfault/lib/python3.6/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so)
==8399==    by 0x214615A3: tensorflow::thread::ThreadPool::Impl::ParallelFor(long long, long long, std::function<void (long long, long long)>) (in /home/nferguson/venv_cholesky_segfault/lib/python3.6/site-packages/tensorflow/libtensorflow_framework.so.1)
==8399==    by 0x2146181E: tensorflow::thread::ThreadPool::ParallelFor(long long, long long, std::function<void (long long, long long)>) (in /home/nferguson/venv_cholesky_segfault/lib/python3.6/site-packages/tensorflow/libtensorflow_framework.so.1)
==8399==    by 0x212C6E80: tensorflow::Shard(int, tensorflow::thread::ThreadPool*, long long, long long, std::function<void (long long, long long)>) (in /home/nferguson/venv_cholesky_segfault/lib/python3.6/site-packages/tensorflow/libtensorflow_framework.so.1)
==8399==    by 0x18A46E44: tensorflow::LinearAlgebraOp<double>::Compute(tensorflow::OpKernelContext*) (in /home/nferguson/venv_cholesky_segfault/lib/python3.6/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so)
==8399==    by 0x213C1D93: tensorflow::(anonymous namespace)::ExecutorState::Process(tensorflow::(anonymous namespace)::ExecutorState::TaggedNode, long long) (in /home/nferguson/venv_cholesky_segfault/lib/python3.6/site-packages/tensorflow/libtensorflow_framework.so.1)
==8399==    by 0x213C20E9: std::_Function_handler<void (), tensorflow::(anonymous namespace)::ExecutorState::ScheduleReady(absl::InlinedVector<tensorflow::(anonymous namespace)::ExecutorState::TaggedNode, 8ul, std::allocator<tensorflow::(anonymous namespace)::ExecutorState::TaggedNode> > const&, tensorflow::(anonymous namespace)::ExecutorState::TaggedNodeReadyQueue*)::{lambda()#1}>::_M_invoke(std::_Any_data const&) (in /home/nferguson/venv_cholesky_segfault/lib/python3.6/site-packages/tensorflow/libtensorflow_framework.so.1)
==8399==    by 0x2145F6D3: Eigen::ThreadPoolTempl<tensorflow::thread::EigenEnvironment>::WorkerLoop(int) (in /home/nferguson/venv_cholesky_segfault/lib/python3.6/site-packages/tensorflow/libtensorflow_framework.so.1)
==8399==    by 0x2145E543: std::_Function_handler<void (), tensorflow::thread::EigenEnvironment::CreateThread(std::function<void ()>)::{lambda()#1}>::_M_invoke(std::_Any_data const&) (in /home/nferguson/venv_cholesky_segfault/lib/python3.6/site-packages/tensorflow/libtensorflow_framework.so.1)
==8399==    by 0x2212D9DF: ??? (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.25)

Describe the expected behavior
Although we clearly shouldn't be passing an empty Tensor to this method, I would expect an exception to occur (in Python) explaining that the input is invalid, rather than a segfault.
Code to reproduce the issue
Run the following code:
import numpy as np
import tensorflow as tf

def go():

    with tf.Graph().as_default():

        with tf.Session() as sess:

            X = tf.placeholder(shape=None, dtype=tf.float64)

            rhs = X[1:]
            rhs = tf.reshape(rhs, shape=(-1, 1))

            chol = tf.ones(shape=(1, 1), dtype=tf.float64)

            iP0 = tf.cholesky_solve(chol, rhs)

            feed_dict = {X: np.asarray([1.])}
            print(sess.run(iP0, feed_dict=feed_dict))

            print('SUCCESS!')

go()

Here the rhs argument to cholesky_solve ends up as an empty Tensor (it has a shape of (0, 1)), which appears to cause the segfault.

I am able to reproduce the issue.Thanks!

@nfergu There was some updates related to this issue. Can you please check whether the issue still persists. Please use tf-nightly and let us know the status. Thanks!

I think it was resolved. Closing due to lack of recent activity. Please open new ticket if you see similar issue. Thanks!


[release/1.2] cherry-pick: Move ctr run --isolation to Windows only

Cherry-pick #2828 since it is effectively a bug-fix as there is no use of the flag on non-Windows.
Signed-off-by: Justin Terry (VM<EMAIL_ADDRESS>

Codecov Report

Merging #3527 into release/1.2 will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           release/1.2    #3527   +/-   ##
============================================
  Coverage        43.66%   43.66%
============================================
  Files              101      101
  Lines            10816    10816
============================================
  Hits              4723     4723
  Misses            5357     5357
  Partials           736      736

Flag
Coverage Δ

#linux
47.25% <ø> (ø)
:arrow_up:

#windows
40.78% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

LGTM


Added regex pattern to color map

Added the option to specify a regex to the color map and added the option to the sandcastle example for color map.

Just that comment, this looks good, @ggetz.  Please check items off the roadmap, https://github.com/AnalyticalGraphicsInc/3d-tiles/issues/2, as you finish them.

Fixed and marked off on the roadmap.

Looks good!


Circuit.SetActiveBus(BusName) is not working

When working with an Circuit and solving a particular DSS diagram and I make a call to Circuit.SetActiveBus(BusName) the Active bus get overwritten with an empty string.  I made the following set of calls.
    buses, err := Circuit.AllBusNames()
    println(buses)
    vmags, err := Circuit.AllBusVmagPu()
    prop, err := dssInstance.Circuit.ActiveCktElement.Properties.Get_Val()
    println(prop)
    println(vmags)
    busname1, err := Circuit.ActiveBus.Name()
    println(busname1)
    num, err := Circuit.SetActiveBus(BusName)
    busname2, err := Circuit.ActiveBus.Name()

From the screen shot below you can see the debugger values that of the resulting calls, and the buses that are available. The BusName value in the SetActiveBus call is "p4".

I think I see the issue (missing some defer), let me test and push a fix.

Awesome thank you.

Done, should work now. It seems it was missing in 8 functions, SetActiveBus being one of them.

Yes that changes now work. Thanks for fixing that issue.


[MCW] Swin_s model with new Conv API on  n150

Executive summary:

Reference commit

Resolution = 512x512, batch=1, batch_size=8 makes issue for conv.

Current pcc of swin_s transformer is > 0.82, This pcc dropped from 0.99 to 0.82 due to using shard MM in patch_merging and mlp sub_module.
swin_s_transformer.csv

Issues listed for torch ops used: slice, roll, masked_fill, variants of reshape and permute.

Current work status: commit

ToDo: Optimize the model, check if the masked fill part can be preprocessed.

Current Issues based on reference commit:
open:
#12431
#12157 (roll)
#12154 (variant of permute)
#12153 (variant of reshape)
#2795 (masked_fill)
Closed:
#8920 (slice)
#9011
#8926
sub-tasks:

[ ] [MCW] Refactor swin_s to use new Conv API on n150
[ ] #12081

Cuurent, Perf sheets for mlp and patch_merging sub_modules:
mlp.csv
patch_merging.csv

Current, Perf sheet of transformer block.
transformer_block.csv

@punithsekar , we have a workaround for masked_fill (#2795). Please test it.


Automator: update istio/client-go@master dependency in istio/istio@master

Generated by Automator - 2021-06-17T18:51:21+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
341209ff281ee0f87cfd9e9e3df582b56776f79f
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-multicluster-tests_istio

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
341209ff281ee0f87cfd9e9e3df582b56776f79f
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/test integ-pilot-multicluster-tests_istio

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
341209ff281ee0f87cfd9e9e3df582b56776f79f
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-cni-k8s-tests_istio
8bc467d92753b4bbd16ec83bb5ce5fe4ed3d541c
link
/test integ-cni-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-cni-k8s-tests_istio

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-cni-k8s-tests_istio
8bc467d92753b4bbd16ec83bb5ce5fe4ed3d541c
link
/test integ-cni-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.