[Admin] Revise API reference intro pages.

This PR introduces the following changes into the kb-host-centric-toc branch:

Revises API overview intro pages for Excel, Word, and OneNote.
Adds new API overview intro pages for PowerPoint and Project (and deletes the page that used to be shared by those hosts).
Updates the 'programming overview' article for OneNote, to add info about requirement sets.
Adds a new 'fundamental programming concepts' article for Word (containing content that used to exist in the Word API ref intro page). Please note that this content was moved into this new article pretty much as-is; it's not perfect, but updating this content is beyond the scope of this current initiative; there's already a VSO work item tracking the need to update this content soon.

It also does some miscellaneous clean-up such as:

Removes https://docs.microsoft.com prefix from URLs throughout the docs.
Updates the value of the displayName attribute in the TOC to remove Visio from all 'common' nodes.

Docs Build status updates of commit 12ca822:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/concepts/privacy-and-security.md
:white_check_mark:Succeeded

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded

docs/develop/bind-to-regions-in-a-document-or-spreadsheet.md
:white_check_mark:Succeeded

docs/develop/localization.md
:white_check_mark:Succeeded

docs/develop/troubleshoot-sso-in-office-add-ins.md
:white_check_mark:Succeeded

docs/excel/custom-functions-troubleshooting.md
:white_check_mark:Succeeded

docs/excel/excel-add-ins-advanced-concepts.md
:white_check_mark:Succeeded

docs/onenote/onenote-add-ins-programming-overview.md
:white_check_mark:Succeeded

docs/powerpoint/index.md
:white_check_mark:Succeeded

docs/project/index.md
:white_check_mark:Succeeded

docs/publish/publish-task-pane-and-content-add-ins-to-an-add-in-catalog.md
:white_check_mark:Succeeded

docs/publish/publish.md
:white_check_mark:Succeeded

docs/reference/javascript-api-for-office.md
:white_check_mark:Succeeded

docs/reference/overview/excel-add-ins-reference-overview.md
:white_check_mark:Succeeded

docs/reference/overview/onenote-add-ins-javascript-reference.md
:white_check_mark:Succeeded

docs/reference/overview/powerpoint-add-ins-reference-overview.md
:white_check_mark:Succeeded

docs/reference/overview/project-add-ins-reference-overview.md
:white_check_mark:Succeeded

docs/reference/overview/word-add-ins-reference-overview.md
:white_check_mark:Succeeded

docs/reference/requirement-sets/powerpoint-and-project-note.md
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

docs/word/word-add-ins-core-concepts.md
:white_check_mark:Succeeded

docs/word/word-add-ins-programming-overview.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 79602c3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/concepts/privacy-and-security.md
:white_check_mark:Succeeded

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded

docs/develop/bind-to-regions-in-a-document-or-spreadsheet.md
:white_check_mark:Succeeded

docs/develop/localization.md
:white_check_mark:Succeeded

docs/develop/troubleshoot-sso-in-office-add-ins.md
:white_check_mark:Succeeded

docs/excel/custom-functions-troubleshooting.md
:white_check_mark:Succeeded

docs/excel/excel-add-ins-advanced-concepts.md
:white_check_mark:Succeeded

docs/excel/excel-add-ins-overview.md
:white_check_mark:Succeeded

docs/onenote/onenote-add-ins-programming-overview.md
:white_check_mark:Succeeded

docs/overview/explore-with-script-lab.md
:white_check_mark:Succeeded

docs/powerpoint/index.md
:white_check_mark:Succeeded

docs/project/index.md
:white_check_mark:Succeeded

docs/publish/publish-task-pane-and-content-add-ins-to-an-add-in-catalog.md
:white_check_mark:Succeeded

docs/publish/publish.md
:white_check_mark:Succeeded

docs/reference/javascript-api-for-office.md
:white_check_mark:Succeeded

docs/reference/overview/excel-add-ins-reference-overview.md
:white_check_mark:Succeeded

docs/reference/overview/onenote-add-ins-javascript-reference.md
:white_check_mark:Succeeded

docs/reference/overview/powerpoint-add-ins-reference-overview.md
:white_check_mark:Succeeded

docs/reference/overview/project-add-ins-reference-overview.md
:white_check_mark:Succeeded

docs/reference/overview/word-add-ins-reference-overview.md
:white_check_mark:Succeeded

docs/reference/requirement-sets/powerpoint-and-project-note.md
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

docs/word/word-add-ins-core-concepts.md
:white_check_mark:Succeeded

docs/word/word-add-ins-programming-overview.md
:white_check_mark:Succeeded

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

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

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/concepts/privacy-and-security.md
:white_check_mark:Succeeded

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded

docs/develop/bind-to-regions-in-a-document-or-spreadsheet.md
:white_check_mark:Succeeded

docs/develop/localization.md
:white_check_mark:Succeeded

docs/develop/troubleshoot-sso-in-office-add-ins.md
:white_check_mark:Succeeded

docs/excel/custom-functions-troubleshooting.md
:white_check_mark:Succeeded

docs/excel/excel-add-ins-advanced-concepts.md
:white_check_mark:Succeeded

docs/excel/excel-add-ins-overview.md
:white_check_mark:Succeeded

docs/onenote/onenote-add-ins-programming-overview.md
:white_check_mark:Succeeded

docs/overview/explore-with-script-lab.md
:white_check_mark:Succeeded

docs/powerpoint/index.md
:white_check_mark:Succeeded

docs/project/index.md
:white_check_mark:Succeeded

docs/publish/publish-task-pane-and-content-add-ins-to-an-add-in-catalog.md
:white_check_mark:Succeeded

docs/publish/publish.md
:white_check_mark:Succeeded

docs/reference/javascript-api-for-office.md
:white_check_mark:Succeeded

docs/reference/overview/excel-add-ins-reference-overview.md
:white_check_mark:Succeeded

docs/reference/overview/onenote-add-ins-javascript-reference.md
:white_check_mark:Succeeded

docs/reference/overview/powerpoint-add-ins-reference-overview.md
:white_check_mark:Succeeded

docs/reference/overview/project-add-ins-reference-overview.md
:white_check_mark:Succeeded

docs/reference/overview/word-add-ins-reference-overview.md
:white_check_mark:Succeeded

docs/reference/requirement-sets/powerpoint-and-project-note.md
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

docs/word/word-add-ins-core-concepts.md
:white_check_mark:Succeeded

docs/word/word-add-ins-programming-overview.md
:white_check_mark:Succeeded

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

@AlexJerabek thanks for the review and awesome feedback!
I incorp'd nearly all of your feedback. The one thing I left alone (for now) is that I didn't merge the "Try out code samples with Script Lab" section in each API ref intro page with the "get hand-on experience with the APIs by completing a tutorial" sentence from the "Learn about API capabilities" section. My main rationale for leaving this content organization as-is is that content in the "Learn about API capabilities" section (where the "get hands-on experience with a tutorial" sentence lives) is about how they can use the docs to learn about API capabilities, where as running samples in Script Lab takes place beyond the scope of the docs (it's another type of learning activity altogether). We can certainly revisit this down the road if need be.
FYI, I've also just the Next Steps section in the "Script Lab" article (as we discussed doing the other day), to add a sentence about installing Script Lab in Excel, Word, or PowerPoint.
Thanks again for the great feedback (and for the prompt review as well); I always appreciate the insight you bring to the table.


Fix ls not following links to directories by default

Fixes #733 by specifically checking if the stat'ed file is a symlink and that the linked file is a directory.

Codecov Report

Merging #764 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #764      +/-   ##
==========================================
+ Coverage   97.38%   97.39%   +0.01%
==========================================
  Files          33       33
  Lines        1222     1227       +5
==========================================
+ Hits         1190     1195       +5
  Misses         32       32

Impacted Files
Coverage Δ

src/ls.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Add tests and fix uncovered issues.

Fixes #24

Coverage increased (+30.3%) to 90.179% when pulling 2e93ecf709699a4188dfbfaad32ce04caa89cf19 on dangle:tests-and-fixes into df8c43fc90bab48fe7ee53eb3d7cfd13ad901b94 on containenv:development.

Coverage increased (+30.3%) to 90.179% when pulling 2e93ecf709699a4188dfbfaad32ce04caa89cf19 on dangle:tests-and-fixes into df8c43fc90bab48fe7ee53eb3d7cfd13ad901b94 on containenv:development.


chore(*): Restoring the 4th digit of the Kong EE version

We made the decision to support 4 digits in Kong EE (<IP_ADDRESS>) until
we finish the Unified Data Plane work. I have tested these changes
locally.
Codependent with https://github.com/Kong/kong-ee/pull/3431
Signed-off-by: Tyler Ball<EMAIL_ADDRESS>

test using the kong-ee branch here: https://internal.builds.konghq.com/blue/organizations/jenkins/kong-build-tools/detail/PR-519/2/pipeline

I tested locally, and things will pass when we builing with the appropriate OSS and EE PRs:
OSS: https://github.com/Kong/kong/pull/9002
EE: https://github.com/Kong/kong-ee/pull/3431
Let's squash&merge this one, then I will bump KBT in the above PR and merge them.


Build failure: ceph (on staging)

Ceph pins an old cryptography for arcane reasons; the rest of the ecosystem has moved beyond it which is causing this failure on staging after the latest batch of Python updates:
┃             ┌─ ⚠ python3.11-trustme-1.2.0 failed with exit code 1 after ⏱ 9s in pytestCheckPhase
┃          ┌─ ⏸ python3.11-requests-toolbelt-1.0.0
┃       ┌─ ⏸ python3.11-cheroot-10.0.1
┃    ┌─ ⏸ python3.11-cherrypy-18.10.0
┃ ┌─ ⏸ python3-3.11.10-env
┃ ⏸ ceph-19.2.0

A trustme test fails because it is calling cryptography methods that are not present in the version Ceph pins. It looks like it’s a convenience library for writing tests, so it’s possible that the fix will be as simple as turning off tests in requests-toolbelt.
cc @nh2

Linking related previous PR here that introduces the pinning of cryptography:

https://github.com/NixOS/nixpkgs/pull/334286

Going to maybe look into this tomorrow, but @nh2 do you think it might be a good idea to ping https://tracker.ceph.com/issues/64213 again as it’s been a few months?

This is present in 24.11 - and unstable, which seems to hit cryptography as described in the OP.

I took a stab at this, and quickly got out of my depth. I put together a draft PR here: https://github.com/NixOS/nixpkgs/pull/369622. Perhaps it's a useful starting point for someone.

This is present in 24.11 - and unstable, which seems to hit cryptography as described in the OP.

Interestingly, it doesn't seem present in 24.11 now - can others confirm? In unstable, I'm still hitting the cryptography build error.

Interestingly, it doesn't seem present in 24.11 now - can others confirm?

Yeah, I'm able to substitute ceph directly from cache.nixos.org when I run nix build nixpkgs/nixos-24.11#ceph.

For the record, once we get past the Python issue described here (which will be addressed by https://github.com/NixOS/nixpkgs/pull/369622), we're going to hit a C++ compilation issue. I've filed https://github.com/NixOS/nixpkgs/issues/369777 to track that.


import Debug

Hi Darryl,
I played around with your compilers since I am currently much interested in compiler design of strongly typed languages. Thx for your work! Two minor things:

I wondered that you have in some REPL.hs files "import Debug" which didn't compile for me. Commenting it out works.
Did you try megaparsec before? It seems to be a better maintained version of parsec.

Best,
Daniel

thanks for letting me know about this! I should've removed this before pushing to github :)
as for megaparsec, no, havent tried it at all, ill have to give it a look


Remove auto-generated Angular "it should create an instance" tests

As mentioned by @dominikmessner in PR #1993, we could remove the auto generated "it should create an instance" tests:
https://github.com/keptn/keptn/pull/1993/files/8b3a047f610b7fec94f2806189f58453cf0efafa#r449132239

As this affects not only the PR, but a whole lot of lines of code in our Angular app, I'd like this to be done in a separate issue. But before we go this way, can anyone provide some more details whether these auto generated tests have any value and how big the impact on removing them would be?

In our internal project, we removed all these tests and could speed up the test execution by 10%. I quickly had a look at a few Angular projects, the ones that I looked at don't have these default tests:

Angular
Material
Barista

I think as soon as there is a proper test for a component, the instance creation will be tested implicitly anyways, that's why it's probably ok to remove them.


Create order should return an object serialized to JSON

Description
Currently the order id is returned as a string from the post endpoint.
It should be returned as a json object.
Tasks

[x] Create return model
[x] Update controller ouput
[x] Update tests
[x] QA
[ ] Update APIM swaggr and docs

Acceptance criteria

[x] Return object from orders POST should be a json object

Verified return object
{
    "orderId": "7898e81a-db9f-4d76-9ec9-c25fa8b4a132"
}


Query program name programmatically

Lacking the traditional int argc, char **argv entrypoint parameters for querying command line arguments, could program.h provide another way to obtain the name of the program? This is often useful for displaying accurate help command syntax for downstream users.

I think the answer to this question is somewhat similar to my response to https://github.com/NuxiNL/cloudabi-utils/issues/11. Something like this could be built on top of what's there already. The argdata could be used to communicate this information to the process.
Let's close this issue to keep the discussion centralized.


Updating an existing item changes the layout of field

Your environment

SDK Version: v1.1.0

Connect Server Version: Docker image 1password/connect-sync@sha256:ea4ee8de21de22edcf35b4218fe4ce0c18f3806b7e3b259e5a7e0f98065fed45, created around 2021-05-20

OS: Ubuntu 20.04

Python Version: 3.8
What happened?

We created a default password item in a vault, here's the initial structure:
{
  "id": "6go6qftma5enrxxxxxxxx",
  "title": "AWS_ACCESS_KEY_ID",
  "version": 1,
  "vault": { "id": "akvk5ifqsjge7xxxxxxxxx" },
  "category": "PASSWORD",
  "sections": [{ "id": "linked items", "label": "Related Items" }],
  "fields": [
    {
      "id": "password",
      "type": "CONCEALED",
      "purpose": "PASSWORD",
      "label": "password",
      "value": "xxxxxxxxxxxxxxxxxx"
    },
    {
      "id": "notesPlain",
      "type": "STRING",
      "purpose": "NOTES",
      "label": "notesPlain"
    }
  ],
  "lastEditedBy": "xxxxxxxxxxxxx",
  "createdAt": "2022-01-17T23:41:32Z",
  "updatedAt": "2022-01-17T23:41:32Z"
}

Then, we used the API to update the password
    # Update 1Password item
    item = Item(
        vault=ItemVault(id=op_vault),
        id=op_uuid_access_key,
        sections=[{ "id": "linked items", "label": "Related Items" }],
        fields=[
            Field(
                id="password",
                type="CONCEALED",
                label="password",
                value=response["AccessKey"]["AccessKeyId"],
            )
        ],
    )
    op_client.update_item(op_uuid_access_key, op_vault, item)

However, instead of modifying the first element in the fields area, the Python SDK adds a new one to the bottom, like this"
{
  "id": "6go6qftma5enrxxxxxxxx",
  "title": "AWS_ACCESS_KEY_ID",
  "version": 2,
  "vault": { "id": "akvk5ifqsjge7xxxxxxxxx" },
  "category": "PASSWORD",
  "sections": [{ "id": "linked items", "label": "Related Items" }],
  "fields": [
    {
      "id": "password",
      "type": "CONCEALED",
      "purpose": "PASSWORD",
      "label": "password"
    },
    {
      "id": "notesPlain",
      "type": "STRING",
      "purpose": "NOTES",
      "label": "notesPlain"
    },
    {
      "id": "password",
      "type": "CONCEALED",
      "label": "password",
      "value": "xxxxxxxxxxxxxxxxxxxxxxxxx"
    }
  ],
  "lastEditedBy": "xxxxxxxxxxxxx",
  "createdAt": "2022-01-17T23:41:32Z",
  "updatedAt": "2022-01-17T23:41:32Z"
}

What did you expect to happen?

The SDK should modify the existing one.
Steps to reproduce

Create a normal Password item
Save its original structure
Use the scripts above to edit it
Compare the updated structure

Notes & Logs

Thanks @edif2008 - this solved my problem.
In case someone else has the same requirement as me. Here is my slightly different code snippet which updates username, password and creates a new field:
item = onepasswordconnectsdk.models.Item(
vault=ItemVault(id=vaultId),
id=itemId,
category='LOGIN',
fields=[
Field(
id='username', #standard field
label='username',
purpose='USERNAME',
value="username"),
Field(
id='password', #standard field
label='password',
purpose='PASSWORD',
value="pass"),
Field(
label="token", #new field
value="123")
],
)
client.update_item(itemId, vaultId, item)
I think this should be added to the documentation.
Thank you

Heey @jessewindebank1809,
Glad to hear that the suggestion worked for you. Thank you for sharing the snippet that will address your use case so that others will see it as well.
I really appreciate you suggesting to add this in the documentation. We will add it as part of examples for using the sdk.


Danger doesn't pickup on renaming files

Report
What did you do?
Renamed a file in PR
bundle exec danger
What did you expect to happen?
Danger to work as usual
What happened instead?
We renamed the file Connection.swift to ConnectionState.swift in our PR but danger still tried to open the old one.
error opening input file '/Users/runner/runners/2.168.0/work/stream-chat-swift/stream-chat-swift/Sources/Client/WebSocket/Connection.swift' (No such file or directory)
8
Most rules will be skipped because sourcekitd has failed.
9
Fatal error: 'try!' expression unexpectedly raised an error: Error Domain=NSCocoaErrorDomain Code=260 "The file “Connection.swift” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/Users/runner/runners/2.168.0/work/stream-chat-swift/stream-chat-swift/Sources/Client/WebSocket/Connection.swift, NSUnderlyingError=0x7feda372eb60 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}: file /Users/jsimard/Projects/SwiftLint/.build/checkouts/SourceKitten/Source/SourceKittenFramework/File.swift, line 28
10

11
Danger has failed this build.
12
Found 1 error.

Your Environment
https://github.com/GetStream/stream-chat-swift/runs/585535427?check_suite_focus=true

Which CI are you running on?
Github Actions

Are you running the latest version of Danger?
6.2.2

What is your Dangerfile?
https://github.com/GetStream/stream-chat-swift/blob/master/Dangerfile

@b-onc I get around this by doing public_files = (git.modified_files + git.added_files)

I have a similar issue, using git.diff.each do |file| ... .
Unfortunately, with this approach, there is no way to obtain the new name of the file, and AFAIS this issue comes from the underlying library. And taking into account the absence of the activity recent time there, not sure if this will be fixed any soon-ish...

I have a similar issue, using (git.modified_files + git.added_files - %w[PreTestDangerfile]).each do |file|.
Any suggestions on how to solve this problem?
I'm using Danger 9.3.0.


DefaultClusterRenderer - allow custom text appearance

Is your feature request related to a problem? Please describe.
I want to be able to customise the text appearance of the cluster marker, without having to implement/use my own IconGenerator. Similar to how I can customise the cluster color. Specifically, I want to be able to set the text color which sits on top of my color, in order to ensure I meet the required contrast for accessibility standards.
Describe the solution you'd like
Expose a protected function in DefaultClusterRenderer which allows overriding the text appearance value. Something like:
@StyleRes
protected int getClusterTextAppearance(int clusterSize) {
    return R.style.amu_ClusterIcon_TextAppearance; // Default value
}

This would allow the same level of customisation as the cluster color, by overriding this function and providing your own style.
getColor included for reference:
protected int getColor(int clusterSize) {
    // ...
    return Color.HSVToColor(new float[]{
            hue, 1f, .6f
    });
}

Then setting the textAppearance of the built in IconGenerator as part of getDescriptorForCluster, e.g.:
@NonNull
protected BitmapDescriptor getDescriptorForCluster(@NonNull Cluster<T> cluster) {
    int bucket = getBucket(cluster);
    BitmapDescriptor descriptor = mIcons.get(bucket);
    if (descriptor == null) {
        mColoredCircleBackground.getPaint().setColor(getColor(bucket));
        mIconGenerator.setTextAppearance(getClusterTextAppearance(bucket));
        descriptor = BitmapDescriptorFactory.fromBitmap(mIconGenerator.makeIcon(getClusterText(bucket)));
        mIcons.put(bucket, descriptor);
    }
    return descriptor;
}

Considerations with this approach:

Does setTextAppearance have a performance overhead if setting for every getDescriptorForCluster? As far as I can tell it doesn't, but I don't know if you have some benchmark tests or anything which could validate that?

Describe alternatives you've considered
To customise the text appearance now, you have to:

Create your own IconGenerator, configuring the content view
Override onBeforeClusterRendered and onClusterUpdated, replicating various code which has already been written within DefaultClusterRenderer`

An example of this is already provided in CustomMarkerClusteringDemoActivity.
This does work for my use case, but it feels very heavy considering how easy it is to just override color.
Additional context
While trying to work this out, I put a PR together ready which I am happy to submit if agreed.
Look forward to hearing some thoughts on this

I still think this is valid.


new debug logging omits keys starting with underscore

When payload is a structured (and perhaps other msg properties) object that contains keys starting with _ then the debug tab omits them with displaying the object.
raw json sent
{"params": ["WikiStart"], "_method": "wiki.getPage", "id": 123}

debug tab message (copy/pasted)
msg.payload : Object
object
params: array[1]
0: "WikiStart"
id: 123

I'm certain the messages are being passed through correctly with the properties there, it's just a debug tab issue.

This was done on purpose in the early stages of developing the new debug view - the msg.req/res objects emitted by the HTTP In node are huge and contain lots of 'internal' properties that start with a _.  Filtering these properties had a huge performance impact - but I did intend to revisit it before release. Thanks for bringing it up.

maybe an option in debug - "show hidden properties" ? (like many file explorers)

No need - can largely remove the filter as there were lots of other performance improvements made along the way - for example, we don't build the full message - we only build each 'level' as you expand it. That solved the main issue the _ properties caused.

@knolleary yeah, that sounds sane.  Looking forward to the update!


plz help me! this error is occur when i am  creating a new project or building an existing project in vs code

Oops; flutter has exited unexpectedly: "FileSystemException: Creation failed, path =
'G:\flutter\bangla\flutter\bin\cache\downloads\storage.googleapis.com\flutter_infra\flutter@lt@@lt@@lt@@lt@@lt@@lt@@lt@ HEAD
9d5b21729ff53dbf8eadd8bc97e0e30d77abec95
75bef9f6c8ac2ed4e1e04cdfcd88b177d9f1850d
@gt@@gt@@gt@@gt@@gt@@gt@@gt@ f30b7f4db93ee747cd727df747941a28ead25ff5' (OS Error: The system cannot find the path specified.
, errno = 3)".
A crash report has been written to C:\Users\Mahim\Desktop\test\flutter_01.log.

Hey @mahimtk2 can you please attach the file at C:\Users\Mahim\Desktop\test\flutter_01.log
Thank you


Add license information

This adds basic license info to fix #75.
This repo was lifted out of code that used to be in the main rust-lang/rust repo.  My assumption that the intent was to continue to release this code under the same licenses.

r? @nikomatsakis
(rust_highfive has picked a reviewer for you, use r? to override)

https://github.com/rust-lang/rust.vim/issues/45#issuecomment-156776738 confirms that the extension was initially developed under the dual license.
@nikomatsakis @pnkfelix @huonw highfive thinks you're the eligible reviewers on this repo; is there any reason against just merging this?

@edunham I agree, lets merge


Re-enable System.define test

My apologies @matthewp, but somewhere in the last work, unrelated changes have caused this to stop working.
It is an unstable feature that hasn't been designed into the pipeline very well. I'm happy to take fixes through PRs, but don't have the time personally to debug this right now for this release.
Note that this feature will be better supported in the upcoming loader changes.

Ok, I'll fix this the next time I pull down es6ml (probably in a couple of weeks or so).

Sure thanks for understanding.
On Tue, 24 Mar 2015 at 2:15 AM Matthew Phillips<EMAIL_ADDRESS>wrote:

Ok, I'll fix this the next time I pull down es6ml (probably in a couple of
weeks or so).
--
Reply to this email directly or view it on GitHub
https://github.com/ModuleLoader/es6-module-loader/issues/333#issuecomment-85256389
.

So is the only way to run this test now in Node?

I'm a little confused, the tests are duplicated, one written in mocha for Node and the old custom test runner for the browser.  Why?  Also, the browser version of this test passes. So it's only Node for some reason.

Ok sure - if it's just not running in Node then we can just add a skip for the test in Node if you're happy with that.
The manual tests there are the old tests which are being phased out but still in use right now.

How do we run the mocha tests in the browser?

@guybedford can we run the mocha tests in the browser?

Yes, with karma --start. See https://github.com/ModuleLoader/es6-module-loader#testing.

Is there not a way to open an html page to see a test? Karma seems great for automation but not for debugging.

Can you reopen this, I was mistaken before, it's not working. Looking into why now.  I'm guessing this is the breaking commit: https://github.com/ModuleLoader/es6-module-loader/commit/c309e1126cd9cc5183e41a5c3109250b1039d48e

I have a fix for the issue, but it doesn't fix the test for some reason.  Will submit a PR when I get that passing again.


Rancher with external db on azure

Does anyone have experience with a rancher ha setup on azure? We could not get past the initializing rancher server docker command. Problem seems to be the clear db (third party provider on azure) mysql database as the tables are created but nothing inserted (every time a different error in the docker logs).
Unfortunately sql server, which is the only managed database on azure, is not supported.
Workaround right now is that we let our rancher ha servers in aws manage the gateway and service instances in azure which is no long term solution.
So does anyone managed to setup a complete rancher ha environment on azure and if yes how?

#5754


Error While Uploading Scan Results

While uploading nessus scan results, HTTP 500 error code is given. Here is the details:

Request Method:
POST

http://<IP_ADDRESS>:8000/test/14/re_import_scan_results

1.11.4

DoesNotExist

System_Settings matching query does not exist.

/usr/lib/python2.7/site-packages/django/db/models/query.py in get, line 380

/usr/bin/python

2.7.5

['/root/Desktop/django-DefectDojo',  '/usr/lib64/python27.zip',  '/usr/lib64/python2.7',  '/usr/lib64/python2.7/plat-linux2',  '/usr/lib64/python2.7/lib-tk',  '/usr/lib64/python2.7/lib-old',  '/usr/lib64/python2.7/lib-dynload',  '/usr/lib64/python2.7/site-packages',  '/usr/lib64/python2.7/site-packages/gtk-2.0',  '/usr/lib/python2.7/site-packages',  '/root/Desktop/django-DefectDojo']

Wed, 9 Aug 2017 03:37:47 -0500

To reproduce the error, upload any .nessus file.

Hi @asdf344 I've fixed this issue with my last PR. Please feel free to reopen if it is not fixed after performing a git pull


Script fix required

[Enter feedback here]
The example script:
Create a new batch
$batch = New-PnPBatch
Add files to classify to the batch
foreach ($listItem in $targetItems) {
Request-PnPSyntexClassifyAndExtract -FileUrl $listItem.FileRef -Batch $classifyBatch
}
Execute batch
Invoke-PnPBatch -Batch $batch
Two issues:

$batch was created, but it was referenced as  $classifyBatch later which is undefined
$listItem.FileRef  could contain whitespaces, so could be improved as: "$($listItem.FileRef)"

Should be fixed as:
Create a new batch
$batch = New-PnPBatch
Add files to classify to the batch
foreach ($listItem in $targetItems) {
Request-PnPSyntexClassifyAndExtract -FileUrl "$($listItem.FileRef)" -Batch $batch
}
Execute batch
Invoke-PnPBatch -Batch $batch

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

ID: 92b31af4-e9f0-a198-1b0c-68f56c9c7e89
Version Independent ID: 92b31af4-e9f0-a198-1b0c-68f56c9c7e89
Content: Use PowerShell to request processing by a custom model - Microsoft Syntex
Content Source: microsoft-365/syntex/powershell-syntex-processing.md
Service: microsoft-syntex
GitHub Login: @jameseccles
Microsoft Alias: jaeccles

@qishengc Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/13174
Once the author approves, the changes will be live.
Thanks
Sri


Rewritten server_status.py

Great! Much cleaner and easier to understand than before. Great work @geotheory


#1005 Get Started update of  trt variables (ARM,ACTARM) in mutate sta…

…tement
Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel branch until you have checked off each task.

[x] Code is formatted according to the tidyverse style guide
[ ] Updated relevant unit tests or have written new unit tests - See Unit Test Guide
[ ] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[ ] Update to all relevant roxygen headers and examples
[ ] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[ ] Address any updates needed for vignettes and/or templates
[ ] Update NEWS.md
[ ] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[ ] Address or fix all lintr warnings and errors - lintr::lint_package()
[ ] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue so that it closes after successful merging.
[ ] Address all merge conflicts and resolve appropriately
[x] Pat yourself on the back for a job well done!  Much love to your accomplishment!

Umm...I would think this would not be mergeable without the task lists being all checked off.  I realize they are not all relevant to this issue.  @thomas-neitmann
Also the reviewer is supposed to merge the branch in and not the developer.  @raqpau

The task list was not required, at least it was not showing here as required. I initially marked only 1 task as done, but then I returned to add some, like: "Pat yourself on the back for a job well done! Much love to your accomplishment!" :)
The other tasks I was not finding relevant. I see that I can even edit the tasks as done/not done now, not sure if it matters
This was my first issue and I wanted to test how all works in here. I was really feeling something will explode while working on it - sorry for that merge, I see it is described in the developers guide it is reviewer task
BR, Paulina

Umm...interesting.  We will need to investigate.
Thanks for doing this PR.  The tasks are meant to be helpful reminders as you work on a more complicated issue - this one was pretty simple.
In the future, the expectation is for you to go through each task and check off in acknowledgment that you have had done your due diligence.  :)
Not sure if we have interacted, but welcome to admiral!!


Unable to display Dark theme on Linux

I'm trying to add Dark mode on Linux.
<Application.Styles>
    <sty:FluentAvaloniaTheme PreferSystemTheme="False" RequestedTheme="Dark" />

It always displays Light theme. Running it in Windows displays Dark theme.
The sample projects do work in Dark mode, not sure where the difference is.
Desktop/Platform (please complete the following information):

OS: Garuda Linux
FluentAvalonia Version: latest
Avalonia Version: 0.10.17

In the code-behind, "RequestedTheme" remains "Light" and is thus ignored from App.axaml on Linux. Setting RequestedTheme from the code-behind then works to switch the theme.


The QR code has expired

Could you please update it? Thanks!

updated

Could you please update it? Thanks!

updated


bug: completion in input

Did you check docs and existing issues?

[X] I have read all the snacks.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of snacks.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.11.0-dev-1376+g738320188f
Operating system/version
MacOS 15.2
Describe the bug
I saw that there is a commit 37038df for disabling completion suggestions for blink.cmp, but I suppose it should be also disabled for nvim-cmp

Steps To Reproduce

use LazyVim with nvim-cmp extra enabled
try to rename a variable

Expected Behavior
No completion in input
Repro
No response

HAs been fixed already, but you need blink main, or wait for a new blink release.
See related other issues in this repo.

Like I mentioned, I use nvim-cmp

Just changed it so that the buftype is prompt, which nvim-cmp excludes.


How would I write this in stampit land ?

const Logger = (name='', level=1) => {
  //Private
  const newName = (''+name).toUpperCase();
  const outputName = `${newName} :`;

  const showLog = level == 1;
  const showWarn = level <=2 && level >=1;
  const showError = level <=3 && level >=1;

  //Public
  const log = (...args) => {
    if (showLog) {
      console.log(outputName, ...args);
    }
  }

  const warn = (...args) => {
    if (showWarn) {
      console.warn('!', outputName, ...args, '!');
    }
  }

  const error = (...args) => {
    if (showError) {
      console.error('!!!', outputName, ...args, '!!!');
    }
  }

  return {
    log,
    warn,
    error,
  }
}

export default (...args) => Logger(...args);

Factory
Public methods can access private variables
User cannot access private variables

This is what stampit aims, however I had hard time implementing it with stampit, except for wrapping this in a stampit().init, however I assume there is a better stampit way of breaking this down into smaller pieces.

You got that pretty much right with using stampit().init. As far as you need access to those private variables, you have to define methods in same closure. Stamps don't provide any magic for private stuff.
Alternatively you can use WeakMap for private state.
const privates = new WeakMap();

const Logger = stampit.init({name = '', level = 1} => {
    const newName = (''+name).toUpperCase();
    const outputName = `${newName} :`;
    privates.set(this, { level, newName, outputName });
}).methods({
    log(...args) {
        const { level, outputName } = privates.get(this);
        if (showLog(level)) {
            console.log(ouputName, ...args);
        }
    }
});

const showLog = (level) => level == 1;
const showWarn = (level) => level <=2 && level >=1;
const showError = (level) => level <=3 && level >=1;

init() is the correct solution in Stampit 3.0. It's basically the same as stampit().init() from 2.0:
const Logger = init(({name='', level=1 }) => {
  //Private
  const newName = (''+name).toUpperCase();
  const outputName = `${newName} :`;

  const showLog = level == 1;
  const showWarn = level <=2 && level >=1;
  const showError = level <=3 && level >=1;

  //Public
  const log = (...args) => {
    if (showLog) {
      console.log(outputName, ...args);
    }
  }

  const warn = (...args) => {
    if (showWarn) {
      console.warn('!', outputName, ...args, '!');
    }
  }

  const error = (...args) => {
    if (showError) {
      console.error('!!!', outputName, ...args, '!!!');
    }
  }

  return {
    log,
    warn,
    error,
  }
});

export default Logger;


[WIP] Store the state and database files in ~/.conda-store by default

Still some issues that need to be worked out here. Also will need #549 to be merged and rebased first.
This work is part of #513.

Description

This pull request:

a
b
c

Pull request checklist

[ ] Did you test this change locally?
[ ] Did you update the documentaion (if required)?
[ ] Did you add/update relevant tests for this change (if required)?

Additional information

Much saner default considering before how it would just write to your current directory. Agree this is needed.

Also need to double check that there aren't any places that were relying on the default values without configuring it (e.g., in the Docker setup).

Hmm, previously I was having issues where the database file was not being initialized properly, but now I'm not. I'm not sure if something else changed in the interim that changed this, or if I'm just not doing the same steps I was before. It would be helpful if someone else can test this (just run conda-store-server --standalone, or alternatively run conda-store-server and conda-store-worker separately, and see if it appears to function and that there aren't any errors printed to the console).

@nkaretnikov to test

Adding another note here: I think it would be a good idea to rename ~/.conda-store/conda-store-state to just ~/.conda-store/state, which is not only cleaner and less redundant, but should help with #588 as well.

Tested this on Windows by manually merged it with #559

I've addressed the review comments.
One thing worth being aware of here is that if anyone is running conda-store without configuring database_url or store_directory but just relying on the defaults, their setup will break. All the example configs do configure it, so hopefully that isn't happening.

One thing worth being aware of here is that if anyone is running conda-store without configuring database_url or store_directory but just relying on the defaults, their setup will break. All the example configs do configure it, so hopefully that isn't happening.

Wait, I think it wasn't an issue before, no? Why is this required now? Like, I'm pretty sure I used to be able to just run with --standalone without passing the config option.

The point is it will break existing installations if they were relying on the default configuration, because the defaults have changed.

Hmm, the test failure is because tests conda_store object from the fixture isn't being used for some reason.

@asmeurer The test failure looks legit. You also need to rebase.
________________ test_conda_store_register_environment_workflow ________________

...

ERROR    celery.app.trace:trace.py:270 Task task_update_storage_metrics[43b3f586-1076-4ec6-8185-6b17c6e0bda6] raised unexpected: FileNotFoundError(2, 'No such file or directory')
Traceback (most recent call last):
  File "/usr/share/miniconda/envs/conda-store-server-dev/lib/python3.10/site-packages/celery/app/trace.py", line 477, in trace_task
    R = retval = fun(*args, **kwargs)
  File "/home/runner/work/conda-store/conda-store/conda-store-server/conda_store_server/worker/tasks.py", line 75, in task_update_storage_metrics
    conda_store.configuration(db).update_storage_metrics(
  File "/home/runner/work/conda-store/conda-store/conda-store-server/conda_store_server/orm.py", line 663, in update_storage_metrics
    disk_usage = shutil.disk_usage(store_directory)
  File "/usr/share/miniconda/envs/conda-store-server-dev/lib/python3.10/shutil.py", line 1280, in disk_usage
    st = os.statvfs(path)
FileNotFoundError: [Errno 2] No such file or directory: '/home/runner/.conda-store/state'

Taking over this one. See https://github.com/conda-incubator/conda-store/pull/639.


Release 1.3.1 release Tag

Hello,
I noticed that version 1.3.1 was referenced in the git history, but the tag wasn't pushed to the repo for our build system to pick up. Would you mind push the tag to the repo as well?
Thanks in advance!
Andrew

Tagged v1.3.1 and v1.3.2. Picked up by GitHub and uploaded to https://build.openconext.org/repository/public/releases/org/openconext/oidc-server/1.3.x


Calloutquote block pattern does not render maximum length quote copy correctly

In release 1.7.0, if we put the maximum allowed characters into the Quote Copy field (200 characters per content model), The copy field is styled incorrectly in the pattern.  Here is a screen shot below:

Note that the copy text is flowing over the Dark block.

@kexuibm try a normal set of sentences.  You have a few very long strings in the copy you have typed there.


Sprout note encryption/decryption implementation.

We need an implementation of note encryption.  This has possible overlap with librustzcash.

https://zips.z.cash/protocol/protocol.pdf#sproutencrypt
https://zips.z.cash/protocol/protocol.pdf#sproutdecrypt

Two levels of completion:

all the types to represent in the transaction
implementing methods to do the note encryption

@dconnolly does this belong in the "Transaction Validation" milestone, or the "Wallet Support" milestone?

Wallet support

We're not planning to do full-node wallet work any time soon.
If we do, we'll need to decide if this ticket is in scope, and update its content, because the spec has changed since it was created.


v0.2.25 breaks History object

Using
for elevenlabs_history in elevenlabs.History.from_api():

I started getting this when I updated to 0.2.25 of elevenlabs package in Python.
Traceback (most recent call last):
  File "/home/user/python_projects/history_test.py", line 50, in <module>
    for elevenlabs_history.History.from_api():
  File "/home/user/python_projects/env1/lib/python3.10/site-packages/elevenlabs/api/history.py", line 95, in __iter__
    history_next = self.from_api(
  File "/home/user/python_projects/env1/lib/python3.10/site-packages/elevenlabs/api/history.py", line 84, in from_api
    return cls(**response)
  File "/home/user/python_projects/env1/lib/python3.10/site-packages/pydantic/main.py", line 165, in __init__
    __pydantic_self__.__pydantic_validator__.validate_python(data, self_instance=__pydantic_self__)
pydantic_core._pydantic_core.ValidationError: 88 validation errors for History
history.56.settings.style
  Field required [type=missing, input_value={'similarity_boost': 0.895, 'stability': 0.895}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.3/v/missing
history.56.settings.use_speaker_boost
  Field required [type=missing, input_value={'similarity_boost': 0.895, 'stability': 0.895}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.3/v/missing
history.57.settings.style
  Field required [type=missing, input_value={'similarity_boost': 0.75, 'stability': 0.895}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.3/v/missing
history.57.settings.use_speaker_boost
  Field required [type=missing, input_value={'similarity_boost': 0.75, 'stability': 0.895}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.3/v/missing
history.58.settings.style
  Field required [type=missing, input_value={'similarity_boost': 0.75, 'stability': 0.75}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.3/v/missing
history.58.settings.use_speaker_boost
  Field required [type=missing, input_value={'similarity_boost': 0.75, 'stability': 0.75}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.3/v/missing

This problem was not present in 0.2.21.
I've also started getting this:
/home/user/python_projects/env1/lib/python3.10/site-packages/pydantic/_internal/_fields.py:127: UserWarning: Field "model_id" has conflict with protected namespace "model_".

Hi @seoldamiai, thanks for reporting. The two issues should be fixed in v0.2.26.


Istio 1.17.0 regression with Knative DomainMappings

Bug Description
Downstream issue: https://github.com/knative/serving/issues/13712
Upgrading to Istio v1.17.0 has caused our DomainMapping feature to break - Istio now returns 503 no health upstream.
We have no issues with v1.16.x. The diff between our v1.17 and v1.16 deployment is here: https://github.com/knative-sandbox/net-istio/pull/1061/files#diff-d30c8c1936a00c0ef1c073c949441ea6cec0aa9d66d9a6da585ed998f642056b
Dump of our Virtual Services and K8s Services are in this gist - https://gist.github.com/dprotaso/64c53787a85b7e7cd1ec9f2b0c427bbe
I think the notable thing is one of our services uses ExternalName
Version
$ istioctl version
client version: 1.17.0
control plane version: 1.17.0
data plane version: 1.17.0 (3 proxies)

Additional Information
No response

It's possible to reproduce this in kind+metallb
Setup
$ kind create cluster
$ kubectl apply -f https://github.com/knative/serving/releases/download/knative-v1.9.0/serving-core.yaml
$ kubectl apply -f https://raw.githubusercontent.com/knative-sandbox/net-istio/ef720f6/third_party/istio-latest/istio-ci-no-mesh/istio.yaml
$ kubectl apply -f https://github.com/knative-sandbox/net-istio/releases/download/knative-v1.9.0/net-istio.yaml

$ kubectl patch configmap/config-domain --namespace knative-serving --type merge --patch '{"data":{"example.com":""}}'
$ kubectl patch configmap/config-network --namespace knative-serving --type merge --patch '{"data":{"autocreate-cluster-domain-claims":"true"}}'

Fixtures
$ kubectl apply -f - <<EOF
apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  name: hello
spec:
  template:
    spec:
      containers:
        - image: gcr.io/knative-samples/helloworld-go
          ports:
            - containerPort: 8080
          env:
            - name: TARGET
              value: "World"
EOF
$ kubectl apply -f - <<EOF
apiVersion: serving.knative.dev/v1alpha1
kind: DomainMapping
metadata:
  name: blah.com
  namespace: default
spec:
  ref:
    name: hello
    kind: Service
    apiVersion: serving.knative.dev/v1
EOF

Run the Test
First one succeeds - second one fails
$ docker run --network kind -it --rm cgr.dev/chainguard/curl -v -H 'Host: hello.default.example.com' <IP_ADDRESS> # Istio Ingress LB
$ docker run --network kind -it --rm cgr.dev/chainguard/curl -v -H 'Host: blah.com' <IP_ADDRESS> # Istio Ingress LB

Here's another bug where it returns 404. This setup is simpler as it doesn't require Knative
Setup
Setup Kind with MetalLB and install istio with istioctl install
apiVersion: v1
kind: Namespace
metadata:
  name: knative-serving
---
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: knative-ingress-gateway
  namespace: knative-serving
  labels:
    app.kubernetes.io/component: net-istio
    app.kubernetes.io/name: knative-serving
    app.kubernetes.io/version: devel
    networking.knative.dev/ingress-provider: istio
spec:
  selector:
    istio: ingressgateway
  servers:
  - port:
      number: 80
      name: http
      protocol: HTTP
    hosts:
    - "*"
---
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: knative-local-gateway
  namespace: knative-serving
  labels:
    app.kubernetes.io/component: net-istio
    app.kubernetes.io/name: knative-serving
    app.kubernetes.io/version: devel
    networking.knative.dev/ingress-provider: istio
spec:
  selector:
    istio: ingressgateway
  servers:
    - port:
        number: 8081
        name: http
        protocol: HTTP
      hosts:
        - "*"
---
apiVersion: v1
kind: Service
metadata:
  name: knative-local-gateway
  namespace: istio-system
  labels:
    app.kubernetes.io/component: net-istio
    app.kubernetes.io/name: knative-serving
    app.kubernetes.io/version: devel
    networking.knative.dev/ingress-provider: istio
    experimental.istio.io/disable-gateway-port-translation: "true"
spec:
  type: ClusterIP
  selector:
    istio: ingressgateway
  ports:
    - name: http2
      port: 80
      targetPort: 8081
---
apiVersion: v1
kind: Pod
metadata:
  name: nginx
  labels:
    app.kubernetes.io/name: proxy
spec:
  containers:
  - name: nginx
    image: nginx:stable
    ports:
      - containerPort: 80
        name: http-web-svc
---
apiVersion: v1
kind: Service
metadata:
  name: nginx
spec:
  selector:
    app.kubernetes.io/name: proxy
  ports:
  - name: http
    protocol: TCP
    port: 80
    targetPort: http-web-svc
---
apiVersion: v1
kind: Service
metadata:
  name: nginx-internal
  namespace: default
spec:
  externalName: knative-local-gateway.istio-system.svc.cluster.local
  ports:
  - name: http
    port: 80
    protocol: TCP
    targetPort: 80
  sessionAffinity: None
  type: ExternalName
status:
  loadBalancer: {}
---
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
  name: nginx-ingress
  namespace: default
spec:
  gateways:
  - knative-serving/knative-ingress-gateway
  - knative-serving/knative-local-gateway
  hosts:
  - nginx.default.example.com
  http:
  - headers:
      request:
        set:
          K-Network-Hash: 0878975ddb3e11427b140f810d15eb3cc2993d744e2f689514280dd8e43b24c5
    match:
    - authority:
        prefix: nginx.default
      gateways:
      - knative-serving/knative-local-gateway
      headers:
        K-Network-Hash:
          exact: override
    retries: {}
    route:
    - destination:
        host: nginx.default.svc.cluster.local
        port:
          number: 80
      headers:
        request:
          set:
            Knative-Serving-Namespace: default
            Knative-Serving-Revision: hello-00001
      weight: 100
  - match:
    - authority:
        prefix: nginx.default
      gateways:
      - knative-serving/knative-local-gateway
    retries: {}
    route:
    - destination:
        host: nginx.default.svc.cluster.local
        port:
          number: 80
      weight: 100
  - headers:
      request:
        set:
          K-Network-Hash: 0878975ddb3e11427b140f810d15eb3cc2993d744e2f689514280dd8e43b24c5
    match:
    - authority:
        prefix: nginx.default.example.com
      gateways:
      - knative-serving/knative-ingress-gateway
      headers:
        K-Network-Hash:
          exact: override
    retries: {}
    route:
    - destination:
        host: nginx.default.svc.cluster.local
        port:
          number: 80
      headers:
        request:
          set:
            Knative-Serving-Namespace: default
            Knative-Serving-Revision: hello-00001
      weight: 100
  - match:
    - authority:
        prefix: nginx.default.example.com
      gateways:
      - knative-serving/knative-ingress-gateway
    retries: {}
    route:
    - destination:
        host: nginx.default.svc.cluster.local
        port:
          number: 80
      headers:
        request:
          set:
            Knative-Serving-Namespace: default
            Knative-Serving-Revision: hello-00001
      weight: 100
---
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
  name: foo.com-ingress
  namespace: default
spec:
  gateways:
  - knative-serving/knative-ingress-gateway
  hosts:
  - foo.com
  http:
  - match:
    - authority:
        prefix: foo.com
      gateways:
      - knative-serving/knative-ingress-gateway
    retries: {}
    rewrite:
      authority: nginx-internal.default.svc.cluster.local
    route:
    - destination:
        host: nginx-internal.default.svc.cluster.local
        port:
          number: 80
      headers:
        request:
          set:
            K-Original-Host: foo.com
      weight: 100

Run the test
Fix one succeeds - second one does not
$ docker run --network kind -it --rm cgr.dev/chainguard/curl -v -H 'Host: nginx.default.example.com' <IP_ADDRESS>
$ docker run --network kind -it --rm cgr.dev/chainguard/curl -v -H 'Host: foo.com' <IP_ADDRESS>

Here's another bug where it returns 404. This setup is simpler as it doesn't require Knative

I think this one is expected, as in the foo.com-ingress VS the authority is rewrited to nginx-internal.default.svc.cluster.local while the nginx-ingress VS matches nginx.default.example.com

Here's another bug where it returns 404. This setup is simpler as it doesn't require Knative

I think this one is expected, as in the foo.com-ingress VS the authority is rewrited to nginx-internal.default.svc.cluster.local while the nginx-ingress VS matches nginx.default.example.com

Ah yeah I see I'm missing the entry in hosts

Hey curious when istio has patch releases?
On Mon, Feb 20, 2023 at 09:37 Istio Automation @.***>
wrote:

Closed #43440 https://github.com/istio/istio/issues/43440 as completed
via #43463 https://github.com/istio/istio/pull/43463.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/43440#event-8562410011, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAERAQR36JREPHBBAHYVKTWYN6RPANCNFSM6AAAAAAU7URTXI
.
You are receiving this because you authored the thread.Message ID:
@.***>

FYI it's out
https://istio.io/latest/news/releases/1.17.x/announcing-1.17.1/


Feature: Agent State Writing

[x] Abstract State Writer Class
[x] Concrete XML Writer
[ ] ~Concrete Binary Writer~

Readers need to support reading of

[x] Agent populations
[ ] Environment

Skipping binary implementation for now, will just add hdf5 afterwards (#157)


chore(workspace): run e2e in Windows

This PR just makes it easier for Windows users to launch e2e tests. It:

provides a .cmd batch script to run the docker image.
preserves LF line endings in .sh script files.

@yinonov Does this work for you on a windows machine?

I don't use windows

@yinonov Does this work for you on a windows machine?

@YonatanKra I don't use windows. if this doesn't affect mac in anyway, is there a reason to preclude this?

still relevant?


[WIP]Introducing a separation of concerns between data sources that are gi…

…ven a dataframe's schema upon write, from FileDataSourceV2, in part to allow data sources that require this notion to be developed in Java (FileDataSourceV2 is not compatible with Java because of its private Table member)

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@AmplabJenkins , thank you for the speedy  note on this patch.  Please, there is no current urgency on this patch.  I marked it as a [WIP] PR because I'm currently in the process of reviewing this change (weighed against other alternatives) with another Spark developer.  I'll keep the notes up to date on this PR.  Thank you!

The schema inference is already in the DS v2 API TableProvider which is not bound to file source. I think this feature "skip schema inference on write" should not bound to file source as well.
Instead of adding a marker trait, I think we can just reuse TableProvider.supportsExternalMetadata, which indicates that the schema inference is expensive. If supportsExternalMetadata == true, the DataFrameWriter.save should not infer schema and just pass the input schema to TableProvider.

@cloud-fan Your idea sounds just right.  Are you proposing to make that change in the work you're already doing (in which case I'll remove this PR)?

@gengliangwang is creating a PR to implement this idea.

I have created https://github.com/apache/spark/pull/30273 for this.

@gengliangwang your PR is better, thank you!


Incompatibility - Valheim+

won't show itself with Valheim+ installed.

Tanks for the report. However I am not able to reproduce it with a clean V+ install where all configs are enabled. The VNEI GUI is visible for me. Could you share your logfile (BepInEx/LogOutput.log) and V+ config (BepInEx/config/valheim_plus.cfg) so I can track the issue down?

LogOutput.log
valheim_plus.txt  <- CFG

You have an old BepInEx version, 5.4.11 not 5.4.15, this doesn't work with the latest Valheim version. Also VNEI isn't installed

well, there you go, i'm the dumbass, well, in all but one, i did have it installed, log should have showed it, vortex says it's Enabled, altough i did disable it yesterday and play a bit before trying to see what might be wrong with it, and finally posting here, should have looked deeper, my bad.

Vortex is weird for Valheim, you have to press a button like 'Elevate' or so to apply the mods really. And Jotunn needs to be installed too, if that isn't the case already

yeah, i did follow the instructions, just failed to see the update in BepX


Add requestPayment and lifecycle stub callbacks

Before this PR,

GET Bucket Lifecycle returns 403 Access Denied because lifecycle is not
included in subresources definition of Riak CS.
GET Bucket RequestPayment returns 404 Not Found because no dispatch rule for it.

In order to response a little more understandable response, this PR changes them as:

For requestPayment, just reply XML with "BucketOwner" after authn/authz.
For lifecycle, just reply error XML of "NotImplemented" without anthentication.

To be truthful, motivation for these changes were from s3cmd error for s3cmd info <bucket> :secret:

Updated.

@borshop merge

Release note: Add 501 stub for Bucket lifecycle and simple stub for Bucket requestPayment
[posted via JIRA by Kota Uenishi]


Update storage-how-to-mount-container-linux.md

Change is done only to the below command:
~/fuse_connection.cfg

@navba : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@navba - Thanks for your contribution!
#sign-off


Alternative defaultProps not working with component syntax

Flow version: 0.235.1
Expected behavior
defaultProps works when declaring it as:
type Props = {
    name: string
}
component Test(...props: Props) {
   return <h1>{`Hello ${props.name}!`}</h1>;
}
component.defaultProps = {
   name: 'World'
}

Actual behavior
Cannot assign object literal to "Test.defaultProps" because property defaultProps is missing in "React.AbstractComponentStatics"

Try-Flow Link
At the end of the docs detaling React class/function components, there's an "alternative" way to declare defaultProps which we have been using so far. However, this doesn't quite seem to work with component syntax, which is kinda weird because one would assume that they largely follow the rules for functional components.
Is this intentional?

This is intentional. Note that it will stop working for functions as well starting from React 19: https://react.dev/blog/2024/04/25/react-19-upgrade-guide#removed-proptypes-and-defaultprops


Setup separate environments in AWS

dev.edexchange.org/net
http://ec2-52-26-231-231.us-west-2.compute.amazonaws.com:8080/home
test.edexchange.org/net
pilot.edexchange.org/net
prod.edexchange.org/net

Currently there are QA and Pilot environments in AWS. Note that we have a certificate for ccctechcenter.org, hence domain names used. I'm unsure of the availability of edexchange.org, or if that is even a requirement, or just an initial suggestion.
https://edex-directory-qa.ccctechcenter.org:8443/home
https://edex-directory-pilot.ccctechcenter.org:8443/home

AWS has been setup for both QA and PILOT environments.


Hidden character in code snippet causes "az aks create" command do fail

When copying the JSON contents with the "copy" button there is a hidden character instead of a whitespace after "noProxy": that is only visible if you paste the copied contents to notepadd++. Check the image:

Because of this hidden character the "az aks create" command fails due to invalid JSON:
Failed to parse aks-proxy-config.json with exception:
Failed to parse JSON: {
"httpProxy": "http://<IP_ADDRESS>:3128/",
"httpsProxy": "https://<IP_ADDRESS>:3128/",
"noProxy": [
"localhost",
"<IP_ADDRESS>"
]
}
Error detail: Expecting value: line 4 column 15 (char 108)

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

ID: 5ed0304b-f115-61e4-f61a-b6d0ec47383d
Version Independent ID: 0ab5871c-869b-fc9a-35e3-6a5118f856d9
Content: Configuring Azure Kubernetes Service (AKS) nodes with an HTTP proxy - Azure Kubernetes Service
Content Source: articles/aks/http-proxy.md
Service: container-service
GitHub Login: @Nickomang
Microsoft Alias: nickoman

@jotavar Thanks for pointing this, the document is updated and changes will go live soon.


Master -> Live

Docs Build status updates of commit 6d5461c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/asset-creation-process.md
:white_check_mark:Succeeded
View

mixed-reality-docs/case-study-expanding-the-design-process-for-mixed-reality.md
:white_check_mark:Succeeded
View

mixed-reality-docs/case-study-the-pursuit-of-more-personal-computing.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-azure-306.md
:white_check_mark:Succeeded
View

mixed-reality-docs/scale.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

mixed-reality-docs/asset-creation-process.md
:white_check_mark:Succeeded
View

mixed-reality-docs/case-study-expanding-the-design-process-for-mixed-reality.md
:white_check_mark:Succeeded
View

mixed-reality-docs/case-study-the-pursuit-of-more-personal-computing.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hololens-known-issues.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-azure-306.md
:white_check_mark:Succeeded
View

mixed-reality-docs/scale.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

mixed-reality-docs/asset-creation-process.md
:white_check_mark:Succeeded
View

mixed-reality-docs/case-study-expanding-the-design-process-for-mixed-reality.md
:white_check_mark:Succeeded
View

mixed-reality-docs/case-study-the-pursuit-of-more-personal-computing.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hololens-known-issues.md
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-azure-306.md
:white_check_mark:Succeeded
View

mixed-reality-docs/scale.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 7e3ad4e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/asset-creation-process.md
:white_check_mark:Succeeded
View

mixed-reality-docs/case-study-expanding-the-design-process-for-mixed-reality.md
:white_check_mark:Succeeded
View

mixed-reality-docs/case-study-the-pursuit-of-more-personal-computing.md
:white_check_mark:Succeeded
View

mixed-reality-docs/color,-light-and-materials.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hololens-known-issues.md
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-azure-306.md
:white_check_mark:Succeeded
View

mixed-reality-docs/recommended-settings-for-unity.md
:white_check_mark:Succeeded
View

mixed-reality-docs/scale.md
:white_check_mark:Succeeded
View

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


Add ESO (External Secret Operator)

Summary
Add ESO (External Secret Operator) as an additional option while creating a secret.
Motivation
Additional options for the user
Proposal
In secret, by adding an options in the dropdown

AB#81

done with #2227


Unclear instructions for configuring .vscode\settings.json

I find the following instructions unclear:

Once installed in Visual Studio Code, "autopep8" will be available as a formatter for python files. Please select "autopep8" (extension id:ms-python.autopep8) as the default formatter. You can do this either by using the context menu (right click on a open python file in the editor) and select "Format Document With...", or you can add the following to your settings:

  "[python]": {
    "editor.defaultFormatter": "ms-python.autopep8"
  }

and change the following, if set:

  "python.formatting.provider": "none"

Specifically, I find the last part unclear as it raises an unanswered question: "Change it to what?" If the intention is to remove the line of code, then a better choice of words would be "and delete the following, if set" or "and remove the following, if set". Kindly clarify.
I also felt that this would be more of a discussion than an issue, but I think discussions aren't enabled yet for the Autopep8 repository.

The intent is if the setting "python.formatting.provider" was set to some value like autopep8 (or black or yapf) then it should be changed to none

I see.
The reason I raised the issue was that I was getting the following warning in VS Code and I didn't know how to go about it:

This setting will soon be deprecated. Please use the Autopep8 extension or the Black Formatter extension. Learn more here: https://aka.ms/AAlgvkb.

Your help will be greatly appreciated.

You will need it until the setting is deprecated and removed.

Noted with thanks.


Does not compile on latest nightly

I am getting this error:
error[E0308]: mismatched types
   --> /home/r/.cargo/registry/src/github.com-1ecc6299db9ec823/compiletest_rs-0.3.14/src/lib.rs:101:22
    |
101 |         run_ignored: config.run_ignored,
    |                      ^^^^^^^^^^^^^^^^^^ expected enum `test::RunIgnored`, found bool
    |
    = note: expected type `test::RunIgnored`
               found type `bool`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0308`.

Ah, seems to be fixed by https://github.com/laumann/compiletest-rs/commit/2ebb5216ab7391817cd02ddfcc8388a493692d70 but there is no new release yet.

Fixed in 0.3.15 -- although now stable is broken. https://github.com/laumann/compiletest-rs/issues/133

0.3.16 is out.


Receipt of manual payments

I may be being dense but I cannot see how I can enter an amount for a manual payment.  Even if I change the status to complete it still shows the total amount as outstanding.  Where the gateway for a payment is manual I need to be able to mark the payment as received.
It seems we need to set Payment->Status to 'Captured'.  I'm not sure if we need Payment->onCaptured() to be called as well.

Unless I'm misunderstanding you this is how I've done it (this would be an extension on Order):
	/**
	 * @param FieldList $fields
	 */
	public function updateCMSFields(FieldList $fields) {
		$fields->addFieldToTab('Root.Main', new ToggleCompositeField('ManualPayment', 'Record Additional Payment', array(
			CurrencyField::create('ManualPaymentAmount', 'Amount'),
			TextField::create('ManualPaymentMessage', 'Note'),
		)));
	}

	/**
	 * This is a little hack to let them add payments from the admin
	 * @param $value
	 */
	public function setManualPaymentAmount($value) {
		$amount = preg_replace('/[^0-9\.\-]/', '', $value);
		if ($amount > 0) {
			$payment = new Payment();
			$payment->Gateway = 'Manual';
			$payment->OrderID = $this->owner->ID;
			$payment->setCurrency('USD');
			$payment->setAmount($amount);
			$payment->Status = 'Captured';
			$payment->write();

			$msg = new GatewayMessage();
			$msg->PaymentID = $payment->ID;
			//$msg->UserID = $this->owner->MemberID;
			$msg->UserID = Member::currentUserID();
			$msg->Message = $_REQUEST['ManualPaymentMessage'];
			$msg->write();

			$this->owner->Paid = SS_Datetime::now()->RAW();
		}
	}

Thanks - that is exactly what I needed


when checking whether assignment texts are in sync with the exercise,…

… compare the texts themselves instead of database entities

Coverage decreased (-0.009%) to 73.321% when pulling 908d6bde34243b449757f27da3ba746b4c6031aa on better-localized-text-comparison into e74229c4d0b89350ef8fefdd59140c176113bca4 on master.

Coverage decreased (-0.009%) to 73.321% when pulling 335c61e1c972e98d9b4a74a65281e9ea55279353 on better-localized-text-comparison into e74229c4d0b89350ef8fefdd59140c176113bca4 on master.


Registration

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/104865
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 13ee05ea763d7f992660f23802525d46df401ae6
git push origin v1.0.0

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/104865
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 9503bfd2915fc421493938212100d608b87bf1e7
git push origin v1.0.0

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/104865
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 49a36512fb66f7595a603e4246730e52b55fa36a
git push origin v1.0.0

@JuliaRegistrator register()

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/111325
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.1.1 -m "<description of version>" d06bc7ca33716a0956aee3ca8bf2adb9ebc94ed6
git push origin v1.1.1

@JuliaRegistrator register()
Release notes
Cleaned up dependencies and updated POMDPs.jl to version 1.0.0.

Registration pull request created: JuliaRegistries/General/113340
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.1.2 -m "<description of version>" ffd02c8d2d12cc1e5022c91fadfbc6cf308c9965
git push origin v1.1.2


DigitalOcean creation fails with "Error creating machine: exit status 255"

Server version - V0.14.1
Steps to reproduce the problem:
Add Digitial Ocean host , providing valid values for all configuration parameters.
Sometimes , Machine creation fails with ""Error creating machine: exit status 255" .
Server logs for the failed machine:
time="2015-04-01T23:26:19Z" level=info msg="Creating Machine" eventId="d59ad9db-4ea5-49cb-b200-eecdcde6a9ea" resourceId=1ph175
time="2015-04-01T23:26:20Z" level=info msg="stdout: time="2015-04-01T23:26:20Z" level="info" msg="Creating CA: /var/lib/cattle/machine/29a12cce-ba74-41e6-b3f2-7e5cd106bec7/machine/certs/ca.pem" " resourceId: =1ph175
time="2015-04-01T23:26:21Z" level=info msg="stdout: time="2015-04-01T23:26:21Z" level="info" msg="Creating client certificate: /var/lib/cattle/machine/29a12cce-ba74-41e6-b3f2-7e5cd106bec7/machine/certs/cert.pem" " resourceId: =1ph175
time="2015-04-01T23:26:29Z" level=info msg="stdout: time="2015-04-01T23:26:29Z" level="info" msg="Creating SSH key..." " resourceId: =1ph175
time="2015-04-01T23:26:30Z" level=info msg="stdout: time="2015-04-01T23:26:30Z" level="info" msg="Creating Digital Ocean droplet..." " resourceId: =1ph175
time="2015-04-01T23:26:32Z" level=info msg="stdout: time="2015-04-01T23:26:32Z" level="info" msg="Waiting for SSH..." " resourceId: =1ph175
time="2015-04-01T23:27:35Z" level=info msg="stdout: time="2015-04-01T23:27:35Z" level="info" msg="Configuring Machine..." " resourceId: =1ph175
time="2015-04-01T23:29:42Z" level=info msg="stdout: time="2015-04-01T23:29:42Z" level="error" msg="Error creating machine: exit status 255" " resourceId: =1ph175
time="2015-04-01T23:29:42Z" level=info msg="stdout: time="2015-04-01T23:29:42Z" level="warning" msg="You will want to check the provider to make sure the machine and associated resources were properly removed." " resourceId: =1ph175
time="2015-04-01T23:29:42Z" level=info msg="stdout: time="2015-04-01T23:29:42Z" level="fatal" msg="Error creating machine" " resourceId: =1ph175
time="2015-04-01T23:29:42Z" level=error msg="Error processing event" err="Error creating machine: exit status 255" eventId="d59ad9db-4ea5-49cb-b200-eecdcde6a9ea" eventName="physicalhost.create;handler=goMachineService" resourceId=1ph175

With docker machine's stability, this error doesn't happen as regular as before. Will re-open if we see it happening again.


Update business process version

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/676606627

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/676606627
Status: success


Not Showing completion code so much (Rarely)

Type: Bug
So I started a new project
then I feel that vs wasn't the same, because it is showing like
"self.setGeometry(1006, 663, 1006, 663)" the word "self" has color and the rest it doesn't show up and
if I try something else
like
"self." then the completion would like "dir","class",etc...

also the vs error showing system like pylance was a lit slow instead of high speed
pls help
VS Code version: Code 1.84.1 ( 2023-11-06T12:35:59.022Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Extensions (17)

Extension
Author (truncated)
Version

code-runner
for
0.12.1

vscode-edge-devtools
ms-
2.1.3

python
ms-
2023.20.0

vscode-pylance
ms-
2023.11.11

jupyter
ms-
2023.8.1002501831

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.8

cmake-tools
ms-
1.15.31

cpptools
ms-
1.17.5

cpptools-extension-pack
ms-
1.3.0

LiveServer
rit
5.7.9

tabnine-vscode
Tab
3.29.0

cmake
twx
0.0.17

intellicode-api-usage-examples
Vis
0.2.8

vscodeintellicode
Vis
1.2.30

vscodeintellicode-completions
Vis
1.0.22

(1 theme extensions excluded)

This issue lack

mentioning of the language and extensions
a complete, yet minimal code sample

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Handle CI startup on no internet connection

Nice CI startup failure if there is no internet connect, or maybe even waiting for connection automatically on startup

I take this card! https://ruby-doc.org/stdlib-1.8.7/libdoc/ping/rdoc/Ping.html


Updating the element under specified label. Possible?

What should happen if I add 2 different elements but with the same label?
Like this:
a = np.zeros(shape=(1,512))
b = np.ones(shape=(1,512))
p.add_items(a, 1)
p.add_items(b, 1)
I thought it would be cool to update in this way the element under specified index.
If I get it right, currently I should do the following to achieve my expected result:
p.add_items(a, 1)
p.mark_deleted(1)
p.add_items(b, 1)
but the element stays in memory.

After Yury's comment here https://github.com/nmslib/hnswlib/issues/72#issuecomment-549405512 I updated the code (wrapped all indexes into arrays) and double checked: what I want to achieve seems working (though updating elements in HNSW index is not officially supported, including Faiss). So I just want to make sure it's actually working as I want and expect.
import hnswlib
import numpy as np
p = hnswlib.Index(space='l2', dim=512)
p.init_index(max_elements = 10000, ef_construction = 200, M = 80)
a = np.zeros(shape=(1,512))
b = np.ones(shape=(1,512))
p.set_ef(200)
p.add_items(a, [1])
p.add_items(b, [1])
p.get_items([1])
[[1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0,......

@realsergii
Yes, it only marks the element as deleted, but it still stays in the memory. The search procedure takes it into account.
Making a full support of deletion is somewhat harder (especially if you want to do it thread safe) and not implemented here yet.

@yurymalkov thanks, but this question is about updating, not deletion. So is updating possible?

@realsergii
It depends on strength of the update. If it is a minor (in a sense that the ordering of the neighbor does not changes compeletely) it is easy to implement. I think now you can do it via the C++ api.
If updates are big, they are equivalent to deleting and adding elements.

@yurymalkov ok, but what I'm doing in my snippet (adding two different elements, but with the same label)
p.add_items(a, [1])
p.add_items(b, [1])
is it equivalent to updating an element under the label 1?

@realsergii
Yes, it is designed to work that way.
I suspect there might be a bug with its implementation in the master though. I'll check it.

@realsergii There was a logical bug there.
Now it is fixed in develop

@yurymalkov thanks! when to expect in master ?

@realsergii A few days, I think

Hello. However, this dont work, when you use space='cosine'. I can not understand this. After update, i get list of [...0.04419417306780815...]

Hi, you mean that it does not work for cosine in any way?


Introduce sidebar with search and tearout

Bit of a large one sorry, but it is split into separate commits to make it a bit easier.

Not now. Tearing out it still unstable.


Refactor Write-Host and Write-Warning usage

As discussed in https://github.com/Crypt32/PSPKI/issues/4, the following functions need to be updated, to get rid of Write-Host and Wriye-Warning (where it is used incorrectly):* Approve-CertificateRequest* Get-RequestRow* Remove-CAKRACertificate* Revoke-Certificate* Remove-CertificateEnrollmentPolicyService* Remove-CertificateEnrollmentService* Remove-DatabaseRow* Deny-CertificateRequest* Add-CertificateEnrollmentService* Add-CertificateEnrollmentPolicyService* Add-CertificateTemplateAclThank you.

Thanks for report. I will follow this list to improve error behavior in these commands.

The work is in progress in this branch: https://github.com/Crypt32/PSPKI/tree/feature-WriteHostCompliance


NLP Notebook: Add Question Asnwering

Added a section for question answering. Even though it is a small section I believe it is an interesting concept worth noting.

I agree this is interesting -- well noted.


[BUG] No Titlebar Icons on QMdiArea on Windows

Description
On Windows, with a QMdiArea, for both Qt5 and Qt6, there are no icons on the titlebar for the close, restore, and minimize. This is only an issue with the dark theme, suggesting it might be an issue with the titlebar icon colors. The menu icon, however, does work. This only reproduces if the Windows Qt style is used, but the other styles don't look good either.
Native

Dark

Light

The menu icon similarly meshes with the system theme on KDE Linux, and only using a custom style (for a different titlebar color) changes this:
Breeze

Fusion


Contributors Detail in /about page

[x] I am from GSSoC23.
[x] I would like to be assigned this task.

I would like to add all the contributors details that are involved in this project
Code of Conduct
By submitting this issue, you agree to follow our Code of Conduct.

[x ] I follow the Contributing Guidelines of this project.
[x] I have checked the current issues for duplicate problems.
[x ] I have read the readme of this repository.

please assign this issue to me


I can't sign in.

OS: Windows 10
Issue Descriptions: I've just installed the program, it's asking me to sign in, I click sign in the button flashes and nothing happens, i can click it again and again but nothing happens
Steps to Reproduce: install program, run program, click sign in, nothing.

Hmm after trying a tonne of times it's suddenly decided to load only after I ended up posting. sorry.

The sign in button is not controlled or created by this application.  Can you ensure

You can sign in correctly in Chrome
You have tried after reinstalling
You have tried on a different network

This is probably a temporary google issue 👍


Feature: CFM 1.0 fault models with scaled aveLowerDepth attribute

SRM team needs new opensha Fault Model XML from CFM with the following requirements

[ ] use v1.0 of CFM (previously used CFM 0.9)
[ ] set aveLowerDepth attribute from the CFM Depth_Dfc instead of Depth_D90 field, and applying a scalar...

[ ] one version is scaled by 0.8
[ ] one version is scaled by 0.66

[ ] As per previous runs, one version including for ALL NZ fault and one with the low rate TVZ faults removed (however this is done).

Done Criteria
There should be a total of four new XML fault models named:

[ ] cfm_1_0_dfc0_66_all.xml
[ ] cfm_1_0_dfc0_66_no_tvz.xml
[ ] cfm_1_0_dfc0_80_all.xml
[ ] cfm_1_0_dfc0_80_no_tvz.xml

@chrisbc I don't have the v1.0 shapefile yet, but have asked Hannu for it. Will crack on with this when that arrives.


VLAZ: Watch ichanfeng901

VLAZ requests the watch of the watch_keyword ichanfeng901. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

ichanfeng901 has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by cigien in Charcoal HQ


Initial folder should allow for pathlib.Path instead of String

It would be great if the constructor accepts pathlib.Path instead of String as the initial folder.

Thank you for the suggestion. I'll add it to the list of future enhancements.


Question about plugin maintenance

In our company we have been using this plugin for quite some time already. The work done here was pretty good so far, but we have noticed that it is not being maintained that often anymore (the last release was in March, already 6 months ago) and some of the features we wanted to have, which might be really useful for others as well, are not merged at all.
Due to this situation, we ended up creating a fork of this project, add our suggestions to it and keep all the backstage dependencies up to date, to avoid any possible issue. However, we would like to get rid of our forked repo and use the actual plugin again.
I've already mentioned it in the Backstage's discord channel, and we would like to know if this plugin is going to be maintained in the near future or not. Otherwise, it might be a good idea if somebody decides to get the ownership of this plugin and bring it to life again. I was also thinking about adding it directly to the list of open-sourced plugins maintained by the backstage community.
What do you think about it?

Hey there!
Happy to know that this humble side-project has proven useful to your company :)
Before I comment on maintenance questions, here's some context around this repository.
I created this plugin to play with both Grafana and Backstage. At the time, I was also using Backstage professionally, so it was easy to find reasons and time to maintain this repo. Since then, I changed jobs and no longer work on a Backstage deployment (directly at least).
That explains the delays and lack of regularity in updates & PR reviews: the project reverted to being a side-project only, work on it pretty much happening when/if I have some motivation and time.
However, the company you work for (and others I presume) understandably have different needs.
I can think of two main ways to ensure that these needs will be met:

a fork: the license allows it, and it's the best way for a company to ensure that the work they need is done, when they need it to be done. There might even be people from the community is willing to do it for free
some kind of discussion + sponsoring: as a way to offload maintenance/feature work to the original maintainer, while providing a fair incentive

So to summarize: I view this project as a side-project and I'll work on it from time to time with no promises on any regularity (unless some kind of sponsoring is involved).
Again: I'm genuinely happy to learn that this repo is useful enough for your company to even have this discussion (and kinda surprised, if I'm honest)

Thanks for your answer @K-Phoen. I would say the fork is definitely the best option, specially because another person is already willing to maintain it (@Vity01). So if you agree, we could start with the transfer of the ownership some time soon, and bring this project back to track :smiley:

@K-Phoen  what about to just assign multiple maintainers for this existing repo without necessary forking?

A fork sounds good to me :)
I like the idea of retaining ownership on this repo since I still plan on playing with it from time to time.

Could we also move this into the main Backstage repo and "donate" it?

Could we also move this into the main Backstage repo and "donate" it?

That was one of our initial ideas, but I think that's not an option anymore: https://github.com/backstage/backstage/issues/20266
But anyways, creating a fork and maintaining it sounds like the best approach here.

Hey @Vity01 , will you then create the new repository for the plugin? Or should we find a different approach to publish it?


Chaos experiment on a Kube cluster

Minor stylistic changes, and introduction is a work in progress
Signed-off-by: Smriti S<EMAIL_ADDRESS>

Preview environment: https://ci.pr.harness.io/pr-174

Preview environment: https://ci.pr.harness.io/pr-174

@SmritiSatya prob the number of  PRs that were not merged causing some of this :-)
Frequent broken links are linking to:

- ../common-tunables-for-all-experiments

- ./aws-experiments-tunables

Exhaustive list of all broken links found:

- On source page path = /docs/chaos-engineering/chaos-faults/aws/elb-az-down:

   -> linking to ../common-tunables-for-all-experiments (resolved as: /docs/chaos-engineering/chaos-faults/common-tunables-for-all-experiments)

   -> linking to ./aws-experiments-tunables (resolved as: /docs/chaos-engineering/chaos-faults/aws/aws-experiments-tunables)

- On source page path = /docs/chaos-engineering/chaos-faults/aws/lambda-delete-event-source-mapping:

   -> linking to ../common-tunables-for-all-experiments (resolved as: /docs/chaos-engineering/chaos-faults/common-tunables-for-all-experiments)

   -> linking to ./aws-experiments-tunables (resolved as: /docs/chaos-engineering/chaos-faults/aws/aws-experiments-tunables)

- On source page path = /docs/chaos-engineering/chaos-faults/aws/lambda-toggle-event-mapping-state:

   -> linking to ../common-tunables-for-all-experiments (resolved as: /docs/chaos-engineering/chaos-faults/common-tunables-for-all-experiments)

   -> linking to ./aws-experiments-tunables (resolved as: /docs/chaos-engineering/chaos-faults/aws/aws-experiments-tunables)

- On source page path = /docs/chaos-engineering/chaos-faults/aws/lambda-update-function-memory:

   -> linking to ../common-tunables-for-all-experiments (resolved as: /docs/chaos-engineering/chaos-faults/common-tunables-for-all-experiments)

   -> linking to ./aws-experiments-tunables (resolved as: /docs/chaos-engineering/chaos-faults/aws/aws-experiments-tunables)

- On source page path = /docs/chaos-engineering/chaos-faults/aws/lambda-update-function-timeout:

   -> linking to ../common-tunables-for-all-experiments (resolved as: /docs/chaos-engineering/chaos-faults/common-tunables-for-all-experiments)

   -> linking to ./aws-experiments-tunables (resolved as: /docs/chaos-engineering/chaos-faults/aws/aws-experiments-tunables)

- On source page path = /docs/chaos-engineering/chaos-faults/aws/rds-instance-delete:

   -> linking to ../common-tunables-for-all-experiments (resolved as: /docs/chaos-engineering/chaos-faults/common-tunables-for-all-experiments)

   -> linking to ./aws-experiments-tunables (resolved as: /docs/chaos-engineering/chaos-faults/aws/aws-experiments-tunables)

- On source page path = /docs/chaos-engineering/chaos-faults/aws/rds-instance-reboot:

   -> linking to ../common-tunables-for-all-experiments (resolved as: /docs/chaos-engineering/chaos-faults/common-tunables-for-all-experiments)

   -> linking to ./aws-experiments-tunables (resolved as: /docs/chaos-engineering/chaos-faults/aws/aws-experiments-tunables)

Preview environment: https://ci.pr.harness.io/pr-174


ci: fix needs param

I should even test it (=_= +)

Tested at https://github.com/apache/incubator-kvrocks/actions/runs/4900989972/jobs/8752006763


Bug fix percentile_approx function coredump when upgrade

Proposed changes
this pr https://github.com/apache/doris/pull/37330 have change the nullable of agg function,
But it's shouldn't change the old percentile_approx  function.
this could cause it's core dump when upgrade.

run buildall

run buildall


Silence this gem

@grossadamm Is this going to be merged soon?  Great gem, but not a fan of the puts statements on spec runs, etc....


Cached Values

We have discussed about a way to cache data or object here.
I've created this issue to we continue discussing a way to implement that without using a procedural approach.
@nunopicado thought about a Maybe object, inspired in Haskell.
I suggested Laze object in that time, but I'm not satisfied with this name yet.
We already thought about using functions/anonymous functions but this was not completely implemented in Free Pascal.
So, let's come back to scratch and think just in simple objects.
I'm thinking in a simple class called TCached. I'll make some drafts and tests. As soon as possible I will publish my results here.

About ifs, there is nothing wrong with ifs in OO world, as long as such if is not spread over the place and causing maintenance problems.  Most of the time we should replace ifs with polymorphic calls, but there are some cases in which ifs are just fine, because the "if i didn't cache this value, then get it, else return cached value" is just fine. Every "purist OO solution" will end up in more complicated code, and simple is just better than any complicated stuff. As long as the "if i didint cache this thing" isn't spread all over the place, I say, such if statement is fine, hidden in the implementation of a decorator that consumers will not ever notice and care about

There are no problems with ifs when they are used in conditionals within the behavior of an object to make decisions about the state of that same object.
When we have a code that are supposing something about other objects, then we have a "controller". This is not good because, in object-oriented design, we should not have a controller telling the objects what to do and in what sequence to do. We should have only objects working together.

I've just realized that we don't need such class.
To make this happen using the "Tell Do not Ask" principle is by using anonymous functions. But, IMHO, this is not a real OOP.
The code for those functions will exists so, why not create them inside a class, as methods?
Besides that, we always can create decorators — as @ortuagustin said https://github.com/mdbs99/james/issues/28#issuecomment-315559961.
/cc @nunopicado


Timing violation on Tang Nano 9K?

Max Frequency Summary:

NO.
Clock Name
Constraint
Actual Fmax
Logic Level
Entity

1
data_pll/CLKOUT.default_gen_clk
50.996(MHz)
122.724(MHz)
4
TOP

2
div_5/CLKOUT.default_gen_clk
67.495(MHz)
45.834(MHz)
16
TOP

Any idea how to resolve this?

These values, along with enabling the 'open source' fifo gives 0 counter errors.
localparam HDMI_PLL_IDIV  = 0;
localparam HDMI_PLL_FBDIV = 7;
localparam HDMI_PLL_ODIV  = 4;

localparam DATA_PLL_IDIV  = 8;
localparam DATA_PLL_FBDIV = 10;
localparam DATA_PLL_ODIV  = 32;

Yes, the Tang Nano 9K is the most tricky one due to the speed grade of the FPGA.
After I recently found a pipelined TMDS encoder optimized for the Gowin FPGAs, I switched to it with commit a9bc7252091895799908c8e0bb583acc55828c5d. Now Fmax for the div_5 clock ist 76.648 MHz.
Can you retry your test?