RLIMIT_NOFILE

In Sep of 2021, with two commits, the liburing project added support to automatically try to increase the soft RLIMIT_NOFILE when its API functions hit the EMFILE error - there were two such API functions at the time. Since then, additional API functions have been added and each has also performed the same check against EMFILE and tried one time to increase the limit before having to return EMFILE to the caller.
Should this crate assume the same role in trying to increase the soft limit when EMFILE is encountered?

I would like to soon provide a PR for the multishot accept operation and it would be nice to support the multishot accept direct operation as well, and so having a large sparse direct fd table setup could be quite common and hitting the soft RLIMIT_NOFILE seems more likely.

@FrankReh I'd say we should, conditional on a builder flag. I think we could let that flag be default though.

@quininer What's your read on this? Would a PR that did this with a builder flag be acceptable?


adjust typescript definition for fromJson and fromDatabaseJson

Split the FromJsonMethod interface into FromJsonMethod and FromDatabaseJsonMethod.
The new FromJsonMethod parameter now accepts the additional ModelOptions argument.
The new FromDatabaseJsonMethod interface is the same as the old FromJsonMethod.

Coverage decreased (-0.1%) to 97.015% when pulling 75e033fd893b8c0be504734d52b4ff23516d969a on jamespedid:fix/adjust-from-json-typescript into 9acd51afc4d1eed9dcfcd28c7f75bc4567c4564e on Vincit:master.

Thanks!


Encrypt bootstrap and direct connections

Basically what it says on the tin.
Also, worth mentioning that currently service discovery test is disabled, because it would be failing otherwise.
This will be fixed once encryption is implemented for service discovery.

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


Improve generic error handling

There have been issues with the "Log In" button in the popup being unresponsive.  I still have this problem, https://github.com/solid/node-solid-server/issues/884 and others had this problem due to an expired cert.
There should be some kind of feedback to the user in this situation, at least an error that they can go to the forum about. Perhaps there should even be a forum link in the error message if it is very generic?

I think the problem is that the feedback never reaches the client code. Fetchers in the browser are not allowed to see many details about request failures, as these can be exploited.
But I can probably set a timeout that results in an error message.
Can someone post exact steps to reproduce?

Hmmm, but in my case, it happens without any network interaction, and it only happens on my laptop, so it is clearly highly environment dependent...  Awfully hard to reproduce... I'll tinker with some plugins and see if that matters, at least.
In JD's case, they had an invalid cert on the WebID provider. Presumably, it can be reproduced simply by having that. These are two very different bugs, but I was hoping there could be some generic fallback error handling...


refactor: avoid using important rule in utility classes

By nature, CSS utility classes should not use an important rule, because they serve as a shorthand way to add CSS declarations. Therefore, we are better removing this unnecessary rule, which has no effect to final result. At least, nothing will change in Infima/Docusaurus styles after that.

No I think we should keep it. When I use a utility class, I expect the
styling to be applied. If you remove the important, classes with higher
specificity might win and make the utility class useless.
FWIW, Bootstrap does this.
On Tue, Jul 13, 2021, 6:46 PM netlify[bot] @.***> wrote:

✔ Deploy Preview for infima ready!
🔨 Explore the source changes: cea3bfe
https://github.com/facebookincubator/infima/commit/cea3bfe08fb3ae6f27b958b343d19018c61d8e24
🔍 Inspect the deploy log:
https://app.netlify.com/sites/infima/deploys/60ed6e945bb904000727dfee
https://app.netlify.com/sites/infima/deploys/60ed6e945bb904000727dfee?utm_source=github&utm_campaign=bot_dl
😎 Browse the preview: https://deploy-preview-154--infima.netlify.app
https://deploy-preview-154--infima.netlify.app?utm_source=github&utm_campaign=bot_dp
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/facebookincubator/infima/pull/154#issuecomment-878982187,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKBCHO2XB7P47LAAMEJL5LTXQKQRANCNFSM5AIZZQCA
.

On the one hand this makes sense, but for example Tailwind does not use important rule in their numerous utility classes. In our case it is also completely unnecessary, only complicates CSS code and increases CSS bundle in vain.
Think that important rule should be used wisely, and in small framework like Infima, which is basically designed to work with Docusaurus, using an important rule seems like completely unnecessary thing. But okay, I'll close it.

Glad I'm not crazy in my reasoning. Tailwind doesn't need important because
all the classes are utility classes with the same specificity. In
Infima/Bootstrap, people can combine normal CSS classes with utility
classes and there will be specificity wars. So using important is the right
way to go for our way of writing CSS.
On Wed, Jul 14, 2021, 2:44 AM Alexey Pyltsyn @.***>
wrote:

Closed #154 https://github.com/facebookincubator/infima/pull/154.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebookincubator/infima/pull/154#event-5015681677,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKBCHMRKNKPLKNSEUOWQLLTXSCPTANCNFSM5AIZZQCA
.


Add GitLab CI/CD

In GitLab by @arisilon on Oct 16, 2019, 13:54

In GitLab by @arisilon on Oct 22, 2019, 10:31
mentioned in commit 4fb8b8e34dc4e5f962404f27d0614f90e27de31d

In GitLab by @arisilon on Oct 21, 2019, 16:56
mentioned in commit d6d0974abb862834fab546a8186e28cf6c0fd59b

In GitLab by @arisilon on Oct 21, 2019, 17:28
mentioned in commit b7d5bdbedd4e5ef07021f0e40adb840f300fe773

In GitLab by @arisilon on Oct 16, 2019, 16:57
mentioned in commit af91079018858d54afb333146c2c5636c7f4f221

In GitLab by @arisilon on Oct 21, 2019, 17:14
mentioned in commit 3cd980cc9d753d4c3c6a0b31217e8d8f0d9f6511

In GitLab by @arisilon on Oct 22, 2019, 14:19
mentioned in commit 9ba86d197b621c5516007ffc2281116ced40a9d2

In GitLab by @arisilon on Oct 22, 2019, 11:17
mentioned in commit 6c8e870e50819e5c1bb3c7f2f30848fb3b05d249

In GitLab by @arisilon on Oct 22, 2019, 11:30
mentioned in commit 8a7bce3ce0c5017771d6b14a9188e80a04fb0994

In GitLab by @arisilon on Oct 22, 2019, 10:56
mentioned in commit 56e412e31edb426618528d392e63f2c2f75a2cf9

In GitLab by @arisilon on Oct 22, 2019, 11:28
mentioned in commit e441c21cf77346ba9904011073b457d2b368a615

In GitLab by @arisilon on Oct 22, 2019, 16:38
mentioned in commit 456bcc0acaf64f99f0a00da964675aeb1a5c1e78

In GitLab by @arisilon on Oct 22, 2019, 15:48
mentioned in commit 3eb76ef7f657ed3e6830375e984ef207643269ce

In GitLab by @arisilon on Oct 22, 2019, 16:25
mentioned in commit 21632371d0b1e0056bb284c36d08daefc206fa1b

In GitLab by @arisilon on Oct 22, 2019, 16:15
mentioned in commit bd354e37750e6cc3ad16477856bd3f79d27cc034

In GitLab by @arisilon on Oct 22, 2019, 16:20
mentioned in commit ebf44a035432b1c083614a2b34bdb9255b175263

In GitLab by @arisilon on Oct 22, 2019, 16:52
mentioned in commit 8dc7c36f9b6cb9dcabc13f9a5822fd3355d8e144

In GitLab by @arisilon on Oct 22, 2019, 17:00
mentioned in commit 5744fd2ec82b14b377e0207035702efacc363bd4

In GitLab by @arisilon on Oct 22, 2019, 19:18
mentioned in commit a68ce9d49ee3b43e64c8aee24ec318e116fb277b

In GitLab by @arisilon on Oct 22, 2019, 19:05
mentioned in commit 4dfd17bd4f11c2dc68d4ad560a0f923b8a4ae64f

In GitLab by @arisilon on Oct 22, 2019, 18:55
mentioned in commit db408656e8e1ca59af4f5d56b4fcbcdd1e248459

In GitLab by @arisilon on Oct 22, 2019, 21:58
mentioned in commit 70e68e474a51e7a01983b4b5b1729c75c61fb1b8

In GitLab by @arisilon on Oct 22, 2019, 20:15
mentioned in commit 133d901accf11b3b1f30b9d8c6e6ab6fcfd648e8

In GitLab by @arisilon on Oct 22, 2019, 21:07
mentioned in commit 859b6588f2233f4ba72b6ab4acf9ae33ca6f2bf1

In GitLab by @arisilon on Oct 22, 2019, 19:38
mentioned in commit 380f05f55a74c9fcae5baa2805abf5f8bef20ce1

In GitLab by @arisilon on Oct 22, 2019, 22:10
mentioned in commit c86721cadb7bf8e681a2ce4a6e9efe6505ed5772

In GitLab by @arisilon on Oct 22, 2019, 22:13
mentioned in commit c5f1335eea21b09779c46541aebc0d821002cf85

In GitLab by @arisilon on Oct 23, 2019, 09:00
mentioned in commit 535630d3d7b1c115ea783c5381bc6849a0805f90

In GitLab by @arisilon on Oct 23, 2019, 09:46
mentioned in commit 1ec2cea8a80a659f6405cf5c79ccc15b15cd9e49

In GitLab by @arisilon on Oct 23, 2019, 09:14
mentioned in commit aa509f364c6c10cc6d7e748f6626130d4fe1db1f

In GitLab by @arisilon on Oct 23, 2019, 08:34
mentioned in commit ee0239e89a193ef7cde1c5e7a2cf474c1c1a1456

In GitLab by @arisilon on Oct 23, 2019, 08:30
mentioned in commit b998e187aec66e904783ca23f9c18ad845480886

In GitLab by @arisilon on Oct 23, 2019, 16:46
mentioned in commit 7c7d44ab83af3af7fbcde04b52e797228ac76b8d

In GitLab by @arisilon on Oct 23, 2019, 21:52
mentioned in commit 6e1bab32c003333ceac878ed1a155a6849d3c1a2

In GitLab by @arisilon on Oct 23, 2019, 17:14
mentioned in commit d4839c4e3b19fa0f61f1559423e438d9a870ae38

In GitLab by @arisilon on Oct 23, 2019, 16:59
mentioned in commit 617bb02c6276f65d60adbcf6122ca0bad3dc275d

In GitLab by @arisilon on Oct 23, 2019, 21:52
mentioned in commit 26b8fb3ca6c0f5ab0f7e967a2b400524dcc35bd4

In GitLab by @arisilon on Oct 24, 2019, 10:39
closed

In GitLab by @arisilon on Oct 23, 2019, 22:16
mentioned in commit 4bb7357e490184411d58f2a4633bd0f24a4a4324


Can't add images to Github wiki

This issue is opened, so we can host images for the Wiki. To host an image, add/edit a comment and include an image. Then grab the image URI and include in the Wiki.

Closing as this "issue" doesn't need to be open to host the images. Carry on adding images as needed.


NFT #0: update metadata file and upload to arweave: links to art, percentages, description

NFT #0
50% Sammie
40% MOI
10% PA

https://github.com/PrisonArt/restore/commit/2d3bae1f3ee6dd40b37aaae36b059c895b91ae7d as well as #15


Created new file GO File Format Guide

Is this different from  go-docs/docs/_docs/go-file-format-guide.md ?

Yes ! sorry about that


1-based indexing should be emphasised in syntax-intro

I will emphasize this issue when talk about the string and array/matrix/vector.


Change User Pool In Android Application

I am trying to integrate amplify in my application to authenticate user. I have already created user pool and I would like to change the user pool but when I change the configuration in

awsconfiguration.json

and run a command amplify push or amplify pull it will change the keys to default.
Related: https://github.com/aws-amplify/aws-sdk-android/issues/1739
Check the related issue one of your team member said I am transferring this issue to cli team
Amplify CLI Version
4.20.0
What AWS Services are you utilizing?
Cognito Pool using with Amplify
awsconfiguration.json
{         "CognitoUserPool": {         "Default": {             "PoolId": "xxxxxxxxxxx",             "AppClientId": "xxxxxxxxxxxx",             "AppClientSecret": "xxxxxxxxxxxxxxxxx",             "Region": "xxxxx"         }     },     "Auth": {         "Default": {             "authenticationFlowType": "xxxxxx"         }     } }

Hello @FazalHussain
Currently the CLI does not support importing existing UserPools, though you can manually configure the UserPool. Docs here: https://docs.amplify.aws/sdk/auth/getting-started/q/platform/android#manual-setup
The use case of importing a resource such as a UserPool is something we are currently looking into please follow the RFC for updates.
RFC: https://github.com/aws-amplify/amplify-cli/issues/3977


Super call of non-method disallowed for static field disallowed unnecessarily

Bug Report
🔎 Search Terms
Only public and protected methods of the base class are accessible via the 'super' keyword.
static getter, setter, field, property
🕗 Version & Regression Information
Repro'd in stable, nightly, and TS 3.3.3

This is the behavior in every version I tried, and I reviewed the FAQ for entries about super.

⏯ Playground Link
Playground link with relevant code
💻 Code

export {};

class SuperClass {
  static get styles() {
    return ['style'];
  }
}

class ChildClass extends SuperClass {
  static get styles() {
    return [...super.styles, 'additional style'];
  }
}

console.log(ChildClass.styles) // logs [['style'], 'additional style'] as expected

🙁 Actual behavior
When targeting ES5 we get the diagnostic Only public and protected methods of the base class are accessible via the 'super' keyword. on the super.styles.
This is a good diagnostic for the non-static case, because if super.styles was a property rather than an accessor then it probably wouldn't be accessible, as SuperClass.prototype.styles because it would be initialized in the constructor.
However a static field can reasonably be expected to have been initialized, and to be accessible at SuperClass.styles regardless of whether it's a property or an accessor.
🙂 Expected behavior
This should be allowed for static getters, as we have the super class object that we can access (unlike the non-static case, where we can't necessarily get at the original field if it wasn't a getter).

Related to #338, but this issue is only concerned with static fields, where the concerns from that issue do not apply.


Safe chain node

It allows not to breck all chain execution by exception in a single node.
The PR was done on top of chain-node-push #45. So please review\approve that first.

Approved


Build on Appveyor using Autotools

Need to add a configuration to appveyor that runs a MinGW build using autotools.

Am I right that the cmake build which was merged is 32 bit?
I think we should have at least one Windows 64 bit build (and the Cmake MinGW build seems a good candidate) because weird things can happen with I32L32P64 that none of the other builds will pick up.

Sorry for venting my feelings against that architecture ;-). I do think CppUTest needs to be tested against it, though

Right, the later changes that got merged after your PR was to make it  32bit.  I've been working on having both builds included, and should have a pull request soon.

@Andne Hi Andy, I was just updating the VC projects to match our latest pull when I notice problems with building the Debug configuration. Isn't this included in the Appveyor build? Shouldn't we have both Release and Debug configurations built (or get rid of one?), in order to avoid this kind of bad surprise?
For example, way back in 3.7.2 I noticed that the Debug build is trying to link the release library in VC60.

I think I may have asked about Release vs. Debug at one point.  It wouldn't take much to run both through Appveyor.  I don't remember what I did by default though, if it was both configurations or just one (Guessing the later based on what you're seeing).
So, what do you think - should we have a Debug and Release build, or strip one out and have a Release build only?  The biggest challenge with the two is which version of the C library to link against, because if CppUTest doesn't agree with the code that's under test, it tends to cause some warnings.  I think I tried to look for how to avoid that, but I didn't find anything obvious or simple.

I guess if we can run both in Appveyor, I would prefer doing so. I fixed the libraries in the .dsp, however, for the life of me I can't find where the libraries are defined in the 201x version. They both link the Debug version (which seams to be the lesser evil) but I don't see it specified anywhere. It seems to come from the "Defaults", but where do the "Defaults" come from?

This is done and can be closed, right?

MinGW on AppVeyor is alive and kicking :D. Apart from the occasional hickup....


Bluetooth: Host: bt_le_oob_get_local gives incorrect address

bt_le_oob_get_local gives incorrect address when using the extended advertisement code paths. (i.e. (IS_ENABLED(CONFIG_BT_EXT_ADV) && BT_DEV_FEAT_LE_EXT_ADV(bt_dev.le.features)) is true.)
Originally posted by @joerchan in https://github.com/zephyrproject-rtos/zephyr/discussions/50967#discussioncomment-3850650
When you start an advertiser using the legacy API (bt_le_adv_*) then the OOB information is provided by bt_le_oob_get_local
When you start an advertiseng using the extended API then the OOB informartion is provided by bt_le_ext_adv_oob_get_local.
The new bug now is that bt_le_oob_get_local does not return the RPA address of the advertiser.
You can verify this bug like this:
west build -b nrf52840dk_nrf52840 tests/bluetooth/shell  -- -DCONFIG_BT_PRIVACY=y -DCONFIG_BT_LOG_SNIFFER_INFO=y -DCONFIG_BT_RPA_TIMEOUT=30
Using the nRF Sniffer for Bluetooth LE.
Add the printed IRK to the sniffer, and select follow IRK.
uart:~$ bt advertise on
Advertising started
[00:00:10.378,570] <inf> bt_id: bt_id_set_adv_private_addr: RPA: 5E:0B:7D:F9:9A:D1
uart:~$ bt oob
OOB data:
addr                          random                           confirm
   4E:44:19:A9:44:12 (random) 015ce2d5e52416dfc3f54a562822b10d c47cb850fd05737e21eb502cd65c8003
[00:00:23.610,137] <inf> bt_id: bt_id_set_adv_private_addr: RPA: 6D:28:FE:FE:A3:61
[00:00:23.610,717] <inf> bt_id: bt_id_set_private_addr: RPA: 4E:44:19:A9:44:12

The advertiser starts using 5E:0B:7D:F9:9A:D1. When calling bt_le_oob_get_local it returns 4E:44:19:A9:44:12 (random), but is advertising using 6D:28:FE:FE:A3:61.
On zephyr 3.0.0 release this works as expected.
Reverting the fix https://github.com/zephyrproject-rtos/zephyr/commit/6c40427931dba65092d0eb050a2ed7e9e8069845 shows that the RPA is not updated, neither on calling bt_le_oob_get_local, or on an RPA timeout.

Course of action, in a PR revert 6c40427931dba65092d0eb050a2ed7e9e8069845 and fix the changes to le_rpa_invalidate that was done in 4e924b6b1f4d8c9acd3fe2501b06572ddf4d4ed3


Xamarin.Forms

May I ask about why does not had Xamarin.Forms?

Hi @cheahengsoon. We had decided to only go with Xamarin Native implementation for this particular sample. However, we will consider working on a Xamarin.Forms sample in the future. The point of this sample is to show that you can use the Azure Storage library in a Xamarin app (native or forms). So any Azure Storage code you see in this app can be applied to a Xamarin.Forms app :)


Move elasticsearch with data to the cloud

Move elasticsearch with all indexed data to the cloud so we can all try different queries, etc.

There's a way to move the index around, without need to reindex the docs.
E.g. Wikipedia ElasticSearch indexes are available at https://dumps.wikimedia.org/other/cirrussearch/

That's good to know, thanks. Unfortunately, it takes 10x to transfer our 40GB index than to reindex all documents...

Fixed?


Reset Level upon Ball death

Currently a big problem with our test level is the inability to restart when the ball has died, which is when it all should end because you can't continue without a ball.
Workaround for this is to refresh or start the application itself, which will not be accepted.
To do this there are several ways to do it we need to look over, biggest being how we know when the ball has died. We want to remember the rules of OOP and not create hard-coded dependencies breaking these. Valid ways we can do this is through dependency injection, and Godot signals. For now it's okay to create a loose dependency where only the parent is dependent on its children but NOT vice versa.
More on signals: https://docs.godotengine.org/en/stable/getting_started/step_by_step/scripting.html
The much prefered Dependency Injection does not have a designated documentation. But the best way to do it in Godot is export it with NodePath type and through the editor a new property is shown where you can drag in the Node. To get access to the Node you need to GetNode() with the path. Here exporting can be seen: https://godotengine.org/qa/51552/export-custom-type-variable-on-inspector-mono-c%23
The next step is deleting the Level1 instance, and adding a new one as a child to Game, which can be seen done here
Lastly a initial velocity must be added like done in _Ready here

For a working example of Dependency Injection currently in our game see b3f1eb80aee46ba6513904d6aabcad9d200e5849.


KYLIN-4128 Remove never called methods

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6668b0d). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #794   +/-   ##
=========================================
  Coverage          ?   25.74%
  Complexity        ?     6049
=========================================
  Files             ?     1394
  Lines             ?    83082
  Branches          ?    11629
=========================================
  Hits              ?    21388
  Misses            ?    59643
  Partials          ?     2051

Impacted Files
Coverage Δ
Complexity Δ

...ain/java/org/apache/kylin/job/JoinedFlatTable.java
0% <ø> (ø)
0 <0> (?)

Continue to review full report at Codecov.

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

Pull Request Test Coverage Report for Build 4852

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.004%) to 28.215%

Files with Coverage Reduction
New Missed Lines
%

core-cube/src/main/java/org/apache/kylin/cube/inmemcubing/MemDiskStore.java
3
78.42%

Totals

Change from base Build 4849:
0.004%

Covered Lines:
23442

Relevant Lines:
83082

💛  - Coveralls


Increase waiting time for protocols to 30 seconds

Quite often, it takes 15 or 20 seconds for the CQL binary protocol to start listening when starting a node. I thought about adding a --protocol-wait-timeout option but I think the added value is very limited. Simply increasing the timeout to 30 seconds will probably handle most cases.

Actually, a configurable value is probably more future-proof.


Refinements in constructors

See:
https://github.com/UCSD-PL/RefScript/blob/master/tests/todo/ref-in-constructor.ts

Ooops, just fixed.


Blooket username

AsianBubu

Gh0sty33

Ronaldofordayzz

Ronaldofordayzz

i know its cringe but this is my alt

what is this for
On Sat, Mar 30, 2024 at 9:56 PM ronika1335 @.***> wrote:

Ronaldofordayzz
i know its cringe but this is my alt
—
Reply to this email directly, view it on GitHub
https://github.com/mrmojololo/blooket-admin-hack/issues/803#issuecomment-2028526700,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4OUUW5URUXH6SLQLIQSD43Y25UKXAVCNFSM6AAAAABFPCBO4CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYGUZDMNZQGA
.
You are receiving this because you commented.Message ID:
@.***>


Support custom tips/warnings at Markdown

Sometimes you may want to use special emphasis for tips/warnings. I've settled for T> and W> for these purposes. Basically I style these cases differently. Here's my implementation you could consider plugging in.
It actually would be enough for me if you could expose marked enough so that I can do these kind of hacks in the user space. You might not want all of this in the core.

For that we have the Hint Specimen 🙂


refactor: modified codes for student and parent views, added url for schools views,  modiied documentation

Please review my code.

All modifications requested from previous OR has been rectified and new updates included in current PR


buildGoModule appears to fail to find a mod file, even when the go build/go install/go mod download works

Describe the bug
I'm using the latest Nixos Unstable revision: d942688fc137169b577e7bf0c09e01a2ac919b73.
My go project located here: https://github.com/MatrixAI/Golang-Demo. Is just a basic Go project that brings in 1 dependency:
require github.com/pelletier/go-toml v1.6.0

It then has a number of subpackages, and a main.go that just outputs some hello world outputs and calculations.

However if I try to use goBuildModule to build, I end up with:
these derivations will be built:
  /nix/store/93ldirdj463bmpvj6aq0lc169mi6n849-golang-demo-0.0.1.drv
building '/nix/store/93ldirdj463bmpvj6aq0lc169mi6n849-golang-demo-0.0.1.drv'...
unpacking sources
unpacking source archive /nix/store/hnzl2wdcbyljzrr97nkd19bj022zxnla-Golang-Demo
source root is Golang-Demo
patching sources
configuring
building
Building subPackage .
go<EMAIL_ADDRESS>reading<EMAIL_ADDRESS>Not Found
builder for '/nix/store/93ldirdj463bmpvj6aq0lc169mi6n849-golang-demo-0.0.1.drv' failed with exit code 1
error: build of '/nix/store/93ldirdj463bmpvj6aq0lc169mi6n849-golang-demo-0.0.1.drv' failed

I tried with other version of go-toml, but the same problem occurs.
To Reproduce

git clone https://github.com/MatrixAI/Golang-Demo.git
cd Golang-Demo
nix-build ./release.nix --attr application

Expected behavior
It should just build result symlink with bin/Golang-Demo.
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 4.19.80, Formbay ML 2 A, noversion`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3`
 - channels(root): `""`
 - nixpkgs: `/etc/nixos/nixpkgs`

It turns out that the reason for this failure is because the modSha256 was wrong. I updated the modSha256 and the nix-build started to work again. Which is strange cause Nix never complained about modSha256. I don't think this goBuildModule is the most robust system, there seems to be impurities in it.
Anyway this is fixed now.

@CMCDragonkai This is actually still an open issue (which I can reproduce), since buildGoModule indeed does not point out that the hash is wrong.

Can confirm that this is unfortunately still an issue, was helping out a person on the CNCF slack who couldn't get argo running because it was complaining about a missing go.mod file.
I suggest this be reopened @r-ryantm

I'm running into the same problem with this build
It has pkgs.lib.fakeSha256 set, but does not compain about it being wrong. Instead when running nix buil it fails with:
caddy> go: downloading github.com/mgutz/ansi v0.0.0-20200706080929-d51e80ef957d
caddy> go: downloading github.com/go-logfmt/logfmt v0.6.0
caddy> go: downloading github.com/shurcooL/sanitized_anchor_name v1.0.0
caddy> go: downloading github.com/mattn/go-colorable v0.1.13
caddy> go: downloading github.com/mattn/go-isatty v0.0.19
caddy> internal error: failed to find embedded files of github.com/Microsoft/go-winio: //go:build comment without // +build comment
error: builder for '/nix/store/q71lfphwj6b5lymn7g4xg0hpmpgxph53-caddy-20231004-go-modules.drv' failed with exit code 1;
       last 10 log lines:
       > go: downloading github.com/jackc/pgservicefile v0.0.0-20221227161230-091c0ba34f0a
       > go: downloading github.com/golang/snappy v0.0.4
       > go: downloading github.com/golang/glog v1.1.2
       > go: downloading github.com/jackc/chunkreader/v2 v2.0.1
       > go: downloading github.com/mgutz/ansi v0.0.0-20200706080929-d51e80ef957d
       > go: downloading github.com/go-logfmt/logfmt v0.6.0
       > go: downloading github.com/shurcooL/sanitized_anchor_name v1.0.0
       > go: downloading github.com/mattn/go-colorable v0.1.13
       > go: downloading github.com/mattn/go-isatty v0.0.19
       > internal error: failed to find embedded files of github.com/Microsoft/go-winio: //go:build comment without // +build comment
       For full logs, run 'nix log /nix/store/q71lfphwj6b5lymn7g4xg0hpmpgxph53-caddy-20231004-go-modules.drv'.
error: 1 dependencies of derivation '/nix/store/xwf8sz0fxhg3685d8afswx627dfxkdix-caddy-20231004.drv' failed to build

This seems to be working fine for vendorHash = lib.fakeHash. Has anyone a reproducer for this on master?

This always happens when the hash is wrong, I've taken to manually keeping the nix file up to date for myself.
We need some way of automating this process though, or perhaps agreeing to a weekly/monthly cadence of updating the nix file.

Its a bit difficult to keep dependencies up to date because of dependabot (which doesn't update Nix deps)


False positive response to Cyrillic characters in a string

Description
faced with a problem when such a fragment  "являются не" in Cyrillic is added to the feedback form, the 941120 rule is triggered, and the server gives the 403 code.
how to fix the problem
Logs
2023/03/27 12:29:12 [warn] 3521#3521: *461 ModSecurity: Warning. Matched "Operator `Rx' with parameter `(?i)[\s\"'`;/0-9=\x0B\x09\x0C\x3B\x2C\x28\x3B]on[a-zA-Z]{3,25}[\s\x0B\x09\x0C\x3B\x2C\x28\x3B]*?=[^=]' against variable `ARGS:message' (Value: `\xd1\x8f\xd0\xb2\xd0\xbb\xd1\x8f\xd1\x8e\xd1\x82\xd1\x81\xd1\x8f \xd0\xbd\xd0\xb5' ) [file "/opt/bunkerweb/core/modsecurity/files/coreruleset/rules/REQUEST-941-APPLICATION-ATTACK-XSS.conf"] [line "89"] [id "941120"] [rev ""] [msg "XSS Filter - Category 2: Event Handler Vector"] [data "Matched Data: ;ONBAO =5 found within ARGS:message: O2;ONBAO =5"] [severity "2"] [ver "OWASP_CRS/3.3.2"] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-xss"] [tag "paranoia-level/2"] [tag "OWASP_CRS"] [tag "capec/1000/152/242"] [hostname "<IP_ADDRESS>"] [uri "/mail.php"] [unique_id "167992015240.544431"] [ref "o2,9v1577,21t:utf8toUnicode,t:urlDecodeUni,t:htmlEntityDecode,t:jsDecode,t:cssDecode,t:removeNulls"], client: <IP_ADDRESS>, server: www.example.com, request: "POST /mail.php HTTP/1.1", host: "site.ru", referrer: "http://site.ru"
mybunker_1  | 2023/03/27 12:29:12 [error] 3521#3521: *461 [client <IP_ADDRESS>] ModSecurity: Access denied with code 403 (phase 2). Matched "Operator `Ge' with parameter `5' against variable `TX:ANOMALY_SCORE' (Value: `5' ) [file "/opt/bunkerweb/core/modsecurity/files/coreruleset/rules/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "80"] [id "949110"] [rev ""] [msg "Inbound Anomaly Score Exceeded (Total Score: 5)"] [data ""] [severity "2"] [ver "OWASP_CRS/3.3.2"] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "<IP_ADDRESS>"] [uri "/mail.php"] [unique_id "167992015240.544431"] [ref ""], client: <IP_ADDRESS>, server: www.example.com, request: "POST /mail.php HTTP/1.1", host: "site.ru", referrer: "http://site.ru/"
Your Environment
OWASP_CRS/3.3.2
(tag:'paranoia-level/2',)
ModSecurity version (e.g., 2.9.6):
Operating System and version: ubuntu 22.04

Hi,
Firstly, it appears that you're running CRS version 3.3.2. You should strongly consider updating to the latest stable release, which is v3.3.4, as that fixes several security vulnerabilities (see here and here for more information.)
Secondly, have you tuned the Core Rule Set for your web application? It looks like you're running with an inbound anomaly score threshold of 5, which is not a good idea unless you have completed the full tuning process - because otherwise you are highly likely to run into false positives like the one you've reported here!
Lastly, let's look at the false positive you've reported. Unfortunately, this is an example where a CRS rule can take valid UTF-8 and its anti-evasion transformations turn that UTF-8 into rubbish. The problem is that the transformed rubbish can sometimes trigger the rule, which is the case here:
Input: являются не
Transformation - UTF-8 to Unicode: "%u044f%u0432%u043b%u044f%u044e%u0442%u0441%u044f %u043d%u0435"
Transformation - Decode percent-encoded string and accept Microsoft %uXXXX variant: "O2;ONBAO =5"

;ONBAO =5 looks a bit like onload="alert(1)" and matches the pattern of this particular anti-XSS rule.

Solution
You'll need to tune this false positive away by creating a rule exclusion.
Full documentation can be found here. Be sure to check out the examples at the bottom: they're very helpful.
Please let us know if you need any further help with this and we can assist further.

thank you for such a detailed answer. to make an exception, I need to add this expression SecRuleUpdateTargetById 941120 "!ARGS: являются не"
am I right? or is there a more flexible solution ?

Hi @flexstat,
Firstly, it appears that you're running CRS version 3.3.2. You should strongly consider updating to the latest stable release, which is v3.3.4, as that fixes several security vulnerabilities (see here and here for more information.)
Secondly, have you tuned the Core Rule Set for your web application? It looks like you're running with an inbound anomaly score threshold of 5, which is not a good idea unless you have completed the full tuning process - because otherwise you are highly likely to run into false positives like the one you've reported here!
Lastly, let's look at the false positive you've reported. Unfortunately, this is an example where a CRS rule can take valid UTF-8 and its anti-evasion transformations turn that UTF-8 into rubbish. The problem is that the transformed rubbish can sometimes trigger the rule, which is the case here:
Input: являются не
Transformation - UTF-8 to Unicode: "%u044f%u0432%u043b%u044f%u044e%u0442%u0441%u044f %u043d%u0435"
Transformation - Decode percent-encoded string and accept Microsoft %uXXXX variant: "O2;ONBAO =5"

;ONBAO =5 looks a bit like onload="alert(1)" and matches the pattern of this particular anti-XSS rule.
Solution
You'll need to tune this false positive away by creating a rule exclusion.
Full documentation can be found here. Be sure to check out the examples at the bottom: they're very helpful.
Please let us know if you need any further help with this and we can assist further.
(P.S. If it were me, I would personally be tempted to tune this away by excluding ARGS:message from rule 941120 for the location in question, which I'm guessing is /mail.php).

hi

Hi @flexstat,
Firstly, it appears that you're running CRS version 3.3.2. You should strongly consider updating to the latest stable release, which is v3.3.4, as that fixes several security vulnerabilities (see here and here for more information.)
Secondly, have you tuned the Core Rule Set for your web application? It looks like you're running with an inbound anomaly score threshold of 5, which is not a good idea unless you have completed the full tuning process - because otherwise you are highly likely to run into false positives like the one you've reported here!
Lastly, let's look at the false positive you've reported. Unfortunately, this is an example where a CRS rule can take valid UTF-8 and its anti-evasion transformations turn that UTF-8 into rubbish. The problem is that the transformed rubbish can sometimes trigger the rule, which is the case here:
Input: являются не
Transformation - UTF-8 to Unicode: "%u044f%u0432%u043b%u044f%u044e%u0442%u0441%u044f %u043d%u0435"
Transformation - Decode percent-encoded string and accept Microsoft %uXXXX variant: "O2;ONBAO =5"

;ONBAO =5 looks a bit like onload="alert(1)" and matches the pattern of this particular anti-XSS rule.
Solution
You'll need to tune this false positive away by creating a rule exclusion.
Full documentation can be found here. Be sure to check out the examples at the bottom: they're very helpful.
Please let us know if you need any further help with this and we can assist further.
(P.S. If it were me, I would personally be tempted to tune this away by excluding ARGS:message from rule 941120 for the location in question, which I'm guessing is /mail.php).

hello again @RedXanadu . can you help and answer my questions above ?

Hi @flexstat,
The first step, find the offending variable. Looking at your log snippet:
ModSecurity: Warning. Matched "Operator `Rx' with parameter `(?i)[\s…\x3B]*?=[^=]' against variable `ARGS:message'…
we can see that the variable ARGS:message is causing the problem.
The offending request is a POST request, so it is very likely that message is a parameter in the HTTP request body. I guess this is a web mail service? So message probably contains the contents/body of the email. Free text input like this can cause many false positives because user input is unpredictable!

To tune away this false positive, we can take the approach like in our example 3:
We wish to exclude the variable message from rule 941120 to prevent future false positives.
# CRS Rule Exclusion: 941120 - XSS Filter - Category 2: Event Handler Vector
# The "message" variable contains free text user input. UTF-8 input in
# particular is known to cause false positives with rule 941120.
SecRuleUpdateTargetById 941120 "!ARGS:message"

This must be placed after the Include directives which load the CRS.
Note: This will turn off rule 941120 for the variable message for all locations. This is probably acceptable, but in some scenarios this is a small security risk (e.g. if message is used on many pages of your web application.)

Alternatively, if you want to restrict the exclusion only to the relevant URI (so that message is only excluded from rule 941120 for the location '/mail.php' and not for all locations) then you could do something like our example 7 instead:
# CRS Rule Exclusion: 941120 - XSS Filter - Category 2: Event Handler Vector
# The "message" variable contains free text user input. UTF-8 input in
# particular is known to cause false positives with rule 941120.
SecRule REQUEST_URI "@beginsWith /mail.php" \
    "id:1000,\
    phase:1,\
    pass,\
    nolog,\
    ctl:ruleRemoveTargetById=941120;ARGS:message"

This must be placed before the Include directives which load the CRS.

Hi @RedXanadu. Thank you !
can you tell me which file I should add this exception to ?
CRS Rule Exclusion: 941120 - XSS Filter - Category 2: Event Handler Vector
The "message" variable contains free text user input. UTF-8 input in
particular is known to cause false positives with rule 941120.
SecRuleUpdateTargetById 941120 "!ARGS:message"

To clarify, message is the variable you need to exclude from the rule.
If you examined the raw HTML request then you would see that there's a variable named message in there (probably in the request body) and the value of the variable message is the contents of the email (again, assuming this is a webmail application).
So, you need to exclude the variable message. Doing that will prevent this false positive from occurring with any future value of message. You're not excluding one specific pattern or content like ";ONBAO =5" or "являются не".
The earlier example was literal: you would need to use
SecRuleUpdateTargetById 941120 "!ARGS:message"
not
"!ARGS:ONBAO =5"
Definitely make sure to add some comments so that you know what this exclusion is for in the future.
And to confirm, you were correct: RESPONSE-999-EXCLUSION-RULES-AFTER would be a valid place to put this type of rule exclusion :slightly_smiling_face:

Now I understand, thank you. unfortunately, we cannot exclude a variable from the check even for certain pages, since it is not safe to tell me, is it impossible to exclude a certain text, not a variable, namely a word or phrase?

Why do you think the proposed solution is not a safe solution?

because an attacker, for example, can take advantage of the fact that this rule is disabled for the form, for example.

Don't overestimate this problem. You assume that CRS would be a canonical set of rules you need to have. In fact it's just an organically grown set of rules we think useful. 1 more or less is usually no bug deal, since you need to see it in the context of the 150 rules that do not exist and would be nice to have.

Hi @flexstat,
I've presented several solutions so far in this thread, rule exclusions ranging from ‘slightly coarse’ to ‘fine’ to ‘very fine’.
Tuning away a false positive requires poking a hole in your web application firewall: the trick is to make the hole as small as is practically possible! I believe that's been achieved here and one of the solutions above will meet your needs in a secure way: you need to pick which solution is right for you and your needs.
I'm not sure there's anything further we can do here. I'm closing this thread now, but feel free to add further comments or questions if you have any. Thanks!


Connection settings window is not resized when additional tab is opened

System information:

Operating system (distribution) and version Win10
DBeaver version 21.3.1

Steps to reproduce, if exist:

Open connection settings window
Open SSH tab
Click on advanced settings

Expected: Window is resized or scroll bar appears
Actual: Can't change settings until window is manually resized

The issue is not reproducible on the DBeaver 23.1.3.


Use loaders.gl/images for image loading

It looks like existing code forces loading as an ImageBitmap. As of loaders.gl 2.1, ImageBitmap loading should work reliably, right? Also, loading with load(url, ImageLoader) should fall back to non-ImageBitmap on non-Chrome/Firefox, right?
Any other reason to keep the copied code?

update loaders.gl to use imagebitmap by default when auto is true

Oh I thought that was existing behavior. So auto defaults to Image?

Oh I thought that was existing behavior. So auto defaults to Image?

Yes deck.gl only got solid support for ImageBitmap in 8.0, so we have perhaps been overly careful to turn this on.


Building custom image fails with Pi-Gen

I have an Ubuntu 20 system running on VM.
I ran the scripts as listed and I get a console error in Stage 2 when it is running the custom picobrew server setup.
Write after the echo for  'Making bluetooth accessible without being root...'
"unable to set CAP_SETFCAP effective capability: Operation not permitted"
Seems like this might be an issue with Pi-Gen and the suggestion there is to run it with QCow turned off on the Buster branch.
Commenting out the bluetooth code seems to work and create the image, but there is software missing. So I'm inclined to believe this is the offending block of code.
Can anyone recreate this?

Did you run the script with sudo?

Yes. All commands were run as sudo.
I don't have full logs because I shut down the VM for the day, but I can
get them early tomorrow
On Sat, Feb 26, 2022, 12:42 PM Pete @.***> wrote:

Did you run the script with sudo?
—
Reply to this email directly, view it on GitHub
https://github.com/chiefwigms/picobrew_pico/issues/331#issuecomment-1052586806,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGKMVMFUX577S3L7DFYOXK3U5E3MLANCNFSM5PNRY7RA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Tried a build and that happens in <checkoutdir>/pi-gen/stage2/01-sys-tweaks/ - all our stuff is in stage2/99-picobrewserver-setup, so its an issue of pi-gen.  Is there a reason you're trying to make a custom image?  The last one should have all the OS tweaks we do in it (i think)...  if not, the last image was built Jan 27, 2021 - so you could try to checkout a hash in pi-gen's repo about the same time (although you wouldn't get whatever official tweaks raspberry pi has made)

Main reason is to get the access point off the network and general "just want to make it work" nerd stuff.
I recall the build failing earlier on the default branch of pi-gen. I've got a couple of machines building the image right now. My investment in this point is just out of curiosity,

[19:48:08] End /home/pibuilder/pi-gen/stage2/03-set-timezone
[19:48:08] Begin /home/pibuilder/pi-gen/stage2/99-picobrewserver-setup
[19:48:08] Begin /home/pibuilder/pi-gen/stage2/99-picobrewserver-setup/00-run-chroot.sh
WARNING: libcap needs an update (cap=40 should have a name).
Making bluetooth accessible without being root...
unable to set CAP_SETFCAP effective capability: Operation not permitted

This is running off of pi-gen -b Buster
[19:47:16] End /home/pi/pi-gen/stage2/01-sys-tweaks/00-packages-nr
[19:47:16] Begin /home/pi/pi-gen/stage2/01-sys-tweaks/00-packages
WARNING: libcap needs an update (cap=40 should have a name).
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package python-is-python3

This is pi-gen main branch.
No modification on either end for the stage2/99-picobrewserver-setup

From https://github.com/RPi-Distro/pi-gen/issues/565, I think latest is bullseye - there's a comment there that says anything not that will take some modifications.  I'm gonna run a build w/ it now, but probably won't check until tomorrow morning

Also - it looks like bullseye has python 3.9 - you'll probably have to pull changes from 3rd_party_updates_02-20-2022 to pull in newer 3rd party packages

I don't recall any changes we have made to the OS level that would require a new image. The only thing that could benefit from doing that the Bluetooth stuff now for Tilt support (used by subset of folks) and to prevent a year of git changes (not that we have a super large number of changes nowadays anyway) from being pulled and someone thinking the second boot takes 5+ minutes is "server is broken" type thing.
Benefits from within Raspbian are the best things we would get from a new image which would be similar to doing things like apt full-upgrade && apt dist-upgrade yourself (we don't do this in the update and restart).
You would likely get further by just making the systemd changes yourself @LMartinez-Py to disable the correct systemd process. This would then tell the OS not to start the process upon next login. There maybe other changes you need to make as mentioned in PMs about how the various systemd processes are linked together another might require the access point before running itself.

True. For my purposes it would be best to make the changes to an already running installation.
If for whatever reason a new build would needed we'd end up running into these problems so I figured it was good to share.

Agreed. Thanks for taking a look and documenting what you ran into. 👍

git rev-parse HEAD

225f69828fa05361d6028edf2d7a69db73fe2b45

Meantime you can simply check out the above sha. I verified today that our image can simply be built from that sha for verifying compatibility with the newer chips included in recently Pi 4 Model B boards. This was to fix another user's issue with starting up with a ~1yr old image... I call that success that we haven't had a need to release another software version in almost a year. https://github.com/chiefwigms/picobrew_pico/issues/334
One of these days I'll get around to writing another 100,000 lines of code to force everyone to update again. 😜  ♾

The way I see it @tmack8001 is you guys have done a remarkable job in building and setting up this project thank you for all of your hard work, dedication, and time you have devoted to helping people like me continue to brew beer after we were let down by a screwed up company. Thank you 🍺🍻🍺👍🍻

@LEFsher I've been able to build from pi-gen master. There was one modification I needed to make given the fact we explicitly want to remove dhcpcd5 from the distro and that was to also remove raspberrypi-net-mods from the stage4/00-install-packages/00-packages file for when building a stage5 image (includes X11 and HDMI display support vs a headless stage2 "-lite" build).
I did however build a RELEASE=bullseye target image vs targeting a RELEASE=buster image so likely whatever issues you were facing were using the master pi-gen for building an older Raspbian release?
I have yet to test the image that I was able to build... as I don't have a spare SD card at the moment and thus would need to remove and re-image one of my existing ones, which isn't a big deal just didn't want to do with the short amount of time I had today.

There are some test images uploaded to https://github.com/chiefwigms/picobrew_pico/releases/tag/untagged-63abf5fbf92dd8711684 for those that might have access to a unreleased release (maybe just @chiefwigms and I as "owner/contributor" people). I can look to upload else where if someone wants to test bullseye with their local setup.

I've been able to get an image created, but did require a bit of fiddling around with dependencies... Will update this issue when identified what is the issue.


[BUG] AutoCrystal Delayed when switching item in hotbars (mainhand)

That's also for surround btw, when holding any item for example gapple and u switch back to crystal the CA will not start placing/calculating instantly making you miss out on some pops
idk if this is a bug or not but this also happens on singleplayer so its either a bug or config issue (which is unlikely cus i spent 2 days making my cfg)
Update: I fixed this by playing around with AntiPackets, idk which setting though so u may look and add descriptions into that
Another Update: it was CHeldItemChange which i belive cancels the packets that i switched items which then i realized causes surround and other shit to place what ever i was placing Ex. crystal etc.
You may use this information to fix switching delay for ca thingy and do anote attempt to SilentSwitch Bypass

Cooldown/Place-Cooldown?

Cooldown/Place-Cooldown?

My cool down is at 1 and tbh ive never seen the setting place cool down will double check

config issue. can not recreate!


Install fails with: The Pod "RELEASE-NAME-yifli-test" is invalid

Describe the bug
To Reproduce
Steps to reproduce the behavior:

Run  mizu install -o | kubectl apply -f -
Fails with following error:

The Pod "RELEASE-NAME-yifli-test" is invalid:
* metadata.name: Invalid value: "RELEASE-NAME-yifli-test": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
* spec.containers[0].name: Invalid value: "RELEASE-NAME-gijqf-test": a lowercase RFC 1123 label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (e.g. 'my-name',  or '123-abc', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?')

Expected behavior
Install is successful
Logs
n/a
Screenshots
n/a
Desktop (please complete the following information):

OS: Windows
Web Browser: n/a

Additional context
k8s server is AKS
mizu check results:
Mizu checks
===================

kubernetes-api
--------------------
√ can initialize the client
√ can query the Kubernetes API

kubernetes-version
--------------------
√ is running the minimum Kubernetes API version

k8s-components
--------------------
√ 'mizu' namespace exists
√ 'mizu-config' config map exists
√ 'mizu-service-account' service account exists
√ 'mizu-cluster-role' cluster role exists
√ 'mizu-cluster-role-binding' cluster role binding exists
√ 'mizu-api-server' service exists
✗ 'mizu-api-server' pod not running

Hi @ogerardin,
Thanks for reaching out, I see this error and working on a fix.
will update you when there is a fix for this issue

Error is gone thanks.


Can't open inspector on Chrome OSX

The CTRL+<backtick> key combo doesn't seem to register as a keyboard event in Chrome (with standard US keyboard layout and OSX settings). How about CTRL+\ instead?
diff --git a/thirdparty/jquery-entwine/src/jquery.entwine.inspector.js b/thirdparty/jquery-entwine/src/jq
index 588a535..991be0d 100755
--- a/thirdparty/jquery-entwine/src/jquery.entwine.inspector.js
+++ b/thirdparty/jquery-entwine/src/jquery.entwine.inspector.js
@@ -45,7 +45,7 @@ jQuery(function($){
        });

        $('body').bind('keypress', function(e){
-               if (e.ctrlKey && e.which == 96) {
+               if (e.ctrlKey && e.which == 28) {
                        if (inspectorPanel.css('visibility') != 'visible') {
                                inspectorPanel.css({top: 0, visibility: 'visible'});
                                $('body').css({marginTop: 400});

You know I've been noticing this in firefox on windows ctrl+backtick jumps to the first tab groups first tab. Interestingly as well backslash () is e.which==92


Chore: Add README.md, LICENSE, and .gitignore files

Since we started by migrating code from LD-Cool-P, these files are not included.

Commits are 58e2e29, 0e7807e, bdcb629


ci: Improved Workflow

Create a customized workflow to replace the default pages release, featuring a spell checker and linter (and testing?).  Could also include CodeQL for more security checks.

spellcheck, semver, and testing added.  Just make custom pages release to mark this as finished.

spellcheck on the application pdf is updated.


Expose @types/node as a peer dependency

ts-node declares @types/node as a peer dependency, so we've gotta also expose it in order to satisfy the peer dependency requirement
Fixes #319

+1

still waiting for this merge 🙏 , my temporarily fix:
packageExtensions:
  ts-node-dev@*:
    peerDependencies:
      "@types/node": "^18.15.3" #TMP FIX W8 for merge of: https://github.com/wclr/ts-node-dev/pull/332

Is there any reason not to merge this?


Update cats-effect to 3.3.5

Updates org.typelevel:cats-effect from 3.3.4 to 3.3.5.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-effect" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Codecov Report

Merging #295 (a1b4d0c) into master (ad92bc5) will increase coverage by 1.58%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #295      +/-   ##
==========================================
+ Coverage   66.66%   68.24%   +1.58%
==========================================
  Files          19       18       -1
  Lines         561      548      -13
  Branches       21       22       +1
==========================================
  Hits          374      374
+ Misses        187      174      -13

Impacted Files
Coverage Δ

...io/github/vigoo/clipp/VersionSpecificParsers.scala

Continue to review full report at Codecov.

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


Update downloaded analysis results to include census data

suggestion: make the download file a zip of CSVs, with a separate CSV for each census feature.

As I mentioned, having both haversine and driving would be quite tricky as is. Although we could serve the files independently and have cached CSVs instead. This would mean a different behavior for the Add your own dataset case though.


Use shared logging configuration.

We have shared configuration/setup code for logging in our codebases at https://github.com/vipyrsec/dragonfly-logging-config. Ideally this should be what is used in mainframe as well.

Blocked by vipyrsec/dragonfly-logging-config#11


award_suppliers_summary.sql is very slow

When transforming collection 1853, this file took 88% of the total time, or 4.2h out of 4.8h (see log messages).
It might be slow due to:

SELECT DISTINCT (also used in parties_* and contracts_summary)
jsonb_array_elements subquery (unique, though used somewhat different elsewhere)
FROM tmp_awards_summary (also used in award_*)
JOIN parties_summary (also used in parties_*)

Log messages
Feb 17 20:09:34 process1 2021-02-17 20:09:34,366 - 19556 - ocdskingfisher.summarize.cli - INFO - Running add
Feb 17 20:09:34 process1 2021-02-17 20:09:34,377 - 19556 - ocdskingfisher.summarize.add - INFO - Arguments: collections=(1853,) note=Created by Yohanna for Latam blogpost name=latam_blog_colombia tables_only=False
Feb 17 20:09:34 process1 2021-02-17 20:09:34,386 - 19556 - ocdskingfisher.summarize.add - INFO - Added latam_blog_colombia
Feb 17 20:09:34 process1 2021-02-17 20:09:34,386 - 19556 - ocdskingfisher.summarize.add - INFO - Running summary-tables routine
Feb 17 20:09:34 process1 2021-02-17 20:09:34,401 - 19556 - ocdskingfisher.summarize.summary-tables - INFO - Processing initial:flatten
Feb 17 20:09:34 process1 2021-02-17 20:09:34,414 - 19556 - ocdskingfisher.summarize.summary-tables - INFO - initial:flatten: 0.012762069702148438s
Feb 17 20:09:34 process1 2021-02-17 20:09:34,415 - 19556 - ocdskingfisher.summarize.summary-tables - INFO - Processing initial:functions
Feb 17 20:09:34 process1 2021-02-17 20:09:34,430 - 19556 - ocdskingfisher.summarize.summary-tables - INFO - initial:functions: 0.014676332473754883s
Feb 17 20:09:34 process1 2021-02-17 20:09:34,449 - 19562 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:release_tmp
Feb 17 20:25:03 process1 2021-02-17 20:25:03,130 - 19562 - ocdskingfisher.summarize.summary-tables - INFO - middle:release_tmp:<PHONE_NUMBER>869293s
Feb 17 20:25:03 process1 2021-02-17 20:25:03,134 - 19564 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:contracts_tmp
Feb 17 20:25:03 process1 2021-02-17 20:25:03,134 - 19563 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:tender_tmp
Feb 17 20:25:03 process1 2021-02-17 20:25:03,135 - 19565 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:parties_summary
Feb 17 20:25:03 process1 2021-02-17 20:25:03,135 - 19566 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:planning_tmp
Feb 17 20:25:03 process1 2021-02-17 20:25:03,137 - 19567 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:awards_tmp
Feb 17 20:28:53 process1 2021-02-17 20:28:53,657 - 19566 - ocdskingfisher.summarize.summary-tables - INFO - middle:planning_tmp:<PHONE_NUMBER>344635s
Feb 17 20:28:53 process1 2021-02-17 20:28:53,658 - 19568 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:planning_milestones_summary
Feb 17 20:28:53 process1 2021-02-17 20:28:53,660 - 19569 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:planning_documents_summary
Feb 17 20:28:56 process1 2021-02-17 20:28:56,972 - 19569 - ocdskingfisher.summarize.summary-tables - INFO - middle:planning_documents_summary: 3.311697244644165s
Feb 17 20:29:31 process1 2021-02-17 20:29:31,087 - 19563 - ocdskingfisher.summarize.summary-tables - INFO - middle:tender_tmp:<PHONE_NUMBER>2127686s
Feb 17 20:29:31 process1 2021-02-17 20:29:31,089 - 19570 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:tender_items_summary
Feb 17 20:29:31 process1 2021-02-17 20:29:31,091 - 19571 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:tender_documents_summary
Feb 17 20:29:31 process1 2021-02-17 20:29:31,091 - 19572 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:tender_milestones_summary
Feb 17 20:30:16 process1 2021-02-17 20:30:16,845 - 19571 - ocdskingfisher.summarize.summary-tables - INFO - middle:tender_documents_summary: 45.75411868095398s
Feb 17 20:30:26 process1 2021-02-17 20:30:26,892 - 19570 - ocdskingfisher.summarize.summary-tables - INFO - middle:tender_items_summary: 55.802512407302856s
Feb 17 20:31:09 process1 2021-02-17 20:31:09,822 - 19568 - ocdskingfisher.summarize.summary-tables - INFO - middle:planning_milestones_summary:<PHONE_NUMBER>7939148s
Feb 17 20:31:24 process1 2021-02-17 20:31:24,358 - 19572 - ocdskingfisher.summarize.summary-tables - INFO - middle:tender_milestones_summary:<PHONE_NUMBER>7278442s
Feb 17 20:33:15 process1 2021-02-17 20:33:15,392 - 19564 - ocdskingfisher.summarize.summary-tables - INFO - middle:contracts_tmp:<PHONE_NUMBER>3770447s
Feb 17 20:33:15 process1 2021-02-17 20:33:15,393 - 19573 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:contract_implementation_transactions_summary
Feb 17 20:33:15 process1 2021-02-17 20:33:15,394 - 19575 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:contract_implementation_milestones_summary
Feb 17 20:33:15 process1 2021-02-17 20:33:15,395 - 19574 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:contract_items_summary
Feb 17 20:33:15 process1 2021-02-17 20:33:15,395 - 19576 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:contract_milestones_summary
Feb 17 20:33:15 process1 2021-02-17 20:33:15,396 - 19562 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:contract_documents_summary
Feb 17 20:33:15 process1 2021-02-17 20:33:15,396 - 19577 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:contract_implementation_documents_summary
Feb 17 20:33:27 process1 2021-02-17 20:33:27,785 - 19562 - ocdskingfisher.summarize.summary-tables - INFO - middle:contract_documents_summary: 12.388645887374878s
Feb 17 20:33:27 process1 2021-02-17 20:33:27,786 - 19575 - ocdskingfisher.summarize.summary-tables - INFO - middle:contract_implementation_milestones_summary: 12.391688585281372s
Feb 17 20:33:27 process1 2021-02-17 20:33:27,786 - 19576 - ocdskingfisher.summarize.summary-tables - INFO - middle:contract_milestones_summary: 12.390355110168457s
Feb 17 20:33:27 process1 2021-02-17 20:33:27,787 - 19577 - ocdskingfisher.summarize.summary-tables - INFO - middle:contract_implementation_documents_summary: 12.38979172706604s
Feb 17 20:33:27 process1 2021-02-17 20:33:27,787 - 19573 - ocdskingfisher.summarize.summary-tables - INFO - middle:contract_implementation_transactions_summary: 12.392741918563843s
Feb 17 20:35:00 process1 2021-02-17 20:35:00,091 - 19565 - ocdskingfisher.summarize.summary-tables - INFO - middle:parties_summary:<PHONE_NUMBER>084015s
Feb 17 20:35:00 process1 2021-02-17 20:35:00,094 - 19566 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:parties_buyer_summary
Feb 17 20:35:00 process1 2021-02-17 20:35:00,095 - 19563 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:agg_parties
Feb 17 20:35:00 process1 2021-02-17 20:35:00,095 - 19569 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:parties_procuringentity_summary
Feb 17 20:35:00 process1 2021-02-17 20:35:00,096 - 19571 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:parties_tenderers_summary
Feb 17 20:35:00 process1 2021-02-17 20:35:00,120 - 19574 - ocdskingfisher.summarize.summary-tables - INFO - middle:contract_items_summary:<PHONE_NUMBER>1726685s
Feb 17 20:37:26 process1 2021-02-17 20:37:26,581 - 19567 - ocdskingfisher.summarize.summary-tables - INFO - middle:awards_tmp:<PHONE_NUMBER>573883s
Feb 17 20:37:26 process1 2021-02-17 20:37:26,583 - 19570 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:award_documents_summary
Feb 17 20:37:26 process1 2021-02-17 20:37:26,584 - 19568 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:award_suppliers_summary
Feb 17 20:37:26 process1 2021-02-17 20:37:26,585 - 19572 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:award_items_summary
Feb 17 20:37:26 process1 2021-02-17 20:37:26,585 - 19564 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:agg_tender
Feb 17 20:37:26 process1 2021-02-17 20:37:26,586 - 19562 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:agg_planning
Feb 17 20:37:26 process1 2021-02-17 20:37:26,586 - 19575 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:tender_summary
Feb 17 20:37:26 process1 2021-02-17 20:37:26,586 - 19576 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:planning_summary
Feb 17 20:37:26 process1 2021-02-17 20:37:26,586 - 19577 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:agg_milestones
Feb 17 20:37:26 process1 2021-02-17 20:37:26,638 - 19562 - ocdskingfisher.summarize.summary-tables - INFO - middle:agg_planning: 0.05278968811035156s
Feb 17 20:37:42 process1 2021-02-17 20:37:42,470 - 19564 - ocdskingfisher.summarize.summary-tables - INFO - middle:agg_tender: 15.885469198226929s
Feb 17 20:38:32 process1 2021-02-17 20:38:32,432 - 19570 - ocdskingfisher.summarize.summary-tables - INFO - middle:award_documents_summary: 65.84830737113953s
Feb 17 20:38:32 process1 2021-02-17 20:38:32,433 - 19573 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:agg_documents
Feb 17 20:38:39 process1 2021-02-17 20:38:39,349 - 19573 - ocdskingfisher.summarize.summary-tables - INFO - middle:agg_documents: 6.91571307182312s
Feb 17 20:40:41 process1 2021-02-17 20:40:41,094 - 19577 - ocdskingfisher.summarize.summary-tables - INFO - middle:agg_milestones:<PHONE_NUMBER>2857056s
Feb 17 20:41:25 process1 2021-02-17 20:41:25,689 - 19571 - ocdskingfisher.summarize.summary-tables - INFO - middle:parties_tenderers_summary:<PHONE_NUMBER>186554s
Feb 17 20:41:32 process1 2021-02-17 20:41:32,352 - 19572 - ocdskingfisher.summarize.summary-tables - INFO - middle:award_items_summary:<PHONE_NUMBER>965454s
Feb 17 20:41:32 process1 2021-02-17 20:41:32,354 - 19565 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:awards_summary
Feb 17 20:42:59 process1 2021-02-17 20:42:59,965 - 19563 - ocdskingfisher.summarize.summary-tables - INFO - middle:agg_parties:<PHONE_NUMBER>445801s
Feb 17 20:43:31 process1 2021-02-17 20:43:31,868 - 19576 - ocdskingfisher.summarize.summary-tables - INFO - middle:planning_summary:<PHONE_NUMBER>9739075s
Feb 17 20:44:07 process1 2021-02-17 20:44:07,428 - 19569 - ocdskingfisher.summarize.summary-tables - INFO - middle:parties_procuringentity_summary:<PHONE_NUMBER>510345s
Feb 17 20:44:12 process1 2021-02-17 20:44:12,244 - 19566 - ocdskingfisher.summarize.summary-tables - INFO - middle:parties_buyer_summary:<PHONE_NUMBER>995422s
Feb 17 20:45:35 process1 2021-02-17 20:45:35,768 - 19565 - ocdskingfisher.summarize.summary-tables - INFO - middle:awards_summary:<PHONE_NUMBER>4661865s
Feb 17 20:45:57 process1 2021-02-17 20:45:57,320 - 19575 - ocdskingfisher.summarize.summary-tables - INFO - middle:tender_summary:<PHONE_NUMBER>666687s
Feb 18 00:51:28 process1 2021-02-18 00:51:28,949 - 19568 - ocdskingfisher.summarize.summary-tables - INFO - middle:award_suppliers_summary: 15242.364590406418s
Feb 18 00:51:28 process1 2021-02-18 00:51:28,951 - 19574 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:agg_awards
Feb 18 00:51:28 process1 2021-02-18 00:51:28,951 - 19567 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:contracts_summary
Feb 18 00:52:21 process1 2021-02-18 00:52:21,452 - 19574 - ocdskingfisher.summarize.summary-tables - INFO - middle:agg_awards: 52.501070737838745s
Feb 18 00:55:05 process1 2021-02-18 00:55:05,248 - 19567 - ocdskingfisher.summarize.summary-tables - INFO - middle:contracts_summary:<PHONE_NUMBER>2013245s
Feb 18 00:55:05 process1 2021-02-18 00:55:05,250 - 19562 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:agg_contracts
Feb 18 00:55:39 process1 2021-02-18 00:55:39,609 - 19562 - ocdskingfisher.summarize.summary-tables - INFO - middle:agg_contracts: 34.35887289047241s
Feb 18 00:55:39 process1 2021-02-18 00:55:39,611 - 19564 - ocdskingfisher.summarize.summary-tables - INFO - Processing middle:release_summary
Feb 18 00:57:29 process1 2021-02-18 00:57:29,667 - 19564 - ocdskingfisher.summarize.summary-tables - INFO - middle:release_summary:<PHONE_NUMBER>667633s
Feb 18 00:57:29 process1 2021-02-18 00:57:29,809 - 19556 - ocdskingfisher.summarize.summary-tables - INFO - Processing final:foreign-key-relationships
Feb 18 00:57:31 process1 2021-02-18 00:57:31,221 - 19556 - ocdskingfisher.summarize.summary-tables - INFO - final:foreign-key-relationships: 1.4114415645599365s
Feb 18 00:57:31 process1 2021-02-18 00:57:31,222 - 19556 - ocdskingfisher.summarize.summary-tables - INFO - Processing final:docs
Feb 18 00:57:32 process1 2021-02-18 00:57:32,934 - 19556 - ocdskingfisher.summarize.summary-tables - INFO - final:docs: 1.71193528175354s
Feb 18 00:57:32 process1 2021-02-18 00:57:32,935 - 19556 - ocdskingfisher.summarize.summary-tables - INFO - Processing final:drop
Feb 18 00:57:35 process1 2021-02-18 00:57:35,239 - 19556 - ocdskingfisher.summarize.summary-tables - INFO - final:drop: 2.3045287132263184s
Feb 18 00:57:35 process1 2021-02-18 00:57:35,240 - 19556 - ocdskingfisher.summarize.summary-tables - INFO - Processing final:analyze
Feb 18 00:57:35 process1 2021-02-18 00:57:35,247 - 19556 - ocdskingfisher.summarize.summary-tables - INFO - final:analyze: 0.006900310516357422s
Feb 18 00:57:35 process1 2021-02-18 00:57:35,247 - 19556 - ocdskingfisher.summarize.summary-tables - INFO - Total time: 17280.860336065292s
Feb 18 00:57:35 process1 2021-02-18 00:57:35,248 - 19556 - ocdskingfisher.summarize.add - INFO - Running field-counts routine
Feb 18 00:57:35 process1 2021-02-18 00:57:35,300 - 27074 - ocdskingfisher.summarize.field-counts - INFO - Processing collection ID 1853
Feb 18 02:45:42 process1 2021-02-18 02:45:42,990 - 27074 - ocdskingfisher.summarize.field-counts - INFO - Collection ID 1853: 6487.687526226044s
Feb 18 02:45:43 process1 2021-02-18 02:45:43,007 - 19556 - ocdskingfisher.summarize.field-counts - INFO - Total time: 6487.757339477539s
Feb 18 02:45:43 process1 2021-02-18 02:45:43,134 - 19556 - ocdskingfisher.summarize.add - INFO - Configured read-only access to latam_blog_colombia

Hmm, it was only slow this one time. I ran:
zgrep -e 'Total time: [0-9][0-9][0-9][0-9]' kingfisher-summarize.log*

To see if anything else has been slow. There was just one field-counts of 1022s (17min) for collection 1911 (latam_blog_mexico_administracion_publica_federal).
There were a fair number spiders running at the same time as the colombia summary, so for now I'll just assume that something blocked the query, or the tool was waiting for a connection.

I did change the query to look like parties_tenderers_summary, which is structurally identical. This change didn't change the EXPLAIN plan.

Ha. I thought I'd recreate the summaries to see if it was something blocking the query, then cancelled the command because I wanted to run it in a tmux, and tried to drop the schema to cleanup, and now that drop command is waiting... so I'm more confident now that the running time is due to Kingfisher Process being busy processing collections.


Auto-register dtypes as UDTs.

Also, only have a single object for each numpy.dtype for UDTs.  This makes it easier and less awkward for us, but could result in weirdness if the same dtype is registered multiple times under different names.  Probably okay.

One small step towards better and more convenient UDTs.  Merging.


How to use a nested custom scalar?

Hi there,
First many props for the awesome GraphQL tooling! One thing though I can't get my head around is to use custom scalar types with my resolver.
Given I have the following schema;
scalar Date
scalar JSON

type Submission {
    id: ID!,
    form: ID!,
    properties: JSON!,
    receivedAt: Date!
}

type Form {
    id: ID!,
    submissions: [Submission]
}

type Query {
    forms: [Form]
}

schema {
    query: Query
}

And my resolver looks like this;
const resolvers = {
  Query: {
    forms(root, args, context) {
      return context.db.collection('form').find().toArray()
    }
  },
  Form: {
    submissions({ _id }, args, context) {
      return context.db.collection('submission').find({ form: _id }).toArray()
    }
  },
  JSON: GraphQLJSON
}

I get a lot of errors but no JSON :sweat: Any thoughts?

Ok it seems that updating GraphQL to a newer version did the trick


mysql cdc restart from checkpoint failed when some binlog file has been purge

Search before asking

[X] I searched in the issues and found nothing similar.

Flink version
1.14.6
Flink CDC version
2.3.X
Database and its version
aws rds
Minimal reproduce step
1.start flink cdc connector job
2.clean some binlog file
3.restart from checkpoint
What did you expect to see?
restart normally
What did you see instead?
restart failed
io.debezium.DebeziumException: The connector is trying to read binlog starting at SourceInfo [currentGtid=null, currentBinlogFilename=mysql-bin.xxx, currentBinlogPosition=xxx, currentRowNumber=0, serverId=0, sourceTime=null, threadId=-1, currentQuery=null, tableIds=[], databaseName=null], but this is no longer available on the server. Reconfigure the connector to use a snapshot when needed. at io.debezium.connector.mysql.MySqlConnectorTask.validateSnapshotFeasibility(MySqlConnectorTask.java:329) at io.debezium.connector.mysql.MySqlConnectorTask.start(MySqlConnectorTask.java:98) at io.debezium.connector.common.BaseSourceTask.start(BaseSourceTask.java:130) at io.debezium.embedded.EmbeddedEngine.run(EmbeddedEngine.java:759) at io.debezium.embedded.ConvertingEngineBuilder$2.run(ConvertingEngineBuilder.java:188) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
Anything else?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

i found the bug in code
 private boolean checkGtidSet(MySqlOffsetContext offset) {
       ........
        // **I think the gtid  set obtained by this method is the exectuted gtid set instead of available gtid set**
        String availableGtidStr = connection.knownGtidSet();
       ......
           ......
            if (!gtidSetToReplicate.equals(nonPurgedGtidSetToReplicate)) {
                LOG.warn("Some of the GTIDs needed to replicate have been already purged");
                return false;
            }
.......
    }

the right avaliable gtid set should be
GtidSet executedGtidSet = new GtidSet(executedGtidStr);
       final GtidSet purgedGtidSet = connection.purgedGtidSet();
       LOG.info("Server has already purged {} GTIDs", purgedGtidSet);
       GtidSet availableGtidSet = connection.subtractGtidSet(executedGtidSet, purgedGtidSet);

@leonardBang @wuchong If this solution works, can this issue be assigned to me, I hope I can contribute code to this project

@leonardBang i have a solution for this  and I have a solution to this problem and have been proving it in production for months，please assign it to me,i can fix it

Hi I think I encountered this issue, too, @dylenWu @leonardBang could you kindly handle it?

Closing this issue as it has been migrated to Apache Jira.


Make Data.Hashable.Class exposed

Exposing this module allows uses to re-use the functions defined for writing Hashable instances. If the module is not safe then it can be marked with Internal or that can be in the docs.

What is missing from the public API, can you be more specific?

No reply, closing.


GSLUX-743: Modify circle geometries

JIRA issue
https://jira.camptocamp.com/browse/GSLUX-743
Description
PR enables editing circle geometries and calculates circle measurements. It refactors the measurement formatting further into directives. Note that vertices are not highlighted anymore like in v3, but the default ol modification style is applied.
There is one remaining issue regarding the circle radius which is not an exact value. Due to resolutionFactor applied before circle.setRadius() it is approximate and decreases on multiple submits or app reloads:

submitted values in the radius input are also approximate on prod
submitting same values multiple times also has an issue on prod
reloading the app on prod may work because encoded polygon geometries are not converted back to circles

I didn't manage to fix this issue (which is partially also present on prod) within setCircleRadius and propose to create a separate ticket for this:
Available options to solve this could be to:

find a solution in get/setCircleRadius (not sure if possible)
handle circle geometries as polygons and introduce a separate modify interaction for them as in v3
encode circle geometries as circles in URL

To-dos:

[x] check area, length calculation
[x] fix issue with (circle radius) measurements, not calculating correct values
[x] display circle radius unit outside of input / continue to refactor formatting to directive
[x] tests
[x] check/fix exports

Thanks for the detailed review @AlitaBernachot ! I've adapted most of the things you found :-)


Update zed-recent-projects extension - Add support for pinned projects

Description
Allows to pin/unpin and order entries in "Search Recent Projects" command
Screencast
https://github.com/raycast/extensions/assets/827338/0fde18ca-56fe-4bdf-aec6-66711b63c441
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hello @pernielsentikaer, could you please take a look?


fix(extension): add new wallet modal closing on overlay click (lw-10975)

Checklist

[ ] JIRA - LW-10975
[ ] Proper tests implemented
[ ] Screenshots added.

Proposed solution
Explain how does this PR solves the problem stated in JIRA ticket.
You can also enumerate different alternatives considered while approaching this task.
Testing
Describe here, how the new implementation can be tested.
Provide link or briefly describe User Acceptance Criteria/Tests that need to be met
Screenshots
Attach screenshots here if implementation involves some UI changes

Allure Report
allure-report-publisher generated test report!

processReports: ✅ test report for 5273ce47

passed
failed
skipped
flaky
total
result

Total
32
0
0
0
32
✅


Upgrade terraform-provider-artifactory to v9.6.0

This PR was generated via $ upgrade-provider pulumi/pulumi-artifactory.

Upgrading terraform-provider-artifactory from 9.4.0  to 9.6.0.
Fixes #479
Fixes #478
Fixes #473
Upgrading pulumi-terraform-bridge from v3.61.0 to v3.62.0.
Upgrading pulumi-terraform-bridge/pf from v0.17.0 to v3.62.0.

/release minor


Update Banner

This updates some of the text in README.md and most importantly changes Discord Trivia's banner.

Banner Preview

This now also adds a asSubcommand option to the TriviaCommandBuilder class to return it as a subcommand builder

#23


GCC 2017 Architecture Follow Up

Notes from @natefoo:
We really need to frame the web request response cycle in the context of a particular request. We walk through the stuff but there is no context and I think that is terrible.
Polled the room asking who was interested in hacking:

The UI: 0 hands
The backend: Many many hands

Polled the room asking if it was too admin-y or too developer-y

Too admin-y: no hands
Too developer-y: ~5 hands

Projects to add:

Ephemeris
Parsec
Kickstart

Components to add:

Jobs
code structure w/ diagrams
JobDestination objects
Job flow
Status changes
Code flow (jobwrapper.prepare() -> runner.queue_job() -> ...
GIEs?
Containers???
Update to latest usegalaxy.org slides.

Random stuff:

Reorder WSGI slides: outline/text before the figure
DrammaJobRunner -> DrmmaJobRunner
Object Store UML should show that the non-nested Object Store plugins are also children of the nested ones
Managers are currently discussed at a random point in the slides - should probably go between controllers and model
Non-slide stuff:
Document webless handlers
Document job_conf.xml plugin workers attrib

Hey @jmchilton would you have time or interest for any of this today during the CoFest? Should we close this or assign it to someone else to do for the next gcc?

I don't think I am going to get to it today - but I thought my presentation of these slides in 2019 was even more .... problematic. They're quite out of date. I'll get to this before the next GCC I'm sure, happy to have others take a pass or two at presenting things better before then.

Closing due to #1906


Modifiers in conditionals are removed

class Main {
	#if !js
	inline
	#end
	static public function main() {}
}

becomes
class Main {
	#if !js
	#end
	static public function main() {}
}

Seems that inline is missing from the token tree completely.

I think inline gets put into a tempStore, so it can be placed below a type, but that type never comes before #end


doc: ibisml for sklearn/Tidymodel users tutorial sessions

It's really important to make sure that ibisml is user-friendly for people who are already familiar with scikit-learn and tidymodel. Adding coverage of scikit-learn and sklearn preprocessing in the documentation and tutorials will make it easier for python and R users to start using ibisml.
In this tutorial or documentation, we should cover the following points:

Mapping scikit-learn and Tidymodel preprocessing techniques directly to ibisml equivalents.
Providing examples of ibisml preprocessing, which can be taken from the API reference documentation.
[Optional] Demonstrating how to integrate ibisml preprocessing with scikit-learn and tidymodels. This was partly covered in the main tutorial, but we can expand on it if needed.

Also need to combine this #30

Mapping scikit-learn and Tidymodel preprocessing techniques directly to ibisml equivalents.

I think this is covered by #30, and is more to track IbisML development priorities and progress, rather than necessarily surfacing to users in a tutorial (I imagine most DS can figure out if they need to use ImputeMean vs SimpleImputer(strategy="mean").
For tracking purposes, I feel like https://github.com/ibis-project/ibis-ml/issues/32 is sufficient for now.

Providing examples of ibisml preprocessing, which can be taken from the API reference documentation.
[Optional] Demonstrating how to integrate ibisml preprocessing with scikit-learn and tidymodels. This was partly covered in the main tutorial, but we can expand on it if needed.

I think a single demo workflow could cover this for now, because it's being integrated in scikit-learn pipeline anyway, and the syntax should be fairly familiar for people coming from tidymodels.


Fix problems related to Onyx.clear and useOnyx

Details

This PR fixes two problems we've discovered on E/App during migration to useOnyx, both related to Onyx.clear. More details here.
It also exposes the reuseConnection flag in useOnyx API for convenience purposes (it's already exposed in Onyx.connect).
Related Issues

https://github.com/Expensify/App/issues/48725
Automated Tests
Unit tests were added to cover the fixes mentioned.
Manual Tests

Checkout this branch on E/App.
Link the changes of this Onyx PR branch to E/App.
Run npm test on E/App and assert all tests are passing.
Login with a user, logout and login with the same user again, assert the whole process works as expected.

❗You will notice that after second login on Web/mWeb, user is redirected to settings page instead of home. Please have in mind that this issue is not related to these fixes, but instead one more fix that would be necessary to be made on E/App when migrating AuthScreens.tsx to useOnyx.❗
Author Checklist

[x] I linked the correct issue in the ### Related Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/2ec75fd9-2a82-48ec-b900-15d61f0546f4

Android: mWeb Chrome
https://github.com/user-attachments/assets/20abd527-ad1f-4c5c-8533-b0e0f2d839ab

iOS: Native
https://github.com/user-attachments/assets/c9389ba4-f4c6-4ea9-a9be-01adf1e80914

iOS: mWeb Safari
https://github.com/user-attachments/assets/858dff39-8952-4cf6-9282-05b8b60fd26e

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/c05274ed-b940-44fa-b5a4-6056564ca7f0
https://github.com/user-attachments/assets/81490232-19a6-4415-b445-61fc2f2b19bf

MacOS: Desktop
https://github.com/user-attachments/assets/84204411-5c48-45b4-b7d7-3da22f686a49

LGTM !

Bump @tgolen @marcaaron

Happy to review this, but I don't yet understand what problem we are solving. Can we update the description with the explanation? I took a look at the comment we linked out to and it says:

From what I've seen this problem doesn't happen for withOnyx basically because the racing condition doesn't occur (maybe because it's a component and it's slightly slower during initialisation?).

Am I reading that "maybe" correctly? Are we not sure why it happens? Do we have a better explanation somewhere?

@marcaaron Addressed the comments and added explanations to the PR description, please let me know if it's clearer now.


python311Packages.pyprecice: <IP_ADDRESS> -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.pyprecice is: Python language bindings for preCICE
meta.homepage for python311Packages.pyprecice is: https://github.com/precice/python-bindings
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found <IP_ADDRESS> with grep in /nix/store/fs4afcxkalhra04c9xcv60r9mfcfrbf1-python3.11-pyprecice-<IP_ADDRESS>
found <IP_ADDRESS> in filename of file in /nix/store/fs4afcxkalhra04c9xcv60r9mfcfrbf1-python3.11-pyprecice-<IP_ADDRESS>

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.pyprecice
python312Packages.pyprecice

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fs4afcxkalhra04c9xcv60r9mfcfrbf1-python3.11-pyprecice-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.pyprecice https://github.com/r-ryantm/nixpkgs/archive/c3496b72ca4c4d99878240806a5d4780e57d47ca.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c3496b72ca4c4d99878240806a5d4780e57d47ca#python311Packages.pyprecice

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fs4afcxkalhra04c9xcv60r9mfcfrbf1-python3.11-pyprecice-<IP_ADDRESS>
ls -la /nix/store/fs4afcxkalhra04c9xcv60r9mfcfrbf1-python3.11-pyprecice-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python311Packages.pyprecice
python312Packages.pyprecice

Maintainer pings
cc @Scriptkiddi for testing.

@NixOS/nixpkgs-merge-bot

@nixos/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge

Since this is a python-modules, the merge bot does not work.
https://github.com/NixOS/nixpkgs-merge-bot?tab=readme-ov-file#constraints

@NixOS/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge


fix: All Chip components to only be one line of text

If the text within a Chip exceeds the width allotted to it, then it will use an ellipsis. A title attribute is also tied to the Chip to display the full value of the chip on hover.

@lucyconklin - Thank you for reviewing the earlier PR. This has completely changed since you approved it according to new direction from the Design team. Rather than giving the option to have a chip truncate its text, we now do it by default. This behavior is done across the board for all Chip related components.


Bump to 0.1.2

format code in humanize/decimal. (As mentioned in last PR)
update README and package number.

@lyweiwei please help to review.

Coverage remained the same at 100.0% when pulling 17b5cfcdeca6a68e70bcea7660c248e1d0170ada on ljqx:bump-to-0.1.2 into d9d37861c5af0b934466e84969a9ac67b6220638 on Microsoft:master.


chore(package): update semantic-release to version 17.0.2

:tada: This PR is included in version 8.12.12 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add CI matrix for macOS builds

homebrew has rudimentary version support by specifying ffmpeg@4, ffmpeg@5 etc. No minor/patch versions AFAICT.
Also reduced the frequency of scheduled builds. Daily is just too much. Caches should stay alive for 7 days at least, so this should not cause problems regarding cache. Time and day are chosen semi-randomly (but moved away from midnight because that is a known hot time for CI jobs)

Failure seems spurious

This time there's a new failure that seems less spurious.


Cannot import new dashboard

Expected Behavior:
Grafana UI / Home / Menu/ Dashboards  / Import
Actual Behavior:
No import location in menu

Only admin can create new dash by default


mish activation

Recently, a new overperforming activation function announced as Mish (https://arxiv.org/abs/1908.08681v2)

Summary
Related Issues
PR Overview

[ ] This PR requires new unit tests [y/n] (make sure tests are included)
[ ] This PR requires to update the documentation [y/n] (make sure the docs are up-to-date)
[ ] This PR is backwards compatible [y/n]
[ ] This PR changes the current API [y/n] (all API changes need to be approved by fchollet)

no tests


Link to the correct location for AAD samples.

Hi @noopman, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@noopman - thanks very much for your contribution! The final prefix for AAD samples is "active-directory". We will be updating links as well, so LMK if you would like to revise the query string your PR. Thanks again!

Closing for now.. LMK if you would like to revisit.


Radio.mixin

This is a little bit more out there, but if you want to extend the Radio api you have to do all sorts of funky stuff.
Backbone.Radio.Requests.myCustomMethod =
Backbone.Radio.Channel.prototype.myCustomMethod = function() {};

Backbone.Radio.myCustomMethod = function(channelName, ...args) {
  var channel = this.channel(channelName);
  return channel.myCustomMethod.apply(channel, args);
};

Edit: Similar to underscores _.mixin

meh


Make CompatibilityCollector able to parse a single version String

PR Summary
Make CompatibilityCollector able to parse a single version String.
I found it odd that the version number is -1 when not being specified (System.Management.Automation.SemanticVersion uses a 0 in that case) but I tried to be at least consistent with the current implementation...
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .cs, .ps1 and .psm1 files have the correct copyright header
[x] Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

Thanks for this @bergmeister!

You're welcome, it was a relatively easy fix


Default make the backtrace tool as optional

When not having GDB installed and even if i put the use_backtrace_gdb_reporter: FALSE the path for GDB is checked. Since I do not want to define tools: backtrace... in my project yml, since I do not use it at the moment, it would be fair to make it optional (and hence removing the path check by default). Optional helps by not having to have gdb installed in CI, but workaround I assume is to define tools: backtrace_settings: optional: TRUE in project.yml
Found in https://github.com/ThrowTheSwitch/Ceedling/pull/739#issuecomment-1545319491

The assumed workaround works, so this pull request can be closed.


Fix port cache calculation in GraphNode

Fixes #91082 by updating the left_port_cache & right_port_cache calculation in GraphNode::_port_pos_update.

@Geometror See also #90229 and #90787. Seems like it's easy to make mistakes in this code with different indices.

@akien-mga Yes indeed (child index, slot index and port index), but unfortunately that's just how the current system works. Changing this would basically require a complete rework of GraphNode/GraphEdit (much more sophisticated than the refactoring I've done). Maybe for 5.0 :)

Thanks! And congrats for your first merged Godot contribution :tada:


[google_maps_flutter] Consider testing both display modes on Android

(See https://github.com/flutter/packages/pull/7282 for context)
We have two display modes that we support for google_maps_flutter on Android, and have for a while, but we only test one of them in the integration tests that run in our example app. The PR referenced above will make the mode we test the mode we recommend to clients, which is an improvement, but if we support two modes we should really be testing both. (This is especially true given that our platform view testing in the engine isn't very comprehensive, so flutter/packages is where we often catch issues in practice; if we aren't testing google_maps_flutter with HC, we're less likely to find engine HC regressions.)

One way of doing this would be to have two examples apps, like we do with google_maps_flutter_ios (for testing different min iOS versions). That does add some complexity and potential flake, but it would give us the coverage.