%20 in AbsolutePath not supported on Windows 11

Describe the bug
When calling File.ReadAllTextAsync() with an AbsolutePath that contains spaces, represented by %20, the file cannot be found on Windows 11.
To Reproduce
Steps to reproduce the behavior:

Using the following code...

if (Application.Current?.ApplicationLifetime is IClassicDesktopStyleApplicationLifetime { MainWindow: not null } desktop)
{
    IHostStorageProvider storageProvider = new HostStorageProvider(desktop.MainWindow.StorageProvider);

    var filePickerOpenOptions = new FilePickerOpenOptions
    {
        FileTypeFilter = new FilePickerFileType[]
        {
            new("All Files")
            {
                Patterns = new[] { "*.*" },
            }
        },
    };

    var result = await _storageProvider.OpenFilePickerAsync(filePickerOpenOptions);

    if (result.Any())
    {
        string Text = await File.ReadAllTextAsync(result[0].Path.AbsolutePath);
    }
}

...attempt to open a file on Windows 11, in a location that contains a space in one of the folders of its path.

Notice the error...

Expected behavior
The file's contents should be loaded into Text
Screenshots

Environment

OS: Microsoft Windows 11 Pro v 10.0.22621 Build 22621
Avalonia-Version: Avalonia for Visual Studio 2022 v11.1

Additional context
If I manually replace the %20s with spaces, the file loads successfully.
If I paste the AbsolutePath containing the %20s into Windows File Explorer, it generates the same error.

https://github.com/AvaloniaUI/Avalonia/issues/12784#issuecomment-1706065698

await File.ReadAllTextAsync(result[0].Path.AbsolutePath)

Please use result[0].OpenReadAsync().
Uri.LocalPath returns file system-friendly path
It's not a bug.


Make amundsen compatible with upcoming release of Atlas i.e., v2.0

Atlas is working on new release, which might break our implementation of Amundsen Atlas proxy. Make sure atlas's 1.1x+ versions are supported by amundsen. Keep backward compatibility in mind while implementing this.

One of the breaking change is that the new version of Atlas does not include relationshipAttributes under attribute key anymore.

@verdan Just reviewed the PR, merged and released it. Let me know if you need anything. Thanks!

thanks @jinhyukchang. this can be closed for now :)


Merge Scenes category into v.next

Last category to merge for the next release.

@philium I've made some more edits, please let me know what you think!


Does not resolve export forwards

The current version of DInvoke does not resolve export forwards. It assumes that all exports are not forwarded. This may be demonstrated by attempting to resolve kernel32.dll!InitializeSRWLock.

Fixed in https://github.com/TheWover/DInvoke/commit/af9f86984a2ce329cb44a97459592f0b191fe252 Will be merged with v1.1.


Following banks ifsc not available in bankname.json

Bank   Internasional Indonesia
Capital   Local Area Bank Ltd
Development   Credit Bank Ltd
Oman   International Bank SAOG
Parsik   Janata Sahakari Bank Ltd
Ratnakar   Bank Limited
The   Lakshmi Vilas Bank Ltd
UBS AG
Westpac   Banking Corporation

Capital Local Area Bank is now a Payments Bank and called Capital Small Finance Bank
Correct spelling for Lakshmi Vilas Bank is "Laxmi Vilas Bank"
Development Credit Bank is now called DCB Bank only
Oman International was merged with HSBC and is called "HSBC Bank Oman S.A.O.G"
Parsik Janta's correct name is named as "Gopinath Patil Parsik Janata Sahakari Bank" in the sheets. I'll see if we need to shorten this to GP
Ratnakar Bank calls itself RBL
UBS shut down in India in 2013: https://timesofindia.indiatimes.com/business/india-business/UBS-to-shut-India-banking-unit/articleshow/20709786.cms
Westpac is in the file: https://github.com/razorpay/ifsc/blame/master/src/banknames.json#L1329

I think IBBK had a similar merger, but need to double check that.

Thank you @captn3m0

IBBK is the same case as Oman. RBI has two banks in this list: https://www.rbi.org.in/Scripts/bs_viewcontent.aspx?Id=2009

Bank Internasional Indonesia
PT Bank Maybank Indonesia TBK

And both of them have a single entry (IBBK0000001) with a different bank name. Thankfully, rest of the details are same, unlike the Oman case (which has a different branch name I think)
We have to pick one, we just picked the second instead of the first.


update gh workflows to ubuntu version 22.04 and label-commenter issue

Description

Just a few weeks back we updated the GitHub actions workflow specifically to ubuntu 22.04 in meshery/meshery repository cause ubuntu-latest is still on 20.04 and it gives some deprecated warning(Even some workflows were using 18.04v).
So should we update GitHub workflow for meshkit repository ?
And I can see some warnings for the label-commenter node.js version.
<EMAIL_ADDRESS>is using node 16)
Even for label-commenter actions, we either need to mention specific versions or mention as the latest
Issue reference:
https://github.com/meshery/meshery/pull/6689
Expected Behavior

Screenshots

Environment:

OS: Ubuntu
Browser: Chrome
Version: [e.g. 22]
Device: [e.g. laptop, iPhone 8]

[Optional] To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

[Optional] Additional Context

@acald-creator @leecalcote what should we do here?
Should we update it or keep it as the latest for meshkit repository?

I'll yield to @acald-creator's perspective.

Closing for now, GitHub will migrate the ubuntu version to the latest when the update is done


Specify domain number in current data set request

Problem
When we query the current PTP state, the underlying function CurrentDataSetRequest() never initialized the domainNumber, causing it to not return any data.
Error:
getting CURRENT_DATA_SET management TLV: read unixgram /var/run/ptpcheck.4312.sock->/var/run/ptp4l: i/o timeout

Proposed Solution
We manually set the domainNumber to the one we use, and the correct data set was returned. We'd like the API to let us specify the domainNumber and other parameters when querying PTP.

Since CurrentDataSetRequest() returns a concrete type, it is trivial to just update any field on it. No other .*Request() functions accept any inputs either.
However, if you believe that this part of the API could be improved in a meaningful way, pull requests are always welcome.

We were using the checker.RunCheck() function as our entrypoint into the library : https://github.com/facebook/time/blob/main/cmd/ptpcheck/checker/runner.go#L68-L85
Somehow in previous versions of the library it always correctly returned data by querying PTP for the current state via /var/run/ptp4l (not sure how it managed to get the right domain no. back then).
Now it returns the above error. After some digging I found that the management TLV requests that it creates as part of https://github.com/facebook/time/blob/main/ptp/protocol/management_client.go#L86 always uses DomainNumber: 0 while our infra of PTP devices uses 11.
Is there a way to use the cmd/ptpcheck package where we'll be able to specify the domain number or should we use the "deeper" packages, like ptp/protocol to build management TLV payloads ourselves and query the state of PTP ?


split the repo for the pipelines focused on HMS and Kempner AI Clusters

Modify the main_nextflow.nf
nextflow_slurm.config
spike_sort.slrm
Change the partition, location of the container, example files, and cluster specific execution environments

make this pull request from the dev branch


JAVA-2723: Enable parallelization of graph tests

Against DSE 6.7 we have a few graph failures, see here. But it's looking pretty good, and from what I saw many failures are just timeout problems.
However the situation is less clear to me against DSE 6.8, see here. Lots of unrelated failures.

Yes, even locally I'm seeing a lot of tests time out that didn't on 4.x. I've tried to raise graph.timeout to 30 seconds to see if that makes a difference, but I'm now also seeing instances of:
com.datastax.oss.driver.api.core.servererrors.InvalidQueryException: Shared data commit failed due to concurrent modification: /

Which reminds me that graph doesn't do well with concurrent schema modifications... Maybe parallelizing those tests is not such a good idea after all.

Which reminds me that graph doesn't do well with concurrent schema modifications...

This is surprising, what tests do concurrent schema modifications? Can we just exclude the ones that do so and keep the rest parallelizable?


Add NixOS module to facilitate scheduled runs

Adds a NixOS module to facilitate scheduled runs. Removing any user action should increase the number of participants in community runs.
Deployment via NixOS is as simple as:
services.kartograf = {
    enable = true;
    workers = 2;
};

The default schedule is monthly (*-*-01 00:00:00 UTC), but this is easily changed (e.g., services.kartograf.schedule = weekly;). By default,  IRR and RV data is used; this is can be changed via the useIRR and useRV settings.
I tried to avoid changes to kartograf code as much as possible, but some were necessary:

Introduce a -s/--silent option, which is enabled in the module by default, to suppress output from pandarallel progress bar to avoid spamming the systemd journal with multiple BLOB entries per second.
Introduce a -p/--workers option to set the number of threads for pandarallel to avoid hogging the CPU. (Since pandarallel is only used in the merge part, I don't see a problem with reproducibility when slowing down this part.)

The systemd job takes care of removing all data produced by kartograf except the final result to avoid filling up the file system (otherwise each run would contribute multiple GB of data, even when the --clean option is used). To avoid further changes to kartograf's code minimal, this task is handled via a systemd post-execution script.
P.S. I did not apply nixpkgs-fmt to the existing flake.nix file because I was not sure if the style was produced with a nix pretty printer I do not know. If it wasn't, let me know if it's ok to format the file.

ACK

ACK, thanks @virtu !


Test Suite

Given our current facility, we can develop a 'feedback loop' test suite,
writing a bunch of SeaQuery schema statements, execute it, run discovery,
if we got back the original schema statement, then we succeed.
This allows us to generalize testing over MySQL and Postgres.

How good is our test suite for now @billy1624 ?

Currently we only compile and run tests/discovery, tests/writer & tests/live (feedback loop) for MySQL & Postgres without asserting anything. See #21

tests/discovery & tests/writer: no assertions
tests/live: some assertions


KBFS does not handle wireless disconnect/reconnect gracefully

After sleeping my laptop and resuming, ls on a directory that does not yet exist in /keybase/public (/keybase/public/marcopolo in particular) hangs.
my log id: c7a28d51c724fc4c66d06b1c

Thanks for the report @rpglover64.
We never saw the corresponding RPCs coming into our server, so I guess the persistent connection was borked.  Looks like you gave it less than a minute before hitting ctrl-c -- I'm curious to know if it would have succeeded eventually.
As of yesterday we added TCP keep-alives on this connection, hoping to discover whether a connection is down more quickly.  So it's possible an upgrade will help the issue but I'm not sure.
@jzila  do you have any thoughts on this?  After resuming this happens in the log:
2677 2016-03-03T15:45:07.617781 ▶ [DEBU FUSE serve.go:838] a75 -> [ID=0x1d4] Release
2678 2016-03-03T15:46:33.386042 ▶ [DEBU kbfs keybase_daemon_rpc.go:187] a76 User 32abd5b8c442c4a258ae2cb33d8ff519 changed
2679 2016-03-03T16:30:21.114679 ▶ [DEBU kbfs keybase_daemon_rpc.go:164] a77 Current session logged in: rpglover64
2680 2016-03-03T16:30:21.114766 ▶ [DEBU kbfs mdserver_remote.go:160] a78 MDServerRemote: resetAuth called with a new connection
2681 2016-03-03T16:30:21.283642 ▶ [DEBU kbfs keybase_daemon_rpc.go:484] a79 new session with username rpglover64, uid 32abd5b8c442c4a258ae2cb33d8ff519, crypt public key 0121f738300edf1e51a3ee5e7ada40687e57f462cacf0e71132d5c62a68e276b7c290a, and verifying key 01207c586b52218a7d8ae1e29d5389f52961338d646d0bc8e8b80df5e4cfa49f04070a

So resetAuth is being called, but the connection doesn't seem to be up.  Could it be because we haven't go an EOF on the old connection yet?

I think RefreshAuthToken is getting called on the old connection, which sits there waiting on GetChallenge until the connection times out.

Thanks @jzila.  So you think this would be improved in today's build, with the TCP keepalives?

I'll try a repro and find out :)

Having trouble reproducing with or without KeepAlives, although the connection definitely took a while to re-establish without them (up to 10 seconds). Assuming they're not a red herring, with KeepAlives the connection was always re-established almost immediately.


some suggestions

Cool project. Respect for pulling that off.
I was reading briefly through the code and I came up with some minor suggestions.
BR,
Peter
PS: Without warranties :smile:

@tronta (Peter), some are quick wins, but some made my head reel :-) Danke.


removed extra duplicate step at the end

Description
removed extra duplicate step at the end
Changes
Tests
Known Issues
Notes
Checklist

[ ] My name is on the list of contributors (CONTRIBUTORS.md) in the pull request source branch.
[ ] I have updated the documentation to reflect my changes.

is there an option to error on a warning when we build the docs?
if yes, we might want to enable that for testing.

is there an option to error on a warning when we build the docs? if yes, we might want to enable that for testing.

yeah the option would be
mkdocs build --strict

however, when I first enabled it I was getting errors all the time and did not have time to fix them so I removed it for now. Some of the warnings that it is giving I am not sure how to fix

That's fair, something to put on the post release to-do list

That's fair, something to put on the post release to-do list

https://trello.com/c/al79B7wH


Update to 2.3.4

Update to 2.3.4. It's not a necessary update, but updating allows us to build for all platforms. Right now each version in prod has a different subset of the supported platforms.

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_197z3xht_q/clone/recipe/meta.yaml:26: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found


Wrong encoding of type variant

Candid definition:
update_secret : (text, nat64, vec SecretConsumer) -> (Result);

Autogenerated types:
type ConsumerPermissionEnum = struct {
	ReadOnly     *struct{} `ic:"ReadOnly,variant"`
	ReadAndWrite *struct{} `ic:"ReadAndWrite,variant"`
}

type SecretConsumer = struct {
	Name           string                 `ic:"name"`
	PermissionType ConsumerPermissionEnum `ic:"permission_type"`
}

Value:
consumers := []SecretConsumer{{Name: id, PermissionType: icp.ConsumerPermissionEnum{ReadAndWrite: &struct{}{}}}}

Expected Behavior
It should work
Actual Behavior
Error on canister decoding arguments:
Canister 47qyl-6qaaa-aaaaa-aabkq-cai trapped explicitly: failed to decode call arguments: Custom(Fail to decode argument 2 from table4 to vec record { name : text; permission_type : variant { ReadOnly; ReadAndWrite } }
Steps to Reproduce the Problem

Create a rust canister that has a method to call a method like this
Generate the candid definition
Create a golang client to run this method
Run that client

Specifications
Version(s):

Rust Version(s):

candid = "0.10.0"
ic-cdk = "0.12.0"
ic-cdk-macros = "0.8.2"

Golang Version(s):

github.com/aviate-labs/agent-go v0.3.1

I can confirm something is not correct on the encoding part. I used the candid cli to test the output
./didc-macos encode '("test_id_3", 11131, vec {record {permission_type = variant {ReadAndWrite}; name = "origin_1"}; })'

Result:
- 4449444c036d016c02cbe4fdc70471aaceb19508026b019ea0d3e60e7f03717c0009746573745f69645f33fbd60001086f726967696e5f3100

e, err := candid.EncodeValueString("(\"test_id_3\", 11131, vec {record {permission_type = variant {ReadAndWrite}; name = \"origin_1\"}; })")
fmt.Printf("%v \n", err)
fmt.Println(fmt.Sprintf("%x", e))

Result:
- nil
- 4449444c036b019ea0d3e60e7f6c02cbe4fdc70471aaceb19508006d0103717c0209746573745f69645f33fbd60001086f726967696e5f3100


Code generation code cleanup for thread variables usage and derivimplicit

See #43. We have been introducing more spaghetti in the code generation passes. This needs to be fixes as soon as ISPC backend and solvers are integrated/tested.

I always like to clean code, but what was the idea behind this ticket?


[PDI-14958] - Grouping in Transformation Executor stopped working

fixed job/trans execution grouping by field and by size
added unit tests

@brosander, @akhayrutdinov, please review the changes.

Recheck, please.

@akhayrutdinov, commited changes due to your comments. Recheck, please.

Checkstyle is OK.
Tests (both) are passing.
Merged.


Updated connection.js, server.js, and ./models

Updated connection and server with boiler plate to use. Set up model for what may be needed as for data.

approved.


Remove legacy kata config status parts

This PR removes parts of KataConfig.status obsoleted by #330 (and #329 before it), totalNodesCount, installationStatus, unInstallationStatus (and the stub of upgradeStatus).

Looks good with kata/peer-pods workloads

Force-push to add a commit switching envtest to the new KataConfig.status (thanks @tbuskey for pointing this out)

QE automation has already been changed to look for .status.conditions and will use  it instead if it exists

I was able to unsubscribe & resubscribe while running a kata workload
oc get kataconfig example-kataconfig -o yaml transitioned to:
apiVersion: kataconfiguration.openshift.io/v1
kind: KataConfig
metadata:
  creationTimestamp: "2023-08-16T13:50:04Z"
  finalizers:
  - kataconfiguration.openshift.io/finalizer
  generation: 2
  name: example-kataconfig
  resourceVersion: "146822"
  uid: c22a6445-8c02-47e7-80b6-eae10d2b93a3
spec:
  checkNodeEligibility: false
  enablePeerPods: false
  kataConfigPoolSelector: null
  logLevel: info
status:
  conditions:
  - lastTransitionTime: "2023-08-16T18:21:44Z"
    message: ""
    reason: ""
    status: "False"
    type: InProgress
  kataNodes:
    nodeCount: 0
    readyNodeCount: 0
  runtimeClass: kata
  waitingForMcoToStart: false

The kataNodes statuses should be 3:
tbuskey-230816-1-bjff5-worker-eastus1-2v54t   Ready    kata-oc,worker   5h35m   v1.27.3+4aaeaec
tbuskey-230816-1-bjff5-worker-eastus2-hnkcr   Ready    kata-oc,worker   5h36m   v1.27.3+4aaeaec
tbuskey-230816-1-bjff5-worker-eastus3-mc77d   Ready    kata-oc,worker   5h35m   v1.27.3+4aaeaec

I will test peer-pods & comment if it is different

When running with peerpodsEnabled: true, I was also able to unsub/sub while a peer-pors workload was running.
The kataconfig yaml transitioned to this:
apiVersion: kataconfiguration.openshift.io/v1
kind: KataConfig
metadata:
  creationTimestamp: "2023-08-16T18:57:12Z"
  finalizers:
  - kataconfiguration.openshift.io/finalizer
  generation: 2
  name: example-kataconfig
  resourceVersion: "170584"
  uid: 8d3ee88b-ff2f-48ff-befb-16487f2a2acf
spec:
  checkNodeEligibility: false
  enablePeerPods: true
  kataConfigPoolSelector: null
  logLevel: info
status:
  runtimeClass: kata
  waitingForMcoToStart: false

Deleting kataconfig puts the deletionTimestamp in the metatdata but the deletion doesn't proceed, even after 15 minutes.


[lexical-list] Bug Fix: Prevent error when calling formatList when selection is at root

Description
Currently, if the selection is at the root and you toggle one of the list options, it throws an error Error: replace: cannot be called on root nodes.
This PR fixes this by selecting the first child of the root if available, or creating a new paragraph, appending and selecting it before re-running the insertList function.
Before
https://github.com/user-attachments/assets/af17623e-5240-4552-91f3-cb01222fe703
After
https://github.com/user-attachments/assets/23e87498-03bd-45bc-a999-a61849854737

Alternatively if you really did want to recurse, you should extract the update function to a $function that is called by insertList, and that function could recurse. A unit or e2e test would also be great here to show that the problem is indeed fixed, and to prevent regressions in the future.

Thanks for the suggestions. Have updated the code to use the $isRootOrShadowRoot guard, removed the recursion and added unit tests that cover the behavior.


render replies

We get data on who a user is replying to, we should render some reply indicator

The fields in the database have been updated to follow this structure:


WIP:Remove Deprecation Warning

[DEPRECATION WARNING]: State 'installed' is deprecated. Using state 'present' instead.

Ansible 2.9 will not support state=installed (I used the web interface, so I can only propose a change to one file at a time but I suppose we should change this elsewhere too.

LGTM, just sign off as indicated by the bot above.

@tompscanlan I updated the same thing for other package managers as well. I double-checked the docs so we shouldn't get deprecation warnings any longer on all platforms.

I changed to WIP: here as well because I saw a couple of other deprecation warnings we can address here... Will push the changes tonight hopefully.

@tompscanlan I updated the role with deprecation warnings resolved. (see: https://docs.ansible.com/ansible/latest/porting_guides/porting_guide_2.7.html#using-a-loop-on-a-package-module-via-squash-actions)
Sorry about the commits being so dirty. I think it'll be a good idea to squash them before merging??

Yes, please squash.  I'm attending a conference right now, but I'll fix up the travis build and merge when I return.
Thanks for your contributions!

@tompscanlan I'll squash them from home... (and do a dry run once as well on a target). I am not using this role as-is in our setup and that's why I'm not sure if changes really work as I'm advertising

@tompscanlan did you get a chance to review?

Still traveling.   Expect I'll get there early next week. Apologies for dragging.

No worries... Was just a reminder :) Since ansible 2.9, some of the deprecation warnings got serious. I'm using a fork of your repo for now.


Persist Runtime TabTitle and  Maximize/Focus/Fullscreen states

Summary of the Pull Request
Adds additional information to the persisted window layouts.

Runtime tab titles
Focus, Maximized, and Fullscreen modes.

References

PR Checklist

[x] Closes #11878  and #11426
[x] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[ ] Documentation updated. If checked, please file a pull request on our docs repo and link it here: #xxx
[ ] Schema updated.
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Detailed Description of the Pull Request / Additional comments
Also,

Adds actions for Set{Focus,FullScreen} that take a boolean
to work in addition to the current Toggle{Focus, Fullscreen} actions.
Adds SetMaximized that takes a boolean.
This adds the capability to maximize (resp restore) a window using
standard terminal actions.
This also involves hooking up a good amount of state tracking between
the terminal page and the window to see when maximize state has changed
so that it can be persisted.
These actions are not added to the default settings, but they could be.
The intention is that they could assist with automation (and was originally)
how I planned on persisting the state instead of augmenting the LaunchMode.

Validation Steps Performed

https://user-images.githubusercontent.com/6185249/147802492-60c76c1a-7cb8-4025-9713-d251f9740cd0.mp4


Dragging the endpoints of the top x-axis zoom bar does not work correctly

Platform: Windows 10 x64 running Joulescope UI 0.6.6
While using a Joulescope in live streaming mode, dragging on the main section of the blue bar works correctly.  However, if you drag the yellow bar then it stops expanding/contracting around the mid-point then picks up again right at the end:
https://imgur.com/a/wkdRDsz
Thank you to Haly-Tom for reporting this issue over on the forum:
https://forum.joulescope.com/t/ability-to-specify-buffered-data-size/122/5

Fixed in 0.9.1.


Add a test to verify that the clamscan executable is available

🗣 Description
This pull request adds a test to verify that the clamscan executable is available.
💭 Motivation and context
This is done in response to issue #49.
🧪 Testing
All automated tests pass.
✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] Tests have been added and/or modified to cover the changes in this PR.
[x] All new and existing tests pass.

The failing tests are due to freshclam being unable to download updated signatures, as usual.  The tests all pass locally.  I'd like to go ahead and merge this PR since I cannot get the tests to pass in GH Actions, although they do eventually pass when run via APB.


Pretrained models from gdrive extraction fails, the tar files cannot be extracted

for inference or continue training from checkpoint you should not extract them. you should pass the checkpoint file for inference (as described in the readme file).
feel free to reopen if have future questions.


The box you're attempting to add doesn't support the provider hyperv

Hello! Thanks for fork kubernetes-the-hard-way
I use Windows 10 and hyperv.
vagrant up --provider=hyperv
Bringing machine 'master-1' up with 'hyperv' provider...
Bringing machine 'master-2' up with 'hyperv' provider...
Bringing machine 'loadbalancer' up with 'hyperv' provider...
Bringing machine 'worker-1' up with 'hyperv' provider...
Bringing machine 'worker-2' up with 'hyperv' provider...
==> master-1: Verifying Hyper-V is enabled...
==> master-1: Verifying Hyper-V is accessible...
==> master-1: Box 'ubuntu/bionic64' could not be found. Attempting to find and install...
    master-1: Box Provider: hyperv
    master-1: Box Version: >= 0
==> master-1: Loading metadata for box 'ubuntu/bionic64'
    master-1: URL: https://vagrantcloud.com/ubuntu/bionic64
The box you're attempting to add doesn't support the provider
you requested. Please find an alternate box or use an alternate
provider. Double-check your requested provider to verify you didn't
simply misspell it.

If you're adding a box from HashiCorp's Vagrant Cloud, make sure the box is
released.

Name: ubuntu/bionic64
Address: https://vagrantcloud.com/ubuntu/bionic64
Requested provider: [:hyperv]

Fix in PR https://github.com/mmumshad/kubernetes-the-hard-way/pull/258


Add lexer for Promela

This pull request adds a lexer for Promela. (https://spinroot.com/spin/whatispin.html)
Promela (Process Meta Language) is a C-like language used by SPIN to formally model software and hardware systems. SPIN (Simple Promela Interpreter) was originally developed in the 1980s at Bell Labs and since 1991 has been open-source and is a popular formal methods tool.
Pygments already supports other popular formal methods languages, including Isabelle, Coq, and NuSmv. Promela would be a fitting addition.
I have not included test snippets since PromelaLexer is derived from CLexer, though I have tested that it produces correct highlighting on a few of my own Promela files. Edit: I added snippets and examplefiles and ran tox -e check and tox -e mapfiles which both succeeded.

(Another potential pygments contributor here...)
You might want to add a line to the CHANGES file also.

You might want to add a line to the CHANGES file also.

Well, we (maintainers) update it ourselves; we don't ask contributors to do this. (But thank you for taking a look at the PR.)

Promela does not have all the types and keywords of C. Only the ones I specified, so inherit, was initentially left out.

Sorry for the delay. Thanks for your contribution!


Toggle overwrite mode from numeric keypad

Suggested changes to system.c to get overwrite mode to work from the numeric keypad.
static const char *numpad[] = { "end", "down", "pagedown", "left", "clear", "right", "home", "up", "pageup", "insert", "delete" };

I would also replace "" with "clear" so this key might become useful.
WINUSER.H Identifier	IBM−Compatible Keyboard
VK_CLEAR 		Numeric keyboard 5 with Num Lock OFF

Makes sense, thanks for the suggestion! Also feel free to submit PR's for stuff like this, so other peoples name appear on the commits log :smile:


Why it remove html tags inside selected element?

Why it remove html tags inside selected element?

I apologize. I don't understand the question @webcredo .

for example in this code it strip list tags and text will be shown in 1 line.

list item

list item

list item

Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.

Because (copying from the readme):

Shave is a zero dependency javascript plugin that truncates multi-line text to fit within a html element based on a set max-height.

I should clarify that more in the readme. Thanks for pointing that out @webcredo

We don't support tags within the target element.
We take the element.textContent which is a text representation of the content (no child tag markup). When we rewrite the content of the target element, any child nodes are replaced with the truncated text.
We could add a check to skip target elements which have child nodes which would be destroyed.

@webcredo I'm going to close this issue after I clarify this in the readme. @pwfisher I don't think that is necessary because that becomes an over extension of the product's goal.

@webcredo the readme is updated - see the sentence close to the bottom of the page. Thanks for pointing that out. 🙌

What if I had a p tag that contained an a tag?


Task update_package_xml does not write correct package.xml for AssignmentRules

Describe the bug
We have a DX project that is also deployed against a persistent org. In that case cumulusci deploys from /src after converting DX metadata. Package.xml is also created from /src via update_package_xml
If the DX source contains a Assignment Rule, deployment will fail immediately with:
Update of AssignmentRule package.xml: Error: You cannot install or upgrade a package that has a AssignmentRule component. Remove components of AssignmentRule type from the package.

Upon inspection cci creates the following package.xml:
    <types>
        <members>Case</members>
        <name>AssignmentRule</name>
    </types>

It should use Plural, i.e. AssignmentRules - when manually adding the Plural-s, the deploy tasks succeeds.
(Happy to patch this locally, just need a pointer)
Reproduction steps

Create CCI Project with DX Source.
Create an Pull an Assignment Rule
(observe: no issues pulling/pushing to scratch org)
connect cci to a persistent org
run deploy against persistent org
n. ...

Your CumulusCI and Python versions
cci 3.63
Operating System
Windows
Windows environment
PowerShell
CumulusCI installation method
pipx
Error Gist
No response
Additional information
No response

You could try changing this YML file:
https://github.com/SFDO-Tooling/CumulusCI/blob/main/cumulusci/tasks/metadata/metadata_map.yml#L42
Where exactly that file is on your computer is hard for me to predict. I could predict it better if you showed a stacktrace from --debug.

(My answer via email was lost)
Thanks, @prescod ! Much appreciated, I know where to go and will remember to use --debug in the future.
Should I open a PR ?

Thanks a lot, Paul. Will work with --debug in the future. I am able to
locate the file on my machine.
Should/Can I open a PR for the fix or will you create a Work Item?
Sz
On Thu, 18 Aug 2022, 19:57 Paul Prescod, @.***> wrote:

You could try changing this YML file:
https://github.com/SFDO-Tooling/CumulusCI/blob/main/cumulusci/tasks/metadata/metadata_map.yml#L42
Where exactly that file is on your computer is hard for me to predict.
I could predict it better if you showed a stacktrace from --debug.
—
Reply to this email directly, view it on GitHub
https://github.com/SFDO-Tooling/CumulusCI/issues/3331#issuecomment-1219775478,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEAGS6VTBRMSHE2PEACTMLTVZZ2PZANCNFSM565DIXQQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


There are have an error after this changes Fixes artisan serve command with PHP_CLI_SERVER_WORKERS environment variable #44204

Laravel Version: 9.31.0
PHP Version: 8.1.5
Database Driver & Version:

Description:
When I run php artisan serve command I get the following errors
https://stackoverflow.com/questions/73829417/how-can-i-fix-the-error-undefined-array-key-1-on-laravel?noredirect=1#comment130365550_73829417
Steps To Reproduce:

Can you please provide more information, such as the operating system and the output of the dump($regex, $line, $matches); variables?

We don't support microsoft Windows 8.1, sorry. Please upgrade to Windows 11.

@driesvints @taylorotwell can the information of the supported Windows version be added into official documentation?


Unable to start local cluster with new k3d and helm instructions

Expected behaviour
local deploy should work
Actual behaviour
not working
Steps to reproduce the problem
follow the readme for public ip.
missing step in readme: create /tmp/data
run k3d cluster create command
set env variables. public_ip set to the machine local network ip and ingress to false.
run the helm command
System information
Issuer node version: rancher/k3s:v1.27.4-k3s1
OS & Version: Macos M1
Browser & Version: Chrome
Logs (if needed)
Logs for: k3d-issuernode-serverlb
=======================================
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: INFO Backend set to file
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: INFO Starting confd
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: INFO Backend source(s) set to /etc/confd/values.yaml
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: DEBUG Loading template resources from confdir /etc/confd
2024/02/18 14:26:11 [notice] 34#34: using the "epoll" event method
2024/02/18 14:26:11 [notice] 34#34: nginx/1.25.1
2024/02/18 14:26:11 [notice] 34#34: built by gcc 12.2.1 20220924 (Alpine 12.2.1_git20220924-r4)
2024/02/18 14:26:11 [notice] 34#34: OS: Linux 6.5.0-10-generic
2024/02/18 14:26:11 [notice] 34#34: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2024/02/18 14:26:11 [notice] 34#34: start worker processes
2024/02/18 14:26:11 [notice] 34#34: start worker process 40
2024/02/18 14:26:11 [notice] 34#34: start worker process 41
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: DEBUG Found template: /etc/confd/conf.d/nginx.toml
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: DEBUG Loading template resource from /etc/confd/conf.d/nginx.toml
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: DEBUG Retrieving keys from store
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: DEBUG Key prefix set to /
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: DEBUG Key Map: map[string]string{"/ports/30000.tcp/0":"k3d-issuernode-server-0", "/ports/30001.tcp/0":"k3d-issuernode-server-0", "/ports/30002.tcp/0":"k3d-issuernode-server-0", "/ports/30003.tcp/0":"k3d-issuernode-server-0", "/ports/30004.tcp/0":"k3d-issuernode-server-0", "/ports/30005.tcp/0":"k3d-issuernode-server-0", "/ports/30006.tcp/0":"k3d-issuernode-server-0", "/ports/30007.tcp/0":"k3d-issuernode-server-0", "/ports/30008.tcp/0":"k3d-issuernode-server-0", "/ports/30009.tcp/0":"k3d-issuernode-server-0", "/ports/30010.tcp/0":"k3d-issuernode-server-0", "/ports/6443.tcp/0":"k3d-issuernode-server-0", "/settings/workerConnections":"1024"}
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: DEBUG Got the following map from store: map[/ports/30000.tcp/0:k3d-issuernode-server-0 /ports/30001.tcp/0:k3d-issuernode-server-0 /ports/30002.tcp/0:k3d-issuernode-server-0 /ports/30003.tcp/0:k3d-issuernode-server-0 /ports/30004.tcp/0:k3d-issuernode-server-0 /ports/30005.tcp/0:k3d-issuernode-server-0 /ports/30006.tcp/0:k3d-issuernode-server-0 /ports/30007.tcp/0:k3d-issuernode-server-0 /ports/30008.tcp/0:k3d-issuernode-server-0 /ports/30009.tcp/0:k3d-issuernode-server-0 /ports/30010.tcp/0:k3d-issuernode-server-0 /ports/6443.tcp/0:k3d-issuernode-server-0 /settings/workerConnections:1024]
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: DEBUG Using source template /etc/confd/templates/nginx.tmpl
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: DEBUG Compiling source template /etc/confd/templates/nginx.tmpl
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: DEBUG Comparing candidate config to /etc/nginx/nginx.conf
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: INFO /etc/nginx/nginx.conf has md5sum 2326fbdee1d62621c41195133ae7d401 should be<PHONE_NUMBER>8523adb59918c56b8afaf0
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: INFO Target config /etc/nginx/nginx.conf out of sync
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: DEBUG Running /usr/sbin/nginx -T -c /etc/nginx/.nginx.conf685703184
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: DEBUG "nginx: the configuration file /etc/nginx/.nginx.conf685703184 syntax is ok\nnginx: configuration file /etc/nginx/.nginx.conf685703184 test is successful\n# configuration file /etc/nginx/.nginx.conf685703184:\n###################################\n# Generated by confd 2024-02-18 14:26:11.626992974 +0000 UTC m=+0.015319488 #\n#             #######             #\n#             # k3d #             #\n#             #######             #\n###################################\n\nerror_log stderr notice;\n\nworker_processes auto;\nevents {\n  multi_accept on;\n  use epoll;\n  worker_connections 1024;\n}\n\nstream {\n\n  upstream 30000_tcp {\n    server k3d-issuernode-server-0:30000 max_fails=1 fail_timeout=10s;\n  }\n\n  server {\n    listen        30000;\n    proxy_pass    30000_tcp;\n    proxy_timeout 600;\n    proxy_connect_timeout 2s;\n  }\n\n  upstream 30001_tcp {\n    server k3d-issuernode-server-0:30001 max_fails=1 fail_timeout=10s;\n  }\n\n  server {\n    listen        30001;\n    proxy_pass    30001_tcp;\n    proxy_timeout 600;\n    proxy_connect_timeout 2s;\n  }\n\n  upstream 30002_tcp {\n    server k3d-issuernode-server-0:30002 max_fails=1 fail_timeout=10s;\n  }\n\n  server {\n    listen        30002;\n    proxy_pass    30002_tcp;\n    proxy_timeout 600;\n    proxy_connect_timeout 2s;\n  }\n\n  upstream 30003_tcp {\n    server k3d-issuernode-server-0:30003 max_fails=1 fail_timeout=10s;\n  }\n\n  server {\n    listen        30003;\n    proxy_pass    30003_tcp;\n    proxy_timeout 600;\n    proxy_connect_timeout 2s;\n  }\n\n  upstream 30004_tcp {\n    server k3d-issuernode-server-0:30004 max_fails=1 fail_timeout=10s;\n  }\n\n  server {\n    listen        30004;\n    proxy_pass    30004_tcp;\n    proxy_timeout 600;\n    proxy_connect_timeout 2s;\n  }\n\n  upstream 30005_tcp {\n    server k3d-issuernode-server-0:30005 max_fails=1 fail_timeout=10s;\n  }\n\n  server {\n    listen        30005;\n    proxy_pass    30005_tcp;\n    proxy_timeout 600;\n    proxy_connect_timeout 2s;\n  }\n\n  upstream 30006_tcp {\n    server k3d-issuernode-server-0:30006 max_fails=1 fail_timeout=10s;\n  }\n\n  server {\n    listen        30006;\n    proxy_pass    30006_tcp;\n    proxy_timeout 600;\n    proxy_connect_timeout 2s;\n  }\n\n  upstream 30007_tcp {\n    server k3d-issuernode-server-0:30007 max_fails=1 fail_timeout=10s;\n  }\n\n  server {\n    listen        30007;\n    proxy_pass    30007_tcp;\n    proxy_timeout 600;\n    proxy_connect_timeout 2s;\n  }\n\n  upstream 30008_tcp {\n    server k3d-issuernode-server-0:30008 max_fails=1 fail_timeout=10s;\n  }\n\n  server {\n    listen        30008;\n    proxy_pass    30008_tcp;\n    proxy_timeout 600;\n    proxy_connect_timeout 2s;\n  }\n\n  upstream 30009_tcp {\n    server k3d-issuernode-server-0:30009 max_fails=1 fail_timeout=10s;\n  }\n\n  server {\n    listen        30009;\n    proxy_pass    30009_tcp;\n    proxy_timeout 600;\n    proxy_connect_timeout 2s;\n  }\n\n  upstream 30010_tcp {\n    server k3d-issuernode-server-0:30010 max_fails=1 fail_timeout=10s;\n  }\n\n  server {\n    listen        30010;\n    proxy_pass    30010_tcp;\n    proxy_timeout 600;\n    proxy_connect_timeout 2s;\n  }\n\n  upstream 6443_tcp {\n    server k3d-issuernode-server-0:6443 max_fails=1 fail_timeout=10s;\n  }\n\n  server {\n    listen        6443;\n    proxy_pass    6443_tcp;\n    proxy_timeout 600;\n    proxy_connect_timeout 2s;\n  }\n\n}\n\n"
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: DEBUG Overwriting target config /etc/nginx/nginx.conf
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: DEBUG Running /usr/sbin/nginx -s reload
2024/02/18 14:26:11 [notice] 34#34: signal 1 (SIGHUP) received from 43, reconfiguring
2024/02/18 14:26:11 [notice] 34#34: reconfiguring
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: DEBUG "2024/02/18 14:26:11 [notice] 43#43: signal process started\n"
2024-02-18T14:26:11Z k3d-issuernode-serverlb confd[33]: INFO Target config /etc/nginx/nginx.conf has been updated
2024/02/18 14:26:11 [notice] 34#34: using the "epoll" event method
2024/02/18 14:26:11 [notice] 34#34: start worker processes
2024/02/18 14:26:11 [notice] 34#34: start worker process 45
2024/02/18 14:26:11 [notice] 34#34: start worker process 46
2024/02/18 14:26:11 [notice] 41#41: gracefully shutting down
2024/02/18 14:26:11 [notice] 40#40: gracefully shutting down
2024/02/18 14:26:11 [notice] 41#41: exiting
2024/02/18 14:26:11 [notice] 40#40: exiting
2024/02/18 14:26:11 [notice] 40#40: exit
2024/02/18 14:26:11 [notice] 41#41: exit
2024/02/18 14:26:11 [notice] 34#34: signal 17 (SIGCHLD) received from 40
2024/02/18 14:26:11 [notice] 34#34: worker process 40 exited with code 0
2024/02/18 14:26:11 [notice] 34#34: signal 29 (SIGIO) received
2024/02/18 14:26:11 [notice] 34#34: signal 17 (SIGCHLD) received from 41
2024/02/18 14:26:11 [notice] 34#34: worker process 41 exited with code 0
2024/02/18 14:26:11 [notice] 34#34: signal 29 (SIGIO) received
2024/02/18 14:26:24 [error] 45#45: *1 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: <IP_ADDRESS>:30001, upstream: "<IP_ADDRESS>:30001", bytes from/to client:0/0, bytes from/to upstream:0/0
2024/02/18 14:26:25 [error] 45#45: *3 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: <IP_ADDRESS>:30001, upstream: "<IP_ADDRESS>:30001", bytes from/to client:0/0, bytes from/to upstream:0/0
2024/02/18 14:26:30 [error] 45#45: *7 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: <IP_ADDRESS>:30001, upstream: "<IP_ADDRESS>:30001", bytes from/to client:0/0, bytes from/to upstream:0/0
2024/02/18 14:27:00 [error] 45#45: *13 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: <IP_ADDRESS>:30001, upstream: "<IP_ADDRESS>:30001", bytes from/to client:0/0, bytes from/to upstream:0/0

Some errors from  logs for: k3d-issuernode-agent-0
E0218 14:26:49.848177    1876 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp <IP_ADDRESS>:8080: connect: connection refused
E0218 14:26:49.848313    1876 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp <IP_ADDRESS>:8080: connect: connection refused
E0218 14:26:49.849747    1876 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp <IP_ADDRESS>:8080: connect: connection refused
E0218 14:26:49.851019    1876 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp <IP_ADDRESS>:8080: connect: connection refused

23 webhook.go:223] Failed to make webhook authorizer request: Post "https://<IP_ADDRESS>:6444/apis/authorization.k8s.io/v1/subjectaccessreviews": context canceled
E0218 14:32:49.616673      23 controller.go:146] "Failed to ensure lease exists, will retry" err="Get \"https://<IP_ADDRESS>:6444/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/k3d-issuernode-agent-0?timeout=10s\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" interval="800ms"
I0218 14:32:49.719500      23 trace.go:219] Trace[1368352604]: "Calculate volume metrics of kube-api-access-p98s9 for pod kube-system/coredns-77ccd57875-vvcdw" (18-Feb-2024 14:32:42.920) (total time: 4254ms):
Trace[1368352604]: [4.254256123s] [4.254256123s] END
W0218 14:32:48.061476      23 reflector.go:456] k8s.io/client-go@v1.27.4-k3s1/tools/cache/reflector.go:231: watch of *v1.Service ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding
W0218 14:32:49.400694      23 reflector.go:456] k8s.io/client-go@v1.27.4-k3s1/tools/cache/reflector.go:231: watch of *v1.Node ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding
E0218 14:32:50.596434      23 server.go:324] "Authorization error" err="Post \"https://<IP_ADDRESS>:6444/apis/authorization.k8s.io/v1/subjectaccessreviews\": context canceled" user="system:serviceaccount:kube-system:metrics-server" verb="get" resource="nodes" subresource="metrics"
W0218 14:32:50.698325      23 reflector.go:456] k8s.io/client-go@v1.27.4-k3s1/tools/cache/reflector.go:231: watch of *v1.RuntimeClass ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding
I0218 14:32:50.835404      23 trace.go:219] Trace[1009075909]: "iptables ChainExists" (18-Feb-2024 14:32:36.467) (total time: 13460ms):
Trace[1009075909]: [13.460280015s] [13.460280015s] END
W0218 14:32:50.871638      23 reflector.go:456] object-"default"/"private-key-secret": watch of *v1.Secret ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding

errors from logs for:
I0218 14:34:53.959508      23 status_manager.go:833] "Failed to update status for pod" pod="kube-system/metrics-server-648b5df564-9rldx" err="failed to patch status \"{\\\"metadata\\\":{\\\"uid\\\":\\\"a94edf65-d0f6-4bf0-a1f9-c32518960752\\\"},\\\"status\\\":{\\\"containerStatuses\\\":[{\\\"containerID\\\":\\\"containerd://32938cfa9551a6895b38d99b381845ba5c7ea04dd20182c966110b621ba0ce96\\\",\\\"image\\\":\\\"docker.io/rancher/mirrored-metrics-server:v0.6.3\\\",\\\"imageID\\\":\\\"docker.io/rancher/mirrored-metrics-server@sha256:c2dfd72bafd6406ed306d9fbd07f55c496b004293d13d3de88a4567eacc36558\\\",\\\"lastState\\\":{\\\"terminated\\\":{\\\"containerID\\\":\\\"containerd://7525e227faac6636d96dcce2608467900b5d825ede9a1f908b08c2075c192027\\\",\\\"exitCode\\\":0,\\\"finishedAt\\\":\\\"2024-02-18T14:30:09Z\\\",\\\"reason\\\":\\\"Completed\\\",\\\"startedAt\\\":\\\"2024-02-18T14:28:26Z\\\"}},\\\"name\\\":\\\"metrics-server\\\",\\\"ready\\\":false,\\\"restartCount\\\":2,\\\"started\\\":true,\\\"state\\\":{\\\"running\\\":{\\\"startedAt\\\":\\\"2024-02-18T14:30:11Z\\\"}}}]}}\" for pod \"kube-system\"/\"metrics-server-648b5df564-9rldx\": Patch \"https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-system/pods/metrics-server-648b5df564-9rldx/status\": http2: client connection lost"
W0218 14:34:53.959542      23 reflector.go:456] k8s.io/client-go@v1.27.4-k3s1/tools/cache/reflector.go:231: watch of *v1.Service ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding
W0218 14:34:53.959552      23 reflector.go:456] object-"kube-system"/"kube-root-ca.crt": watch of *v1.ConfigMap ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding
I0218 14:34:54.117206      23 node_lifecycle_controller.go:1027] "Controller detected that all Nodes are not-Ready. Entering master disruption mode"
W0218 14:34:53.959560      23 reflector.go:456] object-"default"/"postgres-secret": watch of *v1.ConfigMap ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding
W0218 14:34:53.959571      23 reflector.go:456] k8s.io/client-go@v1.27.4-k3s1/tools/cache/reflector.go:231: watch of *v1.Node ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding
W0218 14:34:53.959583      23 reflector.go:456] object-"kube-system"/"local-path-config": watch of *v1.ConfigMap ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding
W0218 14:34:53.959590      23 reflector.go:456] k8s.io/client-go@v1.27.4-k3s1/tools/cache/reflector.go:231: watch of *v1.RuntimeClass ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding
W0218 14:34:53.959871      23 reflector.go:456] k8s.io/client-go@v1.27.4-k3s1/tools/cache/reflector.go:231: watch of *v1.Node ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding
I0218 14:34:53.964624      23 trace.go:219] Trace[1896752470]: "Patch" accept:application/vnd.kubernetes.protobuf,application/json,audit-id:e71083b6-b1b9-46bc-b7b2-7ee563afcbea,client:<IP_ADDRESS>,protocol:HTTP/2.0,resource:pods,scope:resource,url:/api/v1/namespaces/kube-system/pods/coredns-77ccd57875-vvcdw/status,user-agent:k3s/v1.27.4+k3s1 (linux/arm64) kubernetes/36645e7,verb:PATCH (18-Feb-2024 14:33:41.708) (total time: 72255ms):
Trace[1896752470]: ---"limitedReadBody succeeded" len:723 1072ms (14:33:42.781)
Trace[1896752470]: ---"About to apply patch" 3862ms (14:33:46.658)
Trace[1896752470]: [1m12.255817839s] [1m12.255817839s] END
E0218 14:34:54.130182      23 timeout.go:142] post-timeout activity - time-elapsed: 164.286271ms, PATCH "/api/v1/namespaces/kube-system/pods/coredns-77ccd57875-vvcdw/status" result: <nil>
E0218 14:34:53.965878      23 wrap.go:54] timeout or abort while handling: method=PATCH URI="/api/v1/namespaces/kube-system/pods/coredns-77ccd57875-vvcdw/status" audit-ID="e71083b6-b1b9-46bc-b7b2-7ee563afcbea"
W0218 14:34:54.001296      23 controller.go:134] slow openapi aggregation of "middlewaretcps.traefik.containo.us": 1m13.658710131s
E0218 14:34:54.015104      23 wrap.go:54] timeout or abort while handling: method=PATCH URI="/api/v1/namespaces/kube-system/secrets/chart-values-traefik" audit-ID="9957d24d-fb7f-446a-842c-803c1471f2cf"
I0218 14:34:54.015524      23 trace.go:219] Trace[841777482]: "DeltaFIFO Pop Process" ID:v1.coordination.k8s.io,Depth:21,Reason:slow event handlers blocking the queue (18-Feb-2024 14:34:32.378) (total time: 11499ms):

time="2024-02-18T14:34:54Z" level=error msg="error syncing 'kube-system/traefik': handler helm-controller-chart-registration: failed to update kube-system/chart-values-traefik /v1, Kind=Secret for helm-controller-chart-registration kube-system/traefik: Patch \"https://<IP_ADDRESS>:6444/api/v1/namespaces/kube-system/secrets/chart-values-traefik\": http2: client connection lost, requeuing"
E0218 14:34:54.199602      23 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"http: Handler timeout"}: http: Handler timeout
E0218 14:34:54.200142      23 writers.go:122] apiserver was unable to write a JSON response: http: Handler timeout
E0218 14:34:54.200388      23 finisher.go:175] FinishRequest: post-timeout activity - time-elapsed: 241.628µs, panicked: false, err: context deadline exceeded, panic-reason: <nil>
I0218 14:34:54.202792      23 controller.go:129] OpenAPI AggregationController: action for item v1beta1.metrics.k8s.io: Rate Limited Requeue.
E0218 14:34:54.355803      23 finisher.go:175] FinishRequest: post-timeout activity - time-elapsed: 407.544944ms, panicked: false, err: context deadline exceeded, panic-reason: <nil>
I0218 14:34:54.357084      23 scope.go:115] "RemoveContainer" containerID="7525e227faac6636d96dcce2608467900b5d825ede9a1f908b08c2075c192027"
E0218 14:34:54.202950      23 kubelet.go:2281] "Skipping pod synchronization" err="container runtime is down"
E0218 14:34:54.204050      23 controller.go:146] "Failed to ensure lease exists, will retry" err="Get \"https://<IP_ADDRESS>:6443/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/k3d-issuernode-server-0?timeout=10s\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" interval="7s"

Hi @sirpy
We will check and update the readme file if needed.
You can check this https://devs.polygonid.com/docs/issuer-node/install-kubernets as well.

Hi @sirpy We will check and update the readme file if needed. You can check this https://devs.polygonid.com/docs/issuer-node/install-kubernets as well.

The issue I described is AFTER following the instructions

@martinsaporiti


How to enum as custom type?

Currently I have this:
## Invoice (object)
+ id: `1` (number)
... some other fields
+ status: `3` (enum[number])
    + Members
        + `0` - Draft
        + `1` - Unpaid
        + `2` - Partially paid
        + `3` - Paid
        + `4` - Void

Now I need to use the InvoiceStatus elsewhere as well and I don't want to repeat the members definition. So I need to define InvoiceStatus as custom type:
## Invoice (object)
+ id: `1` (number)
... some other fields
+ status: `3` (InvoiceStatus)

## InvoiceStatus (enum[number])
+ Members
    + `0` - Draft
    + `1` - Unpaid
    + `2` - Partially paid
    + `3` - Paid
    + `4` - Void

This however causes error Apiary service responded with an error: Document you are trying to publish is not valid. (expected header block, e.g. '# <text>'). How can I define such type then? What I need to achieve is basically array[InvoiceStatus] for my filtering API.

@enumag + Members directive isn't correct for a data structure, only when you are embedding data structures inside another.
You can remove + Members as follows:
# Data Structures

## Invoice (object)
+ id: `1` (number)
+ status: `3` (InvoiceStatus)

## InvoiceStatus (enum[number])
+ `0` - Draft
+ `1` - Unpaid
+ `2` - Partially paid
+ `3` - Paid
+ `4` - Void

Or convert Members to a heading as follows:
# Data Structures

## Invoice (object)
+ id: `1` (number)
+ status: `3` (InvoiceStatus)

## InvoiceStatus (enum[number])

### Members

+ `0` - Draft
+ `1` - Unpaid
+ `2` - Partially paid
+ `3` - Paid
+ `4` - Void

@kylef Thanks!


Fixed Teams Page CSS #393

please check this PR instead of previous PR #419
solving the issue #393

please checck the PR

@dhairyagothi please stop working on team page to make responsive.

If you want to work on this issue, let me know and share some idea on discord.


Doc page contributors

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Description
Similar to last updated by in the Doc footer where it states the dev who last update a file, there should be an option for listing all the contributors for that specific page.
Here is an imagined UI design for it:

I found that this feature is discussed here
Has this been requested on Canny?
No response
Motivation
Some docs involved many people not necessarily the core team only, e.g. non-profit organisation where people voluntarily contribute to certain doc and those people need to be mentioned not only the last one.
API design
So this is github based so no need for the users to add any components by themselves.
I think it should be enabled/disabled via the config file
Have you tried building it?
I tried to follow the same approach of last updated by by ejecting the doc footer component but that went without luck as I saw it uses useDoc hook so I feel that I couldn’t edit it.
Self-service

[X] I'd be willing to contribute this feature to Docusaurus myself.

Duplicate of #6218

Your mocked UI looks great btw, feel free to re-post under #6218

@osamajandali Can you post the code you used to get this result?
Thanks


unable to login

Hello,
I am using mg ismart to connect to MG hector petrol suv.
But it keeps throwing the following error:
"Failed to authenticate, please check your credentials."
I am sure the username/credentials are fine, because I am able to login to my mobile app.
Please help.

Hi,
Do you have special characters on your password? If that's the case, you need to change it on the iSmart app, as the API does not allow special characters.

Hi, I am not able to set a password without special character in ismart. It says atleast one special character is a must.

That's quite odd. Some time ago I could change the password and do not use special characters.
I'm sorry, but I cannot help on that right now. I was checking again and the API does not accept symbols. Let me see if I mind a workaround, but does not seem something easy.

Sure thank you 👍
On Wed, 23 Oct, 2024, 1:44 pm Alvaro Duarte, @.***>
wrote:

That's quite odd. Some time ago I could change the password and do not use
special characters.
I'm sorry, but I cannot help on that right now. I was checking again and
the API does not accept symbols. Let me see if I mind a workaround, but
does not seem something easy.
—
Reply to this email directly, view it on GitHub
https://github.com/ad-ha/mg-saic-ha/issues/12#issuecomment-2431251646,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BMKXSTQJ5FMJ2CFI66UTFWLZ45LGNAVCNFSM6AAAAABQM7VPECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZRGI2TCNRUGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

I will close this as it is not an actual issue from the integration, but a bug from the API.
Cheers


Add YAMLs for SN002/V1_2

Thanks to:

#240

Adding the configuration files for the SN002/V1_2 robot is easy.
After merging it I will run the creo2urdf-private action for generating the urdfs
cc @pattacini @traversaro @GiulioRomualdi

I had to fix these files:

https://github.com/icub-tech-iit/ergocub-software/commit/eda40cd321dd88bb210ce671692b4b800cc57eb6

I was relying on includes recusively that for now are not implemented in creo2urdf


installs in non standard location on windows.

hello,
the atom installer put the executable in
C:\Users\myusername\AppData\Local\atom\app-1.2.4
Is there is no way to put it in C:\Program Files or elsewhere ?
I'll can't use this as it is now.

1.3 supports "portable mode" which should solve this problem: https://github.com/atom/atom/pull/8442

You can also install to Program Files using AtomSetup.exe --machine.


cleanup code. use constants

I cleanup code - remove unused code.
Constants have better precission for PI based consts.
Precalculated typical PI uses

Thanks for the effort, but these changes won't be necessary since I'm planning a larger re-write of the backend GLSL code in the future. There are many other places in the code that needs a re-touch, so I'll address them when the time comes.


Bad regex causing failure

Thanks Mike Penz for fast response on my last ticket.
It seems that some new bug got introduced, which seems to me to be from the fork?
https://github.com/mikepenz/action-junit-report/blob/main/dist/index.js#L160
As you see here, this regex is taking the string for the name of the workflow, and I believe the + sign in c++ causes it to interfere with the regex. I'll try changing to cxx as a temporary workaround. An example of this failure you can see here:
https://github.com/csound/csound/actions/runs/492358430
ADDED: The test case containing "c++" isn't failing anymore and the action runs fine now, so it's only a problem for failing test cases.

Not sure this is introduced. As the same code already existed in the previous release: https://github.com/mikepenz/action-junit-report-legacy/blob/main/utils.js#L8
Let me see to add a test case in the demo data which contains a + sign

Not sure this is introduced. As the same code already existed in the previous release: https://github.com/mikepenz/action-junit-report-legacy/blob/main/utils.js#L8
Let me see to add a test case in the demo data which contains a + sign


Windows: If rendering takes over 4 seconds, visualizer won't update

OS: Windows 10
Machine tested: cisl-gadsden
If a rendering takes over approximately 4 seconds, the visualizer window will not update. This is a different issue from a single OpenGL rendering taking more than 4 seconds which will cause Windows to kill your application. This can be caused by a CPU intensive operation such as loading data, or by a long OpenGL rendering (split into chunks).
An easy way to reproduce this is by adding a Sleep(5000) in a renderer's paintGL function. (On windows it's Sleep(millis) which is defined in Windows.h)
It appears to only exist in the ray branch

Seems to have fixed itself after restarting the laptop


fix: correct api version in oauth-installed.md

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

@googlebot I signed it!

Thanks for fixing this, @ryan4yin!


(k9s) Switch AU to Get-GitHubRelease

(k9s) Switch AU to Get-GitHubRelease
Description
Switch the method used by update.ps1 to get the release download url from the GitHub releases pages from a simple Invoke-WebRequest to Get-GitHubRelease script
Motivation and Context
update.ps1 script no longer works ( fix #1999 ) because of the GitHub frontend changes ( #2007 )
How Has this Been Tested?
Contains minimal changes tested locally
Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[X] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] I have updated the package description and it is less than 4000 characters.
[X] All files are up to date with the latest Contributing Guidelines
[ ] The added/modified package passed install/uninstall in the chocolatey test environment.
[X] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review

@AdmiringWorm we need your help :) Could you review and complete the PR please?

@moebius87 Please don't ping people on PR reviews. @AdmiringWorm is not the only person who can review PR's in here.

I'm sorry @pauby it was only because I saw that he was the last active user on the project. You're right, I won't do it again.

update.ps1 run fails:
PS C:\Users\vagrant\Desktop\k9s> .\update.ps1
k9s - checking updates using AU version 2022.10.24

URL check
Can't validate URL
Exception calling "GetResponse" with "0" argument(s): "The request was aborted: The connection was closed
unexpectedly.":https://github.com/derailed/k9s/releases/download/v0.27.0/
At C:\Program Files\WindowsPowerShell\Modules\AU\2022.10.24\Public\Update-Package.ps1:110 char:67
+ ... heck_url $url -Options $Latest.Options) { throw "${res}:$url" } else  ...
+                                               ~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Can't validate ...wnload/v0.27.0/:String) [], RuntimeException
    + FullyQualifiedErrorId : Can't validate URL
    Exception calling "GetResponse" with "0" argument(s): "The request was aborted: The connection was closed unexpectedly.":https://github.com/derailed/k9s/releases/download/v0.27.0/

It looks like the regular expression isn't being matched so the URL's are not being formed properly. The releases of this software don't always include a Windows_x86_64.tar.gz (v0.27 for example does not).


fixed virtual machine name validation

Goodness squad fixes #382

This change is

GoodnessSquad participants don't have engine available so addressing comments is not expected. Commit reused in pull #429.


Change GitHub Repository for Amplify Project Without Creating a New App

Environment information
Im using Amplify gen2 to backend and hosting and webapp in Flutter

Description
Hi!
I need to change the GitHub repository my Amplify project uses because I am moving it from my personal profile to my organization’s profile. I have not found a way to do this without creating a new app.
Is there a way to change the linked GitHub repository for an existing Amplify project without starting a new app from scratch?

Hi @ferrivitor 👋 , thanks for reaching out. In scenarios where you need to change the repository associated with an existing AWS Amplify application, our general recommendation is to create a new Amplify app. However, if you absolutely need to switch the repository on an existing application, I would recommend testing the following flow on a non-production application first:
You can leverage the update-app API for this use case.
Prerequisite: Amplify GitHub app must be installed in the target GitHub organization
aws amplify update-app --app-id <app_id_value> --repository <new_repository_url> --access-token <github_personal_access_token>

Replace the placeholders with the appropriate values:

<app_id_value>: The ID of the existing Amplify app you want to update.
<new_repository_url>: The URL of the new repository you want to associate with the app.
<github_personal_access_token>: A GitHub personal access token with appropriate permissions to access the new repository.

Please note that switching the repository for an existing Amplify app is not a recommended practice and may lead to unexpected behavior or issues. It's generally safer to create a new Amplify app and associate it with the desired repository.

Hi Jay! Is rhis solution viable for gen2 apps too?
Thanks in advance!

Yes, its applicable to all Amplify apps (Gen 1 and 2).

Hi! I tried these steps after renaming my existing GitHub repository and it broke branch auto deployments. I even tried deleting the Amplify GitHub app from the repo and reconnecting, and deleting the linked branches in amplify and reconnecting them. I now have no way of deploying my amplify app. Any recommendations (other than creating a new amplify app)?

Hi @ferrivitor 👋 , thanks for reaching out. In scenarios where you need to change the repository associated with an existing AWS Amplify application, our general recommendation is to create a new Amplify app. However, if you absolutely need to switch the repository on an existing application, I would recommend testing the following flow on a non-production application first:
You can leverage the update-app API for this use case.
Prerequisite: Amplify GitHub app must be installed in the target GitHub organization
aws amplify update-app --app-id <app_id_value> --repository <new_repository_url> --access-token <github_personal_access_token>

Replace the placeholders with the appropriate values:

<app_id_value>: The ID of the existing Amplify app you want to update.
<new_repository_url>: The URL of the new repository you want to associate with the app.
<github_personal_access_token>: A GitHub personal access token with appropriate permissions to access the new repository.

Please note that switching the repository for an existing Amplify app is not a recommended practice and may lead to unexpected behavior or issues. It's generally safer to create a new Amplify app and associate it with the desired repository.


Composer custom vendor dir

if i set config > vendor-dir in my composer.json to somewhere other than "vendor" then i get this error while running a composer update command:
[Composer\Downloader\TransportException]
The "https://nodejs.org/dist/v4.1.2/node-v4.1.2-linux-x64.tar.gz" file could not be written to vendor/node-v4.1.2-linux-x64.tar.gz: failed to open stream: No such file or directory
I assume this is because that config is not being picked up.

Please report this bug to https://github.com/thecodingmachine/nodejs-installer
Possible workaround: install nodejs globally (thru your package manager) and nodejs-installer won't need to download it locally.


Storage File Share Readme Issue

Section Link

Suggestion:
Add a summary of examples. As follows:

Section Link

Reason: missing AnonymousCredential
Suggestion:
1、Update to => const { ShareServiceClient, AnonymousCredential } = require("@azure/storage-file-share");
2、Update to =>
const anonymousCredential = new AnonymousCredential();
const serviceClient = new ShareServiceClient(`https://${account}.file.core.windows.net${sas}`, anonymousCredential);

@jongio for notification.

Regarding 2: AnonymousCredential is optional when SAS token is used. Is the code not running as expected with a valid SAS?

@jeremymeng - You're right. If there is no AnonymousCredential, the code can work normally with a valid SAS.
Thank you for your advice. I've updated it.


Add Herringbone Tiling node

Adding Herringbone Tilling node to procedural nodes set. (Including ping-pong Node).

Example for Herringbone Tilling node output:

I pushed an updated version including Triangle wave node. Kindly check it and let me know if you have any comments!

@Cinifreak This looks promising, though I believe you need to resolve merge conflicts between your change and previous ones, using the "Resolve Conflicts" button above.

@Cinifreak I wonder if it's worthwhile to consider the alternative approach to Herringbone Tiling shown in this GitHub Issue?
https://github.com/AcademySoftwareFoundation/MaterialX/issues/1415
In this alternative version, it looks like Herringbone Tiling is implemented in terms of the newly-proposed line node, which would add support for rounded corners, and might lead to a simpler definition.
What are your thoughts?

Is there a PR for line node so I can get the idea ?

about rounded edge, We can add this feature if there is a request for that to be implemented.

@Cinifreak The line node is part of this pull request for 2D shapes:
https://github.com/AcademySoftwareFoundation/MaterialX/pull/1411
Although the rounded corners could be a nice side benefit, I'm imagining the larger potential benefit being a simpler graph implementation, since we're aiming to keep our graph definitions as minimal as possible for efficiency in shader generation and application start-up overhead.
I'm open to a discussion about which implementation would be ideal for MaterialX, and I primarily want to make sure we're fully considering all options before committing to an approach.

@Cinifreak The recent work in #1411 is now merged, and I think the best path forward would be to implement the herringbone pattern in terms of the new line node if possible, so that there's consistency with other line patterns such as grid and crosshatch.  Let us know what your thoughts are!

I'll close out this original proposal, since the new implementation of herringbone is likely to use a different approach, and it deserves its own pull request.  Thanks for putting this together and getting the discussion started!


Cannot use VSCode extension because Plank pod doesn't start up

or cannot be started for some reason. I'm getting this:
serviceaccounts "squash-plank" not found Error: serviceaccounts "squash-plank" not found Usage: squashctl [flags] squashctl [command] Available Commands: completion generate auto completion for your shell deploy deploy squash or a demo microservice help Help about any command squash manage the squash utils call various squash utils Flags: --container string Container to debug --container-repo string debug container repo to use (default "quay.io/solo-io") --container-version string debug container version to use (default "0.5.1") --crisock string The path to the CRI socket (default "/var/run/dockershim.sock") --debugger string Debugger to use -h, --help help for squashctl --json output json format --localport int local port to use to connect to debugger (defaults to random free port) --machine ...

It seem's that this issue is resolved via # #146.
I checked that the demo case works well in my mac OS.

Env: Mac Mojave, kubectl v1.13.4, minikube v0.35.0, squashctl v0.5.5, vscode extension v0.5.5, vscode v1.32.1
@mitchdraft could you close this issue? Thanks!

glad this is working for you @sanha , yes, there was an issue with the download path for squash v0.5.4
thanks for flagging this issue, closing


Pull request comment has incorrect information

When it comments on a pull request, it says the orb will expire in 30 days, it should say 90 days.

@Gaardsholt , thank you for your support and the correction with this orb documentation.
After checking that the fix is valid I accepted your change and created a new patch.

I will move your PR here: https://github.com/CircleCI-Public/orb-tools-orb/pull/240 to solve the current issue while running the circleci internal pipelines.


Bugfix: Fix PHP8.2 compatibility

$data on line 47 is not defined and therefore gives an error on PHP8.2. This fixes the following error:
An exception has been thrown during the rendering of a template ("Creation of dynamic property PedroBorges\KirbyMetaTags\MetaTags::$data is deprecated").

@pedroborges ?


Valine comment plugin does not work with LeanCloud International

As far as I can tell, both listed comments plugins don't work very well, but the valine plugin refuses to work, at least when I use a key from LeanCloud International.
Console upon page load:
index_prod-2141a5c8.js:1  ReferenceError: _ is not defined
    at setup (index_prod-2141a5c8.js:34:28892)
    at cn (index_prod-2141a5c8.js:1:13506)
    at Yf (index_prod-2141a5c8.js:1:52630)
    at Gf (index_prod-2141a5c8.js:1:52415)
    at $ (index_prod-2141a5c8.js:1:39684)
    at m (index_prod-2141a5c8.js:1:39577)
    at C (index_prod-2141a5c8.js:1:36439)
    at D (index_prod-2141a5c8.js:1:37895)
    at Y (index_prod-2141a5c8.js:1:46067)
    at Object.process (index_prod-2141a5c8.js:1:46101)
Y0 @ index_prod-2141a5c8.js:1
index_prod-2141a5c8.js:77  Aurora is developed by TriDiamond https://github.com/auroral-ui/hexo-theme-aurora
index_prod-2141a5c8.js:67  ReferenceError: AV is not defined
    at a7.initLeancloud (index_prod-2141a5c8.js:67:2774)
    at new a7 (index_prod-2141a5c8.js:67:2374)
    at s (index_prod-2141a5c8.js:67:5861)
    at index_prod-2141a5c8.js:1:23998
    at cn (index_prod-2141a5c8.js:1:13506)
    at wt (index_prod-2141a5c8.js:1:13585)
    at Mo.t.__weh.t.__weh (index_prod-2141a5c8.js:1:23878)
    at Gs (index_prod-2141a5c8.js:1:2110)
    at Jr.z [as fn] (index_prod-2141a5c8.js:1:40446)
    at Jr.run (index_prod-2141a5c8.js:1:4979)
initLeancloud @ index_prod-2141a5c8.js:67
index_prod-2141a5c8.js:67  Uncaught (in promise) ReferenceError: AV is not defined
    at a7.queryAll (index_prod-2141a5c8.js:67:3378)
    at index_prod-2141a5c8.js:67:3908
    at new Promise (<anonymous>)
    at a7.getRecentComments (index_prod-2141a5c8.js:67:3887)
    at s (index_prod-2141a5c8.js:67:6080)
    at index_prod-2141a5c8.js:1:23998
    at cn (index_prod-2141a5c8.js:1:13506)
    at wt (index_prod-2141a5c8.js:1:13585)
    at Mo.t.__weh.t.__weh (index_prod-2141a5c8.js:1:23878)
    at Gs (index_prod-2141a5c8.js:1:2110)
index_prod-2141a5c8.js:1  ReferenceError: Valine is not defined
    at a (Comment-14d48132.js:2:751)
    at Comment-14d48132.js:2:1325
    at index_prod-2141a5c8.js:1:23998
    at cn (index_prod-2141a5c8.js:1:13506)
    at wt (index_prod-2141a5c8.js:1:13585)
    at Mo.t.__weh.t.__weh (index_prod-2141a5c8.js:1:23878)
    at Rc (index_prod-2141a5c8.js:1:14879)
    at Nc (index_prod-2141a5c8.js:1:15186)
Y0 @ index_prod-2141a5c8.js:1
index_prod-2141a5c8.js:1  ReferenceError: Prism is not defined
    at d (Post-1a65712f.js:1:1077)

Hey @makinbacon21, thanks for posting an issue. Have you try hexo clean && hexo generate && hexo server ? This looks like the latest scripts are not generated. Just to be sure you have installed the latest hexo-plugin-aurora right?

sigh you are correct. was missing some packs and wasnt cleaning and generating--works now :)


Allow setting Github team/more individuals to get tagged when publishing

A request regarding the information in: https://github.com/bazel-contrib/publish-to-bcr#a-note-on-release-automation.
As I understand it, we'd need to set a single GitHub user in config.yml in order to have tagging from the BCR PR to work correctly. That field also seems to configure the token used for the fork/PR, what we'd like:

Use the GitHub action bot to create the PR, don't mind if thats the associated committer (since GitHub teams can't be commit authors)
Allow setting list of other GitHub individuals/teams to tag on the BCR PR

Use the GitHub action bot to create the PR, don't mind if thats the associated committer (since GitHub teams can't be commit authors)

The Publish to BCR app bot is always the creator of the pull request. I'm assuming that's in line with what you meant here?

Allow setting list of other GitHub individuals/teams to tag on the BCR PR

I see. So you would like to just tag arbitrary people on the PR but continue to use your main org's fork of the BCR for the source of the pull requests?

The Publish to BCR app bot is always the creator of the pull request. I'm assuming that's in line with what you meant here?

Sorry, yep thats what I meant.

I see. So you would like to just tag arbitrary people on the PR but continue to use your main org's fork of the BCR for the source of the pull requests?

Yeah exactly!

I see. So you would like to just tag arbitrary people on the PR but continue to use your main org's fork of the BCR for the source of the pull requests?

Yeah exactly!

That should be fairly easy to do and I think it's a useful thing to add. I'll label this as an enhancement and pick it up when I get the chance.

Perfect, thanks for the quick response!

In the meantime you can just continue to not set a fixedReleaser. The app should work—you just won't receive a notification for the pull requests or be notified of any errors.

Rather than adding more configuration for additional taggers, I'm thinking that I will always tag everyone listed as a maintainer in metadata.json.

Makes sense to me!

Hm though in our case, it's a Google group email and not an actual GitHub account.
Would it email as well?

Ah, looking at your metadata file:
https://github.com/bazelbuild/bazel-central-registry/blob/main/modules/rules_ios/metadata.json#L3
There is another field for a maintainer that most other modules have, github, which points to the GitHub username of the maintainer. I'm not able to find docs on the schema, and I guess there isn't validation for that field since you don't have it for your module.
The idea was to send any error emails to the maintainer emails and tag their github handles in the PR comment. The latter won't work for your case since the group won't have a github user. You could add a github field and set an arbitrary user, but then only one person would be tagged and perhaps you wanted multiple. So maybe I do just need some additional configuration in config.yml to add additional users to be tagged..

@meteorcloudy Is there a schema for the list of maintainers in metadata.json? Are the fields arbitrary?

Yeah, it should look like:
     [{"name": "John Cater", "email"<EMAIL_ADDRESS>       {"name": "Yun Peng", "github": "meteorcloudy"}]

as it's described here: https://docs.google.com/document/d/1moQfNcEIttsk6vYanNKIy3ZuK53hQUFq1b1r0rmsYVg/edit#bookmark=id.1i90c6c14zvx

@luispadron I deployed the changes in https://github.com/bazel-contrib/publish-to-bcr/pull/75, which will tag any maintainers with a github field in the BCR pull request. You could add any users you want to tag in addition to the group email that you already have.
I wanted to check if the above is sufficient for your use case, or if you think there's still a need for the other solution we discussed: a config.yml setting to just add additional github handles to tag in the pr.

I think that resolves this issue and it make sense it's not possible to tag non GitHub users.
I think in the future it would be nice to be able to receive email notifications for releases and such if folks want to manage this via a mailing list vs. maintaining this list.


[bug] no query_mode argument for sentence transformers encode

I haven't been able to find any documentation on the query_mode argument to encode.  I believe this is the right fix.

Hi @snewcomer this parameter query_mode add a distinct prefix token such as '[Q]' for queries and '[D]' for documents. I think you are initializing the ColBERT model using a Sentence Transformer but as you can see in the doctoring, you need to pass the sentence transformer checkpoint name (folder name, available locally or on hugging face) rather than the Sentence Transformer model itself
import torch

from neural_cherche import models, utils, train

model = models.ColBERT(
    model_name_or_path="sentence-transformers/all-mpnet-base-v2",
    device="cuda" if torch.cuda.is_available() else "cpu"
)

Thanks Raphael!  You are right.  This is clearly the wrong fix.  I thought I was hitting an error with query_mode passed to either the tokenizer to the sentence transformers encode via kwargs but I'm not able to reproduce anymore.  Closing!


ArrayBuffer is deprecated in XMLHttpRequest.send(). Use ArrayBufferView instead.

In my phonegap app in console , it will output this warning
It tested on android 4.4.2 devise

Bumped to 1.4.

According to this https://github.com/socketio/engine.io-client/issues/372, it should be fixed now. Please reopen if needed.


OAK-10330: oak-it-osgi: temporarily introduce Guava dependency again

Tests in oak-it-osgi look good. Merging...


Update Wikimate::token() to remember CSRF token (fixes #115)

See issue #115. Storing and re-using the token reduces the number of API calls when invoking multiple edit/delete/etc actions in a session, as is typical bot behavior.
The error value of token() is also changed to null (false should only be used by boolean methods). Since token() is an internal method, I don't consider this an API-breaking change.

Not really, but I think I'll need to rebase/push for the merge conflict first, right?

I think it's nice to rebase even when there aren't conflicts, to avoid crossing branches and provide a semi-linear git graph. :)


ARROW-5212: [Go] Support reserve for the data buffer in the BinaryBuilder

Oh, I need to update the commit message. I wrote it with both reserve and resize but ended up only keeping reserve.

(I'll wait a bit to give a chance to @alexandreyc to comment.)

thanks @sbinet – I thought I tagged you too 👍

Codecov Report

Merging #4204 into master will increase coverage by 0.02%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #4204      +/-   ##
=========================================
+ Coverage   87.58%   87.6%   +0.02%
=========================================
  Files         655     684      +29
  Lines       71866   87062   +15196
  Branches     1251       0    -1251
=========================================
+ Hits        62944   76275   +13331
- Misses       8805   10678    +1873
+ Partials      117     109       -8

Impacted Files
Coverage Δ

go/arrow/array/binarybuilder.go
86.36% <0%> (-5.21%)
:arrow_down:

cpp/src/arrow/util/thread-pool-test.cc
97.66% <0%> (-0.94%)
:arrow_down:

cpp/src/plasma/thirdparty/ae/ae.c
70.75% <0%> (-0.48%)
:arrow_down:

js/src/compute/dataframe.ts

js/src/util/recordbatch.ts

js/src/ipc/metadata/message.ts

js/src/visitor/jsonvectorassembler.ts

js/src/visitor/jsontypeassembler.ts

js/src/visitor/toarray.ts

js/src/ipc/message.ts

... and 230 more

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 c3511db...536861e. Read the comment docs.

ah. @jsternberg could you add a test for this API?
thanks.

I updated the code with a test. The test calls ReserveData and then appends data to it and ensures the capacity doesn't change after the call to ReserveData.

thanks!


[Resolver] Docker error fetching server API version

Hello,
when running openhands resolver I got the following error log
Command run:  python -m openhands_resolver.resolve_issues --repo NaturalAgents/NaturalAgents --issue-numbers 4
Error log:
22:55:27 - openhands:INFO: resolve_issues.py:447 - Limiting resolving to issues [4].
22:55:27 - openhands:INFO: resolve_issues.py:459 - Using output directory: output
22:55:27 - openhands:INFO: resolve_issues.py:483 - Base commit: 196e5ce6afa0c4412e40eebc947188895730bcdc
22:55:27 - openhands:INFO: resolve_issues.py:494 - Writing output to output/output.jsonl
22:55:27 - openhands:WARNING: resolve_issues.py:501 - Output file output/output.jsonl already exists. Loaded 0 finished issues.
22:55:27 - openhands:INFO: resolve_issues.py:506 - Resolving issues with Agent CodeActAgent, model gpt4o, max iterations 30.
22:55:27 - openhands:INFO: resolve_issues.py:518 - Finished issues: 0, Remaining issues: 1
  0%|                                                                                | 0/1 [00:00<?, ?it/s]22:55:27 - openhands:INFO: resolve_issues.py:526 - Using 1 workers.
22:55:27 - openhands:INFO: resolve_issues.py:264 - Starting fixing issue 4.
22:55:27 - openhands:INFO: main.py:73 - Initializing runtime: EventStreamRuntime
22:55:27 - openhands:ERROR: runtime.py:200 - Launch docker client failed. Please make sure you have installed docker and started docker desktop/daemon.
ERROR:root:  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/site-packages/openhands_resolver/resolve_issues.py", line 720, in <module>
    main()
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/site-packages/openhands_resolver/resolve_issues.py", line 700, in main
    asyncio.run(
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/asyncio/runners.py", line 190, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/asyncio/base_events.py", line 654, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/site-packages/openhands_resolver/resolve_issues.py", line 556, in resolve_issues
    await asyncio.gather(*[run_with_semaphore(task) for task in tasks])
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/site-packages/openhands_resolver/resolve_issues.py", line 554, in run_with_semaphore
    return await task
           ^^^^^^^^^^
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/site-packages/openhands_resolver/resolve_issues.py", line 397, in update_progress
    resolved_output = await output
                      ^^^^^^^^^^^^
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/site-packages/openhands_resolver/resolve_issues.py", line 292, in process_issue
    runtime = create_runtime(config, sid=f"{issue.number}")
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/site-packages/openhands/core/main.py", line 74, in create_runtime
    runtime: Runtime = runtime_cls(
                       ^^^^^^^^^^^^
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/site-packages/openhands/runtime/client/runtime.py", line 138, in __init__
    self.docker_client: docker.DockerClient = self._init_docker_client()
                                              ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/site-packages/openhands/runtime/client/runtime.py", line 203, in _init_docker_client
    raise ex
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/site-packages/openhands/runtime/client/runtime.py", line 198, in _init_docker_client
    return docker.from_env()
           ^^^^^^^^^^^^^^^^^
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/site-packages/docker/client.py", line 94, in from_env
    return cls(
           ^^^^
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/site-packages/docker/client.py", line 45, in __init__
    self.api = APIClient(*args, **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/site-packages/docker/api/client.py", line 207, in __init__
    self._version = self._retrieve_server_version()
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rohitmalhotra/miniconda3/lib/python3.11/site-packages/docker/api/client.py", line 230, in _retrieve_server_version
    raise DockerException(

ERROR:root:<class 'docker.errors.DockerException'>: Error while fetching server API version: Not supported URL scheme http+docker
  0%|

I resolved the issue via pip3 install requests==2.31.0 . I found the solution from this thread on stackoverflow: https://stackoverflow.com/questions/64952238/docker-errors-dockerexception-error-while-fetching-server-api-version
Wanted to attach this incase anyone else was facing this issue; cheers!

Moved from All-Hands-AI/openhands-resolver#172

I get a similar error when I try to load a zip project into the frontend:
  File "/Users/boris/Library/Caches/pypoetry/virtualenvs/openhands-ai-ZaE4x3ag-py3.12/lib/python3.12/site-packages/docker/api/client.py", line 230, in _retrieve_server_version
    raise DockerException(
docker.errors.DockerException: Error while fetching server API version: ('Connection aborted.', FileNotFoundError(2, 'No such file or directory'))

The pip3 install requests==2.31.0 didn't seem to fix this.


resvg: 0.35.0 -> 0.36.0

Diff: https://github.com/RazrFalcon/resvg/compare/v0.35.0...v0.36.0
Changelog: https://github.com/RazrFalcon/resvg/blob/v0.36.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

3 packages built:

nanoemoji
nanoemoji.dist
resvg


Licensing

I'd like to know if this project is MIT licensed or something similar. I'd like to use it in a project but I can't do this if it doesn't have an explicit license.
Thanks.

We currently do not have a license, but feel free to use this project as you please. We will look into what needs to happen to make our project MIT licensed ASAP.
Thanks

@coolbnjmn Adding a license is pretty straightforward. All you need to do is to add the MIT license text (http://opensource.org/licenses/MIT) to a 'LICENSE' file in the root and add a note to the Readme that the project is licensed under MIT. It might be a good idea to add something akin to "Licensed under the terms of the MIT license" to the code files as well.

@joshuawilde Added the licensing terms everywhere, it is now under the MIT license.
Thanks


Crashlytics for Android generates conflicting provider

Like #444 and #2141
    <provider
        android:name="com.crashlytics.android.CrashlyticsInitProvider"
        android:exported="false"
        android:authorities="bpu.aimei.crashlyticsinitprovider"
        android:initOrder="100" />

    <provider
        android:name="com.crashlytics.android.CrashlyticsInitProvider"
        android:exported="false"
        android:authorities="dollar_openBracket_applicationId_closeBracket"
        android:initOrder="100" />

I'm still getting the issue where it generates the duplicate providers where one is correct but a second one with dollar_openBracket_applicationId_closeBracket is also added.
Visual Studio 2017

Xamarin.Android.Fabric v1.4.3
Xamarin.Android.Crashlytics.Core v2.6.3
Xamarin.Android.Crashlytics.Beta v1.2.9
Xamarin.Android.Crashlytics.Answers v1.4.2
Xamarin.Android.Crashlytics v<IP_ADDRESS>
Xamarin.Build.Download v0.4.11

Hi, Is there any update on the matter?
With this issue, I can not publish two different apps using Fabric in Xamarin.
A user can not possibly install two apps at the same time with this issue. Even If I didn't develop both apps, and someone else developed an app which implements fabric and the user tries to install my app, the user will get an error on the Play Store.
Please, this is urgent.
This line should be excluded somehow... <provider android:name="com.crashlytics.android.CrashlyticsInitProvider" android:authorities="dollar_openBracket_applicationId_closeBracket" android:exported="false" android:initOrder="100" />

I have done more testing on this and got it to build without the duplicate "bad" line.
In the Obj/[debug/release]/[monoversion=90]/  you end up with folders:

android
assets
...
lp <--- IN THIS FOLDER
proguard
...

In my case 28/jl/AndroidManifest.xml is the manifest for Fabric and looks like the following:
<?xml version="1.0" encoding="utf-8"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" xmlns:tools="http://schemas.android.com/tools" package="com.crashlytics.android" android:versionCode="1" android:versionName="2.9.4">     <uses-sdk android:minSdkVersion="9" />     <uses-permission android:name="android.permission.INTERNET" />     <application>         <provider android:name="com.crashlytics.android.CrashlyticsInitProvider" android:authorities="${applicationId}.crashlyticsinitprovider" android:exported="false" android:initOrder="100" />     </application> </manifest>
If I modify the <provider... line and simply Build my project, the modification shows up in the final AndroidManifest.xml but the "bad" line still co-exists:
<provider android:name="com.crashlytics.android.CrashlyticsInitProvider" android:authorities="com.my.app.crashlyticsinitprovider" android:exported="true" android:initOrder="100" />     <provider android:name="com.crashlytics.android.CrashlyticsInitProvider" android:authorities="dollar_openBracket_applicationId_closeBracket" android:exported="false" android:initOrder="100" />
If I remove the entire <application /> tag, the "good" line is gone from the final AndroidManifest.xml but the bad line is still there.
Then still in folder .../lp/28/jl there is another folder aapt and there is also a AndroidManifest.xml file and it looks like this (contains the "bad" line):
<?xml version="1.0" encoding="utf-8"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.crashlytics.android" android:versionCode="1" android:versionName="2.9.4">     <uses-sdk android:minSdkVersion="9" />     <uses-permission android:name="android.permission.INTERNET" />     <application>         <provider android:name="com.crashlytics.android.CrashlyticsInitProvider" android:authorities="dollar_openBracket_applicationId_closeBracket" android:exported="false" android:initOrder="100" />     </application> </manifest>
If I once again remove the entire <application /> tag, the "bad" line is gone out of the final AndroidManifest.xml
In order for me to Archive the app without the "bad" line:

Rebuild project (this removes any changes made to files in obj)
Go to the lp folder containing the bad manifest (again 28 in my case - didn't change) and remove the <provider... android:authorities="dollar_openBracket_applicationId_closeBracket" ... /> line
Archive project
Success

Thank you @Dooks123! Your suggested workaround works well on my projects! Besides it's a little complicated to execute these steps, it really saves who isn't working with VS 2019 yet!
Still waiting for the properly fix by the author.

https://github.com/xamarin/xamarin-android/issues/2141 should have fixed this issue awhile back.  Please open a new issue if it's still occurring.