Create 1.md

:warning: Validation status: warnings

File
Status
Preview URL
Details

docset1/1.md
:warning:Warning
View
Details

docset1/1.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

docset1/1.md
:warning:Warning
View
Details

docset1/2.md
:warning:Warning
View
Details

docset1/3.md
:warning:Warning
View
Details

docset1/4.md
:warning:Warning
View
Details

docset1/1.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/2.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/3.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/4.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

docset1/1.md
:warning:Warning
View
Details

docset1/2.md
:warning:Warning
View
Details

docset1/3.md
:warning:Warning
View
Details

docset1/4.md
:warning:Warning
View
Details

docset1/5.md
:warning:Warning
View
Details

docset1/1.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/2.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/3.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/4.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/5.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

docset1/1.md
:warning:Warning
View
Details

docset1/2.md
:warning:Warning
View
Details

docset1/3.md
:warning:Warning
View
Details

docset1/4.md
:warning:Warning
View
Details

docset1/5.md
:warning:Warning
View
Details

docset1/6.md
:warning:Warning
View
Details

docset1/1.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/2.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/3.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/4.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/5.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/6.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

docset1/1.md
:warning:Warning
View
Details

docset1/10.md
:warning:Warning
View
Details

docset1/2.md
:warning:Warning
View
Details

docset1/3.md
:warning:Warning
View
Details

docset1/4.md
:warning:Warning
View
Details

docset1/5.md
:warning:Warning
View
Details

docset1/6.md
:warning:Warning
View
Details

docset1/7.md
:warning:Warning
View
Details

docset1/8.md
:warning:Warning
View
Details

docset1/9.md
:warning:Warning
View
Details

docset1/1.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/10.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/2.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/3.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/4.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/5.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/6.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/7.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/8.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/9.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

docset1/1.md
:warning:Warning
View
Details

docset1/10.md
:warning:Warning
View
Details

docset1/11.md
:warning:Warning
View
Details

docset1/2.md
:warning:Warning
View
Details

docset1/3.md
:warning:Warning
View
Details

docset1/4.md
:warning:Warning
View
Details

docset1/5.md
:warning:Warning
View
Details

docset1/6.md
:warning:Warning
View
Details

docset1/7.md
:warning:Warning
View
Details

docset1/8.md
:warning:Warning
View
Details

docset1/9.md
:warning:Warning
View
Details

docset1/1.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/10.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/11.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/2.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/3.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/4.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/5.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/6.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/7.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/8.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/9.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

docset1/1.md
:warning:Warning
View
Details

docset1/10.md
:warning:Warning
View
Details

docset1/11.md
:warning:Warning
View
Details

docset1/12.md
:warning:Warning
View
Details

docset1/2.md
:warning:Warning
View
Details

docset1/3.md
:warning:Warning
View
Details

docset1/4.md
:warning:Warning
View
Details

docset1/5.md
:warning:Warning
View
Details

docset1/6.md
:warning:Warning
View
Details

docset1/7.md
:warning:Warning
View
Details

docset1/8.md
:warning:Warning
View
Details

docset1/9.md
:warning:Warning
View
Details

docset1/1.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/10.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/11.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/12.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/2.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/3.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/4.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/5.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/6.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/7.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/8.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/9.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

docset1/1.md
:warning:Warning
View
Details

docset1/10.md
:warning:Warning
View
Details

docset1/11.md
:warning:Warning
View
Details

docset1/12.md
:warning:Warning
View
Details

docset1/13.md
:warning:Warning
View
Details

docset1/2.md
:warning:Warning
View
Details

docset1/3.md
:warning:Warning
View
Details

docset1/4.md
:warning:Warning
View
Details

docset1/5.md
:warning:Warning
View
Details

docset1/6.md
:warning:Warning
View
Details

docset1/7.md
:warning:Warning
View
Details

docset1/8.md
:warning:Warning
View
Details

docset1/9.md
:warning:Warning
View
Details

docset1/1.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/10.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/11.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/12.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/13.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/2.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/3.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/4.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/5.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/6.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/7.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/8.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/9.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

docset1/1.md
:warning:Warning
View
Details

docset1/10.md
:warning:Warning
View
Details

docset1/11.md
:warning:Warning
View
Details

docset1/12.md
:warning:Warning
View
Details

docset1/13.md
:warning:Warning
View
Details

docset1/14.md
:warning:Warning
View
Details

docset1/15.md
:warning:Warning
View
Details

docset1/16.md
:warning:Warning
View
Details

docset1/2.md
:warning:Warning
View
Details

docset1/3.md
:warning:Warning
View
Details

docset1/4.md
:warning:Warning
View
Details

docset1/5.md
:warning:Warning
View
Details

docset1/6.md
:warning:Warning
View
Details

docset1/7.md
:warning:Warning
View
Details

docset1/8.md
:warning:Warning
View
Details

docset1/9.md
:warning:Warning
View
Details

docset1/1.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/10.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/11.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/12.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/13.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/14.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/15.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/16.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/2.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/3.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/4.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/5.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/6.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/7.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/8.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

docset1/9.md

Line unspecified: [Warning] title is mandatory for each page, please make sure your content file meet at least one of below requirements: "#" exist in MD for <h1> or "title" meta exist in MD YAML block

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset1/1.md
:white_check_mark:Succeeded
View

docset1/10.md
:white_check_mark:Succeeded
View

docset1/11.md
:white_check_mark:Succeeded
View

docset1/12.md
:white_check_mark:Succeeded
View

docset1/13.md
:white_check_mark:Succeeded
View

docset1/14.md
:white_check_mark:Succeeded
View

docset1/15.md
:white_check_mark:Succeeded
View

docset1/16.md
:white_check_mark:Succeeded
View

docset1/17.md
:white_check_mark:Succeeded
View

docset1/2.md
:white_check_mark:Succeeded
View

docset1/3.md
:white_check_mark:Succeeded
View

docset1/4.md
:white_check_mark:Succeeded
View

docset1/5.md
:white_check_mark:Succeeded
View

docset1/6.md
:white_check_mark:Succeeded
View

docset1/7.md
:white_check_mark:Succeeded
View

docset1/8.md
:white_check_mark:Succeeded
View

docset1/9.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Bump Jenkins Core to 2.401 + Add support for OutputStreamTaskListener

Bump Jenkins Core to 2.401 + Add support for OutputStreamTaskListener
Fix for:

https://github.com/jenkinsci/opentelemetry-plugin/issues/749

Build will pass after merging:

https://github.com/jenkinsci/opentelemetry-plugin/pull/780

Testing done

### Submitter checklist
- [ ] Make sure you are opening from a **topic/feature/bugfix branch** (right side) and not your main branch!
- [x] Ensure that the pull request title represents the desired changelog entry
- [x] Please describe what you did
- [ ] Link to relevant issues in GitHub or Jira
- [ ] Link to relevant pull requests, esp. upstream and downstream changes
- [ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

related to changes in the workflow plugin https://github.com/jenkinsci/workflow-api-plugin/pull/294 and https://github.com/jenkinsci/workflow-api-plugin/pull/294

@kuisathaverat it's ready for review. I can't say we improve the readability of the code. the nuances between BuildListener and TaskListener didn't help us 😄

I will take a look next week, overall LGTM, but I want to make a manual test of everything.


Catalog page not showing all components at the first time

Describe the bug
Go to the catalog page, by default kind=compnent will be used as default, not all components will be showed at the first time, to see all components you need to change kind=api for example and them select again kind=component
Expected Behavior
Open Catalog page and see all components without need to interact with the page
Versions of software used and environment
RHDH Helm Chart  1.0-190-CI
Platform: OpenShift version4.13.19

@gustavolira Can I ask what you mean by not everything is shown? Is the title of your initial table of components Owned Components similar to this? If so, then this is expected since the default is to show all components owned by your backstage identity.

To view all the components, just press the All button in the filters:

This should then show All Components:

@Zaperex
Just hitting the page

Changing the kind to another type and setting back kind = componentn

"Changing the 'kind' to a different type and then resetting it to 'kind = componentn'."

Yes it says all=3 but the default filter is for owned components which in your case has 1 component. To view all you just need to select the all filter

@Zaperex I understand, but just change the component to another type and them select kind=component again should keep the same behavior

Oh I think that's because you don't have any owned API entities so it'll then default to all. It'll then keep the all filter when you move back to component.

Hi @gustavolira,
This behavior is expected and desired.
Assume your company uses Backstage and the catalog has 10s of thousands of entries in it. You log in to Backstage, go to the catalog page and you will be presented with 10s of thousands of entries. This is not very good UX, since a regular developer is not interested in ALL the components, his attention is focused only on the components he OWNS or he STARRED (aka bookmarked).
In normal cases, guest login wouldn't be even enabled but if it is - Guests don't own any catalog entries. So.. presenting any guest with an empty catalog would be consistent UX, but also wouldn't make much sense... Why present them with an empty screen?
As a result, we have this 2 fold behavior - different for guests where everything is present and focused for logged-in users.
If you don't mind, I'll close this as not a bug. 🙂


Compiler is confused between parseURI and parseUri

While renaming packages in ceylon.formatter, I noticed that the compiler is now confused between parseURI and parseUri in ceylon.file. It now generates a single class that mixes both names in parseUri.class:
@Ceylon(major=8, minor=1)
@Method
public final class parseURI_
{
  @DocAnnotation.annotation.(description="Obtain a `Path` given the string representation\nof a URI. The scheme determines the file system\nthe path belongs to. The scheme `file:` refers\nto the default file system.")
  @DeprecationAnnotation.annotation.(description="Use [[parseUri]]")
  @SharedAnnotation.annotation.
  @NonNull
  @TypeInfo("ceylon.file::Path")
  @Deprecated
  public static Path parseURI(@Name("uriString") @NonNull String uriString)
  {
    return parseUri_.parseUri(uriString);
  }
}

The resulting error in ceylon.formatter is:
[ceylon-compile] /Users/bastien/Dev/ceylon/ceylon.formatter/source/test/ceylon/formatter/testSamples.ceylon:7: error: the 'ImportVisitor' caused an exception visiting a 'Import' node: '"org.eclipse.ceylon.langtools.tools.javac.jvm.ClassReader$BadClassFile: bad class file: /Users/bastien/.ceylon/repo/ceylon/file/1.3.4-SNAPSHOT/ceylon.file-1.3.4-SNAPSHOT.car(ceylon/file/parseUri_.class)
[ceylon-compile] import ceylon.file {
[ceylon-compile] ^
[ceylon-compile]     class file contains wrong class: ceylon.file.parseURI_
[ceylon-compile]     Please remove or make sure it appears in the correct subdirectory of the classpath."' at 'org.eclipse.ceylon.langtools.tools.javac.jvm.ClassReader.badClassFile(ClassReader.java:354)'

Similar message in ceylon-ide-intellij, but it looks like the cause is different:
[ceylon-compile] /Users/bastien/Dev/ceylon/ceylon-ide-intellij/source/org/intellij/plugins/ceylon/ide/messages/ProblemsModel.ceylon:27: error: the 'ExpressionVisitor' caused an exception visiting a 'BaseMemberExpression' node: '"org.eclipse.ceylon.langtools.tools.javac.jvm.ClassReader$BadClassFile: bad class file: /Users/bastien/Dev/ceylon/ceylon-ide-intellij/intellij-repository/com.intellij.idea-current.jar(com/intellij/execution/impl/ExecutionManagerKtImplKt$sam$Consumer$3f5f7fa1.class)
[ceylon-compile]                         => initial + messages.count((msg) => msg.severity == s));
[ceylon-compile]                            ^
[ceylon-compile]     undeclared type variable: T
[ceylon-compile]     Please remove or make sure it appears in the correct subdirectory of the classpath."' at 'org.eclipse.ceylon.langtools.tools.javac.jvm.ClassReader.badClassFile(ClassReader.java:354)'

package com.intellij.execution.impl;

import com.intellij.util.Consumer;
final class ExecutionManagerKtImplKt$sam$Consumer$3f5f7fa1 implements Consumer {
...
}

package com.intellij.util;

public abstract interface Consumer<T>{
...
}

Should I open a separate issue?

Are you sure this is actually wrong? Remember we have to account for case-insensitive filesystems.

Were you able to build the formatter on your Mac recently? If yes, then I think it's a regression. TBH, it's possible I hadn't done a full build since parseUri was added, so I can't say for sure it used to work on my machine.

Not sure about MS, but Apple seems to have chosen case insensitivity by default for the long term with APFS.
So it may be best to disallow top-levels of the same "kind" with conflicting case insensitive names (top-level functions, values, and objects are suffixed with _, so single conflicts between top-levels and classes and interfaces are ok.)

It seems to me that if those two declarations are located in the same source file, it won't cause any problem before compilation. When the compiler kicks in, IIUC it will generate class files in the zip file directly, which is supposed to handle case sensitivity correctly. Or perhaps the compiler uses temporary files on disk before zipping them in the .car?

Or perhaps the compiler uses temporary files on disk before zipping them in the .car?

That appears to be the case.

(case conflicts don't cause a problem on Linux)


Why aria-hiden = "true" is set to SVGs of category buttons

Hi,
I enabled category buttons on emoji picker but those icons are not displaying SVGs because aria-hidden="true" is set to it.
Can you please remove that attribute if there is no specific intension behind setting it?

I'm not sure why the SVGs are not displaying because aria-hidden is true. Do you have some code you can share?
aria-hidden does NOT control the visibility of elements. This simply means it will not be read by a screen reader. The icons themselves are decorative only - the names of the categories are read by the screen reader via the title attribute.
A repo or codepen showing your issue would be helpful - I don't see why aria-hidden would make the SVGs not appear for you.


Docs.MS Release Updates for azure-sdk-template

Update docs metadata and targeting for release of azure-sdk-template

Docs Build status updates of commit d0d30e7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/preview/sdk-template
:white_check_mark:Succeeded

package.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


l298: Initial implementation

This was tested on the RobotBase Dual H-Bridge motor control board.
There are two examples:
l298-example: This example demonstrates using the class to contol one
of the H-Brdges to control a DC motor.
l298-stepper-example: This example demonstrates using the class to
control a 4-wire dual-phase stepper motor.
Signed-off-by: Jon Trulson<EMAIL_ADDRESS>Signed-off-by: Zion Orent<EMAIL_ADDRESS>

Needed to move the c++ examples to the examples/c++ folder.  Thanks for the great work!  Merged and closing.


Add Nestor Salceda (nestorsalceda) to the sysdig-secure plugin

Hello,
I'm one of the maintainers of Sysdig Secure plugin and I would like to cut a new release, so that I'm requesting permissons to upload it to artifactory.
Thank you!

Hey,
Is there anything else I can do on my side to get this merged?
Thank you!

One of these maintainers to approve:

One of these maintainers to approve:

Okey, I think that @markyjackson-taulia already approved. AFAIK he is jequals5, isn't he?

if marky can confirm that, the joys of separate systems for identity...


Add isMinValueAtCenter property to RadarChartData

Summary
This PR adds the isMinValueAtCenter flag to the RadarChartPainter class to allow the minimum value to be centered in the RadarChart.
Related Issues

Fixes #1351
Fixes #1442

Changes

Added isMinValueAtCenter flag to RadarChartData
Updated RadarChartPainter methods to support centering the minimum value when isMinValueAtCenter is true

isMinValueAtCenter Comparison

isMinValueAtCenter is false
isMinValueAtCenter is true

Thank you for the wonderful product. I use it all the time.
After implementing the changes, I realized that the isMinValueAtCenter flag might not be necessary. Should the minimum value be centered by default? If the current behavior is a bug, it would be better to make the minimum value centered by default instead of adding a flag. This would simplify the code and avoid unnecessary complexity.

Yes I think it is a bug and it should always be centered

I identified a bug where the behavior did not center around zero as expected, so I made corrections. However, I couldn’t get the test to pass. I'm not sure how to adjust the test code to reflect the fix, so I've left it unresolved.


Spearbit-65

Description

Type of change

[ ] Docs change / dependency upgrade
[ ] Configuration / tooling changes
[ ] Refactoring
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Requires changes in customer code

High-level change(s) description - from the user's perspective

Related Issue(s)
Fixes
Related pull request(s)

I did some cleanup around the AssetLogic interfaces:

All the handle* functions are now the ones that deal with wrapping and unwrapping native assets
They return an address asset to show the asset that was transferred out of the contracts
I removed any returning of amount -- because we don't support fee-on-transfer tokens (they revert when trying to transfer to the contract) we can always assume amount in == amount specified
I cleaned up any code handling potential differences in amount


Error with externalsecret: invalid header field value for "Authorization"

Hello!
I am trying to install external-secrets on my EKS cluster (with aws secret manager)  and the ExternalSecret created fails with the following error:
Warning UpdateFailed 85s (x27 over 14m) external-secrets RequestError: send request failed
caused by: Post "https://secretsmanager.us-east-1.amazonaws.com/": net/http: invalid header field value for "Authorization"

I've been looking all day for someone who has reported something similar but I can't find a problem with a similar message.
This is my manifest:
apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
   name: app-secret
specification:
   refreshInterval: 1m
   secretStoreRef:
     name: global-secret-store
     kind: ClusterSecretStore
   target:
     name: app-secret
     creationPolicy: Owner
   dataFrom:
   -extract:
       key: app-secret

My global-secret-store describe:
...
Spec:
  Provider:
    Aws:
      Auth:
        Secret Ref:
          Access Key ID Secret Ref:
            Key:        access-key
            Name:       awssm-secret
            Namespace:  default
          Secret Access Key Secret Ref:
            Key:        secret-access-key
            Name:       awssm-secret
            Namespace:  default
      Region:           us-east-1
      Service:          SecretsManager
Status:
  Capabilities:  ReadWrite
  Conditions:
    Last Transition Time:  2023-01-11T20:33:20Z
    Message:               store validated
    Reason:                Valid
    Status:                True
    Type:                  Ready
Events:
  Type    Reason  Age              From                  Message
  ----    ------  ----             ----                  -------
  Normal  Valid   6s (x2 over 6s)  cluster-secret-store  store validated

These are the pod logs:
{"level":"info","ts":1673468864.0217874,"logger":"provider.aws","msg":"using aws session","region":"us-east-1","credentials" :{}}
{"level":"info","ts":1673468864.0218863,"logger":"provider.aws.secretsmanager","msg":"fetching secret map","key":"app-secret"}
{"level":"info","ts":1673468864.0218961,"logger":"provider.aws.secretsmanager","msg":"fetching secret value","key":"app-secret","version" :"AWSCURRENT"}
{"level":"error","ts":1673468864.3562038,"logger":"controllers.ExternalSecret","msg":"could not get secret data from provider","ExternalSecret":"default/app-secret" ,"error":"RequestError: send request failed\ncaused by: Post \"https://secretsmanager.us-east-1.amazonaws.com/\": net/http: invalid header field value for \"Authorization\ "","stacktrace":"github.com/external-secrets/external-secrets/pkg/controllers/externalsecret.(*Reconciler).Reconcile\n\t/home/runner/work/external-secrets/external-secrets /pkg/controllers/externalsecret/externalsecret_controller.go:190\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/home/runner/go/pkg/mod/ sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:122\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n \t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:323\nsigs.k8s.io/controller-runtime/pkg /internal/c ontroller.(*Controller).processNextWorkItem\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.1/pkg/internal/controller/controller.go:274\nsigs .k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@ v0.14.1/pkg/internal/controller/controller.go:235"}

Does anyone have any idea why this error may occur or where I can continue looking?
Thanks!

after hours of search...
was a new line on the secret_key...
sorry!

no worries :)


using API - bug found

YOURLS version: v 1.7.1 – 9 queries
PHP version:  5.6.27
Any other useful information depending on context (server version, mysql version, browser version, OS version...)

Reproducible Bug Summary

Setup the API

Connect the API and then have it shorten a Long URL in this format:
http://somelink.com/affiliate.php?aff=23&pid=111

The url gets shortened, but the &pid=111 no matter what I put there, always falls off, nothing after the & sign.

This is a bug because... if I go into the admin I can put long urls having that exact url:
http://somelink.com/affiliate.php?aff=23&pid=111
and it works fine, but having the API create it, does not work. it never passes anything past the &.
I had it put it like this:
http://somelink.com/affiliate.php?aff=23?pid=111
and that worked, so it put that whole thing in there, but that does not work because two ? marks make the second one absolete... when I put the & back as either just a & or & it breaks both ways.

Sounds like the input isn't being urlencoded.

how do I encode the url then? what do you recommend?

Look for a url encoding function in whatever language you're using to call the API. Most have such a thing. Or for this specific case you can just string-replace '&' with '%26'.

ah ok. That worked. :) I just had it put this:
var affUrl = "[LinkCode]";
var long1 = encodeURI(affUrl + "%26pid=170"); // Probably best to use ? instead of & here
var long2 = encodeURI(affUrl + "%26pid=171");
then it built it right at the api. :) thank you!!
I first tried it as:
var affUrl = "[LinkCode]";
var long1 = encodeURI(affUrl + "&pid=170"); // Probably best to use ? instead of & here
var long2 = encodeURI(affUrl + "&pid=171");
But that encodeURI did not change the & to %26, so I did it manually, and tested it and it works. :)
Thank you!


Context missing when using Dynamic

Describe the bug
I'm using the @thisbeyond/solid-dnd drag and drop library. In a standard setup it works fine:
function App() {
  return (
    <MyDragDropProvider>
      <MyDraggable id="A">Draggable</MyDraggable>
      <MyDropzone id="B">Dropzone</MyDropzone>
    </MyDragDropProvider>
  );
}

https://stackblitz.com/edit/solid-vite-gigzxd?file=src%2Findex.jsx
However, I'm trying to render the above component tree dynamically using <Dynamic>. This is needed as we're retrieving a "document" as JSON from the backend and then rendering it using components. Similar rendering an MDX file via high1/solid-jsx.
In this scenario, with the exact same components, the context consumer components are not getting the latest data from the context.
Here's the MDX example:
## Hi

<MyDragDropProvider>
  <MyDraggable id="A">Draggable</MyDraggable>
  <MyDropzone id="B">Dropzone</MyDropzone>
</MyDragDropProvider>

https://stackblitz.com/edit/solid-vite-gjiro1?file=src%2FMyDraggable.jsx
Here is the example with my code using Dynamic:
https://stackblitz.com/edit/solid-vite-6ooxdn
The following error occurs:
create-draggable.js:6 Uncaught TypeError: useDragDropContext is not a function or its return value is not iterable     at createDraggable
This is because the context is returning null when it should be returning an array. It returns an array in the first example at the top so it seems to be more of an issue with Dynamic rather than solid-dnd.
Your Example Website or App
https://stackblitz.com/edit/solid-vite-gjiro1?file=src%2FHelloWorld.mdx,src%2FMyDraggable.jsx
Steps to Reproduce the Bug or Issue
To the the example url. See the errors in the console.
Expected behavior
Expect to see:
https://stackblitz.com/edit/solid-vite-gigzxd?file=src%2FMyDraggable.jsx
But get an error in the console:
https://stackblitz.com/edit/solid-vite-gjiro1?file=src%2FHelloWorld.mdx,src%2FMyDraggable.jsx
Screenshots or Videos
No response
Platform

OS: macOS
Browser: Chrome
Version: 101

Additional context
No response

It looks like the children are being created before the parent.. ie before the Provider. There is logic where deserializeElement calls itself for arrays and that ends up rendering beforehand. I haven't completely worked out the fix for the example, but that is where I'd start.

Of course! It was the order of creation that was causing the issue. Thank you so much.
For everyone else's reference, here is the (unoptimized) working code:
import { mergeProps, createMemo } from 'solid-js';
import { Dynamic, For } from 'solid-js/web';
import get from 'dlv';
import * as components from './components'

export function DocRenderer(props) {
  const renderedItem = createMemo(() => {
    return props.item ? <RenderNode {...props.item} /> :
No item
;
  });

  return
{renderedItem()}
;
}

export function RenderNode(props) {
  if (typeof props === 'string') {
    return props;
  }

  let { children, name, ...rest } = props;
  let component = get(components, name) || props.name.toLowerCase();
  return (
    <Dynamic {...mergeProps({ component }, rest)}>
      <For each={children}>{item => <RenderNode {...item} />}</For>
    </Dynamic>
  );
}

// usage
// <DocRenderer item={doc} />


Swagger scan findings are shown multiple times

Consider the following yaml files:

./test/swagger.yaml

openapi: "3.0.0"
info:
  description: "my description"
  version: "1.8.8"
  title: "my title"
servers:
  - url: "http://localhost:3000/"
tags:
- name: "users"
  description: "users tag description"
paths:
  /users/{userId}:
    $ref: "./paths/users/user.yaml"

components:
  schemas:
    MyResponse:
      $ref: "./schemas/MyResponse.yaml"

./test/paths/users/user.yaml

get:
  tags:
    - "users"
  summary: "Get user"
  responses:
    200:
      description: "Ok"
      content:
        application/json:
          schema:
            $ref: "../../schemas/MyResponse.yaml"
    404:
      description: "not found"
      content:
        application/json:
          schema:
            $ref: "../../schemas/MyResponse.yaml"

./test/schemas/MyResponse.yaml

properties:
    message:
      type: string
type: object

When running docker run -t -v $PWD:/path checkmarx/kics:v1.7.2 scan -p /path/test we get the same finding multiple times. For example:

As you can see, test/swagger.yaml:13  appears twice in the results for the same query.
In addition, the above query seems as related to test/schemas/MyResponse.yaml but the code snippets are of test/swagger.yaml:13 and test/swagger.yaml:18

Hello @ayala-orca
We are working in a new feature that will clarify those references. In this case, there is 2 vulnerabilities in the same line:

"paths.{{/users/{userId}}}.get.responses.404.content.{{application/json}}.schema.properties.message.type"
"paths.{{/users/{userId}}}.get.responses.202.content.{{application/json}}.schema.properties.message.type"

It shows that the problem is in test/swagger.yaml because you referenced in it test/schemas/MyResponse.yaml file

Currently, it seems like ./test/schemas/MyResponse.yaml is being scanned multiple times - once per ref.
In some big swagger files, we encountered a serious performance issue - the scan didn't end even after half an hour.
Is this behavior expected to be changed as part of this feature?

Thanks @cx-henriqueAlvelos
Currently, it seems like ./test/schemas/MyResponse.yaml is being scanned multiple times - once for each reference. We observed a significant performance issue when large swagger files were processed.
Is this behavior expected to be changed as part of this new feature?

@cx-henriqueAlvelos
can you try to explain a bit more about the suggested direction/solution
e.g. are we aiming to reduce the issues raised to a single one OR have it more accurately surfaced?

Hello @lior-orca.
Currently, we are working internally in order to find the best approach


Fix output raster type for raw binary math map algebra functions

When a raw binary math operation is performed, there are some cases where the output raster type will be wrong.

When both args are rasters, it uses the type of the first one. But it should use the "largest" type between the two so that adding an int raster to a float raster should produce a float raster.
When one arg is a constant, the output raster type will be the same as the raster arg type. However, if the raster is type int, and the arg is float, the output type should be float.

It looks like a similar problem could occur in RawUnaryMapOp as well


Proposal: Retweet author tweets

I’m proposing changing the behaviour of the Read Rust Twitter account to retweet author tweets when they can be found instead of creating a new tweet @readrust.
The primary motivation for this change is to boost the authors voice. This would also make it easier for followers to like or reply to the original author on Twitter. Additionally there is some overlap in the posts shared on the official Rust account and the Read Rust account. Retweets would ensure you were only shown a tweet once if you follow both accounts.
The main downside of this change is that the tweets from the Read Rust account would no longer all follow the same structure: "Title by Author #category #hashtags".
As an example for this post:
Rust review: The match keyword by Julio Merino: https://t.co/nRKCm2Mk7u #language— Read Rust (@read_rust) June 19, 2018
I would have retweeted this one instead:
Rust's match and pattern matching is something that should exist in other languages... aka the topic for today's part of my Rust review! https://t.co/AWVW1gYMBK— Julio Merino (@jmmv) June 15, 2018

I think this is a great idea. One way to implement it would be to allow users to add a link to a tweet they would like retweeted in their submission. (Maybe this is already what you had in mind, but I read it as if you would do it automatically by searching their profile or something.)
You could modify the submission template to allow users to optionally provide a link to a tweet which would be used instead of the default Read Rust tweet. Restrictions could be added to enforce that the tweet actually contains a link to the article, etc.
A big benefit to this is that it allows authors to choose not only which tweet they want amplified, but also when they want their tweet amplified at all. It is completely opt-in and up to the author to decide when they want this and when they just want the regular Read Rust tweet.

Could you retweet as a quote and keep the hashtags?

Could you retweet as a quote and keep the hashtags?

Hmm that's an interesting way to keep them. Downside is you wouldn't get the de-duplication that you get with retweets.

One way to submit posts could be to tag @read_rust or #read_rust at the end of the author's tweet. It would be request for retweet :P

Rust's match and pattern matching is something that should exist in other languages... aka the topic for today's part of my Rust review! https://t.co/AWVW1gYMBK @read_rust

— Julio Merino (@jmmv) June 15, 2018


remove task comment

This PR removes a task comment (i.e. a comment referring to a work that could/should be done in the future or was already done). Instead, an issue was created.

@jelgun Thanks a lot for your help.


Unable to enable  / disable interface

Describe the bug
I am inable to enable or disable any ethernet or wireless interface usign raw command.
To Reproduce
[     "/interface/enable",     "=numbers=7" ]
returns
Error executing cmd[["/interface/enable","=numbers=7",".tag=j1rkch4mkc"]]: {}
full flow
[{"id":"23b967fa1e0538d1","type":"mikrotik","z":"ed0ca72e.2817a8","device":"69c2a6db.c414c8","name":"","action":"9","command":"","command-type":"str","x":920,"y":3000,"wires":[["318e156a616d8ed5"]]},{"id":"602704237dd3122f","type":"inject","z":"ed0ca72e.2817a8","name":"sfp1 enable","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"[\"/interface/enable\",\"=numbers=7\"]","payloadType":"json","x":770,"y":3000,"wires":[["23b967fa1e0538d1"]]},{"id":"318e156a616d8ed5","type":"debug","z":"ed0ca72e.2817a8","name":"","active":true,"tosidebar":true,"console":false,"tostatus":true,"complete":"payload","targetType":"msg","statusVal":"payload[0][\".id\"]","statusType":"msg","x":1090,"y":3000,"wires":[]},{"id":"69c2a6db.c414c8","type":"mikrotik-device","host":"<IP_ADDRESS>","port":"8728","username":null,"password":null,"ssl":"api"}]
Expected behavior
succes with every command
i tried many variations like set enable, but no success

Few months passed since you posted here but now I tested and it works for me with for both disable and enable with sfp on hAP ac with ROS v6.49. Do you still have issue with it and if so which device is it and which ROS version?
[{"id":"23b967fa1e0538d1","type":"mikrotik","z":"589710b8.068a1","device":"","name":"","action":"9","command":"","command-type":"str","x":660,"y":1020,"wires":[["318e156a616d8ed5"]]},{"id":"318e156a616d8ed5","type":"debug","z":"589710b8.068a1","name":"","active":true,"tosidebar":true,"console":false,"tostatus":true,"complete":"payload","targetType":"msg","statusVal":"payload[0][\".id\"]","statusType":"msg","x":830,"y":1020,"wires":[]},{"id":"106b5aa2.b9d515","type":"inject","z":"589710b8.068a1","name":"sfp1 enable","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"[\"/interface/enable\",\"=numbers=5\"]","payloadType":"json","x":450,"y":1020,"wires":[["23b967fa1e0538d1"]]},{"id":"3090ed4b.f7dd62","type":"inject","z":"589710b8.068a1","name":"sfp1 disable","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"[\"/interface/disable\",\"=numbers=5\"]","payloadType":"json","x":430,"y":1060,"wires":[["23b967fa1e0538d1"]]}]

@Cooper-Dale if you still haven an issue please reopen.

Prolem was with the policy, I forgot to tick write permission for the node-red group policies.
I was using ROS v6.48, now 7.1


Do not display connection on script tab

Could it be possible to add an option to hide the connection label currently displayed on the title of a script tab?

Yes this is possible. You can configure script title in preferences:

You can see supported variable in "Script title pattern" field tooltip or by pressing ctrl+space.

Oops, I didn't see that option is already existing. Thanks!


ASP.net core Angular 2 template not running.

Hi Team,
I followed all the steps from Steve's blog trying to run the template.
http://blog.stevensanderson.com/2016/10/04/angular2-template-for-visual-studio/
I get this error
In Startup.cs this comes up highlighted.
app.UseWebpackDevMiddleware(new WebpackDevMiddlewareOptions {
HotModuleReplacement = true
});
with message
An exception of type 'System.AggregateException' occurred in System.Private.CoreLib.ni.dll but was not handled in user code
Any idea what might be causing this?
Banging my head for 2 days now.
Please help

Inner exception
call to Node module failed with error: TypeError: Cannot read property 'publicPath' of undefined at createWebpackDevServer (C:\Users\Bilal\node_modules\aspnet-webpack\WebpackDevMiddleware.js:9:43) at module.exports.createWebpackDevServer (C:\Users\Bilal\AppData\Local\Temp\tmp85CD.tmp:19:49) at C:\Users\Bilal\AppData\Local\Temp\tmp8726.tmp:113:19 at IncomingMessage. (C:\Users\Bilal\AppData\Local\Temp\tmp8726.tmp:132:38) at emitNone (events.js:67:13) at IncomingMessage.emit (events.js:166:7) at endReadableNT (_stream_readable.js:921:12)...

Do you have a publicPath defined in your package.json?
module.exports = {
    context: __dirname,
    resolve: {
        extensions: [ '', '.js', '.ts' ]
    },
    output: {
        filename: '[name].js',
        publicPath: '/dist/' // This line
}

this is what my package.json looks like at the moment, unchanged from what was in the template
{
"name": "Angular2Spa",
"version": "0.0.0",
"dependencies": {
"@angular/common": "2.0.0",
"@angular/compiler": "2.0.0",
"@angular/core": "2.0.0",
"@angular/forms": "2.0.0",
"@angular/http": "2.0.0",
"@angular/platform-browser": "2.0.0",
"@angular/platform-browser-dynamic": "2.0.0",
"@angular/platform-server": "2.0.0",
"@angular/router": "3.0.0",
"@types/node": "^6.0.38",
"angular2-platform-node": "~2.0.10",
"angular2-universal": "~2.0.10",
"angular2-universal-polyfills": "~2.0.10",
"aspnet-prerendering": "^1.0.6",
"aspnet-webpack": "^1.0.11",
"bootstrap": "^3.3.7",
"css": "^2.2.1",
"css-loader": "^0.25.0",
"es6-shim": "^0.35.1",
"expose-loader": "^0.7.1",
"extract-text-webpack-plugin": "^1.0.1",
"file-loader": "^0.9.0",
"isomorphic-fetch": "^2.2.1",
"jquery": "^2.2.1",
"preboot": "^4.5.2",
"raw-loader": "^0.5.1",
"rxjs": "5.0.0-beta.12",
"style-loader": "^0.13.0",
"to-string-loader": "^1.1.5",
"ts-loader": "^0.8.2",
"typescript": "^2.0.0",
"url-loader": "^0.5.7",
"webpack": "^1.12.14",
"webpack-externals-plugin": "^1.0.0",
"webpack-hot-middleware": "^2.10.0",
"webpack-merge": "^0.14.1",
"zone.js": "^0.6.21"
}
}

It looks like you have an old version of the template.
Try:
npm i -g generator-aspnetcore-spa to update it, then reinstall a new one. yo aspnetcore-spa etc

@MarkPieszak they're using the Visual Studio template, not the Yeoman generator. It's the same content (not as up-to-date, but should still work).
@bilalhassan88 Is your project really at C:\Users\Bilal\? As in, your application files are at the root of your user directory? That would be extremely unusual and probably isn't what you want. Or if your project is in some other directory (or a subdirectory), then it looks like your machine has node_modules installed badly. I see that the directory C:\Users\Bilal\node_modules\ exists, which is worrying, because that is going to interfere with every Node project you create within your C:\Users\Bilal directory (Node looks for node_modules in all ancestor directories of the one your project is in). I'd suggest deleting C:\Users\Bilal\node_modules and being careful not to run npm install from C:\Users\Bilal. After clearing up any rogue node_modules directories, you may need to re-run the template to create a new project so it can install dependencies properly.

@SteveSandersonMS Thanks for the reply, i have just started with node and had no idea how it operated, will remove it and move my project to another directory.
I was banging my head wondering why this was happening, the template was working great on my office laptop.

@SteveSandersonMS I have same issue
"One or more errors occurred. (Call to Node module failed with error: TypeError: Cannot read property 'publicPath' of undefined\n    at c:\Users\Vikar\Documents\Visual Studio 2015\Projects\Modalin\src\Modalin\node_modules\aspnet-webpack\WebpackDevMiddleware.js:159:59\n    at Array.forEach (native)\n    at Server. (c:\Users\Vikar\Documents\Visual Studio 2015\Projects\Modalin\src\Modalin\node_modules\aspnet-webpack\WebpackDevMiddleware.js:148:32)\n    at Server.g (events.js:291:16)\n    at emitNone (events.js:86:13)\n    at Server.emit (events.js:185:7)\n    at emitListeningNT (net.js:1288:10)\n    at _combinedTickCallback (internal/process/next_tick.js:71:11)\n    at process._tickCallback (internal/process/next_tick.js:98:9))"
this is my webpack config
"use strict";
var webpack = require("webpack");
var path = require("path");
var clone = require("js.clone");
var webpackMerge = require("webpack-merge");
exports.commonPlugins = [
new webpack.ContextReplacementPlugin(
// The (\|/) piece accounts for path separators in *nix and Windows
/angular(\|/)core(\|/)src(\|/)linker/, root("./Client"), {}),
// Loader options
new webpack.LoaderOptionsPlugin({}),
];
exports.commonConfig = {
// https://webpack.github.io/docs/configuration.html#devtool
devtool: "source-map",
resolve: {
extensions: [".ts", ".js", ".json"],
modules: [root("node_modules")]
},
context: __dirname,
output: {
publicPath: '/dist/',
filename: "[name].bundle.js"
},
module: {
rules: [
// TypeScript
{ test: /.ts$/, use: ["awesome-typescript-loader", "angular2-template-loader"] },
{ test: /.html$/, use: "raw-loader" },
{ test: /.css$/, use: "raw-loader" },
{ test: /.json$/, use: "json-loader" }
]
},
plugins: []
};
// Client.
exports.clientPlugins = [];
exports.clientConfig = {
target: "web",
entry: { "main-client": "./Client/boot-client.ts" },
output: {
path: root("wwwroot/dist")
},
node: {
global: true,
crypto: "empty",
__dirname: true,
__filename: true,
process: true,
Buffer: false
}
};
// Server.
exports.serverPlugins = [];
exports.serverConfig = {
target: "node",
entry: { "main-server": "./Client/boot-server.ts" },
output: {
path: root("wwwroot/dist"),
libraryTarget: "commonjs2"
},
module: {
rules: [
{ test: /@angular(\|/)material/, use: "imports-loader?window=>global" }
]
},
externals: includeClientPackages(/@angularclass|@angular|angular2-|ng2-|ng-|@ng-|angular-|@ngrx|ngrx-|@angular2|ionic|@ionic|-angular2|-ng2|-ng/),
node: {
global: true,
crypto: true,
__dirname: true,
__filename: true,
process: true,
Buffer: false
}
};
exports.__esModule = true;
exports["default"] = [
// Client
webpackMerge(clone(exports.commonConfig), exports.clientConfig, { plugins: exports.clientPlugins.concat(exports.commonPlugins) }),
// Server
webpackMerge(clone(exports.commonConfig), exports.serverConfig, { plugins: exports.serverPlugins.concat(exports.commonPlugins) })
];
// Helpers
function includeClientPackages(packages, localModule) {
return function (context, request, cb) {
if (localModule instanceof RegExp && localModule.test(request)) {
return cb();
}
if (packages instanceof RegExp && packages.test(request)) {
return cb();
}
if (Array.isArray(packages) && packages.indexOf(request) !== -1) {
return cb();
}
if (!path.isAbsolute(request) && request.charAt(0) !== ".") {
return cb(null, "commonjs" + request);
}
return cb();
};
}
exports.includeClientPackages = includeClientPackages;
function root(args) {
args = Array.prototype.slice.call(arguments, 0);
return path.join.apply(path, [__dirname].concat(args));
}
exports.root = root;

Your problem occurs because your WebPackDevMiddleware don't find your webpack.config.ts.
Specify the configPath value
              app.UseWebpackDevMiddleware(new WebpackDevMiddlewareOptions                 {                      ConfigFile = "AppConfig/webpack.dev.js",                     HotModuleReplacement = true                 });

Hi, I am having the issue, Please help me. the exception is
Call to Node module failed with error: TypeError: Cannot read property 'publicPath' of undefined
    at C:\Users\nadeeshag.NCS\node_modules\aspnet-webpack\WebpackDevMiddleware.js:99:59
    at Array.forEach (native)
    at Server.<anonymous> (C:\Users\nadeeshag.NCS\node_modules\aspnet-webpack\WebpackDevMiddleware.js:88:32)
    at Server.g (events.js:286:16)
    at emitNone (events.js:86:13)
    at Server.emit (events.js:185:7)
    at emitListeningNT (net.js:1279:10)
    at _combinedTickCallback (internal/process/next_tick.js:71:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

Following is the method
app.UseDeveloperExceptionPage();
                    app.UseWebpackDevMiddleware(new WebpackDevMiddlewareOptions
                    {
                        HotModuleReplacement = true
                    });

Did you specify the webpack.config file path in the WebpackDevMiddlewareOptions ?
You have to specify too the "PublicPath" in your webpack.config,

The same solution is working in another computer, only in one computer its not working.
In case I have attached my webpack.confg.js file as well
var isDevBuild = process.argv.indexOf('--env.prod') < 0;
var path = require('path');
var webpack = require('webpack');
var nodeExternals = require('webpack-node-externals');
var ExtractTextPlugin = require('extract-text-webpack-plugin');
var merge = require('webpack-merge');
var allFilenamesExceptJavaScript = /\.(?!js(\?|$))([^.]+(\?|$))/;
var CopyWebpackPlugin = require('copy-webpack-plugin');
const CheckerPlugin = require('awesome-typescript-loader').CheckerPlugin;
const clientBundleOutputDir = './wwwroot/dist';

// Configuration in common to both client-side and server-side bundles
module.exports = (env) => {
    // Configuration in common to both client-side and server-side bundles
    const isDevBuild = !(env && env.prod);

    // Configuration in common to both client-side and server-side bundles
    return {
        stats: { modules: false },
        context: __dirname,
        entry: {
            'polyfills': './ClientApp/polyfills.browser.ts',
            'main-client': './ClientApp/boot-client.ts'
        },
        resolve: { extensions: ['.js', '.ts'] },
        output: {
            filename: '[name].js',
            sourceMapFilename: '[name].map',
            chunkFilename: '[id].chunk.js',
            publicPath: '/dist/',
            libraryTarget: 'var',
            path: path.join(__dirname, clientBundleOutputDir)
        },
        module: {
            rules: [
                {
                    test: /\.ts$/,
                    include: /ClientApp/,
                    exclude: [/\.(spec|e2e)\.ts$/],
                    use: ['ts-loader?silent=true', 'angular2-template-loader']
                },
                 {
                     test: /\.json$/,
                     use: 'json-loader'
                 },
                { test: /\.html$/, use: ['html-loader?minimize=false'] },
                //{
                //    test: /\.css/, use: ExtractTextPlugin.extract({
                //        fallback: "raw-loader",
                //        use: "css-loader"
                //    })
                //},
                {
                    test: /\.(jpg|jpeg|gif|png)$/,
                    exclude: /node_modules/,
                    use: ['url-loader?limit=25000&name=images/[name].[ext]']
                },
                { test: /\.woff(2)?(\?v=[0-9]\.[0-9]\.[0-9])?$/, use: ['url-loader?limit=10000&mimetype=application/font-woff'] },
                { test: /\.(ttf|eot)(\?v=[0-9]\.[0-9]\.[0-9])?$/, use: ['url-loader?limit=1024&name=fonts/[name].[ext]'] },
                {
                    test: /\.svg(\?v=\d+\.\d+\.\d+)?$/,
                    use: ["url-loader?limit=10000&mimetype=image/svg+xml&name=images/[name].[ext]"]
                },
                 {
                     test: /(\.css|\.scss)$/,
                     use: ExtractTextPlugin.extract({
                         fallback: "raw-loader",
                         use: [
                             "css-loader",
                             "sass-loader"]
                     })
                 }
            ]
        },
        plugins: [
            new CheckerPlugin(),
            new ExtractTextPlugin('styles.css'),
            new CopyWebpackPlugin([
                        // Copy icons
                        {
                            context: 'ClientApp/images',
                            from: '**/*',
                            to: 'images'
                        }
            ],
                    {
                        ignore: [
                            // Doesn't copy any files with a txt extension
                            '*.txt'
                        ],

                        // By default, we only copy modified files during
                        // a watch or webpack-dev-server build. Setting this
                        // to `true` copies all files.
                        copyUnmodified: false
                    }),
            new webpack.DllReferencePlugin({
                context: __dirname,
                manifest: require('./wwwroot/dist/vendor-manifest.json')
            }),
            new webpack.ProvidePlugin({
                Reflect: 'core-js/es7/reflect'
            })
        ].concat(isDevBuild ? [
            // Plugins that apply in development builds only
            new webpack.SourceMapDevToolPlugin({
                module: true,
                filename: '[file].map', // Remove this line if you prefer inline source maps
                columns: false,
                moduleFilenameTemplate: path.relative(clientBundleOutputDir, '[resourcePath]') // Point sourcemap entries to the original file locations on disk
            })
        ] : [
            // Plugins that apply in production builds only
            new webpack.optimize.OccurrenceOrderPlugin(),
            new webpack.optimize.UglifyJsPlugin()
        ])
    }
};

I had the same issue that it was working on one computer and not the other, Steve's reply did the trick for me, i had to move my project from C drive to another drive and it worked.

Actually it did the trick for me too. Thank you @SteveSandersonMS @bilalhassan88


Improve link colors in typeaheads

At present, links in typeaheads (e.g., in a channel description) don't look great when the link is highlighted.

We should try making the links the same color as the text. The link should use currentColor + a half transparent 1px underline, and the whole link element to have opacity if 0.6 opacit.

Please be sure to post screenshots in both light and dark theme in the PR description.

CZO thread

@zulipbot claim

So, basically the link should be just white-colored with 0.6 opacity applied to it ?

@zulipbot claim

@zulipbot claim

Hi @alya, I noticed that @lak3rr may not be active. If that’s the case, I’d love to work on this issue. Please let me know if it’s okay for me to proceed.

Sure, reassigning -- thanks.

Sure, reassigning -- thanks.

I think the issue hasn’t been reassigned yet. Could you please assign it to me when you get a chance?

PR #31543 fixes this issue.
@alya

PR https://github.com/zulip/zulip/pull/31543 fixes this issue.
@alya


Is there a way to ask again for permissions?

Hey there,
I couldn't find it in the readme so I am asking:
Any way I can ask again for the permissions if the user has initally rejected (for example accidentially) or if he has manually disabled them via the iOS Settings Menu?
Thanks

not as far as I know.

@jaschaio if you use something like https://github.com/yonahforst/react-native-permissions you can check if the user had denied the permission and if so use openSettings() to take the user to their permission settings.

sounds like a solution. can I close this?

Haven't come around to try it yet but will report afterwards


the sdk  mget example

There is the example about sdk's mget?

the image is error

There is the example about sdk's mget?

the image is error


Sprint documents

I've added Sprint Backlog 7 and Sprint Retrospective 6.
Please check it again and merge.

Rule No.1: Never lose money.  ” - Rick Osborne
I think that this quote is relevant to this pull request. At least for the documents that you pushed in this PR. Btw the ADD is not relevant in this PR.

I think you used an outdated branch.

Indeed I did, thanks!


An example how to use an image as a 3d viewport

This is an example how to use an image as a 3d viewport. remarq: for the now:

the cube is not rotating (i dont know why yet) it seems like the  is not updating.
applying padding to the  a margin  to the  in the css will cause the cube to drift out of the image.

it is a custumization of the bevy render to texture exemple. with more simplificaiton and a rotationg cube (not rotating yet :) ) inside the viewport.

hi, this is a screenshot of the result:

Wow! Looks nice! Thanks! I'll check it and leave comments today or tomorrow.

Thank you for this awesome project. Take your time

And I didn't met issues with cube: it is rotates and doesn't drift.

The drifting happens when i uncomment the style. I will try it again and make the changes you recomanded as soon as possible (probably in 2 or 3 days)

it works perfectly. thank you
on the other side cargo fmt does not seem to make any change; by the way i'm new to rust and and developping UI apps so hope to learn from you :).

Thank you!


Fix PulseAudio problems with 8 channels devices

This fixes the current problem with 8 channels devices with PulseAudio.
@vnen Try this out, you shouldn't have more init errors with this.

Thanks, it works perfectly!

Cherry picked into 3.0.3


Update embedded svc

This is based on the #82 branch, so until that's merged this is blocked.
I only implemented the Wifi trait on the Wifi struct, but where should I implement the Interface trait. This contains the actual IP info, should I directly implement it into Wifi or should we change places into Network, what should we do with the poll_dhcp function then in Wifi
Closes #83

Thanks for your contribution! I thought about doing this, once things upstream settle a bit but great you took this over.
Regarding their Interface trait - I guess it logically fits Network better than Wifi so implementing it on Network makes sense
I guess we can just keep poll_dhcp in the impl of Wifi or is there something I'm overlooking?

Yeah I thought of dhcp because the Wifi trait in svc doesn't mean it has osi 2 support. That's what the other trait is for. But keeping it where it is is also ok.
Btw forgot to update examples, reminding myself.

@bjoernQ Done.
 That should be fixed in another PR, and maybe add a CI check.

@bjoernQ Done.  That should be fixed in another PR, and maybe add a CI check.

Not unexpected ... but yeah definitely a good thing to do
There is one thing to keep in mind and why I am very cautious when even changing small things: we still see miscompilations for Xtensa which are sometimes triggerd by something like moving a static to a different file .... things got much, much better but still. Just mentioning - not to apologize but to explain

clippy warnings are mostly things like needing to do a let if instead of checking if a result is_ok() or doing casting when it's not needed. There were some errors in unsafe code not being wrapped in an unsafe {} which seem important if we care about rust safety

@bjoernQ I'm getting a broken pipe in Linux when doing cargo espflash flash --monitor --features wifi,esp32c3,embedded-svc --example dhcp and it seems to end up in some kind of boot loop because the JTAG appears and disappears

I also tested this in main branch and it still happens :/, can you see if the same happens to you? I suspect its somewhere in init_heap() or initialize()

I tested this on all targets via USB-to-UART bridge (on the dev-board) and it worked well (besides the coex example which needs to get adapted)
BUT I also tried on the ESP32-C3-DevKit-RUST-1 (which you probably also use) and see the same problem (even more problems since I'm on Windows and have trouble to get it to even flash)
I have no idea what could cause this but at least I'm pretty sure it gets until initialize - it doesn't make sense to me to be honest. I'm also almost sure it worked at some point earlier
@jessebraham do you remember testing it on ESP32-C3-DevKit-RUST-1 earlier?

Seems I found a commit that works for me on the DevKit-RUST-1: 7bd248777dfefc4891a9dc9fc92f4fad0ac26218

Created issue #85 for this
IMHO we could still merge this once the coex example is fixed

The ESP32-C3-DevKit-RUST-1 issue should be fixed with #86 - maybe you can test that on your side

rebased because im using my branch currently lol

@bjoernQ I'm unable to get an IP address from the DHCP now, I also tested in the main branch. I tested with a fortigate router and an iOS hotspot.
Tried using wifi_logs but got an exception while on a wifi scan
INFO - V (0) wifi:
INFO - get_scan_id=0
INFO -

Exception 'Store/AMO access fault' mepc=4202617e, mtval=0
TrapFrame { ra: 42026172, t0: 3c0cd7c0, t1: 400015c0, t2: 3, t3: fff80000, t4: 400000, t5: 3c0cd7c0, t6: 0, a0: 0, a1: 4, a2: 90c, a3: 4, a4: 3c0c18f0, a5: 4200dde2, a6: 3fc98f48, a7: fffffff, s0: 3fc8a950, s1: 0, s2: 8, s3: 8a4, s4: 0, s5: 3fcdf930, s6: 3fce0000, s7: fff00000, s8: 60034000, s9: 60033000, s10: 3fce0000, s11: 0, gp: 0, tp: 0, sp: 3fc8a8d0, pc: 4202617e, mstatus: 1881, mcause: 7, mtval: 0 }
0x4200c5c8
0x4200c5c8 - malloc
    at /home/uri/proyects/esp-wifi/src/wifi/os_adapter.rs:844
0x4200ddf6
0x4200ddf6 - esp_wifi::wifi::os_adapter::wifi_malloc
    at /home/uri/proyects/esp-wifi/src/wifi/os_adapter.rs:1636
0x40040ccc
0x40040ccc - r_lld_ext_adv_dynamic_aux_pti_process
    at ??:??

but main still works? strange - I double checked and it still works for me on your branch (with and without wifi_logs)
from the stack trace it seems like it dies when allocating memory - you can try to increase HEAP_SIZE in lib.rs but it also might be just a red herring - maybe worth to try commenting out the wifi scan and try again with wifi_logs

Yeah code works, but DHCP never ends so I get stuck in there waiting for an IP.
I will try what you just said. Still, do you know why DHCP never gets resolved, or does it work in your side?

It completely works on my side (only tested ESP32-C3 today) - I remember there were some issues with DHCP in the past which should be resolved
There is also the dump_packets feature which should show if DHCP packets (or all packets in general) are coming in / out

So, I have tried many things, for some reason when I have wifi_logs it gets stuck after noticing the auth is not none.
With only dump_packets it starts making broadcasts but it never gets answered, I didnt see anything in the AP's side.
I also tried commenting out the wifi scan but wifi_logs still gets stuck on the same part.
I tried using an esp-wroom-32 and it works, it's beautiful haha. I truly dont know whats up with this.
My current esp32c3 is a Wemos Lolin C3 Mini v1.0.0, dont know if that gives you any info.

So, I have tried many things, for some reason when I have wifi_logs it gets stuck after noticing the auth is not none.
With only dump_packets it starts making broadcasts but it never gets answered, I didnt see anything in the AP's side.
I also tried commenting out the wifi scan but wifi_logs still gets stuck on the same part.
I tried using an esp-wroom-32 and it works, it's beautiful haha. I truly dont know whats up with this.
My current esp32c3 is a Wemos Lolin C3 Mini v1.0.0, dont know if that gives you any info.

as mentioned in #88 we had similar problems before which were related to wrong timestamp calculations which shouldn't be the case now
Important thing to know: which was the last commit which worked for you? No need to git-bisect - just a commit that works would be a good hint

Can we merge this meanwhile?

Can we merge this meanwhile?

Generally yes - but the CoEx example needs to get fixed

oops

I don't want to be annoying but unfortunately the coex example doesn't compile yet
❯ cargo "+nightly" run --example coex --release --target riscv32imc-unknown-none-elf --features "esp32c3,embedded-svc,wifi
,ble"
   Compiling esp32c3-hal v0.3.0
   Compiling esp-wifi v0.1.0 (C:\projects\review\ImUrX\esp-wifi)
error[E0382]: use of moved value: `wifi_interface`
   --> examples\coex.rs:163:32
    |
73  |     let mut wifi_interface = esp_wifi::wifi_interface::Wifi::new(ethernet);
    |         ------------------ move occurs because `wifi_interface` has type `esp_wifi::wifi_interface::Wifi<'_>`, which does not implement the `Copy` trait
...
128 |     let network = Network::new(wifi_interface, current_millis);
    |                                -------------- value moved here
...
163 |     let network = Network::new(wifi_interface, current_millis);
    |                                ^^^^^^^^^^^^^^ value used here after move

For more information about this error, try `rustc --explain E0382`.
error: could not compile `esp-wifi` due to previous error
err process exited unsuccessfully: exit code: 101

Deleting line 163 should fix that


LiveForm shouldn't crash if id attr isn't included

To match the behavior of HTML, id isn't required when using <form phx-submit="save"> ... so <LiveForm phx-submit="save">... should have similar behavior.
We shouldn't be injecting an id either. The client should allow the developer to opt-in with recovery.

I think this can be accomplished by creating a FormModel that's local to the LiveForm element if an ID is not present. If an ID is provided, the form model would be held by the coordinator.

I want to aim for feature parity with HTML. Is there a reason why id would he required for SwiftUI? If not then I'd like to match HTML which works, but is less featureful, without id

No reason why an ID would be necessary. I was just noting one possible implementation.

Gotcha, I think we'll find ourselves with less WTFs later on if we match these primitive behaviors. I cannot highlight any one instance this would happen but its always the ones we don't anticipate


atuin import auto doesn't autodetect bash

Observed
$ echo $SHELL
/bin/bash
$ atuin import auto
        Atuin
======================
          🌍
       🐘🐘🐘🐘
          🐢
======================
Importing history...
cannot import /bin/bash history
$ atuin import bash
        Atuin
======================
          🌍
       🐘🐘🐘🐘
          🐢
======================
Importing history...
Importing history from bash
Import complete!
$

Expected
atuin import auto  should manage to autodetect bash from the SHELL env or similar.

$ atuin import bash did the trick. Thanks @vincentdephily.
But yes, auto isn't working for bash in my system, and the $SHELL is pointing to /bin/bash.

Resolved in https://github.com/ellie/atuin/pull/352


Clone Git repositories recursively

Super simple change -- closes #101, I think.

This looks good to me @christopher-dG. Can you add a CHANGELOG entry as well?


Changed the Sorting Order of the list of mangaToUpdate to based on Smart Update Timer

Closes #394
Currently the Updates happen in Alphabetical order of the titles. I want it to Update in order of their Smart Update Timer, going from the smallest to largest.
This way the series most likely to get an update will be prioritized first and you get more immediate results for those series. This can be especially beneficial for those with a large number of series or slow extensions.
This is my first pull request for Mihon. I would appreciate any feedback.

Being Alphabetical makes it more predictable.


Prolongation matrix on non-conforming meshes with tdof size

Hi,
I am trying to set up the restriction and interpolation operators for a geometric multigrid using AMR.
I can obtain the prolongation matrix after refinement using FiniteElementSpace::GetUpdateOperator but the dimension of the operator is the finite element dofs (VSize). Can I obtain this operator with the dimension of the tdofs (TrueVSize)?. Is it possible to modify this operator using FiniteElementSpace::GetProlongationMatrix to obtain the prolongation matrix with tdof dimension? I would appreciate it if you could indicate to me some similar operations in the code.
Thanks in advance.

Hi @davidherreroperez,
Yes, you can use the TrueTransferOperator. You can also take a look in ex26.cpp/ex26p.cpp for an example of geometric multrigrid.
Best,
Socratis


[FLINK-20153] Add documentation for BATCH execution mode

This adds documentation for the new BATCH execution mode. We also explain STREAMING execution mode because there is no central page that explains the basic behavior, so far.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation
Documentation only.

Thanks for the speedy review! And I really appreciate the suggestions that I can just apply right here in Github.
I pushed a commit that should address most comments.

I addressed more comments and also added the important considerations section by Dawid. Could you please take another look?

I now also added sections by Klou and a section about state backends. Now all the content is theoretically in.

I believe I addressed all comments. Please take another look. If there's no objection I would merge this by tomorrow because this PR/discussion is growing a bit unwieldy. Anything else we want to add we can still add later.

Thanks for the reviews! I merged this now.


Don't materialize stream

Undo https://github.com/duckdb/duckdb-wasm/commit/35739b58347eafa95e0c429fda1396baafa8eb95 when https://issues.apache.org/jira/browse/ARROW-14780 is done and released.

I think we can close this until DuckDB-Wasm gets async I/O. The overhead of this copy will rarely hurt if we cannot materialize directly into the wasm heap.


Integration with Microsoft Teams

An integration with Microsoft Teams to set the status just like in the Slack integration would be great.

As with others enhancements, feel free to implement a contribute PR.


[junit4] deprecate the superclass and implement with a rule

One-line summary
Matches JUnit 5 approach to minimize effort to update existing projects
Description

Deprecates the old way that didn't actually work properly
Implements everything as a Rule which is very straightforward

Types of Changes

New feature (non-breaking change which adds functionality)

Considerations

@nadvolod do we need to update documentation for this?

Good news! This implementation is Thread safe!
I've updated it with the newly merged features in JUnit 5


Fix trailingFunctionCommas bugs

Fixes #192 (infinite loop on commented multiline calls without trailing comma).
Fixes #175 (revoming a comma outside the scope of a function call).

cc @adrianheine

Both bugs happened because */ is two characters while \n is one character, so getting it's index + 1 and then incrementing the index again made us skip the closing parens of a call if there was no white space before it, essentially making the code look for a "trailing commas" way past the actual call, either freezing or finding a comma from a different context.

Thanks!


Some pandoc options not working with extra_args

E.g. --template template.latex and --variable urlcolor=cyan
mwe
import pypandoc

output = pypandoc.convert_file(
        'test.md',
        to = 'pdf',
        outputfile = 'test.pdf',
        extra_args = ['--template template.latex']
        )

returns
Traceback (most recent call last):
  File "mwe.py", line 3, in <module>
    output = pypandoc.convert_file(
  File "C:\Python38\lib\site-packages\pypandoc\__init__.py", line 137, in convert_file
    return _convert_input(source_file, format, 'path', to, extra_args=extra_args,
  File "C:\Python38\lib\site-packages\pypandoc\__init__.py", line 320, in _convert_input
    raise RuntimeError(
RuntimeError: Pandoc died with exitcode "6" during conversion: b'Unknown option --template template.latex.\r\nTry pandoc --help for more information.\r\n'
shell returned 1

I believe you need to split the extra arguments into a list of strings, i.e. ['--template', 'template.latex'].
As the readme notes (in a different context, but it also applies for your use case):

This gotcha has to do with the way subprocess.Popen works.

As the original author hasn't responded, I see this issue as resolved.
If not, feel free to open a new issue!


Implement Calibrate command

This command will be tricky to implement, because each sensor has different arguments for its version of this command.
For example, the DO sensor uses these args:

Cal
Cal,0
Cal,clear
Cal,?

The pH sensor uses these args:

Cal,mid,n
Cal,low,n
Cal,high,n
Cal,clear
Cal,?

The RTD (temperature) sensor uses these args:

Cal,t
Cal,clear
Cal,?

For now, I've implemented separate calibration commands: CalibratePh and CalibrateDo. I'm thinking after implementing a couple of these that a pattern(s) may emerge, at which point refactoring into a more generic command makes sense.


Is there any documentation

I have downloaded the project and copied to my server folder. The odontogram loads ok, but I would like to know how to load and save patients data.
Also I have seen in the readme file some images with blue and red colors and I don't know how does it work because I cant see them in the downloaded project.

regards, i would like to know about  the way of create the different images of data (fill with tools), how change the tools, how assign the tools, i would like contribute this project

regards,
good project
is there any documentation?

-----ESPAÑOL
si es complicado usar el proyecto con la poca documentacion  pero logre leyendo el codigo implementar una forma para modificar el odontograma.
agrego
//TECLADO
Flecha -> odontograma de niño
Flecha <- odontograma de adulto
//CODIGO
//  var as="45,25,0,,47,25,0,"; //    engine.setDataSource(as);//CARGAR DATA CON CAMBIOS //   engine.createHeader();// Mostrar encabezado de la funcion engine.loadPatientData();
----INGLES
If it is difficult to use the project with little documentation but I managed to read the code and implement a way to modify the odontogram.
I add
//KEYBOARD
Arrow -> child odontogram
Arrow <- adult odontogram
//CODIGO
`
//  var as="45,25,0,,47,25,0,";
//    engine.setDataSource(as);//LOAD DATA WITH CHANGES
//   engine.createHeader();// Show function header engine.loadPatientData();
`

paint  CARIES center 18_0
engine.load(18,1,'0','');  not working
what is the correct method?

//caries
// var as="18,1,L,'HI3'";
// engine.setDataSource(as);

Does anyone know how to save the odontogram created in a table and then how to load it again?

save in json in one field the table

Hello guys! Sorry, I have not been very active on this profile. This was just a quick project that a put together for a demo. I will try to refresh my knowledge about it and get it up to date.

@bardurt We would like to customise this for our specification, would you be interested in taking this as paid professional service, contact me at<EMAIL_ADDRESS>


Hanamuke no Tori Camera and Facials

I can export the camera with an old version of mltdtools but some of the angles are incorrect, and in the newest version, the camera is just static and the facials for the lips look as if they merged both character's lip animation; motion 1 keeps singing after its supposed to stop as well as motion 2, and im even making sure that "Always Singing" is unchecked.

look forward to hearing back!


Add withdraw coins from chaiinsfr wallet instruction to faq

steps to transfer coins from chainsfr wallet to other wallets

Done and publish


Add experimental plugin support

Experimental Plugin Support

Set $HOME_MANAGER_PLUGINS to the absolute path of a Nix expression.
Home Manager merges plugins into pkgs
Home Manager also loads plugin option declaration modules

Example plugins.nix
The following shows what the plugin expression ought to look like. Just an attrset with each downloaded plugin. In addition to fetchFromGitHub any other fetching mechanism also works.
with import <nixpkgs> {};

{
  org-build = import (fetchFromGitHub {
    owner = "dustinlacewell";
    repo = "nix-hm-org-build";
    rev = "d552b462b25d680981dc5a0d6cdc27a364cce8fd";
    sha256 = "16qs3dnpyx4z90m15g9kk30irxykv2c7i1nxi4a9ssc3w4i9y70d";
  });

  org-export = import (fetchFromGitHub {
    owner = "dustinlacewell";
    repo = "nix-hm-org-export";
    rev = "cbeb9b86e843cf400c95bcbe7a062fcfc63cec73";
    sha256 = "06bsmw95d3fqqqwbgvmpkvd94hmjhzv27bzmjc0nyfv4xdxcg53a";
  });
}

Example plugin source
A plugin is a function that takes { pkgs, lib } and returns an attrset. The attrset is made available in your own modules as pkgs.pluginName.
One attribute, module is special and defines the plugin module. The module attribute should be assigned a module function, module attrset or empty attrset.
This example plugin provides a library function pkgs.org-build.build which compiles an Orgmode file to Elisp. It also declares an Option plugins.org-build. The plugin utilizes its own build function to handle the Option's behavior. The full plugin can be found here: https://github.com/dustinlacewell/nix-hm-org-build/
{ pkgs, lib }:

with lib;
with builtins;

rec {

  # export a library function
  build = { source }: let
    env = { buildInputs = [ pkgs.emacs ]; };
    script = ''
      ln -s "${source}" ./init.org;
      emacs -Q --script "${./org-build.el}" -f make-init-el;
      cp ./init.el $out;
    '';
  in pkgs.runCommand "org-build" env script;

  # export a module to declare options
  module = {config, pkgs, lib, ...}:
  let
    cfg = config.plugins.org-build;
  in {
    options.plugins.org-build = {
      enable = mkEnableOption "Build init.el from Orgmode file";
      source = mkOption {
        type = types.path;
        description = ''
          The source orgfile to build as init.el
        '';
      };
    };

    config = mkIf cfg.enable {
      home.file.".emacs.d/init.el".source = build { source=cfg.source; };
    };
  };
}

Example use
Here is my actual personal expression for installing emacs and rendering init.org -> init.el which uses the org-build plugin.
{ pkgs, ... }:

let
  # call a plugin library function
  result = pkgs.org-export.export {
    source = ./init.org;
    user = "dustinlacewell";
    repo = "emacs.d";
    token = builtins.getEnv "EMACS_D_GITHUB_TOKEN";
  };

in {
  programs.emacs = { enable = true; };
  # utilize a plugin declared option
  plugins.org-build = { enable = true; source = ./init.org; };
}

Thanks for the contribution! I like the idea of plugins and similar methods of making the modules extensible.
Right now I'm suspecting that everything that this form of plugins, at least in its current form, can do also could be accomplished using imports. I'll have to ponder for a while to see whether my suspicion actually is true. If imports is sufficiently powerful then my inclination would be not to merge this and instead suggest to use plain modules and instead do something like
{
  import = [
    (fetchFromGitHub {
      owner = "dustinlacewell";
      repo = "nix-hm-org-build";
      rev = "d552b462b25d680981dc5a0d6cdc27a364cce8fd";
      sha256 = "16qs3dnpyx4z90m15g9kk30irxykv2c7i1nxi4a9ssc3w4i9y70d";
    })
  ];

  org-build =  { enable = true; source = ./init.org; };
}

I don't think so. Module imports can only declare and define new options. Overlays can only make new pkgs available. Plugins are able to make new pkgs library code available in addition to declaring and defining options.

I don't think so. Module imports can only declare and define new options. Overlays can only make new pkgs available. Plugins are able to make new pkgs library code available in addition to declaring and defining options.

I think it would be better to add a nixpkgs.overlays option (like in the nixos module), which can then provide additional attributes to pkgs (including adding functions to lib). Then all of this would be possible through importing modules (which can then again set the nixpkgs.overlays option to provide more packages). This will then be consistent nixos modules.

@dustinlacewell The nixpkgs module is in master now. If it suffices for your purposes then I suggest to close this PR. If not then please let me know which functionality is missing.

I believe all aspects of plugins are now supported so I'll close this. Many thanks for highlighting this missing part of HM!


Undefined symbols for architecture x86_64

I'm using 1PasswordExtension via CocoaPods. Version 1.1 works fine, but when I upgrade to 1.1.2 and try to compile my app, I get these errors:
Undefined symbols for architecture x86_64:
  "_AppExtensionErrorCodeCancelledByUser", referenced from:
      ___45-[RootViewController findLoginFrom1Password:]_block_invoke in RootViewController.o
  "_AppExtensionPasswordKey", referenced from:
      ___45-[RootViewController findLoginFrom1Password:]_block_invoke in RootViewController.o
  "_AppExtensionUsernameKey", referenced from:
      ___45-[RootViewController findLoginFrom1Password:]_block_invoke in RootViewController.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Absolutely nothing else changed in my code.

Hi @kevinrenskers,
Thanks for taking the time to write to us :+1:
Lately we've been getting a quite a few CocoaPods-related issues ( see #180 ). This leads me to believe that there might be a bug on their end.
By the looks of it, it seems that CocoaPods didn't pull version 1.1.2 properly. Did you try to clear Xcode's derived data and restart it?
Can you please force to update to version 1.1.2 in your Podfile the someway that I did in this sample project?
It would be great if you could replicate this issue in the sample project that I've sent you and send it back to me. This we we can determine what causes the issue.
Please let me know how this goes.
If you are using CocoaPods 0.36.0.rc.1 please make sure that you check the interesting discussion in issue #180
Cheers!

Hm weird, it works fine on another computer, so it probably can be solved by clearing derived data or something like that on the original computer. Will let you know.

Same issue. Not using CocoaPods. Clearing derived data resolved issue.

Yea solved it on my other computer as well. Closing this.

Hi guys,
Thanks for letting us know that you've got it all sorted out :smile:
Cheers!


Upgrde SonarQube to 7.8 and sonar-scala to 7.6.

I also changed the following:

removed SonarScala from the full image as it cannot co-exist with sonar-scala
disabled SonarQube telemetry, which is enabled by default 👀
formatted the readme files with prettier

Btw, how about updating to 7.9 LTS, since it's already out there?
https://www.sonarqube.org/whats-new/
They claim that they added Scala support in this release. Can we use it instead of scapegoat, scoverage and scalastyle?


Add DeltaDash to the list of projects using the framework

I'm not quite sure whether open-source is a requirement for being added to this list, there are plans on open-sourcing sometime in the future but for the early state it was deemed closed-source is better, although certain components like parsers and algorithms for the game will be provided as NuGet packages.

Doesn't need to be open source, all good 👍 .


UI: Make backup volume page to be two levels

It's inconvenient for the user to search for the volume only from the volume name dropdown.
We should provide a two-level page in the Backup page.
The first level is a list of all the BackupVolumes, with filters for name etc .
The second level is the same as the current backup page, which is a list of backups for a specified volume. And the user should be able to navigate back to the first level easily.

Done.


Replace string refs in favor of callback refs

For pre-v1 release
React is deprecating this feature in favor of callback refs.
Here is a handy guide to get this issue fixed up. 🌞
Areas of concern:

[x] AutoComplete
[x] CircularProgress
[x] DatePicker
[x] DatePickerDialog
[x] Dialog
[x] FloatingActionButton
[x] IconMenu
[x] EnhancedSwitch
[x] ExpandTransitionChild
[x] FocusRipple
[x] Overlay
[x] Tooltip
[x] LinearProgress
[x] Menu
[x] RadioButton
[x] RaisedButton
[x] RefreshIndicator
[x] Table
[x] EnhancedTextArea
[x] TimePicker

The example below is AutoComplete which is currently using string refs.

I am working on a PR that will address all of these changes together.

Hi,
Don't forget to change the prop name inputRef to ref for the TouchRipple compoennt. You will find it in the ButtonBase components function renderRipple.
The TransitionGroup component that will receive this prop will complain about the name. It will be passed to TransitionGroup as ...other.
I was using React 16 and react-transition-group 2.2.1

@HenrikGr Maybe that explains why I have two unit tests giving me problems. 😆  Thanks for the tip!