Added sql db op list/cancel

This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

Command Guidelines

[x] Each command and parameter has a meaningful description.
[x] Each new command has a test.

(see Authoring Command Modules)
(env) C:\git\azure-cli [cancelop ≡]> az sql db op -h

Group
    az sql db op: Manage operations on a database.

Commands:
    cancel: Cancels the asynchronous operation on the database.
    list  : Gets a list of operations performed on the database.

(env) C:\git\azure-cli [cancelop ≡]> az sql db op cancel -h

Command
    az sql db op cancel: Cancels the asynchronous operation on the database.

Arguments
    --database -d       [Required]: Name of the database.
    --name -n           [Required]: The operation id.
    --resource-group -g [Required]: Name of resource group. You can configure the default group
                                    using `az configure --defaults group=<name>`.
    --server -s         [Required]: Name of the Azure SQL server.

Global Arguments
    --debug                       : Increase logging verbosity to show all debug logs.
    --help -h                     : Show this help message and exit.
    --output -o                   : Output format.  Allowed values: json, jsonc, table, tsv.
                                    Default: json.
    --query                       : JMESPath query string. See http://jmespath.org/ for more
                                    information and examples.
    --verbose                     : Increase logging verbosity. Use --debug for full debug logs.
(env) C:\git\azure-cli [cancelop ≡]> az sql db op list -h

Command
    az sql db op list: Gets a list of operations performed on the database.

Arguments
    --database -d       [Required]: Name of the database.
    --resource-group -g [Required]: Name of resource group. You can configure the default group
                                    using `az configure --defaults group=<name>`.
    --server -s         [Required]: Name of the Azure SQL server.

Global Arguments
    --debug                       : Increase logging verbosity to show all debug logs.
    --help -h                     : Show this help message and exit.
    --output -o                   : Output format.  Allowed values: json, jsonc, table, tsv.
                                    Default: json.
    --query                       : JMESPath query string. See http://jmespath.org/ for more
                                    information and examples.
    --verbose                     : Increase logging verbosity. Use --debug for full debug logs.

The checkin will fail for the moment because the updated python sdk is not yet published - that will be done in the next day or two. Sending now for initial feedback.

Using published SDK, and this is my team's feature so no other SQL signoff required - good to merge from SQL team's point of view.

Can an operation ID be referenced via an ARM resource ID?  If so it seems that the cancel operation should support --ids.

@jaredmoo can you address @tjprescott 's concern? Other then that the code change looks good.

Here's an example operation resource that we can refer to:
{
   "properties":{
      "databaseName":"cliautomationdb01",
      "operation":"UpdateLogicalDatabase",
      "operationFriendlyName":"ALTER DATABASE",
      "percentComplete":0,
      "serverName":"clitestserver000002",
      "startTime":"2017-10-03T23:25:09.073Z",
      "state":"InProgress"
   },
   "id":"/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/clitest.rg000001/providers/Microsoft.Sql/servers/clitestserver000002/databases/cliautomationdb01/operations/d2896db1-2ba8-4c84-bac1-387c430cce40",
   "name":"d2896db1-2ba8-4c84-bac1-387c430cce40",
   "type":"Microsoft.Sql/servers/databases/operations"
}

As per standard, the -n param is the resource's name, which in this case is d2896db1-2ba8-4c84-bac1-387c430cce40. For the help text I wrote operation ID in order to try to disambiguate between name, operationName, and operationFriendlyName since name is the only one of those which is a GUID. It is not the full ARM ID. Do you have any suggestions on how to make this help text clearer?


Trim agent binary by 14mb by conditionally compiled XDS filters

Part of https://github.com/istio/istio/issues/26232
75mb -> 64mb
We could have also done massive refactoring to avoid using build tags,
but I think in the near future we will need build tags for dropping k8s
import, so it seems useful to implement this at least for the short
term.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
4105b2c8236c743065e00d3aa50c45187c8ea48e
link
/test integ-multicluster-k8s-tests_istio

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

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
4105b2c8236c743065e00d3aa50c45187c8ea48e
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
4105b2c8236c743065e00d3aa50c45187c8ea48e
link
/test integ-pilot-k8s-tests_istio

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

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
4105b2c8236c743065e00d3aa50c45187c8ea48e
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
4105b2c8236c743065e00d3aa50c45187c8ea48e
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
81fe642c0d3238c9fc6f88b7a5bdb9d6cfb2cf89
link
/test integ-security-k8s-tests_istio

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

/retest

Looks good, I am verifying.

btw, forgot to mention, the reason we need the imports for pilot but not agent is pilot will marshal/unmarshal arbitrary Any messages for envoyfilter. Agent only unmarshals the top level DiscoveryReq/Resp

We should probably make sure unit tests for agent also have the build flag.

In response to a cherrypick label: #28670 failed to apply on top of branch "release-1.7":
Applying: Trim agent binary by 11mb by conditionally compiled XDS filters
Using index info to reconstruct a base tree...
M	Makefile.core.mk
M	pkg/config/xds/filter_types.gen.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/config/xds/filter_types.gen.go
Auto-merging Makefile.core.mk
CONFLICT (content): Merge conflict in Makefile.core.mk
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Trim agent binary by 11mb by conditionally compiled XDS filters
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to a cherrypick label: new issue created for failed cherrypick: #28705

In response to a cherrypick label: #28670 failed to apply on top of branch "release-1.8":
Applying: Trim agent binary by 11mb by conditionally compiled XDS filters
Using index info to reconstruct a base tree...
M	Makefile.core.mk
Falling back to patching base and 3-way merge...
Auto-merging Makefile.core.mk
CONFLICT (content): Merge conflict in Makefile.core.mk
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Trim agent binary by 11mb by conditionally compiled XDS filters
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to a cherrypick label: new issue created for failed cherrypick: #28706


Using a few OSSF scorecard checks to show more information to Actions consumers

We at GitHub Actions are thinking of surfacing the security posture of a Repo that hosts Actions code on the Actions listing pages.
While there is information we can get by making API calls(E.g: Branch protection enabled or not), for the others (E.g:Binary artifacts, dangerous workflows )we are looking at using the OSSF checks (use the CLI in a workflow and get the score) and start to display that information on the Actions listing page. Since this is a new change, there will be enough time for the Action creators to fix before the information is shown on the listing page.
We looked at all the OSSF checks and using the following checks in the critical, high and medium categories as something that we need to check for and surface to the consumer of the Action.
Dangerous-Workflow
Binary-Artifacts
Branch-Protection
Code-Review
Dependency-Update-Tool
Vulnerabilities
Pinned-Dependencies
SAST
We will use the same scoring process for each of the checks and display the results
CC: @azeemshaikh38 , @laurentsimon

Since the discussion is about the scorecard-action, I have transferred the issue to the Action repo https://github.com/ossf/scorecard-action/issues/1107

I send https://github.com/ossf/scorecard/pull/2773. I think it's actually simpler to make changes only to the Scorecard code.

We at GitHub Actions are thinking of surfacing the security posture of a Repo that hosts Actions code on the Actions listing pages. While there is information we can get by making API calls(E.g: Branch protection enabled or not), for the others (E.g:Binary artifacts, dangerous workflows )we are looking at using the OSSF checks (use the CLI in a workflow and get the score) and start to display that information on the Actions listing page. Since this is a new change, there will be enough time for the Action creators to fix before the information is shown on the listing page.
We looked at all the OSSF checks and using the following checks in the critical, high and medium categories as something that we need to check for and surface to the consumer of the Action.
Dangerous-Workflow Binary-Artifacts Branch-Protection Code-Review Dependency-Update-Tool Vulnerabilities Pinned-Dependencies SAST
We will use the same scoring process for each of the checks and display the results
CC: @azeemshaikh38 , @laurentsimon

I like this idea as it will improve the security posture of the GitHub Actions ecosystem.
Please consider adding Token Permission and Security Policy checks to the list. Token Permission is a high-risk issue as per Scorecard and also recommended by the GitHub Actions security guide - make sure that the GITHUB_TOKEN is granted the minimum required permissions, and Security Policy makes it easier to report vulnerabilities.

I would be very cautious about indiscriminately showing metrics from the scorecard.  “Pinned dependencies” would be actively harmful if it applies to npm packages, and it’s not actually a good idea to apply to actions in every case, since you’d be depriving yourself of automatic bug and security fixes.

@ljharb GitHub Actions are applications so it should avoid the problem.
@anuraag016 I've made a test branch for you to try:
- uses: ossf/scorecard-action@9ea03ba18bab6e2ea29983f3b0fabdb8fd20ecbc # gh-integration
        env:
          SCORECARD_INTERNAL_GITHUB_INTEGRATION: 1
          SCORECARD_INTERNAL_GITHUB_SARIF_TOOL_NAME: tool-name
          SCORECARD_INTERNAL_GITHUB_CHECKS: Binary-Artifacts, Security-Policy

Please tell me if it works.
Note: the tool name will have its first letter capitalized automatically https://github.com/ossf/scorecard/blob/main/pkg/sarif.go#L421

I meant that GitHub Action are not a "libraries".  The GitHub tutorials ask users to use this template https://github.com/actions/javascript-action which uses a lock file.

ahhh ok, so you're talking about providing scores for actions not for the projects that consume those actions. That makes sense, thanks for clarifying!


Import and attribution of external software

For the JOSS review, in general it would be best to import routines from other packages that SIMIO includes in its current codebase, including RADMC3D, galario, and (I think) frank.
For example this function from galario - galario could be made a dependency of SIMIO, and the routine py_sampleImage could be imported rather than copy/pasted. Alternatively, though less preferably, the routine could be kept in SIMIO, but to adhere to the galario LICENSE, this would require (see the 'Conditions' at the top-right of that page) changing the SIMIO license to the same as galario (GNU Lesser General Public License v3.0), documenting the source of the code (as you do) and stating explicitly any changes made to the version in SIMIO relative to that in galario.
Similarly, this function appears to me to be copy/pasted from a function in frank, with slight modification (but I don't see any attribution to frank). Again to keep this in the SIMIO code base would require changing the SIMIO license, documenting the source of the code, and explicitly noting the changes made. Altenatively you couldmake frank a dependency, import the routine from it, and modify the output as needed.
https://github.com/openjournals/joss-reviews/issues/4942

That's ok and no worries, it's just good to always mention where something came from.
I see the current changes and it all looks good.


Show the actual command instead of the origional one

What
Show the actual commands instead of the original one.
Why?
This way it is easier to see what actually gets executed, plus you will be alarmed when you are accidentally running a wrong target. It makes it more explicit what's actually happening.

Thanks for the contribution @RickvdStaaij! I think it's helpful to have the executed commands instead of the parameter ones.


Feature request: Support for animated emoji

Coming from Skype I'd love to see the ability to use GIFs as custom emoji.

@vulkman you can, you just need to do the resizing in a third-party program to 64x64 pixels (or some smaller square size); the libraries we use for turning uploaded images into appropriately small image files for emoji don't support resizing animated emoji yet.  Let me know if you're not able to get that working.
(Regardless, it'd be nice to not have this manual requirement; and based on your report, I suspect whether something is broken in the error handling plumbing for uploading invalid emoji, because you should have gotten a nice error message explaining the problem)

(On the technical side, it's possible that if we track down the gifmaker script mentioned in https://stackoverflow.com/a/30339387 (which seems to have moved in recent versions of Pillow), we could do this with Pillow; )

@timabbott I tried a resized version of the party_parrot emoji. It doesn't seem to continuously play or work in reactions as an animated emoji.

What tool did you use for resizing?  Some tools for resizing gif files will just save the first frame of an animated gif; you need a tool for resizing animated gifs.

It works fine, resized mine with ezgif.com, works like a charm, thank you :)

I tried another converter before this and it only looped once. After trying ezgif.com, it works perfectly. Thanks @vulkman @timabbott

@HarshitOnGitHub maybe step 1 of working on this is that we should provide a better error message that suggests trying something like ezgif.com.


Secrets Exposed

Hey Dakin!
Glad to see you kept hacking on this.
https://github.com/dakinwerneburg/gradify/blob/dbed289538e0712e7962741c146c3cf9b4ad5421/gradify/settings/default.py#L22-L23
The secrets should be set via environment variables and retrieved via os.environ.get('SECRET_KEY').
For development just add a .env.dev file that contains things like this that should be unique to deployment and source it before running ./manage.py
.env.dev
DEBUG=1
SECRET_KEY=324234sdfdsferewr32542ewdsfdsf
DJANGO_ALLOWED_HOSTS=localhost <IP_ADDRESS> [::1]

Hi Ryan,Hope all is well with you.  Thanks for the tip.  I am actually started the Microsoft Software Systems Academy that works with veterans get a job as Cloud Application Developer with Microsoft.  Well one thing they wanted me to do was get an GitHub account because Microsoft owns it, so I just merged my GitLab project with GitHub but looks like some of you have worked on it, so had to do resolve some merge conflicts.    Respectfully Submitted Dakin T. Werneburg Sent from Mail for Windows 10 From: Ryan BradySent: Friday, January 15, 2021 3:59 PMTo: dakinwerneburg/gradifyCc: SubscribedSubject: [dakinwerneburg/gradify] Secrets Exposed (#11) Hey Dakin!Glad to see you kept hacking on this.https://github.com/dakinwerneburg/gradify/blob/dbed289538e0712e7962741c146c3cf9b4ad5421/gradify/settings/default.py#L22-L23The secrets should be set via environment variables and retrieved via os.environ.get('SECRET_KEY').For development just add a .env.dev file that contains things like this that should be unique to deployment and source it before running ./manage.py.env.devDEBUG=1SECRET_KEY=324234sdfdsferewr32542ewdsfdsfDJANGO_ALLOWED_HOSTS=localhost <IP_ADDRESS> [::1]—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.

Hi Ryan,Hope all is well with you.  Thanks for the tip.  I am actually started the Microsoft Software Systems Academy that works with veterans get a job as Cloud Application Developer with Microsoft.  Well one thing they wanted me to do was get an GitHub account because Microsoft owns it, so I just merged my GitLab project with GitHub but looks like some of you have worked on it, so had to do resolve some merge conflicts.    Respectfully Submitted Dakin T. Werneburg Sent from Mail for Windows 10 From: Ryan BradySent: Friday, January 15, 2021 3:59 PMTo: dakinwerneburg/gradifyCc: SubscribedSubject: [dakinwerneburg/gradify] Secrets Exposed (#11) Hey Dakin!Glad to see you kept hacking on this.https://github.com/dakinwerneburg/gradify/blob/dbed289538e0712e7962741c146c3cf9b4ad5421/gradify/settings/default.py#L22-L23The secrets should be set via environment variables and retrieved via os.environ.get('SECRET_KEY').For development just add a .env.dev file that contains things like this that should be unique to deployment and source it before running ./manage.py.env.devDEBUG=1SECRET_KEY=324234sdfdsferewr32542ewdsfdsfDJANGO_ALLOWED_HOSTS=localhost <IP_ADDRESS> [::1]—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.

Dakin,
It looks like we worked on it because we did.  :)  Git keeps the history of commits.  When you merged the gitlab project into the GitHub project, it brought the history with it.    You could have copied the files without the .git directory into a new Git repository and it would have avoided the merge issues, but it’s probably better you didn’t remove the attribution to your fellow authors on the project.
Good luck with the Microsoft program!
S/F,
Ryan

Dakin,
It looks like we worked on it because we did.  :)  Git keeps the history of commits.  When you merged the gitlab project into the GitHub project, it brought the history with it.    You could have copied the files without the .git directory into a new Git repository and it would have avoided the merge issues, but it’s probably better you didn’t remove the attribution to your fellow authors on the project.
Good luck with the Microsoft program!
S/F,
Ryan


imageButton DSL compatibility broken

I recently switched my project to Anko 0.9 and noticed that the imageButton was created but without any image. It came out that while the call imageButton(R.drawable.ic_camera_alt_24dp) worked fine in 0.8.3 and also created button without any complains, but in 0.9 the image was not rendering as the argument was treated as theme; see Views.kt imageButton functions. To fix that we need to either specify resource as e.g. imageButton(imageResource = R.drawable.ic_camera_alt_24dp) or pass the second theme argument e. g. imageButton(R.drawable.ic_camera_alt_24dp, 0).
The main issue is that I had no indication of this change and the code was compiling fine, so it took me a bit to notice the invalid call with resource Id as theme.
Cheers,
Jakub

The bug is fixed in 0.10: all block functions that accept a theme parameter are now renamed to "themed…()" (e.g. themedImageButton()).


Fix rbac includes

Description

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit 67ab6bbc70aa5910ede77d081288ea4397badcff
https://deploy-preview-2602--calico.netlify.com


Expect test success on conduit-parse, dublincore-xml-conduit, opml-conduit, xml-conduit-parse

Follow-up of 56322d1
New versions of these packages have been released to disable hlint tests by default.

Thanks!


SEGSAdmin config and logging functionality

Adds ability to edit and save server and logging settings
Adds more existing settings.cfg and databases checks
Initial/prototype user friendly 'server setup' functionality
User can provide an IP and a default config file is created

Adds to #285  .

@nemerle @ldilley thanks for this, these changes should have been pushed up now.
Bit confused on the layoutWidget review, have dropped you a message in discord

Post fixes and pending build, this looks good. Great job and excellent persistence, @miles200!


SW-2043 Log request and response payloads

To make it easier to troubleshoot problems we discover during QA testing, add the
ability to log request and response bodies for a subset of users.

Current dependencies on/for this PR:

main

PR #853   👈

This comment was auto-generated by Graphite.

Once this lands, I'll update the staging configuration to set this new option to<EMAIL_ADDRESS>so we log everything during internal testing.


Mermaid Diagram Renders as Raster Image Instead of Expected SVG in PDF Output

I have encountered an issue where the Mermaid diagram is rendered as a raster image instead of the expected SVG format in the PDF output. This is inconsistent with the documentation in the README, which states that the diagram should be in SVG format.
Steps to Reproduce:

Clone the repository from https://github.com/TokenScript/documents/
Checkout commit 42ed9788826c38f38ff83af486fbff9b39b059f8
Navigate to the src directory
Generate a PDF using the following command:

dita -i smartlayer-overview.ditamap -f pdf -o output

Expected Result:
The generated PDF (output/smartlayer-overview.pdf) should contain the Mermaid diagram in SVG format.
Actual Result:
The generated PDF contains the Mermaid diagram in raster image format.

It's worth noting that this issue is less severe than issue #10, as a diagram is produced in this case, albeit in an incorrect format. Any assistance in resolving this discrepancy would be greatly appreciated.

@weiwu-zhang at some point I took the decision to embed the diagram as a binary image for the PDF output: https://github.com/oxygenxml/dita-ot-diagrams-plugin/commit/355f3b9a49bd6aa29fe433521e0d5da9138c8053
I'm afraid I forgot the reason for this change I made, I think it was because the generated SVG file in certain cases was not supported by the PDF engine so I decided to produce a binary image instead.
If you want you can try to revert the changes in the "pdfSVG.xsl" and generate it again as an SVG.
I just updated the readme to state that for mermaid images, the binary image is stored inside the PDF instead of the SVG.


ReferenceError: self is not defined

Expected behavior
Our Webpack Server should start normally
Observed behavior
When running out dev server we get the following error:
webpack-internal:///../../node_modules/bugsnag-js/dist/bugsnag.js:855
var env = typeof window === 'object' ? window : self;
                                                ^

ReferenceError: self is not defined

Version
bugsnag-js: 4.7.3
bugsnag: 2.4.3
bugsnag-react: 1.1.1

Hi @dutzi, I just put together a very basic project with bugsnag-js and webpack-dev-server and couldn't reproduce this issue. Could you provide more detail please? If possible, a reduced standalone example that I can clone and reproduce would be great. Thanks!

Closing due to inactivity.

I'm running into the same issue . I was using busnag/js package

Hello @sayo96 , I hope you are doing well.
Do you remember how to fix that problem?


Fix(compiler-base): fix doc string mistakes.

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

issue #115
2. What is the scope of this PR (e.g. component or file name):
compiler_base/error
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[x] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other

fix some import mistake and remove useless part in diagnostic_builder.rs.
4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[x] Other

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.008%) to 60.42%

Files with Coverage Reduction
New Missed Lines
%

kclvm/compiler/src/codegen/llvm/context.rs
3
74.15%

Totals

Change from base Build<PHONE_NUMBER>:
-0.008%

Covered Lines:
23789

Relevant Lines:
39373

💛  - Coveralls


Not possible to modify date of a timesheet entry

Although one can modify a timesheet entry, this extends only to its duration.  It needs to be possible to change the following additional properties of the entry as well:

Date;
Start time;and
Description.

You should be able to edit the start time with the modify ".." --start <time>. Not working?
That also modifies the start date e.g. modify ".." --start yesterday 10am.
Description – yep, not available. Also missing is removing an entry! – if that were available you could just delete and re-create.

Confirmed that it's possible to modify ".." --start <time>.  The confusion arose because duration is a positional argument, whereas start and end are options.  The latter two aren't shown in response to entering help when in a timesheet session, but only at the next level down of modify --help.


Improve number handling in NamedEntitles

plus add my e-mail address to the contributors file

Coverage remained the same at 78.261% when pulling c0171c8e9e2eedcd90907304311211689bdf1d5d on elliott5:chunk into 6caaa3b62663105e71367bed3aad3cd0753eeafd on jdkato:master.

Thanks!


fix(stepdefinitionpath): do not rely on cypress configuration for det…

…ermining the stepDefinitionPath
Relying on any parts of the cypress configuration has been problematic since the beginning, it was
time to use only the configuration that we own. This is a breaking change but it should be
relatively easy to adjust to it. And for people using defaults - nothing changes. Should improve
performance especially on Windows.
BREAKING CHANGE: You need to configure the stepDefinitions if you use the nonGlobalStepDefinitions
option.
re #295 , fix #283

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[COMPATIBILITY] Removing Moons in other Mods

In attempts to remove select moons from
{
https://thunderstore.io/c/lethal-company/p/Generic_GMD/Generic_Moons/
https://thunderstore.io/c/lethal-company/p/Dafini/Dafis_Mega_Moon_Pack_Emporium/ <--- this mod
https://thunderstore.io/c/lethal-company/p/sfDesat/Orion/
https://thunderstore.io/c/lethal-company/p/Magic_Wesley/Infernis/
https://thunderstore.io/c/lethal-company/p/KayNetsua/E_Gypt_Moon/
}
Log:
LogOutput.log
I could not remove moons by using the comma separations. I tried with spaces and without spaces in the LethalConfig.
Specifically, I tried removing the moons from dafis mega moon pack emporium when I had all of these mods installed. I cannot separate moons within this pack without affecting source directly.
The command worked when I tried to remove Wateridge, however failed within the emporium modpack. Why?
LethalExpansion(core) config;
ExcludedMoons - hidden,Wateridge,Windfallfall Island,The Moon,Chao Garden
The moons "windfallfall island", "the moon", and "chao garden" still show after excluding them.
https://github.com/HolographicWings/LethalExpansion/issues/106#issue-2104331913

The log says that Chao Garden, The Moon and Mayhem Temple was excluded, I think the problem is the difference between the moon and planet name, it is registered as Windfall Island but displayed as Windfallfall Island

Yeah. I'm operating from memory here, but Mayhem Temple was the first one I tried excluding. I "removed" it using the command, but it didn't remove it from the terminal list of moons.


Return 401 for requests from the future

The real fix is upstream in chef_auth, this pulls in that fix and adds
a pedant test for it.  Previously, we would return 200 for any request
from the future, even if it was beyond the allowed time skew.
Signed-off-by: Steven Danna<EMAIL_ADDRESS>

Depends on https://github.com/chef/chef_authn/pull/34


Update refined, refined-scalacheck to 0.11.0

About this PR
📦 Updates

eu.timepit:refined
eu.timepit:refined-scalacheck

from 0.10.3 to 0.11.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "eu.timepit" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "eu.timepit" }
}]

labels: library-update, early-semver-major, semver-spec-minor, commit-count:1

Codecov Report
Patch and project coverage have no change.

 Consider uploading reports for the commit 7d6e939 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@              Coverage Diff               @@
##           series/0.14.x    #2163   +/-   ##
==============================================
  Coverage          85.11%   85.11%
==============================================
  Files                 76       76
  Lines               2715     2715
  Branches             344      344
==============================================
  Hits                2311     2311
  Misses               404      404

Flag
Coverage Δ

2.12.17
84.94% <ø> (-0.04%)
:arrow_down:

2.13.10
85.30% <ø> (+0.07%)
:arrow_up:

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

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


Fix bug that caused error reporting to not work in some cases

I'm not sure from which language the his() invocation came, but it is not the JavaScript way.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Hans Huebner seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Need to re-open with correct email address


Clean up temporary directories on startup

Currently, there are 13 GB of documentation in /tmp/docsrs-docs* on the production server. Most of these are from many months ago, which means the temporary directories were never cleaned up. Since we clean up temp directories explicitly, this means a panic happened while the crates were built: https://github.com/rust-lang/docs.rs/blob/9883f210232df2e7ecf0f0bfeae72c4437a3ddc9/src/docbuilder/rustwide_builder.rs#L410
As a workaround, docs.rs should remove all /tmp/docsrs-docs* files at startup (not on an interval, or it may interrupt ongoing builds).

Note that as per the docs, if the destructor for the temp directory is not run, the directory won't be deleted:

Note that if the program exits before the TempDir destructor is run, such as via std::process::exit(), by segfaulting, or by receiving a signal like SIGINT, then the temporary directory will not be deleted.


Expose DatastoreStorageFactory SPI API in a developer-friendlier way

TL;DR
Improve SPI-related APIs of DatastoreStorageFactory, e.g. expose converterFactory field setter as Builder public API.
The DatastoreStorageFactory provides an SPI API that allows configuring how the InboxStorage instance is created with overring the inboxStorageWith(DatastoreWrapper wrapper, boolean multitenant) method.
But at the same time, the DatastoreStorageFactory itself can only be instantiated with an instance of the respective Builder that has a converterFactory which is essential for the factory. The problem is that this converterFactory field cannot be set via Builder public API and thus the factory cannot be properly instantiated.
The only way to instantiate the factory with a properly built builder right now without reimplementing the factory itself is to use reflection API and set the converterFactory directly, e.g. like this:
    private static synchronized void
    setConverterFactory(DatastoreStorageFactory.Builder builder, NsConverterFactory factory) {
        try {
            Field converterFactory = DatastoreStorageFactory.Builder.class
                    .getDeclaredField("converterFactory");
            boolean accessible = converterFactory.isAccessible();
            converterFactory.setAccessible(true);
            converterFactory.set(builder, factory);
            converterFactory.setAccessible(accessible);
        } catch (IllegalAccessException | IllegalArgumentException | NoSuchFieldException | SecurityException e) {
            throw newIllegalStateException(
                    e, "Cannot set `converterFactory` for `DatastoreStorageFactory.Builder`."
            );
        }
    }

The other desirable change should be a public API that allows configuring the DatastoreMode of the DsInboxStorage instances created with the DatastoreStorageFactory.

These changes depend on storage changes that we're going to introduce in v2.


Node connecting multiple times to same peer(s)

info: Stratis.Bitcoin.FullNode[0]
      ======Node stats====== 10/08/2017 08:35:05 agent StratisBitcoin:1.0.2
      Headers.Height:        141052   Headers.Hash:         114d66e7f82740f65d65440b7049b191311340efdcf550142bdcf6bc86b699bb
      LightWallet.Height:    141052   LightWallet.Hash:     114d66e7f82740f65d65440b7049b191311340efdcf550142bdcf6bc86b699bb
      ======Connection======
      Node:::ffff:<IP_ADDRESS>:26178,           connected (outbound),      agent /Stratis:<IP_ADDRESS>/,  height=141048
      Node:::ffff:<IP_ADDRESS>:26178,           connected (outbound),      agent /Stratis:<IP_ADDRESS>/,  height=141048
      Node:::ffff:<IP_ADDRESS>:26178,        connected (outbound),      agent /Stratis:<IP_ADDRESS>/,  height=141052

Above is from running dotnet run stratis -testnet daemon from ./Stratis.BreezeD
However these duplicate connections don't occur with the Bitcoin daemon

This is probably by chance it does not happen in bitcoin (or perhaps it will only created with c# nodes)
Thanks we need to investigate this

This is now fixed https://github.com/stratisproject/NStratis/pull/38


reflect: StructOf allows creation of invalid types

At tip, the following are permitted:
reflect.StructOf([]reflect.StructField{{
	Name:    "height",
	PkgPath: "path/to/bar",
	Type:    reflect.TypeOf(float64(0)),
}, {
	Name:    "age",
	PkgPath: "path/to/foo",
	Type:    reflect.TypeOf(int(0)),
}})

Here, the height and age fields have different PkgPath. To my knowledge, this is not possible for any real normally declared type. I expect this to panic.
reflect.StructOf([]reflect.StructField{{
	Name:    "height",
	PkgPath: `!"#$%&'()*,:;<=>?[\]^{|}`,
	Type:    reflect.TypeOf(float64(0)),
}})

Here, the PkgPath permits characters that the Go specification suggests not be used. Should we panic?

/cc @rsc @ianlancetaylor per owners and /cc @griesemer since this may be related to the Go specification.

@dsnet Do you know if this behavior is new to 1.14, or did it exist in 1.13, 1.12 as well?

This functionality was added in https://go-review.googlesource.com/c/go/+/85661, so it is specific to Go1.14.

\cc @crawshaw


Broken in latest Obsidian update!

The plugin is very likely partially broken from the latest obsidian update. This is because of the removal of app://local links, and the reformatting of embedded src URLs. This will be fixed in the next update but until then some things may be broken. Inlined media should work still.

This is fixed in update 1.6.0


[Feature/Improvement] Allow volume to be passed in to the background service

Purpose: As a user, I would like to be able to control the volume of sound effects.
More details: Original request: https://github.com/a-mabe/OpenHIIT/issues/136
Acceptance Criteria:

Volume can be passed in to the background service.
User has full control of sound effect volume and can adjust to increase or decrease volume as needed.

Closed in #17


Add missing un_locode for south sudan

I've also added a spec to check that each country has a un_locode and regenerated countries cache.

Very good test and all! Thank you for all your hard work!


Allow PrimaryClusterId to be set per session

When running commands against the PowerShell SDK there are many times when I have to set the PrimaryClusterId parameter to 'local' to only retrieve results from the connected cluster.  This gets to be cumbersome having to always filter out objects from other clusters
It would be nice to be able to set the PrimaryClusterId parameter to 'local' or to a cluster id on a per session basis.
This can be accomplished by adding the attribute to the globally defined $rubrikConnection variable within the Connect-Rubrik cmdlet. IE:
$global:rubrikConnection = @{
                id      = $content.id
                userId  = $content.userId
                token   = $content.token
                server  = $Server
                header  = $head
                time    = (Get-Date)
                api     = Get-RubrikAPIVersion -Server $Server
                version = Get-RubrikSoftwareVersion -Server $Server
                authType = 'Basic'
                primaryClusterId = $null
            }

And then setting a default value on the cmdlets which utilize the PrimaryClusterId parameter. IE:
# Filter the summary information based on the primarycluster_id of the primary Rubrik cluster. Use 'local' as the primary_cluster_id of the Rubrik cluster that is hosting the current REST API session.
    [Alias('primary_cluster_id')]
    [String]$PrimaryClusterID = $global:RubrikConnection.primaryClusterId,

As shown below, end-users can then simply set the $rubrikConnection.primaryClusterId value per session and not have to deal with passing it to all of the cmdlets.

The following will retrieve all cmdlets which could be updated with the default PrimaryClusterId
Get-Command -Module Rubrik -ParameterName 'primary_cluster_id'

In talks with @jaapbrasser we think that creating something like Get-RubrikModuleOption and Set-RubrikModuleOption would be a better solution.  This would allow setting more defaults than just the PrimaryClusterId.  IE, being able to apply or not apply custom TypeNames, etc...


nodejs onboarding guide [ch4827]

example code here: https://github.com/windmilleng/tilt-example-nodejs/
screenshots/snapshots pending until all the kinks in the app have been worked out.

Accepted all your suggestions specific to this doc, left a handful that are for shared copy and will apply those in a separate PR.

@nicks or @jazzdan can i get some JS engineer eyes?

Added images (with some templating logic to make it easier to update them, keep logic uniform, etc.) -- possibly overkill but I had a weird morning and this was a nice distraction.


AffinityPropagation.ipynb added

??
is this required or where you testing some code part

This descriptions have TYPOS.

put the seaborn import will together with other in single code cell

??
is this required or where you testing some code part

Yes, It was for testing the code,I will remove it


Roll Flutter Engine from 15c15fd75743 to 5f48d69f3c63 (1 revision)

https://github.com/flutter/engine/compare/15c15fd75743...5f48d69f3c63
2023-07-17<EMAIL_ADDRESS>Roll Skia from f29d58569c67 to f2a4222bb72e (1 revision) (flutter/engine#43746)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Confirm Network Connectivity for Gov endpoints is not working

Hello,
I'm not being successful in testing the government endpoints as suggested in this document. See link:
https://docs.microsoft.com/en-us/azure/active-directory/authentication/troubleshoot-sspr-writeback#confirm-network-connectivity
These are my PowerShell results when testing the following gov endpoint: ssprdedicatedsbprodscu.servicebus.usgovcloudapi.net
PS` C:\WINDOWS\system32> Test-NetConnection -ComputerName ssprdedicatedsbprodscu.servicebus.usgovcloudapi.net
WARNING: Name resolution of ssprdedicatedsbprodscu.servicebus.usgovcloudapi.net failed
ComputerName   : ssprdedicatedsbprodscu.servicebus.usgovcloudapi.net
RemoteAddress  :
InterfaceAlias :
SourceAddress  :
PingSucceeded  : False
Also, I do not see the usgovcloudapi.net endpoint listed for Identity on this article:
https://docs.microsoft.com/en-us/azure/azure-government/compare-azure-government-global-azure#guidance-for-developers
Wondering if there needs to be an update to assist customers with testing SSPR on Azure Government. Thank you.

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

ID: a6c7b290-3f3e-70c9-7524-80d7364dd763
Version Independent ID: d12b324f-57b2-9fd8-a433-b25644424171
Content: Troubleshoot self-service password reset writeback- Azure Active Directory
Content Source: articles/active-directory/authentication/troubleshoot-sspr-writeback.md
Service: active-directory
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

@josuvil
Thanks for your feedback! We will investigate and update as appropriate.

@josuvil sorry for delay but I think the URL is right. I do see it listed under Integration https://docs.microsoft.com/en-us/azure/azure-government/compare-azure-government-global-azure#guidance-for-developers


netCDF dimensions for single level variables

There seems to be an inconsistency between the list of dimensions that we expect to appear in single-level netCDF files and the information about the same single-level variables in the ccmi-2022 MIP tables.
An example is the Aday variable ta500.
In the Aday MIP table, ta500 has the dimensions: "longitude latitude time1 p500" which implies that the pressure level should appear as a dimension in the netCDF file.  However, the ceda-cc checks expect the pressure level to appear as a coordinate attribute.
I think this discrepancy is at the root of the metadata "errors" that ceda-cc is detecting in the NIES data #54 #51 .
It seems to me that Hideharu is following the rules of the MIP table, it is just that those rules are not the same as the conventions that we actually want the data to follow.
        "ta500": {
            "frequency": "dayPt",
            "modeling_realm": "atmos",
            "standard_name": "air_temperature",
            "units": "K",
            "cell_methods": "area: mean time: point",
            "cell_measures": "area: areacella",
            "long_name": "Air Temperature at 500hPa",
            "comment": "Air temperature on the 500 hPa surface",
            "dimensions": "longitude latitude time1 p500",
            "out_name": "ta500",
            "type": "real",
            "positive": "",
            "valid_min": "",
            "valid_max": ""

Hi Charlotte
Looking into the CF conventions document (Section 2.4), there is the following:

Dimensions may be of any size, including unity. When a single value of some coordinate applies to all the values in a variable, the recommended means of attaching this information to the variable is by use of a dimension of size unity with a one-element coordinate variable. It is also acceptable to use a scalar coordinate variable which eliminates the need for an associated size one dimension in the data variable.

Including p500 as a dimension of size one (and not as a scalar coordinate) would also seem to conform to the CF conventions, I guess?? But it does add the complication that people reading the data need to define the variable with this extra dimension of size one which can be a pain when working with a mixture of different approaches.
And I will also add, the CCMI-2022 tables with this extra dimension tacked on the end follows numerous similar examples in the CMIP6 MIP tables. And when I used CMOR3 for CCMI-2022 it seemed to recognize p500 as a scalar coordinate and added the appropriate coordinate attribute.


FIND YOUR STOLEN BITCOIN BY CONTACTING ADWARE RECOVERY SPECIALIST

WhatsApp info: +1 (571) 541‑2918
Website info: www.adwarerecoveryspecialist.expert
Email info: Adwarerecoveryspecialist@auctioneer. net
I remember when my colligue at work were being scammed, The journey began with excitement and promise, as they invested $116,000 worth of Bitcoin with a seemingly reputable online cryptocurrency company. With their investment quickly ballooning to $200,000 in just a few short weeks, it seemed like their financial dreams were coming true. However, when the time came to cash out and enjoy the fruits of their labor, they were met with a harsh reality. Withdrawal requests were repeatedly denied, and their attempts to contact the company for assistance fell on deaf ears. It soon became clear that they had fallen victim to a sophisticated scam, losing not only their initial investment but also their trust in the cryptocurrency market. Amidst the turmoil,  ADWARE RECOVERY SPECIALIST emerged as a beacon of hope. With their specialized expertise in cryptocurrency asset recovery, they took swift and decisive action to rectify the injustice inflicted upon their client. Through meticulous investigation and relentless determination, they traced the stolen funds back to their source, unraveling the intricate web of deception that had ensnared their client. Their efforts culminated in a triumphant victory as the stolen funds were successfully recovered and returned to their rightful owner. What had initially seemed like an insurmountable loss transformed into a story of resilience and redemption, thanks to the unwavering support of ADWARE RECOVERY SPECIALIST. In a landscape rife with uncertainty and fraud,  ADWARE RECOVERY SPECIALIST  stands as a steadfast ally for those who have been wronged. Their commitment to justice and their clients' well-being sets them apart as leaders in the fight against cryptocurrency deception. For anyone who has fallen victim to fraudulent schemes, ADWARE RECOVERY SPECIALIST offers not only a chance to reclaim their lost fortunes but also a glimmer of hope for a brighter future in the world of digital investments. Check out the information above:

CONTACT INFORMATION OF TRUST GEEKS HACK EXPERT
Website. www://trustgeekshackexpert.com/
Email::  trustgeekshackexpert(@)fastservice(.)come
WhatsApp   +1-4-0-6- 2-1-8-6-9-0-0
As a 22-year-old undergraduate student on campus, my journey into trading began during my high school years. Through diligent efforts and strategic investments, I managed to amass a small fortune of $370,000. However, everything took a drastic turn when my close friends caught wind of my success. Soon after, I found myself bombarded with malicious emails, and one fateful day, I made the grave mistake of opening one. In an instant, my account was compromised, and my entire financial portfolio vanished into thin air. Panicked and devastated, I frantically searched for a solution, and that's when I stumbled upon TRUSTGEEKS HACK EXPERT. From the moment I reached out to them, the team at TRUSTGEEKS HACK EXPERT provided me with unwavering support, encouragement, and hope. Despite the overwhelming sense of despair, their reassuring words and effective communication helped alleviate my anxieties. Within just 48 hours, they were able to recover my email account and secure it from further breaches. Unfortunately, my accounts had been wiped clean by the malicious attackers. However, the expertise of the TRUSTGEEKS HACK EXPERT team proved invaluable once again as they swiftly pinpointed the culprits behind the cyber attack. To my shock and dismay, it turned out to be my close friends who had orchestrated the entire scheme.Determined to seek justice, I took legal action against them with the assistance of TRUSTGEEKS HACK EXPERT Despite the initial betrayal, I was pleasantly surprised when my friends ultimately compensated me generously for their wrongdoing. The resolution of the matter not only provided me with financial restitution but also closure and a valuable lesson in trust and loyalty.Reflecting on the experience, I realized the importance of vigilance and cybersecurity in the digital age. I also learned the true value of genuine friendship and the devastating consequences of betrayal. Throughout the ordeal, I remained immensely grateful to the TRUSTGEEKS HACK EXPERT  team for their unwavering support and expertise.In conclusion, my journey with TRUSTGEEKS HACK EXPERT was a testament to their professionalism, dedication, and effectiveness in handling cyber-related crises. For anyone facing similar challenges, I wholeheartedly recommend TRUSTGEEKS HACK EXPERT as a trusted ally in navigating the complexities of digital security and seeking restitution.


Create Gitter room

Can you create a gitter.im room for this repository by any chance, similar to what the roslyn/corefx/coreclr teams have done?

Sure, why not. It's at https://gitter.im/Microsoft/VisualStudio-TestHost
Looks like I can't enable the webhooks because I don't really own this repo. Is that something that's really important? I haven't used gitter.im before.

It's nice, but not required. If you try to configure the webhook through Gitter, there is a section for "Manual" configuration. It will give you a key that you can copy and send to the internal team that actually owns this repository, and they can configure the webhook for you from the GitHub side.


merge MONDO_0019625 'familial thoracic aortic aneurysm and aortic dissection' with OMIMPS

On the comment for MONDO_0019625 'familial thoracic aortic aneurysm and aortic dissection', it says to merge with the OMIM phenotypic series: MONDO_0011769 'familial aortic dissection'

Hi @nicolevasilevsky we currently have 23 gene curations on the ClinGen website that use MONDO_0019625.
See: https://search.clinicalgenome.org/kb/conditions/MONDO_0019625
I have emailed members of our software team for inquiries on how to handle a change like this, as well as talking with the Expert Panel. I hope to be able to update you on this possible change soon.

From GARD:
We have Familial thoracic aortic aneurysm and dissection with Familial thoracic aortic dissection as a synonym.  Orphanet also have Familial thoracic aortic aneurysm and aortic dissection which is more accurate for the clinical features.

Thanks @nicolevasilevsky , I will take this information back to the group to see if we have anymore feedback. So just so that I get my understanding straight, the MONDO:0019625 will still be a valid ID (i.e. it is not be deleted), however the nomenclature or title will change to familial aortic dissection. Is that correct?

Or will the MONDO:0019625 now become MONDO_0011769? @nicolevasilevsky
Thanks!

I think we'll want to keep MONDO:0019625 'familial thoracic aortic aneurysm and aortic dissection' and obsolete MONDO_0011769 'familial aortic dissection'
Would that work for you, @courtneythaxton ?

Yes that would work for me @nicolevasilevsky. Thank you for your responsiveness and feedback!

Glad to see this chain. The point is to avoid dissection!
Thanks,
Ada


Clearing Field

Setting the bound data to an empty string does not clear the date from the input field.

Fixed in 1.3.0


[Bug]: Actual Server fails to start when host has IPV6 disabled

Verified issue does not already exist?

[X] I have searched and found no existing issue

What happened?
When trying to start actual-server locally or through Docker on a host that has IPv6 disabled, the server fails to start as it tries to bind port 5006 to :: on IPV6.  With IPV6 being disabled on the host through the kernel, the bind fails and actual-server is unable to start.
What error did you receive?
Checking if there are any migrations to run for direction "up"...

Migrations: DONE

Listening on :::5006...

node:events:495

      throw er; // Unhandled 'error' event

      ^

Error: listen EAFNOSUPPORT: address family not supported :::5006

    at Server.setupListenHandle [as _listen2] (node:net:1800:21)

    at listenInCluster (node:net:1865:12)

    at doListen (node:net:2014:7)

    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)

Emitted 'error' event on Server instance at:

    at emitErrorNT (node:net:1844:8)

    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {

  code: 'EAFNOSUPPORT',

  errno: -97,

  syscall: 'listen',

  address: '::',

Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Other
Operating System
Linux

Duplicate of https://github.com/actualbudget/actual-server/issues/336


TeX: Correct the Report with reference to Davidson

SVC perfroms way better than Logistic Regression and unified with Davidsons methodology to allow better comparison-

Done in f369769ff2d65932e95f01ebe029e6ac52b71f51


Add offline transaction energy estimation

Local energy estimation allows determining the transaction fee without making a wallet-proxy request. This helps when the transaction payload is too large to fit into a GET request.How it is done in Rust:concordium-rust-sdk/src/types/transactions.rs at 01b00f7a82e62d3642be51282e6a89045727759d · Concordium/concordium-rust-sdk (github.com)

Most transactions are straight forward to implement.
But for the smart contract init- and update-transactions this can only be estimated by running the smart contract using our smart contract execution, which quickly could make this a complex task.

Found out it is already there: Payload.java


Show packager error stack

Motivation: get more info from packager errors to easier debug them
Test Plan
add throw new Error('error') here https://github.com/iyegoroff/react-native/blob/635f2740c28da594f236d4227b6450fddef4b599/local-cli/cliEntry.js#L116 and run
react-native start to see error stack

[CLI] [ENHANCEMENT] [local-cli/cliEntry.js] - Show packager error stack

Can you share an example of how the output is changed after this fix is applied?

Output for throw new Error('some error inside addCommand') without error stack:

Output for throw new Error('some error inside addCommand') with error stack:

Output for throw new Error('some error inside metro/Server/index.js') with error stack:


memdb: refactor code of art to make it more understandable

Some refactor work to make the code of new ART implementation more understandable.

@ekexium @zyguan PTAL


v4 form input issues

Two separate issues noticed on Windows 10, in Chrome 60, Firefox 54.0.1, Edge 38. I noticed these in the docs

A <select class="form-control form-control-lg"> needs more height

Text color is inconsistent between a disabled input vs. select

I came to report this. For select element below styles might update as below...
Base Style for form-control-lg
.form-control-lg, .input-group-lg>.form-control,
.input-group-lg>.input-group-addon,
.input-group-lg>.input-group-btn>.btn {
    padding: 0.6rem 1rem; /* updated */
    font-size: 1.15rem; /* updated */
    line-height: 1.4; /* updated */
    border-radius: .3rem;
}

height update for form-control
select.form-control:not([size]):not([multiple]) {
    height: calc(2.45rem + 2px);
}

height update for form-control-lg
.input-group-lg>.input-group-btn>select.btn:not([size]):not([multiple]),
.input-group-lg>select.form-control:not([size]):not([multiple]),
.input-group-lg>select.input-group-addon:not([size]):not([multiple]), select.form-control-lg:not([size]):not([multiple]) {
    height: calc(3.1rem + 2px);
}

System Details --
Win 7
Chrome - 59.0.3071.115
Above changes update the controls as below.

Yea, text is cutting http://joxi.ru/eAO4PzGt4GpPbr

Not only the select, also the input, under line glyphs does not display correctly

Bug reports must include a live demo of the problem. Per our contributing guidelines, please create a reduced test case via JS Bin or CodePen and report back with your link, Bootstrap version, and specific browser and OS details.

@Johann-S
https://output.jsbin.com/moyujufara
on latest firefox win 10

Regular <select>s are also cutoff https://jsbin.com/sixiqaruxe/edit?html,output

Firefox 55/Linux cuts the input with the standard 1.25 line-height. Here an example of a number field:

Setting the line-height slightly higher to 1.35 fixes the issue:

Stop closing issues that haven't been addressed or even mentioned in regards to fixing.

@kjdion84 please look at what is being closed, what is being kept open, and what's being cross-referenced and consolidated as a single issue (in this case, THIS one). all you're doing now is generating more noise for people to wade through.

Having fundamental issues such as text being cutoff in every single <select> is worth generating more noise about because its ridiculous that this hasn't been fixed yet.

you seem to misunderstand the idea of how open source run by volunteers works. feel free to send a pull request with fixes.

Will do thanks for your time.

Solution:
/* fix form control text cutoff */
.form-control {
    line-height: 1.5;
    height: auto !important;
}

Note that this problem can be reproduced with free Windows virtual machines from Microsoft, see https://github.com/twbs/bootstrap/issues/23769#issuecomment-331377830

Note I believe the issue of height cut off was fixed by https://github.com/twbs/bootstrap/pull/23150 as there is a bug with the form-control-lg height in the current beta (which the above examples are using). I'm afraid it's quite hard to work this out from the git history though.
The padding issue of #24043 (marked as duplicate of this) is still present in current v4-dev. This has a couple of parts:

Options have a little bit of unremovable magic left padding in Chrome, Firefox, (maybe Safari?);
Padding on select is e.g. ignored on desktop Chrome and Safari (but is followed in Firefox), and (sort of) honoured on Android Chrome.
So the left padding needs to be 3px(?) less for selects than inputs in order to align with text inputs, except it still won't in desktop Chrome/Safari as they ignore it whatever it is. The only way everything could always line up would be if the left-padding was fixed, at whatever size, at whatever desktop Chrome/Safari are using as their unchangeable value.

already fixed with our last dist files see : https://codepen.io/Johann-S/pen/MEpBdR

It isn't fixed properly. The issue still exists for even normal selects in Chrome on Windows.
Characters are still being cut off as the text is still not centered vertically properly.
Proof fiddle: https://codepen.io/anon/pen/WZpPPp
Proof image: Imgur

Can y'all test out the changes in #24199?

#24199 looks good! Tested with latest DEV Bootstrap version.
W7 and IE11:

W7 and Chrome:

There is one problem in DEV Bootstrap version:
Windows 7, Internet Explorer 11, see different input and input-group-addon height

It works fine in latest Chrome and Firefox. Should I report it as a separate issue?

#24199 does fix the default form-control being cut off at the bottom, yes :-)
The disabled text colour being different for inputs/selects (original issue part 2) is still present
The left-padding being different for different controls (#24043, closed as a dupe of this) is still present, but as I commented at https://github.com/twbs/bootstrap/issues/23347#issuecomment-332493174 it doesn't really sound easily fixable.

Thanks!
(@jrysig, my personal suggestion would be yes to a separate issue, makes it easier to track.)

@mdo it looks much better and also scales well with -lg.

@jrysig That should be fixed as of #23810.

@josephzidell @dracos The different text color is because the <input> is using a placeholder vs the select menu showing an <option>. Selects don't support placeholder attributes.

@mdo Makes sense! The original text of this issue is fixed, therefore, yes, the only issue is the left padding.


fix(gzip)!: change the default block size

BREAKING CHANGE: the default gzip block size is changed to 256<<12, was previously 256<<10.
The layers created by ecosystem tools and stacker are different for the same tar content. Unfortunately, the OCI image spec doesn't standardize/encode this in the document. Hence, we standardize in the implementation.
We now link against our own fork: github.com/project-stacker/umoci which may change depending on the PR getting merged to upstream.

What type of PR is this?

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

Automation added to e2e:

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

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

Suggestion in commit message:

Updated.


Dependabot stats have low contrast

I find the stats on the dependabot overview card to be a little difficult to read. Also the colors of High severity and critical severity are quite similar.

GitHub appears to use
Critical: #cf222e
High: #bc4c00
Moderate: #bf8600
Low: #24292f
Perhaps it would be good to stick with these colors for contrast and familiarity reasons?

https://app.clubhouse.io/larder/story/3884

Low: #24292f

@dtuite I am just not sure about "Low" with dark theme, but others look good

@Irma12 Good point. It should be just a matter of switching GitHub to dark mode and checking the colors they use for that case. We can use the same 2 sets of colors.


python311Packages.fschat: fix build

Description of changes
The build was broken: https://hydra.nixos.org/build/249263007/nixlog/1

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 288121 run on x86_64-linux 1

2 packages marked as broken and skipped:

python312Packages.fschat
python312Packages.fschat.dist

2 packages built:

python311Packages.fschat
python311Packages.fschat.dist

I'm doubtful that this works, because pydantic 2.0 is a rewrite.
Instead, please bump to today's version, which luckily dropped the pin!
https://github.com/lm-sys/FastChat/blame/main/pyproject.toml#L17


Routes lowercased?

Should routes not be all lowercased?
Right now I have a lot of routes like :
resumeInvites
referenceSources
jobCategories
looks kinda 'ugly' ...

@axyr Yes, I think we should use snake_case because what I found is, most of apis are using snake cases in their urls.
http://stackoverflow.com/questions/778203/are-there-any-naming-convention-guidelines-for-rest-apis
http://blog.octo.com/en/design-a-rest-api/#case

api routes are now snake cased.
folder name for model views is not snake cased.
Also, we are using bit more user-friendly name at various places like views, flash messages etc.
e.g. instead of "UserStatues" in view & flash messages, we are using "User Statues".


ContextMenu

Description
Hey :)
i want to use the ContextMenu Component. But useMouse() and useWindowScroll() are not defined ?

Oh I see, you're trying to replicate the examples of the ContextMenu from the documentation right?
You need to import those composables: import { useMouse, useWindowScroll } from '@vueuse/core' if you haven't installed @vueuse/nuxt.


Test [de]serialization of metadata with more than one item in each container and zero items (where valid)

Description of issue or feature request:
Testing, particularly [de]serialisation, should cover metadata containers with more than one item and, where it makes sense, zero items.
Current behavior:
Testing only covers one item per container.
Ref https://github.com/theupdateframework/tuf/issues/1478

I started working on this and adding tests.


Wrong include directories in library CMakeLists.txt

I tried to build a C++ application using the Vitis AI library (1.4) with a self-built petalinux sdk. When using CMake to find and link to the Vitis AI, CMake complains that the include path /test_publ does not exist. It looks like this stems from this line in the Vitis-AI-Library:
https://github.com/Xilinx/Vitis-AI/blob/f61061eef7550d98bf02a171604c9a9f283a7c47/tools/Vitis-AI-Library/model_config/CMakeLists.txt#L38-L40
This seems to be a bug in the usage of the generator expression. The expression $<BUILD_INTERFACE:${CMAKE_CURRENT_BINARY_DIR}>/test_publ resolves to /test_publ if BUILD_INTERFACE is false, which is the case when using the built library from a SDK. Shouldn't it be $<BUILD_INTERFACE:${CMAKE_CURRENT_BINARY_DIR}/test_publ>, which would result in an empty string in that case?
Or linking in PRIVATE mode since this include directory isn't used when the library is installed?

Thank you for your feedback, please change PUBLIC to PRIVATE, we will fix this problem in the next update

Hi, @andreasmuetzel-ametek . It has been fixed in 2.0, please have a test, after the test is ok, please close the issue. Thanks for your feedback.
And if there is no feedback, we will close the issue 1 week later.

Hi, thanks! I can't test it right now, but I had a look at the changed lines in the master branch and they look fine to me now. So I think it's reasonable to close the issue :)


fix scrollTo behavior

Bring Section#path inline with the sectionPath used by focusDocument.
scrollTo was broken because the comments used the focusDocument,
but the document component was trying to match this with Section#path
To support this the facet had to be add to the Unit when it was loaded.
The PT story has steps to demonstrate the issue:
https://www.pivotaltracker.com/story/show/183643073
Ideally this should have tests to verify the two ways of constructing paths are consistent. But there isn't an easy way to do that because the focusDocument approach requires setting up the whole component hierarchy.

It isn't that urgent, I just wanted to make the code changes before I forgot what I had in mind. I'm supposed to work on something else instead of this. So I think we can take time to get it right, it'll just be in the margins.
I agree that having children know about their parents is bad. It seems reasonable to me to refactor this into an external utility function called something like getSectionPath(section). It'd be nice to put that next to buildSectionPath but that would introduce a dependency on MST inside of the cloud functions. So perhaps the right place is in unit.ts.


Remove notebooks and paper data from pypi release

The current PyPi release is ~15mb which is far too much for a source code repo. We should remove unnecessary data that's not needed for the release, such as the paper code/data.

Closed with #99
Release size has been reduced to ~30 kB.

Closed with https://github.com/neuromorphs/NIR/pull/99
Release size has been reduced to ~30 kB.


Fix some memory leaks and an iterator use after free

This is the 2nd half of https://github.com/gpu/JOCL/pull/37. I think all of these leaks are in error conditions. The only non-error condition fix is an iterator use-after-free in destroyCallbackInfo

Thanks for that. I'm almost certain that the change to the iterator usage also fixes https://github.com/gpu/JOCL/issues/30#issuecomment-688455733 , but this will have to be verified.


Feature: Focus existing tab when opening location from external process

Resolved / Related Issues
To prevent extra work, all changes to the Files codebase must link to an approved issue marked as Ready to build. Please insert the issue number following the hashtag with the issue number that this Pull Request resolves.

Closes #6925

Steps used to test these changes
Stability is a top priority for Files and all changes are required to go through testing before being merged into the repo. Please include a list of steps that you used to test this PR.

Set Files as default file manager
Confirmed opening path from external location focuses on existing tabs
Confirmed opening path from external location adds a new tab if needed

@0x5bfa did you also check functionality wise?

I'll do that in a day I think.


Allow user to change port

I've had to hack at the code to change the default ports from 443, to 8443 as I'm running through a reverse proxy. It's working.
But is there any reason why this option hasn't been added?

Could you please provide the source code of your implementation?
I'm facing the same issue for a specific subdomain.

Could you please provide the source code of your implementation? I'm facing the same issue for a specific subdomain.

Hello. Yes, we can help you. Contact us at<EMAIL_ADDRESS>


CLI 2.0

Several links to GitHub should be update to https://github.com/azure/azure-cli

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

ID: 9bfdd999-341a-7aa8-04cf-f3808d813051
Version Independent ID: 76d4e553-fdd3-8339-6a11-870d53efdeb2
Content: Install the Azure classic CLI
Content Source: docs-ref-conceptual/install-classic-cli.md
Product: azure
Technology: azure-cli
GitHub Login: @sptramer
Microsoft Alias: sttramer

This article is explicitly for installing the Azure "classic" CLI, so all of the links are correct.


how to draw a service path over topology network

Please make sure to read the following list before creating a new issue:

This issue tracker is not supposed to be used for questions on how to use visjs. It is intended to be used for bug reports and feature requests! In case you face yourself with a usage question, then post your question e.g. on stackoverflow tagged with "vis.js".
Have you already used the github search, read the documentation and looked at the examples?
Make sure to use the latest version of vis-network for bug reports.
Make sure to mention which browser and OS you are using when creating a bug report.
Please provide a minimal code example that demonstrates your issue. We recommend using jsbin for that.
Delete this list from the actual issue.

Hi guys,
I have created my network based on vis-network, it is great and efficient. but i have more requirements than this, i want to draw a path over the network topo, do we have a method that can do it, or do we have an API , we could draw a path over the network topo.  just like attached. thank you very much
best
zachary

Burn her!
Where'd you get the coconuts? Burn her anyway! And this isn't my nose. This is a false one. Be quiet!
Ah, now we see the violence inherent in the system! You don't frighten us, English pig-dogs!
Listen. Strange women lying in ponds distributing swords is no basis for a system of government. Supreme executive power derives from a mandate from the masses, not from some farcical aquatic ceremony.
Camelot! The Knights Who Say Ni demand a sacrifice! Well, how'd you become king, then? A newt?
Oh! Come and see the violence inherent in the system! Help, help, I'm being repressed!
But you are dressed as one…
Why?

Who's that then?
We want a shrubbery!! …Are you suggesting that coconuts migrate? We found them. You don't vote for kings. Well, I didn't vote for you. Camelot!
Did you dress her up like this?
Why do you think that she is a witch?

And this isn't my nose. This is a false one.   Oh! Come and see the violence inherent in the system! Help, help, I'm being repressed!
Did you dress her up like this? …Are you suggesting that coconuts migrate? Well, we did do the nose. On second thoughts, let's not go there. It is a silly place. And this isn't my nose. This is a false one.
Well, how'd you become king, then? Look, my liege! Be quiet! Oh, ow! Camelot!
I have to push the pram a lot. And the hat. She's a witch! Be quiet! But you are dressed as one…
Well, I didn't vote for you. I'm not a witch. Bring her forward! We found them. You don't vote for kings. Bring her forward!
But you are dressed as one… I'm not a witch. We found them. Be quiet!  You don't vote for kings.
 The Knights Who Say Ni demand a sacrifice!
  Why? Bring her forward! And this isn't my nose. This is a false one.
Well, what do you want? What do you mean? You don't frighten us, English pig-dogs!
I'm not a witch. A newt? No, no, no! Yes, yes. A bit. But she's got a wart. Bloody Peasant!
 Well, Mercia's a temperate zone! Well, how'd you become king, then? Where'd you get the coconuts? I'm not a witch.
Hi @zachary918,
you can use the afterDrawing event to draw anything on the canvas, including the line shown on your screenshot.

thanks a lot, cloud you please provide an example with afterDrawing, thanks again

great! thanks a lot for your help!


The much awaited name change

Changed:
jigglypuffRL - genrl
jigglypuff-rl - genrl
classicalrl - classical
deeprl - deep

Will add tests and merge after #96 is merged

Can you change things in the docs/source/conf.py as well?

Yeah, there are a lot of changes to be made apart from that also

Ok

I'm able to build documentation and see all modules locally. I think its the name thats conflicting now

Okay, let's see if it works after this

Going through the modules we're pretty much importing everything into the main package which we should change probably in the future

I think you'd have to merge it see the docs, they might not be visible on your fork's website?

But in order to solve merge conflicts, I pulled from master, so I should be able to see it right?


Impending loss of default images remote for LXD

According to the outlined timeline in this post, https://images.linuxcontainers.org will phase out server access for LXD by 01/05/24.
Currently the default remote used by bravetools (and LXD) uses this remote for fetching images if no other remote is specified. Base images specified as "public" are also retrieved from this remote. These flows will break once LXD loses access to the images hosted at images.linuxcontainers.org.
Short term fixes
In the short term, bravetools will likely change the default remote to the "ubuntu" remote hosted by Canonical to allow for continued build and deployment of Ubuntu images at least.
For bravetools users that require non-ubuntu images (for example alpine, Debian, centOS) it is recommended to backup images to your local image store while they are still available (until 01/05/24). This can be done using the brave base command (e.g. brave base alpine/3.16) - future builds will retrieve the local image from "~/.bravetools/images".
Future plans
Longer term, it's possible that Canonical may expand the range of images they offer to include other Linux distributions, but no solid plans are known of yet.
It is possible that bravetools may one day expand to include incus support (suggested in https://github.com/bravetools/bravetools/issues/266), but it would take work to support and seems infeasible to complete before the proposed deadline. In addition, all existing users of bravetools are on LXD and we must continue to support those who cannot simply migrate to incus immediately.

As an update, Canonical has deployed their own images server that hosts images from other distributions (including alpine, centOS, Debian etc...). This server is available at https://images.lxd.canonical.com.
To minimise breakages this image server will be used by default for bravetools going forwards. The one downside to this image repository is that it does not ship Ubuntu server images, only Ubuntu desktop images. If you need Ubuntu server images they are available at a different repository: https://cloud-images.ubuntu.com/releases.
You can configure bravetools to use Ubuntu server images since (https://github.com/bravetools/bravetools/pull/272) by editing or adding the config option 'public_image_remote' in ~/.bravetools/config.yml:
public_image_remote: https://cloud-images.ubuntu.com/minimal/releases/

In future we hope to make configuration of the public remote more seamless.


jsonnet: disable insecure cypher suites for prometheus-adapter

Running sslscan against the prometheus adapter secure port reports two
insecure SSL ciphers, ECDHE-RSA-DES-CBC3-SHA and DES-CBC3-SHA.
This commit removes those ciphers from the list.
Signed-off-by: fpetkovski<EMAIL_ADDRESS>

LGTM, thanks @fpetkovski :+1:


Update pytest.ini

This is required for codecov to work: https://github.com/dry-python/returns/blob/master/setup.cfg#L127
Related #16

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@ba87e8d). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #18   +/-   ##
=========================================
  Coverage          ?   32.03%
=========================================
  Files             ?       65
  Lines             ?     4199
  Branches          ?        0
=========================================
  Hits              ?     1345
  Misses            ?     2854
  Partials          ?        0

Continue to review full report at Codecov.

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

I will reopen PR to test coverage message.


window.CONFIG not defined?

Hi There,
Apologies if this is a straightforward question problem:  I am getting an error thrown from loading config.js.  Browser warns me that
"The 'config.js' configuration file has loaded but window.CONFIG is not defined!  Please make sure that it defines a CONFIG variable with proper configuration"
I am a newbie.
I just loaded version 2.3.0 of Tileboard.
I do get the nice green screen but with no writing.
Any help would be much appreciated.

Once you "OK" this error, you should see a notification popup saying more precisely what the error is (possibly a syntax error in the config file).

Thanks for the speedy response.
I have the following error:  uncaught ReferencError: PASSWORD_TYPES is not defined

Line 17/18 look like this:
passwordType: PASSWORD_TYPES.PROMPT_AND_SAVE,
//password: null,

That says it all. There is no PASSWORD_TYPES defined anywhere unless you define it yourself somewhere in the config.js.
None of that code is from the example config so I'm not sure what are you trying to do there.

Apologies - I am also not sure what it is supposed to accomplish.  I was just following along from a youtube video.
https://www.youtube.com/watch?v=nPA1qvHNGl8
In the video, he uses something slightly different (PASSWORD_TYPES.MANUAL) but that throws the same error as above. From the overview section:
serverUrl: "http://<IP_ADDRESS>:8123",
wsUrl: "ws://<IP_ADDRESS>:8123/api/websocket",
passwordType: PASSWORD_TYPES.MANUAL,
password: "HassAPIpass",
I tried taking both lines out, but that doesn't appear to work either - I get an access token error and then (a few seconds later) page goes to 'site cannot be reached.'
Google seems to show that something needs to be put in here, but I'm not really grokking it.
Appreciate your patience.

That's something that was present in old versions of TileBoard but things have changes since then.
Just remove password and passwordType lines and an authentication page should show up where you would input your credentials.

Sorry to bother you again, and it might be that this issue is closed and I have a new one.
I removed both lines as suggested.  and I get the following error 'ACCESS TOKEN  Error while receiving Access Token'.   After a few seconds the screen goes to "this site cannot be reached".
I was thinking that I need a password in my configuration.yaml,  but the documentation appears to suggest not (https://www.home-assistant.io/docs/authentication/providers/)
Thanks for any last hints.

TileBoard redirects to the OAuth HA page when the token is not saved.
The error page says "Check if there is a typo in homeassitant.local" and indeed there is. Missing "s" in homeassitant. Where does that domain come from, I'm not sure. Possibly somewhere in your HA configuration.yaml file.

you solved it.
Lesson for me...get more accurate with typing!
Many thanks for your patience.


Escape HTML tags in error messages on Source Data Information screen

Summary
On the Source Data Information screen, not all parts of error messages returned by the server are properly escaped.
Example
Trying to select a Kilosort directory with an invalid params.py resulted in the following message:

Request Failed
invalid syntax (, line 3)

The actual response from the server was:
{"message": "invalid syntax (<string>, line 3)", "type": "SyntaxError"}

Cause
While angle brackets in text are converted to HTML entities, type is left alone.
https://github.com/NeurodataWithoutBorders/nwb-guide/blob/29599c137dce1b49c9fdcb149c204cc88db7e7cf/src/electron/frontend/core/components/pages/guided-mode/data/GuidedSourceData.js#L123-L130
Fix
Performing the same replacements on type should resolve this.
I have not tested this change, as I don't have an appropriate environment set up right now.

Thanks for catching this and pushing a fix!

I have not tested this change, as I don't have an appropriate environment set up right now.

Please give it a try and let us know (preferable with screenshot of new error to match expectation), since I don't have a version of the data with invalid params myself
The developer installation instructions can be found here: https://nwb-guide.readthedocs.io/en/stable/developer_guide.html#installation

Thanks @dhmjhu for the PR and minimal example! I was able to demonstrate the fix:

@rly Looks like you should generate and set a new token for chromatic

I would propose merging this to a copy of current main (staging) then merging that into main after chromatic checks pass
I've adjusted the target of this PR

Good idea. Let's do that.


build: Build Swift SDK for WebAssembly

This change adds a new product, WasmSwiftSDK, to build the Swift SDK for WebAssembly. The product is built using the swift-sdk-generator package and takes just built WebAssembly stdlib, clang runtime libraries, and wasi-sysroot as input, and produces a Swift SDK artifactbundle under swift-sdk-generator/Bundles.
The main purpose of building SDK on CI is to test WebAssembly target-specific code in SwiftPM like test runner for now

@swift-ci test WebAssembly platform

Hmm, CI is still using Swift 5.8 but swift-sdk-generator requires 5.9. We might need to wait https://github.com/apple/swift-docker/pull/368 or relax minimum version requirement on swift-sdk-generator? CC: @MaxDesiatov

I think lowering the requirement to 5.8 should be possible, I will look into that.

@swift-ci test WebAssembly

@swift-ci test WebAssembly

@swift-ci test WebAssembly

Looks like there's some bug with CI status propagation. A build seems to be running, but its status is not reflected in the list of current PR checks 😞

@swift-ci test WebAssembly

@swift-ci test WebAssembly

@swift-ci test WebAssembly

@swift-ci test WebAssembly

@swift-ci smoke test

@swift-ci smoke test

@swift-ci test WebAssembly

@swift-ci test WebAssembly

@swift-ci smoke test

@swift-ci test WebAssembly

@swift-ci smoke test Linux platform

@swift-ci smoke test

@shahmishal Could you add swift-sdk-generator repository to checkout in CI infrastructure? :pray:

@shahmishal Gentle ping🙏


Ignore empty gx:coord elements in KML files

This pull request changes the KML parser so that empty gx:coord elements are handled. Fixes #12113.

@MoonE just in case you forgot: did you mean to merge this?


Set macro instead of surpressing the warning for third_party/zlib.BUILD.

As described in issue #13188.

Can one of the admins verify this patch?

I just signed the CLA.

@aselle please review
Jenkins, test this please.


Improvement Use error code when disk exceed capacity limit

Proposed changes
Using error codes can obtain clearer error information.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run p0


Describe errors that are to be "expected"

We sort of have the (unwritten?) alignment that error codes/reasons should be "aligned to VISS", we should document which errors are to be expected in the kuksa.val.v1 API under which conditions on the individual API calls
Should likely be markup in this repo, or - if there is some standard for that - could be documented inside the proto files

Related: #560

Can be integrated with https://github.com/eclipse/kuksa.val/pull/390

I created a wiki-page to describe current status at https://github.com/eclipse/kuksa.val/wiki/KUKSA.val-gRPC-interfaces. I suggest we first document current status on wiki, then we can decide what changes that are needed in the short term so that we create "real" documentation first when the obvious gaps have been fixed

@erikbosch I have read the wiki page you have created and I believe it is a good start. I have some comments/questions but I am not sure where/how to post them. Do you want me to fork the wiki repo and create a PR? Or would you rather have me cite the corresponding sections here in this issue?

I assume you do not have access to edit it, otherwise an option could be to add discussion points directly in it. Forking/copying it and highlight problems or proposed changes and reference that from this issue could possibly be an idea.

Error handling (currently)
Get and Set RPCs rely on {Get,Set}Response protobuf message fields to communicate errors i.e.:
repeated DataEntryError errors = 2;
Error error                    = 3;
This means the caller of either Get or Set needs to check those two fields to decide if there is an error or not. It is easy to miss for someone who would want to implement Get or Set and could lead to hidden errors. The nice thing about them though is that they provide detailed errors (one per data entry).
Subscribe and GetServerInfo don't have such error fields in their respective *Response protobuf messages. Instead, errors if any will result in an exception being raised (e.g. grpc.aio.AioRpcError in python's case) and that already comes without further efforts with protoc-generated code.
In some cases though, Get and Set might still raise grpc.aio.AioRpcError e.g. because of network errors. This means the client needs to handle both grpc.aio.AioRpcError errors and response-message-based errors.

It is unclear (i.e. unspecified) under which circumstances, which of the error fields (global or per Data Entry) will actually be used. In fact, I have not yet experienced a situation where the global error was set ...
One more fundamental issue I see with being able to e.g. update multiple Data Entries in one call, is that it is unclear (i.e. unspecified) what happens if a subset of the Data Entries could be updated, but the others could not, e.g. due to wrong data type being used. Would this result in no entries being updated at all?
It also feels a little odd that, with this approach, the invocation seemed to have succeeded, but then you still need to inspect the error fields. Which, BTW, is a PITA because it means iterating through the whole data structure in order to determine if any of the Data Entry level error fields is set.
So, FMPOV the most important thing would be to actually properly document the error behavior of the gRPC API, because currently, it is basically a guessing/trial-and-error game ...
Apart from that, using the (extended) error info in the Status object makes more sense to me than encapsulating the error info in the response message(s).

We are about to archive this repo soon. If you consider this issue as important please file a new issue at one of the new Kuksa repos at https://github.com/eclipse-kuksa


Integrate with GitHub's Checks API

https://blog.github.com/2018-05-07-introducing-checks-api/

This would be awesome. I've not worked with the checks API, but happy to help if you know how you want it to work.

Hi Danny! Thanks for your interest in contributing to this gem 🙃
The idea I had for Checks support involves integrating this gem with pronto. pronto already supports various Formatters that can comment on pull requests (among other useful integrations). Implementing checks should be a matter of extending the current formatter interface.
Wrapping up:

pronto-undercover will run this gem within pronto run. That's on my to-do list.
new formatter like GithubCheckFormatter < GithubFormatter could post results to the Checks API using credentials from https://github.com/prontolabs/pronto/blob/d34be4f69bce0941337b4d5917a6211a5b0712b1/lib/pronto/github.rb#L82-L87

I hope this will give you some starting points if you decide to look at pronto-undercover. I have done some initial research but didn't get past initial gem setup in development terms. I am open to discussion about this approach or any other you may have.

Thought I'd drop a note here to say that I never got round to this and am not likely to do so in the foreseeable.

@dannysmith I've been recently working on a Checks api integration for undercover in a different repo


intrinsicContentSize is not updated if the numberOfPages is changed

I use it in a cell and the component width is not updated when I update the numberOfPages.
The result being that the dots are not centered in the view anymore.
An easy fix is to force the intrinsicContentSize to be updated and call https://developer.apple.com/documentation/uikit/uiview/1622457-invalidateintrinsiccontentsize

Thank you for your information!

As we updated in 1.0.8, please use that.

ok, I will !

It's working well now!
Thank you Shima-san


Echelon auto restake not working

please fix for the stuck echelon auto compound feature

Hey is there a specific error you're receiving for Echelon?

Hey @tombeynon,
I tested now.
The problem is probably that unable to auto gas adjustment.
Failed to broadcast: Error when broadcasting tx 61F8176AF4639CD12F81EE1EE202075BC9F4BCA67E7ADE4E2EA450E87201ACDF at height 0. Code: 13; Raw log: insufficient fees; got: 2835aechelon required:<PHONE_NUMBER>00000aechelon: insufficient fee


[lit-html] Port until() to lit-html 2.0

We're going to need until() to upgrade Google. The question here is the API around setting a part value for attribute parts. The directive will need an index/offset to represent the expression it's targeting in multi-value attribute bindings.
We'll need a helper like:
setPartValue(part, value, this.index)

Where index is passed to the directive's constructor.

For a bit more detail, I think we can update setPartValue to something like so:
https://github.com/Polymer/lit-html/blob/lit-next/packages/lit-html/src/parts.ts#L68
export const setPartValue = (part: Part, value: unknown, index? number) => {
  if ((part as AttributePart).strings !== undefined) {
    // multi-valued part
    if (i === undefined) {
      throw new Error(...);
    }
    const newValues = [...part._value];
    newValue[index] = value;
    (part as AttributePart)._setValue(newValue, 0);
    (part as AttributePart)._setValue(values, index);
  } else {
    // single-valued part
    (part as NodePart)._setValue(values);
  }
  return part;
};

That check for if ((part as AttributePart).strings !== undefined) { matches what TemplateInstance does: https://github.com/Polymer/lit-html/blob/lit-next/packages/lit-html/src/lit-html.ts#L655


[Blob Service] GetBlockList Support in storage SDK

https://docs.microsoft.com/en-us/rest/api/storageservices/get-block-list

https://github.com/Azure/azure-sdk-for-cpp/pull/144


still mantained?

The litecore.io url redirects to bitcore.

Please check out https://insight.litecore.io/

I know about that but I got cloudflare errors yesterday


Plugin is very slow and sometimes fails to work with large SVG documents

It seems that plugin works extremely slow, or most of the time causes browser to crash or ask user to stop a very slow running script, when SVG documents is bigger than 6MB or so. Hard to say what can cause this, as it won't slow down gradually, but instead will work just fine with 6MB files, but then suddenly stop with a little bit larger ones.
Here is the link for sample SVG that fails:  Large SVG Document.svg

The link you provided doesn't work. This is a correct one.
Did you try using the same file but without this library? Most probably this is not the library issue but a browser limitation.

Yes I did and it loads just fine into all the browsers. More it works if used with [jquery.panzoom] (https://github.com/timmywil/jquery.panzoom) plugin as well.

Same as #146


Multicast UDP packets send/receive fails in loopback

Environment
Windows build number: 18363
Your Distribution version: Ubuntu 20.04
WSL 1

Steps to reproduce

using python socket library, if  we try to receive any UDP multicast packet using the following function
setsockopt(socket.IPPROTO_IP, socket.IP_DROP_MEMBERSHIP, mreq)
Expected behavior
UDP packet should be received in the receiver process.

Actual behavior
Python program ends with the following error
OSError: [Errno 92] Protocol not available

Closing as it may be related to #4604