Support php 7.1

When I tried to install module via composer, I got this error:
Could not find package cloudflare/cloudflare-magento at any version matching your PHP version <IP_ADDRESS>

This is caused by https://github.com/cloudflare/Cloudflare-Magento/blob/master/composer.json#L18
https://getcomposer.org/doc/articles/versions.md#tilde-version-range-

I know, I just proposed to add php 7.1

@tiamo I've re-released in packagist. Could you give it a try?
https://packagist.org/packages/cloudflare/cloudflare-magento
Thanks

Yep, now it works. Thanks


SCM - remove incoming/outgoing/history graph from the Source Control view

Related on Stack Overflow: why will vscode remove incoming/outgoing changes graph.


Adding Sepolia Network

Missing multicall, because the multicall address of makerDAO is not yet on master:
Link of makerDAO multicall PR: https://github.com/makerdao/multicall/pull/48

@lgahdl - I just used the multicall address that someone shared in the makerDAO link.


Adding --ignore-case to files.fd_opts doesn't work.

As title. With settings:
files = {
  prompt = ' File $ ',
  -- WARNING: Run `brew install fd` to install fd.
  fd_opts =
    "--hidden "..
    "--ignore-case "..
    "--no-ignore "..
    " "..
    "--type f "..
    -- "--max-depth 15 "..
    "--exclude .DS_Store "..
    "--exclude .git "..
    "--exclude node_modules "..
    "--exclude '*-lock.json' "..
    "--exclude '*.lock' "..
    " ",
  actions = {
    -- WARNING: This is required. Or files will be opened in quick-fix list.
    ["default"] = actions.file_edit,
  }
},

As img:

That's because files isn't "live", the --ignore-case is meaningless here,  the fdcommand isn't run again every keystroke, it's fzf doing the fuzzy matching for you not fd.
If you wanted to ignore case in the search you need to add -i to fzf_cli_args, from man fzf:
       -i     Case-insensitive match (default: smart-case match)
       +i     Case-sensitive match

Add this via fzf_opts (as a table) or via fzf_cli_args (same thing, different way):
  files = {
    fzf_opts          = { ["-i"] = "" },
    -- fzf_cli_args      = "-i",
  ...
}

You can also add this directly to the call:
:lua require'fzf-lua'.files({ fzf_cli_args="-i" })

Should I remove some lines from my settings? It doesn't work like the image you have shown.

Should I remove some settings of fd lines from my settings? While I use fzf_cli_args, It doesn't work like the image you have shown.

By not work do you mean it does not ignore case or fails to work properly at all?
Your settings make no differnce in this case, as long as fzf receives the -i flag it should be case insensitive, what version of fzf are you using? You can try with an empty setup() function and see if it makes a difference (it shouldn't but you can try)?
Note that if you opted to use skim instead of fzf it does not have the -i flag, it has -case flag instead:
       --case=[smart,respect,ignore]
              To ignore case on matching or not. (default smart)

OK, it works. (I fall asleep so didn't reply immediately) I have tried three versions:

Put fzf_cli_args="-i" inside files:

files = { fzf_cli_args="-i" }

Put fzf_cli_args="-1" the same level as files:

fzf_cli_args="-i"
files = { ... }

And the cmd version you mentioned:

:lua require'fzf-lua'.files({ fzf_cli_args="-i" })

I expected 2. to fail, but it works. Or it is because of some kind of cache that causes this. Can you help me confirm this result?

[...]
You can also add this directly to the call:
:lua require'fzf-lua'.files({ fzf_cli_args="-i" })

OK, I just reproduce that strange behaivour:

Inside files = { ... }. Put the fzf_cli_args="-i" after the fd_opts, then it becomes smart-case like the image in my OP.
Now try putting it before, then it becomes ignore-case as your image shows.

It seems that it also works when I put fzf_cli_args="-i" the same level as files. Is this correct behaviour?

It seems that it also works when I put fzf_cli_args="-i" the same level as files. Is this correct behaviour?

Yes, that's how it should be, putting it at the setup function at the same level of files is equal to sending it like this:
:lua require'fzf-lua'.files({ fzf_cli_args="-i" })

Should I remove some settings of fd lines from my settings? While I use fzf_cli_args, It doesn't work like the image you have shown.

This is a misreport. I guess that I was too sleepy and opened live_grep_resume when I tested it.
I have no issue with this now. Thank you so much!

Btw, I have a suggestion for you, if you want to unerstand what this plugin does and what command gets piped to fzf run grep, live_grep and files with debug=true it will now also print the underlying command as the top line of the reults.
This will clarify the difference between grep (running a single command and having fzf do the matching):
:lua require'fzf-lua'.grep({ debug = true, search='pcall' })

to live_grep, which runs a new command based on what you type:
:lua require'fzf-lua'.live_grep_glob({ debug = true })

and then typing the search term pcall -- *entry* (you can also see the glob parsing in action here too):

You will notice that when using grep or files, only one command is run, it gets piped to fzf which then does fuzzy matching, with the live_xxx versions each keystrokes runs a new command (which you'll be able to see with debug=true).

it's very clear for me now! Thank you!

it's very clear for me now! Thank you!

Great!
On another issue that you had in the past, I just commited a change to make it clear when your regex is incorrect and needs an escape sequence (\), before it would just now show results, now it gives you feedback from rg (in the below, in order to search for [ I needed to enter \[):

Respect your kindness and carefulness! I like this feature!


Dynamic user group list

What type of PR is this?

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

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

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

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

/area build

/area driver-kmod

/area driver-ebpf

/area libscap

/area libsinsp

/area tests

/area proposals

What this PR does / why we need it:
This PR introduces the support for dynamic users and groups management.
At the moment, users and groups are just loaded during startup, by libscap.
Moreover, we do not track containers users/groups. This means that a container that runs a process as uid 1000 on my system will be seen by Falco as being run by "federico".
That's obviously not true and a bug.
Inner workings of the PR is not super linear; it is the following:
Live:

libscap still loads and manages HOST user/group list, to avoid creating a scap files ABI break
libsinsp stores HOST user/group list on top of libscap, it a <container_id, list> map, with container_id == ""
a new class, sinsp_user_group_manager was created
moreover, resolve_container called for any new threadinfo to check if the thread belongs to a container, will check if the thread has an unknown uid/gid (given the container), and eventually will add it to the map.
useradded,userdeleted,groupadded,groupdeleted events were added to notify about user/group updates
All containers related users and groups gets deleted in a bulk once the container is deleted
Once per minute list of HOST users/groups is refreshed and any change is notified

Storing to scap file:

When saving a scap file, libscap still stores the list of HOST users/groups in the headers
moreover, a dump_users_groups api is called right after dump_containers, so that any user/group related events for initial state is stored, to allow to load any container-related initial user or group

When capturing from a scap file:

scap will load HOST users/groups from the header
all user/group related events dumped by dump_users_groups are parsed to rebuild the initial state for sinsp

Obviously we are not able to parse users/groups information inside containers.
This means that we are only able to store the uid/gid inside the container, but we cannot extract username/user home dir or other infos. A default value <NA> is provided.
All of the container-related Falco rules should be updated using user.uid instead of user.name, IMO, to avoid always printing <NA>.
Which issue(s) this PR fixes:

Fixes #149
Special notes for your reviewer:
There is currently a bug that breaks initial parsing of users/groups from pre-existing containers: #219
Does this PR introduce a user-facing change?:

new: users and groups are now managed dynamically per container

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

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

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

@FedeDP: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs
953af19339c8c0f9077df4a5e89db68d3fcaebff
link
true
/test build-libs

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

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

@FedeDP: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs
953af19339c8c0f9077df4a5e89db68d3fcaebff
link
true
/test build-libs

build-libs-with-chisels
953af19339c8c0f9077df4a5e89db68d3fcaebff
link
true
/test build-libs-with-chisels

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

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

@FedeDP: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs
953af19339c8c0f9077df4a5e89db68d3fcaebff
link
true
/test build-libs

build-libs-with-chisels
953af19339c8c0f9077df4a5e89db68d3fcaebff
link
true
/test build-libs-with-chisels

build-libs-bundled-deps
953af19339c8c0f9077df4a5e89db68d3fcaebff
link
true
/test build-libs-bundled-deps

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

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

@FedeDP: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs
953af19339c8c0f9077df4a5e89db68d3fcaebff
link
true
/test build-libs

build-libs-with-chisels
953af19339c8c0f9077df4a5e89db68d3fcaebff
link
true
/test build-libs-with-chisels

build-libs-bundled-deps
953af19339c8c0f9077df4a5e89db68d3fcaebff
link
true
/test build-libs-bundled-deps

build-libs-minimal
953af19339c8c0f9077df4a5e89db68d3fcaebff
link
true
/test build-libs-minimal

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

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

/test build-libs-arm

New changes are detected. LGTM label has been removed.

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

Needs approval from an approver in each of these files:

OWNERS [FedeDP,leogr]

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

@FedeDP: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-arm
a8b39e8ff890e4939ac72a77fe44f41c6cf0cd9b
link
true
/test build-libs-arm

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

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

@FedeDP: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-arm
a8b39e8ff890e4939ac72a77fe44f41c6cf0cd9b
link
true
/test build-libs-arm

build-libs-minimal
a8b39e8ff890e4939ac72a77fe44f41c6cf0cd9b
link
true
/test build-libs-minimal

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

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

@FedeDP: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-minimal
a8b39e8ff890e4939ac72a77fe44f41c6cf0cd9b
link
true
/test build-libs-minimal

build-libs-arm
6c56b0e7ba4e62316aef205ed35af99addfa5ad1
link
true
/test build-libs-arm

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

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

@FedeDP: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-minimal
a8b39e8ff890e4939ac72a77fe44f41c6cf0cd9b
link
true
/test build-libs-minimal

build-libs-arm
6c56b0e7ba4e62316aef205ed35af99addfa5ad1
link
true
/test build-libs-arm

build-libs
6c56b0e7ba4e62316aef205ed35af99addfa5ad1
link
true
/test build-libs

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

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

@leogr  care to re-approve? :D

LGTM label has been added.  Git tree hash: ff4658ccddb535515f809c0f0a821e0718f496fa

About the events, I'm not sure why we want them.  It's not that the users were really added, it's just that the reconstructed state learned about the users. Why do you need ppm events for that? The reconstructed state adds/removes/changes all the time based on the event parsers, and we don't have separate events for learning about fds, threadinfos, etc.
About the uids and users themselves, you're right that there's no distinction between a uid from the perspective of its current namespace, and the "real" uid from the perspective of the host. Same thing is true for users, although it's probably a bit worse for inside containers, as it's fairly common to use a uid (like 65535) for all processes in the container, without having a /etc/passwd entry for that uid in either the container or on the host.
For pids, there's a good design and set of fields, with proc.vpid/proc.vtid representing the pid/tid from its current namespace, and proc.pid/proc.tid representing the pid/tid from the host namespace. I think that's the model we want to have, although I'm not sure how we make that change in a compatible way, as user.uid currently means the uid from its current namespace (the opposite of what we want).

New changes are detected. LGTM label has been removed.

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

f00285e Merge branch 'master' into dynamic_user_group_list

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

@FedeDP: Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

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

@gnosek What do you think about this one?
Do you think that events are overkill too?

@FedeDP: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-libs-with-chisels
3af5639863eb01961b6b60f66961f34e80761e50
link
true
/test build-libs-with-chisels

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

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

@deepskyblue86: changing LGTM is restricted to collaborators

In response to this:

neat

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

/test build-libs-bundled-deps

LGTM label has been added.  Git tree hash: 16d0980147580fb5c0e0b440da5ddbbc1a17438e

I've got an ongoing discussion with @mstemm on this one.
/hold

/unhold


add a snap to point feature

it would be great to have a snap point  to other points,

This would be upstream in Leaflet.draw - closing here, feel free to re-file there.


Optimize StringName by storing StrRange<char> instead of const char * for static C strings.

This avoids needless repeated strlen calls for simple operations on StringName, and will enable further optimizations in follow-up PRs.
The PR also adds the String::ascii factory method for String which constructs the string from a known-length ascii string. No implementation is needed for this constructor since it merely calls the appropriate copy_from.
Benchmark
I tested one of the most affected beneficiaries, which is operator[] since it called strlen to verify the index. string_name[x] now runs at complexity O(1) instead of O(n), which can lead to a 4x speed up for one arbitrary long StringName actually used in the codebase:
	StringName test = StaticCString::create("node_configuration_warning_changed");

	auto t0 = std::chrono::high_resolution_clock::now();
	for (int i = 0; i < 100000000; i ++) {
		char32_t c = test[5];
	}
	auto t1 = std::chrono::high_resolution_clock::now();
	std::cout << std::chrono::duration_cast<std::chrono::milliseconds>(t1 - t0).count() << "ms\n";

This yields

452ms for master (ba2c5c1e6196b774d55baa45de54aab530db08e9)
114ms for this PR (487cc07c67b24593ffbd3211b0879d3142346bcd)

Other beneficiaries are (currently) length(), operator String() and the StaticCString constructor, which can now (sometimes) be evaluated for length at compile time rather than needing to call strlen.
Discussion
Future PRs should address other functions like operator==, which could be accelerated by using the known length.
A future PR could also accelerate D_METHODP by taking StaticCString instead of const char* as arguments, so the strlen can be evaluated at compile time there too.

How are you benchmarking this exactly ? Is it in a separate project ? And is it in release build with same flags as Godot ? I don't really imagine a decent optimization pass not removing your loop entirely here.

How are you benchmarking this exactly ? Is it in a separate project ? And is it in release build with same flags as Godot ? I don't really imagine a decent optimization pass not removing your loop entirely here.

The loop is not removed because test[5] is blackbox to the calling function, as it is defined in another module, and thus cannot be safely avoided.
I am calling this code from test_main in test_main.cpp.

How are you benchmarking this exactly ? Is it in a separate project ? And is it in release build with same flags as Godot ? I don't really imagine a decent optimization pass not removing your loop entirely here.

The loop is not removed because test[5] is blackbox to the calling function, as it is defined in another module, and thus the call cannot be safely avoided (without LTO or SCU anyway). I am calling this code from test_main in test_main.cpp, compiled with scons tests=yes, i.e. -O2.

If I compile it in Godot itself, I have something similar (well 1120ms, but I have a pretty weak machine), so yeah the compiler totally fails to inline that (not even sure it tries). So a x4 speed up would be really nice to have 👍 .

The PR is (technically) still ready for review, but I had to explicitly call latin1 parsing for static c strings, to avoid behavior change, which is incorrect. This is further discussed in https://github.com/godotengine/godot/issues/100641.
I have added FIXMEs to track the mismatch, which should be "good enough for now" until we have a consensus on https://github.com/godotengine/godot/issues/100641.


beta 7 - ipad mini 4 wifi

I have tried several times with different apple ids.. but beta 7 on ipad mini 4 doesn't work.. just restarting after a few secnds or minutes than nothing happens..
version 10.2
Never jailbreaked before.

@keiskodeniz me too I have this exact issue on my wifi iPad Air 2 on iOS 10.2

You will have to try more times, it worked for me after 22 tries on an Air 2 WiFi 10.2.

dang, that sucks

22 tried, are you kidding lol ?

@keiskodeniz not kidding, lol. @msamuel002 hopefully it gets better in the final version, this is the first supported beta for these two devices.

worked first try for me. You can close this

i am puzzled that this is happening, and will try to improve reliability.

how did you count it lol..

My screen goes all funny and has these white lines everywhere when it sometimes fails. I think it's text but it's way to small to read @kpwn

@nicogibbons mee too.. and sometimes it says failed, retry.. once I click, my device restarting with apple logo immediately.

12th time worked a charm for me :).

i didnt count it lol but just pressed on go again.. i think maybe 12-13 in a row.

now i see white screen before my device restart and apple logo appears.

lmao

it always eventually works

worked after 30 tries loool..

after 5 minutes restarted it self :(

It works with me after 6 times

Yeah this sucks on ipad mini 4

On ipad mini 4 it does keep rebooting without installing cydia so i put my ipad on the wall charging and it does finally install cydia hoping the next beta or the final release will be more stable on ipad mini 4 and install cydia from the first time

Before jailbreaking: Put iPad in airplane mode, then restart. Open Yalu, wait 10 seconds, then hold the go button for 5-7 seconds. All of these can raise your chance of successfully jailbreaking.

We can jailbreak but the problem is it isnt stable!!

Yeah, I did see that some people were having trouble getting it to jailbreak as well, that's why I commented that.

For sum random thing I have I pad Air 2 after the 7days ran out so deleted the app and reinstalled with inpact now jb 1st time every time and no reboots

Wow, lucky


[Script]: GeeksForGeeks Scrapper

Aim
Scrap courses from the GFG webpage
Details
Three categories of courses will be scrapped and result will be in form of dictionary
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

/assign


Fixed function name typo in retreiveObjects

Fixes #17

AFAICS we're versioning / packaging this meteor package so this minor change can safely be merged to master anytime. We'll make sure to include a note in release notes next time we release.


Remove Style Dependencies

Somewhere, there is a master style dependency that was created when making the D3 timeline. This is affecting all other pages in the stylesheet directory. Remove this connection and make styles specific to the timeline and independent of other pages.

@kbaumzie this is fixed on my end, I'll commit when I work on the project at 2 today.


Price/Hour Sort

Since the implementation of selecting a number of games to display instead of defaulting to all of them, I've noticed the Price/Hour sort feature hasn't been working for me.

It's not broken, if you sort twice you can notice that price/hour sorts correctly in descending order.

Still running across this:

Also I just wanted to say, thanks for your timely response earlier.

So that's why I didn't see the issue, it only happens on certain profiles. Has to be a datatables issue.

Whenever I sort by price/hour, it seems to just put the games in a random order with unpayed games either at the top or bottom.

This instance has the first lot in order and hen just starts throwing them in randomly.
http://imgur.com/t8k2mx9

@trapbuilder2 This is basically a datatables issue, and I am not sure to fix it, as I set data-sort on every column/row.

Actually nevermind, I just fixed the issue.


Add memoization to resources

const A = createAtom({
  default: 42,
})

const C = createResource({
  get: async () => {
    return await fetch(`/${A.get()}`);
  }
);

await C.get(); // network request
await C.get(); // cached

A.set(3);
await C.get(); // network request
await C.get(); // cached

A.set(42);
await C.get(); // cached

A.invalidate();
await C.get(); // network request
await C.get(); // cached

Memoization will stringify and hash all dependencies, it will then store the return value of the resource/selector to be reused at a later time if the same dependency hash is encountered again.

Resources are memoized selectors optimized for cacheable, IO bound, or computationally heavy operations. Such as network requests, reading from a file, or calculating a complex calculation.

Ex:
const fileName = createAtom({
  default: 'cat.png',
})

const file = createResource({
  get: async ({ get }) => {
    return fetch(`/${fileName.get()}`)
  }
})

const fileEdges = createResource({
  get: async ({ get }) => {
    return getEdges(await file.get())
  }
})

createEffect(async () => {
  console.log(await fileEdges.get())
})

Closed in favor of #28


0.2.51 broke sysctl API

ewnough said, API changed in mutability on first parameter and ptr/size? and that breaks crates like e.g. sysctl ...

ewnough said,

libc has a million APIs, so it would at least be nice to know which API, which target triple, minimum working example (no dependencies) with instructions to reproduce, etc.

nightly-x86_64-unknown-linux-gnu
sysctl(...)  call changed mutability of parameters ...
reproduce: try to compile sysctl crate which takes libc and uses sysctl(..) calls

Read https://github.com/rust-lang/libc/pull/1312/files .

The last commit that changed sysctl on x86_64-unknown-linux-gnu is from 2 years ago (https://github.com/rust-lang/libc/commit/343b7c15bea8777399ab5e667239e6bbe8239542) and landed on libc 0.2.33. There aren't any commits between 0.2.50 and 0.2.51 touching that API.

rust-semverver also reports no breaking changes between 0.2.50 and 0.2.51 on x86_64-unknown-linux-gnu (https://travis-ci.com/rust-lang/libc/jobs/188694789#L819) and it checks for changes in function signature types.

thanks, yet somehow it looks like updating to .51 broke sysctl here. I will try to get you an example today to verify it's not something else

Looked @ it further, it looks like an issues taht has nothing to do with newest libc release but been there since a bit. confusing, it compiles on other plaforms (BSD & MacOS)
Affects stable and nightly ...
--- here's the info, code taken out directly from sysctl-rs crate
extern crate libc;
use libc::{sysctl, c_int, c_void};
fn main() {
let oid: [c_int; 2] = [0, 3];
let mut len: usize = 32;

// We get results in this vector
let mut res: Vec<c_int> = vec![0; 32 as usize];

let name = "abc";

let ret = unsafe {
    sysctl(
        oid.as_ptr(),
        2,
        res.as_mut_ptr() as *mut c_void,
        &mut len,
        name.as_ptr() as *const c_void,
        name.len(),
    )
};

}
[prz@rahi-01 ~/gitlab/sysctl-break]$cargo +stable build
Compiling sysctl-break v0.1.0 (/home/prz/gitlab/sysctl-break)
error[E0308]: mismatched types
--> src/main.rs:16:13
|
16 |             oid.as_ptr(),
|             ^^^^^^^^^^^^ types differ in mutability
|
= note: expected type *mut i32
found type *const i32
error[E0308]: mismatched types
--> src/main.rs:20:13
|
20 |             name.as_ptr() as *const c_void,
|             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ types differ in mutability
|
= note: expected type *mut libc::c_void
found type *const libc::c_void
error: aborting due to 2 previous errors
For more information about this error, try rustc --explain E0308.
error: Could not compile sysctl-break.
To learn more, run the command again with --verbose.
$cargo +stable --version
cargo 1.33.0 (f099fe94b 2019-02-12)
$uname -a
Linux 3.10.0-693.2.2.el7.x86_64 #1 SMP Tue Sep 12 22:26:13 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Is there a version of libc that compiled that example for that target correctly?

https://github.com/johalun/sysctl-rs/issues/22  seems like crate was never tested on linux albeit I remember ages ago to have it working


Python 3 and non-ASCII/UTF-8 data

While implementing Python 3 support in Salmon (see moggers87/salmon#7 ), I stumbled upon this: https://bugs.python.org/issue19662
tl;dr: Python's SMTPd is absolutely useless in anything less than 3.5 (assuming the above patch made it into the 3.5 release)
We should start testing with non-ASCII/UTF-8 data and fix the library to work with Python 3.5 and then decide what do about 3.3 and 3.4.

Python 3.5+ exposes a kwarg decode_data, we should do the same.

OK, so I don't think this is an issue for us because code for LMTPChannel came from Python 2.7, so we never renamed all the private members as happened in Python 3.3 and thus never tried to decode to unicode.
Closing this issue because it turns out not to be our bug :)


Add FailIf methods accepting a collection of errors

Adds methods to FailIf that will accept a collection of Error objects.
Closes #189

Thanks for your time. Please also extend the readme. Then I can merge it.

@altmann All set.  Let me know if any other changes, thanks!


Add benchmarks for queue

Please provide a description of this PR:

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ipv6_istio
1a441bedf96a71feaa499b26c83aff0a6c344749
link
true
/test integ-ipv6_istio

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

/retest

@howardjohn @hzxuzhonghu should this get cherrypicked to 1.15 branch?

Doesn't matter
On Mon, Aug 15, 2022 at 7:54 AM Greg Hanson @.***>
wrote:

@howardjohn https://github.com/howardjohn @hzxuzhonghu
https://github.com/hzxuzhonghu should this get cherrypicked to 1.15
branch?
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/40406#issuecomment-1215108261, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXJBD75ONEFCUNBHHQLVZJK23ANCNFSM56I5PLAQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


cc-proxy/cc-shim high availability

From @sameo on December 2, 2016 17:36
If cc-proxy crashes:

all cc-shim instances terminate.
cc-proxy will not be able to restore its internal state after restarting.

We need to work on:

Have cc-shim retry connecting to the proxy when the socket is closing/disappearing
Have cc-proxy re-build all its states when restarting, based on the stored information

Copied from original issue: 01org/cc-oci-runtime#505

From @laijs on December 4, 2016 23:46
the virtio-serial is not package based transport, it seams hard to find the message header when cc-proxy re-connect to hyperstart.

Hi @dlespiau, do you do anything related to this feature? If not then I'd like to hack on this if you don't mind.

Hi,
I'm doing the low level part of this, framing on top of the Host<->VM serial link so the proxy can recover the start of a frame when reconnecting to a running VM.
I haven't started on the task to save an on-disk state that the proxy can read from when starting again though. You could take that part.

Hi @dlespiau,
That's awesome.
I've started experimenting exactly with on-disk re/store of the state as it's most obvious part for me. Okay. When I have something substantial to show I'll post here a WIP PR.
Cheers.

Thanks @dvoytik! Feel free to create an issue and assign to yourself (and maybe reference this issue) so it's clear to the whole team that that is something you're working on.

@jodh-intel, done. Although I can't assign it to myself.

@dvoytik - thanks - assigned.

@dlespiau any chance you have left some work in progress about the re-sync of a lost frame between proxy and VM serial port ?

Unfortunately, the work has been wiped out when I dd'ed /dev/urandom to my hard-drive :/

@dlespiau no worries, that's what I was expecting :p
That's what you do when you move to something else !

BTW, we have a public IRC channel #clearcontainers on freenode. Come discuss about containers if you're interested ;)

@sboeuf - could you outline what you know about this problem?

@jodh-intel I'll go further, trying to cover all the cases, and how our components should be modified.
The case is simple, we have Clear Containers running, meaning all components runtime/shim/proxy/VM(agent) are up and running. When the proxy crashes, we have shim/runtime/agent detecting the proxy disconnection while they are trying to communicate with.
Here what should do all the components upon this detection:

Shim

Try to reconnect for some time (already handled by this PR https://github.com/clearcontainers/shim/pull/54)
Buffer all the inputs and signals that cannot be forwarded to the proxy while it is getting restarted. When the connection is established again, the shim should send everything that has been buffered.
Save the last command so that we can re-send it after the reconnection to the proxy. Otherwise it's gonna be lost...

Agent

Handle gracefully the re-connection of the proxy to continue properly where we left.
Buffer all outputs supposed to go through STDOUT/STDERR, so that the agent can send them after the proxy re-connection. Specific to IO channel.
Save the last command that got executed while the proxy was crashing, and save the result. The idea is that when the proxy is gonna reconnect, it's gonna send again the last command because it didn't get the result (this command is really gonna be triggered by the shim or the runtime when they reconnect). For that reason, the agent should analyze the command sent by the proxy after it reconnects, and not execute it (in case that matches the last command), but send the saved result, to avoid running the same command a second time. That way, the proxy will receive the result of this command.
In the same way, we should always save the last outputs that we are sending. This would allow the agent to resend the result when the same command is submitted from the shim or runtime, but that we don't want to re-run the command for real, because it could have different results.

Runtime

Try to reconnect to the proxy.
Re-send the failing command. We should not report the command as failing unless this is not related to the proxy crash, but really because of an agent error.

Proxy

Save the most recent states as soon as a modification occurs. Basically, every time a new token/sessionID is created because the runtime asked for. We need the proxy to have the exact map of tokens and seesion IDs when it gets recovered, so that it can directly receive outputs coming from the agent (the last one that never made it through + buffered ones).

@sameo @grahamwhaley @jodh-intel I might have missed few corner cases, but I'd like to get your input on this. This is pretty important since we need to agree before we can open the corresponding issues and start the implementation.

Hi @sboeuf - thanks for this. If you don't mind, I'll merge the above with my notes and put it into a draft design (https://github.com/clearcontainers/runtime/issues/683) doc showing (a) what we have today and (b) what we want in the future...

@jodh-intel great thanks !

But I'd like to get some feedback about it too. Does that make sense for everyone ?


Add missing WebpushFcnOptions entity

Describe your environment

Operating System version: Windows 10
Firebase SDK version: latest
Library version: any
Firebase Product: messaging

Describe the problem
Documentation for Firebase HTTP v1 API says that WebpushConfig can contain WebpushFcmOptions representing options for features provided by the FCM SDK for Web.
But Java client for Firebase Admin SDK doesn't include WebpushFcmOptions, so it's not possible to use this API feature.
Suggestion
I suggest to implement WebpushFcmOptions class and include it in WebpushConfig.

PR was merged, issue is now resolved


automation, travis-ci: Separate integration tests

In order to parallelize the integration test run, separate the nm
subpackage tests from the rest and dedicate for them a CI job.

Coverage remained the same at 65.969% when pulling 0acc60b815c1449d496d82ce53c9b33a7e4cc35f on EdDev:separate-integ-tests into 9183fddf1ed18c58bfc7a2dffbde932938a1bddd on nmstate:master.

Coverage remained the same at 65.969% when pulling 0acc60b815c1449d496d82ce53c9b33a7e4cc35f on EdDev:separate-integ-tests into 9183fddf1ed18c58bfc7a2dffbde932938a1bddd on nmstate:master.

Coverage remained the same at 65.969% when pulling 0acc60b815c1449d496d82ce53c9b33a7e4cc35f on EdDev:separate-integ-tests into 9183fddf1ed18c58bfc7a2dffbde932938a1bddd on nmstate:master.

Until the coverage report is solved, I do not think we can go forward with this separation.
I am closing this PR for the time being.


Fix precedence of operators

Currently there are parenthesis needed in the following example:
let ab = (char("a") ~ char("b")) ^^ { String([$0, $1]) }

That should not be needed because ^^ should have a higher precedence than ~.

Is fixed in release https://github.com/BenchR267/Parsel/releases/tag/2.1.0


[BUG] Spam accounts gets created trough local account (no way?!)

Description
Spammers found a way to register an account without using the given Login Providers (as you can see from the screenshot below)
Gitea Version
1.22.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots

Git Version
2.34.1
Operating System
Ubuntu 20.04 LTS
How are you running Gitea?
Docker-Compose V2
Database
MySQL/MariaDB

You can enable captcha and other methods to avoid spammers. If you want to disable local user, it's duplicated of #13606

Thank you ! 🥇

I have saddly to say, that Captcha is already enabled.
And the given thread from you is also saddly not really helpful to get that issue fixed :-(

I have saddly to say, that Captcha is already enabled.

I've enabled reCAPTCHA and verified that it appears on the registration website. Sadly it does nothing to stop the account spam I've been battling over the last few days.

Disabling local user have been implemented in #32687 and will be released in v1.23.


Installing lightweight-charts in react project breaks react

Steps/code to reproduce:
npx create-react-app my-app --template typescript
npm install lightweight-charts
Result
Unusable react app. While installing this library, it somehow breaks react packages

Just wonder what can happen so one package might break another one.

Unusable react app

What does it mean?

it somehow breaks react packages

How did you notice it? What happened?

Steps/code to reproduce

Is it all you did to reproduce it? What nodejs version you have? What npm version?

By unusable react app I mean the app does not compile, JSX does not work, react import statements shows as not found by typescript.
NPM version: 6.14.13
Node version 14.17.1
And yes, thats two commands to reproduce the issue. While installing this library with npm, I have noticed that it takes longer than creating react boilerplate. Also observed that it removes lots of packages under installation, which might be the case.
To solve the issue i ran npm install again. However, I expect this library to not remove any existing packages.

While installing this library with npm, I have noticed that it takes longer than creating react boilerplate. Also observed that it removes lots of packages under installation, which might be the case.

Didn't you try to run yard add lightweight-charts? It seems that when you run npx create-react-app my-app --template typescript it uses yarn to install packages, that's why you see changes in node_modules. Also, you can run npm install right after npx create-react-app my-app --template typescript just to make sure that your node_modules are "created" with npm.
Thus, since it is not related to lightweight-charts I'm going to close this issue. I think that you might have the same issue with any other package you may use.


Fix gcc builds failing on windows

Addresses 3 seperate errors/failings that occured for me when trying to build on windows with mingw
platform\windows\gl_manager_windows.cpp: In member function 'void GLManager_Windows::_nvapi_disable_threaded_optimization()':
platform\windows\gl_manager_windows.cpp:118:32: error: cast between incompatible function types from 'FARPROC' {aka 'long long int (*)()'} to 'void* (*)(unsigned int)' [-Werror=cast-function-type]
  118 |         NvAPI_QueryInterface = (void *(__cdecl *)(unsigned int))GetProcAddress(nvapi, "nvapi_QueryInterface");
      |                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

A define existed for wglGetProcAddress, but not GetProcAddress like most other Windows files; that's now fixed
platform\windows\display_server_windows.cpp: In member function 'virtual void DisplayServerWindows::set_icon(const Ref<Image>&)':
platform\windows\display_server_windows.cpp:2412:83: error: passing NULL to non-pointer argument 4 of 'LRESULT SendMessageA(HWND, UINT, WPARAM, LPARAM)' [-Werror=conversion-null]
 2412 |                 SendMessage(windows[MAIN_WINDOW_ID].hWnd, WM_SETICON, ICON_SMALL, NULL);
      |                                                                                ^~~~

Typecasting the NULL values as (LPARAM)NULL fixed the errors
'C:/Tools/msys64/mingw64/bin/x86_64-w64-mingw32-objcopy' is not recognized as an internal or external command,
operable program or batch file.
'C:/Tools/msys64/mingw64/bin/x86_64-w64-mingw32-strip' is not recognized as an internal or external command,
operable program or batch file.
'C:/Tools/msys64/mingw64/bin/x86_64-w64-mingw32-objcopy' is not recognized as an internal or external command,
operable program or batch file.

Not technically an error, but .debugsymbols files weren't properly generating because objcopy and strip don't have any prefix. Passing an empty arch value returns the expected path but with no erroneous prefix

In many cases they do, it depends on distribution, so code probably should try both and check if files exist.

Oh! Didn't realize that was a possibility, good to know; I'll adjust accordingly

Adjusting the Python to check for multiple files is a bit beyond the scope of what I expected to do this PR, so I'll leave the old version as-is considering it's functional on some distributions

Thanks!


Chrome 49.xx 无法打开

Chrome 49.xx 版本打开pdf流文件，报缺少PDF文件，但是在Chrome 49+以上版本是可以打开的，是否存在低版本兼容问题

Closing since we can only communicate in English.

Version 49.xx of Chrome opens PDF stream file and reports lack of PDF file, but it can be opened in Chrome 49+ and above versions, is there any problem of low version compatibility

Chrome 49 is over three years old, so I'm not surprised that it doesn't work anymore given that we only support recent Chrome versions. You'll have to upgrade your browser.


Support getParameter's showDetails, allParameters

getParameter supports document with fields showDetails, allParameters, etc. We should support them.
We should also simplify implementation and tests.

I'm interested to continue working on getParameters


[BUG] If a task only specifies resource limit, admin sets the request to a value potentially lower than the limit

Describe the bug
If a task sets memory_limit=200Mi, admin will set the memory_request=500Mi since that's the default it's configured with. This creates an invalid spec. Limit has to be >= request.
Expected behavior
Admin should set request == limit if limit is set, or to the default if not... and should do the same for the limit (set it == request if not set or to the default limit if not set)
Flyte component

[ ] Overall
[ ] Flyte Setup and Installation scripts
[ ] Flyte Documentation
[ ] Flyte communication (slack/email etc)
[ ] FlytePropeller
[ ] FlyteIDL (Flyte specification language)
[ ] Flytekit (Python SDK)
[X] FlyteAdmin (Control Plane service)
[ ] FlytePlugins
[ ] DataCatalog
[ ] FlyteStdlib (common libraries)
[ ] FlyteConsole (UI)
[ ] Other

Environment
Flyte component

[ ] Sandbox (local or on one machine)
[X] Cloud hosted

[X] AWS
[ ] GCP
[ ] Azure

[ ] Baremetal
[ ] Other

Additional context
https://github.com/lyft/flyteadmin/blob/2a065109c8b14f560ef27aa74df67b157c52d9d1/pkg/manager/impl/execution_manager.go#L301-L303

@EngHabu Thank you for filing this bug


Add kafka cluster create test with our simplekafkacluster example and rename zookeeper cluster

Description
This PR adds a test case for creating a kafka cluster, to be more specific the simplekafkacluster example that we have. It also updates the zookeeper cluster naming to zookeeper-server from just zookeeper.
Type of Change

[x] Other (test)

Checklist

[x] I have read the contributing guidelines
[x] I have verified this change is not present in other open pull requests
[x] All code style checks pass
[x] New code contribution is covered by automated tests
[x] All new and existing tests pass

TODO

Add uninstall steps.
Fix pod readiness checks
Make the test slow-failing but ordered somehow

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your<EMAIL_ADDRESS>seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

I think we should do the renaming in different PR.

I think we should do the zookeeper cluster renaming in different PR.

I tend to agree, I was just a bit lazy because this PR would then have to be based on that one, which means another branch added to this testing stuff, I'd rather not bother if possible, though it would be nicer.


Make oracledb run

Codecov Report

Merging #11 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #11   +/-   ##
=======================================
  Coverage   67.54%   67.54%
=======================================
  Files           5        5
  Lines         151      151
=======================================
  Hits          102      102
  Misses         49       49

Impacted Files
Coverage Δ

lib/knex.js
68.9% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@cemremengu  此仓库会迁移到 sunfuze 的个人仓库中进行维护~

@okoala I will submit a PR there then or he can fix this himself on the fly :) Thanks for your work!

<EMAIL_ADDRESS>


add(rpc): Adds getblockheader RPC method

Motivation
This is needed for block explorer support and has been requested by a mining pool.
Closes #8442.
Part of #8446 (always includes height in response when called with verbosity = 2).
Specifications & References
https://zcash.github.io/rpc/getblockheader.html
Solution

Adds a getblockheader RPC method like the one in zcashd

Related changes:

Adds height field to getblock response when called with a height if verbosity == 2

Tests

Adds a snapshot test for querying by height/hash and with verbose being true/false
Adds a vectors test

PR Author's Checklist

[x] The PR name will make sense to users.
[x] The solution is tested.
[x] The documentation is up to date.
[x] The PR has a priority label.

PR Reviewer's Checklist

[ ] The PR Author's checklist is complete.
[ ] The PR resolves the issue.

zcash-rpc-diff util output with verbose = true:

 {
   "hash": "000000002c2063bab0acae547bab7e0309db8e1b7003e9c01eb423c0166d5ac9",
-  "confirmations": 2683651,
+  "confirmations": 169203,
   "height": 10000,
   "version": 4,
   "merkleroot": "e093171fc092c4bc0598c6d475489f892b177e3c6139ca680b064787093e2d1e",
-  "finalsaplingroot": "fbc2f4300c01f0b7820d00e3347c8da4ee614674376cbc45359daa54f9b5493e",
+  "finalsaplingroot": "0000000000000000000000000000000000000000000000000000000000000000",
   "time":<PHONE_NUMBER>,
   "nonce": "000000000000000000000000000004cc00000000000000000000000000000000",
+  "solution": "00275a139867b3816117f666e4ba1442fb14dbdebd1301af4f33e934f5cc56eb0f1c70a562d9ec5fe0912126fd433fb55699e285b5689edf15fab1ac9dc853320a67930d13375df86cb39cdd385e6dbca3f909ac07a5cf1279637001afc1947c8f762121ad2772e1a74d16870881349c3bec75d7158965b17679055cb10b15df4a5152d806a96540b6eeced2d4272b501c69e62a300ae5c6a855f7870f02cf651863ea9f20765c3900772233d5061af31511e2da4eee4885176071804c1080f51f0e8f81abb745c22bd14adf5192d733d9b20f6e18ada5cfa7638d04e35c38f7a1613714fb26a84123cc5ae31e5fd1a4e816d7b254f9a9d22e9973630d7758d9c1092dac5a08831b44a5eac348d7dc7aca0ee37450324c9292e98751916dfebdcd3d250fa0db249fe703994cdf7a69cef57685562db17e3dd43cc442de94463e186174dc4a3454c4b8e4c65e30bff403024468345a216739a42c80d3695c951cc407f1efd81057c40847a23a11b7dc1448172fb2ad3ca9cb29cf057c6eb79ae56fa589e211d0f11fceff17c6be531f283ac21711902461046be5a642f9f8bf5406df53b602e82c3f4f95f06f4ee6254750cd5e862896fbe4602894d9c9914ba9a6f382197c5569e3428ffabb3d0c132bbb37826788abd107e274252edead9aac199e4574ca8ea16fa1358b4fa2a867d44b6af725555d56d7077358f3f5afea45d616314dcefa6b4df9c65b9a8e3cc832c8b2ebde9be1b5a6f081d81417197a7ca3ca0d7afec4a89e7bd915d8678edceae969ffe8b7da4515870f372f65bb05707dc5b6a03c44e6bca3ff211408e0c4c672c5266318cbf6372067aba9bedf8f5ea82e117688d1108cd5cef4c6065fe107e21334f5a78f1ec206bf21a14387472572ee6afd3d80ef11156b671f3ee5782f152a4b2671d20762cdd0a2680f16e74200360df7bb60797f4caea02dc053052c6e1235212006da6a978ab122d1d43ee2091e4299616b60b2f9b519c1111a3b62236f3e51c43d917007aedaa5ddcaa55591f7171962a79f39a5a6d67a39de6301187f2b6119ebc8f17e1afcc9b06aa495de49b45185d650507b1bb5e7346dcba10b91f2e57e9bc7522aabd71b88bd1d5016e1103bc4c9eba31237d1389b0e271d39400d3923bb06632727b9e367449992d16cc2529cbbca9103150366bc23213b8b735b7abee660ef9c893cf5ff0b3fcb1493dbb29b76bc62de035317052ea7ed059e06f21294e88241147163449adac480d249a8b455034295ce8248a5a9358a03c6d470f8ecda6848bf3f66074e3ade5a0a20a703df52a970e486121c3f1c23b82882fe7a9717e9a1566062cab854b6e147b8dc7de233c75e1c085436c6c259984602c5d4922d17137bdb383464cc11dcc5d3aadb4778b9f2f772c8075a57e001e0e9df36960e17c8cc12def8dd324e2bf4bee59e4fcc8c5718d862e3682367d948445b7698111836f1108d08fce80f13acb7045579d6bd4261b3b272a8d166dc5d93d7675fcb96b98929b667fc86583eb8533006ee106a0b516712f36529656066c63ee5179fbe6856613c16d9df7b7d173645ff42d9c63aaa8d5a5b650fa4263b3928d3c5cda0a1af938db8289adde889461473fa73671241bf5a8914436fb3c8812d776b49aa01ef759141b5a55bdc18b3015669e4ed09345bbb6e02f0c2ae6f3ac9e9f62db263ad39e3b295dbddc3ff15634deda2d71b2fd907c9cf25e74a76ccef379d1f1a3429a5f4298341e7c0529855c7c9c91cb15dd1d30cd9b627a6e4b1dd5cec759b7c6da1ce1b0731da1b13ef8b90d90a9b16d521017658ba2831a6895851db21d255d61bcb27912eb4f7ac0b7699f36333fbe5983cb1ba395f15456db1808ae0b4dd4913277f5a1443",
   "bits": "1d01bf9d",
-  "difficulty": "00000001bf9d0000000000000000000000000000000000000000000000000000",
+  "difficulty":<PHONE_NUMBER>097095,
+  "chainwork": "00000000000000000000000000000000000000000000000000000a13fdd5bc69",
   "previousblockhash": "000000001298a3685fbc493751ff2309a9bcef7cefad4565642bafb43f71b4c6",
   "nextblockhash": "00000000980d28a4bd926c4c553f7eaa5b29d3a78e8423f3863b72edd258839e"
 }

It matches exactly when verbose is false, but the difficulty and finalsaplingroot fields aren't matching. It's possible the finalsaplingroot field will match after Sapling activation (my zcashd is still syncing). zcashd also includes the solution and a chainwork field.

The chainwork field is confirmed to be the cumulative work in the chain, which Zebra doesn't store in the finalized state. It's also undocumented so we can probably leave it until/unless someone requests it. It could also still be calculated by the caller by summing up the work for the chain up to the requested block.

The chainwork field was mentioned in the last Zcashd deprecation meeting and as it is an undocumented field it should be safe to ignore it in Zebra.

The failing test seems to be unrelated however it will be good to check that out in another issue/context.

@oxarbitrage can we get a final review here if it's all ok?

@mergify refresh

@mergify update

@mergify refresh

@mergify requeue

@mergify queue


Change the native library names to libSkiaSharp

I have just been working with @galvesribeiro to get SkiaSharp onto a ARM v6l Linux device (yay!) #18. One of the issues was that we had to re-build SkiaSharp just so that we could change the native library name in the [DllImport].
What are the opinions of changing the native library name to a uniform libSkiaSharp so that future Linux (or any other "normal" builds) can just use the Desktop assembly?
We might even remove the need for the .dll.config file currently. (just a guess)

And that is working as you can see! :)

Work being done in #81

Why not use dlsym/GetProcAddress and Marshal.GetDelegateFromFunctionPtr instead of DllImport? That will add a lot of flexibility in native library location like looking for correct CPU arch version in libSkiaSharp-x86.dll or libSkiaSharp-x64.dll depending on current platform.
Something like that (MIT-licensed):
https://github.com/kekekeks/evhttp-sharp/blob/master/EvHttpSharp/Interop/LinuxLoader.cs
https://github.com/kekekeks/evhttp-sharp/blob/master/EvHttpSharp/Interop/OsxLoader.cs
https://github.com/kekekeks/evhttp-sharp/blob/master/EvHttpSharp/Interop/Win32Loader.cs
https://github.com/kekekeks/evhttp-sharp/blob/master/EvHttpSharp/Interop/Event.cs (usage)

The only issue that I see is iOS static linker, but I think that a custom dlsym (skiasharp_dlsym or something)  could be implemented in the native code. We did it this way in our old skia-based backend in avalonia(aka perspex) and it worked quite well.

Are there any instruction on how this was achieved. I want to run SkiaSharp on native Linux but intel.

@jameswalmsley I just use a default name of libSkiaSharp.[a/dll/so/dylib]
I do this in the https://github.com/mono/SkiaSharp/blob/v1.53.0/binding/Binding/SkiaApi.cs#L48-L62
You should be able to just #if __LINUX__ or something. But, it should also fall back to the default "libSkiaSharp" and the mono runtime will automatically select the correct extension on the platform.


for element of value tooltip missing

This node doesn't have the floating tooltip in makecode for microbit.

We don't show a tooltip if the block is disabled. Try attaching it to an event (eg: on start or forever) and you should see a tooltip.


Fix: pkg name typo, output value should be KlusterletConfig type and filter out the nil items.

/assign @qiujian16

Please take review when you have time, thanks


Removing single quotes from api command

Does not appear necessary on Linux
Causes issues on Windows
unsure of Mac
fixes #547 , will need to be merged down to all branches

Thanks for this! I’ll review sometime this weekend. Need to find a way to get this into all the branches more easily; kind of a bummer but better for readers IMO


Get full source code

Is it possible to download the full source code of these samples? Much appreciated.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d55cdb6d-0144-0c97-c373-8728b20664a9
Version Independent ID: d55cdb6d-0144-0c97-c373-8728b20664a9
Content: Control templates - .NET MAUI
Content Source: docs/fundamentals/controltemplate.md
Product: dotnet-mobile
Technology: dotnet-maui
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hi @VanessaAk
Samples or each doc are gradually appearing, week by week. What happens is:

I add them to the maui-samples repo (https://github.com/dotnet/maui-samples).
Samples are ingested into the samples browser (https://docs.microsoft.com/samples/browse/?expanded=dotnet&products=dotnet-maui). This can take a few days.
I add a link to the sample, in the sample browser, to the doc.

I actually prepared the ControlTemplates sample yesterday, and will be checking it into the maui-samples repo today. I'll ping you when that happens.

@VanessaAk https://github.com/dotnet/maui-samples/tree/main/6.0/Fundamentals/ControlTemplateDemos
I'll leave this issue open until the link to the sample, in the sample browser, is added.

Hi David,
Thank you for the link it helped a lot. I was wondering if you had any samples that show how to implement a wizard in maui.
Vanessa
From: David @.>
Sent: July 14, 2022 11:55 AM
To: @.>
Cc<EMAIL_ADDRESS>@.***>
Subject: Re: [dotnet/docs-maui] Get full source code (Issue #694)
@VanessaAkhttps://github.com/VanessaAk https://github.com/dotnet/maui-samples/tree/main/6.0/Fundamentals/ControlTemplateDemos
I'll leave this issue open until the link to the sample, in the sample browser, is added.
—
Reply to this email directly, view it on GitHubhttps://github.com/dotnet/docs-maui/issues/694#issuecomment-1184614811, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2BMBZAJVX3SUIXHFJBJIJTVUAZ77ANCNFSM53QFBOCQ.
You are receiving this because you were mentioned.Message ID: @.***>

Hi @VanessaAk
Afraid not, right now.


Error: couldn't find a usable index.

Hi,
I am using pouchdb-find to do "tag" search locally on my pc with indexedDB.
All docs include a 'tags' field which is an array filled with tags, e.g. ['tagA','tagB','tagC']
1st, createindex like this.
db.createIndex({
index: {
fields: ['tags']
}
}).then( //do my db.find here)
2nd, I am trying to search for docs with a certain tag :
db.find({
"selector": {
"tags": {
"$elemMatch": 'tagB' // I also tried "$elemMatch":{"$eq":"tagB"}
}
}
})
but I got the following error.
Error: couldn't find a usable index. try creating an index on: tags. Make sure that only $eq, $gt, $gte, $lt, and $lte are used for the indexed fields.
later I modified the tags field from an array into a string like this      tags: "tagA tagB tagC" and I thought $regex might work on this.
db.find({
"selector": {
"tags": {
"$regex": 'tagB'
}
}
})
but, I got the same error above.
Something wrong with my code?  $regex, $elemMatch not working on indexed fields?

hi @he-yang you need another selector this blog post will explain it in a bit more details.

thank you for your reply. problem solved, and $regex and $elemMatch can only work "in-memory".
anyone else encounter the same issue can add {_id:{$gt:null} to your selector object and try again.

Great to hear.


[storage] enlarge DB block cache

Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/website, and link to your PR here.)

Feel free to re-open if you'd like to resume.


Futures??

So note sure this is the right place but it looks like Shea's focus has shifted more to Munki and I am wondering if JSSImporter will continue to keep pace with Casper changes?
Thanks!

Hey Everette,
Like any good open-source project, I'm always open to pull requests.
I asked around recently if there was anything that I had missed from recent JAMF announcements/releases in terms of new features that I needed to support in either python-jss or JSSImporter, and I didn't hear anything.
I haven't been able to do any development time or work on the issues for these products, but anyone who can send me code that they've tested that I can pull in would be able to contribute.

Thanks I will work with that in mind.


Serialization does not preserve backend name

Informations

Qiskit Experiments version: b40cb9887061136e26bffd62ee07d5afe79af2b0
Python version: 3.9.10
Operating system: Arch Linux

What is the current behavior?
Serialization does not preserve backend name
Steps to reproduce the problem
import json
from qiskit.providers.aer import AerSimulator
from qiskit_experiments.framework import ExperimentEncoder, ExperimentDecoder
from qiskit_experiments.library import StandardRB

backend = AerSimulator(method='statevector')
exp = StandardRB(
    qubits=(0,),
    lengths=list(range(1, 5)),
    seed=123,
    backend=backend,
)
data = exp.run()
data.block_for_results()
deserialized = json.loads(json.dumps(data, cls=ExperimentEncoder), cls=ExperimentDecoder)

print(f'Original backend name: {data.backend.name()}')
print(f'Deserialized backend name: {deserialized.backend.name()}')

Original backend name: aer_simulator_statevector
Deserialized backend name: aer_simulator

What is the expected behavior?
Backend name should be the same before serialization and after deserialization.
Suggested solutions
None yet. I'm not sure whether this is a bug in Qiskit Experiments or Qiskit Aer.

This is the result of AerSimulator lacking any serialization capabilities (e.g. settings() method or to_json). It's more serious than not preserving the name; none of the options (e.g. number of shots) is saved. This can be hacked in qiskit-experiment by adding a special case to the json.py file, but it's best to fix it in qiskit-aer. I leave it to @chriseclectic to decide what to do; I can do the qiskit-experiments fix.

Backends are not intended to be serializable for now, we should probably just set them to None when serializing.

Backends being serializable will never be guaranteed, we explicitly allow them to not be. Since backends are the entry point for executing/submitting circuits they often contain objects outside of a python context (such as compiled extensions or state in a compiled extension, hooks for async execution handles, etc) which precludes making them generally serializable.


Wifi Init Crashes on boot

Hi,
I'm using the latest commit in master of esp-at and the corresponding commit of esp-idf which is release/v4.0
after setting up the environment, I modified: export ESP_AT_MODULE_NAME ?= PICO-D4
here is what i got when i finish the make flash: (this even happens when using the default esp32 module)

@ShashaDDD Hi, could you please providing the AT+GMR, and AT commands sequence you input.


Document how to generates the documentation

Document how to generates the documentation.
This will help when we modify it, to be sure it is well generated.

The CI generates it using https://github.com/NVIDIA/TransformerEngine/blob/main/.github/workflows/docs.yml - if you submit the PR you can download the zipped version of the built documentation (as an example see https://github.com/NVIDIA/TransformerEngine/actions/runs/4805734879?pr=169)

That should be added in the doc.
Any idea where it should be added in the doc?
Also, could we update the actions to add a comment in the PR with the link to the doc when it is generated? It would make it more accessible.

The zip file link is good.


WMTS Service cannot be added to an Engine after Map Swap

A WMTS service that is created in one engine, cannot be added to another engine once a map swap is performed.

The reLoading of map in a map swap was ignoring wmts services. I added support  in the storage class to reload WMTS.
Test case :
Use branch 240:
Open a cesium map.
Add a wmts service.
map sawp to WW or Leaflet.
The test is a success if the wmts service renders on the map.

Reintegrate

Merged into the dev branch. Closing this issue.


Fix image build after #128 is merged

[ ] Modify the golang service to spawn a static http server for the frontend
[ ] Refactor Dockerfile to build the frontend and serve with the golang binary

Will this solve the issue we have with the UI trying to talk via localhost so requiring the port to be open for that to Fluent Bit?

Closed by #160


Add Support for Modules

JSD should support some form of Module based extensibility to be able to add features beyond it's basic functionality by internal Dev and 3rd parties

Modules no longer seem like a necessary or desired feature. closing for now


Sesotho (PH 1017) should link to Southern Sotho (sout2807), not Sissano (siss1243)

Thanks for this! The issue was fixed in the development version of phoible:
https://github.com/phoible/dev/blob/master/mappings/InventoryID-LanguageCodes.csv#L1018
https://github.com/phoible/dev
But has not yet been released to the website.


JFXDatePicker displays date incorrectly

According to https://material.io/guidelines/components/pickers.html a date picker should display the selected date in the top section like Mon, Dec 4 for December 4, 2017.  JFXDatePicker has the date there to display, except rather than display the date it displays the year (Mon, Dec 17).

you are right, thanks for pointing out the issue 👍


[Frontend] Checkbox get distorted for small screen

Deliverable -

[ ] Fix the checkbox of join us form for small screens

Screenshot of the bug -

Hi @Kajol-Kumari , can I work on this issue?

can i work on this issue

Hey @akshitakanojia please go ahead with this issue.
@Sandi-09 as we need to follow FCFS I request you to look for some other issue.


Binary operation got "AnalysisException" after doing kdf[key] = kdf[key] + 1

Hello, I'm new to koalas and trying to process spatial data based on Series or DataFrame.
When i modify a colum in a DataFrame like code sample below, an AnalysisException  is raised.
Code Sample
from databricks.koalas import DataFrame

data = {"a": [1, 2, 3, 4]}
kdf = DataFrame(data)
kdf['a'] = kdf['a'] + 1
print(kdf['a'] + 1)

Error Output
pyspark.sql.utils.AnalysisException: syntax error in attribute name: `((a + 1) AS `a` + 1)`;

Software versions
python 3.7.6
koalas 1.0.0
pyspark 3.0.0
spark 3.0.0

Is it a BUG? Hope for some help.

This is definitely a bug. Will take a look.


Return all active clusters when using 'org clusters' command

Resolves OSD-17668
Rewrite the org clusters ... command to return all active clusters by default. Previously, this command would only return the first 100 results with no indication that the result set was incomplete, and no way to fetch more results.
Outward facing changes:

Removed --active flag. This flag used to filter the result set down to only active clusters. This was no longer needed as this is now the default behavior
Added --all/-A flag, which will return all clusters for an org regardless of status. This is to still allow for the old behavior, but respect the shift in default behavior as noted in the previous bullet point
Updated Long description for the command and added multiple usage examples under Example that can be used by reviewers to test.
Don't allow both orgId AND --aws-profile with --aws-account-id to be present - only one or the other.
General logging improvements

Code Health changes:

Refactored exported SearchClusters function to be more independent of Cobra CLI for easier testing and external calling

There were two flags used in the function related to AWS flags that were defined in a common file somewhere else. While we should absolutely stop doing this, I wasn't comfortable touching it at this time.

Centralized call to printClusters to be in the command itself.

This is part of an effort I've been pushing to make all of our functions - even specific to a command - independent of Cobra itself. This allows functions to be re-used more freely and tested more easily.

Removed custom structs in favor of ocm-sdk structs for calls to the accounts_management API.
Refactored a branch of code that used to flow from "isAWSProfileSearch"

Prior to this, the old function searchClustersByAWSProfile would look up the org ID from the given AWS account info, and then call through to searchClustersByOrg, which was identical to the path taken when an org ID was present. I rewrote searchClustersByAWSProfile into getOrganizationIdFromAWSProfile which now only performs the one specific task it's named for. Then the two branches (aws vs. org ID) could be immediately consolidated back, making the flow of code easier to follow.

Rewrote searchclustersByOrg into searchAllClustersByOrg. The function will now continuously page to the end of the result set, 100 items at a time.
Rewrote createGetClustersRequest to use the more idiomatic notation for OCM API requests.

Instead of using a generic Get and manually providing an endpoint, search params, etc., we now chain function calls. This is more readable, easier to follow, and will return a specific API response of *v1.SubscriptionsListRequest instead of the generic *sdk.Request.

Removed filtering from printClusters

a function named "printClusters" should do just that - print the clusters that it is given. It is left up to the caller to provide the filtered list that it wants printed.

/lgtm


Can Make Palindrome from Substring (Leetcode-Medium)

Aim
Given a string s, we make queries on substrings of s.
For each query queries[i] = [left, right, k], we may rearrange the substring s[left], ..., s[right], and then choose up to k of them to replace with any lowercase English letter.
If the substring is possible to be a palindrome string after the operations above, the result of the query is true. Otherwise, the result is false.
Return an array answer[], where answer[i] is the result of the i-th query queries[i].
Note that: Each letter is counted individually for replacement so if for example s[left..right] = "aaa", and k = 2, we can only replace two of the letters.  (Also, note that the initial string s is never modified by any query.)
Details
I want to provide my c++ Code for this problem under HCSSoC
Programming language

[ ] C
[ ] C++
[ ] Java
[ ] Python

@Ayush7614 I want to provide my C++ Code Under HCSSoC


When a 'type=number' Control's value has its last decimal removed, cursor is placed at the beginning of input.

Hey!
Found this weird issue when creating an input with a float value. Created a gist here:
https://esnextb.in/?gist=87dc7cd3f897aeeed43b2c0f0d1435dd
Try backspacing from each of the fields to see the behaviour.
Cheers

@MixKCet Seems similar to these issues:
https://github.com/facebook/react/issues/7781
https://github.com/facebook/react/issues/7253
https://github.com/facebook/react/pull/7359
So this is unrelated to RRF, but a current issue with React itself.
Here's a simple workaround:
        <Control.text
          model='.floaty'
          type='number'
          step='.1'
          value={undefined}
        />

The above makes the control uncontrolled, so it can't be remotely updated, but it also avoids the React issues.

Huh, look at that. Thanks @davidkpiano!


Add proxy support

this is a continuation of #314 to address #227 fully

Coverage increased (+0.1%) to 69.963% when pulling 0a926f9a6bf39d7909fd43548f4c6d958e4402a0 on more-proxy-support into<PHONE_NUMBER>9c6c8e824bc3708fafabe0d6346892 on master.

Coverage increased (+0.1%) to 69.973% when pulling f6a160cd6ed22803c19cd9e2a00df1ae433db922 on more-proxy-support into<PHONE_NUMBER>9c6c8e824bc3708fafabe0d6346892 on master.

Coverage increased (+0.1%) to 69.973% when pulling c3c992f1a3163ad08b8e8129e6e8b3af534d252e on more-proxy-support into<PHONE_NUMBER>9c6c8e824bc3708fafabe0d6346892 on master.

Coverage increased (+0.1%) to 69.962% when pulling 60154157fbdf089bd0e9281cd4e33d5e683ca1ef on more-proxy-support into<PHONE_NUMBER>9c6c8e824bc3708fafabe0d6346892 on master.

Coverage increased (+0.1%) to 69.967% when pulling 60154157fbdf089bd0e9281cd4e33d5e683ca1ef on more-proxy-support into<PHONE_NUMBER>9c6c8e824bc3708fafabe0d6346892 on master.


Correct allocated memory accounting for vespalib::string.

@arnej27959 : please review

You might want to add a unit test.

The unit test was compiling with clang.


Fixed implementation to re-order spec tag values

Added code and explanatory comments.

aha, this makes sense, because any spec_hierarchy tags provided for a catalog item represent what the registered type plan is converted from -- as opposed to that tag's meaning for an instantiated entity where that list represents what the type plan is converted to or derived from.  good spot.  merging.


migrate transform logic from axis to grid

Quick attempt to restore the transform ability. In order for tests to pass I had to address some of the issues with _as_axis_kwarg_mapping mentioned in https://github.com/xgcm/xgcm/pull/557
There are several use cases where we need to interpolate a chunked depth coordinate for the transform method.
FAILED xgcm/test/test_transform.py::test_grid_transform_multidim[conservative_depth_temp-threaded_client] - NotImplementedError: Cannot chunk along a core dimension for a grid ufunc which has a signature which includes one of the axis positions ['inner', 'outer']
FAILED xgcm/test/test_transform.py::test_grid_transform_multidim[conservative_depth_temp-processes_client] - NotImplementedError: Cannot chunk along a core dimension for a grid ufunc which has a signature which includes one of the axis positions ['inner', 'outer']
FAILED xgcm/test/test_transform.py::test_grid_transform_multidim[conservative_depth_temp-distributed_client] - NotImplementedError: Cannot chunk along a core dimension for a grid ufunc which has a signature which includes one of the axis positions ['inner', 'outer']

I think this is a real motivation to look into that issue again and see if we cannot find a solution for that.

@TomNicholas Can you allow the CI to run on this? I only ran the transform tests locally and it would be helpful to see if there is anything else that breaks.

Merging this into my Axis class deprecation PR https://github.com/xgcm/xgcm/pull/557, where we will deal with the failures for chunk inputs later


Use dev patcher to patch keystone chart, fixes 503  (SOC-10514)

In order to use a non-merged patch[0] to keystone to fix the probe
timeouts we need to move to local patching and passing the local
patched repo to ariship
This also bumps the keystone-api pod timeout for the probes to 30s
as by default this is 5s and it causes the ingress pod to remove
keystone-api from the pool as soon as it receives a timeout, which
happens when there is load in the servers (i.e. tempest tests)
As a side effect this also includes a minor change to our site/soc
config to keep using the same name as we used before for keystone
rabbit as the way of generating the name was changed here[1]
[0] https://review.opendev.org/#/c/683220/
[1] https://github.com/openstack/openstack-helm/commit/9bcf0df94c1a8455e17aa79f20efaf2736eed0f4

Failure was due to deckhand
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/falcon/api.py", line 244, in __call__
    responder(req, resp, **params)
  File "/usr/lib/python3.6/site-packages/shipyard_airflow/policy.py", line 339, in secure_handler
    return f(slf, req, resp, *args, **kwargs)
  File "/usr/lib/python3.6/site-packages/shipyard_airflow/control/api_lock.py", line 49, in func_wrapper
    return func(self, req, resp, *args, **kwargs)
  File "/usr/lib/python3.6/site-packages/shipyard_airflow/control/configdocs/configdocs_api.py", line 87, in on_post
    empty_collection=empty_coll)
  File "/usr/lib/python3.6/site-packages/shipyard_airflow/control/configdocs/configdocs_api.py", line 213, in post_collection
    document_data)
  File "/usr/lib/python3.6/site-packages/shipyard_airflow/control/helpers/configdocs_helper.py", line 624, in add_collection
    self.deckhand.put_bucket(collection_id, document_string)
  File "/usr/lib/python3.6/site-packages/shipyard_airflow/control/helpers/deckhand_client.py", line 124, in put_bucket
    response = self._put_request(url, document_data=documents)
  File "/usr/lib/python3.6/site-packages/shipyard_airflow/control/helpers/deckhand_client.py", line 345, in _put_request
    'Unable to Invoke deckhand: {}'.format(str(rex)),
shipyard_airflow.control.helpers.deckhand_client.DeckhandAccessError

2019-09-21 13:53:21,125 INFO     bb10fe0d-caa1-4da7-9d2c-d50db23430b8 bb10fe0d-caa1-4da7-9d2c-d50db23430b8 shipyard 2cfe082d56eb452eaee505d535e934f8 logging_mw(57) process_response - POST http://shipyard.ucp.svc.cluster.local/api/v1.0/configdocs/soc-design?buffermode=replace&verbosity=1 - 500 Internal Server Error
2019-09-21 13:53:21,126 DEBUG    bb10fe0d-caa1-4da7-9d2c-d50db23430b8 bb10fe0d-caa1-4da7-9d2c-d50db23430b8 shipyard 2cfe082d56eb452eaee505d535e934f8 logging_mw(63) process_response - Errored Response body: {"kind": "status", "apiVersion": "v1.0", "metadata": {}, "status": "Failure", "message": "Unhandled Exception raised: ", "reason": "", "details": {"errorType": "DeckhandAccessError", "errorCount": 1, "messageList": [{"message": "An error occurred, but was not specified", "error": true}]}, "code": "500 Internal Server Error", "retry": true}```

This also bumps the keystone-api pod timeout for the probes to 30s
as by default this is 5s and it causes the ingress pod to remove
keystone-api from the pool as soon as it receives a timeout, which
happens when there is load in the servers
So... isn't this an upstream issue?

So... isn't this an upstream issue?

Kind of and kind not. In the case of having more than one keystone-api pod (which is the default upstream, other than gating) and/or running this on baremetal instances where the performance is increased VS our engcloud nodes, this timeout is not reached or only one of the 2 pods is not responding momentarily, so the requests are still reaching keystone. In our case, because we default to just one pod, and our performance is not that good, and we also run the airship pods along, which are taxing the nodes, its much much easier for our keystone to take more than 5 seconds to respond, hence the ingress pod takes it out of the pool as soon as those 5 seconds have been reached.
So in that instance the issue is downstream, be it our lack of HA or our lacking performance.
In the case of the probe configuration, that IS an upstream issue, as one-size-fits-all does not work here, we may want to configure that to either be much more letinent or be more agressive with the timeouts. Hence that part was modified upstream to allow finer configuration for the probe options.
Lets discuss on the daily of this is not clear :)

So increasing our default number of pods for keystone would be alternative solution

So increasing our default number of pods for keystone would be alternative solution

Indeed! and that was done to test it under https://github.com/SUSE-Cloud/socok8s/pull/775 and it workerd. It still gave some 503 from time to time, probably due to resource starvation, but it was more stable.
I think that in the short future we may need that (so HA ci deployment to be closer to what we are gonna give customers) + still some timeout configuration to not be that agressive (maybe 15 seconds instead of 30?)

yay!


python3 and a little pep8

changes to run richtextpy in python 3

changes to run richtextpy in python 3


In the cli utxos command the option pretty-print-inline-datum is not optional

If you don't give the --pretty-print-inline-datum value there is an error
Failed to convert from type [java.lang.String] to type [boolean] for value [utxos]

Thanks @Proxiweb . Let me check

The error message has disappeared. That's strange because I haven't updated the devkit... All is well now


Added Powi

removed un-necessary code in fract and utils, added MANTISSA_BITS which is the number of bits reserved for the f32 mantissa (23), and added powi

Was working on another project which needed this functionality in an environment where it wasn't built in.  Saw rust had this functionality as well in std and decided to just implement it for micromath

Nice, looks good!

Any chance to get a release cut with this addition, @tarcieri? 🙏🏻

Released in 1.1.0

Thanks!


'reconstruct' is outputting empty json

Running reconstruct command and an empty pose_3d.json is output:
poseconnect reconstruct pose_2d_data.json camera_calibration_info.json pose_3d.json --pose-model-name COCO-17 --room-x-limits -2.0 7.0 --room-y-limits -2.0 14.0 --progress-bar
My camera calibration data looks like this (6 cameras):
[
  {
    "camera_id": "0",
    "camera_matrix": [
      [
        0.5,
        0.0,
        320.0
      ],
      [
        0.0,
        0.5,
        180.0
      ],
      [
        0.0,
        0.0,
        1.0
      ]
    ],
    "distortion_coefficients": [
      0.0,
      0.0,
      0.0,
      0.0
    ],
    "image_height": 360,
    "image_width": 640,
    "space_id": "0",
    "rotation_vector": [
      0.15173803,
      0.72253,
      -0.019780554
    ],
    "translation_vector": [
      -2.6292982,
      1.6538384,
      -3.0859113
    ]
  },
  ... etc

My pose data looks like this (134 frames of poses x 6 cameras):
[
 {
   "pose_2d_id": "1_0_0",
   "timestamp": "2023-11-04T12:00:00+00:00",
   "camera_id": "0",
   "keypoint_coordinates_2d": [
     [
       25.0,
       -92.0
     ],
     [
       26.0,
       -95.0
     ],
     [
       24.0,
       -95.0
     ],
     [
       23.0,
       -95.0
     ],
     [
       22.0,
       -95.0
     ],
     [
       28.0,
       -78.0
     ],
     [
       12.0,
       -74.0
     ],
     [
       46.0,
       -57.0
     ],
     [
       2.0,
       -51.0
     ],
     [
       55.0,
       -70.0
     ],
     [
       26.0,
       -57.0
     ],
     [
       39.0,
       -27.0
     ],
     [
       26.0,
       -17.0
     ],
     [
       74.0,
       -12.0
     ],
     [
       29.0,
       31.0
     ],
     [
       65.0,
       24.0
     ],
     [
       28.0,
       74.0
     ]
   ],
   "keypoint_quality_2d": [
     0.34907663,
     0.12023085,
     0.3977324,
     0.2603346,
     0.82151484,
     0.9538076,
     0.99108714,
     0.62545544,
     0.96275127,
     0.41110817,
     0.8926207,
     0.96958405,
     0.98871076,
     0.9417263,
     0.9852444,
     0.9072734,
     0.956458
   ],
   "pose_quality_2d": 0.8613986968994141
 },
 ... etc

Greetings! We are a tiny development team and this code base is primarily for our internal use (for now), but we do ultimately hope to make it useful for others and it's actually very helpful for other folks to pressure-test the algorithms.
There are many, many things that could cause the 3D pose output to be empty. Correctly or incorrectly, the algorithm is saying that the 2D poses don't line up, given the camera calibration info. If you're able to share a sample of your 2D pose data (e.g., a few timestamps) and your full camera calibration info, I'm happy to take a quick look.

Thank you for your reply, I can look into this, and also post more data.
Before I do, it would be worth noting that my orientations are defined in a Unity3D scene. If I'm not mistaken, this means that orientations are Left-Hand-Side (LHS). Is this the orientation that your algorithm is expecting? Also it would be really helpful to have units defined in your CLI. I understand that some units are measured in pixels, but I'm unclear if translations are in meters or centimeters and rotations are in radians or degrees. Same for the room limits.

The libraries follows the OpenCV conventions for intrinsic and extrinsic camera calibration parameters:

Image coordinates are in pixels
Rotation vectors are in radians
The units for world coordinates are arbitrary as far as the camera calibration is concerned (you just need to be consistent). However, if you use the default values in poseconnect for things like the maximum height of feet off the floor (which the algorithm uses to filter poses), those default values all assume world coordinates are in meters

That reminds me of something that should be documented better: the algorithm assumes that the world coordinate system is aligned with the floor and the default assumption is that the floor is at $z=0$.

I attempted a run again after increasing the focal length (which was in meters and I changed to cm). I made the images centered on the lower right corner, not the center (so the x and y values for the keypoints are all positive).
Finally, I made a Unity LHS to OpenCV RHS conversion by flipping the y axis for translation, and the x and y components of the rotation quaternions. I still have an empty 3d output. I have attached the input data if you want to see it.
camera_calibration_info.json
pose_2d_data.json


Update llvmlite dependency

Codecov Report

Merging #2320 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2320   +/-   ##
=======================================
  Coverage   86.65%   86.65%
=======================================
  Files         316      316
  Lines       58325    58325
  Branches     6022     6022
=======================================
  Hits        50539    50539
  Misses       6824     6824
  Partials      962      962

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 e618828...23b46bc. Read the comment docs.


One Question in example_rps.py

Could you please explain what 'response' means in this example? We are planning to apply this model to a QA mission. Is 'response' the correctness whether the model succeeds in identifying the item or whether the IRT model succeeds in telling the matching relationship last mentioned?
Also, it couldn't be better if there is some related documentations here.
Thanks a lot and look forward to your reply!

Response refers to whether model A answered item X correctly. So for QA if the answer is correct, response is 1. If it's incorrect, response is 0.
Documentation updates are coming. Stay tuned!


Page Loader Off-Center When Chat is Open

Is this on the latest master?
It looks like this when I test it.

this was fixed.
https://github.com/OpenBazaar/OpenBazaar-Client/pull/1058


katago: init at 1.3.5

Motivation for this change
Katago is the current strongest open source go AI engine.  This derivation provides both the OpenCL (default) and CUDA versions of the engine.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

The specific versions of cudnn and cudatoolkit is because they have to match, CUDA performance is actually quite bad reportedly for 9.2 and KataGo, so I selected 10.0, which is the version that the author mentioned he was originally running when he wrote this program.  This program also is tested as working on cuda 10.2, but it requires using a version of cudnn that has not been accepted into the nixpkgs repository yet.

@grahamcofborg build katago katagoWithCuda
@grahamcofborg eval "p: (p {}).katago.override { cudaSupport = true; useTcmalloc = true; }"
Please and thank you.

Updated default CUDA Toolkit from 10.0 to 10.1 because that's what the repository readme suggested.

@rasendubi @erikarvstedt @averelld Hi there, you were active on the original pull request for Leela Zero.  If it's not too much trouble, can one of you review this pull request?

Great that this is finally being packaged!
I've built an tested several cuda/opencl * tcmalloc combos successfully (builds and runs fine).
I think just defaulting to tcmalloc would be better if we even make it configurable.
Also, the buildbot probably won't evaluate anything with cuda because of it's unfree nature.
Other than the above, LGTM, the quicker we merge the better!

Ugh, I need to be more careful about screwing around with files locally when they still might change later.  This should work now.

Ugh, I need to be more careful about screwing around with files locally when they still might change later. This should work now.

New release, packaged that instead of the old release.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review-may-2019/3032/137

@GrahamcOfBorg build katago katagoWithCuda
Once again into the night we go.

You may have to restrict the platforms: it seems to require SSE, which rules out i686 and aarch64.

For confirmation, because this is the first time I'm attempting to do this, will specifying x86_64-linux be sufficient to address only platforms with SSE?  Or is there something more specific?

Or is there something more specific?

No, I don't think there is anything more specific.
If it's cross-platform try using platforms.x86_64, otherwise restrict it to linux only with "x86_64-linux".

@GrahamcOfBorg build katago katagoWithCuda

I just rebuilt with v1.3.4, with and without cuda still works great.

He released another minor version to fix a few newly discovered bugs.  Sorry about the second version jump in this init pull request.

It's a super short build, I like being up to date (and still works for me).

All right, let's merge this. Thank you @OmnipotentEntity!

Thanks for your help @averelld @rnhmjoj <3


performance isn't great

Hi, I tried to use this project to extract a billing csv file
I tried a 780mb file(compressed size), uncompressed size was 13gb.
when I tried to walk over the lines in the file using a buffer, I got rather bad throughput overall, so I tried to benchmark just the unzip process.
zcat {filename} > /dev/null finished in ~ 52 seconds
uncompressing and copying using std::io::copy(to /dev/null as well) took more than 40min, until I got annoyed with the CPU fan noise and shut it down.
is there any configuration/version you think will make a difference?

Have you compiled the program in release mode?
Off the top of my head, it could be that the CRC32 checksum causes the overhead.
Could you show me your code and a way to generate such a zip so that I could verify it?

I haven't built the binaries myself, downloaded it using cargo(version 0.2 as the readme file says).
About the code, I'm out of office right now, but it's 99% the same as the extract example https://github.com/mvdnes/zip-rs/blob/master/examples/extract.rs, especially when the script wasn't performing as expected, I've commented everything and just io::copy(ed) into an open /dev/null file.
I can't really share the original zip file since it has financial data of our clients, so I'll work on generating an example, but I don't think the file is anything special, just a high compression ratio text file, one thing I noticed is that the CRC in the zip file is missing, or invalid. But as it's only compared at the end of the decompression, as far as I know anyway, so it shouldn't have made a difference to decompression ratio.

About built type, unfortunately I'm new to rust, so I'm not sure if I built it in release mode, but the command was:
cargo run --bin {progname}

Can you try to run it with cargo run --release --bin {progname} ?

Here's the code:
fn file_reader() -> i32{
let args: Vec<_> = std::env::args().collect();
if args.len() < 3 {
println!("Usage: {} reader ({})", args[0], args.len());
return 1;
}
let fname = std::path::Path::new(&*args[2]);
let file = fs::File::open(&fname).unwrap();

let mut archive = zip::ZipArchive::new(file).unwrap();
let mut arch_file = archive.by_index(0).unwrap();

let ctx = zmq::Context::new();
let mut headers = ctx.socket(zmq::PUB).unwrap();
headers.connect("ipc:///tmp/headers").unwrap();
let mut lines = ctx.socket(zmq::PUSH).unwrap();
lines.bind("ipc:///tmp/lines").unwrap();

read_lines(&mut arch_file, &mut headers, &mut lines);

return 0;

}
fn read_lines(file: &mut zip::read::ZipFile, headers: &mut zmq::Socket, lines: &mut zmq::Socket){
let mut outfile = fs::File::create("/dev/null").unwrap();
io::copy(file, &mut outfile).unwrap();
}

--release made a huge difference, The file was decompressed in 81.6 seconds

Programs written in Rust can have a pretty big performance gain by enabling optimizations.
It seems to me that 81.6 seconds is good enough for a 13GB file.
I am closing this issue, but please feel free to reopen it if you are not satisfied.