Transactional selector cache

Make SelectorCache identity updates transactional. This allows changes to selections of different selectors to appear at once on a new version published by the selector cache after all the changes have been completed, which allows removal of the CIDR index within MapState, making computation of CIDR heavy policies ~30% faster, mainly due to reduction of allocations by ~35%.
This change allows SelectorCache users to rely on all the selectors to be in sync with each other, so that if a given identity is selected by multiple selectors, that identity appears in the result of the GetSelections() call for all of them. Previously it was possible that at the time of the respective GetSelections() calls, some of them would have failed to include the new identity, due to the update of that selector still being in progress.
With this change the visibility of new identities in the selections of any cached selector is delayed until all affected selectors have been updated.
Incremental updates are synchronized after each round of identity modifications in the selector cache so that the updates on all affected MapState entries appear during the same round of updates, essentially making incremental updates transactional as well. The consumer of incremental updates gets the version of the selector cache as of after the changes, so that a consistent NetworkPolicy can be computed for Envoy as well.
Now that SelectorCache GetSelections() and incremental updates are both transactional, we can rely on a covering CIDR selector to also select any covered new identities. For example, given a L3-only WORLD deny rule and an toFQDNs allow rule, and newly allocated FQDN identities are also selected by the deny WORLD selector, and we can rely on these new
identities appearing on those selectors "at the same time", so that on any given round of DistillPolicy or ConsumeMapChanges, any new identities appear on all affected selectors, and conversely, and removed identities are likewise removed from all affected selectors.
Given the above, we do not need to go look for non-wildcard superset/subset identities, as keys with them will be added (or have already been added) or removed on the same round and the effect of them will be present in the computed MapState. In the above example, even if on a given round we first add an allow rules the new FQDN-derived identity, we will later replace it with a deny entry based on the same ID being selected by the (deny) WORLD selector. Conversely, if on a given round we add the deny entry first, the allow entry will be naturally bailed due to the existing deny entry.
Endpoint's policy update process is further simplified by creating the required proxy redirects before computing MapState. This is possible due to proxy redirects depending on the selector policy and not the MapState. This way the proxy ports are available when needed, and a 2nd round of policy map sync can be eliminated. This is partially made possible by moving removal of the unnecessary proxy redirects to the policy update finish function, so that these removals never need to be reverted.
Finally, we can eliminate unnecessary NetworkPolicy computations in cases where there are no incremental updates. In that case it suffices to wait for any pending NetworkPolicy update to complete, as another goroutine may have applied the needed policy updates and they may still be pending acknowledgement.
Following PR(s) have been carved out to merge separately:

https://github.com/cilium/cilium/pull/34343
https://github.com/cilium/cilium/pull/34344
https://github.com/cilium/cilium/pull/34346
https://github.com/cilium/cilium/pull/34347
https://github.com/cilium/cilium/pull/34349

/test

Dropped the last commit (changing how incremental updates are regenerated), which turned out to be a significant lift in itself.
Added new commit refactoring container/versioned API as suggested.

/test

/test

/test

/test

/test

/test

/test

/test

/test

/test

Added tracking of updated selectors with versioned.Versioned for more efficient cleanup (no need to scan through all the selectors).

/test

Change from a struct pointer to an interface added a new failure mode where the interface is nil. Struct methods test for nil pointer, but if the interface itself is nil then the dereference crashes before we get to the method.

/test

@bimmlerd

no, you can have an unexported struct with exported methods. https://go.dev/play/p/lFYPMidT6qW

But can you refer to an unexported type from another package?

Changed back to exporting VersionHandle struct directly without an interface in between. Did not like the explicit nil tests that were needed for the interface.

/test

/test

I just thought of something that might reduce the complexity of this significantly: we can invert the incremental update system so it is consistent along the dimension that matters.
We don't care about anything inter-identity. All that matters is that a given identity is atomically added to all selectors at once. The Value() system is a reasonable way to keep cached selectors lock-free (though we might take the SelectorCache RLock anyways?)
But what if the incremental update was the message "identity 1 has been added to selectors S1, S5, S22..."? Then the user (L4 policy) could apply that consistently to it's internal state. Then we wouldn't need any kind of versioning or snapshotting for the incremental system.

/test

/test

/test

/test

/test

/test

Rebased to fix flag provided but not defined: -cilium.extra-opts

/test

/test

Finally managed to minimize the changes needed in pkg/endpoint for this. The main change needed was to apply incremental updates before updating the network policy, as otherwise the network policy would be based on an outdated version in cases where incremental updates were received concurrently with a full policy update.

/test

rebased to resolve merge conflicts

/test

/test

/test

/test

/test

/test

/test

/test

ci-ginkgo is currently failing due to https://github.com/cilium/cilium/pull/34463

/test

Rebased to resolve conflict with main.

/test

/test

Rebased to resolve merge conflict in pkg/policy/resolve_test.go

/test

ci-runtime hit by https://github.com/cilium/cilium/issues/35055

/test


parse strategies as own extras

What does this PR do?
This brings clarity to installing needed strategies just enriched by the correct version
pip install pytorch-lightning[horovod]

Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃
cc @justusschock @awaelchli @rohitgr7

@carmocca in fact, let's keep _load_requirements as we may reuse it in freezing requirements...


Add other scaled images in gallery

Describe the feature you'd like
Would it be possible to add other image formats such as scaled-300- and scaled-800- ?
The thumb-150x150 distorts the image and the scaled-1680- is too large for me
Describe the benefits this would bring to existing BookStack users
The page will render better
Can the goal of this request already be achieved via other means?
I'm not aware of any other solution
Have you searched for an existing open/closed issue?

[X] I have searched for existing issues and none cover my fundamental request

How long have you been using BookStack?
Under 3 months
Additional context
No response

Thanks for the request @vdomos,
Personally I'm not too keen on complicating matters around this with options and/or additional thumb generation since there's been little previous desire for this and tbh I think the benefits would be generally quite negligible. especially where images could be optimized before upload if really required for a specific use-case.

have found some issue related to this: the thumbs for large images are created y 440x250px, but in mobile view the thumb size exceeds up to 552px. that scales up to pixeled image


allows marathon healthcheck interval and max consecutive failure to b…

…e configurable

@sradack any feedback on this?


SDIT-1826 Prevent duplicate global tags

Tags with same name but different descriptions both end up in the global tags section - which gets rejected by the openapi generator.
So we need to have only one "Physical Attributes" tag with a description. Currently that is the one found in PhysicalAttributesController.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 83.53%. Comparing base (79f8876) to head (43020f1).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##               main      #63   +/-   ##
=========================================
  Coverage     83.53%   83.53%
  Complexity      385      385
=========================================
  Files            59       59
  Lines          1160     1160
  Branches        113      113
=========================================
  Hits            969      969
  Misses          119      119
  Partials         72       72

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Clarifications to the deleteMessage() call

I think users, too, cannot delete messages older than 48 hours, not just bots.

On the channels I have created, I can delete older messages.

Bots can delete channel posts older than 48 hours, too, can't they? The 48 hours case is only for groups and private chats.

Bots can delete channel posts older than 48 hours, too, can't they?

No, they cannot .  I have tried and it does not work, therefore I propose updating the documentation to the actual behaviour.

These are not our docs. They're extracted from https://core.telegram.org/bots/api#deletemessage and I'd prefer to keep things perfectly in sync.

If you think something is wrong, you can contact @levlam in https://t.me/tdlibchat.

Rejected in the discussion starting at https://t.me/tdlibchat/34770


feat: Add Edition2024

RFC for Edition2024.  While the RFC is not yet merged, this follows rustc which added the 2024 edition previously in rust-lang/rust#94461
This PR adds Edition2024 as a possible value for edition = "xxxx". I did this by following the guide here.

@bors r+

:pushpin: Commit b3481b7bf36c0405238cd2404ae8bdd5eaeba65e has been approved by epage
It is now in the queue for this repository.

:lock: Merge conflict
This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again.
How do I rebase?
Assuming self is your fork and upstream is this repository, you can resolve the conflict following these steps:

git checkout edition-2024 (switch to your branch)
git fetch upstream master (retrieve the latest master)
git rebase upstream/master -p (rebase on top of it)
Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
git push self edition-2024 --force-with-lease (update this PR)

You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial.
Please avoid the "Resolve conflicts" button on GitHub. It uses git merge instead of git rebase which makes the PR commit history more difficult to read.
Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Cargo.lock conflict is handled during merge and rebase. This is normal, and you should still perform step 5 to update this PR.

Error message
Auto-merging src/cargo/util/toml/mod.rs
CONFLICT (content): Merge conflict in src/cargo/util/toml/mod.rs
Automatic merge failed; fix conflicts and then commit the result.

@bors r+

:pushpin: Commit b2b3cfa524bd360d3b0f35f281cab4cd3938bb1a has been approved by epage
It is now in the queue for this repository.

:hourglass: Testing commit b2b3cfa524bd360d3b0f35f281cab4cd3938bb1a with merge d74bc471b9b0be7540d7c9b70eb46b9811197137...

:sunny: Test successful - checks-actions
Approved by: epage
Pushing d74bc471b9b0be7540d7c9b70eb46b9811197137 to master...


Additional Changes for Challenge 2732

I've fixed the issues that I had discovered in iCare's submission and mentioned here - https://github.com/docusign/DocuSign-eSignature-SDK/pull/44#issuecomment-23544411
I added these validations on senddocument page

Required field validation on subject.
Required field validation on Email.
Required field validation for RecipentName. (if only one)
Required field validation for RecipentEamil. (if only one)
Required field validation for RecipentName and Eamil if more than one
Required field validaiton for if no document selected

I added these validations/ fixes on sendtemplate page

Required field  validation on subject
Required field  validation on Email
Disable post until the user does not select a template and hit the go button
Required field  validation for RecipentName
Required field  validation for RecipentEamil
Custom alert messages for all validation messages.

This software is deprecated. Developers who wish to develop with SOAP should generate their own stubs using the wdsl. Thank you.


Plugin Walletconnect:  Not activating

Hey team,
I am trying to activate the walletconnect plugin since yesterday and it seems like the button is not responding. I tried accessing the IPFS URL of the walletconnect from the plugins folder here as well but it doesn't seem to load up. Can someone please help me with it?
FYI,
I am currently using MacOS 11.3 on a Macbook Pro i5
I have tried using remix within a browser and also by downloading the dmg file.

we had some issues with the ipfs node, this should be ok now, can you try it again?


Use GITHUB_TOKEN per coveralls 3.3.1 help

Getting the following error
Running on Github Actions but GITHUB_TOKEN is not set.
Add "env: GITHUB_TOEKN: ${{ secrets.GITHUB_TOKEN }}" to
your step config.
Following directions from latest coveralls python (3.3.1) help
for Github Actions
https://coveralls-python.readthedocs.io/en/latest/usage/configuration.html#github-actions-support

coverage: 88.963%. remained the same
when pulling e4bae7331248c069acc35f569b054011cb6fc631 on josephbredahl:coveralls-token-crash
into c70fbc1b11938af3e21ad275904e07d324b8ac08 on djc:main.

@djc this seems to be the right or most popular answer. Let me know if you are OK with swapping using COVERALLS_REPO_TOKEN with the GITHUB_TOKEN.
Otherwise, I'm not really sure why COVERALLS_REPO_TOKEN wasn't working. I expect it should have been brought in via load_config_from_environment.
I couldn't quite verify if setting COVERALLS_REPO_TOKEN  within the shell run: | no longer worked. So maybe doing something like...
env:
        COVERALLS_REPO_TOKEN: ${{ secrets.COVERALLS_REPO_TOKEN }}

... would still work.
...So I just defaulted to do what the coveralls-python help suggested. Figured that was the most safe path forward.

Also, let me know if you do or don't want me to bug you with reviews.


Fix line ending in Additional Info

Kate still has one turning up

This issue is referring to 2 lines in the github committed file, knb-lter-nes.16.4.xml, which contain &#13. This is an escaped non-printing carriage return which is not removed with .gitattributes.
Since there are just 2 occurances in the file and only 2 diffs because of it, I recommend we ignore it and do not attempt to implement a fix to strip it out of the files we commit.
@katemorkeski , if you agree please close this issue


Please add example for real time recording and parsing from computer microphone

I am talking about google-cloud-speech
Even being an experienced Java Developer i am struggling a lot with this repository ... there are not many examples on how to use it ... if not any at all .
Add examples for recording and providing speed to text from microphone embedded to the computer .
Like i have done this but it's not working properly and it's very slow :
https://github.com/goxr3plus/java-google-speech-api/issues/4
Add more examples on how to use the library please.

upvoted! I`ts very struggling.

This repository is for client issues.  Samples are in another repository.  I duplicated this issue here: https://github.com/GoogleCloudPlatform/java-docs-samples/issues/1457

Howdy! As noted by sduskis, we host all our samples in java-docs-samples!
Best resource for info however, is still on the Google Cloud Platform docs pages: https://cloud.google.com/speech-to-text/docs/


Update PHP Snippet generation.

Overview
Brief description of what this PR does, and why it is needed.
Demo
Optional. Screenshots, curl examples, etc.
Notes
Optional. Ancillary topics, caveats, alternative strategies that didn't work out, anything else.
Testing Instructions

How to test this PR
Prefer bulleted description
Start after checking out this branch
Include any setup required, such as bundling scripts, restarting services, etc.
Include test case, and expected output

Would it confuse customers if query parameters snippets only work with PHP 8 while the others work across both PHP 7 and 8?

That makes sense. What about having something like this? Knowing these other query parameters that are supposed to be set to null is the problem, at least on the devx side
...addQueryParameters(
null,
null,
'age eq 20',
['email', 'principalName']);

Won't that be confusing, too?

I think for PHP 7 devs the existing snippets seem like the best experience. PHP 8, constructors would be ideal.
Unless we add both snippets? Or only add a comment in the snippet about a better experience for PHP 8 using the constructors?


GEODE-7761: change Ignore description

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

As GEODE-7600 is resolved but didn't fix this test, changed Ignore description.

GEODE-7702 is the current defect tracking this issue.


/meta endpoint is returning a 500 for shares

Describe the bug
I was trying to test deep links for shares in the Android app and I just realised that by using the theoretical correct deep link (this is, the private link provided by the propfind call but replacing https:// by owncloud://), the endpoint is returning a 500 with an empty response.
Steps to reproduce

Construct the deep link corresponding to a share (private link but replacing https:// with owncloud://)
Click the deep link. The Android and iOS apps will send to the /meta endpoint what comes after the /f/ in such link, that is the file ID
/meta endpoint will respond with a 500

Expected behavior
The /meta response should include the correct information for the file requested.
Actual behavior
The /meta response is a 500 error.
Setup
I'm using ocis-traefik.latest, redirected from https://ocis.owncloud.works:
ownCloud Web UI 8.0.0-alpha.12
Infinite Scale 5.0.0-alpha.5+71f7c1e73 Community

Additional context

I think this is specific for oCIS 5.0, since with 4.0 it worked for iOS app (Android didn't have this feature yet).
I also checked just in case it is problem of sending %21 instead of ! in the file ID, but that's not the case, the same 500 response is received in both cases.
Just to be clear: this is working for normal files, the 500 response just occurs with shares.

Clients send the following request (by curl), using the space id from shares
curl -k -X PROPFIND -H 'authorization:Bearer <token>' https://ocis.ocis-traefik.latest.owncloud.works/remote.php/dav/meta/a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668%2521eb249b94-9051-4743-9e36-577b08b851e%20a:4c510ada-c86b-4815-8820-42cdf82c3d51:121da02e-80a3-46cd-8593-837ba4d478a4 --data-binary '\<\?xml version="1.0"?>\n<d:propfind  xmlns:d="DAV:" xmlns:oc="http://owncloud.org/ns">\n  <d:prop>\n    <oc:meta-path-for-user />\n  </d:prop>\n</d:propfind>'
<?xml version="1.0" encoding="UTF-8"?>

Response is 500 with empty body

Clarification about the scenario to reproduce (not real life scenario)

User1 shares an item with User2, so User2 has the file into its shares space/mountpoint... whatever

Getting the private link or the file-id of the shared item in the account of User2 (`PROPFIND returns it if you ask for it). For our example, the file id is

a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668!a64a3467-fdd6-4df5-b177-c518d9f74e97:1165bccb-5cd0-434a-8fef-eb90098730fb:0b317a25-6737-4477-aa6c-67a416390581

Using that file-id, calling the meta endpoint to resolve it, that means, to know its path into the account. This is the request with curl:

curl -k -u <user:pwd> 'https://<url>:9200/remote.php/dav/meta/a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668!a64a3467-fdd6-4df5-b177-c518d9f74e97:1165bccb-5cd0-434a-8fef-eb90098730fb:0b317a25-6737-4477-aa6c-67a416390581' --data-binary '<?xml version="1.0"?>\n<d:propfind  xmlns:d="DAV:" xmlns:oc="http://owncloud.org/ns">\n  <d:prop>\n    <oc:meta-path-for-user />\n  </d:prop>\n</d:propfind>'  -X PROPFIND -i

Response is
HTTP/1.1 500 Internal Server Error
Access-Control-Allow-Origin: *
Content-Length: 0
Content-Security-Policy: default-src 'none';
Date: Wed, 20 Dec 2023 17:03:30 GMT
Vary: Origin
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: ae8671afc5c5/Cyj1dfDyDJ-027952
X-Robots-Tag: none
X-Xss-Protection: 1; mode=block

it should return the requested  <oc:meta-path-for-user /> in the PROPFIND

<oc:meta-path-for-user /> can only be relative to a space root, that is why ocis also returns an oc:spaceid property. Is the android app aware of that? Is iOS, for that matter?
Why do you have to look up the path at all? A stat to https://<url>:9200/remote.php/dav/spaces/a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668!a64a3467-fdd6-4df5-b177-c518d9f74e97:1165bccb-5cd0-434a-8fef-eb90098730fb:0b317a25-6737-4477-aa6c-67a416390581 should give you the propfind result for the resource. The response contains the spaceid, and ocis should also give you a oc:file-parent, an id that allows you to navigate up.
I know this wall not allow you to show the full path to the resource, eg. as breadcrumbs, but it would allow showing a ...
In any case, I would like to understand the neccessity of the path. Fetching it is time consuming and in the graph api we might be able to return it as part of the parent property of driveItems. So, I'm just trying to learn.
Aside from the above the 500 is a bug, but we can only fix it by returning a path relative to a space root, since absolute paths ar a thing of the past.

<oc:meta-path-for-user /> can only be relative to a space root, that is why ocis also returns an oc:spaceid property. Is the android app aware of that?

Yes we are, in fact we do already navigate correctly when we receive the response for a file that is not in the personal space in an oCIS account.

Why do you have to look up the path at all? A stat to https://<url>:9200/remote.php/dav/spaces/a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668!a64a3467-fdd6-4df5-b177-c518d9f74e97:1165bccb-5cd0-434a-8fef-eb90098730fb:0b317a25-6737-4477-aa6c-67a416390581 should give you the propfind result for the resource. The response contains the spaceid, and ocis should also give you a oc:file-parent, an id that allows you to navigate up.

Well, firstly, we need it for oC10 as well, where we are using the /meta endpoint too. But the real point here is that we need the absolute path because we need to discover the different folders where the objective file is located. This is, fetch each of these files from the server so that we can finally navigate to the aim file. We need to do it that way because we just fetch the root folder of each space in first instance, and then we fetch each of the subsequent folders. We cannot do it backwards (with just the file and its file-parent) since these won't be in our local database yet and we cannot retrieve and fetch each of the parents until we arrive to the root folder of the corresponding space.

Aside from the above the 500 is a bug, but we can only fix it by returning a path relative to a space root, since absolute paths ar a thing of the past.

Yes, let's say we need the "absolute path" but just within the space. But remember this is just happening with the files inside the Shares space, so it wouldn't be a problem since the Shares space has a constant ID (https://github.com/owncloud/web/blob/2ab7e6da432cb344cd86f3451eea1678461c5c90/packages/web-client/src/helpers/space/types.ts#L11).
I hope I explained properly, just ask me if you have any other question 👍.

Status: Prio 2 in case of a regression, according to @micbar

update has landed in ocis.


Set knn lib version based on plugin version

Currently, we hardcoded knn plugin version as <IP_ADDRESS>. This should be updated to plugin's build version.

Code example?

I agree that this can be grep from the plugin build version, as long as it still produce correct artifact zips.
The DEB/RPM does not need any reference for hardcoded versions anymore.

Code example: https://github.com/opensearch-project/k-NN/blob/main/jni/CMakeLists.txt#L193-L235.
We use to use CPack to build deb/rpm of lib. But if we dont need this functionality anymore, I think the versioning in cmake can be removed. Just wanted to confirm with you that this is not needed for RPM/DEB OpenSearch bundle build.


fix ensureDirectoryExists uses storage disk

Fixes the method ensureDirectoryExists to use the storage disk passed in the config, otherwise it attempts to create the directory social/open-graph in the projects root directory instead of the intended storage disk path.

Looks good, thanks! @sweptsquash


iOS auto-provisioning code doesn't play nice with flutter run --machine

$ flutter run --machine
[{"event":"app.start","params":{"appId":"95ec9ce1-98b0-4440-a8b3-d73e36fa8d39","deviceId":"b851637e924ad4a23cb62691cfab9a1251fa7aef","directory":"/Users/tvolkert/project/flutter/flutter/examples/hello_world","supportsRestart":true}}]
Launching lib/main.dart on Boq in debug mode...
Multiple valid development certificates available:
  1) iPhone Developer: Google Development (3F4Y5873JF)
  2) iPhone Developer: Todd Volkert (VEM2GJ2RW9)
  a) Abort
Please select a certificate for code signing [1|2|a]: [{"event":"app.stop","params":{"appId":"95ec9ce1-98b0-4440-a8b3-d73e36fa8d39","error":"Bad state: Stream has already been listened to."}}]

@xster

I guess conceptually since we're asking for user input, we're gonna need to translate that feature to support the JSON APIs too?
The simplest solution is probably to just pick the first one, or is there an existing documentation for the JSON APIs for would be --machine developers that I can look at and extend?

@devoncarew

Yeah, we shouldn't be asking for user input in --machine mode, or at least not via stdin.
I possible solution here is to auto-select a certificate, print a message saying what we did, and have some instructions in there telling the user how to select an explicit one going forward. This may even be a good solution for the regular flutter run case - which, even for that, we may not want to interrupt a run by asking for user input.
Multiple valid iOS development certificates available (3F4Y5873JF: Google Development, Todd VolkertVEM2GJ2RW9); autoselecting '3F4Y5873JF: Google Development'. In order to specify a default certificate, running `flutter config mac-certificate=xxx`.

Can we use flutter config to store the default choice going forward?

Yeah, it's just a key value store, and work probably work well for something like this. And just to re-cap my thoughts from above, instead of asking the user for the choice, I think we should:

guess
warn that we guessed
provide a way to configure the choice (in a stateful way on disk)

Great idea. I was thinking about where to save it but there's already prior art. Will use the config store.
+1 on the other points. We already output the chosen one.

Saving choice in #10181.
I was reading the --machine code but it wasn't very clear how it worked. Is there a global state I can read to know that it was from --machine? Doesn't seem passed down to the downstream commands.

Do you mean as an intermediate step towards not asking for user input, or as the solution for this issue? I definitely think we're better off now asking.
If this is just an intermediate step, you'd probably need to record that we're in a non-interactive mode in some global state, perhaps in a context variable (like in globals.dart).

+1 for not asking and just informing the user that we're choosing one and how they can update the config of which choice we'll make.

#10181 is somewhat tangential. Trying to figure out how to know we're in --machine mode in the deeper build commands so we can guess. @devoncarew you answered my question. I'll save that state somewhere.

Oops, pasted the wrong PR for saving before. Fixed


Hotfix

Hotfixes:

Archive command
Editing Archive command
Improve readability, differentiate archive and unarchived entries
fix typos

Codecov Report

Merging #92 (8469217) into master (f31fc2a) will decrease coverage by 0.32%.
The diff coverage is 4.54%.

@@             Coverage Diff              @@
##             master      #92      +/-   ##
============================================
- Coverage     45.09%   44.77%   -0.33%
  Complexity      463      463
============================================
  Files           112      112
  Lines          2428     2448      +20
  Branches        347      357      +10
============================================
+ Hits           1095     1096       +1
- Misses         1248     1266      +18
- Partials         85       86       +1

Impacted Files
Coverage Δ

...edu/address/logic/commands/FindCompanyCommand.java
0.00% <ø> (ø)

...seedu/address/logic/commands/FindEventCommand.java
0.00% <ø> (ø)

...eedu/address/logic/commands/FindPersonCommand.java
100.00% <ø> (ø)

...address/logic/parser/FindCompanyCommandParser.java
0.00% <0.00%> (ø)

...u/address/logic/parser/FindEventCommandParser.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/model/Model.java
75.00% <ø> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
52.70% <0.00%> (-3.42%)
:arrow_down:

...ava/seedu/address/model/entry/UniqueEntryList.java
66.66% <0.00%> (-2.43%)
:arrow_down:

src/main/java/seedu/address/ui/CompanyCard.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/EventCard.java
0.00% <0.00%> (ø)

... and 3 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 f31fc2a...8469217. Read the comment docs.


Stop both replication controllers in update-demo

The update test may have failed, and if we leave an RC around it
causes subsequent tests to fail

LGTM.


Deprecated tag for service

Tag shopware.payment.method.sync was removed in Shopware 6.7.0
[2024-12-11T10:57:43.975739+00:00] php.INFO: User Deprecated: Since shopware/core : The tag shopware.payment.method.sync is deprecated for service PayonePayment\PaymentHandler\PayoneApplePayPaymentHandler and will be removed in 6.7.0. Use shopware.payment.method instead. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Since shopware/core : The tag shopware.payment.method.sync is deprecated for service PayonePayment\\PaymentHandler\\PayoneApplePayPaymentHandler and will be removed in 6.7.0. Use shopware.payment.method instead. at /var/www/html/vendor/shopware/core/Framework/Feature.php:250)"} []

Hello @maximilian-schwarz
we haven't added the 6.7.x compatibility yet, because there is no release-candidate for SW 6.7.
currently we have a few changes in the pipeline, which will be released before these compatibility changes.
Next release will be also compatible with SW 6.6 and 6.7.
You may watch the repository to get a notification if the next release got published.
Thank you for your patience.
--
You should not get the deprecation warnings if you set up the configuration correctly.


parity: 1.9.7 -> 1.10.6 [SECURITY UPDATES]

Motivation for this change
This is security updates according to https://paritytech.io/security-alert-3

https://github.com/paritytech/parity/releases/tag/v1.10.6

Also parity-beta temporary disabled because I have a build issues with v1.11.*
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Success on x86_64-linux (full log)
Attempted: parity
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/15n8qlfvrqyxdc3l8whnk3hm3blq7wqw-parity-1.10.6
shrinking /nix/store/15n8qlfvrqyxdc3l8whnk3hm3blq7wqw-parity-1.10.6/bin/parity
shrinking /nix/store/15n8qlfvrqyxdc3l8whnk3hm3blq7wqw-parity-1.10.6/bin/librlp_derive.so
strip is /nix/store/21ymadblbmsbb2bk4q7gl4kjasp8zmgd-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/15n8qlfvrqyxdc3l8whnk3hm3blq7wqw-parity-1.10.6/bin
patching script interpreter paths in /nix/store/15n8qlfvrqyxdc3l8whnk3hm3blq7wqw-parity-1.10.6
checking for references to /build in /nix/store/15n8qlfvrqyxdc3l8whnk3hm3blq7wqw-parity-1.10.6...
/nix/store/15n8qlfvrqyxdc3l8whnk3hm3blq7wqw-parity-1.10.6

Success on aarch64-linux (full log)
Attempted: parity
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/fjmpglf51v3jxjrk2yp8k86snp70knmb-parity-1.10.6
shrinking /nix/store/fjmpglf51v3jxjrk2yp8k86snp70knmb-parity-1.10.6/bin/librlp_derive.so
shrinking /nix/store/fjmpglf51v3jxjrk2yp8k86snp70knmb-parity-1.10.6/bin/parity
strip is /nix/store/qg2agrqkf240s656d207zqhipl0bc2id-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/fjmpglf51v3jxjrk2yp8k86snp70knmb-parity-1.10.6/bin
patching script interpreter paths in /nix/store/fjmpglf51v3jxjrk2yp8k86snp70knmb-parity-1.10.6
checking for references to /build in /nix/store/fjmpglf51v3jxjrk2yp8k86snp70knmb-parity-1.10.6...
/nix/store/fjmpglf51v3jxjrk2yp8k86snp70knmb-parity-1.10.6


Broken code

Running tests using rust-toolchain nightly-2019-03-15 all tests failed:
failures:

---- test_boxed_slice stdout ----
thread 'test_boxed_slice' panicked at 'assertion failed: `(left == right)`
  left: `24`,
 right: `16`', tests/tests.rs:185:5
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

---- test_heap_size stdout ----
thread 'test_heap_size' panicked at 'assertion failed: `(left == right)`
  left: `24`,
 right: `8`', tests/tests.rs:141:5

---- test_boxed_str stdout ----
thread 'test_boxed_str' panicked at 'assertion failed: `(left == right)`
  left: `24`,
 right: `8`', tests/tests.rs:113:5

failures:
    test_boxed_slice
    test_boxed_str
    test_heap_size

Currently failing the same way on:

1.37.0
1.38.0
1.39.0-nightly (66bf391c3 2019-09-23)

But passes on

1.31.0


Using a .flake8 settings file already in the repo

Is it possible to use an existing .flake8 file that's already in my repo?
Thanks!

The action clones your repository and runs the commands in the root directory. If your file is at the root of the project it should be considered.
The current version of flake is 3.8.3.
Want to send me more information about your project so I can try to help?


Listing a non-existent alias is throwing error

List is working fine if an alias exists, but if the alias does not exist, it does not appear to be handled and throws up a traceback.

It has a cleaner error message now.


cluster: add healthchecks on cluster creation

Hello @nicks,
Please review the following commits I made in branch nicks/issue131:
f5a91c075ca7cbaa765cc7e1630f3214741bc617 (2021-09-22 23:52:58 -0400)
cluster: add healthchecks on cluster creation
fixes https://github.com/tilt-dev/ctlptl/issues/131
Code review reminders, by giving a LGTM you attest that:

Commits are adequately tested
Code is easy to understand and conforms to style guides
Incomplete code is marked with TODOs
Code is suitably instrumented with logging and metrics

oops, this isn't quite right, let me try something else


npm issues with initial install

Hi
Just downloaded the free template and having followed the instructions I get this as the result to npm install:
found 946 vulnerabilities (65 low, 880 high, 1 critical) in 44508 scanned packages
run npm audit fix to fix 874 of them.
1 vulnerability requires semver-major dependency updates.
71 vulnerabilities require manual review. See the full report for details.
The site seems to work but with all those vulnerabilities I'm wondering if this is safe to use?
I'm assuming this also effects the pro-version
~Brett

Hi!
Thank you for your report! In the new version vulnerabilities have been fixed.
Regards


Learn matplotlib cpp

Learn to plot graphs using matplotlib cpp.

Not able to install it. Having tons of issues. ABORTED :'(


Update golange to 1.17

Test name
Status

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1003/commits/58c9de316977690d2ebfd891d494af19ff14dcae
image: perconalab/percona-xtradb-cluster-operator:PR-1003-58c9de31

Test name
Status

haproxy
passed

storage
passed

recreate
passed

scaling
passed

big-data
passed

scheduled-backup
passed

upgrade-haproxy
passed

self-healing
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

init-deploy
passed

self-healing-chaos
passed

limits
passed

demand-backup
passed

smart-update
passed

monitoring-2-0
passed

self-healing-advanced
passed

affinity
passed

one-pod
passed

self-healing-advanced-chaos
passed

auto-tuning
passed

pitr
passed

proxysql-sidecar-res-limits
passed

users
passed

operator-self-healing
passed

upgrade-consistency
passed

operator-self-healing-chaos
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1003/commits/033773208440cc1ec87d712911e235a0dbccef1f
image: perconalab/percona-xtradb-cluster-operator:PR-1003-03377320

Test name
Status

upgrade-haproxy
passed

haproxy
failed

scaling
passed

storage
passed

recreate
passed

big-data
passed

scheduled-backup
passed

scaling-proxysql
passed

self-healing
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

self-healing-chaos
failed

security-context
passed

init-deploy
passed

demand-backup
failed

smart-update
passed

self-healing-advanced
passed

limits
passed

monitoring-2-0
passed

self-healing-advanced-chaos
failed

operator-self-healing
passed

affinity
passed

one-pod
passed

auto-tuning
passed

operator-self-healing-chaos
failed

upgrade-consistency
passed

proxysql-sidecar-res-limits
passed

users
failed

pitr
failed

tls-issue-self
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1003/commits/196aa5e08f1a7dc7d1e38b5487f1ebf86d4387be
image: perconalab/percona-xtradb-cluster-operator:PR-1003-196aa5e0

Test name
Status

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

haproxy
failed

upgrade-haproxy
passed

big-data
passed

storage
passed

scheduled-backup
passed

scaling
passed

self-healing
passed

scaling-proxysql
passed

self-healing-chaos
failed

security-context
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

operator-self-healing
passed

operator-self-healing-chaos
failed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

pitr
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup-encrypted-with-tls
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1003/commits/196aa5e08f1a7dc7d1e38b5487f1ebf86d4387be
image: perconalab/percona-xtradb-cluster-operator:PR-1003-196aa5e0


Client side app code missing in master.

Thank you for creating this awesome plugin. I was going through the code and it looks like client side app code is missing. current master has prod build client app and that's unreadable. Could you please add dev client app.

related #77

related #77

@ElmahCore Any chance of getting the frontend code pushed? We could probably make a PR to offer a configuration option to disable this.

@jafin @hardcoderz I think the UI is here: https://github.com/barestan/ECNewUI


fix: wrong resolver return value not raised by TS

As per the title
Also raise when defining an argument with an invalid GraphQL type (i.e. args: { foo: 'String', typo: 'Strnig' })

:tada: This PR is included in version graphql-gene-v1.2.0-beta.3 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version graphql-gene-v1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add continue to fix 'continue_on_failure' parameter for URL doc loader

Currently, the function still fails if continue_on_failure is set to True, because elements is not set.

Good catch! Should we add an integration test or two to make sure it works. Something as simple as
def test_continue_on_failure_true() -> None:
  """Test exception is not raised when continue_on_failure=True."""
  loader = UnstructuredURLLoader(["badurl.foobar"])
  loader.load()

def test_continue_on_failure_false() -> None:
  """Test exception is raised when continue_on_failure=False."""
  loader = UnstructuredURLLoader(["badurl.foobar"], continue_on_failure=False)
  with pytest.raises(Exception):
    loader.load()

in a new tests/integration_tests/document_loaders/test_url.py file


Segmentation fault in unit test due to SILKRPC_LOG trace

Adding one or more SILKRPC_LOG traces causes the unit test executable to crash with segmentation fault
Probably it's something related to logging streams, please @Sixtysixter provide more info here when available

The log instance responsible for logging is teestream, instantiated by default with std::cerr stream and a null stream (see   https://github.com/torquem-ch/silkrpc/blob/ee585804b3d8a7916b6ea8df01ea08a3b662d047/silkrpc/common/log.cpp#L33). The internal pointers to std::streambuf are initialized calling rdbuf() on
The rdbuf() call on std:cerr, used in this way, returns a pointer that seem bad (at 0x7ffff....).
This cause the segmentation violation fail (both with gcc and clang).
It is need to add
SILKRPC_LOG_STREAMS(null_stream(), null_stream());
to properly set the log instance.
Note that the crash happens if the tested code contains some trace allowed by the verbosity level (ie SILKRPC_LOG) so set the verbosity to NONE is not enough (by default it is set to INFO)


No kind checking

It is possible to use higher-kinded types in union types and type aliases:
type Impossible
    = A List
    | B (List Int Int)

type alias Uninhabited =
    { field : Dict String
    }

None of these types are possible, so while it's not hurting anyone, it's also kind of weird to let meaningless things be written down.
Note: Comment edited to summarize discussion and refinement in the further comments.

Failing test submitted in PR.

Also, this
type A = B Maybe

is accepted, even though it is meaningless.
So the issue here is not really just about type aliasing. It is about a lack of kind checking.
Maybe rename the issue?
Also, here's a case where this (possibility of defining meaningless types this way) hit a user.

It's not 100% obvious to me that higher-kinded type aliases should not be permitted, but it does seem reasonable to demand that a certain things have kind Type, such as record fields or values in a union type. Stuff that needs to be a value that can exist!

Another kind issue: extending record aliases with non-aliases crashes the compiler.
type alias Foo a =
  { a | bar : Int }

type alias Bar = Foo (Int -> Int)

bar : Bar
bar = {bar = 2}

The dumb solution is to improve the error message found here.

Centralizing into #1373, will track from there.

The development branch resolves this by requiring that things line up syntactically. It is not doing a kind check during type inference though. So in this case, it is fixed with:
-- TOO FEW ARGS ------------------------------------------------------- temp.elm

The `Dict` type needs 2 arguments, but I only see 1:

15|     { field : Dict String
                  ^^^^^^^^^^^
What is missing? Is there some typo?


1.8.0-rc1 changelog

As title

Codecov Report

Merging #6363 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6363      +/-   ##
==========================================
+ Coverage   38.88%   38.89%   +<.01%
==========================================
  Files         364      364
  Lines       51215    51215
==========================================
+ Hits        19916    19920       +4
+ Misses      28432    28427       -5
- Partials     2867     2868       +1

Impacted Files
Coverage Δ

models/repo_list.go
66.84% <0%> (-1.06%)
:arrow_down:

routers/repo/view.go
42.07% <0%> (+0.99%)
:arrow_up:

models/unit.go
14.28% <0%> (+14.28%)
:arrow_up:

Continue to review full report at Codecov.

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


Is 1.1 series fit for kotlin 1.2?

@happy15 I'm using it with Kotlin 1.2 and did not have any problems with it yet.

@jschmid nice to hear that. Let me check it out.

I actually do have problems in the form of:
> Could not resolve all dependencies for configuration ':myproject:testCompileClasspath'.
   > A conflict was found between the following modules:
      - org.jetbrains.kotlin:kotlin-stdlib:1.2.10
      - org.jetbrains.kotlin:kotlin-stdlib:1.1.2-4
      - org.jetbrains.kotlin:kotlin-stdlib:1.0.7


Grammatical fixes in middleware docstrings

I have noticed some grammatical errors while reading through the documentation of this crate.
This PR is intended to fix the ones I noticed while not changing what they are supposed to convey.

thanks 🙂


Dont build conda store cli

part 2 to address https://github.com/conda-incubator/conda-store/issues/911
Description
This PR removes steps for building and releasing conda-store (the cli). This includes:

removing the split package from the conda build recipe - now the recipe will just build the conda-store-server
Removing conda-store (cli) build tasks from the CI (this also removes the release build tasks)
Removing conda-store integration tests from the CI
Removing conda-store steps from cut-release-pr script

Pull request checklist

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

Another thought we would need to add a note somewhere about stopping releasing the cli as a separate package

Another thought we would need to add a note somewhere about stopping releasing the cli as a separate package

There are a few public places that users will be able to see this change:

this pr
release notes (for the next release)
pr to conda-forge package that removes the conda-store package

I think release notes is an appropriate place to be broadcasting this change to communicate with users that this change is coming.
Are there any other stream of news that a conda-store user would be looking at to get this type of information?


Argument labels '(itemsCount:)' do not match any available overloads

Please look at the demo project: https://github.com/Ramotion/paper-onboarding/blob/master/PaperOnboardingDemo/PaperOnboardingDemo/ViewController.swift#L49-L66


Add instructions for running JAR in README.md

Added instructions for directly running the JAR file. This fixes issue #3.

Deleting run-jar-instructions branch, since its code has been merged into master.


Call do_io_close instead of HTTP2_SESSION_EVENT_FINI handler

While I was looking into #7471, I realized that Http2ClientSession::do_io_close is not called if clients send GOAWAY.
Calling do_io_close is not equivalent to calling HTTP2_SESSION_EVENT_FINI event handler, and touching this area is always scary, but I don't think we should skip do_io_close. In case this change causes something we should keep do_io_close and fix the new issue.

Agreed that messing with this area seems scary, but moving forward to more standard shutdown sequences probably worth dealing with the potential fallout.


Closes #63 add deployment example with fastapi for declarai task

How do you feel about putting this in an "examples/deployments" tab instead of just deployments?
Also, maybe this or a separate example leveraging dependency injection?

Currently when used with Depends the swagger shows kwargs as input params rather then user_input (for the movie recommendation example).

And defenitely, moved it to examples/deployments

Currently when used with Depends the swagger shows kwargs as input params rather then user_input (for the movie recommendation example).

I see, We might need to extend the decorator to override the LLMTaskOrchestrator call method with the type hints for this to work because Im pretty sure swagger is evaluated in runtime so this should cause it to appear in the swagger as well.
Not urgent but maybe a separate issue, not sure what other implications this might have (like other tools relying on runtime type hints 🙂)


Changes to call response.json() only once. Updates VGK Logo

Description
I changed the response.json() file to only call once. I also updated the pixel art for the VGK logo to be cleaner.
Copilot

copilot:all

@matslina Hey! I forked the repo again and resubmitted the pull request- hope this one works fine. No issues it says so hopefully we're good! Thanks for all the help. =]

LGTM! Thanks for the PR!


doc: text revision in pt-BR in contributing

resolving some grammatical errors, and semantic texts for best comprehension.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @steveklabnik (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks @rust-highfive , i intend to submit others pull requests, with more pt_BR language revisions.

i will review all the site in pt_BR :)


⚠ Bofrost.de has degraded performance

In 2eefb00, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1560 ms

Resolved: Bofrost.de performance has improved in b63139c after 310 days, 1 hour, 54 minutes.


When browser back is used and there is no undo history, the browser should navigate to the previous page

Follow up from https://github.com/microsoft/vscode/issues/176638

Actually I want to be careful of doing this change and wait for community feedback. It may equally be frustrating to leave VS Code when you use the mouse buttons for navigation only because you reached the first navigation point.
Btw for those that are annoyed by this behaviour in total, you can configure workbench.editor.mouseBackForwardToNavigate: false to disable history navigation via mouse buttons.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


Scope doxygen generation to include only *.h and *.md files

Fixes #967

Do you have the generated docs with this change that I can look at to make sure all the data structures and files that we expect are still there?

@ahsonkhan -- https://djurekdocs.z5.web.core.windows.net/no-snippets/index.html

I don't think this is a concern, but just throwing it out there. Is there a way to hide the source for APIs that are in-lined, and hence their implementation is visible in the header file? I think showing them is fine, but curious to know if we have an option.

https://github.com/Azure/azure-sdk-for-c/blob/dc533e1db8f030dd94161e78a155ad66134a0d8a/sdk/inc/azure/core/az_span.h#L290-L293

@ahsonkhan -- there is the option to eliminate all source inlining.
Have a look at the docs: https://djurekdocs.z5.web.core.windows.net/disable-inlining/index.html --
az_span_fill() -- https://djurekdocs.z5.web.core.windows.net/disable-inlining/az__span_8h.html#a67199badce70b5ae10f879a0b977463c

I am not sure what is common practice for C projects and doxygen generated docs, so maybe we would revert this if other projects show the inlined sources, but I do like the docs without seeing code-snippets, even for inlined methods.
Also, looks like it also solves the duplicate enum issue: https://github.com/Azure/azure-sdk-for-c/issues/970
https://djurekdocs.z5.web.core.windows.net/disable-inlining/az__result_8h.html#afdb1073d8e61c1412ec9cc4f5536fd32

The default value for INLINE_SOURCES is NO and I'm not seeing widespread changing of this value.


PostgreSQL JSON result handled improperly?

See this fiddle: http://sqlfiddle.com/#!15/5860d/11
It gives this result:
{ "Value": "[{\"a\":1,\"b\":\"value1\"},{\"a\":2,\"b\":\"value2\"},{\"a\":3,\"b\":\"value3\"}]", "Type": "json" }

When I run the same set of commands directly against PostgreSQL, I get the following result:
[{"a":1,"b":"value1"},{"a":2,"b":"value2"},{"a":3,"b":"value3"}]

It seems that SQLFiddle is adding some kind of wrapping around the JSON string in the result. It escapes the string from the result, maps the escaped result to a "Value" key in a JSON object, and adds a "Type": "json" key/value.
Affects PostgreSQL 9.2 and up (since the JSON features were introduced).

This appears to be fixed now. I dunno how or when.

Was fixed in the new codebase jakefeasel/sqlfiddle2#18


Accessing component on minified react app

Hey.
I'd like to integrate cypress with a React app. Unfortunately, the Create React App build minifies the code, so cypress-react-selector can't recognize component names.
Is there a suggested solution for this?
Thanks

If you had control over the webpack configuration, you could use webpack-react-component-name.
Your problem is create-react-app will not let you configure webpack.

Hi @ofekudi , can you please check if these tickets help?
https://github.com/abhinaba-ghosh/cypress-react-selector/issues/209
https://github.com/abhinaba-ghosh/cypress-react-selector/issues/83


How to add winston logger to moleculer-web service ?

Hi, there!
I need to implement winston logger for my web service but i dont have created any ServiceBroker . My services started directly from console launcher...
/node_modules/.bin/moleculer-runner --repl --hot --envfile .env.dev endpoints

endpoints - is directory where my services are located in and exports by default Nodejs module.exports = {}

So , my question is actual because i don't know how to implement winston logger instead of basic console. Can anyone help me ?

You should create a moleculer.config.js and put the logger config into it:
https://moleculer.services/docs/0.13/logging.html#Winston
// moleculer.config.js

const winston = require("winston");
const { extend } = require("moleculer").Logger;

module.exports = {
    logger: bindings => extend(winston.createLogger({
        format: winston.format.combine(
            winston.format.label({ label: bindings }),
            winston.format.timestamp(),
            winston.format.json(),
        ),
        transports: [
            new winston.transports.Console()
        ]
    }))
};

@icebob its doesn't work
I added winston.transports.File  but logs files does not created.
transports: [       new winston.transports.Console(),       new winston.transports.File({ filename: './error.log', level: 'debug' }),       new winston.transports.File({ filename: './combined.log' })     ]

As you can see console working properly as before with default logger configuration
LOG_LEVEL=info LOG_FORMATTER=default

Please try it again with Moleculer 0.14 and Moleculer-web 0.9

Please try it again with Moleculer 0.14 and Moleculer-web 0.9

How to use with new version bro ?.thank

Please try it again with Moleculer 0.14 and Moleculer-web 0.9

Im upgrade to latest version.
type: "Winston", 			options: { 				winston: { 					transports: [ 						new winston.transports.Console(), 						new winston.transports.File({ filename: "d:/winston.log" }) 					] 				} 			}
How to use "bindings" to get nodeId or service name .... ? thank you


SDK v1.6.1 update

Description of changes:

Player SDK updated to v1.6.1

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

LGTM. Thank you for the PR! Will merge and close.


Use ioctl to create bridge

Please see commit notes for more information

LGTM

LGTM. Works on my CentOS 6.6.

Fixes https://github.com/docker/docker/issues/14174

Fixes https://github.com/docker/docker/issues/14024

@mavenugo I imagine it also fixes #312 then. Once 1.7.1 is released and I can verify #312 is fixed I can close it and docker/docker#14024

@visualphoenix Yes it fixes #312 as well.


Recurring Couldn't Get Process Limits Error

Hi,
Checking logs for a systemd-exporter - that works perfectly fine, ... out of curiosity - I'm finding about the following logs:
Apr 18 08:28:01 xxx systemd_exporter[16389]: time="2021-04-18T08:28:01+02:00" level=warning msg="couldn't get unit's metrics: couldn't get process limits: couldn't parse value<PHONE_NUMBER>3708503040<PHONE_NUMBER>3708503040 bytes: strconv.ParseInt: parsing \"18446744073708503040<PHONE_NUMBER>3708503040 bytes\": invalid syntax" source="systemd.go:332" unit=ntp.service
Apr 18 08:28:11 xxx systemd_exporter[16389]: time="2021-04-18T08:28:11+02:00" level=warning msg="couldn't get unit's metrics: couldn't get process limits: couldn't parse value<PHONE_NUMBER>3708503040<PHONE_NUMBER>3708503040 bytes: strconv.ParseInt: parsing \"18446744073708503040<PHONE_NUMBER>3708503040 bytes\": invalid syntax" source="systemd.go:332" unit=ntp.service
Apr 18 08:28:21 xxx systemd_exporter[16389]: time="2021-04-18T08:28:21+02:00" level=warning msg="couldn't get unit's metrics: couldn't get process limits: couldn't parse value<PHONE_NUMBER>3708503040<PHONE_NUMBER>3708503040 bytes: strconv.ParseInt: parsing \"18446744073708503040<PHONE_NUMBER>3708503040 bytes\": invalid syntax" source="systemd.go:332" unit=ntp.service

Looking into the systemd.go file, I figured out we're trying to read the /proc//limits file corresponding to my ntpd.
I could find back the value it's trying to parse:
# ps ax | grep ntp
 3416 ?        Ssl   27:56 /usr/bin/node_exporter --collector.interrupts --collector.ntp --collector.tcpstat --collector.processes --collector.systemd --web.listen-address=:9142
18793 ?        Ssl    0:06 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -c /run/ntp.conf.dhcp -u 110:116
20191 pts/0    S+     0:00 grep ntp
# cat /proc/18793/limits
Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            204800               unlimited            bytes
Max core file size        0                    unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             64010                64010                processes
Max open files            1024                 524288               files
Max locked memory<PHONE_NUMBER>3708503040<PHONE_NUMBER>3708503040 bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       64010                64010                signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0
Max realtime priority     0                    0
Max realtime timeout      unlimited            unlimited            us

I'm not certain: is that issue due to the exporter expecting to find a single value and parse it?!?
Or... looking at those values: are we overflowing some variable in memory?
Checking the procfs library, they do appear to use some uint64 for those ( https://github.com/prometheus/procfs/blob/master/proc_limits.go ).
Although this seems to be a recent contribution: https://github.com/prometheus/procfs/commit/f1596722788117109e9cacf38f4c8e34f5f8f949#diff-7d0cfb3195c0b0408bfcd91c47e8f9d8df3b4f27894687fec6068707d8b8b672
The version shipping with the systemd-exporter being 0.0.11 (https://github.com/povilasv/systemd_exporter/blob/master/go.mod#L14), we could probably update it.
Let me know if I missed something, or if I can help in any way.
Sorry I'm not familiar enough with Go to submit a proper PR ...

Fixed with https://github.com/prometheus-community/systemd_exporter/pull/50.


PICO-IMX8M-MINI: Update patch to support DT overlay commands in pico-…

Update in imx8mm.h
U-boot patch has to reflect the new change
Signed-off-by: Po Cheng<EMAIL_ADDRESS>

We had sent Miraz a pico-imx8mm + pi DUT. Could you please reach out to Miraz?

Hi @po-cheng-technexion
Mirza is not available at the moment due to personal reasons.
I see that the changes you're doing are for the TechNexion board which exists only on Zeus.
We have introduced the new program for community maintainers: https://github.com/mendersoftware/meta-mender-community/wiki/Community-maintainers
Would you like to become this for the TechNexion mender meta layer?

Hi @TheMeaningfulEngineer
Duo to personal reason, Po can't maintain TechNexion mender meta layer anymore.
I would love to join to mender community to maintain TechNexion mender meta layer.
Thanks~
BR,
Richard

Great @richard-hu thanks :)
I like to share a cup of coffee with all the maintainers to get to know them in an informal setting.
Can you please contact me on<EMAIL_ADDRESS>so we can start looking for a timeslot?

Hey @richard-hu @johnweber
shall we merge this or close the PR?

I see no reason why this cannot be merged.
@richard-hu, do you agree?

Just validate the build on our build server, it competes without problem.
Please merge it and close the PR.
Thanks @johnweber  @TheMeaningfulEngineer

Thanks, merging


[Feature]: About Vue's Code Block

这个功能解决了什么问题？
Can be highlighted in the Vue code block instead of pure black
你期望的 API 是什么样子的？
I hope it's not so pure black

There should be a highlight like this

Currently, rspress uses prism for syntax highlighting, but prism does not support vue for the time being. Here are the details https://github.com/PrismJS/prism/issues/1665.
However, you can use ```html instead.

Shiki is introduced here #345 .
And shiki seems to support vue syntax highlight https://github.com/shikijs/shiki/blob/main/docs/languages.md

@Yukiniro Thank you for your answer. I understand

I think this feature has been completed, reopen it if still have any issues.


[wxwidgets] Fix wrapper

Describe the pull request

What does your PR fix?
Fixes #27316.
Fixes https://github.com/wxWidgets/wxWidgets/issues/22843.

Which triplets are supported/not supported? Have you updated the CI baseline?
unchanged, no

Does your PR follow the maintainer guide?
yes

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
yes

Thanks for the fix!


Update and rename CHANGELOG to CHANGELOG.md

Description of changes:
Added build cache to a Major Changes section. I also edited the Breaking Changes to conform to our usual format.
Resolved issues:
Resolves #ISSUE-NUMBER
Related RFC:

Optional #ISSUE-NUMBER.
Call-outs:

Testing:

How is this change tested?

Is this a refactor change?

Checklist

[ ] Each commit message has a non-empty body, explaining why the change was made
[ ] Methods or procedures are documented
[ ] Regression or unit tests are included, or existing tests cover the modified code
[ ] My PR is restricted to a single feature or bugfix

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

@celinval , is it possible to merge this PR before today's release?


Extend rev-version to also update task.json build patch numbers

Right now --rev-version will patch the extension version, but leaves Build task versions alone. It would be lovely if --rev-version would also rev the build task versions.

I wonder if there is an elegant way to do this. Right now TFX doesn't know about build tasks. Maybe add an optional parameter to --rev-version which specifies a file and a JSON path to the version to get revved?
Something like... tfx extension create --rev-version tasks.json:version somethingelse.json:settings.version
Essentially that would rev the version specified in the manifest, as well as tasks.json's "version" property and somethingelse.json's "settings.version" property.

FWIW - I'd love to have this capability too. On a somewhat related note..
We always ended up having to write custom code in each task repo since tfx didn't have task bumping capabilities and we couldn't find any existing modules that easily supported bumping the task version object out of the box.
We decided to write a custom gulp plugin to provide support for bumping our VSTS tasks, in case that's useful for anyone that wants to bump their VSTS tasks as part of their gulp workflows.

And we've now also published a CLI/Lib - https://www.npmjs.com/package/vsts-bump that can be used for bumping the patch, minor, or major version of VSTS tasks. Not sure if could be utilized by tfx, but we're running the bump cli and then tfx i.e. vsts-bump tasks/**/task.json && tfx [command] which has been working pretty well for us.

Ci/cd tasks for vsts extensions provides support for this as well. I've recently added multi-version task support on top of syncing version numbers.

Nice @jessehouwing! I use the CI/CD tools extension for my own extensions and it works wonderfully.
There were 2 scenarios/use cases where I wished tfx could bump task versions too though (and why we ultimately developed the aforementioned libs):

The "inner" development loop process: I typically upload all of my custom tasks directly to VSTS as I'm developing to test/validate (even if I ultimately publish them as an extension on the marketplace)
Private Tasks: at work we have a variety of custom tasks that we don't package as an extension and publish the marketplace, we just use tfx to upload the new versions to our accounts

@calebcartwright probably unrelated, but do you publish your extension straight out of CI? Or, do you do it manually?
Also, I wanted to show support for fixing this issue. The version in the task.json when not bumped along with the version number in the vss-extension.json, it is very confusing, which version of the task the Az DevOps Agent is running. The version number displayed in the agent is actually from task.json, so it can be quite confusing if one hasn't taken care to bump both versions at the same time the updated extension is published.

It's why the Azure devops extension tasks actually overwrite both the task
and the extension versions from the CI.
On Tue, 30 Apr 2019, 22:25 Praneet Loke<EMAIL_ADDRESS>wrote:

@calebcartwright https://github.com/calebcartwright probably unrelated,
but do you publish your extension straight out of CI? Or, do you do it
manually?
Also, I wanted to show support for fixing this issue. The version in the
task.json when not bumped along with the version number in the
vss-extension.json, it is very confusing, which version of the task the
Az DevOps Agent is running. The version number displayed in the agent is
actually from task.json, so it can be quite confusing if one hasn't taken
care to bump both versions at the same time the updated extension is
published.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/tfs-cli/issues/262#issuecomment-488102049,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA724S75GJVYJFEFY223RZTPTCTNFANCNFSM4EVW4CEQ
.

@jessehouwing I am sorry, but I don't follow what you said.

@calebcartwright probably unrelated to this issue, but do you publish your extension straight out of CI? Or, do you do it manually?

@praneetloke -
For public extensions that we publish to the marketplace, we use a Release pipeline in Azure DevOps to do the final publishing piece (like our ShellCheck extension for example: https://github.com/swellaby/azdo-shellcheck/blob/master/.github/CONTRIBUTING.md#deployment)
In any repository we have that contains AZP tasks, we always add tfx-cli and vsts-bump as dev dependencies with various npm scripts to leverage those tools. We find this model works best for us as it supports the development process (in particular being able to upload individual tasks as part of the dev loop for validation), and it also gives you a consistent experience to version and package the extension.
Our CI job will leverage those same npm scripts (utilizing tfx-cli and vsts-bump) to bump the various versions and create the .vsix package. Our release pipeline then utilizes the Azure DevOps Extension Tasks extension @jessehouwing referenced to help facilitate a variety of tests against the .vsix, and then finally to publish the .vsix package to the marketplace

@calebcartwright thanks for the link to the DevOps Extension Tasks extension! The name is a little confusing, but I get it now.

I've debated so many names... And this was the best I came up with.
On Wed, 1 May 2019, 03:39 Praneet Loke<EMAIL_ADDRESS>wrote:

@calebcartwright https://github.com/calebcartwright thanks for the link
to the DevOps Extension Tasks extension! The name is a little confusing,
but I get it now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/tfs-cli/issues/262#issuecomment-488171957,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA724S6UUSFTY5S2AZZ4ME3PTDYEFANCNFSM4EVW4CEQ
.

The name is just DevOps Extension Tasks.  I think he was just confused about the last "extension" word in the original link, which isn't actually part of the name.

Are there plans to add this to the product backlog and try to resolve / fix this? Or is this issue still open pending a decision?

fix what

To fix/enhance --rev-version so it also rev the build task versions (in task.json for example).

That would result in changes to version control; I think it's by design that they don't do that

For those using "Azure DevOps Extension Tasks extension" to bump the version of the extension/tasks - How do you get it to actually bump the version in the repo containing the extension? As it only updates the version in the artifact/code downloaded by the agent and lives in the agent's working directory. Meanwhile the version in the actual repo containing the extension code remains the same. And next time you make a change to the extension and run the pipeline to publish, it errors because it tries to bump the version to the same number it did last time.

This is just to get around manually bumping the version yourself, right? Wouldn't you want that step to be manual?  Are we sure we want tfx to change source files?  Does it have to commit the changes and add a comment, too?

This is just to get around manually bumping the version yourself, right? Wouldn't you want that step to be manual?

--rev-version is an optional flag that users can leverage when they want to automate the version management process. Folks that want to manually manage their versions can of course not use that optional flag.

Are we sure we want tfx to change source files?

In my experience the extension manifest file is always checked into source control, and --rev-version already modifies this file. The ask of the issue is to have the ability to extend this to the task manifests as well, which yes are also in version control, but there wouldn't be anything novel with the ask relative to versioned files given the existing behavior.

Does it have to commit the changes and add a comment, too?

IIRC tfx with --rev-version does not commit, but that's not really the topic at hand nor what's been asked for. Today with current behavior on the extension manifest it's up to users whether or not they want to commit the modified file after running tfx. That would continue to be the case if the requested feature was provided
I do think it's worth noting that the packaging tool for VS Code extensions, vsce, does have optional support to also commit and tag the changes for users that want that in their workflows, but that's a separate topic.

I don't think it's a good idea to have release jobs changing source code.

I wouldn't jump to the assumption that --rev-version is exclusively being executed from a "release" job. There's a lot of scenarios including inner dev loop flows as well as what some might call "build" jobs where it's common to use this feature, but ultimately context matters and the non-default options exist for those that need/want them. Folks that don't want them are free to not use them :smile:

Usually, though, wouldn't we want our inner dev loop flows to be reproducible as release jobs?  If we're testing our latest changes, we have to do some kind of deployment ("release")*1 don't we?
*1:  I personally normally think of "release" as a production deployment, and I think that's the correct

The problem with the current behavior of --rev-version is that it yields a
new extension version without revving the tasks. Azure Pipelines will
therefore not push out the new version to the agents and will cause strange
behavior during the dev loop.
What I tend to do is to auto set the version on each commit and publish a
dev version so I can easily test in a real agent. I now use a script to do
what the rev-version should do and what works for other kinds of extensions
that don't include build tasks.
Having rev-version fix the task manifests will make the optional flag work
for UI extensions as well as Pipeline extensions.
On Sat, 4 Sep 2021, 08:16 Paul Abrams, @.***> wrote:

Usually, though, wouldn't we want our inner dev loop flows to be
reproducible as release jobs? If we're testing our latest changes, we have
to do some kind of deployment ("release")*1 don't we?
*1: I personally normally think of "release" as a production deployment,
and I think that's the correct
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/tfs-cli/issues/262#issuecomment-912917598,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA724S7QQU5RH2DDO2W26NTUAG2STANCNFSM4EVW4CEQ
.


Document when each part of the API was added

For those that are trying to target old versions of sketch it's incredibly useful to know when I have to drop down to some sketch headers / appkit methods.
For example, in Apple's documentation there is a little SDK version number to help you know what version of MacOS it is supported with.

That's a really good point, haven't had time to implement it yet.
I guess it would also be helpful to be able to navigate the docs for a specific version
cc @christianklotz

I'm currently working on the documentation and including the availability of APIs would be very good indeed since we can't expect people to derive that information from the various branches.
I know that Apple generates this from source code annotations, e.g.
@available(OSX 10.9, *)
class Foo : NSObject {

}

Any suggestions for a streamlined process like this, which could also be useful for deprecations.

oo looks like lodash uses some sort of @since notation https://github.com/lodash/lodash/blob/master/union.js#L10


phase 1 thread failed with: input not sorted

I set  -n 5,      The exception fire every time at [ plot 2 out of 5 ]  , is this ram problem ??? ,  why always be 2 of 5 , not others ?
and  if set n =1 , plot one by one , it work pretty good.
Crafting plot 2 out of 5
Process ID: 18443
Number of Threads: 20
Number of Buckets P1:    2^7 (128)
Number of Buckets P3+P4: 2^7 (128)
Pool Public Key:   8bdf9b303e5723710d477af2eaf07b3e9a0141592fab541c06454a8a5e211a3106267a983eec3e91f323270e8b1bc24d
Farmer Public Key: a2920a6b8e5ed1c6e5a7a3b9b53588d3328ad2a78ecfffb57f4a7425bc7d63e3720f64c7d06fc489926a0de8aa8211b9
Working Directory:   /nvme01/
Working Directory 2: /mnt/ramdisk/
Plot Name: plot-k32-2021-06-26-16-15-0d563cc0920be05da07ab5efa77008a230ed4ad4075ca6cc93520cf3ec207410
[P1] Table 1 took 13.9791 sec
[P1] Table 2 took 94.8257 sec, found<PHONE_NUMBER> matches
[P1] Table 3 took 116.015 sec, found<PHONE_NUMBER> matches
terminate called after throwing an instance of 'std::runtime_error'
what():  thread failed with: input not sorted
Aborted (core dumped)
build chia_plot with this commit .
git log --pretty=oneline
a1f270915777da617f2352657232a6d3e98e1004 (HEAD -> master, origin/master, origin/HEAD) detect final rename and show different message
373b057cb751e697a6ded22be62ae52dca2dc59e use estimated file size for rename() copy
e84b215bbf8a060e3a0fef28b4d96977c8a1408e Merge pull request #664 from roxleopardo/patch-2
08bdcaf419eba51fbc87828fe9d8bebb707c5453 usage update
5cad61de7cceec09c53dd50b785824059d8f86c8 Merge pull request #665 from GTANAdam/master
e3e716aa69b185fed05397be85943af3ae165ecf Revert "Introduction of --hwinfo parameter at the cmd line"
e6cc095963c6ab4a848d1856ad1bfae90f9cebbf Update README.md
a0430c65157bd05faad7af9178c639b8fbd1d408 Merge pull request #627 from Randomblock1/readme

same issue here

getting the same issue

usually that's unstable RAM

Max,
Thank you for the information. I have reset my memory setting to auto and
everything is running smoothly now. I am really liking the plotting time in
the minutes compared to hours.
On Mon, Jun 28, 2021 at 3:56 AM Max @.***> wrote:

usually that's unstable RAM
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/madMAx43v3r/chia-plotter/issues/679#issuecomment-869546785,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABR7G34R7ZI6IZ7BRT5C3WLTVBBM7ANCNFSM47LFSPQA
.

--
George Nazarey
@.***
@.***
To solve the problem is a task.
To understand the problem is knowledge.
fortuno, fortuno, gaudium, gaudium
Computer Science is all about trying to find the right wrench to bang in
the right screw. -T.Cumbo

@madMAx43v3r i've reset memory to auto first, then even decrease frequency - still same error(((

@madMAx43v3r also checked memory - seems to be fine..
root@chia1:~# memtester 120000 1
memtester version 4.5.0 (64-bit)
Copyright (C) 2001-2020 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 120000MB<PHONE_NUMBER>00 bytes)
got  120000MB<PHONE_NUMBER>00 bytes), trying mlock ...locked.
Loop 1/1:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Done.

please advice what to check...

such a short check is not proof of stable RAM, need to do more mem checking, for like 1 hour

guys, here is my case, fyi. it DOES NOT work with default bios settings (error: terminate called after throwing an instance of 'std::runtime_error' what(): thread failed with: input not sorted) after phase 2, but DOES work with overclocked preset (higher CPU frequency and higher memory voltage). I dont know why but it work... maybe it will be helpful for others.

i also have this problem and i was confused about over clocks confog
i try for 10 days and nothing
over clock, under clock and every thing you think does not help
but a 1$ Fan solve my problem at ALL
i always had a "core dump" error in phaze 1 and some times in phaze 3 when i touched the RAM heat sinck with my hand  it was realy hot   very hot
so i use a fan to cool it
after instaling the fan every error gone for ever
it is now plotting 55 plot and no problem at all
anf RAM is so cool that you can touch it with hand like a charm
so HEAT is my problem and i think difrence between good servers and home computers is this
my system config :
x570 tuf gaming
ryzen 3950x
128 gb Ram Gskill
plot time 33 min

happened just once (after hundreds of successful plots)
[P1] Table 1 took 19.0599 sec
terminate called after throwing an instance of 'std::runtime_error'
what():  thread failed with: input not sorted
Aborted (core dumped)


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit a444ac1:
:clock10: Full build: the average full build time is 6 min(s) 5 sec(s), this is based on the last 354 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

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

File
Status
Preview URL
Details
Dependent Files

docs-ref-conceptual/testing.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

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


Remember last opened folder with FileBrowser

Jodit Version:  3.6.16
Browser:  Chrome/IE/Safary/FF
OS: Mac
Is React App:  False
Context
I have a folder tree:
Root

Folder 1

Folder 1.1

Folder 1.2

Folder 2

Folder 2.1

Folder 2.1.1

Folder 2.1.2

Folder 2.2

....

Expected behavior:
Today, I only work with folder name "Folder 2.1.2", I upload some files into it.  Some days after, I can not remember the last folder name I worked.
Actual behavior:
Always open the root folder.

Hi.  I am struggling with the file manager... can you help with a simple working example?