[libra framework] Separate freezing out into separate module, add freezing to VASPs

This pulls account freezing out into its own module. The idea being that this module provides the "atomic semantics" of what it means for an account to be frozen. Other modules (e.g., VASP) can then use these semantics to provide a more semantically rich version of "freezing" e.g., if the parent account is frozen all of the child accounts are frozen, but if the child account is frozen then only that account is viewed as frozen.
Additionally, the libra root account, and TC account cannot be frozen. This is ensured in the AccountFreezing module
Won't land until all spec changes have passed.

instead of removing is_frozen attribute, can you add logic to implement that in the view ? Otherwise we would need an new API for it again.

Shouldn't be an issue to implement in the view. I'll update.

Looks great to me from the Move perspective! The only thing I'm wondering is whether moving the freeze/unfreeze events to a new module is going to create churn for AOS (@moeziniaf?)

Thanks! I believe we're just tailing the chain for Preburn events right now so doesn't seem to be an issue from our end

:umbrella: The latest upstream changes (presumably e3710c1e0681189206a0f6ca5ec0415bb81e20dd) made this pull request unmergeable. Please resolve the merge conflicts.

@bors-libra r=sblackshear

:pushpin: Commit 636f59d has been approved by sblackshear

:hourglass: Testing commit 636f59db64867c2e3a8548e7a64fa6b7bf33da9f with merge 03f7efebec1928b50dff1c5ea338c6f99366ca6e...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: sblackshear
Pushing 03f7efebec1928b50dff1c5ea338c6f99366ca6e to master...


Search configMap with active profile name.

Based on #153 this pull request will search and fetch configMap names with active profiles.
fixes gh-153

This looks good to me, thanks @shahbour!
@salaboy @spencergibb @ryanjbaxter WDYT?

Can you rebase on the 1.0.x branch so we can get this in Greenwich.

Can you rebase on the 1.0.x branch so we can get this in Greenwich.

You are asking me to do that?

@shahbour yes if you submit against the 1.0.x branch we can then merge it forward into master

I did change the request to be into spring-cloud:1.0.x


Advance pos_of_buffer_start when writing directly to a writer

If a message is bigger than the buffer, it will be written directly to the writer, and there was a bug in that case where pos_of_buffer_start was not advanced. This causes later assertions to fail, such as the one in
Message::write_length_delimited_to, which asserts based on total_bytes_written(), which is in turn based on
pos_of_buffer_start.

Can you please add a test reproducing the issue?

I couldn't really figure out rust-protobuf's test setup (I couldn't find any documentation either), but I did make a minimal reproduction here: https://github.com/Colecf/rust-protobuf-assertion-failure-reproduction

rust-protobuf's test setup

Well, it is not easy. Basically, you create two files in
test-crates/protobuf-codegen-protoc-test/src/common/v2/test_xxx_pb.proto
test-crates/protobuf-codegen-protoc-test/src/common/v2/test_xxx.rs

And run cargo test. That will copy these files into three places (v3; v2/v2 with pure codegen).
Alternatively, maybe you can write a simple unit test using CodedOutputStream calls?

Alternatively, maybe you can write a simple unit test using CodedOutputStream calls?

Ah good point, I added a unit test.

Thanks!


🤖 OpenSumi Pre-Release 2.21.11-next

2.21.11-next Pre-Release Summary
7d0f2e91fca38bdf8384c0cefb74ce45d0755f54

28 December 2022

🎉 New Features

实现 TestController.refreshHandler API #1865 by @Ricbet

支持插件注册字体图标 #1880 by @Aaaaash

improve file search results order #1895 by @erha19

trigger editor find widget when no actived element #1980 by @Aaaaash

support detect configuration change from the parent directory #1976 by @erha19

support base64 icon on editor glyphMargin and treeview #2010 by @erha19

修复暂停调试时不会自动打开第一个堆栈源文件的问题 #2028 by @Ricbet

support submenus on editor/title #2088 by @erha19

optimize editor updateContent logic #2097 by @life2015

support space keybinding on filetree #2119 by @erha19

improve file search path on workspace folders #2129 by @erha19

enable editor minimap by default #2127 by @Aaaaash

🐛 Bug Fixes

调整 monaco 代码，使代码片段 prefix 属性支持数组 #1891 by @shilin8805

just progress codeAction when codeActionOnSave existed #2027 by @erha19

Fix invoke ExtensionContext.globalStoragePath error in Windows #2068 by @bytemain

unnecessary re-tokenizer #2125 by @Aaaaash

partial update view #2128 by @erha19

disable some keybindings on filetree filter mode #2132 by @erha19

duplicate search results #2123 by @erha19

💄 Style Changes

improve debug toolbar z-index style #1965 by @erha19

improve SCM delete decoration style #1963 by @erha19

improve image preview editor style #2020 by @Aaaaash

improve empty editor component style #2121 by @erha19

🪚 Refactors

remove package vscode-languageserver-protocol #1988 by @yantze

progressbar component #2114 by @Aaaaash

🚀 Performance Improvements

create output editor when panel is visible #2105 by @Aaaaash

create debug console editor when panel visible #2106 by @Aaaaash

⏱ Tests

add layout e2e test #2044 by @erha19

🧹 Chores

use bash resolve shell path by default #2021 by @Aaaaash

update defualt theme #2087 by @Aaaaash

/pre-release

/pre-release

主链路测试已全部覆盖 https://github.com/opensumi/core/discussions/1475，后续常见问题使用 E2E 案例方式保障可用性。


[Docs]: AWS ECS Fargate

Is there an existing issue for this?

[X] I have searched the existing issues

Documentation Link
https://docs.appsmith.com/getting-started/setup/installation-guides/aws-ecs-on-fargate
Discord/slack/intercom Link
No response
Describe the problem and improvement.
Update to remove the classic AWS console, and move the external MongoDB prerequisite to the top of the list.

@sharat87 - For your information.


Fix leaked storage classes in tier 1 storage tests

What this PR does
Before this PR: Some storage tier 1 tests would create storage classes and never remove them
After this PR: No storage classes are leaked from tests

Fixes CNV-38887
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:  CNV-38887
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

NONE

/test pull-kubevirt-e2e-k8s-1.29-sig-storage pull-kubevirt-e2e-k8s-1.28-sig-storage pull-kubevirt-e2e-k8s-1.27-sig-storage

/test pull-kubevirt-e2e-k8s-1.29-sig-storage pull-kubevirt-e2e-k8s-1.28-sig-storage pull-kubevirt-e2e-k8s-1.27-sig-storage

/test pull-kubevirt-e2e-k8s-1.29-sig-storage pull-kubevirt-e2e-k8s-1.28-sig-storage pull-kubevirt-e2e-k8s-1.27-sig-storage

/lgtm

/cherrypick release-1.2


Suggestion: RuneWatch & WDR pull ability

Would be awesome if this bot had the ability to do !rw @username or !wdr @username to check if the player has been reported for scamming, et cetera.

Is there a decent API to use for this?

I believe so, yes. Not 100% what it is but Twisty Bot uses it and I would
prefer to just have your bot than both ;)
On Tue, Jul 21, 2020 at 3:57 PM Jakesterwars<EMAIL_ADDRESS>wrote:

Is there a decent API to use for this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wise-old-man/wise-old-man/issues/337#issuecomment-662102209,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMBCWFRP2ZDLZUX6M3WZ2ELR4X6K3ANCNFSM4PEBI5WA
.

--
Mr. Kyle T. Hillman
Email<EMAIL_ADDRESS>Mobile:<PHONE_NUMBER>

Yeah I was looking at RuneLites plugin hub for their plugin for Runewatch and seemed to just use the url to look for a case with the username. Seems pretty simple enough.

Sort of like appending user args to a google command, right? Or like the
OSRS stats grabbing command. Not 100% sure. Just thought it may give your
awesome bot an advantage, since only shitty bots seem to have, and thus,
creates the need for two bots.
I’m not sure if there’s two different APIs for Runewatch and one WeDoRaids,
though.
On Tue, Jul 21, 2020 at 11:10 PM Jakesterwars<EMAIL_ADDRESS>wrote:

Yeah I was looking at RuneLites plugin hub for their plugin for Runewatch
and seemed to just use the url to look for a case with the username. Seems
pretty simple enough.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wise-old-man/wise-old-man/issues/337#issuecomment-662230046,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMBCWFULELVJ535ZKIWXXPLR4ZRC5ANCNFSM4PEBI5WA
.

--
Mr. Kyle T. Hillman
Email<EMAIL_ADDRESS>Mobile:<PHONE_NUMBER>

Any update?
On Tue, Jul 21, 2020 at 11:15 PM Kyle Hillman<EMAIL_ADDRESS>wrote:

Sort of like appending user args to a google command, right? Or like the
OSRS stats grabbing command. Not 100% sure. Just thought it may give your
awesome bot an advantage, since only shitty bots seem to have, and thus,
creates the need for two bots.
I’m not sure if there’s two different APIs for Runewatch and one
WeDoRaids, though.
On Tue, Jul 21, 2020 at 11:10 PM Jakesterwars<EMAIL_ADDRESS>wrote:

Yeah I was looking at RuneLites plugin hub for their plugin for Runewatch
and seemed to just use the url to look for a case with the username. Seems
pretty simple enough.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wise-old-man/wise-old-man/issues/337#issuecomment-662230046,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMBCWFULELVJ535ZKIWXXPLR4ZRC5ANCNFSM4PEBI5WA
.

--
Mr. Kyle T. Hillman
Email<EMAIL_ADDRESS>Mobile:<PHONE_NUMBER>

--
Mr. Kyle T. Hillman
Email<EMAIL_ADDRESS>Mobile:<PHONE_NUMBER>

I don't think this feature is within the scope of this project, as it mainly focuses on player progression.

But it checks stats and prices, etc? Wouldn’t it be a valuable asset to
check if a player is a scammer to? In turn, to help the player who is
checking progress (without being scammed)?
On Tue, Jul 28, 2020 at 6:39 PM Ruben Amendoeira<EMAIL_ADDRESS>wrote:

I don't think this feature is within the scope of this project, as it
mainly focuses on player progression.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wise-old-man/wise-old-man/issues/337#issuecomment-665348434,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMBCWFXOQJUB4RK32AAGSFDR55OSNANCNFSM4PEBI5WA
.

--
Mr. Kyle T. Hillman
Email<EMAIL_ADDRESS>Mobile:<PHONE_NUMBER>

It doesn't do anything with prices. Only hiscores (stats)

Oh darn okie :(
On Tue, Jul 28, 2020 at 6:58 PM Ruben Amendoeira<EMAIL_ADDRESS>wrote:

It doesn't do anything with prices. Only hiscores (stats)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wise-old-man/wise-old-man/issues/337#issuecomment-665353562,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMBCWFXPSGFGK5GTZJKV4H3R55Q33ANCNFSM4PEBI5WA
.

--
Mr. Kyle T. Hillman
Email<EMAIL_ADDRESS>Mobile:<PHONE_NUMBER>

Sorry buddy, I appreciate the suggestion tho! Closing this issue.


build: update major and minor tags update publishing

This PR adds a Github action to update tags automatically after publishing a new release. Validated in this job run.

Also, we need to allow actions to have write access to this repo, I am not sure if it's enabled because I don’t have access to check.

Also, we need to allow actions to have write access to this repo, I am not sure if it's enabled because I don’t have access to check.

Write permission is checked.

note: this PR is inspired by https://github.com/notaryproject/notation-action/pull/41


Kubescape Operator - Controls that require visibility of the nodes are missing in report (e.g., Worker Configuration Files and Kubelet) for CIS framework

Description
Deployed the Kubescape operator Helm chart with all capabilities enabled in the Helm values.yaml, including nodeScan variable for GKE. However, no related controls checks for Worker Configuration Files and Kubelet were found in the workload reports indicating host scans was not possible/configured?
However, Using the CLI with --enable-host-scan scans all controls with no Action Required * in the output and successfully provides all findings. I understand this is now deprecated so I would like to know how to make this work using the operator.
Environment

OS: Windows
Kubescape Version: v3.0.18

Steps To Reproduce

Install the Kubescape operator with the following command:helm upgrade --install kubescape /helm-charts/charts/kubescape-operator \
  -n kubescape --create-namespace \
  --set clusterName=$(kubectl config current-context) \
  -f values.yaml

NB: Enable all capabilities in the Helm values.yaml, including nodeScan.
Expected behavior

Host-related controls (e.g., Worker Configuration Files and Kubelet) should appear in the reports generated by the operator when all capabilities, including nodeScan, are enabled.

Can you filter to scan for only the framework cis-v1.23-t1.0.1 in the operator?

Actual Behavior
No host-related controls are included in the reports when using the operator.
Running the CLI with --enable-host-scan does successfully include these findings.
Additional context
kubescape scan framework cis-v1.23-t1.0.1 --enable-host-scan --use-from regolibrary/offline/cis-v1.23-t1.0.1.json --verbose --controls-config regolibrary/controls-inputs.json
This command scans all controls, including host-related ones, because of the --enable-host-scan flag. However, this feature is deprecated, and findings are expected to be included in the operator's reports without relying on the CLI.

good catch, thanks

@matthyx Can you confirm the following?

Timeline to resolve this bug?
What frameworks are scanned by default by the operator?
How to set the default framework used by the operator for GKE environment to cis-v1.23-t1.0.1 and cis-aks-t1.2.0 for AKS.

Hi @AdonisOkpidi, as for the host scan missing controls (point 1), in the initial scan of the operator it is not enabled, but for the recurring scans.
As for the point 2, in the initial scan it scans for "allcontrols", "nsa" and "mitre" frameworks and at recurring scans it scans all FWs.
As for point 3, one can tweak the configmap named "kubescape-scheduler" to something like the following  (an example could be found here) to scan only specific framework(s).
{
    "commands": [
        {
            "CommandName": "kubescapeScan",
            "args": {
                "scanV1": {
                    "targetType": "framework",
                    "targetNames": [
                        "cis-v1.23-t1.0.1"
                    ]
                }
            }
        }
    ]
}

Please let us know if you have any other questions.


Move Python bindings to its own repo

Python bindings moved here: https://github.com/spruceid/didkit-python
Published yesterday, following #269: https://pypi.org/project/didkit/0.3.0/


drivers: pwm: generate pwm with nxp flexio IP

This pwm driver can be used for both mcux and S32 SoCs which have the flexio IP.
The requested pwm channels from dt are automatically allocated by the flexio misc driver based on the timers available.

LGTM, just minor nits. @sumitbatra-nxp was this patch tested with any pwm test/sample?

Both pwm loopback (just that I commented out the capture) and pwm api (where I made it to use both  pwm-0 and pwm-1 alias

@sumitbatra-nxp, please address the CI failures, merge conflicts, and reviewer comments so we can close on this PR

@sumitbatra-nxp I updated your west.yml to align with the merging of the HAL side

@henrikbrixandersen did @sumitbatra-nxp address your change request?

@henrikbrixandersen did @sumitbatra-nxp address your change request?


Native binding 1.8

Release Note
NONE

@christophd Is the fix already backported? The test is still failing on my localhost.

@bouskaJ this is the backport PR - it has not been merged yet. CCI jobs are failing

Please rebase to see if the test is passing now.


add secure routes for riders and matches admin queries

@dmilet nothing fundamentally new here, just adding two secure routes (for riders and matches) to provide that info to the front-end operators page

@dmilet great, thanks 👍 I'll merge and deploy shortly


Feature: Support for custom path in Path particles

Provide support for custom path functions for Path particles, in two ways

within extraData.path = function(x) { return x*x; } or
__emitter__.pathFunction = function(x) { return x*x; }

Also, these custom path functions can control either only y, or both {x, y} values, which opens up a lot of options that allows particles to move in both x- and y-axis, against previously where we could calculate only y value.
These path functions can be changed at run-time.
@andrewstart, For more details, please check following newly added examples:

bubbleStreamCustomPath.html
bubbleStream2DPath.html

Sorry, the email for this slipped past me and just recently saw it. I like making PathParticle able to handle function inputs as well as point outputs from path functions. I'm not a fan of making Emitter know about specifics of non-basic particle types. Modifying the function for an emitter's particles globally could still be done by having the provided function branch internally:
let mode = 0;
function pathFunction(movement) {
    switch (mode) {
        case 0:
            return bloop(movement);
        case 1:
            return blip(movement);
    }
}
function bloop(movement) {
    // some stuff
}
function blip(movement) {
    // different stuff
}

Sorry, the email for this slipped past me and just recently saw it.

No issue, man. Thanks for your prompt reply though.

I'm not a fan of making Emitter know about specifics of non-basic particle types.

I understand, but presently there isn't any way to control a Particle class' config during run-time, except for changing particleConstructor getter/setter which will trigger init(). I didn't wanted to make a lot of changes.

Modifying the function for an emitter's particles globally could still be done by having the provided function branch internally:
let mode = 0;
function pathFunction(movement) {
    switch (mode) {
        case 0:
            return bloop(movement);
        case 1:
            return blip(movement);
    }
}
function bloop(movement) {
    // some stuff
}
function blip(movement) {
    // different stuff
}

The same with this one. Cannot change during run-time. Run-time modification will be a nice feature to have, as I've done in given examples. However, I'm open to suggestions.

After getting some better sleep, I see now that my "example" was completely unrelated to what you are actually doing, sorry about that (if you ever wanted to change the path of all living & future particles at once, that is how I would do it).
My suggestion would be to subclass Emitter in your project to make a PathEmitter, which would also allow you to enforce the usage of the PathParticle constructor without needing to pass it in for each emitter.
Also, I don't see any reason why we couldn't have a reset parameter to init() that defaults to true - that would allow someone to put in a whole new config while letting living particles die out if they wanted to. So long as particleConstructor isn't changed, then particle recycling is completely safe. To make it even simpler, we could also add a replaceConfig(config) method that calls this.init(this._origArt, config, false).

My suggestion would be to subclass Emitter in your project to make a PathEmitter, which would also allow you to enforce the usage of the PathParticle constructor without needing to pass it in for each emitter.
Also, I don't see any reason why we couldn't have a reset parameter to init() that defaults to true - that would allow someone to put in a whole new config while letting living particles die out if they wanted to. So long as particleConstructor isn't changed, then particle recycling is completely safe.

Quite a modular approach. But as I said, I didn't wanted to make a lot of changes in the main flow.

To make it even simpler, we could also add a replaceConfig(config) method that calls this.init(this._origArt, config, false).

It will be a nice addition. Will make a simple PR later. :-)

Finally made the modular approach in release 5.0.0, and as part of that you can supply a function directly.


Randomize top level tests

Add override to specs to allow random, on order or default.

Added to Spec's and ProjectConfig.


ld: symbol(s) not found for architecture arm64: Please Help!

SDK/Library version: 5.4.1
iOS, XCode 8
Integration type and version: CocoaPods 1.21

We have been having a major issue when trying to get our app to build as part of our CI process. The process has been failing on our MacInCloud instance with the following message;
Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_CardIOPaymentViewController", referenced from:
      objc-class-ref in PaymentMethodViewController.o
  "_OBJC_CLASS_$_CardIOUtilities", referenced from:
      objc-class-ref in PaymentMethodViewController.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

What makes the problem worse is that it's not consistent. It works on our vendors local machines but our internal developers can't get it to run. To that last point; on my Mac trying to do a local build, I get a mach-o linker error with the cardio SDK. However, the vendors developers have not seen this issue.
We have tried reinstalling the pods files, clearing the pod cache, without any luck.
Another clue; At one point we removed the pods from source control and added pod install to our build steps. Which resulted in the following error message and the pod was not imported at all;
Unable to read the license file /Users/vstsagent/agent1/_work/4/s/Pods/CardIO/LICENSE.md for the spec CardIO (5.4.1)
I think the issue is something in how cardio has been implemented into the project itself, that when any updates are made (like changing the provisioning profiles) it changes something so that cardio is no longer linked properly.
We are at a loss and any help would be greatly appreciated. The app is being maintained by a third party on our behalf. I'm a .NET developer and what I have learned about iOS and XCode8 has been over the course of the past few weeks trying to get this to work.

I doubt anyone will reply anytime soon, so I wanted to let you know that I could NOT get the cocoa pod version of this project to work in Xcode 8 nor 9 beta.  I simply could not get it to compile as part of a static/dynamic library no matter what I tried.  I think there is something messed up with the code that prevents it from being part of a larger pod library.
So thus instead, I did the non-pod installation inside of my main project, and I now have it working.  Let me know if I can help.

Hi, how did you do the non-pod installation i am still getting the arm64  error!

I pretty much followed the 'if you don't use cocoapods' section from their sdk page: https://github.com/card-io/card.io-iOS-SDK

I ran into exactly the same issue using XCode 9 after following the 'if you don't use cocoapods' instructions. I fixed it by adding the .a files from SDK as "Linked Frameworks and Libraries"


Disabling exact match and automatic sorting

There might be a common case to disable displaying only exact matches and removing auto-sorting (sorting before I'm passing the list to awesomplete).
I think the library should have a feature to disable both of these functionalities.

Can't you simply override the filter and sort methods to be essentially non-functional?

Can you give an example? Would have thought the below would return the given array but is still sorting it by some logic.
this.awesomplete = new Awesomplete(this.searchEl, {
	sort: () => 0
});

Unfortunately making sort non-functional for an array of objects is not quite possible:

If compareFunction(a, b) returns 0, leave a and b unchanged with respect to each other, but sorted with respect to all different elements. Note: the ECMAscript standard does not guarantee this behaviour, and thus not all browsers (e.g. Mozilla versions dating back to at least 2003) respect this.`

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort

Related #16771 and Lea's comment https://github.com/LeaVerou/awesomplete/pull/16771#issuecomment-159978615

There is a way around this bug -- add a key to your object that indicates sorting order and sort on it.

For what it's worth, if you comment out .sort(this.sort) (which should be around line 239) then sorting is disabled.

For people that can't wait till 1.1.2 is released:
aMyArray = ['a', 'aa', 'abc'];
this.Awesomplete = new Awesomplete(input, {
list: aMyArray,
autoFirst: true,
minChars: 0,
maxItems: 999,
sort: (a, b) => {
return aMyArray.indexOf(a.label) < aMyArray.indexOf(b.label) ? -1 : 1;
}
});


Let's use a joint conda environment

[ ] Make a joint conda environment for everyone to use with all the important packages installed

I already copied the py37_pytorch environment and added xarray, cartopy, netcdf4 and that seems to work well so far.
Now I just need to do that with sudo permissions, I assume so that everyone can access it.

Absolutely agree. Most importantly, we should maintain a environment.yml file in the repo so we can quickly recreate out conda environment if we move to a new machine.
Is there a way to make our new conda environment the default when logging into the shell? Might have to happen in the jupyterhub settings.

I just set up a new VM with a GPU but would have to do all of the setup I did for the first VM manually. Maybe we should think about a way to semi-automate these processes, like creating a joint conda env, mounting the hard-drive (have to do that every time you restart the VM).

I just set up a new VM with a GPU but would have to do all of the setup I did for the first VM manually. Maybe we should think about a way to semi-automate these processes, like creating a joint conda env, mounting the hard-drive (have to do that every time you restart the VM).

I created an environment called nwp-downscale from the root account. However, now it's a little dump to install packages because you have to be the root user. So you need to log into the nwp-downscale account and install the packages. I think we should somehow give all users permission to do this but I am tired right now :D

I created an environment called nwp-downscale from the root account. However, now it's a little dump to install packages because you have to be the root user. So you need to log into the nwp-downscale account and install the packages. I think we should somehow give all users permission to do this but I am tired right now :D

@raspstephan Does cartopy work for you with the environment? For me it doesn't (some matplotlib deprecation error), and I have no clue what the problem is exactly. I would assume some dependencies are wrong. Maybe I'll spend some time figuring it out later, but for now I just use regular plots, no maps.

@raspstephan Does cartopy work for you with the environment? For me it doesn't (some matplotlib deprecation error), and I have no clue what the problem is exactly. I would assume some dependencies are wrong. Maybe I'll spend some time figuring it out later, but for now I just use regular plots, no maps.

I think I also had some issues. I am so annoyed by conda and packages at the moment. See #20
I was so annoyed I stopped working on it for a couple of days...

I think I also had some issues. I am so annoyed by conda and packages at the moment. See #20
I was so annoyed I stopped working on it for a couple of days...

I will close this for now since our current "solution" seems to work at the moment even if it's not pretty.


⚠ AGEG website (redirect) has degraded performance

In db4d869, AGEG website (redirect) (https://ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 2852 ms

Resolved: AGEG website (redirect) performance has improved in e2ca329.


Checkbox component does not make use of color prop

What package has an issue
@svelteuidev/core
A clear and concise description of what the bug is
The checkbox component appears gray no matter what color is specified
In which browser(s) did the problem occur?
Microsoft Edge
Steps To Reproduce
<Checkbox color="blue" size="lg">
	<Icon />
</Checkbox>

Do you know how to fix the issue
No
Are you willing to participate in fixing this issue and create a pull request with the fix
No
Relevant Assets
No response

Fixed in the new patch 0.12.1


Plasma 6 support

I have just upgraded to plasma 6.0.1 on endeavourOs and this is showing as a "not supported widget" on both x11 and wayland session. Just wanted to let you know about it. Let me know if you need any testing done.
Thanks

Can you please update it here? https://store.kde.org/p/2015475

Is already updated, however you must manually uninstall the widget and reinstall the Plasma 6 version: https://store.kde.org/p/2114471/.
I will update the Plasma 5 widget directly in the kde store as this would break all existing installations of this widget in Plasma 5.

It installs, but it doesn't detect the monitors. The list is empty.

Possibly because of https://github.com/davidhi7/ddcci-plasmoid/issues/73. Check ddcutil detect output for errors.

This is what I get
ddcutil detect
(i2c_open_bus                  )           busno=3, flock() returned: EAGAIN(-11): Resource temporarily unavailable
/dev/i2c-3 locked.  Retrying...
(i2c_open_bus                  )           busno=3, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=3, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=3, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=3, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=3, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=3, flock() returned: EAGAIN(-11): Resource temporarily unavailable
Max wait exceeded for /dev/i2c-3
Programs holding /dev/i2c-3 open:
   COMMAND  PID  USER FD   TYPE DEVICE SIZE/OFF NODE NAME
   ddcutil 9954 kalzi 3u   CHR   89,3      0t0  977 /dev/i2c-3
   sh      9968 kalzi 3u   CHR   89,3      0t0  977 /dev/i2c-3
   COMMAND  PID  USER FD   TYPE DEVICE SIZE/OFF NODE NAME
   ddcutil 9954 kalzi 3u   CHR   89,3      0t0  977 /dev/i2c-3
   sh      9971 kalzi 3u   CHR   89,3      0t0  977 /dev/i2c-3
Processes locking /dev/i2c-3 (inode 977):
   1372
      1372
   egrep: warning: egrep is obsolescent; using grep -E
   Name:        org_kde_powerde
   State:       S (sleeping)
   Pid: 1372
   egrep: warning: egrep is obsolescent; using grep -E
   Name:        org_kde_powerde
   State:       S (sleeping)
   Pid: 1372

(i2c_open_bus                  )           Cross instance locking failed
(i2c_open_bus                  )           busno=7, flock() returned: EAGAIN(-11): Resource temporarily unavailable
/dev/i2c-7 locked.  Retrying...
(i2c_open_bus                  )           busno=7, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=7, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=7, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=7, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=7, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=7, flock() returned: EAGAIN(-11): Resource temporarily unavailable
Max wait exceeded for /dev/i2c-7
Programs holding /dev/i2c-7 open:
   COMMAND  PID  USER FD   TYPE DEVICE SIZE/OFF NODE NAME
   ddcutil 9954 kalzi 3u   CHR   89,7      0t0 1017 /dev/i2c-7
   sh      9996 kalzi 3u   CHR   89,7      0t0 1017 /dev/i2c-7
   COMMAND  PID  USER FD   TYPE DEVICE SIZE/OFF NODE NAME
   ddcutil 9954 kalzi 3u   CHR   89,7      0t0 1017 /dev/i2c-7
   sh      9999 kalzi 3u   CHR   89,7      0t0 1017 /dev/i2c-7
Processes locking /dev/i2c-7 (inode 1017):
   1372
      1372
   egrep: warning: egrep is obsolescent; using grep -E
   Name:        org_kde_powerde
   State:       S (sleeping)
   Pid: 1372
   egrep: warning: egrep is obsolescent; using grep -E
   Name:        org_kde_powerde
   State:       S (sleeping)
   Pid: 1372

(i2c_open_bus                  )           Cross instance locking failed
No displays found.
Run "ddcutil environment" to check for system configuration problems.

Edited the file just like in #73 , rebooted and it is the same.
Ran ddcutil environment and here is what I got
ddcutil environment
The following tests probe the runtime environment using multiple overlapping methods.
(i2c_open_bus                  )           busno=3, flock() returned: EAGAIN(-11): Resource temporarily unavailable
/dev/i2c-3 locked.  Retrying...
(i2c_open_bus                  )           busno=3, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=3, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=3, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=3, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=3, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=3, flock() returned: EAGAIN(-11): Resource temporarily unavailable
Max wait exceeded for /dev/i2c-3
Programs holding /dev/i2c-3 open:
   COMMAND  PID  USER FD   TYPE DEVICE SIZE/OFF NODE NAME
   ddcutil 2846 kalzi 3u   CHR   89,3      0t0  976 /dev/i2c-3
   sh      2856 kalzi 3u   CHR   89,3      0t0  976 /dev/i2c-3
   COMMAND  PID  USER FD   TYPE DEVICE SIZE/OFF NODE NAME
   ddcutil 2846 kalzi 3u   CHR   89,3      0t0  976 /dev/i2c-3
   sh      2859 kalzi 3u   CHR   89,3      0t0  976 /dev/i2c-3
Processes locking /dev/i2c-3 (inode 976):
   1394
      1394
   egrep: warning: egrep is obsolescent; using grep -E
   Name:        org_kde_powerde
   State:       S (sleeping)
   Pid: 1394
   egrep: warning: egrep is obsolescent; using grep -E
   Name:        org_kde_powerde
   State:       S (sleeping)
   Pid: 1394

(i2c_open_bus                  )           Cross instance locking failed
(i2c_open_bus                  )           busno=7, flock() returned: EAGAIN(-11): Resource temporarily unavailable
/dev/i2c-7 locked.  Retrying...
(i2c_open_bus                  )           busno=7, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=7, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=7, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=7, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=7, flock() returned: EAGAIN(-11): Resource temporarily unavailable
(i2c_open_bus                  )           busno=7, flock() returned: EAGAIN(-11): Resource temporarily unavailable
Max wait exceeded for /dev/i2c-7
Programs holding /dev/i2c-7 open:
   COMMAND  PID  USER FD   TYPE DEVICE SIZE/OFF NODE NAME
   ddcutil 2846 kalzi 3u   CHR   89,7      0t0  986 /dev/i2c-7
   sh      2885 kalzi 3u   CHR   89,7      0t0  986 /dev/i2c-7
   COMMAND  PID  USER FD   TYPE DEVICE SIZE/OFF NODE NAME
   ddcutil 2846 kalzi 3u   CHR   89,7      0t0  986 /dev/i2c-7
   sh      2888 kalzi 3u   CHR   89,7      0t0  986 /dev/i2c-7
Processes locking /dev/i2c-7 (inode 986):
   1394
      1394
   egrep: warning: egrep is obsolescent; using grep -E
   Name:        org_kde_powerde
   State:       S (sleeping)
   Pid: 1394
   egrep: warning: egrep is obsolescent; using grep -E
   Name:        org_kde_powerde
   State:       S (sleeping)
   Pid: 1394

(i2c_open_bus                  )           Cross instance locking failed
*** Basic System Information ***

ddcutil version: 2.1.4

/proc/version:
   Linux version 6.7.8-arch1-1 (linux@archlinux) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Sun, 03 Mar 2024 00:30:36 +0000

Architecture:     x86_64
Distributor id:   EndeavourOS
Release:          rolling
Found a known architecture

/proc/cmdline:
   BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=25fe5e6c-8c5c-40cf-96f6-f14571cc44d2 rw rootflags=subvol=@ nowatchdog nvme_load=YES resume=UUID=d1b587a4-5163-4cce-96eb-e080ebc83354 loglevel=3

*** Primary Check 1: Identify video card and driver ***

Obtaining card and driver information from /sys...
Primary video controller at PCI address 0000:01:00.0 (boot_vga flag is set)
   Device class:        x030000    VGA compatible controller
   Vendor:              x1002      Advanced Micro Devices, Inc. [AMD/ATI]
   Device:              x67df      Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
   Subvendor/Subdevice: 1682/c580  Radeon RX 580
   Driver name:         amdgpu
   Driver version:      Unable to determine
   I2C device:          i2c-3      name: AMDGPU DM i2c hw bus 3
   I2C device:          i2c-1      name: AMDGPU DM i2c hw bus 1
   I2C device:          i2c-4      name: AMDGPU DM i2c hw bus 4
   I2C device:          i2c-2      name: AMDGPU DM i2c hw bus 2
   I2C device:          i2c-0      name: AMDGPU DM i2c hw bus 0

*** Primary Check 2: Check that /dev/i2c-* exist and writable ***

Current user: kalzi (1000)

Checking /dev/i2c-* devices...

Devices /dev/i2c-* must exist and the logged on user must have read/write permission for those devices (or at least those devices associated
with monitors).

Typically, this access is enabled by:
  - setting the group for /dev/i2c-* to i2c
  - setting group RW permissions for /dev/i2c-*
  - making the current user a member of group i2c

Alternatively, this can be enabled by just giving everyone RW permission
The following tests probe for these conditions.

Checking for /dev/i2c-* devices...
   crw-rw----+ 1 root i2c 89, 0 Mar  8 09:44 /dev/i2c-0
   crw-rw----+ 1 root i2c 89, 1 Mar  8 09:44 /dev/i2c-1
   crw-rw----+ 1 root i2c 89, 2 Mar  8 09:44 /dev/i2c-2
   crw-rw----+ 1 root i2c 89, 3 Mar  8 09:44 /dev/i2c-3
   crw-rw----+ 1 root i2c 89, 4 Mar  8 09:44 /dev/i2c-4
   crw-rw----+ 1 root i2c 89, 5 Mar  8 09:44 /dev/i2c-5
   crw-rw----+ 1 root i2c 89, 6 Mar  8 09:44 /dev/i2c-6
   crw-rw----+ 1 root i2c 89, 7 Mar  8 09:44 /dev/i2c-7

Current user (kalzi) has RW access to all /dev/i2c-* devices.

*** Primary Check 3: Check that module i2c_dev is loaded ***

Checking for driver i2c_dev...
   sysfs reports module i2c_dev is loaded.
   Module i2c_dev is NOT built into the kernel
   Loadable i2c-dev module found
   Module i2c_dev is loaded

*** Primary Check 4: Driver specific checks ***

Performing driver specific checks...
No driver specific checks apply.

*** Additional probes ***

Examining /sys/bus/i2c/devices...
   /sys/bus/i2c/devices/i2c-0/name:   AMDGPU DM i2c hw bus 0
   /sys/bus/i2c/devices/i2c-1/name:   AMDGPU DM i2c hw bus 1
   /sys/bus/i2c/devices/i2c-2/name:   AMDGPU DM i2c hw bus 2
   /sys/bus/i2c/devices/i2c-3/name:   AMDGPU DM i2c hw bus 3
   /sys/bus/i2c/devices/i2c-4/name:   AMDGPU DM i2c hw bus 4
   /sys/bus/i2c/devices/i2c-5/name:   AMDGPU DM aux hw bus 0
   /sys/bus/i2c/devices/i2c-6/name:   AMDGPU DM aux hw bus 1
   /sys/bus/i2c/devices/i2c-7/name:   AMDGPU DM aux hw bus 2

Env_Accumulator:
   architecture:                  x86_64
   distributor_id                 EndeavourOS
   Drivers detected:              amdgpu
   /dev/i2c device numbers:       0 1 2 3 4 5 6 7
   sysfs_i2c_devices_exist:       true
   /sys/bus/i2c device numbers:   0 1 2 3 4 5 6 7
   dev_i2c_devices_required:      true
   module_i2c_dev_needed:         true
   module_i2c_dev_builtin:        false
   loadable_i2c_dev_exists:       true
   i2c_dev_loaded_or_builtin:     true
   group_i2c_checked:             true
   group_i2c_exists:              true
   dev_i2c_common_group_name:     i2c
   all_dev_i2c_has_group_i2c:     true
   any_dev_i2c_has_group_i2c:     true
   all_dev_i2c_is_group_rw:       true
   any_dev_i2c_is_group_rw:       true
   cur_uname:                     kalzi
   cur_uid:                       1000
   cur_user_in_group_i2c:         false
   cur_user_any_devi2c_rw:        true
   cur_user_all_devi2c_rw:        true

Configuration suggestions:
   Current user has RW access to all /dev/i2c-N devices.
   Skipping further group and permission checks.

KDE Plasma is still locking ddcutil. The fix solved this for me just fine. If you edited the service file correctly and it doesn't fix the issue, this is a bug in KDE Plasma.

I added this line to the file
Environment="POWERDEVIL_NO_DDCUTIL=1"  as is under the [service] field and without the #. Ctrl+o to save them exited. Even rebooted

KDE Plasma is still locking ddcutil. The fix solved this for me just fine. If you edited the service file correctly and it doesn't fix the issue, this is a bug in KDE Plasma.

Just to let you know, I fixed it using the #73 solution. I was just placing the lines in the wrong place. All good now. Thank you

In theory in Plasma 6 you can control the brightness of your monitor from the default brightness widget (where you controlled your laptop display brightness only in Plasma 5). That's the reason it uses libddc. My guess is that it should not "lock" ddcutil, though (ie: if both plasma and this plasmoid should be able to use ddcutil at the same time), but there might be more going on that I don't know.

Hmm, I updated. Uninstalled and reinstalled. Also restarted kwin and plasmashell.
But it still complains that the widget is for an older version. The metadata.json in .local/share/plasma/plasmoids/de.davidhi.ddcci-brightness/ has: "X-Plasma-API-Minimum-Version": "6.0",
Is there anything else needed to flush the cache or something?


New component: Switch

Related information and insight

Toggle and Switch is both used as name for this component
UX Planet: https://uxplanet.org/ui-switch-component-3f29bc7f4f45
https://aksel.nav.no/komponenter/core/switch
https://design.entur.org/komponenter/skjemaelementer/switch
https://designsystem.dk/komponenter/toggle/
https://carbondesignsystem.com/components/toggle/usage/

Switch specification
TheSwitch component should be used to enable and disable different options.

The switch should have only two states: on and off
The change should be applied immediately
Use clear colors to indicate the on and off state to the user
To indicate the switch’s purpose, provide a clear label
Should be large enough to be easily tapped or clicked by the user.
Add requirements and specification

### Tasks
- [x] Write about specification, requirements and scope in this issue
- [ ] https://github.com/digdir/designsystem/issues/644
- [ ] https://github.com/digdir/designsystem/issues/645
- [ ] https://github.com/digdir/designsystem/issues/646
- [ ] https://github.com/digdir/designsystem/issues/647

The switch component is ready for use: https://storybook.designsystemet.no/?path=/docs/felles-switch--docs


Add AdminServer

This is a new server meant to implement the Admin API, handling application deployments.

https://ocd.appscale.com:8080/job/Daily Build/3103/
https://ocd.appscale.com:8080/job/Migration/1337/
Please see https://github.com/AppScale/appscale-tools/pull/614

https://ocd.appscale.com:8080/job/Daily Build/3130/
Migration: https://ocd.appscale.com:8080/job/Migration/1359/

https://ocd.appscale.com:8080/job/Daily Build/3146/
Migration: https://ocd.appscale.com:8080/job/Migration/1376/ (see https://github.com/AppScale/appscale-testing/pull/221)

https://ocd.appscale.com:8080/job/Daily Build/3152/

This must go in with https://github.com/AppScale/appscale-tools/pull/614 and https://github.com/AppScale/appscale-testing/pull/221


⚠ ClamAV has degraded performance

In 3a2469e, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in b4e380e.


Warn validators with slow hardware

Closes: #12017
TODO:

[x] Move Metric to sc-sysinfo
[x] Move Requirement(s) to sc-sysinfo
[x] Compare the benchmark results inside sc-sysinfo to requirements.

polkadot companion: https://github.com/paritytech/polkadot/pull/6269
cumulus companion: https://github.com/paritytech/cumulus/pull/1863

@ggwpez PTAL.

Looking at the #12017, my understanding of it is to change the log level to a warn if the benchmark is slow and --validator flag is passed, not enable hw bench unconditionally when --validator is enabled.

WIP

@ordian Could you take another look now that I have updated the code?

Looks good to me in effect, but I'll let the substrate team judge whether moving the types to sysinfo is OK. Thanks!

@ggwpez @koute Did you manage to think of a better approach so that there is less repetition or is it ok like this?

@ggwpez I have tested this to try if this actually works by running:
./target/release/substrate --chain=local --validator

I have set one of the requirements too high so that I can see if I will get a warning when not passing. I did get the warning but if I am being honest I would never actually notice it :P(I initially thought it wasn't working because it just blends into the rest of the logs.). Maybe using some ⚠ emoji would help?

Maybe using some :warning: emoji would help?

Yea good idea. Some :warning: :warning: :warning: could help.

@ggwpez I have added warning emojis to the log. Could you approve the PR if the changes are fine?

@ggwpez I have added warning emojis to the log. Could you approve the PR if the changes are fine?

Yea sorry for the slow responses here, am really busy right now.

Please put your address for a tip.

I have added my address, Thanks!

The companion checks are still red. Dont know why it says its un-mergable, but i can also not build Polkadot with it locally.

Should still figure out those companion/polkadot issues mentioned above though

@sam0x17 It should probably work now. I don't have permission to rerun the CI so it would be good if you could do that.

re-running cumulus now :)

Hmm, it is weird that it still doesn't pass the CI check. For some reason, the cumulus PR doesn't see the changes made in the Polkadot PR. I tough putting polkadot companion: https://github.com/paritytech/polkadot/pull/6269 would fix this.

I dont get it either. Looks correct.

/tip small

/tip small

/tip small


Add option to set check icon tint while in Unchecked state

Currently, there's no option to tint check image while it's in Unchecked state, I thought it should be useful.

Thanks @jimmy0251!
How do I use this branch in gradle dependencies?

compile('com.github.canopas:MultiImagePicker:1.3.2')


 (Reference)
My initial plan was to do a PR to help you out, but it looks like this repository isn't up-to-date with a 1.19-forge branch.

Sure, I'll give it a try.

Updated in 2.6.3, thank for your contribution :D


Increase default SM request timeout

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Coverage remained the same at 85.861% when pulling<PHONE_NUMBER>4dfb79b226098b6688b56f20759976 on increase-sm-req-timeout into b95a599c07a48834ee72045b6ed8eab5dc25018d on master.


cancel pending requests if user navigates away from the page

closes #51

Can you please solve the merge conflicts


Parser has Issues with Blanks and Quotes in Unique Attributes

While possible a bad example, the following will produce corrupted data in AST:
[url=javascript:alert('XSS ME');]TEXT[/url]
[url=javascript:alert("XSS ME");]TEXT[/url]

This can already be seen in the HTML Render demo, that outputs the (processed) AST tree as:
[
  {"tag":"a","attrs":{"href":"ME');"},"content":["TEXT"]},
  "\n",
  {"tag":"a","attrs":{"href":");"},"content":["TEXT"]},"\n"
]

If debugging the parsed tree prior to processing, the first line is represented as:
[
  {
    "tag": "url",
    "attrs": {
      "javascript:alert('XSS": "javascript:alert('XSS",
      "ME');": "ME');"
    },
    "content": [
      "TEXT"
    ]
  }
]

the second one as:
[
  {
    "tag": "url",
    "attrs": {
      "javascript:alert(\"XSS ME": "javascript:alert(\"XSS ME",
      ");": ");"
    },
    "content": [
      "TEXT"
    ]
  }
]

This is possible a similar issue to: #194.
While it may be argued, if the BBCode should not have used, for example, quotes for the first example (which works as expected):
[url="javascript:alert('XSS ME');"]TEXT[/url]

The pain point is, that typically BBCode origins from manually written markup. Thus, more fault-tolerance would be highly appreciated.
Alternative Challenges
[quote=J. D.]T[/quote]
[quote=J. "The T" D.]T[/quote]

Pretty expected behavior, it's hard for parser to understand where ends one attribute value and start new one. So parser assumes that all attributes delimited by space. For single attribute tags like [url=someurl] I think need to ignore any symbols except ending tag ] and this behavior I think can solve another issue with [url=https://example.org/ fakeUnique=fakeUnique]T[/url], that will be transformed to <a href="https://example.org/ fakeUnique=fakeUnique">....

For single attribute tags like [url=someurl] I think need to ignore any symbols except ending tag ].

Agreed. The question is, where to provide this information.
My gut feeling: It should be made available as an additional option to "unique arguments", so that tag mappings may decide, if they want to support, for example, [url=someurl target=_blank] (an option, BBob supports, currently), or if they prefer supporting blanks within the unique attribute.
This may come in combination with a different representation for "unique attributes" (#202). Perhaps even "in parallel" to existing tree data, so that current usages do not break.
Suggested parsed structure in tree:
[
  {
    "tag": "url",
    "attrs": {
      // unchanged to stay compatible
      "javascript:alert('XSS": "javascript:alert('XSS",
      "ME');": "ME');"
    },
    // Suggestion for this issue.
    "attrString": "javascript:alert('XSS ME');",
    // Suggestion for #202; requires a decision though, what is the
    // best value here. I would vote for enforcing "value right behind the tag's "=",
    // which, for the given example, would evaluate then to: "javascript:alert('XSS", instead.
    "uniqAttr": "ME');",
    "content": [
      "TEXT"
    ]
  }
]

Regarding the existing API, it may be nicer to put these "extra attributes" into the attrs object, but it raises the probability to be breaking towards current usages of BBob.
Eventually, a decision has to be made for the existing presets, e.g., if HTML5 Preset switches to using attrString for the URL rather than the unique attribute.


[stable/rabbitmq-ha] Changelog for Charts

Is your feature request related to a problem? Please describe.
My coworker installed a very old Snapshot version of the chart and i may want to upgrade it. I have no way to find out what changed in the chart due to missing changelogs. I could crawl through the git commits but that is not very productive.
Describe the solution you'd like
Well, manage a Changelog which describes updates in the chart.
Describe alternatives you've considered
See description of the problem.
Additional context
None.

This chart has been deprecated and is no longer maintained. It is recommended to use the Bitnami maintained RabbitMQ chart which has a similar feature set, including high availability. See #23746 and #21103. Can you please close. Thanks!


Not getting click event after scroll

Describe the bug
I want to handle click event of every row but after scroll i am not gettiing position
To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Stacktrace
If applicable, add the stacktrace you encountered.
Code for a Minimum Reproducible example
To assist investigation a Minimum Reproducible example App should be included.
Tools:

FixedHeaderTableLayout version: [e.g. <IP_ADDRESS>]
Android version: [e.g. 11]

Additional context
Add any other context about the problem here.

As per the documentation on the feature todo list on the main page "Nothing is clickable in the table yet."
I'm working on this feature but have not completed it yet.

The position gets shifted exactly by the number of scrolled rows. Is their any hack or workaround solution to get the correct position? This thing is highly wanted!

I had a draft version working, but it needed some improvement to Motion Event handling, which I've done but not tested yet, so nearly there. The clicks are current getting through just at the wrong location because of the way this scales and pans it's children, the motion Events need to be mapped to the canvas matrix. Hopefully I've release a version with working clicks soon.

I can help testing it. Is it in <IP_ADDRESS> commit?

Have got it fixed myself already. I don't code in Jave, so ported it into Kotlin first. You can find the code here.
The onInterceptTouchEvent function is of the intereset. Also onTouch was replaced by onTouchEvent and resetScale added.

Fixed in commit https://github.com/Zardozz/FixedHeaderTableLayout/commit/4e2cf4f6a2d0b9d4438e94358bf33f8f08461324
Will be released soon as <IP_ADDRESS>
PS There are too many issues with the Kotlin language to make it worthwhile using, even google mostly use Java for their own libraries. It's not worth learning as well and google will probably drop it at some point as they do a lot with various projects.

Here is a fix for the onInterceptTouchEvent solution. You can take a look if you wish. In my point of view this solution is much simpler and hence less error prone than having custom handlers for each MotionEvent action.

The move to custom Handlers was due to the available GestureDetector also intercepting other gestures that actually would be more useful if available to the children views.

Your updated fix using a OnTouchListener still has the possibility of a child stealing Motion Events that are needed for the scale and scroll functionality.
If you are interested reading https://stackoverflow.com/a/22490810/2373819 should help understand why doing it in an override of dispatchTouchEvent() is a better solution (Note the FixedHeaderTableLayout is a ViewGroup)
The other difference as mentioned earlier that handling the low level events directly for scroll means I steal as little as possible (ScaleGestureDetector is used because that only steals scale related events)

I read that post when working on the fix.

The difference is that dispatchTouchEvent is dispatching MotionEvents and onInterceptTouchEvent tells if it should intercept (not dispatching the MotionEvent to children) or not (dispatching to children).

In our case there is no difference.

Either way children have no possibility to steal any event unless the parent allows it. The only possible case of stealing with onInterceptTouchEvent approach is the use of requestDisallowInterceptTouchEvent, but this case is very specific.
PS:

fix using a OnTouchListener still has the possibility of a child stealing Motion Events that are needed for the scale and scroll functionality.

I assume you meant onInterceptTouchEvent here and not OnTouchListener.


Allow MPN decide token-indices itself

Codecov Report
Patch coverage: 64.28% and project coverage change: -0.17 :warning:

Comparison is base (1192679) 76.58% compared to head (6c4aba2) 76.41%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master      #75      +/-   ##
==========================================
- Coverage   76.58%   76.41%   -0.17%
==========================================
  Files          97       97
  Lines        4988     4987       -1
==========================================
- Hits         3820     3811       -9
- Misses       1168     1176       +8

Impacted Files
Coverage Δ

src/client/explorer.rs
44.96% <ø> (+1.99%)
:arrow_up:

src/client/messages.rs
23.33% <ø> (+2.12%)
:arrow_up:

src/core/transaction.rs
95.12% <ø> (ø)

src/mpn/mod.rs
90.90% <ø> (+3.28%)
:arrow_up:

src/wallet/tx_builder.rs
97.97% <ø> (ø)

src/zk/mod.rs
85.09% <ø> (+3.84%)
:arrow_up:

src/mpn/deposit.rs
81.72% <55.55%> (-3.34%)
:arrow_down:

src/mpn/update.rs
75.16% <66.66%> (-1.55%)
:arrow_down:

src/mpn/withdraw.rs
79.06% <66.66%> (-0.46%)
:arrow_down:

... and 3 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


test: restoring e2e

v13.0.1 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.


upgrade pyarrow dependency to 0.17

I used to have pyarrow 0.17 (the latest) on my machine.  When I installed the latest superset, it downgraded it to 0.16.
Then, I have to manually upgrade again but it complains that superset 0.36 is incompatible with 0.17:
$ pip3.6 install --user --upgrade pyarrow
WARNING: pip is being invoked by an old script wrapper. This will fail in a future version of pip.
Please see https://github.com/pypa/pip/issues/5599 for advice on fixing the underlying issue.
To avoid this problem you can invoke Python with '-m pip' instead of running pip directly.
Collecting pyarrow
  Downloading pyarrow-0.17.0-cp36-cp36m-manylinux2014_x86_64.whl (63.8 MB)
     |████████████████████████████████| 63.8 MB 10.5 MB/s
Requirement already satisfied, skipping upgrade: numpy>=1.14 in /home/hc/.local/lib/python3.6/site-packages (from pyarrow) (1.18.4)
Could not build wheels for numpy, since package 'wheel' is not installed.
ERROR: apache-superset 0.36.0 has requirement pyarrow<0.17.0,>=0.16.0, but you'll have pyarrow 0.17.0 which is incompatible.

There is a bug in an older version of cython that pyarrow 0.16 uses.  Hence, it would be great if superset could change the dependency of pyarrow to 0.17.
Thanks!

0.36.0 has pinned pyarrow at <0.17, as 0.16.0 was the most recent version available when 0.36.0 was released. This is due to semver not guaranteeing forward compatibility for minor versions. master branch of Superset has bumped pyarrow to 0.17.0, hence the next release will automatically pull that in. If you want, you should be able to bump pyarrow after you've installed Superset, as in this case there didn't seem to be any breaking changes in the new version that affected Superset, i.e. the error can be ignored.
Note, however, that it is recommended to always run Superset in an isolated virtualenv separately from your system installation to avoid precisely these kinds of problems.

Thanks for clarifying!


servant(-*) 0.5

Lumping all the servant-* bounds restrictions into one issue.
servant-0.5 depended on by:

[ ] dixi-<IP_ADDRESS> (==0.4.*). Liam O'Connor<EMAIL_ADDRESS>@liamoc
[ ] google-translate-<IP_ADDRESS> (==0.4.*). David Johnson<EMAIL_ADDRESS>@dmjio. @dmjio
[ ] haskell-kubernetes-0.3.2 (==0.4.*). Aaron Levin<EMAIL_ADDRESS>@aaronmblevin. @soundcloud
[ ] lackey-0.1.2 (==0.4.*). Taylor Fausak<EMAIL_ADDRESS>@tfausak. @tfausak
[ ] servant-JuicyPixels-<IP_ADDRESS> (==0.4.*). Timo von Holtz<EMAIL_ADDRESS>@tvh. @tvh
[ ] servant-jquery-<IP_ADDRESS> (==0.4.*). Haskell Servant<EMAIL_ADDRESS>@jkarni. @SoenkeHahn @jkarni
[ ] servant-yaml-<IP_ADDRESS> (>=<IP_ADDRESS> && < 0.5). Oleg Grenrus<EMAIL_ADDRESS>@phadej. @phadej
[ ] smsaero-0.4.1 (==0.4.*). Nickolay Kudasov<EMAIL_ADDRESS>@fizruk. @GetShopTV

servant-blaze-0.5 depended on by:

[ ] dixi-<IP_ADDRESS> (==0.4.*). Liam O'Connor<EMAIL_ADDRESS>@liamoc

servant-client-0.5 depended on by:

[ ] google-translate-<IP_ADDRESS> (==0.4.*). David Johnson<EMAIL_ADDRESS>@dmjio. @dmjio
[ ] haskell-kubernetes-0.3.2 (==0.4.*). Aaron Levin<EMAIL_ADDRESS>@aaronmblevin. @soundcloud

servant-docs-0.5 depended on by:

[ ] dixi-<IP_ADDRESS> (==0.4.*). Liam O'Connor<EMAIL_ADDRESS>@liamoc

servant-mock-0.5 depended on by:

[ ] haskell-kubernetes-0.3.2 (==0.4.*). Aaron Levin<EMAIL_ADDRESS>@aaronmblevin. @soundcloud

servant-server-0.5 depended on by:

[ ] dixi-<IP_ADDRESS> (==0.4.*). Liam O'Connor<EMAIL_ADDRESS>@liamoc
[ ] haskell-kubernetes-0.3.2 (==0.4.*). Aaron Levin<EMAIL_ADDRESS>@aaronmblevin. @soundcloud
[ ] servant-jquery-<IP_ADDRESS> (==0.4.*). Haskell Servant<EMAIL_ADDRESS>@jkarni. @SoenkeHahn @jkarni
[ ] servant-yaml-<IP_ADDRESS> (>=<IP_ADDRESS> && < 0.5). Oleg Grenrus<EMAIL_ADDRESS>@phadej. @phadej

See also:
http://haskell-servant.github.io/posts/2016-03-19-servant-0.5-release.html

lackey-0.2.0 supports servant-0.5.

servant-jquery is being deprecated in favour of servant-js

Here's a PR to remove servant-jquery and add servant-foreign and servant-js: https://github.com/fpco/stackage/pull/1301

Fixed dixi.

My library giphy-api depends on servant-client==0.4.* too. I've got an upgrade patch ready; do you have a recommendation on how to publish it? Should I add an upper bound in the section for the current 0.4-compatible release?

Should I add an upper bound in the section for the current 0.4-compatible release?

@passy probably yes.

I've got an upgrade patch ready; do you have a recommendation on how to publish it?

The general recommendation is to publish your packages with whatever bounds they require.

@DanBurton Thanks, I just wanted to make sure I don't cause you any avoidable work. :)

Btw, we've just released servant-0.6. It's a breaking change for servant-client only.

I'm really looking forward seeing 0.6 in stackage. ☀
Thanks everyone for taking care of this !

lackey-0.3.0 now supports servant-0.6. It also uses servant-foreign, which was a joy to use!

Thanks everyone!
I am going to disable google-translate, haskell-kubernetes, and smsaero, and reintroduce dixi to allow Nightly to move to servant-0.6 hopefully.

@juhp  servant is now 0.7: http://hackage.haskell.org/package/servant . otherwise, thanks !

👉 https://github.com/fpco/stackage/issues/1394

That's right, that will be the next step.


render document style error, Transparent shapes will be rendered black by plugin

Transparent shapes in a word document are rendered black in the page, eg:
this is origin file

and on the websize is

1.铸销加工会议问题.docx

Would recommend you to add next style to your application, to fix this issue
.docx svg {
    fill: transparent;
}

Partially fixed in 0.3.1


Assignment to TypedDict field does not handle bidirectional type inference properly

 Environment data

Language Server version: 2021.7.7
OS and version: linux x64
Python version (and distribution if applicable, e.g. Anaconda): 3.9.4 -- pyenv and a normal venv based virtual environment
python.analysis.indexing: undefined
python.analysis.typeCheckingMode: basic

 Expected behaviour
Pylance understands that TypedDict is a wrapper around dict at runtime and __call__ on any TypedDict is just a call to dict()
which will happily accept a dict as its argument.
 Actual behaviour
Pylance complains that you cannot pass a dict to SomeTypedDict(), stating that instead one must use key/value args
 Logs

Python Language Server Log
[BG(1)] getSemanticTokens delta previousResultId:1628246633795 at /home/ad/development/python/EDMarketConnector/test-pycodestyle.py ...
[BG(1)]   parsing: /home/ad/development/python/EDMarketConnector/test-pycodestyle.py (1ms)
[BG(1)]   binding: /home/ad/development/python/EDMarketConnector/test-pycodestyle.py (0ms)
[BG(1)] getSemanticTokens delta previousResultId:1628246633795 at /home/ad/development/python/EDMarketConnector/test-pycodestyle.py (7ms)
[FG] parsing: /home/ad/development/python/EDMarketConnector/test-pycodestyle.py (0ms)
[FG] binding: /home/ad/development/python/EDMarketConnector/test-pycodestyle.py (0ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: setFileOpened
Background analysis message: markFilesDirty

 Code Snippet / Additional information

from typing import TypedDict

class Test(TypedDict):
    thing: bool
    stuff: str

x = Test({"thing": True, "stuff": 'test'})

print(x, type(x), dict({"test": "stuff"}))

I think you mean __init__ rather than __call__. The latter is used only when calling an instance of the class, but in your example, you're calling the class itself (i.e. invoking its constructor), so __call__ is not involved.
PEP 589 is very clear that a TypedDict class should not allow non-keyword arguments passed to its constructor, so pylance is correct in reporting an error here.

The created TypedDict type object is not a real class object. Here are the only uses of the type a type checker is expected to allow: ... It can be used as a callable object with keyword arguments corresponding to the TypedDict items. Non-keyword arguments are not allowed.

Passing a dict to the constructor of a TypedDict class doesn't make sense because that's redundant. In your code example, you're allocating a dict object and then attempting to construct a second copy of that same dict. It's the equivalent of dict({"thing": True, "stuff": "test"}) rather than simply using {"thing": True, "stuff": "test"}.
Here's how a TypedDict type is meant to be used.
x: Test = {"thing": True, "stuff": "test"}

Sorry, I misread the source for the metaclass. You are correct I wanted __init__.
Runtime behavior is however as I described (and thus against the PEP, but thats an argument for the core devs).
I wanted to use it due to I guess a different edgecase or misunderstanding in behaviour where:
from typing import Optional, TypedDict

class Thing(TypedDict):
    thing: bool
    stuff: str

class Thing2(TypedDict):
    other_thing: Optional[Thing]
    stuff: str

thing2: Thing2 = {"other_thing": None, "stuff": "a"}
thing2['other_thing'] = {"thing": False, "stuff": "a"}
# ^^^^^^^^^^^^^^^^
# Could not assign item in TypedDict
#   Type "dict[str, Unknown]" cannot be assigned to type "Thing | None"
#     "dict[str, Unknown]" is incompatible with "Thing"
#     Type cannot be assigned to type "None"
#   PylancereportTypedDictNotRequiredAccess

Thus my first solution would be to wrap it in Thing to make the type checker happy (though it should work anyway. I see no reason why it wouldnt?).
Perhaps I should open an issue regarding that behaviour instead?
In the code Im working on I had gone with creating a new var and annotating it appropriately, then using that in the assignment, but its an extra step that feels quite pointless.

I agree that this code should work. I've fixed the underlying reason for this error message. This will be fixed in the next release of pylance.

fixed in 2021.8.1


Emacs (25.1.1) Fails on Startup

In CI, Emacs is failing to start up in certain cases due to line 3 in user-config-system.el as of 5ad51d14ee28a367d55db1e76681f0ce18d18b44.

Since it looks like we don't even use it in that file, I think the fix is to remove that line and not require git.

sorry i think this was an artifact from when i was using a package for git instead of calling the executable directly

Which approach is better? Using a package or using an executable?

I think the current solution is fine.


Singularity installation

Hey all,
Personally I faced quite a few problems with the singularity installation, which could not find the go installation by following the 3.5 singularity installation guide. Following the issues at the singularity repo, they now suggest following the latest documentation:
https://singularity.hpcng.org/admin-docs/master/installation.html
With the latest installation guide I managed to get it to work and it worked with your benchmarks too, as such maybe you can update the README with the link above, so that other users do not face the singularity related issue.

Hey Arlind,
thanks for providing your solution.
We will update the docs accordingly.


Disable "Save card to Google / Apple"

Is your feature request related to a problem? Please describe.
I believe the native CardField component works in a way that prompts android / ios to save the card which could not be desirable at all. This behavior should be driven from a prop on the RN side.

Describe the solution you'd like
I would like to be able to disable the integration with Apple/Google payments so that the user is not being prompted to save the card on his phone.

@tlvenn could you provide steps to reproduce it? I am not able to do it on emulator

Closing for inactivity. Please provide steps to reproduce and we can reopen!

Hi @charliecruzan-stripe. We are getting this in production as well, but using the stripe-android SDK. (However, this was the only place I could find the issue listed or noted, and it is the same effect).
So far this is only replicable on Android 12 and when using a physical device. The simulator is not presenting this.
We create a payment method via createPaymentMethod (either in test mode or live). On successful creation ( new ApiResultCallback<PaymentMethod>() ), we're getting this Google card.
So far we have tried disabling google wallet via the meta-data tag in the Android Manifest, to no avail.

Upon further review, I am not sure this is something fixable outside Google Settings.
It seems Google Phones with Settings -> Privacy -> Autofill enabled with attempt to recognize card inputs both in applications and on the web and then ask to fill them. Disabling this on the device fixes the issue on our Google phone(s), while nothing else seemed to. Possibly helpful information for @tlvenn as well.

Ah thanks @loganthompson for sharing that! That's super useful to know, although unfortunate that you can't disable this at the application level


Ensure that Panoptes calculates classification duration and session number for each user classification.

@vrooje @ggdhines and I have all needed to do analysis on user sessions when looking at user classification behaviour. The best way to do this is to record a classification duration for each classification (that is, the time between the end of user's previous classification and the end of this one). Each time the classification duration is greater than one hour, that indicates the start of a new session (this is accepted in papers etc as a standard approach for identifying sessions). This metric is so useful that it would be good to have this generated automatically after a classification is stored.
I discussed with @camallen and he had 3 ideas:

the aggregation engine could have a worker which listens for the classification update then calculates the classification duration and session ID and adds this metadata to the classification.
the "current session number" for each user could be stored in Kafka, and updated each time 1 hour has elapsed since the last classification.
Cam had another idea, I'll invite him to add it here.

Notes:
Even though the classifications may come in non-sequentially, you should be able to reliably get the order of classifications for a user after the fact by using the incremental key
The current Panoptes model has start time and finish time - however the classification duration is more than this, as it has to take into account the previous classification as well.
Having this metric automatically in place for all projects will be hugely useful in future experimental work or user behavioural analysis.

So this seems like a place where a stream of classifications from Kafka could be used to determine which user sessions classifications belong to.

the aggregation engine could have a worker which listens for the classification update then calculates the classification duration and session ID and adds this metadata to the classification.

I.e. a batch process that runs over the set of classifications to create these session identifiers and duration. It would then append these fields to the classification or store them in another table with the list of associated classification ID's. Sessions would be static so this process would only need to be run on new data coming in.

the "current session number" for each user could be stored in Kafka, and updated each time 1 hour has elapsed since the last classification.

So I thought we could have a storm / spark streaming process listening to the stream of classifications that would create / use a per user : project session ID that expires / increments after a set timeout (e.g. the 1 hour mentioned above). It could attach this session id, start and end times on the classification or store the details in a separate table. Duration of the session could be calculated by inspecting the classification session groups.

Cam had another idea, I'll invite him to add it here.

Specifically adopting the idea from point 2 above but for an existing Ouroboros project (snapshot serenget) that can run in @edpaget's storm topology.

Would we want to run this for a user's sessions in individual projects, or count people who switch projects without ever taking a break as the same session? Would it be hard to do both?

@parrish can we use the notifications system presence system to construct / retrieve a session identifier that can be appended to the classification?

sounds like we should just use a client side session identifier from PFE for this.

Just noting somewhere for future reference: @willettk and I have been chatting about how classification duration (time it takes to do 1 classification) might be used to identify bots, by comparing each user's typical classification duration against the overall distribution and identifying outliers.


Converters.Add is not thread safe

Thanks for the package it's easy to use and  works great. Recently using your Core package I've ran into a concurrency issue.
Under load I get an issue similar https://github.com/dd4t/DD4T.Core/issues/100
I think the issue is in: https://github.com/olohmann/Lohmann.HALight/blob/master/src/Lohmann.HALight/Converters/ResourceConverter.cs
public override void WriteJson(JsonWriter writer, object value, JsonSerializer serializer)
{
   serializer.Converters.Remove(this);
   var root = new JObject();
   ConvertRecursively((IResource)value, root, serializer);
   root.WriteTo(writer);
   serializer.Converters.Add(this);
}

As I understand it for MVC Core formatters the JsonSerializer instance passed to WriteJson uses a Object Pool, therefore Adding and Removing Converters in the WriteJson methods will eventually corrupt the collection and lead to a concurrency issue.
As a quick and dirty workaround I just new up the JsonSerializer in WriteJson (I prefer this to using a lock), this solves the problem.
 public override void WriteJson(JsonWriter writer, object value, JsonSerializer serializer)
 {
  //serializer is created a using an Object Pool when used via ASP.NET Core MVC formatters, Adding and Removing Converters will eventually lead to a concurrency issue.
   var halSerializer = JsonSerializer.Create(HalJsonSerializerSettingsProvider.CreateSerializerSettings().AppendHalConverters());

   halSerializer.Converters.Remove(this);
   var root = new JObject();

   ConvertRecursively((IResource)value, root, halSerializer);
   root.WriteTo(writer);

   halSerializer.Converters.Add(this);
}

Is there a way to re-write the WriteJson override not to add and remove Converters, avoiding this workaround altogether?

Thanks a lot @DalSoft! I'll look into it and see what I can do avoid the outlined workaround.


wip: employee checkin

Please provide enough information so that others can review your pull request:

Explain the details for making this change. What existing problem does the pull request solve?

Screenshots/GIFs

Pull Request Test Coverage Report for Build 935

0 of 6 (0.0%)  changed or added relevant lines in 1 file are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.006%) to 51.901%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

frappe/boot.py
0
6
0.0%

Files with Coverage Reduction
New Missed Lines
%

frappe/utils/change_log.py
3
21.53%

Totals

Change from base Build 933:
-0.006%

Covered Lines:
21705

Relevant Lines:
41820

💛  - Coveralls

@vishdha, rename this PR to suggest that we're changing how user timezones are loaded, the employee checkin fix can happen in the separate PR you've made at https://github.com/DigiThinkIT/erpnext/pull/360.

yup

Closing this for now, let's re-open if this comes up again


Repaired HTML5 build CI.


Changing Accuracy to Quality in screed-related files

See #685

@bocajnotnef Please bring this branch up to date

[ ] cut an RC for screed and publish to testpypi; update khmer's setup.py in refactor/acuqual to reference that URL
[ ] get this branch through code review
[ ] you or I will run the khmer acceptance tests at the point
[ ] then cut a screed release
[ ] finally update khmer's setup.py to point to the released version of screed (in a new PR)

How's this going?

Am working on it. Working on getting master merged in.

retest this please

restest this please

@mr-c CR, please

Overall LGTM, although I think merging #759 and #762 first would simplify things a bit, if we can manage it.  @mr-c shall I merge this PR, or what?

I'm not a big fan of the autopep8 stuff happening in the middle of the PR, but I guess it's in line
with the idea that we fix up files as we go.  So fine.

rretest this please

@mr-c @ctb CR?

Or are we still waiting for merges in other PRs?

I think we're waiting on either a review/merge from @mr-c, or a merge of #759 by @mr-c and then updating this.

Or, well, I guess I don't understand how we're dealing with the screed release, exactly.

@ctb I believe screed is waiting on a run of the khmer acceptance tests before screed v0.8 is released. Screed v1.0 is pending your API review.

@bocajnotnef Okay, khmer builds just fine with the new screed; time to run the acceptance tests
(which may be tricky if any of the eel-pond scripts need conversion as well)

I'm going to merge this as is and we'll update the setup.py file once the new version of screed is out.


Chaining animations ?

Is it possible to chain animations elegantly, while the following works, you have to nest this multiple times:
var animationEnd = 'webkitAnimationEnd mozAnimationEnd MSAnimationEnd oanimationend animationend';

$("body").animateCss("flip");
$("body").on(animationEnd, function () {
	$(this).animateCss("bounce");
});

I don't think there's an easy to achieve this. If you're chaining a lot of animations, there's a big chance you'd be better with an animation library like green sock or or velocity.

I use wowJS and play with the duration of the animation,
You can check the WOW page https://wowjs.uk/
If someone uses something different please let me know

@Legends @eltonmesquita see #678

Use promises. Works for me
example -
const bounceInImage = (image) => new Promise((resolve, reject) => {
  image.addClass('animated zoomIn').one(animationEnd, () => {
      image.removeClass('animated zoomIn');
  });

  setTimeout(() => {
    resolve(true);
  }, 100);
});

const showImages = () => {
  $('.round-image').parent().toArray().map((image)=>{
    return(()=>{
      return (bounceInImage($(image)));
    });
  }).reduce((pacc, fn) => {
    return pacc = pacc.then(fn);
  }, Promise.resolve());
}

I had to use animation-delay and chain 4 sets of animation.

As I think this is solved, with plenty of options, I'll close this. Let's keep the repo tidy.

I find this is a good solution:
https://codepen.io/austencm/pen/WvbwQa

@Skura23 do you have some example without JQuery?


MUI button weird behaviour when a MUI Dialog fired

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Steps:

Opening a MUI Dialog
Mui button changes its shape and color instantly

https://user-images.githubusercontent.com/60811247/206689669-508bceb8-7eda-4c4c-8e96-d61f08790580.mp4
Current behavior 😯
i'm expecting buttons shape and color stay like they are
Expected behavior 🤔
what i'm getting is a weird looking button
Context 🔦
i'm trying to open a Mui Dialog, but i noticed that all mui buttons in the same page change their shape and color to white instantly.

  Output from `npx @mui/envinfo` goes here.

It doesn't look like this bug report has enough info for one of us to reproduce it.
Please provide a CodeSandbox (https://mui.com/r/issue-template), a link to a repository on GitHub, or provide a proper minimal code example that reproduces the problem.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

Sandbox: https://codesandbox.io/s/github/darkpsinight/Facture and open client tab, you will see a Fab button there.

@darkpsinight I am getting errors in your CodeSandbox. First of all I added the missing react-polyfill package, then navigated to Clients from the top-left Hamburger menu which throwed an error.


Kubelet does not handle valid DNS subdomain names/namespaces correctly

This is forked from #3453.
Our documentation says that the name and the namespaces of a resource should be a valid DNS subdomain format: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/design/identifiers.md.
Multiple places in Kubelet use . as a delimiter, even though dot could be used in a valid name or namespaces. For example,
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/config/config.go#l342
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/types.go#l79
A more concrete example would be that kubelet won't be able to run the two pods below at the same time as they all resort to the same name:
name: xxx, namespace: yyy.zzz  -> xxx.yyy.zzz
name: xxx.yyy, namespace: zzz  -> xxx.yyy.zzz

Note that the full pod name <name>.<namespace>.<source> is used to construct the container name. As @thockin suggested in #3453, kubelet should switch to using underscore _ as the delimiter since it is not allowed in the DNS subdomain, but allowed in the docker container names. This change will not be backward compatible with existing container names.
Marking this P1 as this is a real bug.

We didn't fix this before is due to backward compatibility issue.

@dchen1107, it makes sense to me to fix this before v1.0 so that we could avoid hitting the compatibility issue further down the road.

Yes, we should fix it before 1.0. My point is that we should combine those destructive changes together and send one announcement to all users.

I am not sure if there are other destructive changes planned before 1.0, maybe some service related ones? cc/ @thockin

If this is just about bouncing containers I am not too concerned.
On Mon, Mar 2, 2015 at 11:48 AM, Dawn Chen<EMAIL_ADDRESS>wrote:

I am not sure if there are other destructive changes planned before 1.0,
maybe some service related ones? cc/ @thockin https://github.com/thockin
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4920#issuecomment-76797356
.

This is fixed by #5103


Deployment of css

It seems the guidelines lose the css file when being deployed. All the rules for attributeUsage, attributeDesc, etc. from the local build are missing online.

Related to #959
Will be (hopefully) fixed with the refactored build process.

Just double-checked again on the website, and it seems that rules for .specPage .attributeDef .attribute... are applied in the online guidelines.

@rettinghaus Can you please check if this is still an open issue and if so, provide an example where the CSS is missing?

Everything seems to be fine now. Maybe this was just an hiccup in the process …

Great, thanks!


Document how to use Elastic Search & MongoDB containers from uwazi-docker with non-containerized uwazi

The steps to run uwazi from host (e.g. developer machine) with dockerized Elastic Search + MongoDB where deleted on recent commits.
Since the docker plays even nicer for local development, let's document it again, and put here or at the huridocs repository.

TODO: report that yarn install step must be documented

Good catch! At some point when more stable, we can merge to official docs. Even the docker & docker-compose configs are on public domain (or MIT), so even if I get busy and can't anwser fast and there is sufficient people inside Uwazi to maintain updated huridocs not only could, but should copy even without  the need of asking first.
This also means for people who can use this uwazi-docker as base prepare for containerization other great humanitarian FOSS out there.

Also this tweet can make you and other people aware of what I will say
https://twitter.com/fititnt/status/987747799495213060
Simple reason is this: machine learning systems have much more documentation and tutorials based tech who could have a bad social impact (think Uberization of jobs, unethical mass surveillance, etc) than technology who could mitigate social issues caused by the exponential power of future intelligent systems.
Maybe I'm going too far about how to connect point A to point B, but I think one more more inexpensive way to empower a lot of HFOSS is abstracting part of it's complexity and give some quick starts for non-specialists in the software stack, but good at other tech. For example, a lot of machine learning software are written in Python, not in JavaScript (used in this case by Uwazi Software) so is more harder for expert volunteers help. Or maybe people on universities who could use Uwazi integrated with other systems for some published papers. Or people who could promote AI hackatons in the future and have a few softwares with some work already done, so instead of people writting hackaton code from scratch and never be used again, we could start have some better contributions.
Using Uwazi as example, it's stack also uses Mongo and Elastic Search, and for external people would be nice that uwazi-docker also gives some suggestion on GUI usages, so help on make easier #4 and #5 (thinking in the perspective of non Mongo / Elastic Search previous specialists) would also improve the quick start for possible researchers on the future (or improve chances about Uwazi being selected on AI Hackatons).
Will take some time to me discover other things that could be useful to add at the docker-compose.yml (for who does not know, is a file used for people just use a command to run additional software, e.g. that could allow people use software like Uwazi as part of some experiment platform). In general the people who work with artificial intelligence work do their jobs in softwares like Tensorflow / Theano /  Keras, but there are others less powerful but simpler to use to discover patterns without coding (or, if use code, platforms that are less complicated) and that could be embed on "toolkits" like a uwazi-docker draft.
In this case, Uwazi uses 2 databases, Mongo and Elastic Search. Some software who do some machine learning using these data storage or (maybe just other softwares who create nice dashboards based on statistics) could be embed and used without need of put "on the cloud" because even one old computer with 4 or 8GB of RAM could do the work locally (if have access to datasets). Since more HFOSS uses databases like Mongo and Elastic Search, the same knowledge and documentation can serve for multiple projects.
This repository have a public domain as default license on propose. Uwazi is just one of the software I'm looking on, but I'm doing this aiming smaller open source projects. Some of these projects embed some machine learning tools but do not document very well, and maybe some quickstarts or infrastructure as code to use as inspiration could foster results at scale.

@fititnt I'm not sure I'm fully following you, but I hope I can provide some useful information.
We are already working in parallel in machine learning implementations for Uwazi. Most of the research we are doing involves, NLToolkit, Fasttext, Word2Vec and Tensorflow. Everything is coded in python in the server side and we integrate it with Uwazi via an http API.
There is a branch of Uwazi with the prototype for the front-end: https://github.com/huridocs/uwazi/tree/ML. This is just a scaffolding for a future production ready feature, but so far so good. At the moment we are focusing in text classification, which comes very handy for tagging large datasets.
Next steps involve feature extraction and entity reconciliation.
As you mentioned in your twitter thread, the idea is to make this technology available for small organizations with limited resources, so they can achieve more with their data.

The pull request https://github.com/huridocs/uwazi/pull/2559 @vorburger and documentation of https://github.com/huridocs/uwazi#docker already do this.
Is possible to run docker both ways, but https://github.com/huridocs/uwazi is likely have far better documentation to run only the databases on docker while user can edit/contribute to huridocs/uwazi.
This could be documented on fititnt/uwazi-docker, but mostly would means just expose the ports, so not something really complex, so will not do it here.
Closing this issue now


Use git command instead of git2 in build script

This doesn't remove git2 from our dependencies (cargo and
crates-index-diff both use it), but it does simplify the build script.
r? @QuietMisdreavus

This is great but I am really wondering why you needed to change this portion of code. When I wrote this I assumed git might not be available in the machine this is running and that is why I used git2 crate instead of git command (same crate also used in cargo and crates-index-diff like you said).

IMO, the new code is somewhat simpler and easier for me at least to understand. I also hope that we'll eventually get to a point where we don't need to depend on Cargo directly and possibly even crates-index-diff can go away for some other way of getting a "new crates list" that doesn't need a git2 dependency; basically, I'm just removing a dependency that I don't think is necessary. The chances of someone building docs.rs without git are very slim IMO.

@Mark-Simulacrum are you still interesting in making this change? It looks good to me, it just needs to be rebased.

The chances of someone building docs.rs without git are very slim IMO.

Actually it would have to be even more of an edge case: you got the .git repo somehow without having git installed.
I do want to think about making it possible to build docs.rs without a git repo, using something like https://docs.rs/git-testament would abstract that a bit and give reasonable version numbers even without .git in the same directory. That doesn't have to go in this PR, just something to think about.

I don't have time right now to rebase this, but I think it would be a good change to make.
Feel free to close this, or I'll try to get to it sometime this week (or maybe on the weekend).

Going to close this since I don't feel that strongly about the change and you haven't had time to pick it back up. Feel free to reopen if you find the time :)


TO Go: check for missing cert files before starting

What does this PR (Pull Request) do?
Adds an informative message to traffic_ops_golang if either the cert file or key file are missing.

[x] This PR fixes #3479

Which Traffic Control components are affected by this PR?

CDN in a Box
Traffic Ops

What is the best way to verify this PR?
In an existing installation, modify /opt/traffic_ops/app/conf/cdn.conf.  The cert and key are specified in the hypnotoad.listen entry:
https://...?cert=/etc/pki/tls/certs/localhost.crt&key=/etc/pki/tls/private/localhost.key&...

Change the file names in that listen entry and restart traffic_ops.  traffic_ops_golang should produce an error message that the file doesn't exist and exit with a proper error code.
No changes in normal operation,  so no test or documentation or CHANGELOG needed
The following criteria are ALL met by this PR

[x] This PR includes tests OR I have explained why tests are unnecessary
[x] This PR includes documentation OR I have explained why documentation is unnecessary
[x] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[x] This PR includes any and all required license headers
[x] This PR ensures that database migration sequence is correct OR this PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3505/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3508/
Test PASSed.

I see your point..

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3510/
Test FAILed.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3512/
Test PASSed.


ColumnFacet on date fails

https://dux.fly.dev/parquet/geonames?_facet=updated_at

This might be OOMing due to 256mb on the free instance - check locally

Same root cause as #8


Support display formulas for values

In Palantir ontology xml they support various display formulas for multi-value properties

OBE... composite properties removes the need for this


TypeError: Cannot read properties of undefined (reading 'getSkin')

https://user-images.githubusercontent.com/38668796/144252476-e2183ad0-7324-4f16-8c7b-eec17f72773d.mp4

Thanks for the video, but I can not reproduce the issue.
I need a step-by-step sequence of actions to get to the issue. Good to also make sure it is reproduced in the demo app or provide a minimal code example.


Error in S4HANA Cloud ??

Hello ABAP Reference Scenario Team:
I've just pulled the latest version from the ABAP-platform-cloud branch to our S4HANA Cloud (2308) environment
I get these warning and active error.
Is this a issue?
Best Regards
Thank you so much.

Hi,
I have also tried to install it, there are some errors that occur and some objects that are missing. I have created the number range objects manually, but I am currently facing a problem:
In the class /DMO/CL_FLIGHT_DATA_GENERATOR it dumps when calling the badi /dmo/data_generation_badi.
These are the errors that occur for me.
Thank you and best regards
Adalbert

Hi,
thanks for reporting this. We have updated the cloud branch. Please pull and activate again.
Best regards
Georg

HI Georg
Thanks for your reply.
Pull the repo again and create the simple type , it is OK.
Thank you so much.


[irq] Disable irq if do_schedule() just returned in irq_resched()

Hi @vvaltchev
In irq_resched(),  if do_schedule() just returned, then irq_entry() will return with interrupts enabled! This doesn't seem to cause any problems with the i386 architecture. But for developers trying to port tilck to other architectures, they often assume that the interrupt is off when irq_entry() returns. Therefore, disable interrupts here to avoid causing confusion for developers.

Thanks for the fix, @aenrbes. Yes, it makes perfectly sense to make that symmetric.
I guess that was a leftover from the past when do_schedule() never returned. The function just did a full context switch to the same task, if necessary.


fix closes #6 Removed offending test because referenced data file got lost

Also added -v to the test target to see which test fails.

I added the same changes but left the test commented instead of fully removing, so one can scan the TODOs in the repo later.


wrong description on readme and NPM page.

Usage -> Options ->
interruptStep default to 0, not 1000.

Thank you! I'll close this issue once I publish the updated README to NPM.

Published v1.3.1. Thanks again!