Remove beacon_block_root field from ShardBlob

Follow up to PR #2590
Since the order of data of an L2 getting into the shard-data layer doesn't matter it makes sense to remove beacon_block_root field from the ShardBlob
Some comments from @protolambda

L2s will still need some kind of anchoring, but if it's part of the L2 validation rules, and respected in fraud proof in rollup case (i.e. bad beacon block root in data is not slashable, just not a useful block), then it's not necessary in protocol layer case
And fee validation is w.r.t. the estimate block it's going to be included in, not the anchor, so it's fine there
Same applies to shard proposer index
The anchor could give a hint of which branch to look at, but ultimately it must be valid and should be included in the canonical chain

I love deleting code! 🙌

Oh yeah!


cromwell-genomics: "caller does not have permission, forbidden" when deploying outside an organization

What are you trying to accomplish?
I am deploying into an existing project.
tfvars:
billing_account_id = "<BILLING-ACCOUNT>"
project_name       = "<PROJECT>"
create_project     = false
organization_id    = null

For organization ID, I also tried "" with the same result.
What challenge are you running into?
I see this error, despite the fact that I am not running inside an organization.
google_project_organization_policy.shielded_vm_policy[0]: Creating...
google_project_organization_policy.restrict_vpc_peering_policy[0]: Creating...
google_project_organization_policy.trustedimage_project_policy[0]: Creating...
╷
│ Error: googleapi: Error 403: The caller does not have permission, forbidden
│
│   with google_project_organization_policy.restrict_vpc_peering_policy[0],
│   on orgpolicy.tf line 33, in resource "google_project_organization_policy" "restrict_vpc_peering_policy":
│   33: resource "google_project_organization_policy" "restrict_vpc_peering_policy" {
│
╵
╷
│ Error: googleapi: Error 403: The caller does not have permission, forbidden
│
│   with google_project_organization_policy.shielded_vm_policy[0],
│   on orgpolicy.tf line 50, in resource "google_project_organization_policy" "shielded_vm_policy":
│   50: resource "google_project_organization_policy" "shielded_vm_policy" {
│
╵
╷
│ Error: googleapi: Error 403: The caller does not have permission, forbidden
│
│   with google_project_organization_policy.trustedimage_project_policy[0],
│   on orgpolicy.tf line 63, in resource "google_project_organization_policy" "trustedimage_project_policy":
│   63: resource "google_project_organization_policy" "trustedimage_project_policy" {
│
╵

What have your tried so far?
See above.

Thank you for reaching out @seandavi !
As you are spinning up the module in the project with no parent (Organization or Folder) you will also need to set below Org Policy setting variables to false in your tfvars. This is documented here.
set_restrict_vpc_peering_policy = false
set_external_ip_policy          = false
set_shielded_vm_policy          = false
set_trustedimage_project_policy = false

Try out the deployment with the above variables set and please feel free to reach out if you run into any other issues or have any additional questions.

Thanks, @guptamukul-google. Once you gave me the context for that documentation section, it became obvious. Apologies for the noise. And thanks for taking the time to build and maintain this repo. It saves us (researchers) a very significant amount of work!


Docs: Profiling a backend plugin

What this PR does / why we need it:
Document how to profile a backend plugin.
Which issue(s) this PR fixes:
Closes #958
Related to https://github.com/grafana/grafana/pull/90048 and https://github.com/grafana/grafana-plugin-sdk-go/pull/1025
Special notes for your reviewer:
Should probably add the configuration details to https://grafana.com/docs/grafana/latest/setup-grafana/configure-grafana/#pluginplugin_id instead of here?

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

@josmperez feel free to review/take over this since I'm going to be off for 4 weeks after tomorrow.

@josmperez feel free to review/take over this since I'm going to be off for 4 weeks after tomorrow.

Done. I hope you get a chance to take a look at my commits before you go.


fix(starr): DTS-X CF mismatching

Pull Request
Purpose
Fix the DTS X CF mismatching and not matching on various different naming schemes.
Approach
Update the regex to more accurately match DTS X.
Requirements

[x] These changes meet the standards for contributing.
[x] I have read the code of conduct.

does (?![-_. ]?(26[456]) need to cover HEVC AVC ect?

hmm not sure tbh, never seen HEVC or AVC after the audio codec

does (?![-_. ]?(26[456]) need to cover HEVC AVC ect?

hmm not sure tbh, never seen HEVC or AVC after the audio codec

search for "DTS HEVC" on bhd yeilds 110 pages.

does (?![-_. ]?(26[456]) need to cover HEVC AVC ect?

hmm not sure tbh, never seen HEVC or AVC after the audio codec

search for "DTS HEVC" on bhd yeilds 110 pages.

yes but not directly after, which would be the problem here

don't we need a updated regex example for future reference, and testing?


Provide keyboard shortcut to switch between servers.

@geeeeeeeeek what keys are you using?
CC @synicalsyntax @lonerz, we will probably want to figure out a way to document the hotkey(s) only available in the desktop app (like switching organization).

@timabbott It's displayed in the sidebar. CmdOrCtrl+${tabIndex} are used.

@akashnimare @timabbott Closed since changes in this PR is part of #202.

I feel like those keyboard shortcuts have maybe too must visual weight in the sidebar; maybe we should use a lighter color or make them only visible on hover, or something?

@timabbott This is how Slack looks like.. Maybe I can try a lighter color.


vs2015 compile error related question

Is there any way to build walnut in vs2015?
C3249: illegal statement or sub-expression for 'constexpr' function occurs in big_uint_word.h

Walnut is written in C++14. It appears that vs2015 does not work because it does not have full C++14 support for constexpr.
The missing feature is listed as "extended constexpr" on https://devblogs.microsoft.com/cppblog/c111417-features-in-vs-2015-rtm/.


add napari plugin

This adds the initial sample data plugin for the hiv dataset.
I put the sample data function in the same file as the dataset. I think that makes sense so that everything related to a dataset is in a single file.

Loading sample data from a cached image!
https://user-images.githubusercontent.com/1120672/206909850-dd6e9260-695b-4b6c-bf52-bd76ce985ae7.mov

Codecov Report

Merging #4 (da0b94d) into main (f3f5f72) will decrease coverage by 1.77%.
The diff coverage is 25.00%.

@@            Coverage Diff             @@
##             main       #4      +/-   ##
==========================================
- Coverage   94.07%   92.30%   -1.78%
==========================================
  Files           9        9
  Lines         152      156       +4
==========================================
+ Hits          143      144       +1
- Misses          9       12       +3

Impacted Files
Coverage Δ

src/cryo_et_sample_data/_hiv.py
62.50% <25.00%> (-37.50%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

This is great! One thing I'm not sure about: as you know I wanted to be able to use these through https://github.com/brisvag/blik for easy testing/showcase. Is there a way to use a specific plugin to read the sample data?

I'm not sure what you mean @brisvag - having this plugin installed will make the sample data available from the sample data menu, if you add it as a dep you should be good?

If I understand correctly, the way sample data works is that it simply returns a pre-made napari layer, so it won't be read by a specific reader. Or am I misunderstanding? If that's the case, it won't be compatible with blik, cause the scale won't be set correctly, and it won't have the metadata necessary to know which experiment_id it belongs to.

forward ref fixed and added a tqdm dep which is required for running the example - will merge when tests pass

ah! there are two layers to this package - non napari and napari, you can depend on this, get the data saved on disk and access it directly from the hiv instance of the dataset... check the example for how :)

Awesome! However, installing the package will show the dataset in napari sample data menu, so all I can do from blik is "double it" and have another menu entry :/

Yeah not really sure what to suggest there...

Anyways, it works for now (and it specifies which plugin it comes from, so that's at least distinguishable). Only thing is that I need to use _get_data() (so I can just pass the path to the cryohub reader), which is private here, so it would be nice to expose that.


Add Image metadata to all pages.

Feel free to close this once it's done.

Accessories will be done by import

OK, closing.


Local Leader keybindings not detect when entering buffer for the first time

Thanks for a great plugin, it is proving very helpful.
Not sure if this is a bug or a feature. Vimtex uses <localleader> for most of it's bindings and are buffer specific. When in a non-TEX buffer, <localleader> does nothing, which is correct because there are no keybindings set for it. When you load a
TEX file <localleader> does nothing even though there are bindings for <localleader>. If you then use any other WhichKey trigger, the bindings are added and you can then use <localleader> in the TEX buffer. The <localleader> trigger is correctly not active in non-TEX buffers.
Is there a command that can be trigger upon creation of TEX buffers so WhichKey will setup the bindings?
This is similar to the closed issue 35

If I understand correctly, Vimtex creates buffer-local mappings for tex buffers. Those mappings work as expected, but don't show up in WhichKey? Did you register any labels in WhichKey for those mappings?

Thank you for the quick reply.
Vimtex as far as I can tell is creating the buffer-local mappings. But these mappings are not working until you trigger WhichKey with a different trigger (, g etc). From then on in the TEX buffer everything works.
I have not registered any labels for WhichKey for those mappings.
In my setup the only plugin that is using  is Vimtex.

That is really odd, since whichkey has nothing to do with vimtex. Vimtex keybindings should work regardless of whichkey.
Do you change your <localleader> key in the file that has the config for whichkey by any chance?

I have tried both changing the <localleader> to ";" and leaving it to the default "\".
I think I know why this is happening and I should of mentioned this at the beginning, but I did not realise this. I am using the LunarVim config, which I now understand delays loading the plugins until they are needed. So when WhichKey is configured, VimTex is not loaded yet, only when a TEX beffer is opened for the first time, VimTex is loaded. Please accept my apologies for me missing this.
So really my question is, is there anything I can call after the TEX buffer has loaded to get WhichKey to configure the bindings?

Best way would be to register the key bindings to whichkey from inside the vimtex config

Thank you, I will close this issue, unless you have objections.


Unique signature indices

This PR adds the concept of unique signature indices to the Module struct in wasmtime-environ. Before, we were doing the dedup'ing in crates/obj/src/context. This moves the work up a little, and addresses what was a TODO left in crates/environ/src/module_environ.rs.

Can you say more about the motivation for deduplicating signatures?
[...] Are there runtime reasons for wanting to ensure a lack of duplicates?

I would like to try to start integrating lucet into wasmtime. In order to get there, I would like lucet to eventually use wasmtime's definition of a wasm module , which looks fairly similar to what we have in lucet.
Currently, lucet deduplicates both function and signature indices. It would be nice to hang onto these optimizations, so this is a small port of that logic to wasmtime.
As far as reasons to explicitly ensure a lack of duplicates, we would like to gracefully handle wasm modules that are not optimized. Using unique indices for functions and signatures also helped fix some other bugs in lucet related to duplicate imports and indirect calls.
Admittedly I am newer to wasmtime's codebase, so feel free to let me know if this doesn't make sense to also have in wasmtime. My guess was that because signature indices were already being deduped when emitting an object file, it couldn't hurt to deduplicate earlier as well.

One of the reasons this is tricky is that Wasmtime does actually deduplicate signatures, but it does so at the level of the wasm store, rather than the wasm module. This allows it to support indirect calls across instance boundaries. So the second issue you linked to above, about indirect calls, is already fixed, just in a different way.
The other issue seems to be a case of some things deduplicating and not others. It's important to do things consistently, but it seems like we could go either way.
So, is it worthwhile to deduplicate signatures at the module level? It would make some tables smaller in some cases, but in my experience those tables aren't that big and don't have a lot of duplication in them. And it would make debugging a little more complex, because it's harder to see the correspondences between the in-memory Module and the actual module file. So my sense is that we're not ready to be doing these kinds of optimizations, at least without more evidence that they're important.
I am, of course, open to discussing it though.

I ran across this today and this is pretty old at this point but I believe that the underlying feature here is actually implemented in Wasmtime nowadays already too. The main motivator was module linking, and I never got around to coming here and seeing this!


Qualifiers Ordering

Hi again!
After #52, there seems to be a "bug" about the ordering of the qualifiers.
The code says:
// Qualifiers is a slice of key=value pairs, with order preserved as it appears
// in the package URL.

However, with the switch to the url.URL type, when encoding the qualifiers they actually get ordered lexicographically.
Now I've started to wonder what the "correct" behaviour for this is. The PURL Spec even says:

If the qualifiers are not empty and not composed only of key/value pairs where the value is empty:
...

sort this list of qualifier strings lexicographically
...

So admittedly, according to the spec, the "new" behaviour is correct.
Should I submit a PR to remove the comment that the order is being preserved? I'm wondering if this should be considered a breaking change.
Or do you have an opinion / better idea on what to do here?
Thanks!

I'm just piling another small issue on top: #52 starts making use of JoinPath, which I've just noticed has only been added with Go 1.19. The go.mod file still only requires Go 1.17, so this just broke a build for me where a tool is using this library with Go 1.18...
I'd suggest to bump that version as well, or replace the usage of JoinPath with it's implementation:
	url, err := Parse(base)
	if err != nil {
		return
	}
	result = url.JoinPath(elem...).String()
	return

Again, happy to open a PR for both of these issues!

Should I submit a PR to remove the comment that the order is being preserved? I'm wondering if this should be considered a breaking change.

Yes please. We should strictly follow the PURL spec and everything that differs, is clearly wrong.

I'm just piling another small issue on top: https://github.com/package-url/packageurl-go/pull/52 starts making use of JoinPath, which I've just noticed has only been added with Go 1.19. The go.mod file still only requires Go 1.17, so this just broke a build for me where a tool is using this library with Go 1.18...

PRs are welcome of course :)

Oh sorry, I hope your recovery is going well! 🍀
Alright, I've opened #56 for this.


update: add a way to retrieve plugin framework's api version; plus add semver check when loading new plugin

What type of PR is this?

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

/kind feature
Any specific area of the project related to this PR?
/area libscap
/area libsinsp
What this PR does / why we need it:
The PR exposes 3 new methods to fetch framework's plugin api version, at scap level with: scap_get_plugin_api_version and at sinsp level with: get_plugin_api_version and get_plugin_api_version_str.
Moreover, it introduces a proper semver check on required plugin api version when loading a plugin.
Which issue(s) this PR fixes:
Fixes #146
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
new: added scap_get_plugin_api_version() plus sinsp get_plugin_api_version() and get_plugin_api_version_str() to fetch framework's plugin api version.
new: properly semver check loaded plugins required api version.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: FedeDP
To complete the pull request process, please assign leogr after the PR has been reviewed.
You can assign the PR to them by writing /assign @leogr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

Hi @FedeDP. Thanks for your PR.
I'm waiting for a falcosecurity member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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

/ok-to-test

@gnosek i agree; but right now your PR is strictly connected to the PPM_API_VERSION meaning; if we could decouple your PR from driver API only, i am super happy to wait for it!
Eg: renaming PPM_API_VERSION macros to something less specific, and changing
bool scap_is_api_compatible(unsigned long probe_api_version, unsigned long required_api_version) signature to eg:
bool scap_is_api_compatible(unsigned long internal_version, unsigned long required_api_version)
What do you think?

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

Needs approval from an approver in each of these files:

OWNERS

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

@gnosek i decided to follow @mstemm  suggestion and put everything in libsinsp; i do not use any of your macro anymore :)

Welp, that means we'll have duplicated code. Not the first instance, nor probably the last.

Welp, that means we'll have duplicated code. Not the first instance, nor probably the last.

Mmh i guess so; well the only duplicated code is the actual sinsp_plugin::version::check() method.
If scap exposes a semver.h header with a semver_check(mine, yours) API, we could both call that.
This can be done in a future PR i guess.

LGTM label has been added.  Git tree hash: 54a842986adf4b553f2fc6e7d9bfa6e23d59e98e

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

Needs approval from an approver in each of these files:

OWNERS [leogr]

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


Athenz UI build forced to stop when using Screwdriver.cd

By default, Jest runs tests in 64 workers, which can sometimes consume too much of the resources in the Screwdriver.cd execution containers, leading to incomplete tests.
https://cd.screwdriver.cd/pipelines/6606/builds/926683/steps/build

I suggest using the --maxWorkers option to limit the number of parallel processes. In our environment, setting --maxWorkers=8 has proven to stabilize the builds on Screwdriver.cd.
https://github.com/AthenZ/athenz/blob/073a1741ed7bfd09ab5b1ba2c5733223ab4ffca1/ui/package.json#L29

I truly appreciate your assistance with the issue that I raised.

Thank you for reporting and providing a solution!


RKE2 and K3S - KDM Update for K8s April 2024 patch release for Rancher 2.7

KDM Updates

New Kubernetes Version
Min Rancher Version
Max Rancher Version

v1.27.13+rke2r1
v2.7.11-alpha1
v2.8.99

v1.27.13+k3s1
v2.7.11-alpha1
v2.8.99

KDM Branch
dev-v2.7
Chart Changelog

Chart Name
New Version
Affected Kubernetes Version(s)

TBD
Argument Changelog

Argument Name
Affected Kubernetes Version(s)

TBD
Additional Notes

K3S - v1.27.13-rc2+k3s1, Rancher v2.7.12

K3S - v1.27.13-rc2+k3s1 and v1.28.9-rc2+k3s1, Rancher v2.8.3

KDM has been merged and this is validated as per the screenshots above. It is known that during the "rc" phase, it shows as "experimental" but with the non-rc versions, it does not show the "experimental" element in the UI.


Update Kelly Cason Canvas App Components to version 1.0.1

Uploaded new .zip file for the Kelly Cason Component Library 1.0.1 and updated the readme to include new solution file link

@kellycason Excellent update for our repo! Merging. Thank you!


panic: Success

Hello,
Elementum appears not to be working anymore on CoreELEC 19.2-Matrix_rc2.
It was working fine until not long ago (i know, don't we all say that).
I've enabled debug logging, and all i can see in the logs that looks relevant is this:

2021-07-30 00:01:25.379 T:28212 WARNING : [plugin.video.elementum] INFO  bittorrent   ▶ AddTorrent       .[0mSetting sequential download to: true
2021-07-30 00:01:25.379 T:28212 WARNING : [plugin.video.elementum] INFO  bittorrent   ▶ AddTorrent       .[0mAdding new torrent item with url: /storage/.kodi/temp/elementum_torrents/7bec122ce4dd8b6d9540
e80e8f26fe542ee44893.torrent
2021-07-30 00:01:25.379 T:28212 WARNING : [plugin.video.elementum] INFO  bittorrent   ▶ NewTorrent       .[0mAdding torrent with storage: File
2021-07-30 00:01:25.379 T:28212 WARNING : [plugin.video.elementum] INFO  bittorrent   ▶ loadTorrentFiles  .[0mLoading torrent file f52012e3d76c81b6ecf505cc04dfee6b76b0f6bc.torrent
2021-07-30 00:01:25.380 T:28212 WARNING : [plugin.video.elementum] INFO  bittorrent   ▶ AddTorrent       .[0mAdding torrent from /storage/.kodi/temp/elementum_torrents/f52012e3d76c81b6ecf505cc04dfee6b76
b0f6bc.torrent
2021-07-30 00:01:25.380 T:28212 WARNING : [plugin.video.elementum] panic: Success
2021-07-30 00:01:25.383 T:28140   ERROR : CCurlFile::FillBuffer - Failed: Server returned nothing (no headers, no data)(52)
2021-07-30 00:01:25.383 T:28140   ERROR : CCurlFile::Open failed with code 0 for http://<IP_ADDRESS>:65220/repository/elgatito/plugin.video.elementum/addons.xml.md5:
2021-07-30 00:01:25.383 T:28140   ERROR : CFileCache::Open - http://<IP_ADDRESS>:65220/repository/elgatito/plugin.video.elementum/addons.xml.md5 failed to open
2021-07-30 00:01:25.383 T:28140   ERROR : CRepository: failed read 'http://<IP_ADDRESS>:65220/repository/elgatito/plugin.video.elementum/addons.xml.md5'
2021-07-30 00:01:25.383 T:28212 WARNING : [plugin.video.elementum]
2021-07-30 00:01:25.384 T:28212 WARNING : [plugin.video.elementum] System information: linux_armv7
2021-07-30 00:01:25.385 T:28212 WARNING : [plugin.video.elementum] Kodi build version: 19.1 (19.1.0) Git:fb3ff50005b8afdec70f9e53a4d87504a4850d55
2021-07-30 00:01:25.385 T:28212 WARNING : [plugin.video.elementum] OS type: Linux
2021-07-30 00:01:25.386 T:28212 WARNING : [plugin.video.elementum] uname: uname_result(system='Linux', node='kodisambard', release='4.9.113', version='#1 SMP PREEMPT Sun Jun 6 11:49:21 CEST 2021', machine
='armv7l', processor='')
2021-07-30 00:01:25.602 T:28143   ERROR : CCurlFile::Open failed with code 404 for https://raw.githubusercontent.com/kodinerds/repo/master/addons.xml.md5:
2021-07-30 00:01:25.602 T:28143   ERROR : CFileCache::Open - https://raw.githubusercontent.com/kodinerds/repo/master/addons.xml.md5 failed to open
2021-07-30 00:01:25.602 T:28143   ERROR : CRepository: failed read 'https://raw.githubusercontent.com/kodinerds/repo/master/addons.xml.md5'
2021-07-30 00:01:26.128 T:28140 WARNING : Repository add-on repository.elementum uses plain HTTP for add-on downloads in path http://<IP_ADDRESS>:65220/repository/elgatito/ - this is insecure and will make y
our Kodi installation vulnerable to attacks if enabled!
2021-07-30 00:01:27.328 T:28546    INFO : Skipped 2 duplicate messages..
2021-07-30 00:01:27.328 T:28546    INFO : initializing python engine.
2021-07-30 00:01:29.351 T:28546    INFO : CPythonInvoker(21, /storage/.kodi/addons/script.embuary.info/default.py): script successfully run
2021-07-30 00:01:30.476 T:28212 WARNING : [plugin.video.elementum] elementumd: starting elementumd
2021-07-30 00:01:30.478 T:28181    INFO : JSONRPC Server: New connection added
2021-07-30 00:01:30.479 T:28181    INFO : JSONRPC Server: Disconnection detected
2021-07-30 00:01:30.479 T:28212 WARNING : [plugin.video.elementum] Kodi's JSON-RPC service is available, starting up...
2021-07-30 00:01:30.526 T:28546    INFO : Python interpreter stopped
2021-07-30 00:01:30.530 T:28212 WARNING : [plugin.video.elementum] Binary detection. Source: /storage/.kodi/addons/plugin.video.elementum/resources/bin/linux_armv7/elementum, Destination: /storage/.kodi/u
serdata/addon_data/plugin.video.elementum/bin/linux_armv7/elementum
2021-07-30 00:01:30.531 T:28212 WARNING : [plugin.video.elementum] Deleting stale files set()
2021-07-30 00:01:30.532 T:28212 WARNING : [plugin.video.elementum] Binary detection: [ Source: /storage/.kodi/addons/plugin.video.elementum/resources/bin/linux_armv7/elementum, Destination: /storage/.kodi
/userdata/addon_data/plugin.video.elementum/bin/linux_armv7/elementum ]
2021-07-30 00:01:30.532 T:28212 WARNING : [plugin.video.elementum] Binary dir: /storage/.kodi/userdata/addon_data/plugin.video.elementum/bin/linux_armv7, item: /storage/.kodi/userdata/addon_data/plugin.vi
deo.elementum/bin/linux_armv7/elementum
2021-07-30 00:01:30.532 T:28212   ERROR : [plugin.video.elementum] Existing process found from lockfile, killing...

Eventually, we reach something ilke

2021-07-30 00:38:33.546 T:32054   DEBUG : [plugin.video.elementum] elementumd: no attempts left

So it looks like it loads, goes through most of startup, then dies (panic: Success), then tries to load a few more times until giving up.
This, earlier in the log, may also be useful:

2021-07-30 00:38:04.183 T:31993   DEBUG <CAddonSettings[plugin.video.elementum]>: trying to load setting definitions from old format...

I realised that debug logging is only enabled for Kodi, not Elementum. I will get a log with that enabled too, tomorrow.
Steps to Reproduce (for bugs)
Honestly, no idea. I wish i could say.
Context
I believe Elementum was recently updated to 0.1.83. (the files in .kodi/addons/plugin.video.elementum are dated from the 18th of July)
Your Environment

Version used: 0.1.83

Environment name and version: 19.1.0

Operating System and version: CoreELEC 19.2-Matrix_rc2 on arm v7 (ODROID N2)

Link to Kodi debug log: i can share a full debug log if necessary

@axelsimon That is probably an error from libtorrent. Elementum Debug log needed to see the problem.

@axelsimon Closing because of a missing log.

Hi @elgatito, sorry for not providing the log in time. I completely understand you closing the issue.
Here's a quick summary of what happened in the past month.

I eventually moved .kodi/userdata/addon_data/plugin.video.elementum/ to a backup directory and restarted Kodi: Elementum came back up fine.
Then my Kodi system (CoreELEC 19.2-Matrix_rc2, rc3 after August 5 or so) crashed, and the same problem happened: Elementum tries to start multiple times and eventually gives up.
I've hade multiple crashes since, and each time Elemetum fails to start after. I've moved the corrupted elemenum add-on directory out of the way each time, and i now have a collection of 5 crashed Elementum add-on directories (and multiple .parts files in my download path).

I currently have debug logs enabled but right now, as Elementum is working, the log shows nothing helpful. I will restore the original corrupted dir and get the Kodi debug log, so this can be investigated.

You can try to run the binary manually from ssh.
/storage/.kodi/addons/plugin.video.elementum/resources/bin/linux_armv7/elementum

will turning on libtorrent logs give more info? elementum log messages mystically end.

They end because most probably process will killed.

I was able to look into this again tonight.
After a chmod +x on the elementum binary, I was able to start it manually and discovered that it crashes with the Panic Success message after trying (and failing) to load a torrent from .kodi/temp/elementum_torrents/ (or maybe .kodi/temp/elementum/ wasn't able to capture the log.
I've removed the file that was causing elementum to panic: Success and it started fine after. If this happens again, i'll check if it's the same problem. What is strange is that while i removed the .kodi/userdata/addon_data/plugin.video.elementum directory after Elementum/Kodi crashes (which would make Elementum start again), until today i'd never removed any saved torrent file. So something in the plugin settings would change and prevent Elementum from starting.
@elgatito Does this help? Could you reopen the issue?


Use early return, set satisfies for exported handler

Summary
A few "cleanup" items for the typescript example here that (I believe) make the code a bit simpler and idiomatic as well as properly typing the returned fetch handler (like how it is done with wrangler generated code)
Formatted with Prettier default formatting (which I believe is the convention)
Screenshots (optional)

Documentation checklist

[x] The documentation style guide has been adhered to.
[x] If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
 All PRs prior to August 12 need to be reworked due to the platform migration to Astro.


Generic login recipe

Can we review our login recipes to provide something generic to be used across platforms/systems?
This is the existing generic version:
https://github.com/jiscdev/xapi/blob/master/generic/login.md
I want to be clear on its uses and ensure it can be applied more broadly across different systems/platforms and have these mapping to appropriate activity types.
Currently we have:
Mobile - https://github.com/jiscdev/xapi/blob/master/recipes/studyapps/app-login.md
VLE - https://github.com/jiscdev/xapi/blob/master/recipes/vle/vle-login.md
And I am merging in the now closed PC Login issue into this new ticket:
https://github.com/jiscdev/xapi/issues/135
Can we also consider the overlap between logins and 'accessed service' which is effectively authentications into external resources (generally published and content aggregators).

https://github.com/jiscdev/xapi/pull/341


Persistent text labels

When "label" is turned on in the UI, the interactive label text box follows the mouse showing information about each annotation element the mouse is pointing to (see image). Sometimes it is desirable to see all labels at once (just the label of each element, without the other info) as copy-able text (geojs allows this, although not copy-able) or at least to be able to use some keyboard shortcut to "de-couple" the current label from mouse movement so that its information can be copied.
Why is this relevant? In my project I'm creating a gallery of images and annotations (using large image and/or VIPS) for rapid review by the pathologist, and if they'd like to further examine a specific field, they should be able to either copy-paste or directly click the label URL, which points to the source slide from which the field came. Currently, this is not possible.

@manthey Is this a simple thing to do or is it more of a "need to edit a whole bunch of files and parameters here and there" kind of enhancement?

There are two different things here: sticky labels that stay present despite mouse movement so you can copy from them, and showing labels on all elements.
Showing labels as all elements via the "popover" style won't work (or at least not well) if there are more than a few hundred annotations.  We could have a threshold where under that number would be allowed.  This would probably be implemented as another checkbox ("Labels" could be used for this and ""Hover Info" for the existing behavior, perhaps).  Showing all labels as non-selectable text could work (even with a huge number of elements).
It would be a small work to make the Labels check box have three states (rather than off/on, off/on/sticky).  The sticky mode would leave the box open (e.g., when it vanishes now it would just stay with whatever information it had).  You could then select the text within the box.

It would be a small work to make the Labels check box have three states (rather than off/on, off/on/sticky). The sticky mode would leave the box open (e.g., when it vanishes now it would just stay with whatever information it had). You could then select the text within the box.

Thank you so much for your help David. Yes indeed, that simple option would be ideal!! Maybe when the sticky mode is activates the label only shows when the user wants it to, say when they press control then double left-click the annotation, but it says on unless the user repeats the action for the same annotation or un-checks the "label" checkbox. Does that sound reasonable


[ Flatten ] backwarding

This PR includes back propagation of Flatten Layer.
. backwarding Flatten Layer.
. batch(), channel(), width(), height(), setDim() of tensor
. unit test of flatten layer
Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: jijoong.moon<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #186. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/186-202006181109190.1912829875946-1c63281a2a2b5a4e091d6c3b38d927adc3d38775/.


Check for dodgy multiple inheritance of cdef class

Closes https://github.com/cython/cython/issues/4350 (by raising
a runtime error on the cases that will fail).
Some notes:

The check works all the time in Cython code, but in Python code,
it only works on Python 3.6+. I think that's OK for something
that's designed to help users not to shoot themselves in the
foot rather than a core feature. Supporting earlier versions
would probably be more intrusive.

The test case is in "errors" rather than "run" even though its
checking for runtime errors. I decided that was the most
suitable place, but maybe I'm wrong...

It's interesting that Python is more lenient on multiple
inheritence of cdef classes that Cython would be if "C" were
defined as cdef classes

Some of these errors could be detected at compile-time in
principle too. This seems like a lot of effort given that we'll
need the runtime check anyway. Thus I haven't done it.

On the "all" tests:

TypeError: Invalid inheritance from cdef class SkipDeclarations: PxdPostParse.base must be a subclass of SkipDeclarations. (PxdPostParse.base == CythonTransform)

This is either an error in Cython or it should be explicitly allowed (because SkipDeclarations doesn't require any custom tp_new or tp_dealloc). Not sure for now

Closing and reopening to see if this works now

I'm marking this as "read for review" since it no longer breaks Cython compilation.
I think if we do want to do this then we should do it in Cython 3 because it likely breaks a small amount of existing code. I'd argue the existing code was very very close to being broken already. But it's possible we could make less drastic versions of this check.


Mesh Extraction: out['num_samples_full'] is 0

Thank you so much for this great work and for putting the code up!
When running the mesh extraction (under instant-nsr-pl) the out['num_samples_full'] on this line appears to be 0 (commenting it out also results on nan losses).
I'm testing the default owl example and the results from Wonder3D work just fine (and are placed in the right folder etc) so I was wondering if you have any insights on why would this be the case?
Thanks again!

i have meet the same problem and finally fix it.
the problem is something incompatible with  pytorh_lightning on windows
i have goto the original instant-nsr-pl github repository and found there exist some issues with similar problem , and the author has publish a branch named "fix-win-data" for these problem , then i compare the changes form:
https://github.com/bennyguo/instant-nsr-pl/compare/main...fix-data-win
and then i remove all  ".to(self.rank)" and "device=self.dataset.all_images.device" from the code, and add ".to(self.device)" to the data that need to send to gpu.
and final , it work


[Diagnostic] Improve diagnostics for situations with ambiguity caused by conformance requirements

Adjust diagnoseAmbiguity to use a local slice of overloads

Solver re-opens stdlib array and dictionary types to maintain subtyping which means
that in diagnostics mode it's possible to produce two solutions that have a different
number of type variables but are otherwise equivalent. Such cases should be diagnosed
as if there was just one viable solution.

Don't increase a score for conditional requirement failures

Remove an artificial rule that increased score of solutions with conditional requirement
failures, assuming that such failures always lead to member unviability, which is not
the case.
This also helps code completion to produce a better match set when optional types
are involved.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 66fbdce2f8dbf6a068d19ffb14878f86d0f93ed0

@swift-ci please test Linux platform

@swift-ci please build Windows platform

@swift-ci please test Windows platform

@swift-ci please test Windows platform

@swift-ci please test Windows platform


Static file generation

Generate JSON files for all courses per season

Resolved in https://github.com/coursetable/coursetable/pull/180


onChange() where mode:multiple gets called twice

The onChange() event gets called twice when you unselect a date.
https://codepen.io/tako1337/pen/wZqbeL
Your Environment

flatpickr version used: 4.5.7
Browser name and version: Chrome 73
OS and version: Windows 10

This issue and #1748 are very much related. This happens because updateValue() is called in selectDate(). Since the selectedDates array has a length of 0, clear() is called. clear() calls a second triggerEvent("onChange") and sets latestSelectedDateObj to undefined.

I'm pretty sure line 2594 in src/index.tst, just isn't neccessary. I've commented this line out in a local override in my browser and flatpickr seems to still work perfectly fine, without duplicate onChange events, and latestSelectDateObj is not null when deselecting.
    if (self.selectedDates.length === 0) return self.clear(triggerChange);

@chmln
@viorelsfetea (you're pretty active, so I'd like your input)
Does this sound like a solid excuse to remove this call to clear() in updateValue()? Not sure what else would break. Let me know and I'll submit a PR.

@chmln Can you mark this and #1748 as 'pending release'? I saw your commit here should fix this: https://github.com/flatpickr/flatpickr/commit/37cfef5cf18c8bac5fdfe3125d632b39d8fe298d

@takuy thanks for the notice and sorry for the late reply :)


Which aspect ratios we can set on cameraView?

What means which aspect ratios? You know, there is a SizeMap of picture sizes and a SizeMap of preview sizes. They both contain a key "aspectRatio" and a List value containing the available resolutions. So this is a per device requirement.


CI / CD Pipeline Setup

Be able to build a functional image after each request is pushed to the repo on branch.
Use Github Actions

@NickThorne123 Any recommendations for a decent platform that you might have played around with that we can utilise as a CICD pipeline for this project?

Hi, Not directly (as you can see from the repo), but I have used pytest in VSCode, and am aware of GitHub CI/CD.
GitHub Actions for testing Python is described here
And there's a good overview of testing here
I use Python Testing inside VSCode, as described here, which could be added to this Flask/Dash app.


Add bearer token to requests.auth?

in request.auth there is HTTPBasicAuth , HTTPProxyAuth, and HTTPDigestAuth, but no HTTPBearerAuth - for bearer authentication.
It would look something like this:
class HTTPBearerAuth(requests.auth.AuthBase):
    def __init__(self, token):
        self.token = token

    def __eq__(self, other):
        return self.token == getattr(other, 'token', None)

    def __ne__(self, other):
        return not self == other

    def __call__(self, r):
        r.headers['Authorization'] = 'Bearer ' + self.token
        return r

Is there a reason to not add bearer auth to the codebase?

Hi @richtier thanks for opening this.

Is there a reason to not add bearer auth to the codebase?

The main reasons are the following:

because Bearer authentication is so terribly simple that it can be implemented as above easily (or even more simply, really)
because we're under a fairly strict feature-freeze and this would constitute a break of that freeze
this can be easily shipped via the requests-toolbelt for people who don't want to implement this simply

@sigmavirus24 good reasons :+1:

@sigmavirus24, yes, it is simple but will be used in many projects. In my experience - it is most popular auth method.

But why I need to manually migrate that part of code from project to project and violate DRY principle?
Can you add/plan it to the next feature-freeze?
As I don't use (and currently don't plan to use) requests-toolbelt - why I should install it, if all similar auth types are in requests?

Thanks in advance.

In my experience - it is most popular auth method.

Your experience doesn't match mine. Anecdotal data is useless.

Can you add/plan it to the next feature-freeze?

No. This project is in perpetual feature-freeze. There is a high bar for new features, this does not even come close to it.

As I don't use (and currently don't plan to use) requests-toolbelt - why I should install it, if all similar auth types are in requests?

There are 2 auth-types natively supported by Requests:

HTTP Digest Authentication
HTTP Basic Authentication

There are a myriad of libraries for other authentication types (oauth, kerberos, ntlm, and so many more). The toolbelt, includes other auth mechanisms that are helpers for more basic concerns.

Please reconsider this decision.
It's about having a consistent API and symmetric API.
Like e.g. my thinking was:

I need bearer auth
let's look at requests.readthedocs.io. Ok understood: authentication looks like  requests.get(url, auth=<auth-type>(...))
search for Bearer on that page.
Search again for Bearer on that page.
Last resort: Google: https://www.google.com/search?q=python+requests+bearer
tying to understand https://stackoverflow.com/questions/45868120/python-post-request-with-bearer-token?rq=1
"why is this so much more complicated????"

Which means, by omitting bearer authentication, cause it is so simple, you in fact made bearer authentication much more complicated than other authentication schemes. Unfortunately.

Which means, by omitting bearer authentication, cause it is so simple, you in fact made bearer authentication much more complicated than other authentication schemes.

I guess that makes OAuth impossible? This logic makes no sense. BasicAuth and DigestAuth are the two most common auth types (or were over 10 years ago). Given that most of the auth handlers just update headers and you can do that yourself here, I don't understand why this is more complicated to you. The toolbelt exists for just such "dead-simple and borderline popular" options so that folks don't have to reimplement it themselves but no one has sent an implementation and I don't care enough to do it myself.
Also, the library is in feature-freeze. So new features are not accepted no matter how complicated you think this is or how common one person thinks this is.
If you want a library that will accept any old feature request without regard to the long-term quality of the software itself, it's maintainability, or the effect all of that has on the maintainer(s) still working on the project, maybe find a different HTTP client. There's tonnes at this point, some might even be of better quality.
I no longer represent this project though, so take all of this for whatever little you already value my opinion (given that you have thumbs-downed my comments for explaining rationale and thought it was appropriate to revive an issue that's been closed and dormant for 2 years).

Which means, by omitting bearer authentication, cause it is so simple, you in fact made bearer authentication much more complicated than other authentication schemes.

I guess that makes OAuth impossible? This logic makes no sense. BasicAuth and DigestAuth are the two most common auth types (or were over 10 years ago). Given that most of the auth handlers just update headers and you can do that yourself here, I don't understand why this is more complicated to you.

I'm not talking about the complexity of the authentication mechanism, but of the python API here. By that I think using OAuth is easier that Bearer for inexperienced users right now.

The toolbelt exists for just such "dead-simple and borderline popular" options so that folks don't have to reimplement it themselves but no one has sent an implementation and I don't care enough to do it myself.

Thank you for the hint!

Also, the library is in feature-freeze. So new features are not accepted no matter how complicated you think this is or how common one person thinks this is.

That's indeed unfortunate.

If you want a library that will accept any old feature request without regard to the long-term quality of the software itself, it's maintainability, or the effect all of that has on the maintainer(s) still working on the project, maybe find a different HTTP client. There's tonnes at this point, some might even be of better quality.
I no longer represent this project though, so take all of this for whatever little you already value my opinion

Well. Obviously, my intention was not to offend you, but provide some input why I think Bearer should be reconsidered.

... thought it was appropriate to revive an issue that's been closed and dormant for 2 years.

I for one would not be offend by someone commenting on older issues.


Incorrect mouse position due to ctx.set_pixels_per_point

Describe the bug
When setting a zoom factor with either ctx.set_pixels_per_point or ctx.set_zoom_factor the mouse position that is being "used in the GUI" doesn't match the mouse position that is shown on my monitor.
https://github.com/emilk/egui/assets/36443559/3d7ac0d6-5a3f-4199-8b8d-b63ca2ff1e57
To Reproduce

Download the eframpe template (02ee968537e783e375a0e439426518bf91e762b6)
add the following line:

impl TemplateApp {
    /// Called once before the first frame.
    pub fn new(cc: &eframe::CreationContext<'_>) -> Self {
        // This is also where you can customize the look and feel of egui using
        // `cc.egui_ctx.set_visuals` and `cc.egui_ctx.set_fonts`.
+       cc.egui_ctx.set_zoom_factor(1.5);

        // Load previous app state (if any).
        // Note that you must enable the `persistence` feature for this to work.
        if let Some(storage) = cc.storage {
            return eframe::get_value(storage, eframe::APP_KEY).unwrap_or_default();
        }

        Default::default()
    }
}

Desktop (please complete the following information):

OS: Windows 11
Browser: Chrome v121, Firefox v123

Additional context
This had been working as expected with egui/eframe 0.23

I can reproduce this, but only in the web assembly version

On web the browser should be in control of the zoom level, so that's probably why this is only a problem on web

I think #4260 fixes this. It's already released in 0.27.1


Building Entity classes from connection.entities metadata

I believe that your library assumes that Entity classes are defined separately as per the usual "TypeORM way". I'd love to have the entity classes generated however in order to act as building blocks for further "decoration" as described here
As I understand it, the connectin.entities is a map, where each key is the entityKeyName ie. the entity/class name.
If so, one could then iterate through each entity key and call a function to generate a class decorated by @Entity (or via HOF) and store them in a map. Then iterate the field metadata and decorate each Entity field/method as per the constraint directive options that is part of the field metadata generated from the GraphQL type def schema.
Then I could achieve exactly what I'm looking for, having the constraints also apply on the Entity models directly, not just the mutation resolvers, possibly using different validation frameworks if needed (via transformation/translation).
Your thoughts?

This library doesn't require you to write separate TypeORM entity classes they are auto generated as entity schema objects instead. The example shows generating and using dynamically at runtime but you could just as easily have a separate script to build those files and then reference them directly in your man server script. In the Readme there is this block of code
const connection = createConnection({     type: {YOUR_TYPE},     host: {YOUR_HOST}",     port: {YOUR_PORT},     username: {YOUR_USERNAME},     password: {YOUR_PASSWORD},     database: {YOUR_DATABASE},     entities: getEntitySchemas(jsSchema).map(schema => new EntitySchema(schema)),     synchronize: true }).then(connection => {
getEntitySchemas here takes the js object schema and builds an array of Entity schema objects. The mapping I do is just TypeORM's way to initiate the model from a schema as opposed to the classes directly. In other words the connection.entities[key] is already a key/value mapping of Entity Name to Entity instance.
I am still a little confused by what you are trying to achieve because unless you have found something I am unaware of (entirely possible the typeorm docs last i checked tended to get a bit behind) there is no TypeORM built in validation at all. So any validation done on TypeORM (outside of the context of graphql) is just user defined opt in external behavior provided by an unrelated library called "class-validation". That said to answer your actual question it would be pretty easy to follow the template metaphor instead and build out the entity classes as opposed to entity schemas. I think i mentioned yesterday that originally I had started down that path but felt that entity schemas were cleaner but switching back over should be fairly easy if you truly need it.
Alternatively is your intention is to support multiple API endpoints(like rest and graphql) and you want the automatic support for TypeORM insertions to come from non graphql endpoints like maybe rest or just internal mechanisms to your project? If so you as an alternative solution you could probably get that behavior either functionally wrapping the db mechanisms of typeorm and enforcing their use or alternatively you could probably extend EntitySchema and do the same idea enforcing built in typeorm validation in your projects. These would require you probably to work iwth the library validators.js which is the library that class-validation is built on top of since you'd be working with plain old objects not instances. Sorry just trying to understand what it is you're shooting for so throwing out ideas.

getEntitySchemas here takes the js object schema and builds an array of Entity schema objects.
Yup, this is what I figured out, but wasn't sure if this ended up as the metadata itself or was somehow transformed into Entity classes.
In other words the connection.entities[key] is already a key/value mapping of Entity Name to Entity instance.
Great! Exactly what I was looking for. That was not clear at all. This is exactly the map I wanted. But I assume you mean classes and not instances? the instances become individual rows in a table/collection of a DB.
"there is no TypeORM built in validation at all. So any validation done on TypeORM (outside of the context of graphql) is just user defined opt in external behavior provided by an unrelated library called class-validation."
Yes, I'm perfectly aware of that, but I want to cover all the bases and ideally add the same validation logic in every application layer. That way the DB is not beholden to only a specific API access, such as GraphQL, as you point out.
"it would be pretty easy to follow the template metaphor instead and build out the entity classes as opposed to entity schemas."
Yes, I would like to add a template for that as well. Like to keep all the options open.
"Alternatively is your intention is to support multiple API endpoints(like rest and graphql) and you want the automatic support for TypeORM insertions to come from non graphql endpoints like maybe rest or just internal mechanisms to your project?"
Yes, exactly what I want.
"you could probably get that behavior either functionally wrapping the db mechanisms of typeorm and enforcing their use or alternatively you could probably extend EntitySchema and do the same idea enforcing built in typeorm validation in your projects."
I want to do it in a non-intrusive way. That's why I need to build the Entity classes from the typeorm metadata or access them directly if mapping already available as hint they are.
These would require you probably to work iwth the library validators.js which is the library that class-validator is built on top of since you'd be working with plain old objects not instances.
Yup, figured that out as well. I have already extended the graphql-constraint-directive for this purpose and made it more directly accessible.
This is so I can use either these validators as described here using the same directive or alternatively via class-validator with a slight mapping/transformation.
I'm trying to set up an infrastructure to automatically build and sync most of the core application infrastructure from one source of truth, the GraphQL schema.
All in all a similar approach to TypeGraphQL just using a "GraphQL type definitions first" approach, using directives instead of decorators.
I also recently did a lot of work on graphql-faker to generate a completely mocked or fake GraphQL API backend from a GraphQL type def.
I very much appreciate that you have took the time for this dialogue over these issues. Perhaps we should continue communicating over a different channel if you are interested. What are your goals?
You seem to be going in a similar direction if I'm not mistaken?

I've now extracted the logic I wanted in graphql-typeorm-validation and removed it from my fork


Recaptcha for login to prevent bruteforce

Hello, I like the wrapper :+1:  need some help integrating with Login Form (not just register).
For it to work, I understand that the recaptcha needs to call google validation service, but when user clicks submit, its posting back to my server - so how can I get the correct validation. Or, is this auto handled?
What do I need to do to ensure the validation service will work in the login form?
Do I need to catch/wrap and route the google recaptcha check?
thanks

Thanks for using the wrapper :)
Login and register should be handled pretty similarly.
When you use reCaptcha (put Google script on the page) the recaptcha control is rendered on the page, the control communicate with Google servers automatically.
The only thing you left to do on your side is validating with Google the user response on server side.
The wrapper provide a call for that.
I hope I assisted you ^_^
קובי קדוש,
נשלח מה-iPhone שלי
ב-26 ביוני 2016, בשעה 6:15, papyr<EMAIL_ADDRESS>כתב/ה:

Hello, I like the wrapper 👍 need some help integrating with Login Form (not just register).
For it to work, I understand that the recaptcha needs to call google validation service, but when user clicks submit, its posting back to my server - so how can I get the correct validation. Or, is this auto handled?
What do I need to do to ensure the validation service will work in the login form?
Do I need to catch/wrap and route the google recaptcha check?
thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks so much for the response.
One more question, when I check google help page for ASP, it says V2 for recaptcha. Here it recommends including API script, can you tell me which scripts I should use, and which will ones I do not have to worry about the version conflicts

ReCaptcha V2 Google took a different approach, they didn't supply an SDK.
They instruct the users to include their script straight without any library.
This wrapper do all the work for you, with a simple interface allows you to use reCaptcha.
If you want to use Google instructions you can go head, there is no necessary need to you this wrapper, it exists only for your convince 😊
קובי קדוש,
נשלח מה-iPhone שלי
ב-26 ביוני 2016, בשעה 21:58, papyr<EMAIL_ADDRESS>כתב/ה:

Thanks so much for the response.
One more question, when I check google help page for ASP, it says V2 for recaptcha. Here it recommends including API script, can you tell me which scripts I should use, and which will ones I do not have to worry about the version conflicts
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi, can you please tell me which section of the web.config would I add the recaptcha

You don't have to configure in the web.config (it is just for your convenience).
I you choose to configure the keys like it's suggested by the Readme, you need to configure the keys in the  section.
Look at the link below
https://msdn.microsoft.com/en-us/library/aa903313(v=vs.71).aspx
קובי קדוש,
נשלח מה-iPhone שלי

On 2 Aug 2016, at 22:46, papyr<EMAIL_ADDRESS>wrote:
Hi, can you please tell me which section of the web.config would I add the recaptcha
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Allow extends in referencing same file

When the yaml is loaded and transformed into an map, the default value for the context is "."  https://github.com/compose-spec/compose-go/blob/5a8e67720466339ad22c8bac1249f97e0e73e831/transform/build.go#L25-L31
Currently, there is an assumption of one level when searching for the extended value from files, by skipping the extended operation.
https://github.com/compose-spec/compose-go/blob/5a8e67720466339ad22c8bac1249f97e0e73e831/loader/extends.go#L117-L138
However, the presented use case in https://github.com/docker/compose/issues/11431 looks valid and so we can't do this assumption.
Fix: https://github.com/docker/compose/issues/11431

The root cause is indeed that we apply default value while doing canonical transformation. This should be a separate step so that we can keep the data structure with "unset" value, and not infer a wrong value during extends/include processing.
While such a refactoring would make sense, a simpler approach as a quick fix is to make the Transform.Cannonical call optional (just introduce a new opts.SkipTransform)  so that when loading extends.file we keep the yaml data structure unchanged, and doing so don't set some default values)

closing as issue was fixed by https://github.com/compose-spec/compose-go/pull/558


Expand docs on modifiers

I hope this should make them more accessible to newbies (like me).

This is very helpful :+1:

Fixed and rebased.

Can we add back a note somewhere that you can write your own modifiers? This is a big reason for their use.


Remove session close exception

While performing segmentation though ADS performs segmentation it throws the following session closed exception. This quick PR aims to resolve this issue.

That's odd; this line (sess.close()) has been in the software for a very long time (a couple of years at least), and it hasn't caused an issue like yours before. Why do you think this is - is it possible it has to do to with the Keras upgrade?
@perone @alzaia I'm not as well versed in tensorflow as you both; is there any risk (or ressource-wise) to not closing the tensorflow session here?

Unless there is somewhere that we recently deleted a statement that opens a session - maybe that was in the bulk-delete that was done during the Keras transition?

Something about this solution just doesn't feel clean to me; maybe we could. take a look at a couple of the recent merges to see when this issue began.

It's true unit tests didn't catch (I don't know why) this though at the end of each travis build you could see the following  exception.

That's odd; this line (sess.close()) has been in the software for a very long time (a couple of years at least), and it hasn't caused an issue like yours before. Why do you think this is - is it possible it has to do to with the Keras upgrade?
@perone @alzaia I'm not as well versed in tensorflow as you both; is there any risk (or ressource-wise) to not closing the tensorflow session here?

When we were on TensorFlow 1.3.0 we were not encountering this exception but since when  we shifted to TensorFlow 1.13.1 this error came into picture.

Yup I just saw that while comparing Travis logs. It means that something about how tensorflow sessions are started/stopped changed; we should look into that to make sure we're doing it the proper way.

Coverage decreased (-0.009%) to 82.729% when pulling 973891305aa5a828a32b6a04034adc76143ff3ef on session_close_exception into a7da6a1e7bf56a84b917045b9cdee1b8d0d48246 on master.


issue with port 8090

how to run tasks with port 8090 now

Hi,
Can you please close this issue? As, you've already asked this in #53.

Hello,
I'm a bit embarrassed, but I have the same problem! what am I doing wrong?
Thanks for the help.

replace 8090 to 8081
On Wed, Jul 25, 2018 at 5:05 AM, Andres8427<EMAIL_ADDRESS>wrote:

Hello,
I'm a bit embarrassed, but I have the same problem! what am I doing wrong?
Thanks for the help.
[image: image]
https://user-images.githubusercontent.com/33126305/43177360-8e8223c4-8f8d-11e8-8d5f-9fdbf5754270.png
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/druid-io/docker-druid/issues/52#issuecomment-407618849,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXdEkQOzym40z8wLx4pmNVDGQUbvkO-Sks5uJ-CWgaJpZM4USNDb
.


⚠ Bofrost.de has degraded performance

In 9efa1a3, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 701 ms

Resolved: Bofrost.de performance has improved in 559b2fe after 8 minutes.


Occasional WirePattern gc test failures on CI

The WirePattern garbage collection test is failing occasionally on CI, especially on Node.js 0.12 (Travis) and on Windows. Seems like a timing issue?
Component traits WirePattern when grouping requests should collect garbage every N requests:
     AssertionError: expected [ Array(3) ] to have a length of 2 but got 3
    at Context.<anonymous> (C:\projects\noflo\spec\Helpers.coffee:1524:57)

https://ci.appveyor.com/project/bergie/noflo/build/1.0.548#L1242
cc / @trustmaster

Here's an example of the same test passing on Windows: https://ci.appveyor.com/project/bergie/noflo/build/1.0.547#L1238


Dependency problems

On a Kubuntu x64 16.04.05:
╰─$ sudo dpkg -i fancon_0.12.0_amd64.deb
dpkg: warning: downgrading fancon from 0.12.8 to 0.12.0
(Reading database ... 393708 files and directories currently installed.)
Preparing to unpack fancon_0.12.0_amd64.deb ...
Unpacking fancon (0.12.0) over (0.12.8) ...
dpkg: dependency problems prevent configuration of fancon:
 fancon depends on libboost-atomic1.62.0; however:
  Package libboost-atomic1.62.0 is not installed.
 fancon depends on libboost-chrono1.62.0; however:
  Package libboost-chrono1.62.0 is not installed.
 fancon depends on libboost-date-time1.62.0; however:
  Package libboost-date-time1.62.0 is not installed.
 fancon depends on libboost-filesystem1.62.0; however:
  Package libboost-filesystem1.62.0 is not installed.
 fancon depends on libboost-log1.62.0; however:
  Package libboost-log1.62.0 is not installed.
 fancon depends on libboost-system1.62.0; however:
  Package libboost-system1.62.0 is not installed.
 fancon depends on libboost-thread1.62.0; however:
  Package libboost-thread1.62.0 is not installed.
 fancon depends on libstdc++6 (>= 6); however:
  Version of libstdc++6:amd64 on system is 5.4.0-6ubuntu1~16.04.10.
 fancon depends on libc++-helpers; however:
  Package libc++-helpers is not installed.

dpkg: error processing package fancon (--install):
 dependency problems - leaving unconfigured
Processing triggers for systemd (229-4ubuntu21.10) ...
Processing triggers for ureadahead (0.100.0-19) ...
Errors were encountered while processing:
 fancon

Hi - I had a similar problem using  Elementary OS (another Debian disto)
Fixed it using apt --fix-broken install
Hope this helps :)

This step has been added to the installation instructions

Thanks man @hbriese!


Can the checkNullSafety method for class objects be automatically generated?

🔍 Search Terms
Can the checkNullSafety method for class objects be automatically generated to detect whether the attribute values of the runtime class object comply with the definition after empty security is enabled, such as let foo=JSON. parse (ioInput); Let ok=foo. checkNullSafety(), there is a non empty field called prop1 in the Foo class. If the prop1 obtained after JSON. parse is null or undefined, foo. checkNullSafety() will return false
✅ Viability Checklist

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
none
📃 Motivating Example
check null safety
💻 Use Cases
let foo: Foo = JSON.parse(ioInput);
if (!foo.checkNullSafety()) {
throw new Error("input is not corrent JSON string");
}

I'm not sure what you're asking for exactly but it's clearly some sort of runtime feature, which means that you should not have checked this checkbox

[x] This isn't a runtime feature

Which implies that this will be declined. TypeScript is out of the business of adding runtime functionality. If you want to see something like this happen, it needs to be implemented first in JavaScript.

I'm not sure what you're asking for exactly but it's clearly some sort of runtime feature, which means that you should not have checked this checkbox

[ ]  This isn't a runtime feature

Which implies that this will be declined. TypeScript is out of the business of adding runtime functionality. If you want to see something like this happen, it needs to be implemented first in JavaScript.
So you should close this issue. (If you don't, the TS team will almost certainly close it for you, but you can save them the effort by doing it yourself.)

This is not a runtime feature, but rather a hope that typescript can automatically generate a check for whether the property values of the class object comply with the non null/undefined definition when compiling the relevant classes after null safety is enabled

hope that typescript can automatically generate a check method

Which would be in violation of these two points:

This could be implemented without emitting different JS based on the types of the expressions
This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals


Bug: width of Dropdown.Item not expanding dynamically

Dropdown should have a min-width rather than a fixed width.
also ability to set width of dropdown (size prop) could easily be added in while doing this.

fixed now in new version


ceylon-model project

[@gavinking] Currently, to run a Ceylon application that uses reified generics or the metamodel on the JVM, the following runtime dependencies are required:

ceylon.language-1.1.0.car
com.redhat.ceylon.typechecker-1.1.0.jar
com.redhat.ceylon.compiler.java-1.1.0.jar
com.redhat.ceylon.common-1.1.0.jar
org.jboss.modules-1.3.3.Final.jar
com.redhat.ceylon.module-resolver-1.1.0.jar

On some platforms (Android), this is totally unacceptable.
We need to create a com.redhat.ceylon.model.jar that contains:

the model package that currently resides in the typechecker, and
the AbstractModelLoader and ReflectionModelLoader, along with just what they absolutely need to function in an environment without ceylon-runtime.

It would be acceptable if this new lightweight model loader is "incomplete" is certain ways. That is, it's OK if it doesn't support some modularity-related functionality, for example, package scanning, since it will likely run in a non-modular runtime. But it does need to provide support for basic reified-generics-based is tests, and basic metamodel usage, including reading annotations.
It is highly desirable that com.redhat.ceylon.model.jar has no dependencies.
I would say that this is a critical issue for the whole platform.
[Migrated from ceylon/ceylon-compiler#1763]

This was done.


Lastest Next version doesnt works with jest and next-css

Examples bug report
Example name
with-jest
Describe the bug
Conflict between webpack and next-css
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Clone next 'with-jest' example
Add "@zeit/next-css": "^0.2.0" to package json
Add

const withCSS = require('@zeit/next-css')
module.exports = withCSS()

in next.config.js

See error on build

Expected behavior
Run build with success
System information

OS: macOS
Browser (if applies) [e.g. chrome, safari]
Version of Next.js: latest

Additional context
My current package.json
{
  "name": "with-jest",
  "version": "1.0.0",
  "dependencies": {
    "next": "latest",
    "react": "^16.5.2",
    "react-dom": "^16.5.2",
    "@zeit/next-css": "^0.2.0"
  },
  "devDependencies": {
    "babel-core": "7.0.0-bridge.0",
    "babel-jest": "^23.6.0",
    "enzyme": "3.4.3",
    "enzyme-adapter-react-16": "1.2.0",
    "jest": "23.5.0",
    "react-addons-test-utils": "15.6.2",
    "react-test-renderer": "16.4.2"
  },
  "scripts": {
    "test": "NODE_ENV=test jest",
    "dev": "next",
    "build": "next build",
    "start": "next start"
  }
}

Current next.config.js
const withCSS = require('@zeit/next-css')
module.exports = withCSS()

"@zeit/next-css": "^0.2.0" isn't compatible with 7.0 as far as I know, you need to update it to "@zeit/next-css": "^1.0.1".


Feat Introducing Multiple WPs into ToC section

@JuankCadavid you decide whether I accept this or not, taking into consideration Sonar's analysis.

@gcmartinezg @JuankCadavid the bugs and security hotspots were already addressed. But the code smells and code duplication is old code that due to time issues can't be addressed at this time.

Taking into account that the initial solution had many problems and was refactored as much as possible with the time we had, I am going to proceed to approve the merge without taking into account the comments from sonar cloud.


Tokenomics Research

https://skale.network/blog/validator-economics/

Further resources will be posted on Tokenomics Discussion section: https://github.com/hypersign-protocol/hid-node/discussions/130


Potential for multiple policy controllers running on a single cluster

What
In a setup where the hub and spoke are the same cluster, we can end up with two policy controllers running.
Installing the kuadrant operator using the OCM addon can result in two policy controllers running on the same cluster more than likely with different versions.
make local-setup OCM_SINGLE=true

cat <<EOF | kubectl apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: mgc-catalog
  namespace: olm
spec:
  sourceType: grpc
  image: quay.io/kuadrant/kuadrant-operator-catalog:latest
  grpcPodConfig:
    securityContextConfig: restricted
  displayName: mgc-catalog
  publisher: Red Hat
EOF

kubectl annotate --overwrite managedclusteraddon kuadrant-addon "addon.open-cluster-management.io/values"='{"CatalogSource":"mgc-catalog", "Channel":"preview"}'

make docker-build-gateway-controller kind-load-gateway-controller docker-build-policy-controller kind-load-policy-controller deploy-gateway-controller

kubectl get deployments -A -n kind-mgc-control-plane | grep policy
kuadrant-system                          kuadrant-operator-policy-controller       1/1     1            1           78m
multicluster-gateway-controller-system   mgc-policy-controller                     1/1     1            1           79m

This is only obvious when you use the OCM_SINGLE flag and the latest version of kuadrant operator. This will cause issues with our e2e tests when the kuadrant operator is eventually updated in the stable channel.

One option here may be to limit the operator being installed via its operator group to a set of specific namespaces IE the spoke cluster namespaces
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  name: my-group
  namespace: my-namespace
spec:
  targetNamespaces:
  - kuadrant-spoke-namespace1


"operation killed by thread-priority-watchdog" error even for very short routes

BRouter-web has been throwing the "operation killed by thread-priority-watchdog" error a lot of times these last 2 days, on both instances http://brouter.de/brouter-web and https://brouter.damsy.net/latest.
I have tried calculating very short routes (less than 2 km long) both with the standard trekking profile and the fastbike profile. I have tried changing my web browser (I tried with Google Chrome and with Mozilla Firefox), and I tried from several devices (one laptop and one smartphone).
Is there a problem with the routing engine itself?

Can you provide a link to the planned route?
Maybe I'm able to take reproduce the described behavior on my BRouter-Web instance and take a closer look into the BRouter server log.

The issue does not seem to be reproducible this morning, which is good news.

See brouter.de under heavy load from china robots.


Add click listener to icon

<template>

<vk-icons-cog v-on:click.native="onClick"></vk-icons-cog >
 // doesn't work
  <test-cmp v-on:click="onClick"></test-cmp> // works

</template>

Shouldn't this work ?
Here is the SO I posted https://stackoverflow.com/questions/51200811/vue-onclick-doesnt-work-on-vuikit-icon
(I created the tag vuikit so any questions related to the library can be tagged with it :) )

The native modifier is used on more complex components, it is unnecessary for the icons. However your code would not work even without the native modifer and that will be fixed in next revisions.
Meantime you can wrap the icons with vk-icon or a simple span and apply the listeners to them, as suggested in StackOverflow.
Take in consideration that vk-icons-cog would render the raw icon, while vk-icon icon="cog" would render the icon wrapped with span class="uk-icon", which is necessary for UIkit styling.


fixed error about power_on

On my computer,I can not find power_now in /sys/class/power_supply/BAT0/

So i use voltage_now*current_now to replace it

Codecov Report

Merging #55 into develop will decrease coverage by 0.37%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##           develop      #55      +/-   ##
===========================================
- Coverage    21.01%   20.63%   -0.38%
===========================================
  Files            7        7
  Lines          495      504       +9
  Branches        80       80
===========================================
  Hits           104      104
- Misses         383      392       +9
  Partials         8        8

Impacted Files
Coverage Δ

power/linux.py
21.8% <0%> (-1.59%)
: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 2c99b15...bbeaefd. Read the comment docs.


Spurious rebuilds due to filesystem rounding file modification timestamps

Problem
The issue #2874 was not completely fixed by #2880. I'm still seeing the exact same problem in latest Cargo:

Dirty libc v0.2.142: the dependency build_script_build was rebuilt<PHONE_NUMBER>.647155753s, 647155753ns after last build at<PHONE_NUMBER>.000000000s)
Dirty openssl-sys v0.9.86: the dependency build_script_main was rebuilt<PHONE_NUMBER>.891768399s, 891768399ns after last build at<PHONE_NUMBER>.000000000s)

Steps
I'm using Docker and mounting target/ dir as a Docker volume (in order to cache it). I think the docker volume rounds the timestamps to 1-second precision. However, this doesn't always cause spurious rebuilds, only maybe 25% of the time, and it's always build_script_build or build_script_main, not other files.
Possible Solution(s)
I assume Cargo wouldn't want to introduce imprecision in comparison, such as always comparing the integer number of seconds or allowing 1-second difference between timestamps. Therefore, I propose detecting this problem explicitly: there's only one in a billion chance that the nanosecond part will be exactly 0. So if either of the timestamps being compared has exactly 0 nanosecond part, compare only the integer number of seconds. Otherwise compare in full precision. I can make a PR with that.
Notes
No response
Version
cargo 1.71.0-nightly (d0a4cbcee 2023-04-16)
release: 1.71.0-nightly
commit-hash: d0a4cbcee614fdb7ba66e860e603a00a644d71f8
commit-date: 2023-04-16
host: aarch64-apple-darwin
libgit2: 1.6.3 (sys:0.17.0 vendored)
libcurl: 7.88.1 (sys:0.4.61+curl-8.0.1 system ssl:(SecureTransport) LibreSSL/3.3.6)
ssl: OpenSSL 1.1.1t  7 Feb 2023
os: Mac OS 13.4.0 [64-bit]

@weihanglo I'm unable to perform the research of filesystems and libc implementations that you suggested.
I've been using a fork of Cargo with this change, and it worked fine for me.
If someone else wants to develop a less hacky fix or investigate all platforms, please do.

@kornelski, could you share the patch so we can weigh on how we can integrate that, or provide a config for low precision filesystem as a escape hatch. Using fingerprint instead of mtime is also under the consideration https://github.com/rust-lang/cargo/issues/6529. Since we have experimental SQLite integration, #6529 might be more possible to move forward.

I think I have this issue too.
Sometimes cargo tries to rebuild from libc .

Sometimes cargo tries to rebuild from libc .

Hi, @yuyang-ok. could you share what filesystem/OS/environment you are on? That would help evaluate possible solutions.

I'm seeing this as well with z3:
       Dirty z3-sys v0.8.1: the file `target/release/build/z3-sys-0afb7a39553d3e75/out/param_kind.rs` has changed<PHONE_NUMBER>.081130554s, 81130554ns after last build at<PHONE_NUMBER>.000000000s)

I'm building in a Linux VM running on macOS host. The filesystem with the project is a virtfs passed to QEMU as:
-virtfs local,path=/Users/ivan/projects,security_model=none,mount_tag=projects

Inside of the VM:
ivan@vm:~$ mount | grep projects
projects on /mnt/data/homes/ivan/projects type 9p (rw,relatime,dirsync,access=client,trans=virtio,_netdev)

I'm not sure where the rounded timestamp comes from. Both VM's fs and remote fs produce ns precision timestamps:
$ stat target/release/build/z3-sys-0afb7a39553d3e75/out/param_kind.rs ~/.rustup
  File: target/release/build/z3-sys-0afb7a39553d3e75/out/param_kind.rs
  Size: 295       	Blocks: 8          IO Block: 131072 regular file
Device: 0,42	Inode: 213528511   Links: 1
Access: (0644/-rw-r--r--)  Uid: (  501/    ivan)   Gid: (   20/ dialout)
Access: 2023-12-25 03:28:52.416478161 +0000
Modify: 2023-12-25 03:28:52.081130554 +0000
Change: 2023-12-25 03:28:52.081130554 +0000
 Birth: -
  File: /home/ivan/.rustup
  Size: 94        	Blocks: 0          IO Block: 4096   directory
Device: 259,1	Inode: 103875877   Links: 6
Access: (0755/drwxr-xr-x)  Uid: (  501/    ivan)   Gid: (   20/ dialout)
Access: 2023-12-25 03:38:09.415500979 +0000
Modify: 2023-07-23 20:06:26.016396583 +0000
Change: 2023-07-23 20:06:26.016396583 +0000
 Birth: 2023-07-23 20:06:12.887530972 +0000

Running cargo build on the host only builds once.
Running it in a VM almost always produces a rebuild, but not 100% of the time, as it converges eventually:
ivan@vm:~/projects/advent-of-code-2023/problem-42$ rm -rf target

ivan@vm:~/projects/advent-of-code-2023/problem-42$ cargo build --release
   Compiling glob v0.3.1
   Compiling proc-macro2 v1.0.71
   Compiling unicode-ident v1.0.12
   Compiling libc v0.2.151
   Compiling cfg-if v1.0.0
   Compiling memchr v2.6.4
   Compiling regex-syntax v0.8.2
   Compiling minimal-lexical v0.2.1
   Compiling libloading v0.7.4
   Compiling nom v7.1.3
   Compiling bindgen v0.66.1
   Compiling clang-sys v1.6.1
   Compiling lazy_static v1.4.0
   Compiling rustc-hash v1.1.0
   Compiling lazycell v1.3.0
   Compiling bitflags v2.4.1
   Compiling shlex v1.2.0
   Compiling peeking_take_while v0.1.2
   Compiling regex-automata v0.4.3
   Compiling radium v0.7.0
   Compiling quote v1.0.33
   Compiling cexpr v0.6.0
   Compiling syn v2.0.42
   Compiling regex v1.10.2
   Compiling tap v1.0.1
   Compiling wyz v0.5.1
   Compiling log v0.4.20
   Compiling funty v2.0.0
   Compiling fnv v1.0.7
   Compiling bitvec v1.0.1
   Compiling z3-sys v0.8.1
   Compiling z3 v0.12.1
   Compiling problem-42 v0.1.0 (/mnt/data/homes/ivan/projects/advent-of-code-2023/problem-42)
    Finished release [optimized + debuginfo] target(s) in 35.51s

ivan@vm:~/projects/advent-of-code-2023/problem-42$ cargo build --release
   Compiling proc-macro2 v1.0.71
   Compiling clang-sys v1.6.1
   Compiling bindgen v0.66.1
   Compiling quote v1.0.33
   Compiling syn v2.0.42
   Compiling z3-sys v0.8.1
   Compiling z3 v0.12.1
   Compiling problem-42 v0.1.0 (/mnt/data/homes/ivan/projects/advent-of-code-2023/problem-42)
    Finished release [optimized + debuginfo] target(s) in 24.45s

ivan@vm:~/projects/advent-of-code-2023/problem-42$ cargo build --release
   Compiling clang-sys v1.6.1
   Compiling bindgen v0.66.1
   Compiling z3-sys v0.8.1
   Compiling z3 v0.12.1
   Compiling problem-42 v0.1.0 (/mnt/data/homes/ivan/projects/advent-of-code-2023/problem-42)
    Finished release [optimized + debuginfo] target(s) in 21.92s

ivan@vm:~/projects/advent-of-code-2023/problem-42$ cargo build --release
   Compiling z3-sys v0.8.1
   Compiling z3 v0.12.1
   Compiling problem-42 v0.1.0 (/mnt/data/homes/ivan/projects/advent-of-code-2023/problem-42)
    Finished release [optimized + debuginfo] target(s) in 9.06s

ivan@vm:~/projects/advent-of-code-2023/problem-42$ cargo build --release
   Compiling z3-sys v0.8.1
   Compiling z3 v0.12.1
   Compiling problem-42 v0.1.0 (/mnt/data/homes/ivan/projects/advent-of-code-2023/problem-42)
    Finished release [optimized + debuginfo] target(s) in 6.17s

ivan@vm:~/projects/advent-of-code-2023/problem-42$ cargo build --release
    Finished release [optimized + debuginfo] target(s) in 0.56s

ivan@vm:~/projects/advent-of-code-2023/problem-42$ cargo build --release
    Finished release [optimized + debuginfo] target(s) in 0.71s

Pragmatically this would be the best thing to do for the environment.

I think I've found the cause of the problem:
https://github.com/rust-lang/cargo/blob/bf79c8b154fa6b3e4d781c26935429948cbd9b2b/crates/cargo-util/src/paths.rs#L695-L697
Cargo tries to write timestamps back to the file system.
Cargo assumes that the precision of timestamps is the same in all I/O operations, but this assumption is empirically wrong: Docker's overlay file system, when running under VirtioFS + Apple Virtualization Framework, has a buggy utimensat function that discards nanoseconds (easily reproducible in C). In this setup stat has nanosecond precision, but update of file timestamps keeps only the whole seconds part.

That is really an impressive investigation. Thank you so much!!
If I understand correctly, the detection only run once, and with rounding-up it makes a lower false-positive rate than #13955. But still, the "one-in-a-billion-chances-happen-at-scale" problem is there when the actual mtime has zero in nanosecond precision?


Cast objc_msgSend calls to placate compiler.

With the default Xcode build settings these days, this code doesn't even compile unless the casts are in place.
It's also a Good Idea to do these casts. I know this code steers clear of the pitfalls, but just in case someone uses this code to try to learn something, we might as well give them the right idea!

I agree. We've added that a long time ago in PSPDFKit but haven't synced the lib with what we use in a while. I'll merge your solution, it's similar to what we did. Thanks!


Feature rule editor import flyout

Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

The DCO and Developer Certificate of Origin checks are failing because your commits don't have signed off. The To add your Signed-off-by line to every commit in this branch section of the details link for the DCO check has steps for retroactively adding sign off to commits.


"verbose_name" doesn't work.

My code:
class LdapUser(ldapdb.models.Model):
    base_dn = "ou=people,dc=example,dc=org"
    object_classes = ['posixAccount', 'shadowAccount', 'inetOrgPerson']

    first_name = CharField('First Name', db_column='givenName')
    last_name = CharField('Last Name', db_column='sn')
    full_name = CharField('Full Name, db_column='cn')
    email = CharField('E-Mail', db_column='mail')
    phone = CharField('Phone Number', db_column='telephoneNumber', blank=True)

I tried also
first_name = CharField(db_column='givenName', verbose_name='First Name')

but it still doesn't work. Maybe it is my fault, but I tried it with a normal model and it works.

This seems to

class LdapUser(ldapdb.models.Model):
base_dn = "ou=people,dc=example,dc=org"
object_classes = ['posixAccount', 'shadowAccount', 'inetOrgPerson']

first_name = CharField('First Name', db_column='givenName')
last_name = CharField('Last Name', db_column='sn')
full_name = CharField('Full Name, db_column='cn')
email = CharField('E-Mail', db_column='mail')
phone = CharField('Phone Number', db_column='telephoneNumber', blank=True)

This is working for me.

Thanks for your answer, i will examine the problem.

@ikreb7 I've added some tests, I'm not able to reproduce your issue :/
Feel free to reopen this if need be :)


New Icon Store Implementation in UI Toolkit Components

Changes:
Old IconStore Component Deleted.
Old stories style files are placed with base-css lib.
New icon-store lib implementation and migration.
Button and Chip component icon prop changed to iconComponent.
IconStore stories revamp.


Add guide for contributing to ModdingDocs

Basic build instructions and useful tools for anyone unfamiliar with working with reStructuredText and readthedocs.
It's not fully in the state I want the page to be in. For example it's written for someone familiar with working with CLI and having some of the necessary dependencies installed (python and make) but it's in a state where I'd consider it publishable with improvements following later.
Definitely better than what we have currently (i.e. nothing :P)

Only suggestion I have is to maybe move this to the bottom of the guides section, as I think it's more appropriate than at the top.

Done with 81954ab2d084b41546a0684f03038af0d46f82aa

i should've taken a look earlier. would have been able to point out that the requirements are in docs/requirements.txt so you can do pip install -r docs/requirements.txt


All the Files related to the Zod validations are corrected.

@abhay-raj19 https://github.com/abhay-raj19/FitBody/issues/115 I have Successfully Created the Zod Validation in the File and passed it as a middleware. As our project is currently in the initial phase I have made it as a middleware so that where we want any validation related to the zod we can get it using middleware.
Please View it Once.Looking forword to make entire Backend Setup for you.
Solved all Problems Related to PR #192. Sorry for inconvenience Caused. Please Assign the labels as previous PR once I have Closed those PR Done all things from beginning

ITS WORKING FINE NOW !!

LGTM


Wrong scale and viewport when printing

We have built our own viewer upon the pdf.js library and I have experienced some issues regarding to print. Our viewer displays one or two pdf-pages based on the ratio of the window. Resize your browser window until you see a single page of the newspaper and make sure it is page 23. For some reason the Firefox print functionallity doesn't like it when you resize the window so you may need to reload the page if the browser shows you a dialog saying something unexpected went wrong. But when you have a single page and it is page number 23 and try to print the pages the output is in the wrong scale. If you use Chrome you can print the spread of page 22-23 and in this scenario page 22 get's ok but 23 will be wrong.
Each page in the newspaper is a separate pdf document and I load the pages using the same worker. I have used the same pattern as in the pdfjs-viewer for setting up and rendering to a new canvas in a printContainer and using that for the print output.
I have used the print pattern from the pdfjs-viewer and in the PDFPageView_beforePrint function the following two lines seems to make all the difference:
var viewport = pdfPage.getViewport(1);
var PRINT_OUTPUT_SCALE = 2;
The thing is that if I change it so I call getViewport with the scale of 2 and give the PRINT_OUTPUT_SCALE the value of 1 the print output is correct.
The attached page is only one example, the bug occurs on different pages and I haven't figured out why. I think the bug occurs when rendering the page to the canvas because if I inspect the element with chrome web inspector I can see that the canvas in the dom has the wrong scale.

scale_print_problem.pdf
PDF file attached is password protected: 3d329e5531f5d674b70dba4b9f0a6ae5
Configuration:

Web browser and its version: Firefox 47.0.1, Chrome 51.0.2704.103 (64-bit)
Operating system and its version: OSX El Capitan 10.11.6
PDF.js version: 1.3.62#084bb86 (also tried the latest 1.5)
Is an extension: No

Steps to reproduce the problem:

Press the print-button in the GUI or cmd-p on your keyboard while viewing a single page (page number 23).
Print or preview the page.

What is the expected behavior?
Should print the entire contents of the page
What went wrong?
Prints the upper left part of the page
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension): http://webapp.im-epaper.se/pdfjs/print-bug/#pages/10902/3/23

for me the same problem when i open the pdfjs viewer in a pop up window (resize to client screen),
the doc printed is resized smaller then the real file much for about the quarter of the page...
also tried to view the file by pure browse (chrome + firefox) and i see it very good but on print i get 14 blank pages from your demo viewer- take a look here : https://aloni.azurewebsites.net/partials/pdfjs/web/viewer.html

Now PDF.js prints pages as the sizes specified by the PDF document. See if scaling issues addressed by #7677. I also suspect that CSS width of document is not set properly and it's pushing right margin far the the right -- hard to test that for "@media print" needs and more experimentation. Closing as answered.

The printing is very bad!

why won't we use the browser print preview with a link to the file as print preview ?

@alonisoft offtopic here, but ff implemented font loading api which does not work with mozPrintCallback. The issue is tracked somewhere else.

ok,
and what about the use of browser's print preview which seems to me the best "clean and easy" :)  ?
or, open the specified link file in a new tab (not download) and let the browser do the rest... ?

I'm sorry it's hard to answer the questions above -- to many threads of the discussion (probably good for IRC conversations but not for issue tracking). Please read https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md to request more detailed response.


Feat /  Always call the render left/right control functions

For accessibility reasons, it is better to always call the render (left/right) controls function and leave the implementation details to the developer. With this change, it's the developer's responsibility to hide or disable the control based on the disabled argument.
When the control function returns a falsy value, the control wrapper won't get rendered. Preventing an unneeded <div /> wrapper.
⚠ I removed the hasSlideBefore state, which always evaluates to false, causing the left control to be disabled when you have reached the end of the slider (when using cycle-mode stop). I did some (mobile) swipe tests with console.log on the state, but I have never seen this being evaluated as true. I don't know which problem this variable tries to solve. Please be aware of this while reviewing.
Ticket: https://videodock.atlassian.net/browse/DDSB-4967

I think hasSlideBefore is not meant for cycleMode=="stop", but for the other cycle modes. Its intention is to disable the leftControl initially, until the slider was used before, so that you don't start the wrong way.

I understand the reasoning behind it now. But I think it's a bit opinionated to disable the control it on first instance and enable it afterwards.
It was missing on L219 though and not on L194. Because it needs to toggle after sliding.
Do you agree we keep it removed @royschut ?
This implementation detail can also be done by the developer by using the TileSlider onSlideEnd prop and making a custom (local) hasSlideBefore state to disable the (left) control. That is easier done for the developer, than undoing this logic, because then you need to write your own disable logic (repeating  (cycleMode === 'stop' && state.index === 0)). I rather keep the TileSlider "dumb".

Do you agree we keep it removed @royschut ?

Yes, you're right, we can handle it from the implementation if needed!


Add compatibility for SQL2 changes

Part of this is updating the quotation syntax, as @wdhutton ran into in quasar-analytics/quasar#1107

The other part is various unary operators now require parens. See the blog post.

The primary changes here are quotation and parentheses, correct? Are there any more operators to add support for?

@yanatan16 No, I don't think so.

Done. Released as version v1.2 of quasar-fdw. I also released v1.0.1 with quasar 3.x compatibility.


windows - structure - cannot find device

I have a Structure sensor from Occipital, i'm trying to get it running for a quick evaluation on depth capture images. It's turning out to be difficult!
I installed the Windows x64  package from here: https://structure.io/openni
I followed the instructions on the document on how to modify the Openni driver .ini files to set the required line to be: UsbInterface=0
I also set Openni.ini to Verbose = 0 and LogToConsole (from some tests already and some research).
I then launch NiViewer.exe and this is what is printed:
     1419 INFO       --- Filter Info --- Minimum Severity: VERBOSE
     1793 VERBOSE    No override device in configuration file
     3412 VERBOSE    Configuration has been read from 'C:\Program Files\OpenNI2\Tools\OpenNI.ini'
     3555 VERBOSE    OpenNI 2.2.0 (Build 33)-Win32 (Nov 12 2013 16:11:44)
     3677 VERBOSE    Using 'C:\Program Files\OpenNI2\Tools\OpenNI2\Drivers' as driver path
     3872 VERBOSE    Looking for drivers in drivers repository 'C:\Program Files\OpenNI2\Tools\OpenNI2\Drivers'
     5612 WARNING    Failed to load library 'Kinect.dll'. Error code: 126
     5697 VERBOSE    Couldn't use file 'Kinect.dll' as a device driver
     7041 INFO       New log started on 2017-11-24 12:45:20
     7191 INFO       --- Filter Info --- Minimum Severity: VERBOSE
    11501 INFO       New log started on 2017-11-24 12:45:20
    11548 INFO       --- Filter Info --- Minimum Severity: VERBOSE
    12972 VERBOSE    Trying to open device by URI '(NULL)'
    13076 ERROR      Can't open default device - none found
openDevice failed:
        DeviceOpen using default: no devices found

Press any key to continue . . .

Is there a step i'm missing? I have exactly the same issue on Windows 7 Professional and Windows 10 Home, two different computers.
If I have to adjust the PS1080 .ini files, why is the NiViewer program trying to load/use Kinect drivers (a different set of .ini and .dll in the Drivers folder..).  How can I force it to use the PS1080 drivers?

Hello I have a similar issue on my side too. I am using a Windows 10 PC. I even tried to install from the github code of OpenNI instead of using the binaries given in the above mentioned link.
When I tried to debug the code then I see the URI is NULL. What I have understood the function which opens the device using the device driver is expecting a string of URI. I don't know how to provide the URI to the function.
Please help to provide the URI string format if anyone of you know it. I want to try that too.