Patch CVE-2023-45853 for boost

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

What does the PR accomplish, why was it needed?
Fix CVE-2023-45853 for boost
Change Log

CVE-2023-45853

Does this affect the toolchain?

NO
Associated issues

#xxxx

Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-2023-45853

Test Methodology

Pipeline build id: 441203

Auto cherry-pick results:

main :white_check_mark: -> https://github.com/microsoft/CBL-Mariner/pull/6608

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=441624&view=results


(Fix) Update deployment constants for Token Wizard 2.0

The current deployment constants:
export const DEPLOYMENT_VALUES = {
  GAS_REQUIRED: {
    DEFAULT: 8044737,
    WHITELIST: 96040,
    RESERVED_TOKEN: 42220

  },
  TX_REQUIRED: {
    DEFAULT: 3,
    WHITELIST: 1,
    RESERVED_TOKEN: 1
  }
}

Required max gas constants are outdated. Should be updated for Token Wizard 2.0 deployment.

https://github.com/poanetwork/token-wizard/wiki/Token-Wizard-Deployment-Time-and-Gas should be changed also


QA Org 2gp runs install scripts

Critical Changes
Changes
Issues Closed
New Metadata
Unpackaged Metadata
Deleted Metadata
Testing Notes
Run qa_org_2gp against a prerelease org shape

It looks good. I second Samsheeth's suggestion on avoiding running duplicate flows/tasks.

@MatthewBlanski  You may or may not wish to hold this PR. We are releasing a fix to CumulusCI today that will have 2GP packages run install scripts correctly.

DO NOT merge until further notice.

QA Testing Passes - Will merge on Monday


misc:new_window_takes_over_fullscreen = 1 is not making new window takes over if fullscreen is maximize by fullscreen, 1

Hyprland Version
 System/Version info
Hyprland, built from branch HEAD at commit d74607e414dcd16911089a6d4b6aeb661c880923  (props: bump ver to 0.33.1).
Tag: v0.33.1

flags: (if any)

Bug or Regression?
Bug
Description
Actually I'm not sure it is a bug or not. But it is not as expected, I think. Dispatcher fullscreen has 1 option that is similar to maximize rule of window rules to my understanding. And misc:new_window_takes_over_fullscreen = 1 means new window takes over fullscreen. But it only works if fullscreen is not maximize or fullscreen, 1. It shows only red border suggesting a new window opens under the current fullscreen, 1 window.
How to reproduce
Set misc:new_window_takes_over_fullscreen = 1. Open two windows and dispatch fullsccreen, 1 and open third window. It will only show red border suggesting the third window opened under the current fullscreen, 1 (maximize) window.
Crash reports, logs, images, videos
No response

Did you find a solution for this?


Client Allocation Request for: Shanghai Huiya

Client Allocation Questions
Core Information

Name: Shanghai Huiya
Website / Social Media: www.shhuiya.com
Region: Greater China
DataCap Requested: 50TiB
Addresses to be Notarized: f1dvqutfi4m53vl7wxl7xvdjk7fbcebk5hjzznxwi
Notary Requested: neogeweb3

@Huiya2 Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Hey, thanks for the request. I have some questions regarding your request. Please describe answers as much specificity as you can.

Can you introduce yourself? Where can I find you online? (Github, Twitter, Linkedin handle, Wechat, etc.)
If you represent an organization, what is the name, nature, registration country, time since inception, and named officers of your organization?
In which region(s) do you intend to use the DataCap?
What is your use case for the DataCap being requested?
Do you plan to specify advanced features when utilizing a DataCap in your storage deal? If so, please specify the feature.
How many miners do you plan on allocating the DataCap? If you have a specific miner(s) you would like to allocate a DataCap, please specify.
Do you agree on providing transparency of DataCap allocation decisions & execution details in public to prevent excessive/unfair (20% of DataCap allocation) self-dealing?

Moreover, I encourage you to take a look of my allocation strategy  and flow which shows how I utilize the assessment. Thanks.

I'm Roger, CEO of Huiya. My Github: Huiya2
My company is Huiya. Shanghai Huiya Information Technology Co., Ltd. is a "double-software" software company recognized by the Shanghai Municipal of Economic and Informatization. My company was established in September 2007. In February 2012, my company obtained the "Huiya" and related LOGO trademark registration certificate.
Mainly China, maybe other countries.
I want to store live videos.
NO.
4 miners.
OK, I'm agree with it.
@neogeweb3

Can you provide some proof that you are the CEO of Huiya? What would be the best email I could reach out to you, I will need a work email under the domain shhuiya.com, thanks.

Sorry it took so long to see this,  this is my work email<EMAIL_ADDRESS>

Hi Roger, thanks for your email. Are you able to provide some clarity around the concerns raised in your LDN request? I will need these answers to process your allocation request.

f01870475
f01850141
f047666
f061666
@neogeweb3 We communicated with these SPs for application.

Allocation was successful: https://filfox.info/en/message/bafy2bzaceauwkgkspzj2zv2y6awiiq4xqowpv64ddo2t6ucu6zb6nsiw3m7b6


New Telegram Notification

New Telegram Notification “AutoBuyer has started” “AutoBuyer has stopped” cannot be disabled in an way on latest release. Could you please add an option to disable it ? It’s really distracting since the bot notifies you every couple minutes… thanks a lot for your work!

It looks like it’ll still send those notifications even if set to B or L. Just tested it on Chrome on macOS.

@ckalgos Don’t want to bother you, just wanted to know if you also have noticed the same behavior. It looks like it’s ignoring the B or L setting altogether and still giving the AutoBuyer has started / stopped notification.

Problem fixed on latest release, thanks a lot for your hard work!


Swift 3.0.2 support.

Hi, are you planning on releasing Paper Onboarding for Swift 3.0.2 and when will you do this?
Thanks.

PaperOnboarding supports Swift 3.1


Go: Mitigate a crash resulting from tag mismatch. [phab:D1491]

Created by fromberger at 2017-04-05 03:54:03:
If the indexer gets a compilation whose source list contains files with
incompatible build tags,[1] it is possible to drive the indexer into a state where
it has competing incompatible declarations for what should be a single type or
function.
To fully fix this, we will need to be smarter about handling build tags; if the
extractor can't do this sensibly (which apparently it doesn't now), we may have
to teach the indexer to handle it.
For the moment, just stifle the crash.
[1] http://godoc.org/go/build#hdr-Build_Constraints

salguarnieri wrote at 2017-04-05 14:40:17:
What is a build tag?

salguarnieri accepted this revision at 2017-04-05 14:40:17

fromberger wrote at 2017-04-05 14:47:55:

! In (earlier comment), salguarnieri wrote:
What is a build tag?

I added an explanatory link to the description.

fromberger closed via commit 40a4cc077f5099f658ecf8f86a3722caccc81406 at 2017-04-05 14:48:31


Disable checking of write permissions on PRs

TODO:

[x] what about Koji? keeping as is?

Disables checking of user's write permissions in the repository that PR
is created against.
Fixes #920
Signed-off-by: Matej Focko<EMAIL_ADDRESS>

yes, please let's leave koji as it is now and do this only for the CI PR builds

yes, please let's leave koji as it is now and do this only for the CI PR builds

nice, LGTM!
interesting that no tests need an update 🤔

removed code is unreachable, it gets denied even sooner 🙃😪

nice, LGTM!
interesting that no tests need an update 🤔

removed code is unreachable, it gets denied even sooner 🙃😪

@TomasTomecek @lachmanfrantisek please check, there is also description of allow/deny changes in last commit

@TomasTomecek @lachmanfrantisek please check, there is also description of allow/deny changes in last commit

GitLab namespace

BTW, do we differentiate between git-forges? What about GitLab namespace, that matches the name of the GitHub one that is whitelisted...

GitLab namespace

BTW, do we differentiate between git-forges? What about GitLab namespace, that matches the name of the GitHub one that is whitelisted...

GitLab namespace

BTW, do we differentiate between git-forges? What about GitLab namespace, that matches the name of the GitHub one that is whitelisted...

there's no difference between user and namespace either

GitLab namespace

BTW, do we differentiate between git-forges? What about GitLab namespace, that matches the name of the GitHub one that is whitelisted...

there's no difference between user and namespace either

also I could probably switch the naming of whitelist since I'm probably going to touch the database because of github vs gitlab

also I could probably switch the naming of whitelist since I'm probably going to touch the database because of github vs gitlab

Sorry for another group of comments...

definitely won't be last one till finish :D

Sorry for another group of comments...

definitely won't be last one till finish :D


testing using locally published instance of incrementalcompiler

Publish incrementalcompiler locally and try using it from Zinc etc.
problem
[info]  + ! zinc -status
[error] ! zinc -nailed -debug -d a/target/classes -analysis-cache a/target/analysis/compile a/src/A.scala
[error]   /xxx/work/zinc/src/scriptit/analysis/cache/test:5
[error]   [error] Required file not found: compiler-bridge_2.10-sources.jar
[error]   [error] See zinc -help for information about locating necessary files

notes
I am guessing this is because of the layout difference between Maven and Ivy.
Are we using
"org.scala-sbt" % "compiler-bridge_2.10" % incrementalVersion withSources(),

equivalent or
"org.scala-sbt" % "compiler-bridge_2.10" % incrementalVersion classifier "sources",

?
/cc @Duhemm

Maybe this is due to the way zinc is set up.
classpathTypes += "src"

solved my issue, I think.


Requesttracker: Feature - ability to upload files using MIME types

Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[X] Testing of all the changes has been performed (for bug fixes / features)
[ ] The readme.html has been reviewed and added / updated if needed (for bug fixes / features)
[X] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[ ] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[ ] Verify all checks are passing.
[X] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[ ] Do NOT submit updates to dependencies unless it fixes an issue.

Pull Request Type
Please check the type of change your PR introduces:

[ ] New App
[ ] Bugfix
[X] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other (please describe):

Security Considerations (REQUIRED)

[ ] If you are exposing any endpoints using a REST handler,
please document them in the readme.html.
[ ] If this is a new connector or you are adding new actions

[ ] Please document in the readme.html all methods (eg, OAuth) used to authenticate
with the service that the connector is integrating with.
[ ] If any actions are unable to run on SOAR Cloud, please document this in the readme.html.

[ ] Are you introducing any new cryptography modules? If yes, please elaborate their purpose:
[ ] Are you are accessing the file system? If yes, please verify that you are only accessing paths returned through
the Vault API.
[ ] Are you are marking code to be ignored by Semgrep with nosemgrep?
If yes, please provide justification in an additional comment next to the ignored code.

Release Notes (REQUIRED)

Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.

What is the current behavior? (OPTIONAL)

Describe the current behavior that you are modifying.
When uploading images into RT, those images are not rendered in the ticket.

What is the new behavior? (OPTIONAL)

Describe the behavior or changes that are being added by this PR.
By adding the MIME type eg. image/png, the image will be rendered inside the ticket body

Other information (OPTIONAL)

Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

Thanks for contributing!

Hi @iciubotarasu, Instead of using extra parameter for file type, we have used the field mime_type in file_info return from vault info API. which determine mime type of file itself.
Refer this: https://docs.splunk.com/Documentation/SOAR/current/PlaybookAPI/VaultAPI


Creating a Card for Likability in the UI Page

User Story: I want to be able to express my liking for content or features by interacting with a likability card on the UI page, so that I can engage with the website in a positive and interactive manner.
Actions: Design a visually appealing card that represents likability, potentially including icons, emojis, or other visual elements.
Results: Users visiting the UI should see the likability card and be able to interact with it to express their liking.


Run test win

In this PR:

actually run the tests on Windows;
do not build the conda recipe on Travis-CI;
test the source distribution creation (in case we decide to upload to PyPI).

There is a flaky test for Python 3.5 that seems to fail randomly: https://travis-ci.org/ocefpaf/pocean-core/jobs/217282767
I will investigate this later today and some tests are failing on Windows.

Most of the Windows tests are failing due to the file lock.

Huh, interesting.

Huh, interesting.

Let me know if you figure out a better way to fix that.
PS: Now that the tests are passing on Windows is it OK to mint a release?

Yup, all set. Can you do it? I'm busy until tonight

Yup, all set. Can you do it? I'm busy until tonight

Sure.

Wow, great work guys!  Thanks!


How can I do data augmentation to special classes?

My datasets is just like 100 dogs, 10 cats and 20 pigs.But I only want to do do augmentation on cat class and pig class.How can I change the config file.I used mask rcnn for training instance segmentation.Thx a lot.

或者直接对少的类别过采样就可以？请问是先采样再做数据增强还是先做数据增强再采样？

If you consider balancing by sampling, you can use ClassBalancedDataset


♻ 🧪 Introduces an e2e test methodology

Purpose
This PR introduces an e2e test methodology based on Gherkin, a textual, behavior-oriented approach that is human-readable, simple to implement, and highly extensible. This is the same approach adopted for the axone-protocol/axoned repository as seen in this PR.
Objective
This approach has several aims. First and foremost, while our test coverage is currently excellent, it suffers from a number of weaknesses:

The Tester Experience (TX) is suboptimal because writing tests in Rust is difficult to implement, develop, and maintain, especially regarding the complexity of some data types (like the ones used for querying).
The secondary objective of serving as a functional repository and documentation is not fully realized due to the complexity of Rust-based tests.

Gherkin's approach addresses these issues by focusing on the feature itself and introducing a DSL that simplifies the process of writing and understanding tests. This DSL allows for more readable and maintainable tests, improving both the implementation and documentation aspects of our project.
Changes
To pave the way, this PR introduces a very basic Gherkin test suite that allows for the execution of InstantiateMsg and ExecuteMsg for the InsertData operation onto the Cognitarium Smart Contract. This lays the groundwork for a more user-friendly and maintainable testing framework I believe.

size-limit report 📦

Path
Size

target/wasm32-unknown-unknown/release/axone_objectarium.wasm
395.17 KB (0%)

target/wasm32-unknown-unknown/release/axone_law_stone.wasm
596.25 KB (0%)

target/wasm32-unknown-unknown/release/axone_cognitarium.wasm
760.48 KB (+0.06% 🔺)

target/wasm32-unknown-unknown/release/axone_dataverse.wasm
621.05 KB (+0.01% 🔺)


Video detail watch

Removed files from project that we don't need.

I reviewed this and it looks positively awesome. Great job.


Return unknown if position is over 100

Fix #44

I don't see the link with the issue.

@tetienne sorry, the context was in a PR linked to that issue. https://github.com/iMicknl/ha-tahoma/pull/48#issuecomment-654299947

@tetienne sorry, the context was in a PR linked to that issue. #48 (comment)

Oh that's why there was an offset in the previous code?

@tetienne sorry, the context was in a PR linked to that issue. #48 (comment)

Oh that's why there was an offset in the previous code?

Nope, that offset is not related to this issue. That was even older legacy code. :)

Meanwhile I was able to try out this fix based on #187 (#172 was already merged to master). In my case it works as expected. Thank you all for your effort fixing this issue.


Optimization

WIP

When I profiled, nothing VFPT / FCS related was executed in UI thread :( It must be blocked waiting for a background thread to complete ==> UI freeze.

Done :)

Although it does not freeze in my scenario anymore, code editing is not absolutely smooth (as in Xamarin, for example).

I doubt we will ever make unused (open) declarations fast enough. Moreover, FSharpBinding in Xamarin Studio didn't have incremental multi-project checking last time I checked.

Scenario:

Turn on "Resolve unopened namespaces" and both "Gray out..." (I have not tried with these options off though)
Add Seq.filter (fun x -> Thread ) into this pipe https://github.com/fsprojects/VisualFSharpPowerTools/blob/master/src/FSharpVSPowerTools.Logic/QuickInfoMargin.fs#L119
Wait until "add open declaration" smart tag appears
Play with Thread word a bit (delete it, type it again and so on)
After 30 seconds of this game UI frizzed for very long time, now the lags is about 1 second or less

In short, just try to edit any error-squizzled code (preferably a large area of such code) in a not-so-small project.


Custom chunks and STL iostream read/write

Hello, I'm looking to replace tinygltf with something more flexible. Both tinygltf and fx-gltf don't have support for reading from std::istream and writing to std::ostream which is essential for my application, and I think it's better abstraction and more flexible than filenames, and assuming the client wants to use filesystem to store possibly intermediate data.
Another problem with both libraries is lack of support for custom chunks in the binary input/output. My application works with single .glb file containing all the vertex and image data, and also utilizes JSON extra and custom binary chunk for storing app specific data.
I would like to contribute to this library and I'm wondering if there's a will in the upstream to merge these improvements. Thank you

Hi Skrat, thanks for the suggestions and the PR.  I think having an iostream interface option sounds reasonable at first glance and I'd be willing to see how that might integrate here.  As for the extra chunks, I will need to think about that a bit.
My time is somewhat limited these days but I'll leave some initial comments from my very brief look through the code in a bit.  It would be best if these were submitted as 2 separate PRs though to keep things separated.

As a followup for the extra chunks, I spoke a little bit with the folks running glTF and I'll update this comment here as replies come in etc.
Summary:

Prefer to use custom bufferViews into the main BIN chunk for custom data (all the machinery is already in place as bufferViews let you know how/where to access it)
In either case, extensions should be used to identify how to access the extra custom data
Using new chunks is technically supported but doesn't seem to have much use (padding with 0x00 bytes to hit alignment requirements is probably fine)

Ed Mackey [10:30 AM]
@deadpin Rather than do that, I think a more standard approach would be to store the custom data in its own bufferView view into the single GLB binary chunk.  A glTF extension could be used to specify the index of which bufferView holds the custom data.
Don McCurdy [11:22 AM]
@deadpin @VPenades @Ed Mackey I agree with Ed that using a bufferView would be the more standard approach. That said, I believe it is valid to append custom chunks after the default two. From https://github.com/KhronosGroup/glTF/blob/master/specification/2.0/README.md#chunks –

Client implementations must ignore chunks with unknown types to enable glTF extensions to reference additional chunks with new types following the first two chunks.
(edited)

In either case, an extension should be included to identify the model as non-standard.

iostream support has now been checked in to master.


mkdocs: Use symlink alias types

Using symlinks allow deep linking into a particular version of the documentation.

Fixed conflicts, needs a new approval.


Setup automation with pre-commit-mirror-maker

We're gonna stick to the patterns in pre-commit-mirror-maker, which means:

use setup.py instead of pyproject.toml to declare the dummy package
remove .pre-commit-config.yaml, as that file isn't necessary here

@charliermarsh I was able to test this locally, but in order to get this running, we'll need to:

merge this PR
delete the existing tags
manually trigger the workflow (or wait until it runs automatically on schedule)

I can push the commits with the versions here, but that won't include the tags.

Awesome! Will review in the AM. Will this retroactively create tags for all past ruff versions? Or only future releases?

Awesome! Will review in the AM. Will this retroactively create tags for all past ruff versions? Or only future releases?

It does it retroactively too, with one commit and one tag for each. Here's the output from running it locally:

pre-commit-mirror --language python --package-name ruff --entry ruff --types python --description "Run ruff to lint

％ pre-commit-mirror --language python --package-name ruff --entry ruff --types python --description "Run ruff to lint Python files." --args='--fix' .
[automatic c1b93e0] Mirror: 0.0.13
 3 files changed, 21 insertions(+), 7 deletions(-)
 create mode 100644 .version
 create mode 100644 setup.py
[automatic ff29202] Mirror: 0.0.14
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 807ff2b] Mirror: 0.0.15
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 8950f85] Mirror: 0.0.16
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 7bcbc06] Mirror: 0.0.17
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 5321cc4] Mirror: 0.0.18
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 0f031dc] Mirror: 0.0.19
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 28ad5c6] Mirror: 0.0.20
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 97ec025] Mirror: 0.0.21
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic a2b2298] Mirror: 0.0.22
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 0130159] Mirror: 0.0.23
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 255ed62] Mirror: 0.0.24
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 390eacf] Mirror: 0.0.25
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic d090bed] Mirror: 0.0.28
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 43483eb] Mirror: 0.0.29
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 6055e0c] Mirror: 0.0.30
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic e5a5dd3] Mirror: 0.0.31
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic d85eae3] Mirror: 0.0.32
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 9bee895] Mirror: 0.0.33
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 77d37c1] Mirror: 0.0.34
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic d8b7d6f] Mirror: 0.0.35
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 3029016] Mirror: 0.0.36
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic ae828ad] Mirror: 0.0.37
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic af03f87] Mirror: 0.0.39
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 7afb91f] Mirror: 0.0.40
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic b72ce1f] Mirror: 0.0.42
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 0b6f7a1] Mirror: 0.0.43
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 5ace987] Mirror: 0.0.44
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 3c52d65] Mirror: 0.0.45
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 2514d93] Mirror: 0.0.46
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic f5a9492] Mirror: 0.0.47
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic d0b6d6a] Mirror: 0.0.48
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 2d70e0c] Mirror: 0.0.49
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 4dbd7fd] Mirror: 0.0.50
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic aa31ab3] Mirror: 0.0.51
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic c78e5a7] Mirror: 0.0.52
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic aa1f45c] Mirror: 0.0.53
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic aaf1833] Mirror: 0.0.54
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 6be1dbf] Mirror: 0.0.55
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic cc01b7c] Mirror: 0.0.57
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 435b228] Mirror: 0.0.58
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 0eb1b65] Mirror: 0.0.59
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 7f8fa0d] Mirror: 0.0.60
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 4e61eef] Mirror: 0.0.61
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 6d361c9] Mirror: 0.0.62
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 8ae64b6] Mirror: 0.0.63
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 4913c9f] Mirror: 0.0.64
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 38ebc46] Mirror: 0.0.65
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 8c48278] Mirror: 0.0.66
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 9337378] Mirror: 0.0.67
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 5f8be0b] Mirror: 0.0.68
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 827a4b0] Mirror: 0.0.69
 2 files changed, 2 insertions(+), 2 deletions(-)
％ cat .pre-commit-hooks.yaml
-   id: ruff
    name: ruff
    description: 'Run ruff to lint Python files.'
    entry: ruff
    language: python
    'types': [python]
    args: ["--fix"]
    require_serial: false
    additional_dependencies: []
    minimum_pre_commit_version: '0'

It also write a local file called .version with the latest version, so if you want to have it only create the versions after 0.0.65, we could create a file named .version and write 0.0.65 to it, in that case the script would only create the tags after that:
％ echo 0.0.65>.version
％ pre-commit-mirror --language python --package-name ruff --entry ruff --types python --description "Run ruff to lint Python files." --args='--fix' .
[automatic 8c3e1f9] Mirror: 0.0.66
 3 files changed, 21 insertions(+), 7 deletions(-)
 create mode 100644 .version
 create mode 100644 setup.py
[automatic 7253cdf] Mirror: 0.0.67
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic 4131e48] Mirror: 0.0.68
 2 files changed, 2 insertions(+), 2 deletions(-)
[automatic c096fd3] Mirror: 0.0.69
 2 files changed, 2 insertions(+), 2 deletions(-)
％ git tag
v0.0.66
v0.0.67
v0.0.68
v0.0.69

If you prefer that, I can include that .version file in this PR.

Okay cool -- looks great! I'll follow the steps you outlined above.

Worked perfectly!
One issue is that we used --entry ruff when it should be --entry lint I think?

One issue is that we used --entry ruff when it should be --entry lint I think?

Hmm, I just tested and it seems to work? Is lint a sub-command or something like that? entry is the executable that will be executed, so if we want to run something like ruff lint, we'd set entry to ruff and pass lint as an argument.

Yeah it totally works! It just may not be backwards compatible?
E.g., I had this in an existing repo:
repos:
  - repo: https://github.com/charliermarsh/ruff-pre-commit
    rev: v0.0.69
    hooks:
      - id: lint

Which now yields:
[ERROR] `lint` is not present in repository https://github.com/charliermarsh/ruff-pre-commit.  Typo? Perhaps it is introduced in a newer version?  Often `pre-commit autoupdate` fixes this.

I had to change to:
repos:
  - repo: https://github.com/charliermarsh/ruff-pre-commit
    rev: v0.0.69
    hooks:
      - id: ruff

Ohh I see, my bad, didn't realize that that was the case. In that case we should've done --entry ruff --id lint to keep it backwards compatible.

I think the only way to resolve would be to delete all tags + the last ~70 commits, then re-run the process -- is that right?

I think the only way to resolve would be to delete all tags + the last ~70 commits, then re-run the process -- is that right?

You can just delete the tags and delete the .version file, then re-trigger the workflow. You'll have the ghost commits in the history, but they won't be tagged, so it should be fine.

Oh ok, in that case, maybe I'll go ahead and do that. Thanks :)

Okay great, I think that worked! Thank you. I have a better understanding of how this works now too.
I did disable --fix by default, can we make that a parameter in some way instead? I think it should be opt-in.

I did disable --fix by default, can we make that a parameter in some way instead? I think it should be opt-in.

Yeah, users can use args to set it in their configuration! Something like:
repos:
  - repo: https://github.com/charliermarsh/ruff-pre-commit
    rev: v0.0.69
    hooks:
      - id: lint
        args:
          - --fix


Install module from command line

Is it possible to install a zmodule with a command line instead of editing a file then calling update?
it would be nice to have something like:
zmodule install url bla and the zimrc file be updated ?
I know people like to annotate config files it but adding that line at the end of the file automatically might  be useful.

Sorry, I know this is two years old, butI wrote this function (two variations of, actually) for myself to accomplish just that (I'm using OSX Ventura):
adding module from most recent contents of clipboard
zim_mod_pb() {gsed -i "$azmodule pbpaste" $ZDOTDIR/.zimrc &&  zimfw install}
and
adding module from string given on command line
zim_mod_cl() {gsed -i "\$azmodule $1" $ZDOTDIR/.zimrc &&  zimfw install}
I also wrote one for removing modules:
zim_rm() {rm -r -f $ZIM_HOME/modules/$1 && gsed -i "/$1\$/d" $ZDOTDIR/.zimrc}
I also ALSO made a MacOS shortcut for installing a module, if you'd be interested. It uses BetterTouchTools 'Get Selected Text' action, but could be modified to run with all native actions too.  Hopefully this finds you well enough two years late!


OIDC4VCI test 12 for Dutch profile fails with wallet Profile selection and no error displayed

Need to know if it is a server issue or a wallet issue ?

Not a server issue.. We are getting the response but data are not matching with our model...


Add math interop features to bevy_math

Objective
This is mostly useful for plugin authors when external libraries are using e.g. cgmath, vek and other popular linear algebra crates.
For example in bevy_fbx we have to duplicate glam as dependency only to add mint feature for converting fbxcel-dom PointX types into glam's FooVecX used by bevy_math.
Solution

Enable "mint" feature in bevy_math

Changelog

Add "mint" feature in bevy_math to interop between math libraries

Migration Guide
Not required

See https://github.com/HeavyRain266/bevy_fbx/pull/2

@DJMcNab There is no Cargo.lock in the repo. It's ignored.

I don't think this should be added to Bevy. Definitely not by default, and as feature are additives it doesn't help that much / is less explicit to add a feature for it in Bevy than to let others add the feature for glam themselves

Current workaround is to add glam as dependency in Cargo.toml with same version as used by bevy and then add mint feature which "patches" it instead of duplicating deps.


Replace CommonJS module.id references with the full module path

In a CommonJS module, module.id is supposed to return a value that another module would be able to use to require it. In our case, simply replace references to module.id with the full module path.

Importing this now


Add knowledge horizon functions to sensor specifications

Specifically, the ENTSO-E price sensor should be set up with
knowledge_horizon_fnc="x_days_ago_at_y_o_clock"
knowledge_horizon_par={"x": 1, "y": 12, "z": "Europe/Amsterdam"}  # gate closure of EPEX SPOT

For the other sensors, the default suffices.

@Flix6x I would some more explanation to understand this issue.


change the UI of all the calculators to match the home page

i want to change all the ui of the calculators matching the homepage. i want to work on this issue under JWOC.

@taniaban2712 yes. go for it.

@Srijita-Mandal
I would like to work on this under JWOC

@Awesomeasma You are assigned for this issue.

@Awesomeasma go for it.


[ST] Can't bump a txn

Describe the bug
The Current relayer fee is clearly not enough to have Ethereum as destination chain but the UI isn't showing the Additional required relayer fee and it can't be bumped.

Link to ticket in discord
https://discord.com/channels/454734546869551114/1225938123993645158
@oncall

Another case, this time to Linea
https://connextscan.io/tx/0x3de9e07dc8ba3ee412425d0f1dc9d528a886f4946d4ca4f2b36e88d0454cd5ce?source=search

Ticket: https://discord.com/channels/454734546869551114/1225945937567023124

Another case, again Polygon to Ethereum
https://connextscan.io/tx/0x296bf4c71bb7092ae4e4f6bc2a9ecba61ae6ccd33fc4b8538d2ff65d700d652a

Ticket: https://discord.com/channels/454734546869551114/1225949024910049280


Using cppflow with TFSecured

The current project I'm working on needs the ability for me to encrypt frozen .pb files and decrypt back within the app to run for inference . I came across this small library called TFSecured which allows exactly that: https://github.com/dneprDroid/TFSecured
Does anyone know how to go about integrating the TFSecured library to work with Cppflow?

Moving this to a discussion because there is no plan into integrating this. If anyone can help, it can post the answer in the discussion.


Use stable sort when ordering files by timestamp

The unstable sort here means different systems may produce a different run order when two or more migrations have matching timestamps:
https://github.com/salsita/node-pg-migrate/blob/c2e3cacd507e3898c94fd67b4ad32f2ae9460041/src/runner.ts#L49

hi @hempels @Shinigami92! thanks for creating an issue.
Could you say what is the use case to have several migrations with same timestamp?
From my point of view - the order of migrations is meant to be based on a number - timestamp. The developer needs to be careful by creating a right timestamp but that's actually in usual circumstances much easier then checking the alphabetical order of the names for example. So at the moment, I don't really see the problem here. We assume the migrations have different timestamps and it's quite hard to create unintentionally two migrations with same timestamp.

Closing but feel free to reply and reopen. Thanks!

I'm unsure of the circumstances that cause it. We have multiple developers working in a single project with hundreds of migrations, merging in multiple branches, and it isn't possible to monitor the naming of each one to make sure the timestamp portion is unique. Fixing them once they're already committed wrong is a nightmare.
Providing a stable sort here would be a relatively easy way to eliminate negative impacts of inadvertent overlap. Certainly much easier than checking the file names of every migration in every commit.

Beside that, my fix is fairly easy to resolve this issue

Closing but feel free to reply and reopen. Thanks!

@littlewhywhat What do you mean by "reopen"? You want a new issue that goes back over the same ground?
The PR (#818) created by @Shinigami92 is simple, unlikely to introduce any bugs, and won't have any effect for the case where there isn't a problem. It will, however, effortlessly resolve the issue for cases where there currently is a problem.

Honestly I'd be more inclined to fail fast in these situations. As soon as we find two migrations with the same timestamp we should fail - thus avoid the situation in the first place. Trying to work around an erroneous state isn't really a solution to the problem.
I understand your current pain @hempels, though. A general problem with this library is that once the migrations are applied, there's no way back, unless you dare to fiddle with the DB directly. Also establishing a stable order right now might not fully solve your current issues since that order might not reflect how the previous migrations were already applied.
I suggest you do you homework to solve the current problems and we'll introduce the check to avoid them in the future. How would you feel about that?

Frankly, I'm finding the resistance to this change very frustrating. It has no impact for anyone not experiencing the issue and for those that are, it solves the problem absolutely and without any ambiguity. There is no reason to fail in these cases. So long as the order of migrations is deterministic, the timestamp of any given migration is immaterial. Even if all of the migrations have the same timestamp and only vary by suffix, it would still be fine so long as their order is stable.

I suggested to fail fast before we apply anything to the DB thus avoiding this:

Fixing them once they're already committed incorrectly is a nightmare because people have already applied them.

Anyway neither I nor @littlewhywhat see any technical problem with the PR. What bothers us is, that this library is meant to be used with unique time-stamps - that's why the create command is there and that's why you have the problems. For that reason I'd rather communicate this explicitly (hence my suggestion for uniqueness check) than soften the rules and basically allow a flow that is not according to the initial design.
If we apply the fix, then we could easily say that there's no need for any timestamp anymore... your developers could basically start doing: 11111111-migration-A, 11111111-migration-B, 11111111-migration-C etc... but then what's the point of the timestamp? I'm not saying that the timestamp is the greatest solution to the problem - there might be better ones. However this is a fundamental change to the concept of the how the migrations are supposed to be handled.
That all said, I guess we'll merge the PR silently to keep you happy. But in the next major release, I'd love to see the duplicity check so that no other new user gets into your shoes. We will introduce a backwards compatibility flag though... something like --ignore-duplicate-timestamps.

I've thought through your argument more and in theory I am content with the idea of failing immediately if a duplicate timestamp is detected. That would fix the problem and would shift the onus for resolving it to the person who created the problem.
The practical issue is that would introduce a breaking change given our existing migrations where some of those duplicates are hundreds of migrations up the line. We would be forced to rename any old migrations with duplicate timestamps and deal with the renaming challenges, which are very awkward. Adding a compatibility flag helps, but then we still need the stable sort PR applied.

That would fix the problem and would shift the onus for resolving it to the person who created the problem.

Exactly my point. I'm happy you agree.

would introduce a breaking change

We could possibly introduce the change in not-so-breaking way... I assume we're always fetching the already applied migrations from the DB, are we @littlewhywhat? In that case we could strip those from the full list and do the dupe test only on the non-applied ones (maybe including the latest applied one). Thus we would prevent the problem with any future migration, but still allow the already applied cripples to pass.

stable sort PR applied

Let's apply it, since the new major version will take some time anyway. Agreed @littlewhywhat ?

Let's apply it

ok i will reopen the PR and take a look, thanks!

I assume we're always fetching the already applied migrations from the DB

we load all migrations files and fetch all migration records to check the order each time if that's what you mean.

@hempels FYI even with the PR applied, if the current migrations table (on your master branch, I guess) doesn't have migrations sorted alphabetically then you would need to fix it as our check gonna fail with error that some migration A precedes migration B. So it may not solve your issue so effortlessly.

@hempels FYI 6.1.0 is now released with the fix for this issue https://github.com/salsita/node-pg-migrate/releases/tag/v6.1.0


Projected balance date choice

We already display on the account tile, along with the current balance, the projected balance.
But currently the user is not able to choose a future date.
Features needed:

Be able to choose a future date (for each account)
Use that projected_date for balances API calls

The projected balance amount will then be automatically updated on the tile.

Done in PR #34


docs: Improve docstrings for all statements

Codecov Report

Merging #14 (2b1de38) into dev (4169911) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

:exclamation: Current head 2b1de38 differs from pull request most recent head bc254bb. Consider uploading reports for the commit bc254bb to get more accurate results

@@            Coverage Diff             @@
##              dev      #14      +/-   ##
==========================================
- Coverage   85.68%   85.66%   -0.02%
==========================================
  Files          17       17
  Lines         957      956       -1
  Branches      200      200
==========================================
- Hits          820      819       -1
  Misses         93       93
  Partials       44       44

Impacted Files
Coverage Δ

deirokay/parser/parser.py
81.42% <ø> (ø)

deirokay/profiler.py
81.25% <ø> (ø)

deirokay/statements/base_statement.py
83.33% <ø> (ø)

deirokay/statements/contain.py
93.75% <ø> (ø)

deirokay/statements/not_null.py
80.64% <ø> (ø)

deirokay/statements/row_count.py
96.87% <ø> (ø)

deirokay/statements/unique.py
100.00% <ø> (ø)

deirokay/statements/column_expression.py
87.32% <100.00%> (-0.18%)
:arrow_down:

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 4169911...bc254bb. Read the comment docs.


Fix warnings reported by ID3D11InfoQueue

In our engine we can't use ID3D11InfoQueue and RenderDoc both enabled in our engine, because there are some errors in how RenderDoc uses d3d11. These changes fix them

This change is fine but can you explain what you mean that you couldn't use RenderDoc together with ID3D11InfoQueue becauseof this? RenderDoc blocks application access to the API validation for that kind of reason.

Sorry, it is not ID3D11InfoQueue, it is IDXGIInfoQueue

OK I didn't realise that interface existed, I'll need to wrap & block it to ensure things work correctly. In the meantime I'm happy to merge this PR once the CI is green - it looks like the commit message formatting is off.


May images resized

They were around 10 Mb each

haha yeah thanks — I saw the same, included in a bunch of changes in #969 — so going to close this one out, thanks Victor!


Update ResourceState combine

Codecov Report

Merging #207 (d877161) into main (0e36738) will decrease coverage by 0.18%.
The diff coverage is 27.27%.

:exclamation: Current head d877161 differs from pull request most recent head 1e87956. Consider uploading reports for the commit 1e87956 to get more accurate results

@@            Coverage Diff             @@
##             main     #207      +/-   ##
==========================================
- Coverage   75.11%   74.93%   -0.19%
==========================================
  Files          62       63       +1
  Lines        2885     2904      +19
  Branches      468      465       -3
==========================================
+ Hits         2167     2176       +9
- Misses        459      469      +10
  Partials      259      259

Impacted Files
Coverage Δ

...exvanyo/composelife/resourcestate/ResourceState.kt
29.16% <0.00%> (-7.68%)
:arrow_down:

...yo/composelife/resourcestate/CompositeException.kt
100.00% <100.00%> (ø)

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 f2f84a9...1e87956. Read the comment docs.


Error response from daemon: No such container

When gale and ghx imports different dagger version it fails with following error.
failed to get exit code: input:1: container.from Unavailable: connection error: desc = "error reading server preface: command [docker exec -i dagger-engine-e7ae55a590c74d2e buildctl dial-stdio] has exited with exit status 1, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=Error response from daemon: No such container: dagger-engine-e7ae55a590c74d2e\n"

We should ensure they're always using the same version.  Maybe we should consider mono repo again.

As the ghx repo has recently depreciated, this issue is now less frequent, so we could close it.


Timezone-setting missing

Hi =) I've discovered that the container is not able to set a Timezone...So you can't plan Backups properly...a TZ-variable would be really nice (as this would also work in swarm) =)

Have a look at the base image https://github.com/tiredofit/docker-alpine/blob/3.11/README.md environment variables for information on setting timezone.

Oh cool :-) that's perfect thank you very much :-))) sorry I've overlooked that...


Feature Request: Support FFI

Both bun and Deno have ffi. As seen on https://bun.sh/ SQLite benchmarks, the ffis put up impressive benchmarks for sqlite. Therefore it would be interesting to support their dialects.
I could take a crack at it, although I can't get to it for a while, and so wanted to gauge interest here for implementing it.

So, according to my understanding, the way to implement it is just execute all SQL statements can be performed using FFI, just like kysely-sqlite-worker?

kysely-sqlite-worker code seems adaptable yes. Just import the FFI Database package and run the statements on it. And worker threads if they're useful here. older bun example without worker - https://github.com/dylanblokhuis/kysely-bun-sqlite/blob/master/src/driver.ts

Looks like Bun only has web workers for now. Worker threads will hit before they go 1.0 on Sept 7, so any day now.

Worker threads are available in bun 0.7.2

bun worker dialect have produced, but only using worker threads, currently no ffi

according to https://github.com/denodrivers/sqlite3#benchmark, bun:ffi is slower than bun:sqlite

Good note! I thought bun:sqlite was FFI originally as its similar in performance to Deno FFI but it is not.

a bun worker dialect is published


fix(mdx-loader): allow spaces before mdx-code-block info string

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[x] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation
I have a website using Quarto and Docusaurus, and after updating Docusaurus from v2 to v3, I noticed that mdx-code-block was broken.
The issue is here: quarto-dev/quarto-cli#8333
Pandoc (used internally by Quarto CLI) adds spaces between backticks and info strings when outputting Markdown files.
e.g.
```foo
bar
```

to
``` foo
bar
```

The current Docusaurus does not allow this space, which would prevent it from rendering as intended.
In v2, spaces were allowed. This difference doesn't seem to be what was intended, so I opened this PR thinking I might be able to fix it here.
This is just a simple regular expression modification.
Test Plan
Test links
Related issues/PRs

Thanks
Yes that seems to be a reasonable thing to support considering Markdown/MDX usually allow passing code block languages with spaces.
This regression only appeared because the way we have to handle mdx-code-block items in Docusaurus/MDX v3 is significantly different from before, and not super clean unfortunately. We did our best to keep this feature working but it doesn't play super well with MDX v3.

Thanks for merging!


Cannot enable knative

I can't enable knative.
It waits for istio to be ready but istio doesn't seem to be ready.
I tried to disable and enable istio again but it gives another error.
(kubeflow) user01@user-X299-WU8:/data/mhkwon/kubeflow/istio-1.8.4$ microk8s enable knative
Enabling Knative
Addon istio is already enabled.
Waiting for Istio to be ready
......................................................................................^C
Aborted!
(kubeflow) user01@user-X299-WU8:/data/mhkwon/kubeflow/istio-1.8.4$ microk8s status
microk8s is running
high-availability: no
  datastore master nodes: <IP_ADDRESS>:19001
  datastore standby nodes: none
addons:
  enabled:
    dashboard            # The Kubernetes dashboard
    dns                  # CoreDNS
    gpu                  # Automatic enablement of Nvidia CUDA
    ha-cluster           # Configure high availability on the current node
    ingress              # Ingress controller for external access
    istio                # Core Istio service mesh services
    metallb              # Loadbalancer for your Kubernetes cluster
    metrics-server       # K8s Metrics Server for API access to service metrics
    storage              # Storage class; allocates storage from host directory
  disabled:
    ambassador           # Ambassador API Gateway and Ingress
    cilium               # SDN, fast with full network policy
    fluentd              # Elasticsearch-Fluentd-Kibana logging and monitoring
    helm                 # Helm 2 - the package manager for Kubernetes
    helm3                # Helm 3 - Kubernetes package manager
    host-access          # Allow Pods connecting to Host services smoothly
    jaeger               # Kubernetes Jaeger operator with its simple config
    keda                 # Kubernetes-based Event Driven Autoscaling
    knative              # The Knative framework on Kubernetes.
    kubeflow             # Kubeflow for easy ML deployments
    linkerd              # Linkerd is a service mesh for Kubernetes and other frameworks
    multus               # Multus CNI enables attaching multiple network interfaces to pods
    portainer            # Portainer UI for your Kubernetes cluster
    prometheus           # Prometheus operator for monitoring and logging
    rbac                 # Role-Based Access Control for authorisation
    registry             # Private image registry exposed on localhost:32000
    traefik              # traefik Ingress controller for external access
(kubeflow) user01@user-X299-WU8:/data/mhkwon/kubeflow/istio-1.8.4$ microk8s disable istio
Disabling Istio
Error from server (NotFound): namespaces "istio-system" not found
(kubeflow) user01@user-X299-WU8:/data/mhkwon/kubeflow/istio-1.8.4$ microk8s enable istio
Addon istio is already enabled.

This is the tarball.
inspection-report-20210323_204727.tar.gz
I'm facing so many bugs on microk8s...

Can microk8s kubectl get pods -A -o wide

I'm sorry to hear that you are facing issues with MicroK8s.  With regards with knative and istio, i think it has something to do with kubeflow's istio components.  The way the enable works, is it checks for certain pods to be present.  Kubeflow includes istio components.
This is something that needs to be fixed.  As of the moment you can try to install knative from upstream. 🙁

Thx for reply.
I tried to install istio with the yaml below as a prerequisite for knative, introduced by knative.
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  values:
    global:
      proxy:
        autoInject: disabled
      useMCP: false
      # The third-party-jwt is not enabled on all k8s.
      # See: https://istio.io/docs/ops/best-practices/security/#configure-third-party-service-account-tokens
      jwtPolicy: first-party-jwt

  addonComponents:
    pilot:
      enabled: true

  components:
    ingressGateways:
      - name: istio-ingressgateway
        enabled: true

And it says
This will install the Istio default profile with ["Istio core" "Istiod" "Ingress gateways"] components into the cluster. Proceed? (y/N) y
✔ Istio core installed
✘ Istiod encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the condition
Deployment/istio-system/istiod
✘ Ingress gateways encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the conditiontiod
Deployment/istio-system/istio-ingressgateway
✘ Addons encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the condition
Deployment/istio-system/istiod
- Pruning removed resources                                                                                Error: failed to install manifests: errors occurred during operation

Don't know much about istio and knative, do you mind sharing microk8s kubectl get pods -A -o wide

This is the output.
(base) user01@user-X299-WU8:/var/snap/microk8s/current/args$ microk8s kubectl get pods -A -o wide
NAMESPACE         NAME                                           READY   STATUS             RESTARTS   AGE   IP             NODE            NOMINATED NODE   READINESS GATES
default           iris-training-4925-2sv2p                       0/1     Completed          0          22h   <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kube-system       nvidia-device-plugin-daemonset-fg2rw           0/1     CrashLoopBackOff   153        8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          istio-pilot-57b4fc6d5c-8sq6h                   0/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          metadata-api-7b8b588ccf-mqk9q                  0/1     Running            31         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          metadata-db-0                                  0/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          pipelines-db-0                                 0/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
ingress           nginx-ingress-microk8s-controller-7wmq7        0/1     Running            11         11d   <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          argo-ui-79997765b6-gq2c7                       0/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kube-system       coredns-86f78bb79c-pj9tk                       0/1     Running            10         11d   <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          katib-db-0                                     0/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
admin             private-reg                                    0/1     Terminating        231        47h   <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          pipelines-api-operator-0                       1/1     Running            11         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          katib-controller-operator-0                    1/1     Running            11         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          kubeflow-dashboard-operator-0                  1/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          pipelines-visualization-54757695b5-slrhs       1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          argo-controller-operator-0                     1/1     Running            11         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          seldon-core-operator-0                         1/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          pipelines-viewer-operator-0                    1/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          metadata-api-operator-0                        1/1     Running            11         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          istio-pilot-operator-0                         1/1     Running            11         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          oidc-gatekeeper-operator-0                     1/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          metadata-envoy-696c6bbdcf-klzr7                1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          minio-operator-0                               1/1     Running            11         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          admission-webhook-7998c89c96-4wgb7             1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          katib-db-operator-0                            1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          jupyter-controller-operator-0                  1/1     Running            11         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          jupyter-web-operator-0                         1/1     Running            11         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
controller-uk8s   controller-0                                   2/2     Running            22         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kube-system       hostpath-provisioner-5c65fbdb4f-bd6sp          1/1     Running            12         11d   <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          argo-ui-operator-0                             1/1     Running            12         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          pytorch-operator-8449b4ff65-rt82k              1/1     Running            11         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          jupyter-controller-7d4c954b9b-pv4km            1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          metadata-ui-87c584c46-fdbfd                    2/2     Running            20         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          pipelines-api-c89969c98-wxwth                  2/2     Running            42         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          istio-ingressgateway-operator-0                1/1     Running            12         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          pipelines-ui-operator-0                        1/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          katib-manager-5fd7bf6c56-47qvf                 1/1     Running            12         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          katib-ui-7b9db945df-t8gdx                      1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          istio-ingressgateway-7799df4bb4-26vc4          1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          kubeflow-dashboard-64dd996b5-2cdjb             2/2     Running            23         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          dex-auth-86796c8bf4-62vfq                      2/2     Running            42         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          pipelines-persistence-operator-0               1/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kube-system       calico-kube-controllers-847c8c99d-bd5g4        1/1     Running            11         12d   <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          metadata-db-operator-0                         1/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
controller-uk8s   modeloperator-5d9757f556-vvdn5                 1/1     Running            11         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kube-system       metrics-server-8bbfb4bdb-ds9qh                 1/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          minio-0                                        1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          dex-auth-operator-0                            1/1     Running            12         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          pipelines-visualization-operator-0             1/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          pipelines-viewer-78f7dcb544-cf4bv              1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          jupyter-web-6987858ff5-7v9bf                   1/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          admission-webhook-operator-0                   1/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          katib-manager-operator-0                       1/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          kubeflow-profiles-694d9f9495-wql9b             2/2     Running            20         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          metadata-ui-operator-0                         1/1     Running            11         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          kubeflow-profiles-operator-0                   1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          katib-ui-operator-0                            1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          seldon-core-656c7f7f4f-hkpwj                   1/1     Running            12         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          metadata-grpc-65484b66bc-jnks6                 1/1     Running            17         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          modeloperator-85dd445b8c-f2trq                 1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          metadata-envoy-operator-0                      1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          pipelines-persistence-5b7f97d785-v6w87         1/1     Running            14         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          pipelines-scheduledworkflow-5885f8b7b9-25mxd   1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          oidc-gatekeeper-6b8847b678-fzm2f               2/2     Running            20         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          tf-job-operator-operator-0                     1/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          katib-controller-78fbb9dc9d-4zpsg              1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          argo-controller-595dfb97b8-bh89q               1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          metadata-grpc-operator-0                       1/1     Running            11         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          metacontroller-74b758df8-7n6hb                 1/1     Running            10         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>
metallb-system    controller-559b68bfd8-2z4nb                    1/1     Running            11         11d   <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kubeflow          pytorch-operator-operator-0                    1/1     Running            11         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          pipelines-ui-5b85f985d-ngdzx                   1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kube-system       calico-node-89dbd                              1/1     Running            16         12d   <IP_ADDRESS>    user-x299-wu8   <none>           <none>
metallb-system    speaker-gfnlx                                  1/1     Running            16         11d   <IP_ADDRESS>    user-x299-wu8   <none>           <none>
kube-system       dashboard-metrics-scraper-6c4568dc68-zbdhw     1/1     Running            12         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          metacontroller-operator-0                      1/1     Running            11         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          tf-job-operator-79865dfbf4-wd5kn               1/1     Running            12         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          pipelines-db-operator-0                        1/1     Running            10         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kubeflow          pipelines-scheduledworkflow-operator-0         1/1     Running            11         8d    <IP_ADDRESS>   user-x299-wu8   <none>           <none>
kube-system       kubernetes-dashboard-7ffd448895-nhx8q          1/1     Running            12         8d    <IP_ADDRESS>    user-x299-wu8   <none>           <none>

Many of your pods aren't running.  Most importantly the coredns.
Need to see what is wrong with coredns.  What do you see when you do microk8s kubectl describe po coredns-86f78bb79c-pj9tk -n kube-system.  Also the logs of this pod.

What I see is
Name:                 coredns-86f78bb79c-pj9tk
Namespace:            kube-system
Priority:<PHONE_NUMBER>
Priority Class Name:  system-cluster-critical
Node:                 user-x299-wu8/<IP_ADDRESS>
Start Time:           Fri, 12 Mar 2021 15:19:29 +0900
Labels:               k8s-app=kube-dns
                      pod-template-hash=86f78bb79c
Annotations:          cni.projectcalico.org/podIP: <IP_ADDRESS>/32
                      cni.projectcalico.org/podIPs: <IP_ADDRESS>/32
                      scheduler.alpha.kubernetes.io/critical-pod:
Status:               Running
IP:                   <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/coredns-86f78bb79c
Containers:
  coredns:
    Container ID:  containerd://914b58a114cd5a746dd04bc2e683b97f5397a7af121590bd968151afd87773a8
    Image:         coredns/coredns:1.6.6
    Image ID:      docker.io/coredns/coredns@sha256:41bee6992c2ed0f4628fcef75751048927bcd6b1cee89c79f6acb63ca5474d5a
    Ports:         53/UDP, 53/TCP, 9153/TCP
    Host Ports:    0/UDP, 0/TCP, 0/TCP
    Args:
      -conf
      /etc/coredns/Corefile
    State:          Running
      Started:      Tue, 23 Mar 2021 23:27:59 +0900
    Last State:     Terminated
      Reason:       Unknown
      Exit Code:    255
      Started:      Tue, 23 Mar 2021 14:32:29 +0900
      Finished:     Tue, 23 Mar 2021 23:05:54 +0900
    Ready:          False
    Restart Count:  10
    Limits:
      memory:  170Mi
    Requests:
      cpu:        100m
      memory:     70Mi
    Liveness:     http-get http://:8080/health delay=60s timeout=5s period=10s #success=1 #failure=5
    Readiness:    http-get http://:8181/ready delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:  <none>
    Mounts:
      /etc/coredns from config-volume (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from coredns-token-2wd6j (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      coredns
    Optional:  false
  coredns-token-2wd6j:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  coredns-token-2wd6j
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     CriticalAddonsOnly op=Exists
                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:          <none>

This pod doesn't seem ready at all.  Can you upload another inspect tarball?

Here it is.
inspection-report-20210324_170107.tar.gz

I can't find the reason why coredns doesn't want to start.  Have you restarted microk8s?

In the Api server logs I also see this:
3월 24 16:09:26 user-X299-WU8 microk8s.daemon-apiserver[28351]: W0324 16:09:26.965240   28351 dispatcher.go:170] Failed calling webhook, failing open admission.juju.is: failed calling webhook "admission.juju.is": Post "https://modeloperator.kubeflow.svc:17071/k8s/admission/fd8e2ea1-14ce-4661-878b-2db12f81b868?timeout=30s": dial tcp <IP_ADDRESS>:17071: connect: connection refused

This reminds me of issue: https://github.com/ubuntu/microk8s/issues/1520 but I am not sure about the connection.

@knkski any idea what that might be?

@ktsakalozos coredns isn't running, that could be the reason why.
The node is also in NotReady state.  But calico is reported to be up.

@balchua
Changed machine name with the --hostname-override argument.
And restarted microk8s.
inspection-report-20210325_113711.tar.gz

Hi is finance-ai-test network  resolvable by the node?


raw bson

sometimes it's not possible (https://jira.mongodb.org/browse/SERVER-267) or practical (database load) to project only relevant fields (or if you want to just copy objects between servers). deserialization of bson is then the performance bottleneck.
it would be great if Cursor could yield raw_bson with behaviour like in c++ driver.
for my data, it's <10seconds vs 3minutes.

As a step toward this I've created #328, which removes all reference to the Bson type from the wire_protocol, without affecting any public interfaces outside that module.  A next step might involve creating a way to feed raw bson bytes to and from methods on Collections directly.  I'll give some thought as to what that should look like and put together a proposal or a PR for further discussion.

Hello everyone! We've just released an alpha of an official MongoDB Rust driver; you can read about it here! Because of this, we won't be updating this driver anymore, and the repository will be made read-only as soon as I get finished posting these messages. Thanks for using this driver, and we hope you try out the new one!

Apologies, the blog post link is this: https://www.mongodb.com/blog/post/announcing-the-official-mongodb-rust-driver


Sampler ycbcr conversion

- Added `SamplerYcbcrConversion`, and the ability to attach it to a sampler or image view.

Depends on #1806.
A sampler YCbCr conversion is a Vulkan object that's used for sampling video frames. It's a bit more of a niche feature, and I myself have no use case for it, but it's just one more thing that brings Vulkano closer to being complete. It's also needed for video encoding/decoding, a still-experimental Vulkan feature that was requested in #1756. I don't know if it's wise to implement an experimental feature, but if we do, then the requirements are now done.

@Rua After the #1806 merge, there are merging conflicts.

@Rua Merged :+1:


Avoid NoSuchElementException in ManualAESDecryptor.

An exception was possible if System.in was redirected to read an empty file.

@rgrig Thanks a lot for your help.

 Avoid NoSuchElementException in ManualAESDecrypto light-4j master

 Avoid NoSuchElementException in ManualAESDecrypto light-4j 1.6.x


Using Artoo with Google Puppeteer

How can I use Artoo with Puppeteer. I tried npm install artoo-js , it did not work. should I tried injecting the following  scripts as well \node_modules\artoo-js\build\artoo.concat.js  and \node_modules\artoo-js\build\artoo.chrome.js     but nothing

Yes, this is not as straightforward. Check how I used to inject artoo with PhantomJS here.

This should be more or less the same idea with puppeteer I think.

@Yomguithereal  I tried using page.injectFile(filePath) from puppeteer and using the phantom js code.  No luck. However I was able to successfully inject query using page.addScriptTag(url).  Not sure  how many others are trying to use it with Puppeteer, but I would find an example really useful.

Pupeteer is quite recent so I am not sure anyone has tried yet. Can you check if injecting artoo phantom's code throw something? I think artoo checks if it is run in a phantomjs scope which it's not in this case. You'll need to edit the code in artoo.phantom

This worked: first download wget https://medialab.github.io/artoo/public/dist/artoo-latest.min.js
then inject it in code like so:
const puppeteer = require('puppeteer');
(async() => {
    const url = 'https://news.ycombinator.com/';
    const browser = await puppeteer.launch();
    const page = await browser.newPage();
    // Go to URL and wait for page to load
    await page.goto(url, {waitUntil: 'networkidle'});
    // Inject Artoo into page's JS context
    await page.injectFile('artoo-latest.min.js');
    // Sleeping 2s to let Artoo initialize (I don't have a more elegant solution right now)
    await new Promise(res => setTimeout(res, 2000))
    // Use Artoo from page's JS context
    const result = await page.evaluate(() => {
        return artoo.scrape('td.title:nth-child(3)', {
            title: {sel: 'a'},
            url: {sel: 'a', attr: 'href'}
        });
    });
    console.log(`Result has ${result.length} items, first one is:`, result[0]);
    browser.close();
})();


Walton SOM

Walton cannot be used as a name on its own. There are other Waltons in SOM. Unfortunately places like Walton in Gordano will be linked to it.
Please change the name to Walton (Street). Please remove all search records attached to Walton and let me know when it is done. I will get the vld revalidation amended to cope with re-linking.
Geoff

Done


[CLOSED] libStorage Refactor (DADD)

 Issue by akutz
Tuesday Mar 22, 2016 at 14:23 GMT
Originally opened as https://github.com/emccode/libstorage/pull/9

This patch is the basis for libStorage moving forward -- providing a framework more consistent with an evolutionary take on the Docker HTTP platform. Features include:

Contextual logging
Centralized types
Generated server names
Executor generation based on enforced Go interface types
Librarification of the REX-Ray CLI
Using make run|run-debug|run-tls|run-tls-debug to start a server directly from source, from the command line.

akutz included the following code: https://github.com/emccode/libstorage/pull/9/commits

 Comment by codecov-io
Tuesday Mar 22, 2016 at 14:27 GMT

Current coverage is 36.44%

Branch #9 has no coverage reports uploaded yet.

No diff could be generated. No reports for master found.

Powered by Codecov. Updated on successful CI builds.

 Comment by clintonskitson
Tuesday Mar 22, 2016 at 16:19 GMT

Make sure to run a make deps before executing the tests.


Industry user can't access User Access Management tile [8]

Describe the Bug:
When logged in as bc-cas-dev, the dashboard looks like this:
If you click the user tile you get this error:
Logs:

Probability (how likely the bug is to happen, scored from 1-5): 4
(For example, probability of 5 is something like "it happens to all users every time they log in."
Probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Effect (how bad the bug is when it does happen, scored from 1-5):4
(For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected."
Effect of 1 is "It makes some styling look a little bit weird.")
Steps to reproduce the behaviour:
Screenshots:
Additional information:

OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]
Additional context

This will be fixed by #28


Shows Doppler Phase For Items

Shows doppler phase (if applicable) beside the paint seed

Closes #42

Added missing phases


Cannot save file

Hello! I'm new to docker and I don't know if there is something that I'm missing
I downloaded your image and monodevelops works, the only thing is that it doesn't save my projects. When I close it and open again it doesn't have them.
I'm running sudo docker run -v /tmp:/tmp zachdeibert/monodevelop $DISPLAY $USER
This code opens monodevelop but also shows chown: cannot access '/home/leo/*': No such file or directory
Any help?

The filesystem is completely different inside the container than outside the container.  This is why it seems not to save your projects (new container means entirely new filesystem).  To change this, you can use the -v option (like you already have with /tmp since the files needed to connect to the desktop manager are in /tmp).  So for example, if you want /home/leo/projects to save to your local machine instead of in the container, you'd run sudo docker run -v /tmp:/tmp -v /home/leo/projects:/home/leo/projects zachdeibert/monodevelop $DISPLAY $USER.  Let me know if that fixes your problem.

Yes! It works perfectly. Now I can modify my files
Thanks a lot!


⚠ Bofrost.de has degraded performance

In 42d438f, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1157 ms

Resolved: Bofrost.de performance has improved in fc8320e.


Fix search item link

The link to the found items on the search screen doesn't work at the moment.

Resolved


The Application was Forced to Exit

Dear GrowServer Developers,
Problems
I have problems doing connect. And I have the details and What happened.
Details

Growtopia: Version 4.05
Nodejs: Version 20.3.1

What Happen
I have done everything that was instructed. And I set the host on the right IP.
When I do connect and in the Updating Item log, I exit the application by itself.
{
  parsed: {
    tankIDName: 'admin',
    tankIDPass: 'admin',
    requestedName: 'BraveTiny',
    f: '1',
    protocol: '175',
    game_version: '4.01',
    fz: '16474664',
    lmode: '0',
    cbits: '1024',
    player_age: '24',
    GDPR: '1',
    category: '_12',
    totalPlaytime: '0',
    hash2: '1318604448',
    meta: 'lolwhat',
    fhash: '-716928004',
    rid: '01DB992F19676EC6019AF77222F6FF98',
    platformID: '0,1,1',
    deviceVersion: '0',
    country: 'us',
    hash: '403377526',
    mac: 'e4:fd:45:ab:a5:63',
    wk: '3E596CE6CB01F2CB5524C417D24337C4',
    zf: '-1434588773'
  },
  dataType: 2
}
{ parsed: { action: 'refresh_item_data' }, dataType: 2 }
Unknown tank TankPacket {
  data: {
    packetType: 4,
    type: 24,
    punchID: 0,
    buildRange: 0,
    punchRange: 0,
    netID: -1,
    targetNetID: 0,
    state: 0,
    info:<PHONE_NUMBER>,
    xPos: 0,
    yPos: 0,
    xSpeed: 0,
    ySpeed: 0,
    xPunch: 0,
    yPunch: 0
  }
}

What do I have to do

Is there a specific version of Growtopia ?
Does the server have to be placed on a Virtual Host ?

It seems that you're using an older version of Growtopia.
The problem come from items.dat, since the source are using v4.31 (Latest v4.36) Growtopia items.dat.
Maybe try changing the items.dat with your growtopia version or update the growtopia to newer version

Yeah, It works.
Thank's @JadlionHD


[WIP] Add metrics

To finish metrics we need:

[ ] Add an interval for the graph
[ ] Add metric points through the API
[ ] Display metric points on graph

Rebased to fix issues with Composer.

@GrahamCampbell don't kill me, I've been messing around just getting it to work for now.
With my most recent changes we get:

Over to you @joecohens to check I've not missed anything and then we should merge.

All done. Merge away :)


Change date event

How can i modify the change date event for fullcalendar in vuejs2

You can use the [Config prop] (https://github.com/CroudTech/vue-fullcalendar#custom-config) to modify events


Split out success and error APIs

In order to better support future development, it might be useful to split out success and error callbacks (e.g. like Retrofit)

Note: I've been working on this in the background, and it seems to work very nicely. It adds an extra parameter, but that's worth it. Also works very nicely with Templated error listeners and stringdef'd results.

Pushed to Develop - this is a required step before Queues or Rx can be written


[NETBEANS-126] Re-instate browser icons

Reinstates those browser icons that were originally removed from Oracle's donation to Apache. See NETBEANS-126 for more information.
IANAL, but I assume that we are allowed to distribute these icons as part of Apache NetBeans, but that Oracle didn't want them in the donation bundle as this is not their trademarks. Please validate assumption before merging.

I'd suggest you start a new thread in the Apache NetBeans dev mailing list with this question, starting with [mentors] in the subject line to ensure they're notified of this question.

It would be great, if we can have new icons, modern, flat for example and free to use. As you can see, the icons are different, different opera icon, different chrome icon, so a set of icons which is the same is needed here anyway.

@Chris2011. The browser icons are about 0.5% of all icons used in the Platform / IDE. Wouldn't it look strange if we replaced only those few icons with a design different than all the other 99.5%  ?

But why not starting there first and do it incremental further? Or starting to make them looks both the same, as you can see both opera and both chrome icons are diffferent. We need consistency and I think we can start there. Only IMHO.

@geertjanw.
Tracked in LEGAL-343. If this is wrong procedure, I'll withdraw LEGAL-343. I was just assuming that mentors would guide us to this process anyway (I would certainly do that as a mentor)

Which question are we following here?
If it is the copyright of the icons, there are several free icon themes out there, that have free enough licenses and hold the icon, there is also font-awesome, that holds glyphs with the shapes. I would feel better with sensible licensed icons.
If it is trademark then I would not advertise with the icons, but using in the program to represent the application they belong to sounds sensible.

How they are used:

For css.editor I don't think the icons add much value. See NETBEANS-126 for how they are actually used.
For "web.browser.api I'm not aware of how they are actually used.

The license of the art-work
I've taken the icons in the PR from the NetBeans Hg. Thus, I assume that they already have a proper 'free' license. If that assumption falls short then we'll have to review each and every icon in NetBeans. Ouch!
I wonder if the NetBeans core has (historically) had any policy wrt to icons and other art work?

For css.editor I don't think the icons add much value. See NETBEANS-126 for how they are actually used.

What do you mean with much value? They are used to show you the browser compatibility of css features.

For "web.browser.api I'm not aware of how they are actually used.

I think it is for the run/debug session, the panel, where you can choose your browser to start from NetBeans, when you run an application. Only guessing.

For css.editor I don't think the icons add much value. See NETBEANS-126 for how they are actually used.

What do you mean with much value? They are used to show you the browser compatibility of css feature.

I just meant that the same can easily be conveyed without using the actual logo - if usage of the logo turns out to be a legal problem.

PR289 is an alternative to this pull request which I think is what should be done for now.
However, I'll leave this PR intact so that it can be activated later if need be.


No prompts inputted into ExtendSAM

Thank you very much for your meaningful work. I have briefly debugged the training of semantic segmentation and found that no prompt inputs were sent to ExtendSAM. My understanding is that it may be appropriate to use 32x32 grid points as a prompt and classify the mask. Or perhaps I have misunderstood the purpose of your prompt inputs, and I'm curious about why you used them.

Yeah, you are very patient, the default SAM uses 32*32 points as prompt, and the FA is designed to input prompt through PromptEncoderAdapter, But I did not design it yet. So now Extend-SAM’s prompt input is ‘None’, don’t worry, I will design PromptEncoderAdapter later.
Now the performance of fine-tuned Extend-SAM on VOC has been acceptable. After adding the prompt part will be better, please wait a moment.
If you have any idea to design the PromptEncoderAdapter, please submit PR to me, thanks for your attention.

Why Now the performance of fine-tuned Extend-SAM on VOC has been acceptable?
To the best of my knowledge, No prompts = No outputs.  In this version of FA, the output of mask tokens are useless. Am I right?

FA support customized MaskDecoderAdapter, and the SemSAM class is an extend-SAM model whose MaskDecoderHead was modified. When the prompt is None, it will output an output, the shape of the output is the standard shape for the semantic segmentation task. The design of MaskDecoderHead in SemSAM is for class-ware mask predictions. The design of   SemSAM may not be very suitable, it is an example for users to design their own Extend-SAM models. Scientific research requires a lot of experimentation and thinking, Scientific research requires a lot of experiments and thinking, we are more inclined to provide a tool to help realize their ideas.
For the prompt part, I will seriously consider your suggestion and try to design an easy-to-use prompt interface.
by the way, if you have a good idea, you are welcome to submit PR to this repository.

Thanks for your kind reply. I think the MaskDecoder in SemSAM is not prompt-driven anymore. The finetune processing only make a new task-specific head. This paper (How to Efficiently Adapt Large Segmentation Model(SAM) to Medical Images) did a similar thing.

Thanks for your kind reply. I think the MaskDecoder in SemSAM is not prompt-driven anymore. The finetune processing only make a new task-specific head. This paper (How to Efficiently Adapt Large Segmentation Model(SAM) to Medical Images) did a similar thing.

Thanks for your attention,
Yes, The SamSAM has no prompt, it is hard to design a model to output class-ware semantic mask, and this repository is not finished. For the semantic segmentation task, if we add different kinds of prompt, the model needs a lot of post-processing and need to merge similar mask, so I didn't add a prompt for semantic segmentation now. If we fix processing for a specific task, the users will lose the freedom to design their own idea. If the research community proposes a better solution, I will use it.
If I support the Instance segmentation or detection, I think the prompt processing will be easier to design.


We are facing diffculty in updating current documentation and we haev deployed in local. We cannot able to update the current local documentation. Can someone please help?

We are facing diffculty in updating current documentation and we haev deployed in local. We cannot able to update the current local documentation. Can someone please help?

Are you getting any error messages?

From where to update this document. I am not getting error but I dont see
any option to update the document. Please check screenshot.
On Tue, Mar 31, 2020 at 11:35 AM Mike Ralphson<EMAIL_ADDRESS>wrote:

Are you getting any error messages?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/slatedocs/slate/issues/1212#issuecomment-606419567,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AELHN7PHDLXJY556TURAE3LRKGBZPANCNFSM4LXHG3JQ
.

Please attach the screenshot to the issue directly.

You simply need to edit source/index.html.md and rebuild.

Closing due to inactivity - but please feel free to reopen the issue if necessary.


Yandex panoramas don't work on ios

Thanks to the author for a great app! I noticed a strange peculiarity. When redirecting traffic from iPhone via SpoofDPI, blocked sites work fine, but panoramas in the Yandex.maps app stop working. I tried limiting the list of proxied domains via privoxy, but it didn't help. Here is the list of domains that are redirected to SpoofDPI:
.googlevideo.com
.youtube.com
.ytimg.com
.ggpht.com
.nhacmp3youtube.com
Client information
OS:
server: macos, linux
client: ios
Version:
0.10.8
Command to run spoof-dpi:
spoof-dpi -addr <IP_ADDRESS>

Have you tried providing domains that should be proxified as multiple -pattern [domain|regex] options directly to Spoof-DPI?
Consider posting logs.

Tried it with this command:
spoof-dpi -addr <IP_ADDRESS> -debug -pattern .googlevideo.com -pattern .youtube.com -pattern .ytimg.com -pattern .ggpht.com -pattern .nhacmp3youtube.com
Same result. Here are the logs:

CONNECT report.appmetrica.yandex.net:443 HTTP/1.1
Host: report.appmetrica.yandex.net
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-08-19T23:01:36+03:00] [DNS] report.appmetrica.yandex.net resolving with system dns
DEBU[2024-08-19T23:01:36+03:00] [PROXY] Start HTTPS
DEBU[2024-08-19T23:01:36+03:00] [HTTPS] New connection to the server report.appmetrica.yandex.net <IP_ADDRESS>:50538
DEBU[2024-08-19T23:01:36+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:63133
DEBU[2024-08-19T23:01:36+03:00] [HTTPS] Client sent hello 517bytes
DEBU[2024-08-19T23:01:36+03:00] [HTTPS] Writing plain client hello to report.appmetrica.yandex.net
DEBU[2024-08-19T23:01:36+03:00] [PROXY] Request from <IP_ADDRESS>:50539
CONNECT p158-caldav.icloud.com:443 HTTP/1.1
Host: p158-caldav.icloud.com
User-Agent: Mac+OS+X/10.15.7 (19H2026) CalendarAgent/930.5.1
Connection: keep-alive
Proxy-Connection: keep-alive
DEBU[2024-08-19T23:01:36+03:00] [DNS] p158-caldav.icloud.com resolving with system dns
DEBU[2024-08-19T23:01:36+03:00] [PROXY] Start HTTPS
DEBU[2024-08-19T23:01:36+03:00] [HTTPS] New connection to the server p158-caldav.icloud.com <IP_ADDRESS>:50540
DEBU[2024-08-19T23:01:36+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:50539
DEBU[2024-08-19T23:01:36+03:00] [HTTPS] Client sent hello 517bytes
DEBU[2024-08-19T23:01:36+03:00] [HTTPS] Writing plain client hello to p158-caldav.icloud.com
DEBU[2024-08-19T23:01:39+03:00] [PROXY] Request from <IP_ADDRESS>:63134
CONNECT 6s3yaq-skadsdkless.appsflyersdk.com:443 HTTP/1.1
Host: 6s3yaq-skadsdkless.appsflyersdk.com
Proxy-Connection: keep-alive
Connection: keep-alive
DEBU[2024-08-19T23:01:39+03:00] [DNS] 6s3yaq-skadsdkless.appsflyersdk.com resolving with system dns
DEBU[2024-08-19T23:01:39+03:00] [PROXY] Start HTTPS
DEBU[2024-08-19T23:01:39+03:00] [HTTPS] New connection to the server 6s3yaq-skadsdkless.appsflyersdk.com <IP_ADDRESS>:50541
DEBU[2024-08-19T23:01:39+03:00] [HTTPS] Sent 200 Connection Estabalished to <IP_ADDRESS>:63134
DEBU[2024-08-19T23:01:39+03:00] [HTTPS] Client sent hello 517bytes
DEBU[2024-08-19T23:01:39+03:00] [HTTPS] Writing plain client hello to 6s3yaq-skadsdkless.appsflyersdk.com
DEBU[2024-08-19T23:01:41+03:00] [HTTPS] Error reading from <IP_ADDRESS>:63133 timed out
DEBU[2024-08-19T23:01:41+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:63133
DEBU[2024-08-19T23:01:41+03:00] [HTTPS] Error reading from <IP_ADDRESS>:63134 timed out
DEBU[2024-08-19T23:01:41+03:00] [HTTPS] Closing client Connection.. <IP_ADDRESS>:63134
DEBU[2024-08-19T23:01:41+03:00] [HTTPS] Closing server Connection.. report.appmetrica.yandex.net <IP_ADDRESS>:50538
DEBU[2024-08-19T23:01:41+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-08-19T23:01:41+03:00] [HTTPS] Error reading from <IP_ADDRESS>:443 timed out
DEBU[2024-08-19T23:01:41+03:00] [HTTPS] Closing server Connection.. 6s3yaq-skadsdkless.appsflyersdk.com <IP_ADDRESS>:50541

I don't own any iOS-based devices, so I tried to reproduce it on Android, without any luck, unfortunately. Looks like the YM app for Android sends requests to proxy.mob.maps.yandex.net to fetch street view data. The app bypasses the proxy when it sends requests to this specific domain. Not sure, how it works on iOS.

В общем проблема была в самом наличии переадресации через http прокси. В иос нет возможности указать отдельно http и https и нет возможности использовать только один из них. Пришлось поднять openvpn, указав в его конфиге переадресацию только на https прокси - в таком виде все работает.

This may be related to an issue with HTTP packet processing that was fixed by #229 and #230. The fix was merged to main, but has not been released yet.


New version: TechSmith.Snagit.2024 version <IP_ADDRESS>91 (24.2.2)

Created by 🥟 Dumplings in workflow run #7505.

Log
Updated: 24.2.1 → 24.2.2
No ReleaseNotes (en-US) for version 24.2.2
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

This package installs and launches normally on a Windows 10 VM.

This package installs and launches normally on a Windows 10 VM.


How to show loading indicator during POST processing?

Hi there, thanks a lot for the incredible work on this great tool! I see in https://github.com/tableflowhq/csv-import/pull/134 that there used to be some work about a loading indicator, but the branch got deleted and never merged into main? Is that functionality already in main and I am missing it? If yes, how do we show a loading indicator while posting results from the tool to a backend?
Thanks a lot for your answers :)

Hi @leomorpho! We no longer have that loading indicator, we can add an issue to include it back (let me know if this is something you'd want to work on).

I am personally interested in this feature!
It would help provide users with a clear understanding of what's happening behind the scenes :)

I'm also interested in this feature. This would make thing more clear for the user


state_machine.transition action/condition parameters are not validated

Currently there's no validation for the from, input and to parameters on the state_machine.transition action and on state_machine.transition confition. This is something that would be nice to add.
I don't know ESPHome validation framework well enough to implement this. If you know how to do that please help :)

Can potentially use CORE.raw_config to access state machine config to validate actions/conditions


Fix localProps & compact warnings

Some unwanted properties were passed down from React to DOM elements.
Fixed by renaming the props with a $ prefix to make them Transient.
How to test

Run the storybook locally
Open the Accordion
Open the Button component

They should work like before and no warnings should be logged in the console.
I've also tested this version of safe-react-components with the safe-react locally, and it also doesn't show the warnings anymore ✅
Fixes #105 and #105

Travis automatic deployment:
https://pr115--safereactcomponents.review.gnosisdev.com