Make the templates more discoverable

When I'm searching for a template my first obstacle is to find the templates repositories. I often forget that it is not located in the LiaScript org.
While searching, I always go to the github.io website and often I scroll over the link (below JavaScript Ready).
My first idea would be to add a specific link into the navigation bar at the top of the github.io page. This could be also done for the LiaBooks.

Just another fact about the website:
When clicking on one of the navigation links the page jumps to the specific part. But when I'm searching for the Docs and I click on the Docs I would expect the website to bring me directly to the docs. But I have to click another link which is called 'here'.
Maybe the navigation bar could be divided into page-jumping links (explaining what LiaScript is) and direct links to specific places (docs, templates, books, source, blog)?

This is a good point, originally I added webcomponent for previewing:
https://aizac.herokuapp.com/markdown-just-got-a-new-preview-tag/
The idea was to link other courses and preview their meta-information. So that it is not required to update the readme, but instead the overview is always up-to-date ... I am going to update during the weekend ;)
Another Idea was to use the GitHub-search API, so that only projects marked with a tag "LiaScript" are searched. This seems to work quite good and also the content of the README is used by the search. The problem there was the rate limit per user
https://docs.github.com/en/rest/reference/search#rate-limit
And hacked search using an iframe was not an option so far...
At the moment, I guess, the best option would be something like a curated list index, that can also be updated by other users.

The separation on the main-page is also a good point. We need to add more resources that can be used as a bootstrap.

This is a good point, originally I added webcomponent for previewing:
https://aizac.herokuapp.com/markdown-just-got-a-new-preview-tag/
The idea was to link other courses and preview their meta-information. So that it is not required to update the readme, but instead the overview is always up-to-date ... I am going to update during the weekend ;)
Another Idea was to use the GitHub-search API, so that only projects marked with a tag "LiaScript" are searched. This seems to work quite good and also the content of the README is used by the search. The problem there was the rate limit per user
https://docs.github.com/en/rest/reference/search#rate-limit
And hacked search using an iframe was not an option so far...
At the moment, I guess, the best option would be something like a curated list index, that can also be updated by other users.

The separation on the main-page is also a good point. We need to add more resources that can be used as a bootstrap.

Templates can be tagged on GitHub with liascript-template, which adds them to the following topic list:
https://github.com/topics/liascript-template


Proposed in: https://github.com/hash-gaming/slackproval/pull/11

added in #11


Call base ctor

Flexbox, VBox and HBox did not work anymore because the new __init__ including the deprecation warning did not call the base class' __init__.

Whoops, thanks!


feat(sidebar): adds vote option in sidebar for mobile site

Added vote option in sidebar for mobile site
Closes #3020

Thanks!

Why is this page just empty? Makes no sense to me.


fix: quick filter focus text doesn't match canvas text

looks like tnum wasn't being inherited.

Chrome still shifts by a couple pixels, and can fix that by changing the top padding in .iris-grid-input-field to 5px...

That massively mis-aligns it for me in chrome/win the opposite direction.

I am guessing we are running up against platform limitations. I adjusted so it's right in chrome/firefox on windows, but I don't think we can get it perfect against the matrix of OS and browsers. Does it look reasonable to you on linux or is it way off still?


Read handlers not responding / plugin slowing down Homebridge

Got the plugin setup using my login. On initial and following restarts of Homebrige the plugin manages to display the accessories in the Home app but they immediately begin displaying "not responding" error messages.
Logs state that "read handlers were slow to respond," then that "read handlers didn't respond at all"
Have tried restarting and reinstalling with no luck on a fix.
To Reproduce:

Install using the Homebridge UI (no 2FA or Unit specified)
Restart Homebridge UI
Log displays errors and cannot control devices

Logs:
[25/01/2022, 09:12:42] [homebridge-smartrent] Restarting Process...
[25/01/2022, 09:12:42] [homebridge-smartrent] Launched child bridge with PID 31743
[25/01/2022, 09:12:43] Registering platform 'homebridge-smartrent.SmartRent'
[25/01/2022, 09:12:43] [homebridge-smartrent] Loaded homebridge-smartrent v1.0.2 child bridge successfully
[25/01/2022, 09:12:43] Loaded 5 cached accessories from cachedAccessories.0E936C2E1CBD.
[25/01/2022, 09:12:43] [homebridge-smartrent] Loading accessory from cache: Kitchen Sink - Leak Sensor
[25/01/2022, 09:12:43] [homebridge-smartrent] Loading accessory from cache: Water Heater - Leak Sensor
[25/01/2022, 09:12:43] [homebridge-smartrent] Loading accessory from cache: Front Door - Lock
[25/01/2022, 09:12:43] [homebridge-smartrent] Loading accessory from cache: Kitchen island
[25/01/2022, 09:12:43] [homebridge-smartrent] Loading accessory from cache: Kitchen Track lights
[25/01/2022, 09:12:43] Homebridge v1.3.9 (HAP v0.9.8) (homebridge-smartrent) is running on port 51922.
[25/01/2022, 09:12:43] [homebridge-smartrent] Found 1 rooms
[25/01/2022, 09:12:43] [homebridge-smartrent] Found 6 devices
[25/01/2022, 09:12:43] [homebridge-smartrent] Restoring existing accessory from cache: Kitchen Sink - Leak Sensor
[25/01/2022, 09:12:43] [homebridge-smartrent] Restoring existing accessory from cache: Water Heater - Leak Sensor
[25/01/2022, 09:12:43] [homebridge-smartrent] Restoring existing accessory from cache: Front Door - Lock
[25/01/2022, 09:12:43] [homebridge-smartrent] Restoring existing accessory from cache: Kitchen island
[25/01/2022, 09:12:43] [homebridge-smartrent] Unknown device type: thermostat
[25/01/2022, 09:12:43] [homebridge-smartrent] Restoring existing accessory from cache: Kitchen Track lights
[25/01/2022, 09:12:47] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Leak Detected' was slow to respond! See https://git.io/JtMGR for more info.
[25/01/2022, 09:12:47] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Leak Detected' was slow to respond! See https://git.io/JtMGR for more info.
[25/01/2022, 09:12:47] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Lock Current State' was slow to respond! See https://git.io/JtMGR for more info.
[25/01/2022, 09:12:47] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Lock Target State' was slow to respond! See https://git.io/JtMGR for more info.
[25/01/2022, 09:12:47] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://git.io/JtMGR for more info.
[25/01/2022, 09:12:47] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://git.io/JtMGR for more info.
[25/01/2022, 09:12:53] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Leak Detected' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[25/01/2022, 09:12:53] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Leak Detected' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[25/01/2022, 09:12:53] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Lock Current State' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[25/01/2022, 09:12:53] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Lock Target State' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[25/01/2022, 09:12:53] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[25/01/2022, 09:12:53] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[25/01/2022, 09:13:26] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Leak Detected' was slow to respond! See https://git.io/JtMGR for more info.
[25/01/2022, 09:13:26] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Leak Detected' was slow to respond! See https://git.io/JtMGR for more info.
[25/01/2022, 09:13:26] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Lock Current State' was slow to respond! See https://git.io/JtMGR for more info.
[25/01/2022, 09:13:26] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Lock Target State' was slow to respond! See https://git.io/JtMGR for more info.
[25/01/2022, 09:13:26] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://git.io/JtMGR for more info.
[25/01/2022, 09:13:26] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://git.io/JtMGR for more info.
[25/01/2022, 09:13:32] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Leak Detected' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[25/01/2022, 09:13:32] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Leak Detected' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[25/01/2022, 09:13:32] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Lock Current State' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[25/01/2022, 09:13:32] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'Lock Target State' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[25/01/2022, 09:13:32] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[25/01/2022, 09:13:32] [homebridge-smartrent] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
Plugin Config:
"email"<EMAIL_ADDRESS>"password": "xxxxxxxxxxx",
"platform": "SmartRent",
"_bridge": {
"username": "xx:xx:xx:xx:xx:xx",
"port": 51922
Environment:

Plugin Version: v.1.0.2
Homebridge Version: 1.4.0
Node.js Version: 16.13.2
NPM Version: 8.1.2
Operating System: Raspbian

Seeing same issue

Same issue here... running Homebridge on a Raspberry Pi. HomeBridge 1.4.0 with the 1.0.2 version of the plugin.


ci: Pin onnx version to 1.12

Need fixing #249 for supporting onnx 1.13

CI still emitting similar error though?
>           C.check_model(protobuf_string, full_check)
E           onnx.onnx_cpp2py_export.checker.ValidationError: Field 'type' of 'value_info' is required but missing.

CI still emitting similar error though?

Just pinned github ci and fixed mypy errors


Should we place libv8_base.a in git repo directly?

I don't think it's very good idea to store big binary file like that in git. Could we store it in ftp and download, or build from source? Is that difficult in current build system?

The v8 binaries are not so big. The v8 source code is much bigger in total.  Also the V8 version has its own repo https://github.com/NativeScript/android-v8
Can you describe what is the issue first, so we can thing of ways how to resolve it.

Source code compressed by git is not so big either. I shallow cloned v8 repo, and the size of .git was 21.4MB.
Since binaries are not so diffable as text files and not all source files are updated in each version, you will easily exceed the size of git repo in source code form.
So binaries are not so efficient in size.
Also binary files are not always convenient, since I will get merge conflict easily If I update v8 binary by myself.
I think that's one of the reason why nodejs stores v8 in source code rather than in binary.

V8 repository you refered to in your comment is outdated. (9 months?) Where can I find its build configuration?

Hi,
We update the V8 binaries only when we update the version of V8 in {N}. These files are not changed regularly. What do you mean by exceeding the git repo size.
There is GitHub LFS https://help.github.com/articles/versioning-large-files/. but that is designed for files over 100MB. We don't have this scenario. We have 47MB V8 libs that compressed total at 11MB.
Also not sure about the merge conflicts you can get when replacing the V8 library on your side. With binary files it very easy - you either choose the {N} version or yours.
We choose to include the V8 libraries in the project so runtime builds are faster and you don't need to build V8 everytime you need to build the runtime. Much simpler for getting started and working on {N} runtime codebase. Keep in mind that we have a V8 fork that we customize a little so it is working in {N} context.
Also we have the V8 repository public so you can craft your own version of V8 if needed.
cheers,
blagoev

For latest version of V8 check the branches @ https://github.com/NativeScript/android-v8

What do you mean by exceeding the git repo size.
I just wanted to say that git compress source files much better than binary files.
Using much disk space for storing history of binaries is not much a problem today, though using much more bandwidth for sending binary diffs can be a problem.
I don't care about size of source trees you get with "git checkout".

I overlooked that branch of android-v8. Why is it not set to default branch or just make latest one master?
Another problem I come up with binaries is, you need to build binaries for all cpus to make git history consistent, which will take more time than testing for one architectures. Or I have to delete precompiled binaries from git?
This problem might be bigger than other ones.
node-gyp support compiling addon with both precomiled one and node compiled by yourself.
It fetches headers and precompiled libs from https://nodejs.org/dist/ if you want. I think that this method is better.

Does this repo refer to android-v8 with commit hash?
I couldn't found hash in log message.
If you don't want to move precompiled binaries to another place, being able to choose another dir for v8 libs will solve the problem of binary update or merge conflicts.
Can I do that easily?

in the {N} runtime we use binaries because it's more convenient, than building our tweaked v8 every time, and we already discussed that the size of those binary wouldn't pose a problem
if you wish to build your own version of v8 and use it, you can do it by going to the repo and follow the build instructions for whichever version you chose.
in case you want to change the v8 binary with yours, you can simply remove our version of the distribution and use yours. there will be no merge conflicts in any case.


fix(solve_by_elim): improve backtracking when apply creates multiple goals

This depends on the as-yet-unmerged https://github.com/leanprover/mathlib/pull/382.

The purpose of this change is to make
example {α : Type} (r : α → α → Prop) (f : α → α → α)
  (l : ∀ a b c : α, r a b → r a (f b c) → r a c)
  (a b c : α) (h₁ : r a b) (h₂ : r a (f b c)) : r a c :=
begin
  solve_by_elim,
end

work as expected.
Previously, solve_by_elim was applying l, then guessing to apply h₂ (while h₁ is the correct path), but after that failing to backtrack. The simple fix is to not use ;, but rather >>, at https://github.com/leanprover/mathlib/pull/393/commits/f45363abb10f95d65f09f7be4bf9a6531ee4bcc0#diff-f971bb8d933f299b31d4f4e9dd951958R426.

Is this meant to be related to the "tidy bug" thread on Zulip?

No, I doubt it is related.
On Sat, Oct 6, 2018 at 9:13 PM Patrick Massot<EMAIL_ADDRESS>wrote:

Is this meant to be related to the "tidy bug" thread on Zulip?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/leanprover/mathlib/pull/393#issuecomment-427565707,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdLBMs7Alc0Jti9bSWchi7kfqvtyh_Aks5uiJBZgaJpZM4XLLds
.

Or rather, I have no idea if it is related, I haven't thought about that
bug yet.
On Sat, Oct 6, 2018 at 11:57 PM Scott Morrison<EMAIL_ADDRESS>wrote:

No, I doubt it is related.
On Sat, Oct 6, 2018 at 9:13 PM Patrick Massot<EMAIL_ADDRESS>wrote:

Is this meant to be related to the "tidy bug" thread on Zulip?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/leanprover/mathlib/pull/393#issuecomment-427565707,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdLBMs7Alc0Jti9bSWchi7kfqvtyh_Aks5uiJBZgaJpZM4XLLds
.

That's a really simple fix. I wonder why I wasn't using ; before.


None for witness_lookup bad for PSBT.create()

Passing in None to the witness_lookup in psbt_helper::create_multisig_psbt
does the wrong thing if you end up passing in a P2WSH address as an output.
It seems that an empty dictionary behaves correctly as an empty
witness_lookup object.

Good catch, thanks @howech!
Let me submit a PR to add test coverage so I can merge this in (and make a new release for pypi).

On second thought, this PR looks good as-is.
However, I'm confused why both this PR branch and the old main branch pass test-coverage as-is. There are many instances in test_psbt_helper.py of create_multisig_psbt() being called without an issue both before your PR (current main branch) and after it.
@howech was there a bug/issue that made you catch this? I agree with the change but am confused how it wasn't previously a problem (and that this change didn't break test coverage). witness_lookup only matters in this code path here, so I'm thinking it has something to do with how the pubkey_lookup or tx_lookup is constructed here (or more precisely, what information is fed into the construction logic).
Separately, for some reason github didn't fire off any CI tests on your PR. I'm not sure why that is. But, I manually ran the tests on your PR branch and they do indeed pass. And I just tested that Github CI is indeed working, so I'm going to keep my eyes on that but I think it's unrelated to your PR and sometime github CI just doesn't run.

Hi @mflaxman - yes, this was in response to a bug we found.
Trying to build a psbt with an output to this address:
tb1q9hj5j7mh9f7t6cwdvz34nj6pyzva5ftj2ecarcdqph5wc3n49hyqchh3cg  (from here)
fails with AttributeError("'NoneType' object has no attribute 'get'",)

hi @mflaxman -- don't have access to everything with me right now as I'm out of town, but I believe this was all that was needed to make the error happen (could be wrong, if this isn't enough, can figure out more tomorrow)
xpubs = [('b8ce6f0f', 'tpubDEaV1ww4hcTUiRfuGqt5s2UgxQ5Nc4XejS7gL9iAMNWr5dgRoz9CjvohtqQArpRwfEkFCKra5E3AAWoAbGdnEpWKVM43skmauoA1y3ikteQ', "m/45'/1'/1'/6"), ('c22fe2ac', 'tpubDF17mBZYUi36PMxKJDNCbDAQHkvn4B44ACTFGRCFcTXjJth5c9KehzXwNM2iU7DKbmjdtu2e2fGeg9PQccCmYrr1Hn1R2cg6KJXUFfC258w', "m/45'/1'/0'/16"), ('deadd916', 'tpubDF7U4FTHkZgjopMgwobKuSxLQQSrTcxmzgG4pYztMEJBZHubuJfQXKe5dK3VPWtCzaNW4wFWjir77srSvHBENWsj9696AFRcVLyEPw6yqU4', "m/45'/1'/2'/6")]

inputs = [{'prev_tx_dict': {'hex': '02000000000107e1c76d4b7e9415fd82597a9906857a5c28c3c76adf479e7432287593ecc0fe99000000001716001433b7afc8bad5f5349e2e6d419cc8b5b4734805effeffffff2f9e91eebe40e05791e486e492bc980477478c31b0b088adc75127b0cf8d603f0000000017160014cefea4d47717441eada491d5ddf81f1205246e33feffffff0013630847984d436c60199d88093d6b335217e989cb6d8c091dab01c15eacad00000000171600147d83ab70b4b3b51dbefa459c3ce4cfb9663d2989feffffffa17c7d257bee51c3b113693d1de673b39346916db18f035eb2a1379a7504866a000000001716001412357d9a9789fd316b58f1f6ff8fa5f76b25f15bfeffffff0f792f582c72bbe8c0fb3743a67316e969579ccccabbe57fff6b78e2ba26784b0000000017160014a40186c4e562c89ce5449c55d6557d70d2b5a6e2feffffffd6f4b17c8dbf7628d02cf55fdbb016ce0eb7fb3df40e193e9788b76f6a9d1ca600000000171600147363016ddbfde7f7e00814fc5d0508b86a89fcaefeffffffaa2b74590fe84c761ae44e633c91f94193b9daeff465d8f9109de5a9697642d00000000017160014512195bc9e2a7caecdebee967b217076f8300a2afeffffff0100c2eb0b0000000017a914c6162b3fcb88b82981ab6d7867f064981adaf90f870247304402200a3c17eb15cceed617d8f8ce15046dae2e147f14f6366ef21e2a171437073d2602203e559118aea948e067b71542e49be8020a6e8dffa5a40e84f1c9725d23abc2c9012103ca25f9df60856fbe21b02b5dfb24ddb857541ae36eb2dc8a22e960f6a563cdf00247304402205d6b742f60144b8119da59d6884e7d576bbbd7af3d31ae1585ced98aee02f95802203d9998f80e9b08a4cbb8cc2b70676fb2a85ccf39991504e274ec37e607c4e68a012102bb1e0e3c64bfade3b38ac4e840b996b868e358f96c0d39fbfc51b0ceba92f24d024730440220243a648ac452273da2538db29aa42e67ea759e541c39188fc6909db9ef9a3e9202205dc0260e9e6e9037c264b26e4246c0fefa35c9a23b2e3837f4ddd9b1f81d7a010121020e183d80df21a7912b96eedc1eca76dbb6fe8892de2d58381eaf0234de203c060247304402202889b0987639f24d7578625f5f6f0285bae96878d682e7cc6083afef83425b8902206beb7fffa15258bc1e31c97419adae659216ec0d99547aa603db05cd43f238ec012103f6ccb3f8b6c456bc30ae36d305e6dbcde778c94d30f4119ee7494c983511742a024730440220360e9898995ee75d907d99bf566041dc38251e5fc55f7febfce09f7a4dfbd9a002205c0ac1eaecc0e608f961954f1c2faa1799582cfcf01bfe0618bee4cb637ebccd01210314ccf2cfe7dcdf96eaa82c8f5e670f569b51e55e3496219f04164d95ca9c9ad10247304402204184e777af586b5d8648f38cce84b61b371232a39ada7c00a2ef07e68b9552620220544531b2dcb2237d7625817c4110d1d7811a979c0351cf16f72a082b6b0332ce01210345e4af5fde3cd5584a82b56972863e17f5715bb1cb66f9eb24e1510627d7c9510247304402205c58225a7a6a150f8755a6822025bed742c309ce5abaac3272985edcd232837302200fbb05c563d27e8b51f2eea446e5790d145e97f4058616fbb486b03fccec92d8012103ee26e1d57eb2876f429a8292a642f8dc22e0bec632134e8b5d1070b72974a8829c080000', 'hash_hex': '0a3dfa609e0120b2b25d853f4d0fbd64613a35a552b1d39759fd33aafd769223', 'output_idx': 0, 'output_sats': 200000000}, 'quorum_m': 2, 'path_list': [('b8ce6f0f', "m/45'/1'/1'/6/0/0"), ('c22fe2ac', "m/45'/1'/0'/16/0/0"), ('deadd916', "m/45'/1'/2'/6/0/0")]}, {'prev_tx_dict': {'hex': '02000000000105ad51f0e6b8fa00dea857818846449986046c9bb45d615ff45ad29ec80e532cb500000000171600142cdd14024b9490a5a9161c296bff402172d8d7e7feffffff5358dcfb86662636452af9fb85eea457a4b9ff561f13e758b23607142fcd10ea0000000017160014ffbe73f96869c2f970354d7ffe448f53ac435f1efeffffff45145f5dadac3d891b5508947bd75635e5f328427629f19db8dd14e87329f4b800000000171600147a26b913ddf4de28b309119fd5889ced4e14d267feffffff433a783525338c7a613d0d729c420fabfaf76bd50505aef1fbce6660bbabff8500000000171600140f498a82544c3e185f3290f6b503535a0314831dfeffffff0b73b4e48bf2e0a959eab1999386d085a67ae826fc9ca4f95a442997c3e652c900000000171600144c2843e40f72a6943ba129b0875eabffdd00354efeffffff02f21a10000000000017a9145d06690836805bc562141e84106a055f8c1bbf338780f0fa020000000017a914c6162b3fcb88b82981ab6d7867f064981adaf90f87024730440220186eb4ec2744ad20be0ffff18edcc90aa32820fb1cffd0aa64609ef173ebf41a02200ad99996a1a404eec24aced4310a924b0e5219f45777f19f1b6317463e18475c01210279dd68e6864716a858d4969e64210d7b216c7623a4f2c11415066caa028f08be0247304402200c32ff94c50329a8b49b2010a3edfdefa6ca2f7486d9be004805ba124f44ab2a022067da71b118b5e2510552e523ca5f80c6bce4a5bb8b14322306b72bc7cc4591b501210205dd3585ca48f6b97ee13a238a484b921180593317506f58d28d21a9b3ed89160247304402201c7f8352667309d67383b568542206519fd30143d5633880f5d11d81adf7a9b7022021f6bf731d8c4f1613af4d0efc02f9a2152cc8444d76760c8afd4ce55bcc120d0121038cc9458ebf264a31803492c86ce0b1aaf729ad53a710e8a14341f6d358c11a720247304402207b7b444a8267d2972d2cb20fee632cd3b439a1e0bd363af84f16e395d816e2e2022036b56b473199971145fd93ba25c89a96036f4756b4d895456341c90e6ef6b5ef0121029801635f5b14994be58e0bb37eaec9c8ffadacdf513189a806e9e1a207af1ace02473044022031bd0fa64f04225c9764ebac3bdefcaa23f5df918e74598b7b180adc2a233262022051f0af2c760d17f144d60708dfb7bef716489ecb129366c6baadfc67e61e11980121035d03fc0b2ef8ad2f6821f7f561a7936c6772fdd53f1ea58d54e5a8673d4da5019b080000', 'hash_hex': '998eaf2f1d0e95261128c23652d311d9cba27dc505a73d058c7177e258c92a2a', 'output_idx': 1, 'output_sats': 50000000}, 'quorum_m': 2, 'path_list': [('b8ce6f0f', "m/45'/1'/1'/6/0/0"), ('c22fe2ac', "m/45'/1'/0'/16/0/0"), ('deadd916', "m/45'/1'/2'/6/0/0")]}]

outputs = [{'sats': 10000000, 'address': 'tb1q9hj5j7mh9f7t6cwdvz34nj6pyzva5ftj2ecarcdqph5wc3n49hyqchh3cg'}, {'sats': 239997984, 'address': '2MuCSCsAa8QD7AQ2VcMPoumsCrFkTgK8feh', 'quorum_m': 2, 'path_dict': {'b8ce6f0f': "m/45'/1'/1'/6/0/1", 'deadd916': "m/45'/1'/2'/6/0/1", 'c22fe2ac': "m/45'/1'/0'/16/0/1"}}]

fee_satoshis = 2016

Thanks @humanumbrella! Confirmed that is a bug on the main branch and that this PR fixes it.
Digging into it now.

I just tried generating a PSBT using tb1q9hj5j7mh9f7t6cwdvz34nj6pyzva5ftj2ecarcdqph5wc3n49hyqchh3cg and it works fine:

Doh, I just realized I was on this PR branch when I ran my code above. My code snippet above (as well as yours) does indeed throw an error on the main branch.
Good news is that makes this an easy fix! Thanks @humanumbrella and @howech for catching/fixing this. Submitting a PR to this PR to add test coverage now, then we can merge and I'll cut a new release for pypi.

I added test coverage and bumped the version number, but I couldn't find a way in GitHub's workflow to submit a PR to this PR (I think GitHub doesn't allow that because this PR is coming from @howech's branch and not a buidl-python branch).
So, I included @howech's commit along with one from me to add test coverage, and merged it in here:
https://github.com/buidl-bitcoin/buidl-python/pull/131
Thank you @humanumbrella and @howech! I cut a new release on pypi: https://pypi.org/project/buidl/0.2.36/


How to filter orders by delivery method?

I'm trying to filter orders with GraphQL Admin API by query="delivery_method:XXXX" but I can't figure out which field value stands for delivery_method. I've tried almost all fields from Order -> ShippingLine such as carrierIdentifier, title, code, id but it seems like they are not working.
Have some has any idea how it can be done?
If I'm asking in a wrong place, please redirect me. I'm searching for an answer for quite a while now. Will be glad to see any help.

Hi @vavan19! Usually, you should send this kind of question to the Community forums where you'll get faster and more complete answers, GitHub issues are usually used for bug reports.
As per the Shopify GraphQL reference, you'll find delivery methods under fulfillment orders (which themselves are under orders). Perhaps the values you're looking for are in DeliveryMethodType?
Hope this helps!


Make more of the hoomd parameters accessible in the MSIBI API

We should make more of the hoomd simulation parameters accessible within the MSIBI API, so that can be changed as needed.
Some of the things that are currently hard coded:
Integrator choice and mode
dt,
gsd write out period
seed

I think the MSIBI class makes the most sense to hold these attributes. It seems like either of the __init__ or optimize functions could work. Or, we can add a method for setting the simulation related parameters.
Something like:
opt = MSIBI(...)
opt.set_hoomd_args(
    n_steps = 1r6, dt=0.001, gsd_period=1000, integrator=`hoomd.nd.nvt`, tau = 0.1
)

Since the different integrators contain different parameters it can be a little tricky, maybe the integrator's specifc args can be passed in as a dict?
Some examples:
opt.set_hoomd.args(
    integrator = "hoomd.md.integrate.nvt",
    integrator_kwargs = {"tau": 0.1}

opt.set_hoomd.args(
    integrator = "hoomd.md.integrate.langevin",
    integrator_kwargs = {"seed": 1,}

opt.set_hoomd.args(
    integrator = "hoomd.md.integrate.npt",
    integrator_kwargs = {"tau": 0.1, "tau_p": 0.05}


Can't build

After running…
$ pip install pyassimp
$ ./build.sh

I get the following…
Traceback (most recent call last):
  File "./meshconvert.py", line 4, in <module>
    from pyassimp import *
ImportError: No module named pyassimp
./build.sh: line 15: ./bufferize: No such file or directory
./build.sh: line 16: ./bufferize: No such file or directory
error: unknown argument: '-fdiagnostics-show-option'
llvm-link: No such file or directory
opt: wasm.bc: error: Could not open input file: No such file or directory
llc: error: llc: wasm.bc: error: Could not open input file: No such file or directory
wasm-ld: error: cannot open wasm.o: No such file or directory
./build.sh: line 26: zopfli: command not found
./build.sh: line 27: zopfli: command not found
./build.sh: line 28: zopfli: command not found
./build.sh: line 29: zopfli: command not found
rm: src/*.bc: No such file or directory
rm: wasm.bc: No such file or directory
rm: wasm.o: No such file or directory

System Specs:
OS: macOS Big Sur 11.6.1
Architecture: M1
LLVM: 14.0.6_1

Presumably your pip pyassimp installation is for python 3, but this project is pretty old and runs python 2. If you don't want to bother with all that you can perhaps simply use the pre-built model buffer at https://aransentin.github.io/cwasm/demo/model.buf

Thank you, will try!


Auto-generate migrations for models

A new feature that I think might be useful for sails migrations:
The ability to auto-generate a migration based on a model file. It wouldn't consistently auto-generate migrations for changes, as this seems like it would be difficult and require managing state. The thought is more of a one-time per model time saver. You define your model then call:
sails-migrations generate:model [name of model]
It then parses the model file and creates a migration file based on that model. It doesn't have to parse everything in attributes, if there is some non-standard or in-depth attribute we can just rely on the user updating the migration file to handle that attribute. In my mind the low hanging fruit are:

Table Names
Column Names
Types
Required (though waterline ignores this in auto-migrations, so maybe we should too)
Unique
Simple relations (make them integers)
More complex relations (Too difficult without having context on both models?)

I'm happy to take a hack at it, but it will just be weekend time which itself is a bit limited right now for me.

Hmm, sounds really cool,
And not that hard, no actual parsing is probably needed since we actually load sails, so you can access all the models easily.
I've no idea when i'll have some free time to work at it.. a lot on my plate right now.

Still open for PRs though :D


When Building via npm run build:prod, module.bundle.js is not minified

I'm not sure whether it's intentional but I would expect also module.bundle.js to be minified.

Hi @vanthome thanks for reporting this.
This needs to be investigated.

Hi @vanthome now this should be solved.


V2 'Simple Device' Tutorial Issue

New to ophyd, and immediatlely hit a problem... The tutorial to Make a Simple Device appears to be broken.
Minimal example taken from the source:
"""Demo EPICS Devices for the tutorial"""

from enum import Enum

from ophyd.v2.core import StandardReadable
from ophyd.v2.epics import epics_signal_r, epics_signal_rw

class EnergyMode(Enum):
    """Energy mode for `Sensor`"""

    #: Low energy mode
    low = "Low Energy"
    #: High energy mode
    high = "High Energy"

class Sensor(StandardReadable):
    """A demo sensor that produces a scalar value based on X and Y Movers"""

    def __init__(self, prefix: str, name="") -> None:
        # Define some signals
        self.value = epics_signal_r(float, prefix + "Value")
        self.mode = epics_signal_rw(EnergyMode, prefix + "Mode")
        # Set name and signals for read() and read_configuration()
        self.set_readable_signals(
            read=[self.value],
            config=[self.mode],
        )
        super().__init__(name=name)

s = Sensor('test')

yields:
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Cell In[2], line 31
     25         self.set_readable_signals(
     26             read=[self.value],
     27             config=[self.mode],
     28         )
     29         super().__init__(name=name)
---> 31 s = Sensor('test')

Cell In[2], line 22, in Sensor.__init__(self, prefix, name)
     20 def __init__(self, prefix: str, name="") -> None:
     21     # Define some signals
---> 22     self.value = epics_signal_r(float, prefix + "Value")
     23     self.mode = epics_signal_rw(EnergyMode, prefix + "Mode")
     24     # Set name and signals for read() and read_configuration()

File [~/.python/py3/lib/python3.11/site-packages/ophyd/v2/epics.py:87](https://file+.vscode-resource.vscode-cdn.net/home/oscar/CamDrive/bluesky/~/.python/py3/lib/python3.11/site-packages/ophyd/v2/epics.py:87), in epics_signal_r(datatype, read_pv)
     77 def epics_signal_r(datatype: Type[T], read_pv: str) -> SignalR[T]:
     78     """Create a `SignalR` backed by 1 EPICS PV
     79
     80     Parameters
   (...)
     85         The PV to read and monitor
     86     """
---> 87     backend = _make_backend(datatype, read_pv, read_pv)
     88     return SignalR(backend)

File [~/.python/py3/lib/python3.11/site-packages/ophyd/v2/epics.py:56](https://file+.vscode-resource.vscode-cdn.net/home/oscar/CamDrive/bluesky/~/.python/py3/lib/python3.11/site-packages/ophyd/v2/epics.py:56), in _make_backend(datatype, read_pv, write_pv)
     54 w_transport, w_pv = _transport_pv(write_pv)
     55 transport = get_unique({read_pv: r_transport, write_pv: w_transport}, "transports")
---> 56 return transport.value(datatype, r_pv, w_pv)

AttributeError: 'function' object has no attribute 'value'

Running ophyd '1.8.0'.

The problem is that ophyd v2 supports both CA and PVA, so the base install doesn't install either. You need to pip install ophyd[ca] to get the CA libraries. Unfortunately this isn't added in the tutorials, I have done so in https://github.com/bluesky/ophyd/pull/1133. The error message is bad because of https://github.com/bluesky/ophyd/issues/1113 which was fixed a few days ago but hasn't been released yet. To test this theory, please can you do the following:

Post the output of pip freeze
Do a pip install git+https://github.com/bluesky/ophyd.git and run the tutorial code again, and check you get a better error message saying something like "CA support not available"
Do a pip install ophyd[ca] and the tutorial should work

Thanks! It would be useful to include some mention of this in the bluesky installation docs.


Error when try to save file.

I do like this, but have error. " -[PHAsset defaultRepresentation]: unrecognized selector sent to instance 0x1783a3f00"
- (void)assetsPickerController:(CTAssetsPickerController *)picker didFinishPickingAssets:(NSArray *)assets
{
    NSString *FolderPath = [MySingleton sharedMySingleton].FolderPath;
    NSString *FileName;
    for(ALAsset *assetObject in assets)
    {
        ALAssetRepresentation *rep = [assetObject defaultRepresentation]; // ERROR ON THIS LINE
        Byte *buffer = (Byte*)malloc(rep.size);
        NSUInteger buffered = [rep getBytes:buffer fromOffset:0.0 length:rep.size error:nil];
        NSData *data = [NSData dataWithBytesNoCopy:buffer length:buffered freeWhenDone:YES];
        FileName = [w FileNumber:[FolderPath stringByAppendingPathComponent:[[assetObject defaultRepresentation]filename]] FileDestination:FolderPath];
        [data writeToFile:[FolderPath stringByAppendingPathComponent:FileName] atomically:YES];
    }
}

Version 3.0 now uses the Photos framework which means the assets that you get are no longer ALAssets.
You now get PHAssets and have to use the PHImageManager to get the data you need.
See https://developer.apple.com/library/prerelease/ios/documentation/Photos/Reference/PHImageManager_Class/index.html.

Oh thanks, now everything worked!!!
- (void)assetsPickerController:(CTAssetsPickerController *)picker didFinishPickingAssets:(NSArray *)assets
{
    NSString *FolderPath = [MySingleton sharedMySingleton].FolderPath;
    __block NSString *FileName;
    for(PHAsset *assetObject in assets)
    {
        PHImageRequestOptions * imageRequestOptions = [[PHImageRequestOptions alloc] init];
        imageRequestOptions.synchronous = YES;
        [[PHImageManager defaultManager] requestImageDataForAsset:assetObject options:imageRequestOptions resultHandler:^(NSData *imageData, NSString *dataUTI, UIImageOrientation orientation, NSDictionary *info)
        {

            FileName = [w FileNumber:[FolderPath stringByAppendingPathComponent:[[info objectForKey:@"PHImageFileURLKey"]lastPathComponent]] FileDestination:FolderPath];
            [imageData writeToFile:[FolderPath stringByAppendingPathComponent:FileName] atomically:YES];
        }];
    }
}

@Remyoman Thanks for your help.


Release/1.11.1

Coverage decreased (-0.05%) to 93.601% when pulling 005f5ab273b44f4505a62dbb638c53eae595904f on release/1.11.1 into 69d68904b4ae0c8ba3c0d60991c3a6a38066040d on master.


Changed the bluetooth filter to allow more linak models to be discovered

Got a new desk  with a Linak dpg1c controller, I saw your all and it wasn't able to identify my desk, the name of the des has DESK written all in caps.
After changing the bluetooth filter, the desk works flawlessly with the app.
Don't know if you want to have this just for the idasen, if so, feel free to close and disregard this PR.

@pgloria What desk did you buy?   FWIW, @DWilliames  I have heard it is possible to swap out controller on an Idasen for a  Linak dpg1c as well.  Would be nice if we had something more precise than a device name here (to identify compatible controllers), but overall I think it is a net positive if the app is flawlessly compatible with a non-Idasen desk 🤷♂

@pgloria do you have a build of the app so I can test? thanks


Layer breaker: browser/dnd

Try to compile only sources from editor,  platform/{common,browser}, and base/{common,browser} and notice a compile error in dnd.ts. That is because it is coded against electron specific apis

To repo put this in our tsconfig-file and compile from the command line using tsc
{
	"$schema": "http://json.schemastore.org/tsconfig",
	"compilerOptions": {
		"module": "amd",
		"moduleResolution": "classic",
		"noImplicitAny": false,
		"removeComments": false,
		"preserveConstEnums": true,
		"target": "es5",
		"sourceMap": false,
		"experimentalDecorators": true,
		"declaration": true,
		"noImplicitReturns": true,
		"baseUrl": ".",
		"types": []
	},
	"include": [
		"typings/thenable.d.ts",
		"typings/lib.ie11_safe_es6.d.ts",
		"typings/es6-promise.d.ts",
		"typings/require.d.ts",
		"vs/css.d.ts",
		"vs/monaco.d.ts",
		"vs/nls.d.ts",
		"vs/editor/*",
		"vs/base/common/*",
		"vs/base/browser/*",
		"vs/base/parts/tree/*",
		"vs/base/parts/quickopen/*",
		"vs/platform/*/common/*",
		"vs/platform/*/browser/*"
	],
	"exclude": [
		"node_modules/*"
	]
}


Make it installable via pip (PEP-517)

I noticed that you mentioned in the README that this is only installable via poetry so far.
Thanks to PEP-517, it is very easy to make python projects installable via pip also, which is super nice for someone who quickly wants to test this.
I added the PEP-517 compatibility as described in the poetry docs here. I also updated the README to explain how to install this via pip.

If you want to confirm that the pip installation is working before merging, you can try it out with pip install git+https://github.com/The-Ludwig/yml2block.git.


update golangci-lint to latest stable version

Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>Describe what this PR does
update golangci-lint to the latest stable version

@humblec PTAL


Account info not found

Information

qiskit-ibm-provider version: master
Python version: 3.10.6
Operating system: OSX

What is the current behavior?
I have a IQX token installed, but the qiskit-ibm-provider cannot find it:
provider = IBMProvider()

gives AccountNotFoundError: 'No default ibm_quantum account saved.'
But the Runtime and regular IBMQ provider have no problem finding my credentials
Steps to reproduce the problem
What is the expected behavior?
Suggested solutions

IBMProvider.saved_accounts() finds my info
{'default-ibm-quantum': {'channel': 'ibm_quantum',
  'token': 'XXXX',
  'url': 'https://auth.quantum-computing.ibm.com/api',
  'verify': True}}

I believe it's defaulting to look for an ibm-cloud account - this should be fixed by https://github.com/Qiskit/qiskit-ibm-provider/pull/399

@nonhermitian are you still having this issue?

fixed by #399

I still see this error on the latest version of the provider and Qiskit:
from qiskit_ibm_provider import IBMProvider
provider = IBMProvider()

gives
AccountNotFoundError: 'No default ibm_quantum account saved.'
But IBMQ.load_account() works just fine.

Do you have an account named default-ibm-quantum in your qiskit-ibm.json file? I can't seem to replicate this issue
"default-ibm-quantum": {
    "channel": "ibm_quantum",
    "token": "...",
    "url": "https://auth.quantum-computing.ibm.com/api"
  }

Shouldn't it look for my other credentials from the usual IBMQ provider?

Shouldn't it look for my other credentials from the usual IBMQ provider?

It looks for credentials from the qiskit-ibm.json file, not the qiskitrc file from the old provider. In the runtime provider, we implemented https://github.com/Qiskit/qiskit-ibm-runtime/pull/370 which copies the qiskitrc file credentials into a new qiskit-ibm.json if one doesn't already exist. This feature was never implemented in this repo, but I can work on adding it.

Ahh ok.  I thought it worked the same here.  I am creating materials for teaching people how to use our new tools, and it would help to ease the transition when moving from the old provider to the new one.


Accumulate "Platforms" on NCPI studies when studies are being built using build-ncpi-db

Need
On the NCPI-Catalog dx versoin studies that belong to multiple platforms are not combined to a single study with a list of platforms.
Should be like:

Instead, we have:

Approach
In the ncpi-catalog explorer, there is a script called  build-ncpi-catalog.ts that is run using npm run build-ncpi-db. This script iterates over the list of PlatformStudyStubs that make up the script's input and expands using the dbGaP FHIR API to into the studies and platforms that are displayed on the study and platform tabs in the ncpi-dataset catalog version of the explorer app. Studies and platform json files are written into the /out directory under /files/ncpi-catalog/files
Currently, this script outputs one study per row in the dashboard-source-ncpi.tsv file.
Some studies are in multiple "platforms," however, and the study then is duplicated in the out/ncpi-platform-studies.json file.
Instead, the studies as keyed by their dbGaPId fields need to be unique in the ncpi-platform-studies.json file and when a study belongs to two platforms, both platforms are listed in the platforms section so:
"platforms": [
      "AnVIL",
       "BDC",
    ]

Instead of
"platforms": [       "AnVIL"     ]
One way to do this is is to de-dupe ncpiStudies here before it is returned, and modify any studies that are duplicated to be a single study with both platforms added to the platform array.

@hunterckx when launching the application go http://localhost:3000/explore. There you will see two tabs, studies and platforms. The studies tab is the one we are interested in here e.g. http://localhost:3000/explore/studies
All these  "explorer" apps going to /explore will tell you the list of entities you can select from.

Done!


Update dependencies

Please provide a description of this PR:
Update 3rd party dependencies

@jacob-delgado: 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

unit-tests-arm64_istio
9782a08cb05dd623c834dbb7cb5cbc5d4a73f403
link
true
/test unit-tests-arm64

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.

@jacob-delgado: 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

unit-tests-arm64_istio
9782a08cb05dd623c834dbb7cb5cbc5d4a73f403
link
true
/test unit-tests-arm64

unit-tests_istio
9782a08cb05dd623c834dbb7cb5cbc5d4a73f403
link
true
/test unit-tests

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.

@jacob-delgado: 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

unit-tests-arm64_istio
9782a08cb05dd623c834dbb7cb5cbc5d4a73f403
link
true
/test unit-tests-arm64

unit-tests_istio
9782a08cb05dd623c834dbb7cb5cbc5d4a73f403
link
true
/test unit-tests

release-test_istio
9782a08cb05dd623c834dbb7cb5cbc5d4a73f403
link
true
/test release-test

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.

@jacob-delgado: 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

unit-tests-arm64_istio
9782a08cb05dd623c834dbb7cb5cbc5d4a73f403
link
true
/test unit-tests-arm64

unit-tests_istio
9782a08cb05dd623c834dbb7cb5cbc5d4a73f403
link
true
/test unit-tests

release-test_istio
9782a08cb05dd623c834dbb7cb5cbc5d4a73f403
link
true
/test release-test

integ-basic-arm64_istio
9782a08cb05dd623c834dbb7cb5cbc5d4a73f403
link
true
/test integ-basic-arm64

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.


Navigation issue

Thank you for the beautiful library. When you open the library for navigation, it shows the month, and when you press back, it returns to the year display and then goes to the other screen.

I'm not sure what the issue is here? this functionality is correct

We decided to use it in our project for its beautiful appearance. but it was a waste of our time. When you put it in a normal page, it works very well, but when you put it on the 2nd or 3rd page of the navigation view in a structure when you press the back button on the navigation bar, your library shows the yearly in the monthly display and then closes.

i faced the same issue. I use  ElegantCalendarView(calendarManager: calendarManager).theme(CalendarTheme.yellowTheme).vertical()  like this. When clicking dismiss, it firstly shows previous month and then navigate to back.

I realized the navigation issue occurs when initialMonth is setted.

The owner closed the bug but it is a big bug @ThasianX @yahyaizala .

Maybe it uses uikit I don't know why but somehow  in navigationview when we initialize in navigationlink class.  it insert itself to view. Maybe that is why it happens.
@metin-atalay i solved it when opening the calendar I show a progress and after initialization I fade calendar,
before page is dismissed I remove it with a state. That way its strange behavior not seen by user.

Maybe it uses uikit I don't know why but somehow  in navigationview when we initialize in navigationlink class.  it insert itself to view. Maybe that is why it happens.
@metin-atalay i solved it when opening the calendar I show a progress and after initialization I fade calendar,
before page is dismissed I remove it with a state. That way its strange behavior not seen by user.

@yahyaizala thanks for the info


on OSX it doesn't use high DPI mode

cjay reports about the Homebrew binary:
02:34 < cjay-> and it dosen't use high dpi mode, so edges are a bit softened

Probably we'd need convenient scaling (#127) before we tackle that one, unless I misunderstand how the high DPI mode works. Softened edges are a problem, because this is a pixel-perfect font, so it should be crisp (and scaled up by integer multiples, preferably).

I don't know if it can and should be set automatically when High DPI mode is detected, but allFontsScale set to 3 produces 4K display, so it should at least be mentioned in README, release notes OSX section and possibly in the homebrew package description.

I've just noticed that when in Windows 10 DPI is changed from 96 to some other value, the game window is scaled and the fonts are deformed. So we should probably query DPI from OS and automatically scale using appropriate SDL2 mechanisms to prevent non-pixel perfect fonts. If the player wants the display scaled, he can do that in the config file, choosing the ratios in a way that keeps the fonts aligned with pixels.


Add a failing test for proc do |*args|

Add a test case for an example that the compiler can't handle.
Motivation

More tests!
Test plan

See included automated tests.

Do you think it’s worth assigning it to a variable and calling it as well? This test doesn’t print anything

Yes, that's a good idea. Given that the compiler was crashing when compiling it this felt like a good enough start, but I'm happy to add some prints as well.


Suggestion: Template project adopt "lib/screens" structure

I'd suggest that, even if the content of the template stays the same, there should be greater separation of concerns (as opposed to everything Flutter being in 1 .dart file). This is a suggestion, but I typically use the following:
lib
  screens
    - main_screen.dart
  - main.dart

I've adopted "screen" but I know the example is using "page". Not sure if that is a flutter-ism i just ignored/missed. Also, we might want to keep states separate to screens. Not sure. That would also be a good guidance from the team as to what is the "best practice" in lieu of having one of your/my own.

We've gotten similar requests from Google teams wanting more guidance on best-practices/layout.  I suspect it's time to make our template a bit more sophisticated or something between the template and gallery and hello_services more accessible.  FYI @mit-mit

Are we agreeing that "screens" is a reasonable default/convention for Flutter app structure?
Would we take a patch for this?
In absence of anything better, makes sense to me :)

I think we should keep our initial template to a single file and let people do what they want beyond that. I've never actually organised my code the way this bug describes, but I could definitely see it being reasonable. I just don't think there's value in the template having an opinion on this.
Having a single file for the template has the huge advantage that it allows new users to see everything in one file.

let people do what they want beyond that

I think there's a lot of value for Flutter apps to be organized in a similar way. Similar to how Rails projects are created (models go into models/, etc), similar to how pub packages are created (tests go into test/), etc. Convention over configuration is a powerful pattern.
I like simple starter projects, but I do think we want to have more opinion (over time) about how our projects are structured. It may be too early to see a pattern emerge here. I'm curious what our internal customers are doing here, to structure their app's source code in directories.
cc @tvolkert have you seen any patterns?

I agree with @Hixie that this level of organization should be left up to apps.  The discussion we've had internally in Google are more about where Dart (Flutter) vs ObjC (iOS) vs Java (Android) code goes -- which is fairly prescriptive inside Google.

So no one is organizing their code around screens? Good to know...

I'm sure some people are. I just don't see that as our job to prescribe.

Sounds like we're not yet ready to prescribe more app structure via our starter app template. We do think it's a good idea to document more app structure and best practices as we learn them.
We appreciate the suggestion, but we're going to close this one for now.
Feel free to blog your own Flutter app structure thoughts. Hopefully over time, the community will converge on some conventions.


Add more field types

Adds two more field types for later validation as mentioned
in #440

Ive changed the VALUE_TYPE_ variables names so that @jochenklar can merge it in the 1.8.1 release


Check, Join region logic and navigation

🗃 Github Issue Or Explanation for this PR. (What is it supposed to do and Why is needed)
#1616
✅ Checklist

[x] Github issue details are up to date for people to QA.
[x] I have tested all my changes.

🕵♂ Notes for Code Reviewer

Detect user has or not a region on Join Region screen mounted.
Navigation to Main region Screen on Join succesfully.

Note: I have to hardcode a Leave a region button to test the join and leave flow.
🙈 Screenshots
https://user-images.githubusercontent.com/42857405/160038083-fd5d96e9-3ad6-4dc9-b40b-c46fba006b51.mp4
👯♀ Paired with
"nobody"

Ohh I see I did an extra work I did not notice you can navigate to Region Detials Screen by pressing the search result tile.
Well I guess I could move that in other PR.


Review existing document

taxonomy of stories
metrics
research

Repos:

https://github.com/nprapps/carebot
https://github.com/nprapps/graeae

Docs emailed to Matt.


[Don't pull - for comparison] E2T part refactored

Renamed storeTradeReserveData to storeSingleReserveData
Refactor E2T to split and non-split

revamp kills this direction


mat-cell:first-child for mat-table suddenly has 24px left padding which it didn't have before

Bug, feature request, or proposal:
Bug?
What is the expected behavior?
mat-cell:first-child for mat-table suddenly has 24px left padding which it didn't have in earlier material versions all the way up to at least @6.0.0.beta.4.
I would expect no default left padding as before.
What is the current behavior?
With the upgrade to version 6.0.1 I now have the following css...
mat-cell:first-child,
mat-footer-cell:first-child,
mat-header-cell:first-child {
    padding-left: 24px;
}

which messes up the alignment of all my tables.
I have to now supply this override in my global css.
mat-cell:first-child,
mat-footer-cell:first-child,
mat-header-cell:first-child {
    padding-left: 0px !important;
}

What are the steps to reproduce?
None needed.
What is the use-case or motivation for changing an existing behavior?
That is my question to you.  :)
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
material 6.0.1
Is there anything else we should know?

The problem comes when you hide some columns according to browser size. For example (using Bootstrap display utilities):
<ng-container matColumnDef="accountName">     <mat-header-cell *matHeaderCellDef class="d-none d-lg-flex"> Account </mat-header-cell>     <mat-cell *matCellDef="let item" class="d-none d-lg-flex">{{ item.accountName }}</mat-cell> </ng-container>
I could control the browser size changes from the controller and then modify the array with the displayed columns, but I don't like to control responsiveness from the controller as I think this is a completely view-related issue.

I've finally changed the styles to revert the situation, so I have those (SCSS):
.mat-table {
  mat-row, mat-header-row, mat-footer-row {
    padding-left: 24px;
    padding-right: 24px;
  }

  mat-cell:first-child, mat-footer-cell:first-child, mat-header-cell:first-child {
    padding-left: 0;
  }

  mat-cell:last-child, mat-footer-cell:last-child, mat-header-cell:last-child {
    padding-right: 0;
  }
}

This way I can hide the first or last column and the padding remains.

Thank you @andrewseguin, this Solved my Problem.


Fix jax2tf device incompatiblity for Export

This PR checks whether the installed packages for JAX and TF both can access the GPU when JAX with GPU is being used for export.
If TF is CPU-only, the export API will prevent the usage of JAX-native serialization, allowing cross-device compatibility, but at the expense of performant serving from the exported artifact.

This resolved the tests.  But should we add an argument to model.export so user can specify the export target device as GPU or CPU? so we don't automatically infer based on what the user has installed which could be different from what the user wants to run it in?
@fchollet - WDYT?

@fchollet - WDYT?

This is also a good idea. Is it viable to configure the target device at export time?

@fchollet @sampathweb There doesn't seem to be a way to configure the target device at export time. JAX only has device placement for running functions with jax.jit, but jax2tf.convert will run on JAX's default device (in this case, GPU). The only option is enabling cross-device compatibility by allowing non-native serialization. (We could potentially add this as a flag?)
There isn't any device scope like we see in TF, unfortunately.

Ok, let's just merge this, we can revisit the solution later.

Sounds good! Feel free to merge!


Hardcoded MPS port "3000" in docker-compose file

Hardcoded MPS port in docker-compose file and also in MPS Dockerfile.

While we are integrating AMT setup with other microservices(ESH RI related recipe) in that case one of the microservice uses "3000" port giving conflict to AMT setup (All these microservices including AMT will be deployed in the same machine).
If we change the exposed port from 3000 to some other will that impact or creates any issue with the below command in docker-compose.yml
command: >
/bin/bash -c "
while ! nc -z mps 3000;
do
echo waiting for mps;
sleep 5;
done;
echo MPS Running!;
node ./dist/Index.js;
"

Gotcha, ok yeah so the issue stems from the 2nd point in my earlier post. We'll take care of it.

I see a couple issues with in our master branch that need to be resolved in that mainly we should not be changing the port inside the container and only the port for which is exposed. This is something that will be addressed in the next release.


Adding Folders and Files

#1
There is a user Dashboard, app/dashboard/page.js ,
On dashboard we are able to see some cards so now we have to create pages for each card
Your Task is to create app/${FolderName}/page.js for each features on dashboard
the folder name should be same as feature name
Comment below /Attempting and Start working on it

/Attempting

Merge Completed
adding files and folders -- >
 app/ContentSharing/page.js
 app/Discussions/page.js
 app/InquireAboutCrops/page.js
 app/LearningAndResources/page.js
 app/PersonalAiSupportBot/page.js
 app/SeasonDashboard/page.js
 app/UserProfiles/page.js
 app/WeatherDashboard/page.js
Thanks For Your Contribution.
Make Shure You add Your Details
After Contributing in    Contributing
No Worries you can add next time


Can't run quickwit on aws linux

I had first an issue with libsasl2.so.2
./quickwit
./quickwit: error while loading shared libraries: libsasl2.so.2: cannot open shared object file: No such file or directory

I tried to solve it with this fix
cd /usr/lib64
sudo ln libsasl2.so.3 libsasl2.so.2

And then I got these errors:
./quickwit: /lib64/libsasl2.so.2: no version information available (required by ./quickwit)
./quickwit: /lib64/libpthread.so.0: version `GLIBC_2.28' not found (required by ./quickwit)
./quickwit: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by ./quickwit)
./quickwit: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by ./quickwit)
./quickwit: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by ./quickwit)
./quickwit: /lib64/libc.so.6: version `GLIBC_2.29' not found (required by ./quickwit)
./quickwit: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by ./quickwit)
./quickwit: /lib64/libc.so.6: version `GLIBC_2.30' not found (required by ./quickwit)

was linux info:
cat /etc/os-release
NAME="Amazon Linux"
VERSION="2"
ID="amzn"
ID_LIKE="centos rhel fedora"
VERSION_ID="2"
PRETTY_NAME="Amazon Linux 2"
ANSI_COLOR="0;33"
CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
HOME_URL="https://amazonlinux.com/"

Fixed via #2546, #2549, and #2550.


FaceMesh inconsistency when evaluating the same image [Python]

When I execute the following code I get the necessary landmarks.
import cv2
import mediapipe as mp
import imageio.v3 as iio
import numpy as np

mpDraw = mp.solutions.drawing_utils
drawSpec = mpDraw.DrawingSpec(thickness=1, circle_radius=2)
mpFaceMesh = mp.solutions.face_mesh
faceMesh = mpFaceMesh.FaceMesh(max_num_faces=1, refine_landmarks=True, min_detection_confidence=0.01)

url = <URL HERE>
img = iio.imread(url)
img = cv2.cvtColor(img, cv2.COLOR_BGR2RGB)
results = faceMesh.process(img)
ih, iw, ic = img.shape
if results.multi_face_landmarks:
    for faceLms in results.multi_face_landmarks:
        mpDraw.draw_landmarks(img, faceLms, mpFaceMesh.FACEMESH_CONTOURS, drawSpec, drawSpec)

However when I use a list of URLs it fails to even detect a face for some of them. Other times the landmarks are found to be in different positions than when processed in the above snippet. It is always the same ones that fail so it does not appear to be a race condition.
import cv2
import mediapipe as mp
import imageio.v3 as iio
import numpy as np

mpDraw = mp.solutions.drawing_utils
drawSpec = mpDraw.DrawingSpec(thickness=1, circle_radius=2)
mpFaceMesh = mp.solutions.face_mesh
faceMesh = mpFaceMesh.FaceMesh(max_num_faces=1, refine_landmarks=True, min_detection_confidence=0.01)

urls = <LIST OF URLS HERE> # the first offending image happens to be index 29. It happens frequently after that point.
for url in urls:
    img = iio.imread(url)
    img = cv2.cvtColor(img, cv2.COLOR_BGR2RGB)
    results = faceMesh.process(img)
    ih, iw, ic = img.shape
    if results.multi_face_landmarks:
        for faceLms in results.multi_face_landmarks:
            mpDraw.draw_landmarks(img, faceLms, mpFaceMesh.FACEMESH_CONTOURS, drawSpec, drawSpec)

I've tried playing with the min_detection_confidence (normally I would never set it so low as 0.01) but that had no effect.

static_image_mode needed to be True.... Closing


Build target(s) for Intel MIC

Original issue: https://charm.cs.illinois.edu/redmine/issues/190

We should incorporate the work done to build on MIC with the main codebase. If it's easily backported, it should go on the stable branch as well.

Original date: 2013-06-20 22:14:35

The initial issues here stem from subtle interactions between the Intel cross compiler scheme for MIC (aka Intel Xeon Phi, KNC, Knight's Corner, plus whatever the, arguably overly fecund, brand name developers from Intel come up with next as a name for these things) and Charm++ compiler wrapper settings.
All libraries which a MIC application binary must link to must go through the cross compiler (icc -mmic, or a more gnarly explicit path call to x86_64-k1om-linux-g++, which should probably be avoided as we have no guarantee about name stability for that thing) and its linker.
All binaries which would be executed on the host (usually charmc and various configure tests) should usually not go through the cross compiler.  In the past, we have generally used CMK_NATIVE (aka charmc -seq) for these.  However, -seq has crept into a bunch of things which must be linked to by application binaries, such as libckqt.a.  So we now have some semantic confusion over what -seq means in this context and how it should be configured.
In the general case, on machines like Stampede, the mic0 host is not always directly accessible, so various tools like charmrun, should not be compiled with -mmic.  On experimental machines, like NCSA's Xeon Phi, root access to mic0 is available and they might wish to use charmrun natively compiled for the MIC.  IMHO, anyone doing that should be expected to solve their own wacky compilation and linking issues.  Our main audience is people trying to leverage Phi on Stampede.
On a related note, the MIC environment has its own issues.  Notably, there is no MIC ibverbs library to link to on stampede, so you cannot even attempt to use their verbs proxy within the MIC context.
One can build using intel MPI with one binary for host and one for MIC and use ibrun.symm to have PEs running on both host and MIC.  The process currently requires some somewhat arduous hackery.  That process will be covered in a different issue.
A proper native layer should be able to use the dual binary launch scheme of ibrun.symm, but the necessary underpinning is not yet developed.

Original date: 2015-08-18 16:12:51

Just saving some useful changes from knc3 which is being decommissioned today:

1.       renamed:    src/arch/mpi-linux-x86_64/conv-mach-mic.h -> src/arch/common/conv-mach-mic.h
1.       renamed:    src/arch/mpi-linux-x86_64/conv-mach-mic.sh -> src/arch/common/conv-mach-mic.sh

Original date: 2016-12-13 23:27:36

is this still relevant or should it be closed?

Original date: 2016-12-14 21:14:30

Sam White wrote:

is this still relevant or should it be closed?

I'm not sure. Kavitha or Seonmyeong can comment further as they've been using new KNL hardware recently.

Original date: 2017-02-02 04:38:45

KNL is self-hosted and doesn't require the complicated dual binary launch scheme. Since this is off the radar for now, but something similar could appear in the future, reassigning to PPL for now.


Fix parallelization by fixing pickling and un-pickling of CADET-dll

As described in https://github.com/cadet/CADET-Python/issues/25  with CADET-Python v1.0.0 the parallelization is broken because we can not pickle ctype pointers.
My proposed solution is to remove all pointers from the state, only save the _cadet_path and then on __getstate__ re-load the dll and pointers in the child-thread.
ToDo:

[x] Fix pickling
[x] Add test

Just out of curiosity, can you elaborate what function __getstate__ serves?

__getstate__ get's a pickleable state of the object. Usually, that's just self.__dict__, but by overriding __getstate__ we can change that. We can, e.g. remove all non-pickleable parameters and then change __setstate__ to re-create the removed parameters.


Improve uploads

Main use case here is for documentation, but uploading a screenshot or diagram is currently a pain...
Let's have drag and drop/copy and paste upload integration within the editor using something like https://www.dropzonejs.com/.

https://codepen.io/sn4ke3ye/pen/GRppEGr
https://stackoverflow.com/questions/32493709/enable-copy-and-paste-files-in-dropzone-js
https://gitlab.com/meno/dropzone/-/wikis/FAQ#how-to-show-files-already-stored-on-server
https://ourcodeworld.com/articles/read/491/how-to-retrieve-images-from-the-clipboard-with-javascript-in-the-browser
https://www.sitepoint.com/file-upload-form-express-dropzone-js/
https://www.group-office.com/blog/post?id=6650328555423695690

Closed in #108.


vscode intellisense does not show union types for typescript

VSCode Version:3.6.2
OS Version: Windows PRO 10

Steps to Reproduce:

const map = new Map<string, number>();
const rc2 = map.get('hello');

Hover over the rc2 constant, you will see only "number" not "number|undefined"
you will see this (screenshot below), the lookup (Map.get) is not always successful ofc, so
undefined is certainly a possibility
Screenshot

I solved this by setting the tsconfig setting is "strictNullChecks": true,


Missing installer roles

Description
When running the installer via ./installer/install.sh the following error is raised:
ERROR! the role 'install-socat' was not found in /Users/eshortis/workspaces/rhmap/mobile-core/installer/roles:/Users/eshortis/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/Users/eshortis/workspaces/rhmap/mobile-core/installer

The error appears to have been in '/Users/eshortis/workspaces/rhmap/mobile-core/installer/playbook.yml': line 6, column 5, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

  roles:
  - role: install-socat
    ^ here

This can be fixed by commenting it from the playbook.yml, but then this happens:
ERROR! the role 'openshift-origin-client-tools' was not found in /Users/eshortis/workspaces/rhmap/mobile-core/installer/roles:/Users/eshortis/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/Users/eshortis/workspaces/rhmap/mobile-core/installer

The error appears to have been in '/Users/eshortis/workspaces/rhmap/mobile-core/installer/playbook.yml': line 9, column 5, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

  - role: openshift-origin-client-tools
    ^ here

Similarly, it can be fixed by commenting out if the tools exists on your machine already.
Environment

ansible - <IP_ADDRESS>
oc - v3.7.1+ab0f056

Operating system: macOS - 10.12.6
Steps to reproduce
Per above, run installer/install.sh

Updating to Ansible 2.5+ fixed this. It seems to be some issue related to the OpenSSL version used by Python on macOS (brew version vs system installed version)
Anyways. Fixed!


Notification icon does not render

The Greenbay community founder has notified us that the notification icon does not render on his phone:

I have tested the notification icon for Leu and Greenbay. It works fine for me. However, I have researched potential issues, and I have a hypothesis. I would like to know where the error originates from, how it occurs on the phone, and in which specific scenarios. Could you provide more information about this error?

I ran a bug report and extracted all lines containing the word "encointer" in it.
The device is a Google Pixel 6. Let me know if this helps!
encointer_lines.txt

@adamsteeber thanks a lot. I'm trying to test with Google Pixel 6.

Hello!
I tested showNotification/scheduleNotification the notification icon with the Pixel 6 emulator and couldn't find any errors.
Could you please test it again? According to my research, if the icon is not displayed for Android, it seems that you need to specify the icon (for example 'icon: ic_launcher') in the AndroidNotificationDetails. But it's working for us. @adamsteeber could it be just a coincidence?

Here's a link to a screen record of me replicating the issue.
I wonder if it's specific to my device, perhaps some kind of specific cross-app interaction/ conflicting defaults or notification settings. Note, the chime doesn't work as well - in fact no notification sound is played.
I'm guessing it's some kind of default on my device that's overriding the encointer notification settings. But I'm really not sure.


Implement various pagination improvements

[x] Fix bug that reloads history when reloading service page (without this fix, if you load a service page, then go to the home page and reload the same service page again, it will reload the history, resulting in duplicate items)
[x] Disable next page button when there isn't a next page
[x] Implement previous page (fixes #45)
[x] Only load Trakt/TMDB/Corrections data for items in the current visible page (prevents unnecessary requests)
[x] Only allow selecting/syncing items in the current visible page
[x] Immediately update page to reflect changes to items per load option
[x] Change data loading order (more useful to load correction suggestions before images)
[x] Fix bug that loads next page when reloading service page
[x] Use axios (makes canceling requests easier)
[x] Cancel requests when loading a new page or exiting (prevents unnecessary requests)

Done here. Noticed some other stuff that need to be fixed, but I'll put them in other PRs. Only missing the NO translation.


Feature/root dash

Purpose
Add parent and root project names to the dashboard
Changes

Embeds those names in the API request for each project
Handles private projects
Notes if parent and root are not directly touching in the project tree

Side effects

Already tested for special characters
Already tested for same named parents/children
Already tested for periods in name
Any failed request becomes an empty string, and strings are compared to see if projects match. Unforseen failures may result in a positive match.

Ticket
https://openscience.atlassian.net/browse/OSF-6027

I fixed the jshint error when I merged. Merged into release/0.78.0. 🐙


Add output file option to avoid overwriting original board

Currently, the CLI app always overwrites the original file. This is similar to the Action Plugin, which acts on the working board data.
However, for some use-cases it might be useful to create a set of boards, each with a different variant (e.g. for CI or multiple outputs). Currently this requires copying the original file beforehand.
Add an --output / -o option to change the name of the output file to something different than the original file name.

Implemented on main branch: 9e9ea1ec927906fd4530ba38c983eafcc2366b97


Hot reload

Is there a way to do a hot reload of the example App when the component code changes. Currently, it seems that we need to clean node_modules and install again for testing the changes to the component being developed.

@brodybits  - I mean when we change the JS code in the module component. Reason for that is when someone is developing a component, it would be lot faster for them to test changes.

Just copy your JavaScript code into the example while you are developing it then copy it back where it belongs and test once more before committing. It should be no problem to do import { NativeModules } from 'react-native' or import { requireNativeComponent } from 'react-native' in the example app while you are developing.
Does this answer the question?

Ya. It does. If that is the recommended approach.
Alternatively we could just make the contents of the example folder as the package itself, but just export the components and npmignore any of the app code.
This way, we don't need to do copy paste everytime when we need to make updates.
I guess, I am thinking of modules which will be regularly updated etc and hence avoiding copy paste will be better.


cliprdr long format names support

There's a serious bug in the current cliprdr plugin where capabilities are ignored, and long format names are improperly handled. When connecting to Windows Server 2008 R2 SP1, the server capabilities are the following:
DBG_CLIPRDR cliprdr_process_general_capability (106): Version: 2
generalFlags (0x0000001E) {
CB_USE_LONG_FORMAT_NAMES
CB_STREAM_FILECLIP_ENABLED
CB_FILECLIP_NO_FILE_PATHS
CB_CAN_LOCK_CLIPDATA
}
The problem then comes in cliprdr_process_format_list where the implementation assumes the usage of the short format name instead of the long usage name. The plugin then falls into an infinite loop, eating the CPU.

I just completed the implementation of long format names, now I can actually use clipboard redirection successfully. RemoteApp is a different ticket though, it'd be great to have but there are other challenges to go over before having both RAIL and CLIPRDR functional at the same time.


docs(kong-mesh) describe how to configure vault step by step

Added a description of how to configure Vault with Kong Mesh
Changed inline to inlineString, which is probably more convenient for the token, you don't have to do base64
Changed the structure of Authentication to have ## Using Vault CA -> ### Configure Vault, ### Configure Mesh. mTLS to Vault is optional.

TODO:
can't get the tabs to be properly put into steps!

@jakubdyszkiewicz I copied your changes over to my release PR (#2845) where I had to fix the tabs issue differently (turns out we don't support tabs nested inside lists, it was not you). So closing this one unmerged bc taken care of there. Thank you!


Devil May Cry 5 (220440)

Has it's graphic options being synced through the Steam Cloud, making it a pain to go back and forth between PC and Steam Deck, especially with regards to resolution.

If you can give me some info on the where the settings file is I can try to add it to the script. I don't own this game so can't test it directly and steamdb doesn't tell me where it is.

If you can give me some info on the where the settings file is I can try to add it to the script. I don't own this game so can't test it directly and steamdb doesn't tell me where it is.

It should be in the games folder under the name dmc5config.ini

Can you try the script in this branch?

@MrBareBones Were you able to test this?
Also you have the game name "Devil May Cry 5" which would be app ID 601150 but you have app ID 220440 which is a different Devil May Cry. Can you clarify which one you meant?

@MrBareBones Were you able to test this?
Also you have the game name "Devil May Cry 5" which would be app ID 601150 but you have app ID 220440 which is a different Devil May Cry. Can you clarify which one you meant?

Nearly a year late, but no I wasn't. Also yeah I accidentally got the Steam ID for DMC: Devil May Cry by mistake instead of DMCV's


Fatal Python error: (pygame parachute) Segmentation Fault

Same issue on more than one computer usinf Linux Mint 17.2
File main.py :
from kivy.app import App
from kivy.lang import Builder
from kivy.uix.screenmanager import ScreenManager, Screen, FadeTransition
class MainScreen(Screen):
pass
class AnotherScreen(Screen):
pass
class ScreenManagement(ScreenManager):
pass
presentation = Builder.load_file("main.kv")
class MainApp(App):
def build(self):
return presentation
MainApp().run()
File main.kv :
#: import FadeTransition kivy.uix.screenmanager.FadeTransition
ScreenManagement:
transition: FadeTransition()
MainScreen:
AnotherScreen:
:
name: 'main'
Button:
on_release: app.root.current = 'other'
text: 'Another Screen'
font_size: 50
:
name: 'other'
Button:
on_release: app.root.current = 'main'
text: 'back to the home screen'
font_size: 50
error when running code :
[INFO   ] [Logger      ] Record log in /home/sandrine/.kivy/logs/kivy_15-10-15_5.txt
[INFO   ] [Kivy        ] v1.9.1-dev
[INFO   ] [Python      ] v2.7.6 (default, Jun 22 2015, 17:58:13)
[GCC 4.8.2]
[INFO   ] [Factory     ] 177 symbols loaded
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_gif, img_pygame, img_pil (img_ffpyplayer ignored)
[INFO   ] [Window      ] Provider: pygame(['window_egl_rpi'] ignored)
[INFO   ] [GL          ] OpenGL version <4.4.0 NVIDIA 340.93>
[INFO   ] [GL          ] OpenGL vendor
[INFO   ] [GL          ] OpenGL renderer <Quadro 600/PCIe/SSE2>
[INFO   ] [GL          ] OpenGL parsed version: 4, 4
[INFO   ] [GL          ] Shading version <4.40 NVIDIA via Cg compiler>
[INFO   ] [GL          ] Texture max size <16384>
[INFO   ] [GL          ] Texture max units <32>
[INFO   ] [Window      ] virtual keyboard not allowed, single mode, not docked
[INFO   ] [Text        ] Provider: pygame
[INFO   ] [OSC         ] using  for socket
[INFO   ] [Base        ] Start application main loop
[INFO   ] [GL          ] NPOT texture support is available
Fatal Python error: (pygame parachute) Segmentation Fault

How did you install kivy?

sudo add-apt-repository ppa:kivy-team/kivy
sudo apt-get update
sudo apt-get install python-kivy python-dev
I even tried with easy_install
for some reason works fine on my raspbian jessie

Try installing these deps then reinstalling kivy http://kivy.org/docs/installation/installation-linux.html#dependencies-with-sdl2.

Pygame should not be used by kivy if everything goes well.

Now, even if I uninstall pygame and a different kivy version
[INFO ] [Logger ] Record log in /home/sandrine/.kivy/logs/kivy_15-10-15_10.txt
[INFO ] [Kivy ] v1.9.0
[INFO ] [Python ] v2.7.6 (default, Jun 22 2015, 17:58:13)
[GCC 4.8.2]
[INFO ] [Factory ] 173 symbols loaded
[INFO ] [Image ] Providers: img_tex, img_dds, img_gif, img_pygame, img_pil (img_ffpyplayer ignored)
[INFO ] [Window ] Provider: pygame(['window_egl_rpi'] ignored)
[INFO ] [GL ] OpenGL version <4.4.0 NVIDIA 340.93>
[INFO ] [GL ] OpenGL vendor
[INFO ] [GL ] OpenGL renderer
[INFO ] [GL ] OpenGL parsed version: 4, 4
[INFO ] [GL ] Shading version <4.40 NVIDIA via Cg compiler>
[INFO ] [GL ] Texture max size <16384>
[INFO ] [GL ] Texture max units <32>
[INFO ] [Window ] virtual keyboard not allowed, single mode, not docked
[INFO ] [Text ] Provider: pygame
[INFO ] [OSC ] using for socket
[INFO ] [Base ] Start application main loop
[INFO ] [GL ] NPOT texture support is available
Fatal Python error: (pygame parachute) Segmentation Fault

I was able to make it work after remove anytrace of kivy.
Reinstall by following your instructions by ignoring ffmepg because it's not available on mint.
And after everything worked perfectly.


Adding/removing physical segment for a logical table

I have the following setup:
2 (two) pinot servers hosting same real-time table (same table name / kafka consumer group id); each one of the servers receivs 1/2 of total of msgs from the kafka stream.
1 (one zookeper), 1 (one) broker and 1 (one) controller
What happens if one of the servers crashes (the server process itself), I understand that the second server will consume 100% of the messages while the second server is down (I can see that the broker query returns about half of the documets numbers in this case), but how can I add the second server again (if at all) in order to restore the original setup ?
What's going to happen if a broker/controller crashes ?
In general, how should I manage adding/removing pinot segments for reducing workload balance and/or system crash ?
Thank you

Currently, the realtime consumption in Pinot uses the high level consumer which leads to the behavior you're seeing.
If you want to create two servers that consume from Kafka, each of them should get their own consumer group ID so that they each get all of the data; since the realtime segment boundaries include offsets, all replicas of the realtime segments should contain the same data, so a server node that crashes does not change the query results.
This is not ideal and it's on our roadmap to improve Kafka consumption.

What happens if one of the servers crashes (the server process itself), I
understand that the second server will consume 100% of the messages while
the second server is down (I can see that the broker query returns about
half of the documets numbers in this case), but how can I add the second
server again (if at all) in order to restore the original setup ?
There are two scenarios,
#1. adding a new server
In this case, the new server will start handling 1/2 of the total msgs. I
think, there is a need to tag the new machine with the same name as the old
one. I know there is an api for this buts its probably not documented. (we
will provide a command to do this).
#.Bringing the failed server back up
In this case, the messages will again be distributed equally among the two
nodes. There is no need to make any additional modifications to the tag as
in previous case.
In general, you want to use have multiple replicas to handle failures.
Broker: Have more than one broker will provide you fault tolerance. The
request can be forwarded to any live broker.
Controller: Simply start multiple controllers, there is leader election
among the controllers and only one controller will manage the cluster. If
the leader fails, a new leader is elected and it starts managing the
cluster.
Server: Here when you create a resource, you specify the number of replicas
needed for each segment. Typically we use 3 replicas in our deployment. In
case of failure, broker automatically detects the failures and routes the
queries to live servers.
Hope this helps.
Thanks,
Kishore G
On Thu, Jun 25, 2015 at 4:02 PM, Jean-François Im<EMAIL_ADDRESS>wrote:

Currently, the realtime consumption in Pinot uses the high level consumer
which leads to the behavior you're seeing.
If you want to create two servers that consume from Kafka, each of them
should get their own consumer group ID so that they each get all of the
data; since the realtime segment boundaries include offsets, all replicas
of the realtime segments should contain the same data, so a server node
that crashes does not change the query results.
This is not ideal and it's on our roadmap to improve Kafka consumption.
—
Reply to this email directly or view it on GitHub
https://github.com/linkedin/pinot/issues/16#issuecomment-115424476.

Thank you for your answers,
Can you please be more specific about the how server vs replicas work?
I'm taking the scenario of real-time consumption and storing same table on multiple servers.
Are replicas created and queried by the server process or using the controllers ?
I'm asking that because I want to be sure that I know how to deal with potential failures.
A server process dumps its segment data to the hard disk (I assume that we use 3 replicas per segment), and this data is read when query is received.
If suddenly the server process stopped (due to an exception memory error etc.) - the stored data of the replicas isn't reachable anymore, right ? It's not ever relevant that the data is replicated, because the process which is responsible for reading the data is down.
Let's say I re-start the same failed server process again. Will the old replicated data will be available as soon as the new server process is up ? Will it continue to add new data to the old replicas, or will create new replicas and the old (pre-failure) data will be lost?
Thank you again. Pinot is an exciting project and I really want to understand how to use it in my case.
P.S. if there's some technologies that Pinot is build on and will answer my questions I'd be happy to read about it.


inspect.getargspec() is deprecated since Python 3.0

Since release 0.9.3 this method raises a DeprecationWarning in Python3:
.../sentry_sdk/consts.py:61: in _get_default_options
    a = inspect.getargspec(ClientConstructor.__init__)
.../python3.6/inspect.py:1078: in getargspec
    DeprecationWarning, stacklevel=2)
E   DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use inspect.signature() or inspect.getfullargspec()

Thanks, I will release 0.9.5.

Wow, that's quite a response time. Thank you!


React tab for code snippets

Updated all components and tested snippets that might be problematic. Everything works fine.

mockup-code changes need to be discarded.

Due to the script, there was an issue with mockup-code.svelte.md. The issue is due to the using the pre tags as start and finish points.
Here is the fixed file.
mockup-code.svelte.md

Awesome!
I will merge this after making sure all examples are okay.

@WickedInvi Thanks for the effort.
Everything looks fine except:

mockup-code.svelte.md issue as you said:
Please add the file changes you mentioned to the PR.
a few other JSX syntaxes that must be replaced:

numerical values like this tabindex="0" ➡ tabindex={0}
All SVG atrributes must be camelCase like thisstroke-linecap ➡ strokeLinecap [Full list here]

It would be cool to automate this process using a script like the one you provided but since this is a one-time job and we don't need to translate HTML to JSX for all examples every time, I think we can just merge this PR (after fixes) and for new additional component examples, we will provide JSX code as well as HTML code.

I've updated the mockup-code.svelte.md and added the JSX syntax

is the htmlFor='' attribute an alternative to for='' in just react? just an observation that the  for="" attribute remains at. not sure if

https://daisyui.com/components/modal/ in the jsx template
and possibly some other places.

happy to make a pr :)

@chazzox nice catch! Yes, PRs are welcome of course.

hopefully this catches everything :) https://github.com/saadeghi/daisyui/pull/1095


Fix k8s data transfer setup

Instead of reusing (abusing) the original job, launch a separate deployment with a busybox pod and minimal requirements to facilitate data transfer.
This addresses #647 and #648

Instead of separating data transfer from the main job, we should consider using a sidecar or, probably better yet, an init container as part of the main job, with the sole purpose of performing data transfer. What do you think?

Won't the init container be started for each job pod though?

Yes, although that's a feature rather than a bug. 😄 We can use the init container for synchronization when parallelism is greater than 1.
E.g. use the first init container for the actual data synchronization process, and use the others just to wait until the data copy finishes.

There's still an issue, though: copying the results back once the job finishes running.


Added additional domains for Gov. of Netherlands

Additional domains added for the Government of Netherlands based on the appendix of "Meting Informatieveiligheidstandaarden overheid september 2020", 30 October 2020, Forum Standaardisatie. Related publication. Furthermore, I updated the flags for bounty and swag based on this blog.

@jeroenvdmeer are you sure about this list, I myself found the following list: https://www.communicatierijk.nl/vakkennis/rijkswebsites/verplichte-richtlijnen/websiteregister-rijksoverheid
And on your link it mentions central government (Dutch Rijksoverheid) looking at the sheet downloaded from the url I mentioned I do not believe all cities and such should be included. Neither should the KvK and other similar instances.

@martinvw I think you are correct. At the bottom of the responsible disclosure page on the website of the central government it's mentioned that NCSC's scope is the central government. Provinces and municipalities are excluded. I must note that in practice I've seen NCSC processing my reports that included provinces and "zbo's", but I guess that was just out of politeness and it cannot be guarenteed that NCSC will remain doing so. As a result of this conclusion I will close this PR.


Pulling tasks from Todoist, removes recurring schedule from Todoist.

If I pull tasks from Todoist having a recurring schedule, then after successful, the todosit task gets updated which removes the recurring schedule from the task.
Task before pull

Task after pull

same issue


Gas reporter isn't enabled by default

Eventhough it says the default value of enabled in config is true, gas reporting wasn't working for me when I did tests with the following Hardhat config:
import { HardhatUserConfig } from "hardhat/config";
import "@nomicfoundation/hardhat-toolbox";
import "hardhat-gas-reporter";

const config: HardhatUserConfig = {
    solidity: {
        version: "0.8.17",
        settings: {
            optimizer: {
                enabled: true,
                runs: 200
            }
        }
    },
[...]
}

When I explicitly added the gas reporter and set enabled to true, gas reporting worked:
import { HardhatUserConfig } from "hardhat/config";
import "@nomicfoundation/hardhat-toolbox";
import "hardhat-gas-reporter";

const config: HardhatUserConfig = {
    solidity: {
        version: "0.8.17",
        settings: {
            optimizer: {
                enabled: true,
                runs: 200
            }
        }
    },
[...],
    gasReporter: {
        enabled: true
    }
}

I think the readme is misleading about being enabled by default.

I faced this too

Same here

yes the same problem I was facing, the report was getting report but I enabled to true and it worked.

If you're using the hardhat toolbox you have to read the hardhat.config.ts that installs with the project. They have set it up to run with an environment variable.
if (gasReporterConfig?.enabled === undefined) {
    // eslint-disable-next-line @typescript-eslint/strict-boolean-expressions
    configAsAny.gasReporter.enabled = process.env.REPORT_GAS ? true : false;
}

https://github.com/NomicFoundation/hardhat/blob/2f5c30cec52434e6a798dadfd314979c7fd4c742/packages/hardhat-toolbox/src/index.ts#L30-L33


Fix link to nodeport Service type

This will correct the link to the Nodeport service type's section in the Service concept document.

recheck CLA signature registration ?


delete some unit tests

Pull Request Test Coverage Report for Build 16

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.7%) to 97.19%

Files with Coverage Reduction
New Missed Lines
%

boards/views.py
5
94.32%

Totals

Change from base Build 11:
-0.7%

Covered Lines:
761

Relevant Lines:
783

💛  - Coveralls

Codecov Report

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

@@            Coverage Diff            @@
##             master       #7   +/-   ##
=========================================
  Coverage          ?   97.19%
=========================================
  Files             ?       26
  Lines             ?      783
  Branches          ?        0
=========================================
  Hits              ?      761
  Misses            ?       22
  Partials          ?        0

Continue to review full report at Codecov.

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

Codecov Report

Merging #7 into master will decrease coverage by 2.16%.
The diff coverage is 7.69%.

@@            Coverage Diff             @@
##           master       #7      +/-   ##
==========================================
- Coverage   97.89%   95.72%   -2.17%
==========================================
  Files          27       26       -1
  Lines         808      796      -12
==========================================
- Hits          791      762      -29
- Misses         17       34      +17

Impacted Files
Coverage Δ

accounts/views.py
67.56% <7.69%> (-32.44%)
:arrow_down:

boards/views.py
94.31% <0%> (-5.69%)
:arrow_down:

Continue to review full report at Codecov.

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


MAINTENANCE STATUS

is this still maintained?

I don't think so, last commits were my merged PRs and it was quiet some time ago.

hi @vv9k, I landed on there repo from docker docs which mentions shiplift as one of the unofficial docker sdks for rust. Thanks a lot for recommending bollard, it saved me a ton of time!
I'd like to make few changes so that people like me don't have to hunt for what they are looking for.

Update Bollard as a replacement to shiplift on official docker docs. (I'm currently working on creating an issue).
Ask @softprops to give up maintainer-ship of this project or archive it with a note forwarding users to bollard or docker-api.