Lint idea: old-functionality-hidden-behind-new-default-feature

Describe your use case
If a crate adds a new default feature that gates functionality that was previously always available, it would be a breaking change for a user of the crate that has default-features = false in the import in Cargo.toml.
E.g. the crate exports the function foo in version 0.5.0 and then adds a feature bar that is enabled by default in version 0.5.1, and gates the function foo behind it. A user of version 0.5.0 that run without default features would then encounter a breaking change if they run cargo update.
Describe the solution you'd like
Check if the public API changes between the baseline and current versions when default features are disabled.
Alternatives, if applicable
No response
Additional Context
I do not know a lot about how features and #[cfg] interact with this project, so what I propose may well be out of scope. Feel free to close this issue if so.
I accidentally did this in one of my crates once, so unfortunately I know it can happen!

Good news! This is already possible today, via a suitable (and not necessarily obvious) application of the existing CLI flags.
In cargo-semver-checks, we always compare a "baseline" and a "current" version. Normally, the "baseline" is "whatever is currently on crates.io" and the "current" version is "whatever we're about to cargo publish".
In the use case you describe, the baseline and current are both the same source code, but with different features. We can do this by a combination of the --only-explicit-features, --baseline-features, and --current-features flags.
For example, assuming you're in the directory of the project you want to check
cargo semver-checks \
    --baseline-root .                 # the current directory is the baseline too
    --only-explicit-features          # disable the feature-selection heuristic
    --baseline-features std           # enable only the "std" feature in the baseline version
    --current-features std,default    # enable the "std" and "default" features in the current version

I believe naming the default feature as default should work. If it doesn't, that's almost certainly a bug and not intentional — please let us know and we'll fix it.
Please let me know if this sounds good, or if there's a use case that isn't covered by this! I'm always happy to make the tool even more useful whenever we can.

Ah, thank you for the response! I edited my comment to be clearer what comparison I want to do, but if I have understood those CLI arguments correctly the command I want is
cargo semver-checks --only-explicit-features --baseline-features baz --current-features baz

where the current version has added a default feature called bar that hides the function foo. However, doing this leads to an error that says that cargo-semver-checks failed to run cargo update because the crate does not have the feature baz (even though it does).
The error message gives me a command that is supposed to reproduce the error, but that command completes successfully.

Ah, thanks, there's definitely a bug here. Apparently our CLI-feature-parsing code doesn't support comma-separated feature names. Thanks for flagging the problem, and sorry for the inconvenience! I'll open a separate issue for that.
The command you listed will compare the crate in the current working directory (with only feature baz) against the largest-versioned release on crates.io for that crate that is <= the version in the working directory, again with only feature baz. This is a legal command, but it doesn't sound quite like what we were chatting about, I think.
Running the following command on the semver-checks-features branch catches the breaking change:
$ cargo semver-checks --baseline-rev main --only-explicit-features --baseline-features 24bits --baseline-features 50bits --baseline-features libm --current-features 24bits --current-features 50bits --current-features libm
     Cloning main
     Parsing lambert_w v0.5.7 (current)
      Parsed [   0.763s] (current)
     Parsing lambert_w v0.5.6 (baseline)
      Parsed [   1.185s] (baseline)
    Checking lambert_w v0.5.6 -> v0.5.7 (minor change)
     Checked [   0.008s] 82 checks: 81 pass, 1 fail, 0 warn, 7 skip

--- failure function_missing: pub fn removed or renamed ---

Description:
A publicly-visible function cannot be imported by its prior path. A `pub use` may have been removed, or the function itself may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.35.0/src/lints/function_missing.ron

Failed in:
  function lambert_w::sp_lambert_w0, previously in file /tmp/lambert_w/target/semver-checks/git-main/a09016532578dced9c723272f6d65d3d26fc47da/src/lib.rs:137

     Summary semver requires new major version: 1 major and 0 minor checks failed
    Finished [   1.968s] lambert_w

Here I used a baseline of "the local repo's main branch", a current version of "the current directory (implicitly)", and enabled the libm,24bits,50bits features in both, albeit a bit verbosely to avoid comma-separated lists.
Running with --baseline-root . --baseline-features default works as well, and produces the same outcome. It uses the current directory as baseline, and enables the default features. This simulates the difference between "the current version on default features" vs "the current version with the previous-version's-default features enabled explicitly."

Thank you so much for your help! I'll see about adding some semver-checks commands to my CI then :D

Happy to help! Thanks for helping us find a bug as well!


Images are displayed from topleft side of the screen in inconsistent times

https://github.com/thiagoperes/IDMPhotoBrowser/blob/01fbba9cfa07199be79d5023e0178fd5f07a0a14/Classes/IDMPhotoBrowser.m#L372
This method return zero in inconsistently, do you have any idea about the reason why?

it is because of jsqmediaitem


 Make sure this is correct

Sorry to not have responded earlier but I'm still having that issue. Also, as stated in the issue, both computers share the same configuration. About my $XTERM value, here's what it's about https://github.com/YoEight/dot-files/blob/master/xterm-256color-italic.terminfo
Thanks for your time.


Release 1.0.1

Creates checks for fetchEntitlements, fetchProfile that can be passed in from Authflow options.
Fixes the relyingParty being null when trying to fetch an xbox token without calling a minecraft token function.
Un-exposes endpoints because its not needed.

can you just call this pr what this is and release it in a different pr?


discov package:  etcd can config TLS config using CertFile/KeyFile/TrustedCAFile

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

discov package: etcd can config TLS config using CertFile/KeyFile/TrustedCAFile

@sunshineing PTAL.


Several issues

I am curious about the solution for multisite. We recently ran into this issue as well where entry of the second language would overwrite the entry of the first language in our algolia index.
As far as I can see this was solve by adding site id to objectID as well as adding some checks in canIndexElement.

Why does it work when running the index commands in CLI, but not when editing an entry in Craft prior to 1.0.0? I would have thought the getElementQuery function would handle this because $this->critera either had a site handle or siteId present and thus would not return an element if the entry was of a different site handle or siteId? If this worked as expected (my expectations may be wrong) that would eliminate the need for checking site handle and id in the canIndexElement function in v1.0.0?

Why was site id added to objectID? What purpose does it serve?  The recommended solution for multilingual search in Algolia is to either have separate indexes or language specific keys in the same index. https://www.algolia.com/doc/tutorials/full-text-search/multi-language-search/multilingual-search/

Adding siteId to objectID breaks splitElementIndex as it is not handled there, it relies on the pre v1.0.0 where it was just element->id.

The comparison check for siteId added in v1.0.0 expects a comparison of same types, however, I specify siteId as an int in criteria whereas the siteId from Craft is of type string, making this comparison fail. I recommend adding changing it to if (isset($this->criteria['siteId']) && intval($element->site->id) !== intval($this->criteria['siteId'])) { if its necessary and can't be solved by the getElementQuery.

Because of a recent move to docker for development environments we experience a timeout issue connecting to Algolia because the network can be slow on some machines. This is easily solved by adding an option to set connection timeout on the algolia client instance. $this->client->setConnectTimeout(10); The value should be possible to specify in config/scout.php and not hardcoded of course.

I can make a pull request to fix some of these issues, but as question 1 and 2 was not clear to me I wanted to find out why it was solved this way before fixing 3 and 4.

Duplicate because of github issues.


Gizzard Shad

Lol but the whole fish is gizzard shad. Gizzard isn't an adjective describing the shad! Hahahahaha
Can we also add Grey Sole and Yellow Perch? So I guess just sole and perch as animals if those don't exist, and grey and yellow as adjectives


PMM-7 fixed mongo cluster for upgrade test

https://pmm.cd.percona.com/blue/organizations/jenkins/pmm2-upgrade-tests/detail/pmm2-upgrade-tests/24715/pipeline


Adjust to boost::asio API changes in boost 1.66.0

Mostly opening up this PR to trigger a discussion on how to handle the boost::asio API changes in boost 1.66.0.

@vosst , thank you for sending the PR.
It seems that the PR contains unrelated commit. Please use up-to-date master.
I will support boost.1.66.0 changes. It contains beast.
mqtt_cpp needs to support boost.1.66.0 and older releases. So I need to consider the mechanism.

I implemented new asio and beast supporting.
See #106 and #107.
So I close the PR.


Warning: cannot write object field <*Desc>

I get a bunch of following errors when trying to write model. I'm running the example in cudnn mode. When I sanitize the model using this: https://gist.github.com/szagoruyko/b6e70f6c6be9a8399c10 , the warnings went away, but the resulting model.t7 file is empty.
Any ideas?
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field
$ Warning: cannot write object field

use this snippet to sanitize your model, that version looks buggy:
   function removeDescriptors(net)
      net:for_each(function (val)
                      if torch.type(val):find('cudnn') then
                         for name,field in pairs(val) do
                            if torch.type(field) == 'cdata' then
                               val[name] = nil
                            end
                         end
                      end
                   end)
   end

Either ways the warning are harmless.
I just tested that this function works properly and saves the model correctly.

Added a model sanitizer to the example by default: https://github.com/facebook/fbcunn/commit/de2fd6ddb3bdb67bf4d314411ebcb6072b0645ea

@soumith thanks for the reply!
I'm still getting an empty model.t7 after using this new function. Any ideas?
ls kevenet,nEpochs=1/,SatFeb2802:23:182015/ -l
total 24
-rw-r--r-- 1 root root 5812 Feb 28 02:23 classes.t7
-rw-r--r-- 1 root root    4 Feb 28 02:26 model_1.t7
-rw-r--r-- 1 root root  169 Feb 28 02:26 optimState_1.t7
-rw-r--r-- 1 root root  140 Feb 28 02:26 test.log
-rw-r--r-- 1 root root  115 Feb 28 02:26 train.log
root@keven4255:~/fbcunn_imagenet/imagenet_runs#

i have no idea why you're getting an empty model. did you modify the example, or are you reporting out-of-the-box behavior?

It's likely an issue on my end. I did modify the example model. I will look into it. Thanks!


bundle.js includes react

The bundle includes React. You should add React and ReactDOM to webpack externals so that they are not included

The bundle is for the documentation website only, only the lib dir gets used in prod.

Touché. I thought it might have been for UMD support (might be worth considering, it's a pretty simple change to support)

Cool! I will look into it :)


wip: plugin system

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature
Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area driver-kmod

/area driver-ebpf

/area libscap
/area libsinsp

/area tests

What this PR does / why we need it:
Still a WIP. A detailed description will come soon.
Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:
Does this PR introduce a user-facing change?:

@ldegio: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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

@ldegio: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please ask for approval from ldegio after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ldegio
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [ldegio]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/retest build-libs

@leogr: The /retest command does not accept any targets.
The following commands are available to trigger jobs:

/test build-libs
/test build-libs-bundled-deps
/test build-libs-with-chisels

Use /test all to run all jobs.

In response to this:

/retest build-libs

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

/test build-libs

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

4289fdb fix a couple of compilation issues under Windows

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

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

Test name
Commit
Details
Rerun command

build-libs-bundled-deps
4289fdb02c08a8bfcf9049e0d883e9376f88c4b7
link
/test build-libs-bundled-deps

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Rerun command

build-libs-bundled-deps
4289fdb02c08a8bfcf9049e0d883e9376f88c4b7
link
/test build-libs-bundled-deps

build-libs
4289fdb02c08a8bfcf9049e0d883e9376f88c4b7
link
/test build-libs

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Rerun command

build-libs-bundled-deps
4289fdb02c08a8bfcf9049e0d883e9376f88c4b7
link
/test build-libs-bundled-deps

build-libs
4289fdb02c08a8bfcf9049e0d883e9376f88c4b7
link
/test build-libs

build-libs-with-chisels
4289fdb02c08a8bfcf9049e0d883e9376f88c4b7
link
/test build-libs-with-chisels

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

4289fdb fix a couple of compilation issues under Windows
e100eb7 don't link tbb on windows

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

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

Test name
Commit
Details
Rerun command

build-libs
4289fdb02c08a8bfcf9049e0d883e9376f88c4b7
link
/test build-libs

build-libs-with-chisels
4289fdb02c08a8bfcf9049e0d883e9376f88c4b7
link
/test build-libs-with-chisels

build-libs-bundled-deps
e100eb730de2b93a9d00a9c0d4d10fe628a433fa
link
/test build-libs-bundled-deps

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Rerun command

build-libs-with-chisels
4289fdb02c08a8bfcf9049e0d883e9376f88c4b7
link
/test build-libs-with-chisels

build-libs-bundled-deps
e100eb730de2b93a9d00a9c0d4d10fe628a433fa
link
/test build-libs-bundled-deps

build-libs
e100eb730de2b93a9d00a9c0d4d10fe628a433fa
link
/test build-libs

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Rerun command

build-libs-bundled-deps
e100eb730de2b93a9d00a9c0d4d10fe628a433fa
link
/test build-libs-bundled-deps

build-libs
e100eb730de2b93a9d00a9c0d4d10fe628a433fa
link
/test build-libs

build-libs-with-chisels
e100eb730de2b93a9d00a9c0d4d10fe628a433fa
link
/test build-libs-with-chisels

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

4289fdb fix a couple of compilation issues under Windows
e100eb7 don't link tbb on windows
0a85889 exclude unnecessary dependecies on Windows

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

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

Test name
Commit
Details
Rerun command

build-libs
e100eb730de2b93a9d00a9c0d4d10fe628a433fa
link
/test build-libs

build-libs-with-chisels
e100eb730de2b93a9d00a9c0d4d10fe628a433fa
link
/test build-libs-with-chisels

build-libs-bundled-deps
0a8588941c48007ec101dfa9371121a57a2a2896
link
/test build-libs-bundled-deps

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Rerun command

build-libs-with-chisels
e100eb730de2b93a9d00a9c0d4d10fe628a433fa
link
/test build-libs-with-chisels

build-libs-bundled-deps
0a8588941c48007ec101dfa9371121a57a2a2896
link
/test build-libs-bundled-deps

build-libs
0a8588941c48007ec101dfa9371121a57a2a2896
link
/test build-libs

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Rerun command

build-libs-bundled-deps
0a8588941c48007ec101dfa9371121a57a2a2896
link
/test build-libs-bundled-deps

build-libs
0a8588941c48007ec101dfa9371121a57a2a2896
link
/test build-libs

build-libs-with-chisels
0a8588941c48007ec101dfa9371121a57a2a2896
link
/test build-libs-with-chisels

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

4289fdb fix a couple of compilation issues under Windows
e100eb7 don't link tbb on windows
0a85889 exclude unnecessary dependecies on Windows
27cee54 windows compilation fix

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

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

Test name
Commit
Details
Rerun command

build-libs-bundled-deps
0a8588941c48007ec101dfa9371121a57a2a2896
link
/test build-libs-bundled-deps

build-libs-with-chisels
0a8588941c48007ec101dfa9371121a57a2a2896
link
/test build-libs-with-chisels

build-libs
27cee540407cd7325dc8c972a322fffbfe7a492e
link
/test build-libs

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Rerun command

build-libs-with-chisels
0a8588941c48007ec101dfa9371121a57a2a2896
link
/test build-libs-with-chisels

build-libs
27cee540407cd7325dc8c972a322fffbfe7a492e
link
/test build-libs

build-libs-bundled-deps
27cee540407cd7325dc8c972a322fffbfe7a492e
link
/test build-libs-bundled-deps

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Rerun command

build-libs
27cee540407cd7325dc8c972a322fffbfe7a492e
link
/test build-libs

build-libs-bundled-deps
27cee540407cd7325dc8c972a322fffbfe7a492e
link
/test build-libs-bundled-deps

build-libs-with-chisels
27cee540407cd7325dc8c972a322fffbfe7a492e
link
/test build-libs-with-chisels

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Rerun command

build-libs
27cee540407cd7325dc8c972a322fffbfe7a492e
link
/test build-libs

build-libs-with-chisels
27cee540407cd7325dc8c972a322fffbfe7a492e
link
/test build-libs-with-chisels

build-libs-bundled-deps
1d25409895a2947bcdafdb6037be2f677543f578
link
/test build-libs-bundled-deps

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Rerun command

build-libs-with-chisels
27cee540407cd7325dc8c972a322fffbfe7a492e
link
/test build-libs-with-chisels

build-libs-bundled-deps
1d25409895a2947bcdafdb6037be2f677543f578
link
/test build-libs-bundled-deps

build-libs
1d25409895a2947bcdafdb6037be2f677543f578
link
/test build-libs

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Rerun command

build-libs-bundled-deps
1d25409895a2947bcdafdb6037be2f677543f578
link
/test build-libs-bundled-deps

build-libs
1d25409895a2947bcdafdb6037be2f677543f578
link
/test build-libs

build-libs-with-chisels
1d25409895a2947bcdafdb6037be2f677543f578
link
/test build-libs-with-chisels

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale


#784: VIP updates and DCOS package cleanup

I noticed that we had inconsistent use of host port and VIP in the bootstrap, so this has been corrected. I've tested this in our dev cluster and everything appears to be correctly routing via the VIPs. This further solidifies our dependence on DCOS 1.8+ and we should ABSOLUTELY call this out in the upcoming 4.4.0 release.
I also cleaned out the DCOS_USER and DCOS_PASS environment variables which I had discovered to be irrelevant since DCOS_OAUTH_TOKEN is the only value that correctly allows bootstrapping apps within Marathon when authentication is enforced (EE). All this is to prep for the DCOS Universe updates I'm also working on for 4.4.0 release.

I'm seeing behavior with this change that raises some concern for extensive use of VIPs. It appears like available connections are being exhausted between webserver and DB that my be evidence of the problem documented here: https://dcos.io/docs/1.7/usage/service-discovery/load-balancing/#persistent-connections
This can be PRed but merge should be held off until further testing can identify the problem.

I'm going to close this for the present, as I don't have time to full investigate the issue with VIP use. Its not a huge concern that we switch entirely to VIPs at this time.


[C++][Parquet] Add compressed data page unit tests

Reporter: Wes McKinney / @wesm
Assignee: Wes McKinney](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=wesm) / @wesm
Note: This issue was originally created as PARQUET-457. Please see the migration documentation for further details.

Wes McKinney / @wesm:
Can be completed after PARQUET-456 is done.

Wes McKinney / @wesm:
see patch here https://github.com/apache/parquet-cpp/pull/58

Julien Le Dem / @julienledem:
Issue resolved by pull request 58
https://github.com/apache/parquet-cpp/pull/58


[docs] Fix broken link in README.md

Fix broken link, minor thing 😉

@Primajin Thank you for this first PR :)


Question about audio shape

In the code of transformer_decoder.py," audio_features = audio_features.repeat(1, self.num_queries, 1).reshape(self.num_queries, -1, audio_features.shape[-1])  " Is it really correct to use the reshape operation instead of permute here?

According to https://pytorch.org/docs/stable/generated/torch.permute.html and https://pytorch.org/docs/stable/generated/torch.reshape.html, 'permute' is better.
When possible, the return of the 'reshape' will be a view of input that is equal to 'permute'.


cfn-signal doesn't exist

buildkite-elastic.yml includes this in the UserData script:
/usr/local/bin/cfn-signal -e \$? -r 'cfn-init finished' \
  --stack $(AWS::StackName) --resource 'AgentAutoScaleGroup' --region $(AWS::Region)

However, /usr/local/bin/cfn-signal doesn't exist:
Cloud-init v. 0.7.7 running 'modules:config' at Tue, 07 Jul 2015 00:56:00 +0000. Up 50.92 seconds.
#!/bin/bash -xv
/usr/local/bin/cfn-init -s arn:aws:cloudformation:us-east-1:349538293217:stack/ci-20150706-175140/55799120-2442-11e5-b551-50fa1dbb2c64 -r AgentLaunchConfiguration --region us-east-1
+ /usr/local/bin/cfn-init -s arn:aws:cloudformation:us-east-1:349538293217:stack/ci-20150706-175140/55799120-2442-11e5-b551-50fa1dbb2c64 -r AgentLaunchConfiguration --region us-east-1
/var/lib/cloud/instance/scripts/part-001: line 2: /usr/local/bin/cfn-init: No such file or directory
/usr/local/bin/cfn-signal -e $? -r 'cfn-init finished' \
  --stack ci-20150706-175140 --resource 'AgentAutoScaleGroup' --region us-east-1
+ /usr/local/bin/cfn-signal -e 127 -r 'cfn-init finished' --stack ci-20150706-175140 --resource AgentAutoScaleGroup --region us-east-1
/var/lib/cloud/instance/scripts/part-001: line 3: /usr/local/bin/cfn-signal: No such file or directory

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.04
DISTRIB_CODENAME=vivid
DISTRIB_DESCRIPTION="Ubuntu 15.04"

$ curl http://<IP_ADDRESS>/latest/meta-data/ami-id ; echo
ami-55986a3e

(it needs to be installed in the AMI)


Parse void function

I add the feature of parsing function with void type and error handling for variables having void type.

You shall add test cases regarding void support. Also, you have to consider the usage of pointer to void.

Append Close #4 in Git commit messages so that once this pull request is merged, #4 will be closed by GitHub automatically.

The usage of pointer to void means I need to add type conversion support?

The usage of pointer to void means I need to add type conversion support?

You can regard void * as char * except the disallowed rule about dereference on void *. That is, the result of dereference of char * is a char typed object, but it is forbidden to dereference void *.

I only test arithmetic of pointer to void, should I test more ?  (I can't find another)

I only test arithmetic of pointer to void, should I test more ? (I can't find another)

You can send another pull request to improve C Pointer arithmetic.

Use git rebase -i to rework these commits. I expect 2 functional commits:

changes against C compiler internals;
related test case(s);

I am very sorry for those ugly commit on . I think I need to think the rule clearly and experiment them before
continuing to follow up the PR.

I am very sorry for those ugly commit. I think I need to think the rule of git clearly and experiment them before continuing to follow up the PR.

No problem. I can even squash these commits.

I create a new branch for new test set to check pointer arithmetic. Should I pull request it after finishing the PR, or now?

I create a new branch for new test set to check pointer arithmetic. Should I pull request it after finishing the PR, or now?

You can simply push these commits to this PR/branch.


[NTR] migratory muscle precursor

Preferred term label:
migratory muscle precursor
Synonyms
Definition (free text, please give PubMed ID)
Muscle precursor cells that delaminate from the dermomyotome after epithelial-to-mesenchymal  transition (EMT) and undergo long-range migration while retaining proliferative capacity.


Fix/Rework Bookstack Update function

[!NOTE]
We are meticulous when it comes to merging code into the main branch, so please understand that we may reject pull requests that do not meet the project's standards. It's never personal. Also, game-related scripts have a lower chance of being merged.

Description
Complete Rework of the Update function, so it actually updates the APP.
It now creates a backup of all relevant files in an archive, as well as a dump of the Database.
I
Fixes #757
Type of change
Please check the relevant option(s):

[X] Bug fix (non-breaking change that resolves an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (a fix or feature that would cause existing functionality to change unexpectedly)
[ ] New script (a fully functional and thoroughly tested script or set of scripts.)

Prerequisites
The following efforts must be made for the PR to be considered. Please check when completed:

[X] Self-review performed (I have reviewed my code, ensuring it follows established patterns and conventions)
[ ] Testing performed (I have tested my changes, ensuring everything works as expected)
[ ] Documentation updated (I have updated any relevant documentation)

Additional Information (optional)
Provide any additional context or screenshots about the feature or fix here.
Related Pull Requests / Discussions
If there are other pull requests or discussions related to this change, please link them here:

Related PR #

I´m on a Business trip until Friday evening. I will work in the changes when I get back home.
I have testet the file restore beforehand, I test it again after the changes.

I have made the requested changes and removed the backup part. I testet it and the data migration seems to be working.
If you can, please test it also if you can: bash -c "$(wget -qLO - https://raw.githubusercontent.com/michelroegl-brunner/ProxmoxVE/refs/heads/dev/ct/bookstack.sh)"
Thank you!


Add box-shadow?

Forgive me if this has been asked but why is there no box-shadow?
I don't like to rely on too many images and can do almost everything with straight css.
I'd love to contribute after I learn my way around the codebase.
Thanks!

Hi @ShaggyDude
As said on Slack box-shadow isn't supported by most of clients. If you still want to use it, in 3.3.3 you will be able to add css-class to any MJML element and apply it in mj-style.

Any solution?

It's still the same situation, you can use a css-class on your element and define the box-shadow in a mj-style

@iRyusa this still doesn't work. adding box-shadow to css-class defined in mj-style produces no results

https://mjml.io/try-it-live/r1UfEXtOH It does work fine.

This works on mjml v4.4.0 and later. It doesn't work on https://mjml.io/try-it-live because the one runs v4.3.0
<mjml>
    <mj-head>
        <mj-style>
            .box-shadow a, .box-shadow p {
                box-shadow: 0 4px 6px hsla(0,0%,46%,0.2), 0 1px 3px hsla(0,0%,46%,0.2);
            }
        </mj-style>
    </mj-head>
    <mj-body>
        <mj-section>
            <mj-column>
                <mj-button css-class="box-shadow">You can't click me!</mj-button>
            </mj-column>
        </mj-section>
        <mj-section>
            <mj-column>
                <mj-button css-class="box-shadow" href="google.com">Visit google</mj-button>
            </mj-column>
        </mj-section>
    </mj-body>
</mjml>

It does work on the try it live too, it's just hidden in the default background color : https://mjml.io/try-it-live/SkDAvRY_S

Correct me if I'm wrong but box-shadow are still not support by many clients


Refactor/polymake

I added a second property for the polymake variety and already incorporated it where it is easy. Furthermore I changed some names to the Oscar convention.

I propose to keep the above points as issues, so we can discuss them at some point(https://github.com/oscar-system/JToric/issues/35, https://github.com/oscar-system/JToric/issues/36). Still, I do merge these changes now.


Fixed delay to use AHB clock / 8 instead of CORE clk

I noticed delays where off by a factor 8. This was because the delay function calculated it's time based off the core clock. The cortex system timer is actually connected to AHB clock with a prescaler of /8.

Confirmed working - also see: https://stackoverflow.com/questions/64172446/systick-timer-on-cortex-m4-what-is-its-prescaler
@dotcypress Can you take a look ?

Confirmed working - also see: https://stackoverflow.com/questions/64172446/systick-timer-on-cortex-m4-what-is-its-prescaler
@dotcypress Can you take a look ?

Awesome, thanks!

Awesome, thanks!


feat(c8yscrn): Add screenshot automation workflow

With c8yscrn, a new tool for automating screenshot workflows has been introduced. It supports yaml configuration of workflows and wrap Cypress screenshot capabilities as well as actions to click, type, highlight, etc. before taking screenshots. More information and detailed documentation can be found in the docs/ folder of cumulocity-cypress.
Closes #161

Approved


Update 301 links

$ httpx -l /tmp/urls.txt -silent -sc -mc 301
https://github.com/AshiqurEmon/nuclei_templates.git [301]
https://github.com/PedroFerreira97/nuclei_templates [301]
https://github.com/bhataasim1/PersonalTemplates.git [301]
https://github.com/badboy-sft/badboy_17-Nuclei-Templates-Collection [301]
https://github.com/5cr1pt/templates [301]
https://github.com/0x727/ObserverWard_0x727 [301]
https://github.com/themoonbaba/private_templates [301]

Thanks again! @szybnev


Statement Schemas

It's becoming apparent that there is a need to track the schema of the objects contained in a statement, as part of the statement envelope  -- aleph/44
Adding support at the statement proto is relatively straightforward: a new field can be added without invalidating existing statements.
Supporting indexing and MCQL queries using the schema can be implemented in two ways:

extend the envelope to include the schema, which can be NULL
index schemas with a secondary index table, only track statements where the schema is not NULL

The first option is more intrusive, as it will require an alteration of the Envelope table. It also has complications with NULL semantics.
The second option is preferrable:  straightforward creation of a new table and index (trivial migration), with MCQL support similar to how we query on wki, perhaps with criteria extended to support prefix matching.

I think this has gotten trickier: there are now new nodes operated by the community in the wild, and it's not reasonable to ask them to re-ingest their data to get schemas.

So we need a migration path that will migrate existing statements to have schemas.
One approach is to iterate through the statement db and republish statements with the schema inferred by the dependency and the schema wki in mediachain.schemas.
This should only happen for locally published statements, statements merged from other nodes should not be republished, but instead be remerged (to get the new statements) once the publishers have migrated.
We also need a mechanism for cleaning up those old statements, so perhaps we need to take the Envelope table extension approach and treat schema as an envelope selector in MCQL -- cf NULL semantics.

Hmm vyzo let's punt on this for 1.2 and think about a backfill/migration mechanism

agreed.


Fix pathological backtracking regexp

This particular pattern (..+)* has been responsible for several
instances of non-terminating regexps in Parsoid.

Thank you!


🐛 [BUG] - Block translated content causes the page to overflow horizontally on the experiment admin form page

Description

The block translated content's inline form causes the page to overflow horizontally on the experiment admin form page. If you collapse all the block translated content inline forms on the page, the overflow disappears.
A possible solution is to make the individual inline forms have their own overflow with scroll. If we can make the whole inline form more compact horizontally, that would probably help a bit as well.
Screenshots

Overflow

Collapsed block translated content overflows not

Reproduction URL
No response
Reproduction steps
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Logs
No response
Browsers
No response
OS
No response
Additional context
No response

I'm hoping that this will be addressed as a side effect of #1321, so self-assigning this one.


make the Union{Bool,Missing} widening behavior (#543) configurable

As requested at https://github.com/aviatesk/JET.jl/pull/543#issuecomment-1606721610.

Codecov Report
Patch coverage: 95.83% and no project coverage change.

Comparison is base (e46dbe7) 89.81% compared to head (61ebd56) 89.82%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #547   +/-   ##
=======================================
  Coverage   89.81%   89.82%
=======================================
  Files          10       10
  Lines        3055     3067   +12
=======================================
+ Hits         2744     2755   +11
- Misses        311      312    +1

Impacted Files
Coverage Δ

src/analyzers/jetanalyzer.jl
87.71% <95.45%> (+0.04%)
:arrow_up:

src/JET.jl
82.07% <100.00%> (+0.03%)
:arrow_up:

src/toplevel/virtualprocess.jl
94.47% <100.00%> (ø)

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

There is an increase in minor allocations, but I am unable to find any further optimization methods. Hopefully this regression may be eliminated during refactoring ReportPass when addressing #544.


FFmpeg backend

FFmpeg parameters for opencv capture
I have started looking through CamGear and am hoping it will allow for more control of the ffmpeg backend
Question
So is it possible to launch an opencv capture object with an ffmpeg command.
The reason being i would like to use cuvid/ h264_cuvid (hardware decoder)
(i know you can kinda do it with # OPENCV_FFMPEG_CAPTURE_OPTIONS="video_codec;h264_cuvid|rtsp_transport;tcp")
but this doesnt give access to all the other ffmpeg features)
but also pipe that capture to another containter .mp4 with a codec copy so we dont waste resources.
and also potentially map it to another sink like an ffserver feed
Regards Andrew

Hello @SurionAndrew, this information is new to me. What version of OpenCV API you are using your machine? Also, Kindly answer following questions:

The reason being i would like to use cuvid/ h264_cuvid (hardware decoder)

Can you point me to the API/docs/example-code on how you'll enable support for this decoder?

So is it possible to launch an opencv capture object with an ffmpeg command.
but also pipe that capture to another containter .mp4 with a codec copy so we dont waste resources.
and also potentially map it to another sink like an ffserver feed

Can you demonstrate each of them with any example code/command, or provide a link or something related?
Also, kindly fill the issue template properly before opening an issue.

Raw FFmpeg command that doesnt decode at all:
ffmpeg -re -override_ffserver -rtsp_transport tcp  -i "rtsp://USRNAME:PASS@<IP_ADDRESS>:554/Streaming/Channels/101/" -map 0:0 -c:v copy http://localhost:8090/feed1.ffm -map 0:0 -c:v copy out.mp4
This uses nearly no cpu or gpu but pipes the output to ffserver (for streaming)  and also saves the video in an mp4 container(camera stream is already encoded as h264)
Python
import os
os.environ["OPENCV_FFMPEG_CAPTURE_OPTIONS"] = "video_codec;h264_cuvid|rtsp_transport;tcp"
cap = cv.VideoCapture(ipCamera)
This leverages the ffmpeg backend to use the Nvidia hardware decoder (cuvid/nvdec)
I have previously written my own c/c++ classes using libAV which allows far more control of the libAV functions(what ffmpeg was built on)
Gstreamer
I was hoping there could be a way of giving a string cmd similar to how gstreamer works with opencv
https://answers.opencv.org/question/202017/how-to-use-gstreamer-pipeline-in-opencv/
Architecture :
RTSP(h264)   ----> opencv (decoded)
RTSP(h264)   ----> mp4 (codec copy)
RTSP(h264)   ----> streamed(codec copy)
OpenCV details
OpenCV 4.1.1

@SurionAndrew Thank you for this valuable information. But sorry to say, I'm still confused what's the goal here?
Are you trying:

To use Nvidia hardware decoder for OpenCV's videocapture API?
To save the video from a rstp server to a mp4 fileformat?
To run a Gstreamer Pipeline within OpenCV?
all or them?

Because It's all possible with vidgear but with multiple gears. Camgear API alone cannot achieve all this.

Sorry the goal is to ultimately create a system that analyses as many ip camera feeds as possible while maintaining the ability to:

Save Video Footage
Stream the footage real time
Uses Neural Nets for classification (computationally expensive)
Many more future features

Yes I have decided to use NVIDIA Gpu's to help accelerate the system for both inference as well as having hardware encoders and decoders
I have already achieved many of my development goals however I am always on the lookout for better solutions

@SurionAndrew Thanks for explaining, Here's how you can achieve these tasks with vidgear:

Save Video Footage

See the powerful WriteGear API's Compression Mode that uses FFmpeg as backend, and allows us to exploit almost all available parameters(framerate, bitrate, codecs, format, and encoder, etc.) supported by FFmpeg, effortlessly and flexibly and while doing that it robustly handles errors/warnings all along very quietly.
💡 You can install FFmpeg according to system by following this Wiki, plus automated installation on Windows OSes.

Stream the footage real time

Currently for streaming video, VidGear provides NetGear API, which is exclusively designed to transfer video frames & data synchronously (Pair & Client/Server) as well as asynchronously (Publish/Subscribe) between various interconnecting systems over the network in real-time. It provides a flexible wrapper around ZeroMQ  (also known as ØMQ, 0MQ, or zmq) - a high-performance asynchronous distributed messaging library that aim to be used in distributed or concurrent applications.

Uses Neural Nets for classification (computationally expensive)

VidGear is a high-performance python Video Processing library, so you have to use a third party library with vidgear to deal with Neural Nets. But surely VidGear's threaded APIs will definitely helps in boosting up the overall performance.

Many more future features

Anything related to powerful Video Processing is possible with vidgear's APIs. Kindly go thoroughly through each Gear(a.k.a API's) Wiki to see know more about them. If something doesn't works or supported ask here.

Yes I have decided to use NVIDIA Gpu's to help accelerate the system for both inference as well as having hardware encoders and decoders

Although, NVIDIA GPUs isn't that great with OpenCV, but you can surely boost performance with FFmpeg by enabling CUDA backend, thereby boosting performance of WriteGear API's encoder(see my comment to use HW accelerated encoder in WriteGear) in compression mode. Another great news is that OpenCV recently added support for CUDA backend in DNN modules. Also as you shown above, its possible to leverages the ffmpeg backend to use the Nvidia hardware decoder (cuvid/nvdec). Therefore, hardware acceleration is possible in both encoders and decoders part.

I was hoping there could be a way of giving a string cmd similar to how gstreamer works with opencv
https://answers.opencv.org/question/202017/how-to-use-gstreamer-pipeline-in-opencv/

See CamGear API Wiki, It can handle any and any number of video streams. Almost anything.

Finally, I'll advise you to read entire vidgear's WIKI docs carefully and thoroughly as there's a lot of hidden tips and answers to all your problems.  Examples  are also given in the wiki. Good luck!

Awesome!
Thank you so much for taking the time and effort to gt back to me :)
I will take some time to have a deep dig around

Maybe you can use a gstreamer pipeline to boost your decoding (using nvidia decoder and converter). But then you will have a CPU copy because opencv appsink needs frames in CPU memory instead GPU memory....


ticket309.apply-integer-serialization-bugfix-to-externalized-libzerocash.0

Since this was already landed (and upstream just merged it), I'm declaring it reviewed and merging it.


runtime: Garbage Collector is falling into infinite loop

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go1.10 darwin/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/bart.smykla/Library/Caches/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/bart.smykla/go"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.10/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.10/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/5p/3w59xw4n7h5b2r4841mbrfsc0000gn/T/go-build756935331=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
Occasionally (few times a day) after our application doesn't succeed sending a message (simple HTTP request) Garbage Collector is falling into infinite loop.
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
Unfortunately I can't reproduce it manually. It appears randomly.
What did you expect to see?
server_1              | {"caller":"/go/src/server/handler.go:30","component":"Handler","error":"dial tcp: lookup api on <IP_ADDRESS>:53: no such host","function_name":"server/handler.(*Handler).ProcessMessage","level":8,"method":"ProcessMessage","msg":"dispatching msg","success":false,"timestamp":1531923332,"type":"ERROR", "reqMethod": "POST", "endpoint": "http://api:8080/attempts/v1"}

What did you see instead?
server_1              | {"caller":"/go/src/server/handler.go:30","component":"Handler","error":"dial tcp: lookup api on <IP_ADDRESS>:53: no such host","function_name":"server/handler.(*Handler).ProcessMessage","level":8,"method":"ProcessMessage","msg":"dispatching msg","success":false,"timestamp":1531923332,"type":"ERROR", "reqMethod": "POST", "endpoint": "http://api:8080/attempts/v1"}
websdk-server_1       | gc 2 @8.492s 0%: 0.030+0.62+0.085 ms clock, 0.12+0.19/0.49/0.73+0.34 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 3 @8.510s 0%: 0.061+0.72+0.084 ms clock, 0.24+0.29/0.40/0.99+0.33 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 4 @8.529s 0%: 0.042+0.55+0.093 ms clock, 0.17+0.17/0.40/0.62+0.37 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 5 @8.548s 0%: 0.035+0.61+0.22 ms clock, 0.14+0.22/0.38/0.54+0.91 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 6 @8.568s 0%: 0.032+0.53+0.10 ms clock, 0.12+0.15/0.31/0.60+0.40 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 7 @8.585s 0%: 0.026+0.53+0.18 ms clock, 0.10+0.14/0.34/0.66+0.72 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 8 @8.602s 0%: 0.035+0.63+0.14 ms clock, 0.14+0.18/0.48/0.52+0.57 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 9 @8.618s 0%: 0.039+0.42+0.050 ms clock, 0.15+0.15/0.31/0.44+0.20 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 10 @8.635s 0%: 0.039+0.49+0.073 ms clock, 0.15+0.16/0.37/0.49+0.29 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 11 @8.653s 0%: 0.032+0.58+0.14 ms clock, 0.12+0.14/0.46/0.53+0.56 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 12 @8.670s 0%: 0.033+0.52+0.14 ms clock, 0.13+0.15/0.30/0.55+0.57 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 13 @8.686s 0%: 0.11+0.48+0.12 ms clock, 0.46+0.22/0.32/0.64+0.49 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 14 @8.703s 0%: 0.042+0.57+0.10 ms clock, 0.16+0.15/0.32/0.63+0.41 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 15 @8.721s 0%: 0.044+0.58+0.078 ms clock, 0.17+0.18/0.45/0.63+0.31 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 16 @8.738s 0%: 0.033+0.46+0.12 ms clock, 0.13+0.18/0.33/0.58+0.48 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 17 @8.754s 0%: 0.032+0.47+0.079 ms clock, 0.12+0.15/0.34/0.55+0.31 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 18 @8.771s 0%: 0.043+0.48+0.086 ms clock, 0.17+0.18/0.33/0.67+0.34 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 19 @8.787s 0%: 0.032+0.43+0.22 ms clock, 0.13+0.13/0.37/0.56+0.90 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 20 @8.806s 0%: 0.036+0.55+0.16 ms clock, 0.14+0.15/0.35/0.65+0.66 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 21 @8.823s 0%: 0.055+0.62+0.088 ms clock, 0.22+0.26/0.37/0.66+0.35 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 22 @8.840s 0%: 0.026+0.51+0.11 ms clock, 0.10+0.14/0.28/0.64+0.44 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 23 @8.855s 0%: 0.027+0.53+0.083 ms clock, 0.11+0.16/0.39/0.63+0.33 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 24 @8.873s 0%: 0.042+0.64+0.12 ms clock, 0.16+0.26/0.50/0.61+0.51 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 25 @8.889s 0%: 0.028+0.51+0.11 ms clock, 0.11+0.16/0.38/0.75+0.44 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 26 @8.906s 0%: 0.030+0.52+0.069 ms clock, 0.12+0.16/0.30/0.64+0.27 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 27 @8.922s 0%: 0.026+0.47+0.054 ms clock, 0.10+0.15/0.34/0.45+0.21 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 28 @8.938s 0%: 0.031+0.60+0.14 ms clock, 0.12+0.19/0.52/0.53+0.57 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 29 @8.954s 0%: 0.025+0.43+0.10 ms clock, 0.10+0.14/0.32/0.41+0.43 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
websdk-server_1       | gc 30 @8.972s 0%: 0.025+0.50+0.073 ms clock, 0.10+0.16/0.36/0.70+0.29 ms cpu, 4->4->0 MB, 5 MB goal, 4 P
...

It's fairly unlikely that the garbage collector is in an infinite loop.  It's much more likely that your program has entered an infinite, or long-lasting, loop that is allocating memory.
Is there a way that we can reproduce the problem ourselves?


Support for type-aware rules

Clear and concise description of the problem
Type-aware rules require type information to run. It would be great if type-aware rules "just worked".
Suggested solution
Ideally, this should be all that is needed (when using @typescript-eslint/parser v8):
const { valid, invalid } = createRuleTester({
  name,
  rule,
  configs: {
    languageOptions: {
      parser: typescriptParser,
      parserOptions: {
        projectService: true, // or `project: true`
      },
    },
  },
});

I don't know what needs to be changed under the hood to make this actually work.
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I don't know what is missing for that to work. Ideally, it should directly work.
I don't use it and don't have the bandwidth to investigate into this, pr welcome, thanks!


801 - History: Database implementation

Based on discussion with the team next possible solutions were identified:

using pgAudit (https://github.com/pgaudit/pgaudit/blob/master/README.md) to generate changelogs and use them to populate history table;
using triggers in DB to populate history table;
using custom code and handle CRUD events in the code and insert data to history table.
After initial investigation, second approach seems to be a best choice as it saves a lot of efforts.
Chosen extension: https://github.com/supabase/supa_audit/blob/main/README.md

What was done:

copied code from https://github.com/supabase/supa_audit/blob/main/supa_audit--0.3.0.sql
updated script to add permissions to ccbc_auth_user, ccbc_analyst, ccbc_admin;
installed extension uuid-ossp (run in psql create extension "uuid-ossp";);
updated script to expicitly use public schema for calls to uuid_generate_v4 and uuid_generate_v5;

Is there something here for PO review?


Add MintBurn indexer

Ready for review, changes since the mob review:

handling of intervals and a new interval test
end-to-end test now also uses generator to create TxMintValue

I think I've also found and fixed two bugs in rewindable index:

4af8f94 filterWithQueryInterval wasn't using the start of interval to filter out elements
594f20a rewind didn't account for gaps in events

Not sure about the filterWithQueryInterval fix as it makes a test fail in rewindable-index: New index properties -> Insert is folding the structure.
@raduom should inspect these and perhaps add tests to for regressions.
(CI fails currently due to a bug in cabal-fmt, being worked on here: https://github.com/input-output-hk/plutus-apps/pull/921)

Pre-submit checklist:

Branch

[X] Tests are provided (if possible)
[X] Commit sequence broadly makes sense
[X] Key commits have useful messages
[ ] Formatting, PNG optimization, etc. are updated
[X] Important changes are reflected in changelog.d of the affected packages

PR

[X] Self-reviewed the diff
[X] Useful pull request description
[ ] Reference the ADR in the PR and reference the PR in the ADR (if revelant)
[X] Reviewer requested

Some of the Plutus E2E tests fail in CI but (1) those are unrelated to this pr and (2) they are being worked on elsewhere.


[Doc] Add steps to remove weave-net

Coverage remained the same at 34.684% when pulling 265414130feae6c14bf42d0ac55f992da8de35ad on binyli/doc into 2950a8d1b4c123e361e552e00501991f9dc2778e on master.

Is it possible to write an ansible role to do this work?

Is it possible to write an ansible role to do this work?

I am not sure. The kubectl need to run on dev-box, Seems we need to add localhost in the inventory.
The kubectl command only need to run once. It's not time consuming. And admin should have basic knowledge about k8s.

Is it possible to write an ansible role to do this work?

I am not sure. The kubectl need to run on dev-box, Seems we need to add localhost in the inventory.
The kubectl command only need to run once. It's not time consuming. And admin should have basic knowledge about k8s.

Agree with you about the point that admin should have knowledge of k8s.


support iOS native momentum scrolling

see http://css-tricks.com/snippets/css/momentum-scrolling-on-ios-overflow-elements/

Actual code base of ui-scroll is in https://github.com/Hill30/NGScroller. Please re-submit your issue over there if needed.


[Spark] Merge should materialize source with correlated subqueries

Which Delta project/connector is this regarding?

[x] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[ ] Other (fill in here)

Description
Small fixes for determinism determination for Merge Materialize Source.

since we consider joins as potentially non-deterministic, we should also consider correlated subqueries as such, because they essentially are also joins.
non Delta source will not be found in subqueries in findFirstNonDeltaScan, but found in findFirstNonDeterministicNode. This will make merge source materialization give wrong reason for materialization.

How was this patch tested?
Added tests with subqueries and nested subqueries in Project and Filters and correlated subqueries.
Does this PR introduce any user-facing changes?
No.

@larsk-db @cstavr @tomvanbussel this is a redo of https://github.com/delta-io/delta/pull/2896 after investigating the test failures the new tests caused.


CloudEvent must be an abstraction of the spec, and not JSON specific

Again, I'm not saying the current prototype is incorrect, but writting this issue so I'm sure we address the spec explicitly.
Cloud Event is an abstraction of what is an event: https://github.com/cloudevents/spec/blob/v1.0/spec.md
As so, our CloudEvent class should not assume any serialization of a CloudEvent concept, and model the concept without thinking about the serialization. This implies:

There should be no data_base64 attribute, but helpers to set bytes correctly
Extensions should be treated as explicit extensions (and not simple new attributes at the base level).

Example:
c = CloudEvent(
    id=12,
    source='MyApp',
    type='CreateStuff'
)  # specversion is set by default to "1.0"

c.subject = "mynewfile.jpg"  # I could have set it as kwargs, but for the sake of sample

# Set data. API here could be discuss, we could use `data` property setter for instance
c.set_bytes_data(b"PDF%...", "application/pdf")

# Extensions are allowed aside, to avoid collision
c.extensions["reasonCode"] = 204

c.model # Returns the deserialized model

A JSON serialization of this would be:
{
    "id": 12,
    "source": "MyApp",
    "type": "CreateStuff",
    "subject": "mynewfile.jpg",
    "datacontenttype": "application/pdf",
    "data_base64": "ABCDEF_BASE64_OF_PDF",
    "reasonCode": 204
}

While a binary mode serialization would be HTTP request
ce-id: 12
ce-source
ce-source: MyApp
ce-type: CreateStuff
ce-subject: mynewfile.jpg
ce-datacontenttype: application/pdf
ce-reasonCode: 204

PDF%...

Notes from our OOB discussion:
Extensions:

take as kwargs, potential risk overlap with data_base64/data args.

Binary vs. json serialization:

kwarg overload in send() to let control of this.  We assume b64 in absence of any guidance since it "will just work" consistently.

Have enum for overload type, e.g. JSON or binary serialization mode.

won't need set_bytes_data since this will be handled at send time.
data as string? send plain.  bytes?  b64 encode and send. (with optional overload.)

this is gonna be wacky in 2.7.  Perhaps "if unicode send directly; if otherwise encode and bytes."

c.model: StorageBlobDeletedEvent, keep in mind this may shift as we adjust the "GetData" discussions.


Moves @ConditionalOnBean to the bean level

Even though tests are passing, my test app is erroring out at runtime.

FYI: #377


InfoView and Spotlight improvements

This PR improves and adds various things, including:

Addition of optional gradient
changed showSpotlight() to goToSpotlight(index: Int) which improves when spotlightView methods are called to improve animations
Improved animation of InfoView appearing and changing, so it is smoother
changed some naming of methods
added none to SpotlightTarget
improved background color animation when appearing
Maybe some other stuff as well

fyi, this breaks the info box


Question: consistency guarantee during the cluster partitioning

Hello here!
Let's assume I have "Record A" saved in DynomiteDB cluster. Now, I got network partitioning, which splits my cluster into two parts: part A (with "Record A" and all replicas) and part B (no replicas of "Record A").
During partitioning, my client application has an access to only part B, thus, the "Record B" is unavailable.
Now, I'm trying to check if "Record A" exists and create if it doesn't exists yet. Aerospike (in AP mode) in this case would perform a master selection and allow me to write a new record. And when the cluster re-join again - it would merge duplicate records. Which is not optimal is my case. See details in this nice article - https://aphyr.com/posts/324-jepsen-aerospike
How would Dynomite behave in this scenario? Is it possible to fail read/write request if there is no quorum of replicas available due to network partitioning? That would be ideal for me.
Thank you in advance!

Yes, in that case part of the data is not available and Dynomite will complain and read/write will fail.

thanks, @shailesh33
Just to double check we are talking about the same thing here. I found the following description of Dyno's behavior in another thread:
>> When a node leaves the cluster (ex. when it fails), the Dyno client will be notified of the failure due to failed health checks and will direct traffic away from the failed node...until it is brought back online.
Does "will direct traffic away from the failed node" means that:
a) Dyno would start using less nodes that configured as replication factor (for instance, I had RF=3, after 1 node went down, Dyno sends requests to 2 nodes only, thus, QUORUM requests would still succeed, but ALL requests would fail)
or
b) Dyno would select different node from available to replace failed node and would keep writing/reading data from 2 old nodes + 1 new node. (by the way, in this case, I wonder if data will be rebalances to newly selected node for keys that were stored on failed node).
Thanks in advance.

option a is correct. However its not dyno which replicates the data, its dynomite server which does it for you. Client do not have to write to multiple nodes, that why you can use any client, even a basic redis-cli to talk to dynomite.

thanks a lot!


Using imencode and Mat.fromList throws error

Question
When trying to use imencode function I keep getting error:
Usage:
imageData is Uint8List representing jpeg image.
final mat = imdecode(imageData, IMREAD_UNCHANGED);
Error:
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Invalid argument(s): Failed to lookup symbol 'VecUChar_NewFromPointer': dlsym(RTLD_DEFAULT, VecUChar_NewFromPointer): symbol not found
Also I've tried to convert Uint8List to Mat using Mat.fromList constructor, but it throws an error as well.
Usage:
final mat = Mat.fromList(height, width, MatType.CV_8UC1, imageData.toList());
Error:
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Invalid argument(s): Failed to lookup symbol 'Mat_NewFromBytes': dlsym(RTLD_DEFAULT, Mat_NewFromBytes): symbol not found
I'm not getting it. Is something wrong with my bytelist or it its something with implementation of those methods?

Looks like your dynamic library is broken, please update to the newest version or run setup manually with -f flag to overwrite the existed library and try again.

It was so easy.. OMG, thank you!

Never mind~


Implement type macros

Need to be careful about compile time, the macro parsing code is not currently compiled in Macros 1.1 mode.

The following test cases depend on type macros:

type-macros-hlist.rs
type-macros-simple.rs
proc_macro.rs

Higher priority now that type macros are stable in Rust 1.13.

Added behind a flag in 0047c71c93ae9902839856b0b48e6fe816579f61.


support a general Go releaser

Is your feature request related to a problem? Please describe.
The current Go release is specific to our client libraries. A general implementation would be nice for the community and other Go repositories found in our org.
Describe the solution you'd like
A new releaser type: go
Additional context
Was recently talking with someone on getting release-please on a new cloud events repo written in Go: https://github.com/googleapis/google-cloudevents-go

Can you describe which files need to be updated?

There are no required files to be updated for a simple project (no pom.xml equivalent that states a version) so I guess just a changelog. I believe the base case for a single module (unit of packaged code) codebase is relatively basic. If we wanted the releaser to support mutil-module projects generically, such as we have with our google-cloud-go, that is where the tricky bits would lie.
I suspect supporting the base case would be good enough for now. Mutil-module projects are quite rare in the ecosystem.

The base ReleasePR class (or an empty Go class that extends ReleasePR to provide a future place for customization) would do this. We would just need to adjust the factories to be able to build that type.


This company RANNED !!!!!!

THIS  company  is    By  Liberals .... For  You  a will see   Why U Think    Its a Good Compay . Your.   Wrong !!!!!!!!    Learn More.......

Spam

Spam


Commit sctruct on events

The commit data from events is a little different from other commit data from API
This is the commit data from PushEvent:
    {
      "id": "da1560886d4f094c3e6c9ef40349f7d38b5d27d7",
      "message": "fixed readme",
      "timestamp": "2012-01-03T23:36:29+02:00",
      "url": "http://example.com/mike/diaspora/commit/da1560886d4f094c3e6c9ef40349f7d38b5d27d7",
      "author": {
        "name": "GitLab dev user",
        "email": "gitlabdev@dv6700.(none)"
      },
      "added": ["CHANGELOG"],
      "modified": ["app/controller/application.rb"],
      "removed": []
    }

And this json is used in other events like:
https://github.com/xanzy/go-gitlab/blob/master/events_test.go#L151
https://github.com/xanzy/go-gitlab/blob/master/events_test.go#L240
Can we use this data in the Commit struct or create another struct?

Hi @leandro-lugaresi I'm afraid I don't understand your question. Could you rephrase and/or explain a bit more what you want to know? Thanks!

Sorry.
The commit data from webhooks have some diffs from Commit struct used by gitlab API.
The struct we are using is https://github.com/xanzy/go-gitlab/blob/master/commits.go#L36 but the json is different for commits from webhooks.

@leandro-lugaresi I understand now. Don't know what the best solution is... Adding the data directly into the structs that need it is probably the most clean. It will prevent having 2 structs that are almost the same with probably also almost the same name. But it then does mean the code (the struct fields) are then duplicated a couple of times...
Still think it is the best solution to just add the fields directly into the event structs that need it...

Closing this issue as the question seems to be answered and no conversation is happening anymore on this topic. Please reopen if you have additional questions/issues.


🐛 BUG: unstable_dev fetch cannot accept query param

Which Cloudflare product(s) does this pertain to?
Wrangler
What version of Wrangler are you using?
2.8.1
What operating system are you using?
Mac
Describe the Bug
Due to the code here:
https://github.com/cloudflare/wrangler2/blob/89d78c0ac444885298ac052b0b3de23b69fb029b/packages/wrangler/src/api/dev.ts#L302-L328
The URL that's passed into fetch for unstable_dev does not handle query params. This obviously causes any test using these to fail.
Repro:
import { writeFile } from 'fs/promises';
import { expect, test } from 'vitest';
import { unstable_dev } from 'wrangler';

test('unstable_dev fetch repro', async () => {
	const script = `
	export default {
		fetch(req) {
			const url = new URL(req.url);
			const name = url.searchParams.get('name');
			return new Response('Hello, ' + name);
		}
	}
	`;
	await writeFile('script.js', script, { encoding: 'utf8' });

	const worker = await unstable_dev('script.js');

	const res = await worker.fetch('http://worker?name=Walshy');

	expect(res.status).toBe(200);

	const text = await res.text();

	expect(text).toBe('Hello, Walshy');

	await worker.stop();
});

Error:
 FAIL  test/repro.test.ts > unstable_dev fetch repro
AssertionError: expected 'Hello, null' to be 'Hello, Walshy' // Object.is equality
 ❯ test/repro.test.ts:25:15
     23|  const text = await res.text();
     24|
     25|  expect(text).toBe('Hello, Walshy');
       |               ^
     26|
     27|  await worker.stop();

  - Expected   "Hello, Walshy"
  + Received   "Hello, null"

A fix I'd suggest is instead just relying on the URL object, something like:
const url = new URL(input);
url.protocol = `${protocol}:`;
url.hostname = readyAddress;
url.port = readyPort;
input = url.toString();

Instead of manually constructing the URL string.

Related/additionally, it doesn't unpack a Request at all if it's passed in, so even changing the path has no effect if you use the template: https://github.com/cloudflare/workers-sdk/blob/6fd062419c6b66c2c5beb7c45ec84a32dfa89e01/templates/worker-typescript/src/index.test.ts#L17
i.e. If you change that to new Request('http://falcon/foo', { method: 'GET' }); your app receives http://ip:port/ as the request.url


A small suggestion, slug is currently limited to lowercase characters, and the error message only says the wrong format, a more precise error message can be given.

A small suggestion, slug is currently limited to lowercase characters, and the error message only says the wrong format, a more precise error message can be given.

As part of the URL, slug can only be lowercase and cannot have spaces.
The prompts here are not very friendly at present, and can be improved later.
In addition, after connecting to AI later, slug should be generated by AI.


Set up DAO Producer Job

Overview
Once our Kubernetes Cluster is set up we can create jobs that run. This job will be used in our Hub App for DAO processing.
Details

Create a job that pushes DAOs to queue to be processed

Query subgraphs for each DAO in the queue
Drops in the DAO address, safe address fields, network (needed to query for token balances)

Deliverables

DAO Producer Job set up in our infrastructure that supports the Hub App data processing needs

Related Issues

#195
#172
#196

Requires Helm

Waiting on this pr to get merged to resolve the esm issues https://github.com/nrwl/nx/pull/10414


Google Analytics

Would it be possible to add a hook for Google Analytics? I pass users from my main Wordpress site to IdeaSpace and then lose track of them.

Yeah, what would you exactly need?

I need a way to add my Google Analytics ID to the website. I could probably hack it into one of the files if I knew where to look but it would be great to just be able to add it from the admin console.
I would suggest that if you were to add this feature that the Google tracking ID could either be entered as a global setting or, and this is probably preferable, for each space separately. That way each space can be tracked individually by Google Analytics.
Here's some more info I found.
https://websitesetup.org/google-analytics-wordpress/


[CARBONDATA-3674] remove Encoding.DICTIONARY and Encoding.DIRECT_DICTIONARY usage

Why is this PR needed?
After Global Dictionary feature is deprecated, we can refactor the Dict/NoDict usage. This PR is one of the effort for this refactory.
What changes were proposed in this PR?
This PR remove Encoding.DICTIONARY and Encoding.DIRECT_DICTIONARY usage in if check. They are changed to check against DataTypes.DATE instead of checking Encoding.
Does this PR introduce any user interface change?
No
Is any new testcase added?
No

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/1824/

Please rebase it.

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/1825/

@jackylk Is compatibility verified?

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.4/3/

@Indhumathi27 I have tested by reading carbon table which written by 1.6.1 branch code

LGTM


Problem with background image

I am not sure if you're still updating this. I installed the theme and my background is not as it should be. What I'm getting is this:

While I should be getting this:

This could be related to the background colour you picked, try disabling the effect to see if it fixes it.
Could you provide your browser + OS so I can troubleshoot the issue please?

This could be related to the background colour you picked, try disabling the effect to see if it fixes it.
Could you provide your browser + OS so I can troubleshoot the issue please?


fix NuGet.Core issue in OptimizedZipPackage

Fix for failing nuget pack when encountering non-compliant OPC packages https://github.com/NuGet/Home/issues/1921

@yishaigalatzer is this one good to go?

cc @emgarten @deepakaravindr


address and address on participants view

We have two "address" on the participant view, I think one is for the address and the other is for the postal code?
Also, we don't have the city name  it's just written "city :"

You're right, the "Address" label should be replaced by "Postcode" in the second instance. The "City" field is empty because there is not data (it is not a mandatory item, so it can be left blank).

[ ] Replace label "Address" with "Postcode"
[ ] Prepend field labels to actual text for easier reading.


unprivileged namespace use - how to disable again

I was shocked to see that there is no Linux wallet yet.
Your beta
https://forum.cardano.org/t/iohk-statement-a-beta-release-for-daedalus-on-linux/10316
when downloaded and started
needs these commands
sysctl -w kernel.unprivileged_userns_clone=1 ; echo kernel.unprivileged_userns_clone=1 > /etc/sysctl.d/nix-user-chroot.conf

2 questions:

is there really no way around this? I have never seen that with any (over a hundred) cryptocurrency ...
how can this be undone afterwards? what is the full command to reverse this decision?

Thanks!

that command can be reversed by setting it to 0 with sysctl and also removing the file /etc/sysctl.d/nix-user-chroot.conf that it creates

that command can be reversed

Thanks a lot.
So, like this:
sysctl -w kernel.unprivileged_userns_clone=0 ; rm /etc/sysctl.d/nix-user-chroot.conf

?
Then please add that to the instructions.
But also ... isn't the second command too harsh? Removing the whole file?
Imagine some other tool has also written to the same file - then your suggestion would destroy that too

Secondly:
is there really no way around this? I have never seen that with any (over a hundred) cryptocurrency ...

the original echo kernel.unprivileged_userns_clone=1 > /etc/sysctl.d/nix-user-chroot.conf command would overwrite the entire file anyways, so no other tools should ever have contents in there


Feature/16272 jupyter examples

Add some example jupyter notebooks
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Tested by running notebooks locally
Test Configuration:

Environment:

Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have made corresponding changes to the architecture
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

To view the notebooks properly, navigate to code view and select the branch. Then click on the notebook files to see it properly rendered.


Default GPIO Button configuration conflicts with reserved GPIO pins

Bug
What I did
I installed the Jukebox on an Raspberry Pi 3 using the Waveshare PN532 NFC HAT over I2C with a Shutdown button.
What happened
After wiring the Shutdown button on the default PINS from gpio_settings.ini, the NFC HAT was going out of work.
I expected this to happen
I expected exactly this because the default configuration uses the I2C data wire at GPIO3 (SCL PC).
Further information that might help
The default gpio_settings.ini should not use GPIO pins which are reserved for protocols like I2C, UART, or SPI.
As you can see in the Pin numbering on the RPi, the green PINs are free to use, others are reserved for something.
Here is my working example that I am currently using:
[PrevNextControl]
enabled : True
type : TwoButtonControl
pin1 : 5
pin2 : 13
functioncall1 : functionCallPlayerPrev
functioncall2 : functionCallPlayerNext
functioncalltwobuttons : None
hold_time : 0.3
pull_up_down : pull_up
hold_mode : None

[PlayPause]
enabled : True
type : Button
pin : 21
hold_time : 0.3
functioncall : functionCallPlayerPause
pull_up_down : pull_up

[Shutdown]
enabled : True
type : Button
pin : 27
hold_time : 2
functioncall : functionCallShutdown
pull_up_down : pull_up

And there are my thoughts on my custom configuration:
I put the Shutdown button on GPIO27 because of the Ground on the opposite and a 3.3V power supply next to it.
I did this because I have a button with an LED light inside where the LED cables have two separate cables and plugs for + and -.
But the on/off toggle is one plug with two cables connected.
Hardware
RaspberryPi version
3 B+
RFID Reader
Waveshare PN532 NFC HAT

Relocating the default pin for the Shutdown button away from GPIO3 is a bad idea, since GPIO3 is the only pin which also allows to power up the pi again from a standby state by later pressing the same button.

@T0bi79 thanks for pointing that out.
From my point of view there is no perfect default configuration, so usually users need to adapt the GPIO pin settings to their individual setup.
Therefor I would close this issue for now as wontfix.
please feel free to open a new issue, if there’s a new problem.


Translation Tool Inserts Extra Quotes(") in the Translation

Describe the bug
I am creating a translation file for the Austria region. The source file is in US English, and the target language is DE-AT. The issue is the translated file contains Double quotes in the translated text which throws run time errors in App functionality.
For Example:

XXX XXX Total XXX Value Details Report
XXX-XXX-Bericht ' XXX Wert Details '
Page xxxx- Action xxxx- Property Caption

We are using Microsoft Dynamics 365 - Translation Service Tool for the translation.
To Reproduce
Steps and to reproduce the behaviour:

Go to https://support.lcs.dynamics.com/
Upload the Source Language file
Set the Target Language to DE-AT
Download the Translated file, You will see it has inserted Double Quotes(") for some of the captions(Mainly reports).
Try to open the Same Report, it will throw an error for illegal Characters.
Note:: This issue is mainly occurring in Reports.

AL Code to reproduce the issue
Expected behavior
There can be two expected behaviours
1.) Either the Translated file should not contain Double quotes.
2.) Or Dynamic 365 should not throw an error for Double(") Quotes in the Captions.
Screenshots
If applicable, add screenshots to help explain your problem.

5. Versions:

AL Language: v6.1.352568

Business Central: US Business Central 16.3 (Platform 16.0.14073.16910 + Application 16.3.14085.17081)

Hi! Please take a minute to read the guidelines for this repository https://github.com/microsoft/AL and our collection of frequently asked questions https://github.com/Microsoft/AL/wiki/frequently-Asked-Questions .
As this repository is only for issues related to the AL compiler in latest developer preview environment for Dynamics 365 Business Central. We suggest that you open a support case or file a bug in Collaborate, to ensure that all Business Central users benefit from your catch as soon as possible.
To open a support case, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using.


Tap while already scrolling the content shouldn't trigger the tap/click on an element in the content at all.

Ionic version:  (check one with "x")
[ ] 1.x
[x] 2.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

Expected behavior:

Steps to reproduce:

Related code:
insert any relevant code here

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
insert the output from ionic info here

Hello, thanks for using Ionic! Could you please add the info requested in the issue template?

I guess this is related to my issue from over 2 weeks ago. https://github.com/driftyco/ionic/issues/9945

Hello, thanks for the heads up @AndreasGassmann ! I am going to close this issue as a duplicate of #9945 .


Option to ignore any errors in rule(s)

In some cases, I would see it beneficial if you could provide Yara with an option or parameter to ignore any errors in any rule(s), in which Yara would simply skip that rule as a whole and continue with the rest.
Obviously, it would be explicitly stated what this parameter would do, as it's not exactly the best thing to do, but in some cases it'd be of help.

+1


fix(keymaps): update next and previous header keybindings

Description
Updated the keybindings for navigating to the next and previous headers from ] to ]] and from [ to [[ respectively in both the README and configuration files.
It's pretty common to use [ and ] as first char in Vim/Neovim motion keymaps. So the editor usually pause for a couple of milliseconds before process [ and ] as standalone motion.
Checklist

[x] I've read the CONTRIBUTING guidelines.

Great spot! Thank you


Get/detect declared methods in eval()d script

Example use case:
Interpreter i = new Interpreter();
i.eval("void run() {}");
Runnable r = i.getInterface(Runnable.class);
r.run();
// throws java.lang.reflect.UndeclaredThrowableException
It would be nice to know if a script supported an
interface or not.  E.g. APIs like this:
i.hasMethod("run");
i.hasMethod("run", new Class[] { ... });
And this would be nice too:
i.invoke("run", new Object[] {}, new Class[] {});
And this would be good if a script only implements some
methods:
// See http://en.wikipedia.org/wiki/Duck_typing
i.noopUndeclaredMethods(true);
What can happen:
i.eval("void run() { throw new RuntimeException() }");
Runnable r = i.getInterface(Runnable.class);
r.run();
Compare to:
i.eval(" /* nothing */ ");
Runnable r = i.getInterface(Runnable.class);
r.run();
It would be better to throw
OperationNotSupportedException or something different,
since both cases throw very similiar exceptions.
Reported by: genman
Original Ticket: "beanshell/feature-requests/14":https://sourceforge.net/p/beanshell/feature-requests/14

TBD


Fix domain_id, registrar and contact parsing for afilias

Afilias has changed there whois format in accordance with ICANNs requirements. This is a try at updating to parse the new format.

Thanks for all the patches @cork. I'll schedule some time this week to review and merge them.

@weppos this PR helps to fix issue https://github.com/weppos/whois-parser/issues/99

For the record I ended up starting my fork in which I fixed all the Afilias based whois parsers (.ME, .ORG, .INFO, .PRO, .BZ, .GI, .LC, .MN, .SC, .VC, .AG, .IN, .AERO, .ASIA, .MOBI, .POST, .XXX) in e2b84e73f43ef692e834c2d151f5c7e50b384eae. So people who need this can use my fork:
gem 'whois-parser', github: 'jarthod/whois-parser' # Unofficial but more up-to-date fork, check status at https://github.com/jarthod/whois-parser


Fix Typos in Italian CONTRIBUTING.md

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@elenaramon Translation corrections look good, thanks. But someone else merged another PR first that conflicts with this. Could you resolve the merge conflict please? Thanks.


pyftinstance?

There is pyftsubset and pyftmerge... should there be a pyftinstance?

Because we want to avoid having too many scripts installed and prefer that all future console entry points are sub commands of the fonttools main CLI.

At least, that was my preference, open to discuss and change my mind

Because we want to avoid having too many scripts installed and prefer that all future console entry points are sub commands of the fonttools main CLI.

Agreed. pyftsubset / pyftmerge / ttx are grandfathered.


New App Submission - Defii Wallet

App Logo

App Details (Required)
Type: Wallet
Name: Defii
Homepage Url: https://defii.app/
Chains supported: Ethereum , Binance Smart Chain .
App Url (Required - at least one)
Browser Url:
iOS Url: https://apps.apple.com/vn/app/defii/id1561955575
Android Url: https://play.google.com/store/apps/details?id=io.defii
Mac Url:
Windows Url:
Linux Url:
Mobile Linking (Optional)
Deep Link: defii://
Universal Link: https://defii.app/
Desktop Linking (Optional)
Deep Link:
Universal Link:
Metadata (Optional)
Short Name: Defii
Primary Color: #FCB751
Secondary Color: #E84615

@pedrouid

Is the app still maintained?

Added on commit a4a23c37fb09fb182d5c5c21727d2890e2820cc1


Redirect H2Connection.writeLoop errors to logger

Fixes https://github.com/http4s/http4s/issues/7014.

Good question. We need a way to simulate a write failure in the tests, let me take a look at that.

Sorry, I'm going to land the fix and flake on the test. 🥺


Serializers error: 'FileField' object has no attribute 'max_length'

Looks like mongoengine's FileField doesn't have this attribute. So are EmailField and URLField. This is needed for DRF's FileInput widget though. (ref line 340-342 in serializers.py)

Thanks for heads up, will try to resolve it this weekend

Still experiencing this on 2.0.2/3

Looks like it just needs https://github.com/umutbozkurt/django-rest-framework-mongoengine/blob/master/rest_framework_mongoengine/serializers.py#L351 removed

should not bean issue in last release.


Running on Travis

I can't seem to figure out a nice way to just use hihat to run tape tests on Travis. How are people doing this sort of thing?

Using tape-run works, but I really don't want to add more modules just to run it in CI:
browserify test/index.js -t babelify | tape-run

Plus this in .travis.yml
addons:
  apt:
    packages:
      - xvfb
install:
  - export DISPLAY=':99.0'
  - Xvfb :99 -screen 0 1024x768x24 > /dev/null 2>&1 &
  - npm install

Hmm, I haven't tested CI yet since mainly I am using hihat for local prototyping/development/debugging. I have tinkered a little with testling and smokestack in the past, which are better suited for CI and also generally lighter since they don't need Electron.
Lately I've been moving away from using hihat and similar Electron-based tools as local dependencies, since the module size is really significant and it gets annoying across many modules... Sucky. :disappointed:
But, it should probably be possible to get hihat working on the server with some tinkering. :smile: Make sure to use the --exec flag. I think one thing that might still be a problem is exit codes; for tools like ava we would need to shim process.exit properly so that the server exits with the right code.


feat: for Pwa Side bar Menu draggable &/or button to manually hide

Feature Request
Ionic version:

[x] 5.x
Describe the Feature Request

For Pwa Side bar Menu have the possibility of a draggable &/or button to manually hide de sidebar Menu
Additional Context

In situations like this
https://github.com/MInesGomes/Ionic-Sidebar-Suggestion/blob/master/sidebar.gif
It would be nice the user be able to hide manually the sidebar or change the size manually
Describe Preferred Solution

Have a button like this to hide manually the side bar or/and change the size manually
https://github.com/MInesGomes/Ionic-Sidebar-Suggestion/blob/master/sidebarHide.png

Thanks for the issue. Can you please clarify your feature request?
You can hide the side menu by setting the disabled property on ion-split-pane to true: https://ionicframework.com/docs/api/split-pane#properties.
In addition, you can change the size of the side menu by setting the --width CSS variable: https://ionicframework.com/docs/api/menu#css-custom-properties

Thanks @liamdebeasi for the css properties.
The suggestion I am making is to let the user change dynamically the menu:
When the mouse is in the border, changes to draggable

and when pressed can drag to change the size.
Something like this do drag:
https://github.com/MInesGomes/Ionic-Sidebar-Suggestion/blob/master/menuHidding.gif
And to hide the menu maybe in the borders button like:

And after clicked, the menu is hidden, but the button is not hidden, so the user is able to 'unhide' the menu

Thanks for the follow up. I discussed this feature request with the team, and while we definitely agree this is a useful feature, we feel this is better implemented on a per-app basis.
I made a CodePen that shows how you can implement this in your own application: https://codepen.io/liamdebeasi/pen/KKdodjd
The code that is responsible for updating the sizing of the menu uses the gesture utility that Ionic exposes: https://ionicframework.com/docs/utilities/gestures
Hope this helps!

Thank you @liamdebeasi . Really nice!