Add support for publish to optionally take the index that can be used

This form part of alternative-registries RFC-2141, it allows crates to optionally specify which registries the crate can be be published to.
@carols10cents, one thing that I am unsure about is if there is a plan for publish to still provide index, or for registry to be provided instead. I thought that your general view was that we should move away from the index file. If we do need to map allowed registries to the index then there will be a small amount of extra work required once #4506 is merged.
@withoutboats, happy for this to be merged into your branch if you want, the main reason I did not base it on your branch was due to tests not working on there yet.

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

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

Looks great! I think I'd like to try to throw this in with https://github.com/rust-lang/cargo/pull/4506 though as we'll want to be sure to feature gate the acceptance of a list of strings here I believe (and the feature gate bits were added in that PR)

It looks like #4506 is getting close to merge, so maybe that should be merged, then I will add in feature gating to this PR when I merge the changes in.

Ok sure yeah, either way's fine by me

I think we should probably merge #4506 separately. I have some big picture concerns about how we're handling publishing in general, which we're talking about on #4574, but also these smaller concerns:
I think this list should take registry names (as will be introduced in #4506), not index URLs, as @cswindle mentioned doing in the first comment. In general we're moving away from users dealing with index URLs as much as possible.
There's also the issue with passing registry.token raised in #4574. Basically, I think we should never pass registry.token to any registry tracked through one of those registries objects. I don't have an opinion about how you could declare an alternative token for those registries, either just add another key to the object (alongside index) or something with cargo/credentials, etc.

In the case of providing a registry that we want to use in publish, I actually wonder if we should just make a minor tweak to registry_configuration to pass in the registry (if provided) and look up the "registry..token" in the config, otherwise just get "registry.token". That way we can cross off the issue to support multiple registry tokens.

@cswindle ah yeah it was my expectation that registry.token is basically synonymous with registry.crates-io.token (but not used for other registries)

@alexcrichton I presume that is not something that would need to be done in an rfc and could just be implemented as part of this pull request (assuming resolution of #4574 is that we want to be able to push to private registries).

@cswindle indeed yeah!

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

Looks great! For now as well, could this be gated on the same alternate registries feature in the manifest?

@alexcrichton, now that the alternate registries has landed I was planning on updating this to be gated on the feature in the manifest. I have been taking a look into adding support for --registry for publish and login and if that is available it actually makes the code to perform the registry lookup easier (assuming that it is ok to mandate that if you want to push to alternate registry you use --registry rather than --index), so I might try and get that in first.

@cswindle ok sounds great! I think with a --registry argument we can definitely deprecate --index (which only ever existed for Cargo's own test suite anyway)

See #4680 for the PR to add --registry support.

I have now merged in my changes to add support for this. I am aware of the following two issues from further testing of this:

[ ] unable to publish when there are dependencies in another registry
[ ] we do not currently set the registry field in the index

I am in the process of sorting these last couple of bits out, so think it would make sense to do so in this pull request, rather than having another to do the last couple of bits.

I believe that this should now allow publishing and can be reviewed.

@alexcrichton, I have updated the code for most of the review comments, there are a couple where I have not updated, but in those cases I have explained why in the comments.

r? @withoutboats
I think you'll want to take a final pass here

@bors: r+
Sorry to take a while to review. This all looks good to me, no further changes. needed :)

:pushpin: Commit cb37d33 has been approved by withoutboats

:hourglass: Testing commit cb37d335fc6046b4658746cf831a0cc66d45b66e with merge 6a1aee06680d8f074a25431c938c42d7e8d0ab4e...

:sunny: Test successful - status-appveyor, status-travis
Approved by: withoutboats
Pushing 6a1aee06680d8f074a25431c938c42d7e8d0ab4e to master...


Add delete by metadata filter support

Adds support for deleting by metadata filter

Still need to add changelog entry

@benjaminran we would need to update index_grpc too

Thanks @rajat08 , I've updated grpc_index


Feature request: settings to exclude some files

Hey, thanks for nice plugin!
I have autocmd command for auto sourcing my vimrc. And when the plugin is saving file I'm getting my vim unnecessary frozen during sourcing the config..
autocmd bufwritepost $MYVIMRC source $MYVIMRC

It would be nice to have a setting to ignore/exclude some files, smth like this:
let g:auto_save_files_ignore = [$MYVIMRC]

Btw I have these settings:
let g:auto_save = 1
" https://github.com/907th/vim-auto-save/issues/53#issuecomment-571819789
let g:auto_save_events = ["CursorHold"]
set updatetime=300

Btw2 I can donate few dollars for this feature!

@milushov Hello, Roma!
I think that your feature request can be implement with a presave hook, like that:
" This will run AbortIfVimRc function before each save
let g:auto_save_presave_hook = 'call AbortIfVimRc()'
function! AbortIfVimRc()
  if <check that current file is vimrc somehow>
    let g:auto_save_abort = 1
  else
    let g:auto_save_abort = 0
  endif
endfunction

I don't know how to exactly <check that current file is vimrc>, but I believe you'll be able to google it easily yourself.
Thank you for getting in touch and for using my plugin!

To <check that current file is vimrc somehow> you can check the ft
if &ft == "vim"


[csi-rbd] Support erasure coded pools

As suggested by @travisn, I'm opening this to track a feature gap between the rook RBD volume provisioner and the ceph CSI RBD plugin:
From what I could gather from the source, when defining a StorageClass, the plugin only supports specifying a single pool, which will be sent as --pool argument to rbd create.
But, in order to be able to use erasure coded pools with RBD, you also need to send --data-pool, as described here.
Rook allows you to specify both the replicated metadata and the erasure coded data pool, as documented here:
apiVersion: storage.k8s.io/v1
kind: StorageClass
...
parameters:
  blockPool: replicated-metadata-pool
  dataBlockPool: ec-data-pool

this will be addressed in rook https://github.com/rook/rook/issues/2650

@poornimag can you please take a look at this ?

which will be sent as --data argument

Just to clarify, it is sent as the --pool argument

@dillaman Updated, thanks for the heads up!

Ping!
@rootfs From what I can see, there's still no way of creating a StorageClass backed by different metadata and  data pools. Any idea if this was considered / is on the roadmap?

@lbogdan #605 adds support for erasure-coded pools


Fix/sub modify and sub restart at item level

Makes sub_modify and sub_restart cart wide configurations

Resolved conflicts that appeared after #30. @brettflorio feel free to review and merge when you have a moment :)


Fix vagrant url

Proposed Changes
Fix vagrant url
...

Screenshots of your changes (if applicable)

Associated documentation repository pull request (if applicable)

Type of Change
(Write an X or a brief description next to the type or types that best describe your changes.)

Type
Applies?

🚨 Breaking change (fix or feature that would cause existing functionality to change)

✨ New feature (non-breaking change that adds functionality)

🐛 Bug fix (non-breaking change that fixes an issue)

🎨 User interface change (change to user interface; provide screenshots)

♻ Refactoring (internal change to codebase, without changing functionality)

🚦 Test update (change that only adds or modifies tests)

📦 Dependency update (change that updates a dependency)

🔧 Internal (change that only affects developers or continuous integration)
x

Checklist
(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)
Before opening your pull request:

[ ] I have performed a self-review of my changes.

Check that all changed files included in this pull request are intentional changes.
Check that all changes are relevant to the purpose of this pull request, as described above.

[ ] I have added tests for my changes, if applicable.

This is required for all bug fixes and new features.

[ ] I have updated the project documentation, if applicable.

This is required for new features.

[ ] If this is my first contribution, I have added myself to the list of contributors.

After opening your pull request:

[ ] I have updated the project Changelog (this is required for all changes).
[ ] I have verified that the pre-commit.ci checks have passed.
[ ] I have verified that the CI tests have passed.
[ ] I have reviewed the test coverage changes reported by Coveralls.
[ ] I have requested a review from a project maintainer.

Questions and Comments
(Include any questions or comments you have regarding your changes.)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.757%

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
41178

Relevant Lines:
44199

💛  - Coveralls


No new data for 4/20

No new data for 4/20

Big fail, pushing now. Thanks!

Site is redeploying... There was a Github pages issue that prevented it from being pushed. It should be live again within an hour.

awesome, thank you for quick response.  just checked our data of today, and looks good.


Hi, one question

Hi,
You transfer it to me and I take charge of it to support version 3 of sublime text?
Thanks

Hi,
Yeah, sure. I'm not using ST anymore anyway.

I tried to transfer but kallookoo/WebSearch already exists. Do you still want ownership?

Yes, I'll erase my fork and transfer them to me when you can, thanks

Transfer in progress...  Enjoy :-)

Thanks!!!


Implement Your Own Operators

With the current version of Rx.PHP, if you want to implement a custom operator, you need to add it to BaseObservable.
I propose that we take a page from RxJava and add a lift operator, which would allow custom operators to be added to the chain.
For Example:

$observable = new Rx\Observable\ArrayObservable(array(21, 21, 42));
$observable
    ->select(function($elem) { return $elem * 2; })
    ->lift(new DistinctUntilChangedOperator())
    ->subscribe($stdoutObserver);

I've been working on an implementation of this here: https://github.com/davidwdan/Rx.PHP/compare/master...operators?diff=unified&name=operators
It includes the lift operator along with tap, never and distinctUntilChanged.
If this is a direction you're interested in going, let me know and I'll create PRs.

Shipped. :+1:


Key Error: 'id_token' on Starlette

Describe the bug
The Async OpenID integration does not work in the v1 builds.
Error Stacks
Traceback (most recent call last):

  File "/usr/local/lib/python3.9/site-packages/uvicorn/protocols/http/httptools_impl.py", line 375, in run_asgi
    result = await app(self.scope, self.receive, self.send)
  File "/usr/local/lib/python3.9/site-packages/uvicorn/middleware/proxy_headers.py", line 75, in __call__
    return await self.app(scope, receive, send)
  File "/usr/local/lib/python3.9/site-packages/fastapi/applications.py", line 208, in __call__
    await super().__call__(scope, receive, send)
  File "/usr/local/lib/python3.9/site-packages/starlette/applications.py", line 112, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/usr/local/lib/python3.9/site-packages/starlette/middleware/errors.py", line 181, in __call__
    raise exc from None
  File "/usr/local/lib/python3.9/site-packages/starlette/middleware/errors.py", line 159, in __call__
    await self.app(scope, receive, _send)
  File "/usr/local/lib/python3.9/site-packages/starlette/middleware/sessions.py", line 75, in __call__
    await self.app(scope, receive, send_wrapper)
  File "/usr/local/lib/python3.9/site-packages/starlette/middleware/cors.py", line 78, in __call__
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.9/site-packages/sentry_sdk/integrations/asgi.py", line 106, in _run_asgi3
    return await self._run_app(scope, lambda: self.app(scope, receive, send))
  File "/usr/local/lib/python3.9/site-packages/sentry_sdk/integrations/asgi.py", line 152, in _run_app
    raise exc from None
  File "/usr/local/lib/python3.9/site-packages/sentry_sdk/integrations/asgi.py", line 149, in _run_app
    return await callback()
  File "/usr/local/lib/python3.9/site-packages/starlette/exceptions.py", line 82, in __call__
    raise exc from None
  File "/usr/local/lib/python3.9/site-packages/starlette/exceptions.py", line 71, in __call__
    await self.app(scope, receive, sender)
  File "/usr/local/lib/python3.9/site-packages/starlette/routing.py", line 580, in __call__
    await route.handle(scope, receive, send)
  File "/usr/local/lib/python3.9/site-packages/starlette/routing.py", line 241, in handle
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.9/site-packages/starlette/routing.py", line 52, in app
    response = await func(request)
  File "/usr/local/lib/python3.9/site-packages/fastapi/routing.py", line 226, in app
    raw_response = await run_endpoint_function(
  File "/usr/local/lib/python3.9/site-packages/fastapi/routing.py", line 159, in run_endpoint_function
    return await dependant.call(**values)
  File "/app/./example/oauth/google/routes.py", line 32, in google_oauth
    user_info = await oauth.google.parse_id_token(request, token)
  File "/usr/local/lib/python3.9/site-packages/authlib/integrations/base_client/async_openid.py", line 59, in parse_id_token
    token['id_token'],
  File "/usr/local/lib/python3.9/site-packages/starlette/requests.py", line 68, in __getitem__
    return self.scope[key]
KeyError: 'id_token'

See additional error stack in https://github.com/authlib/demo-oauth-client/issues/17
To Reproduce
@app.get('/auth')
async def google_oauth(request: Request):
    token = await oauth.google.authorize_access_token(request)
    user_info = await oauth.google.parse_id_token(request, token)

See additional example in https://github.com/authlib/demo-oauth-client/issues/17
Expected behavior
As @sondrelg found, I think the problem is in the way that authlib is reading the nonce parameter via httpx which is causing the whole function to fail. This same function worked as is in the 0.15.2, but newer version of httpx did not work with it.
Environment:

OS: Ubuntu
Python Version: 3.9.5
Authlib Version: 1.0.0b1

@rushilsrivastava from my understanding, you don't need to parse_id_token manually.
https://github.com/lepture/authlib/blob/b8f7cc7b709a5222591ee7d56954b6e893696fa4/authlib/integrations/starlette_client/apps.py#L65-L70
There will be a userinfo in the token when authorize_access_token

Yes, you are right. Sorry, this is not a bug in the code but in the documentation - should have taken a closer look there.
I think the documentation for 1.0.0 needs to be updated as well: https://docs.authlib.org/en/latest/client/starlette.html


[DOCS] Area/Area2D class ref update

Clean up language and make consistent across both nodes.

Hang on, there's a parsing error. Fixing now.


Moving UI updates and window rect checks over to post-process tick for engine to accurately reflect the intended code flow.

This was missed with the initial addition of the post and pre process ticks to the engine.  It was intended that UI updates happen after all pre, idle, and post notifications are sent.

I caught this issue when debugging some UI which was updating its position in the post-process tick group.  It was causing jitter every so often as the paint methods weren't being called in the proper order.  This moves the paints to the proper place and all is well again.


added: elements with icons translation

translates elements which innerHtml starts with icons

this problem requires an universal fix, not one just for icons


Changed out the AzureFundamentals Hero item

Now item points to Azure SDK for .NET.  That Learn module is deprecated at this point anyway

This PR introduced a build warning (bad link). Can someone fix? @CamSoper @DavidCBerry13

This PR introduced a build warning (bad link). Can someone fix? @CamSoper @DavidCBerry13

@gewarren Mea culpa, I'll fix.

@gewarren Mea culpa, I'll fix.

@CamSoper  I already fixed it in #22568. Can you approve that instead?

@CamSoper  I already fixed it in #22568. Can you approve that instead?


Add links to supporting documents

Not styled appropriately, but this adds appropriate links for supporting
documents in the regs.gov docket
For eregs/notice-and-comment#295. To see this in action, apply the following diff:
diff --git a/notice_and_comment/settings/base.py b/notice_and_comment/settings/base.py
index bb0c858..efd8332 100644
--- a/notice_and_comment/settings/base.py
+++ b/notice_and_comment/settings/base.py
@@ -107,6 +107,14 @@ CFR_CHANGES = {
 PREAMBLE_INTRO = {
     "0000_0000": {
         "meta": {
+            "supporting_documents": [
+                {"regs_id": "AAAAA", "title": "A document title"},
+                {"regs_id": "BBBBB", "title": "B document title"},
+                {"regs_id": "CCCCC", "title": "C document title"},
+                {"regs_id": "DDDDD", "title": "D document title"},
+                {"regs_id": "EEEEE", "title": "E document title"},
+            ],
+            "primary_docket": "DOCKETDOCKET",
             "primary_agency": "Environmental Protection Agency",
             "title": "EPA's new proposal",
             "comments_close": "2016-05-29",

Looks like:

...

For real data, we need eregs/regulations-parser#262 and eregs/notice-and-comment#187

👍


Add a "review needed" label

I have used "help wanted", but I think "review needed" would be far better.
This label would be widely used, because major chapter changes or new assessment guides generally need to be reviewed by another member of the team before release.

This seems suitable so I can add it. The labels serve different purposes:

review needed - I want someone to check over this.
help wanted - I can't do this, someone else please help me.


List icon misaligns when href is given

			person
			Bryan Cranston

giving href to the list icon in navigation drawer misaligns icon and the text.
see below image for reference. In the image i only gave href to the 1st list and others are just  texts.
mdl v1.1.1
http://i.imgur.com/Z7848ul.png

@shmshd12 It's a bit hard to tell where the problem is coming from with just the screenshot, but it looks to me that the problem is the navi-link class you're applying, which seems to be your own code. You'll need to make sure that the font and alignment settings for that don't shift things around.
Here's an example that, albeit ugly, works fine: https://codepen.io/anon/pen/ONMpBN

mdl v1.1.3 fixed this issue.


Add flag to disable 'x-' prefix prepended in makeComponentTemplate

This is a: Feature Request
My version of UI-Router is: 1.0.0
Feature Request
Add a flag to disable the 'x-' prefix that is prepended to component elements in makeComponentTemplate. Adding the prefix can interfere with css and dom selectors. Adding a way to opt out of or into using the prefix will make it possible to workaround the problem.
This issue referenced in https://github.com/angular-ui/ui-router/issues/3276

This flag should be able to be configured globally 👍

This will be fixed by https://github.com/angular-ui/ui-router/commit/60b9ef923c701c831c66a145ebae36039782cf68 in 1.0.1
We will only prefixing if the component name requires the prefix (it is named xFoo or dataFoo)

Thanks for the quick turnaround @christopherthielen. I tried 1.0.1 and the element names are indeed without the 'x-' prefix again. However, the attribute names are still being prefixed with 'x-'. Would it be possible to only add the prefix to the attributes when the component name requires it as well?

@jordandh yeah I suppose that would make sense

Ha, I ran into this as well: when will 1.0.1 be available through npm?

1.0.1 was released last week.  Note the package changed to @uirouter/angularjs: https://unpkg.com/<EMAIL_ADDRESS>

@Remco75 1.0.1 was released last week.  Note the npm package changed to scoped package @uirouter/angularjs https://github.com/angular-ui/ui-router/issues/3424
Read more: https://ui-router.github.io/blog/uirouter-scoped-packages/

thnx man, great work as usual. I think npm registry cache got the better of me, it wasn't there yet when I checked ;-)


Edit watcher server to restart the server when file change

I change this function a little, my approach was looking if something happen in the folder/moclojer.yml and then se if the file is moclojer.yaml if is I will restart the server if not I won’t.

closes #208


efivar: 37 -> 38, efibootmgr: 17 -> 18

Description of changes

https://github.com/rhboot/efibootmgr/releases/tag/18
https://github.com/rhboot/efivar/releases/tag/38

Had to upgrade efivar from 37 -> 38 to fix efibootmgr build warning treated as error (Wno-pointer-sign)

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg test tests.installer-systemd-stage-1 tests.kexec tests.systemd-boot tests.systemd-initrd-btrfs-raid tests.systemd-initrd-swraid tests.lvm2

Result of nixpkgs-review pr 198789 run on x86_64-linux 1

4 packages marked as broken and skipped:

discover
gnome-firmware-updater
libsForQt512.discover
libsForQt514.discover

13 packages built:

efibootmgr
efivar
fwupd
gnome-firmware
gnome.gnome-software
libsForQt5.discover
mokutil
pantheon.elementary-greeter
pantheon.switchboard-plug-about
pantheon.switchboard-with-plugs
pantheon.wingpanel-applications-menu
pantheon.wingpanel-with-indicators
system76-firmware

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

fwupd:

Package is missing a meta section.
If the package is using runCommand please make sure to inherit or create a meta section.

libsForQt5.discover:

Package is missing a meta section.
If the package is using runCommand please make sure to inherit or create a meta section.

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

efivar suffers from a different -Werror on i686-linux (and any other common 32-bit platform probably), blocking nixos-unstable channel: https://hydra.nixos.org/build/198430706

https://github.com/NixOS/nixpkgs/pull/200916


updated Readme

update goals
update headings

Thank you, no. This is not a change that I think improves the project.


RuntimeError: Errors occured while writing lanelet map:

I am getting the following error

while trying to write the map generated from the shortest route query
 graph = lanelet2.routing.RoutingGraph(map, traffic_rules)
 route=graph.getRoute(start_lanelet, end_lanelet,0,1)
 laneletSubmap = route.laneletSubmap()
 map = laneletSubmap.laneletMap()

 map.add(LineString3d(getId(),centerline_points))

 path = os.path.join(os.path.dirname(os.path.abspath(__file__)), 'output_.osm')
 lanelet2.io.write(path, map, proj)

it is complaining about the way of the centerline nodes are missing in the final output. PLease let me know if i am missing something here.
Thanks

looks like the following code
laneletSubmap = route.laneletSubmap()
 map = laneletSubmap.laneletMap()

couldn't extract the ''centerline'''nodes way id which was originally available in the lanlet relation definition

Looks like our map building algorithm is ignoring customized centerlines. I'll look into it. Shouldn't be too hard to fix.

Thanks for acknowledging that. Would you let us notified once you fix the issue ?

Thanks guys the issue is sorted out now.


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v4.19.114 to before v4.19.222",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6fb0e4385928900ccb8697748555b3f54bba5193",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=18c73170de6719491f79b04c727ea8314c246b03"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "6fb0e4385928900ccb8697748555b3f54bba5193",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "18c73170de6719491f79b04c727ea8314c246b03",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "net/packet: rx_owner_map depends on pg_vec\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.19.222 by commit 18c73170de6719491f79b04c727ea8314c246b03, it was introduced in version v4.19.114 by commit 6fb0e4385928900ccb8697748555b3f54bba5193. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002655


Build Signup Functionality

Sign-up is working however, may need to verify and test once we add JWT


Reduced coordinates / featherstone for joints

Use something like the Featherstone algorithm to calculate joint state in reduced coordinates - one coordinate for each rotational/translational degree of freedom for each joint.
This would be a major rewrite and has a number of subtasks - the first of which is to determine whether the underlying algorithms (mass matrix calculation, forward kinematics, etc) are all XLA/TPU-friendly.

Some other references in case they are useful.
Tiny Differentiable Simulator implementation - https://github.com/google-research/tiny-differentiable-simulator/blob/master/src/rb_constraint_solver.hpp
Which references Michael Cline's thesis - https://open.library.ubc.ca/soa/cIRcle/collections/ubctheses/831/items/1.0051676


Reduce the frequency of None in Option Gen

The idea here is that if you are generating 100 values, it's probably
not that useful for 50 of them to be the same (None). Having a 50%
chance of None is especially problematic when a data structure has
several nested Option fields, in which case it becomes pretty unlikely
that any non-None values are generated for the innermost Option field.
I've arbitrarily chosen a 10% None frequency here, but feel free to
recommend other values that may be better.

👍
I think 10% None sounds about right. Since by default we generate 100 tests, this makes it very likely to get some nones in there without wasting too many test cases on the same value.

Closing and reopening the PR to try to get the build to pass again (I think it failed because the series of tubes is under attack).

👍


[phenyl-http-client] Appear warning when webpack bundles modules

I use the following version.
webpack: 3.11.0
babel-loader: 7.1.4
WARNING in ./node_modules/encoding/lib/iconv-loader.js
9:12-34 Critical dependency: the request of a dependency is an expression
 @ ./node_modules/encoding/lib/iconv-loader.js
 @ ./node_modules/encoding/lib/encoding.js
 @ ./node_modules/node-fetch/lib/body.js
 @ ./node_modules/node-fetch/index.js
 @ ./node_modules/phenyl-http-client/dist/fetch.js
 @ ./node_modules/phenyl-http-client/dist/index.js
 @ ./src/modules/index.js
 @ ./src/app.js
 @ ./index.js
 @ multi (webpack)-dev-server/client?http://localhost:8080 babel-polyfill ./index.js
webpack: Compiled with warnings.

This issue is related to iconv-loader issue


No longer reporting ParseErrors for Invalid HTML

I was able to reproduce this via this test:
    [TestFixture]
    public class OptionInBodyCreatesParseError
    {
        [Test(Description = "Ensures ParseError is created for Option in Body")]
        public void EnsureParseErrorIsCreatedForOptionInBody()
        {
            var html = "<option></option>";
            var doc = new HtmlDocument();

            doc.LoadHtml(html);

            Assert.That(doc.ParseErrors.Count(), Is.EqualTo(1));
        }
    }

Running this test through the w3c validator confirms this is not valid HTML.  Previous version of HAP would return errors via ParseErrors property.  This is no longer the case with the latest package on Nuget and the latest code in master.

Hello @brianfeucht ,
Thank you for reporting,
We will look how option and select was validated before we applied our latest changes.
Best Regards,
Jonathan

Help us to support this library: Donate

Hello @brianfeucht ,
The previous version of HAP was returning the following error: End tag </option> is not required
The expected error is more about the SELECT tag is missing.
I'm not sure for now if we want to start to handle this kind of error or not since this library doesn't really currently handle it.
We will for sure try to do it in 2018, but I will mark this request as nice to have for now.
Best Regards,
Jonathan

Help us to support this library: Donate

@JonathanMagnan for what is it worth, build 1.5.5 returns a parsing error for these cases.
This is blocking us from converting projects to .NET Standard.  Something about the 1.5.5 build causes us to get this error after upgrading a dependent project to .NET Standard 2.0 (the project throwing this has the HtmlAgilityPack added as a nuget package):
error CS0012: The type 'HtmlNode' is defined in an assembly that is not referenced. You must add a reference to assembly 'HtmlAgilityPack, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.

After upgrading to 1.6.6 the build error goes away but our unit tests depending on ParseErrors start failing.
I'm happy to help fix this.  Can you summarize why this stopped working between build 1.5.5 and 1.6.6?

Sorry I reread your previous comment.  I'll see what I can do from here to change our unit tests then


Thumbnails support

Hi there! Please consider adding thumbnails support to be used with slick slider plugin on Wordpress: https://wordpress.org/plugins/slick-slider/.
Thanks a lot!!!

I'm afraid it's out of the scope of Featherlight, sorry.


Failed to connect

once installed via HACS, I want to setup frigate via adding the integration.
it seems I am not able to connect.

The integration simply connects to a running instance of frigate. It does not run anything itself. Where are you running frigate?

You are totally right, thank you for the update. I got it working :)


[UBS Client] Change logic in cancelFormedOrder() and makeOrderAgain()

Change the logic in cancelFormedOrder() and makeOrderAgain() as described in User story #2865

Method cancelFormedOrder() should get back bonuses to user if order with status FORMED is canceled.
Method makeOrderAgain() should return information about bags and their quantity in DTO.


SavePath

hi, the argument type "SavePath" is not recognised somehow? do i have to import something other then spock?
thanks in advance!

Seems like the import shim got lost in one of the last commit. Fixing real quick. Sorry!

https://github.com/fidelity/spock/releases/tag/v2.4.2
This should fix the issue. Will be up on PyPi in a moment to pip install


Update README.rst

Complete this sentence
THIS PULL REQUEST __ [IS/IS NOT] __ READY TO MERGE
Feature or improvement description

Related issue, if one exists

Impacted areas of the software

Additional supporting information

Test results, if applicable

Thanks for catching this and submitting the fix @IAbda!


Allocation failures on macOS.

For my renderer I wanted to use vma to deal with my allocations. However, it seems that this is broken on macOS.
I am on big sur running under xcode 12.5. Many of my allocations fail with "CPU memory allocation failed.", and reverting the change from: https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator/pull/137, specifically going back to the old alignment behaviour which is used on older macOS version, resolves the allocation failures.

The library is developed mostly on- and for Windows PC. Unfortunately I don't have a development environment for MacOS. Any suggestions about how to fix this problem are welcome.

OK, I merged that pull request. Thank you.

@nico fyi, your changes were reverted in master earlier this year. I'm trying to update the integration we use and noticed this. Any ideas on what could be happening?

@phuang fyi


(storage): move from github.com/pkg/errors to 'errors' and 'fmt'

The package https://github.com/pkg/errors is not maintained anymore.
This PR replaces https://github.com/pkg/errors with official errors and fmt golang packages in storage package
Signed-off-by: Matthieu MOREL<EMAIL_ADDRESS>

Thanks!


Access Vue instance with typescript composable

Hi, I have an application with socket.io implementation with vue-socket.io-extended library.
Now. In Vue2 i have a file mixins.js with the mixins of my app. And I can access the properties of the socket like this.$socket.client.id
Something like this:
// Mixins.js file

export const myMixins ={
methods:{
async update() {
......
      const idSocket = this.$socket.client.id;
.........
    },
}
}

Now in Vue3 with typescript, I have the file Mixins.ts
// Mixins.ts file

const myMixins = () => {

const  update = async ()  => {
......
      const idSocket = this.$socket.client.id; -> the Vue instance is not recognized with "this".
.........
    }

return {update}

}

export default myMixins;

What is the closest approximation to be able to do the same process in Vue3 with TypeScript and Composables?

Please take usage questions to chat.vuejs.org, stack overflow etc.
As a hint, you are likely looking for the ComponenrPublicInstance type.


What's the diffenence between image tracking and marker tracking?

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Please, read the README before opening pull requests. This repo is not maintained anymore. Please open issues on the new repository: https://github.com/AR-js-org/AR.js. Thank you!


[connectors-ui] Request info about not enabled connector with Hubspot

User story
As a User
I want to request info about a connector that is available somehow, but I can not use now (because it is not enabled to me, it's out of my plan, beta...)
So that I can use it ASAP
Use this table as a guide: https://docs.google.com/spreadsheets/d/1b_7BxwpR7wvn3KfdJ5q-IjT6FPxVyUcI-ffmh1dNndk/edit#gid=0
Tasks:

[x] Define request method in hubspot --> @alonsogarciapablo See https://github.com/CartoDB/product/issues/496 for reference
[x] Check isConnectorEnabled and any other check we must do in order to describe the cause of it not being available --> @alejandraarri
[x] Implement request & confirmation --> @alejandraarri (e: 0.5 points)

Acceptance
Do connect to a branch at staging
Then try to add a new dataset of a disabled connector
Verify You have a proper message + an option to request the enablement.
Verify 2 PM can check we receive a request, identifying the Client / the Connector / the type of request = 'Enable'

cc/ @alejandraarri
Does it make sense to do this FIRST?

Which connectors?
Is it valuable?

Closing as the acceptance has been successfully done. 🎉 https://github.com/CartoDB/cartodb/pull/15281#issuecomment-561223291


Generalisze_Absolute_Pose usage

Hi there,
First of all, thank you for sharing this code.
Having such a python level control of COLMAP is exactly what I am looking for!
I am particularly interested in using rig_absolute_pose_estimation(), but I am not sure I understand correctly the required inputs.
In my case, I start with:

N rgb images
N cameras world transforms (coming from ARKit)
N camera intrinsics (coming from ARKit)

My biggest problem is to understand what 2d points and 3d points are expected:

I can generate 2d points from feature extraction per rgb image (using SuperPoint for example)
I can match 2d points across images to create pairs (using SuperGlue for example)
I can compute 3d points from these pairs of 2d points by triangulating using ARKit transforms
But I am not sure how to feed rig_absolute_pose_estimation() with these inputs

If you could provide a small example illustrating how to prepare 2d points and 3d points, it would be very useful
Thanks in advance,
PP

I do not really understand why you want to use the generalized absolute pose estimation. In general, GPnP is used for localizing a rig with known calibration (intrinsics and relative poses between the cameras of the rig) inside of a 3D world map. In your case, you already have these world transforms (from ARKit) and you only have a single iPhone / iPad camera not a rig (unless you treat the whole trajectory as a rigid rig, but that will have problems with drift).
If you, for instance, want to register your iPhone trajectory with respect to another 3D map, that is where the 3D points for GPnP will come from - you will have to establish correspondences between the images in the current trajectory and the images in the reference model and the lift the keypoints from the reference model to 3D using e.g. a sparse SfM model or a lidar scan / mesh.

Hi Mihal,
Thanks for the quick answer.
I should have explained what I am trying to achieve:

I have a recorded AR session composed of a set of synchronised images, extrinsics and intrinsics
I can extract visual features from images and pair features across images

My purpose is to use the bundle adjustment features of Colmap to refine the ARKit extrinsics that can sometime drift, especially in the scenario of closing loops.
I want to use the extrinsics from ARKit as initialisation for the bundle adjustment.
I would like to avoid having to deal with the colmap dataset
How would you recommend to use pycolmap to achieve this?
Thanks in advance,
Pierre

PyCOLMAP currently has very limited functionality - we only have bindings for localization purposes: single image pose estimation, rig pose estimation, and relative pose (E / F). There are people working on integrating mapping as well (https://github.com/mihaidusmanu/pycolmap/pull/20), but it might take a while until it is available.
However, for your task, you can simply run from the command line colmap point_triangulator to triangulate a 3D model from the ARKit poses and intrinsics followed by colmap bundle_adjuster to refine the poses and intrinsics . Please refer to https://colmap.github.io/faq.html#reconstruct-sparse-dense-model-from-known-camera-poses for more details regarding the point triangulator.

I wish you answered the original question, since I'm also confused regarding the inputs of rig_absolute_pose_estimation.
There's a list of lists of 3d points.  And a list of lists of 2d points.  If I had 2 cameras, left and right would the first 2d list be left keypoints, and 3d would be the corresponding original 3d,  and second list the right 2d points with corresponding 3d in the original?
Or do all the keypoints have to be related somehow (left and right match up)?

The parameters are lists of lists of 2D/3D points, each inner list corresponding to a camera. There is no consistency needed between cameras. In your case points2D = [points2D_left, points2D_right] and points3D = [corr_points3D_left, corr_points3D_right].
You can check out the implementation for more details https://github.com/colmap/pycolmap/blob/master/estimators/generalized_absolute_pose.cc#L298-L310

This is perfect, thank you.


It loads the URL of Page so does not work with Responsive Modal window. Please do something for it.

I am trying to use this in my google sheets to save all my emails in google drive so there is an addon in google sheets which save emails automatically but I have to click on the run button manually to save 20 emails in every one minute. So I tried to use this Auto click, it has everything I want time interval and where to click but the problem is it reloads the page whenever it has to start so that addon modal disappears everytime the page reloads. So what i need is basically i will open the google sheet and that addon in the same window and fill in the auto click detail about which button has to be clicked for a specific period of time and time interval. And without reloading the page it will start doing the process. So if that is possible then please do it. My heart appreciation for you.

You can keep the repeat interval little longer so extension will retry after that much specific interval of time. Also you can email us your scenario so we can figure out how we can help you.


NoSuchMethodError when trying to open Shell

[centos@leader1 ~]$ accumulo shell -u root
Loading configuration from /home/centos/install/accumulo-2.0.0/conf/accumulo-client.properties
Exception in thread "shell" java.lang.NoSuchMethodError: java.nio.ByteBuffer.rewind()Ljava/nio/ByteBuffer;
	at org.apache.accumulo.core.client.security.tokens.PasswordToken.setPassword(PasswordToken.java:140)
	at org.apache.accumulo.core.client.security.tokens.PasswordToken.<init>(PasswordToken.java:61)
	at org.apache.accumulo.core.conf.ClientProperty.getAuthenticationToken(ClientProperty.java:280)
	at org.apache.accumulo.shell.Shell.config(Shell.java:326)
	at org.apache.accumulo.shell.Shell.execute(Shell.java:513)
	at org.apache.accumulo.start.Main.lambda$execKeyword$0(Main.java:129)
	at java.lang.Thread.run(Thread.java:748)

This was after the disk filled up running CI for 2 days.  The Master node wasn't full though, which is where I tried running the shell.  This was from the RC-0 branch so its possible I built with Java-11.  And I believe the pom builds for java 8.
Extracting the core jar:
file org/apache/accumulo/core/Constants.class
org/apache/accumulo/core/Constants.class: compiled Java class data, version 52.0 (Java 1.8)

OK this was definitely built using
Build-Jdk: 11.0.3
and I used mvn clean package

This is now fixed in 2.0.0-SNAPSHOT

@milleruntime When you say it is fixed in 2.0.0-SNAPSHOT, do you mean that it is fixed when Build-Jdk is 11 and runtime JVM is 8?

@milleruntime When you say it is fixed in 2.0.0-SNAPSHOT, do you mean that it is fixed when Build-Jdk is 11 and runtime JVM is 8?

Yes

@milleruntime When you say it is fixed in 2.0.0-SNAPSHOT, do you mean that it is fixed when Build-Jdk is 11 and runtime JVM is 8?

Yes

Weird. Unless I'm misunderstanding something (entirely possible), then Java 11 may have produced different byte code with, and without, the -release 8 option, even though -source 1.8 and -target 1.8 were specified and the animal-sniffer enforcer rule verified the compilation results against Java 1.8. That's very strange, but if it works with the -release 8 option (which is now automatically added by a profile which is activated when building with javac 9 and later), then I guess all is well.


Can I use UTXOs from different addresses?

I am a beginner of developing bitcoin.
I explained to my boss , it's impossible to use UTXOs from different addresses because due to different pvriverty keys are signed it will fail in script OP_EQUALVERIFY, bu he still wants me to do it.
Is it possible to use UTXOs from different address with different priverty keys in the api?If no is there any other way to do it?

Yes.

@dabura667 , sorry, I still don't understand how can I do this, Are there any articles about this?
I search 'multi UTXO from different address' 'different addresses UTXO' and so on in Google, but can't get any useful result.

There are no specific articles about it, no.
Just sign with two keys.
Did you try?
If so, show us your code. Use some testnet coins. Give us the utxo info.

@dabura667 sorry, I make a mistake ,get wrong priverty key to sign .


Filter view issue

HI,
When you selected view by Group Results by Policy or Group Results by Category and didn't select any category or policy that displays empty

When you selected any policy or catagory then it works

Seems, you don't send all into query

Thanks I will check it.

I fixed it with the release v1.6.3, so you can try it when the build is done with the image.tag 1.6.3

I fixed it with the release v1.6.3, so you can try it when the build is done with the image.tag 1.6.3

Thanks, it works as expected


all: expose the rest api response?

my cloud application was using the NodeJS bindings of Google Cloud API, but for reasons of execution performance and better utilize multi-core CPU, some components have been re-written in Go, but with the Go bindings of Google Cloud API, I feel the major shortage is the access to raw api response from the GCloud's REST API, for example, with Node version's job.get I can always access the apiResponse object
https://googlecloudplatform.github.io/google-cloud-node/#/docs/bigquery/0.8.0/bigquery/job?method=get
job.get(function(err, job, apiResponse) {
  if (!err) {
    // `job.metadata` has been populated.
  }
});

# or with ES6 promise style:

job.get()
.then(( [ job_, apiResponse ] ) => {
   // use the apiResponse, to get the apiResponse.statistics or many other fields
})
.catch(err => ...)

With Go binary of same bigquery, from https://godoc.org/cloud.google.com/go/bigquery I see I can only get this much information from the Job, get the string id, or wait the job is till Done, or read job query results;
I believe both are just wrapping the REST API https://cloud.google.com/bigquery/docs/reference/rest/v2/jobs with Go binding without access to the raw apiResponse, it's hard to get statistics and like many other fields, users have to wait #347 fixed to get the statistics, for information in other fields, may have to wait another PR to get;
Also, if upstream BigQuery REST API keeps changing to add more features in api response, this Go language binding has to to make code changes to adapt; Versus in NodeJS it's just exposing apiResponse for user to interpret whatever it changes
So question to this google-cloud-go repo maintainers, is it possible to expose the raw apiResponse for the better flexibility (as in NodeJS) ?
type Job
  func (j *Job) Cancel(ctx context.Context) error
  func (j *Job) ID() string
  func (j *Job) Read(ctx context.Context) (*RowIterator, error)
  func (j *Job) Status(ctx context.Context) (*JobStatus, error)
  func (j *Job) Wait(ctx context.Context) (*JobStatus, error)
type JobStatus
  func (s *JobStatus) Done() bool
  func (s *JobStatus) Err() error

from https://cloud.google.com/bigquery/docs/reference/rest/v2/jobs
  "statistics": {
    "creationTime": long,
    "startTime": long,
    "endTime": long,
    "totalBytesProcessed": long,
    "query": {
      "queryPlan": [
        {
          "name": string,
          "id": long,
          "waitRatioAvg": double,
          "waitRatioMax": double,
          ...

We don't want to expose that type.
It looks like #347 is moribund, so I'll take ownership of it and try to make progress.

Clarifying: we don't want to expose it because it's an implementation detail. Our BigQuery client won't always be implemented on top of the HTTP/JSON client.

We don't want to expose that type.
Clarifying: we don't want to expose it because it's an implementation detail.

That can be understood as Go is not as flexible as Javascript (NodeJS) on JSON handling? In fact the NodeJS binding is facing the scenario here, bottom layer implementation detail could be over HTTP, or could be over gRPC, NodeJS is handling both well, and I don't think Go binding have to deal with more details than NodeJS binding when interacting same BigQuery server, over either HTTP/REST API or gRPC;
and the Node binding is intentionally exposing raw api Response to tackle some problems like GoogleCloudPlatform/google-cloud-node#1681
I hope in Go can have same level of flexibility.

Go is typed, and the gRPC and HTTP/JSON layers use different types. To hide the implementation, we have to wrap or translate the types into a type at the client layer.

I believe the GCloud Nodejs Client library is facing the same BigQuery (and other google cloud services) servers and it's handling both gRPC and HTTP/JSON well, and providing library users a unified apiResponse object, in the doc you can see all bigquery calls have the apiResponse in the callback parameter
So in Go language, I believe there should be some way to represent the raw api response in some type,
for example in the JSON api response how about expose the raw api response in the json.RawMessage type ? https://golang.org/pkg/encoding/json/#RawMessage it's just purely the []byte type to show me the bytes of api response; I'm not knowing enough details about gRPC, but how is google-cloud-node library archived that?
my app is in a state when some parts need better utilizing all available CPU cores, I want to convert the code in Go, for better execution performance because Nodejs is only good for IO-bound applications; but the google-cloud-go library isn't so good so flexible as google-cloud-node, many pending issues (#347 #110 #108 and others) here are road-blockers of turning all code into Go;
this one #554 to expose raw api response is something for users can work around even google-cloud-go library is not doing any translating the type into some specific type; hope it helps to be Future-Proof
the other thing is could you ask Google put more developer resources to build this library better? some issues here pending over 2 years doesn't make sense

We'll be focusing on improving the BigQuery client over the next couple of months.


Update ruff settings

Description
To avoid warnings about deprecated settings:
warning: The top-level linter settings are deprecated in favour of their counterparts in the `lint` section. Please update the following options in `pyproject.toml`:
  - 'extend-select' -> 'lint.extend-select'
  - 'ignore' -> 'lint.ignore'
  - 'select' -> 'lint.select'
  - 'flake8-pytest-style' -> 'lint.flake8-pytest-style'
  - 'pydocstyle' -> 'lint.pydocstyle'

Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[x] Configuration Update
[ ] Bump-up dependent library

To avoid warnings about deprecated settings:

Why wouldn't we fix this?

Before this fix: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_lightspeed-service/471/pull-ci-openshift-lightspeed-service-main-verify/1760396682211627008/artifacts/test/build-log.txt
After this fix: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_lightspeed-service/472/pull-ci-openshift-lightspeed-service-main-verify/1760411628320329728/artifacts/test/build-log.txt

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (8f46f1d) 94.83% compared to head (c985f2b) 95.83%.
Report is 22 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #472      +/-   ##
==========================================
+ Coverage   94.83%   95.83%   +0.99%
==========================================
  Files          36       43       +7
  Lines        1181     1368     +187
==========================================
+ Hits         1120     1311     +191
+ Misses         61       57       -4

This is the fix. So the Ruff will be happy again.  Not fixing them
you said To avoid warnings about deprecated settings: rather than To *fix* warnings about deprecated settings:
so that's why i thought that (avoid vs fix)
/lgtm /approve

yup sorry about that bad wording. That's sign that it's too late here ;)


Post process material for camera

Hello folks,
I'm new to programming on the Unreal Engine. I want to create a post process material similar to the attached picture. It consists on a black rectangle drawn on the screen in Carla. From what I researched, I have to use some sort of sub_UV function and multiply the resulting pixels by 0. However, I cannot find a function to retrieve a small portion of all UVs. Any input would be very much appreciated. Kinds regards.

.

Wouldn't it be easier to just apply this to the generated images? Why do you need to do this in Unreal?

I need to see how disruptive this kind of thing is to trained network
models.
On Mon, 22 Oct 2018 at 16:40, Christopher Barber<EMAIL_ADDRESS>wrote:

Wouldn't it be easier to just apply this to the generated images? Why do
you need to do this in Unreal?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/carla-simulator/carla/issues/893#issuecomment-431872594,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQUNuSZhQV2rOc7Cm5HzRgSAvgL_vQ5cks5uneb1gaJpZM4XyjWo
.

Sure, but you can still do this to the generated rgb images before passing to your network. There is no need to do it in Unreal.

I'd like to do it in unreal, as I can train existing networks and later
compare how networks trained specifically for this perform.
On Mon, 22 Oct 2018 at 18:17, Christopher Barber<EMAIL_ADDRESS>wrote:

Sure, but you can still do this to the generated rgb images before passing
to your network. There is no need to do it in Unreal.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/carla-simulator/carla/issues/893#issuecomment-431902424,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQUNuTT9_IyODckCcJbrobn78bmTgn2Uks5unf2UgaJpZM4XyjWo
.

Once again, there is no reason you cannot do that MUCH more easily outside of Unreal.  What would you do if you were working with real video cameras? Would you try to build a special video camera that blocks out part of the image?
I really would not waste your time with making special post-processing materials unless it is something that relies on material properties of the scene or takes significant advantage of the GPU pipeline.

Ok. I must do it in the complicated way, inside Unreal. If you can't help,
that's fine --- I'm hopeful somebody can.
For experienced Unreal users, this should be an easy thing to do. Fingers
crossed, someone will reply with useful information. Many thanks.
On Mon, 22 Oct 2018 at 18:50, Christopher Barber<EMAIL_ADDRESS>wrote:

Once again, there is no reason you cannot do that MUCH more easily outside
of Unreal. What would you do if you were working with real video cameras?
Would you try to build a special video camera that blocks out part of the
image?
I really would not waste your time with making special post-processing
materials unless it is something that relies on material properties of the
scene or takes significant advantage of the GPU pipeline.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/carla-simulator/carla/issues/893#issuecomment-431913332,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQUNufEIRW1zmDwyxjoNTebBtNDuH7Ddks5ungVfgaJpZM4XyjWo
.

I assume you have read the Unreal documentation on Post processing materials: https://docs.unrealengine.com/en-us/Engine/Rendering/PostProcessEffects/PostProcessMaterials
You want to create a post processing material that either passes through the SceneTexture post processing input or mask it out based on the angle between the camera direction and the direction to the pixel being rendered which you can compute from the CameraDirectionVector and the CameraVectorWS nodes.

Hi.
I know about the need for using SceneTexture and, multiplying the range of
pixels by 0 (black). However, I cannot come to find a way to select a
smaller portion of the whole screen UVs, which would correspond to the
rectangle.
I will try the CameraDirectionVector and the CameraVectorWS nodes
alternative, though.
On Mon, 22 Oct 2018 at 21:23, Christopher Barber<EMAIL_ADDRESS>wrote:

I assume you have read the Unreal documentation on Post processing
materials:
https://docs.unrealengine.com/en-us/Engine/Rendering/PostProcessEffects/PostProcessMaterials
You want to create a post processing material that either passes through
the SceneTexture post processing input or mask it out based on the angle
between the camera direction and the direction to the pixel being rendered
which you can compute from the CameraDirectionVector and the CameraVectorWS
nodes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/carla-simulator/carla/issues/893#issuecomment-431969429,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQUNuUlInQ8nM_Azu0ZCVElKXllQKmYuks5unilQgaJpZM4XyjWo
.

I think you probably want to use ScreenPosition.

Using ScreenPosition, to me, needs to break the UV float into its
individual components, then compare if these components are within your
boundaries. I cannot find a way to do multiple conditional branching in
Unreal. For example: If (x >= start_x and x <= end_x and y >= start_y and y
<= end_y) then 0, else 1. Zero (black) and 1 (no change) would then be
added to a multiply node.
On Tue, 23 Oct 2018 at 00:29, Christopher Barber<EMAIL_ADDRESS>wrote:

I think you probably want to use ScreenPosition.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/carla-simulator/carla/issues/893#issuecomment-432027371,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQUNuVg8wg940f_sCjpeymGqle7SrTxZks5unlTWgaJpZM4XyjWo
.

Use arithmetic operators in place of logical ones. If you are working with ones and zeros, multiply is equivalent to and.

Also, logical operations are really expensive in shaders, try to avoid them.

Hi. I want to implement a post process for dirt and dust on the camera. What's the easiest way to do that? Should I add some kind of noise to the trained neural network? I can see the default industry practice is to add gaussian noise when training CNN models. It's assumed this will eventually happen. I however do not know how camera occlusion (e.g. dirt) would be dealt with. There's this paper here: https://arxiv.org/abs/1807.06172. It does not use CARLA though.


GRUB Theme not installling even after Finding theme correctly on Fedora37

The Issue
After modifying my /etc/default/grub and installing using all of these commands:
sudo grub2-mkconfig -o /etc/grub2-efi.cfg
sudo grub2-mkconfig -o /etc/grub2.cfg
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
I haven't been able to install the theme, I'm getting the default black and grey grub menu.
My /etc/default/grub
GRUB_TIMEOUT="5"
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT="saved"
GRUB_DISABLE_SUBMENU="true"
#GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init rhgb quiet initcall_blacklist=simpledrm_platform_driver_init rd.dr>
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG="false"

GRUB_THEME="/usr/share/grub/themes/tartarus/theme.txt"

I don't know much about Fedora, so I may not be able to help you much, but most of the people I know who use this distro usually use the grub-customizer package because it usually gives many problems if not. You can try selecting the theme and doing the configuration you want there to see if it works.

Check if the theme directory (tartarus) placed correctly in the destination, in this case $ ls /usr/share/grub/themes/.

I've checked the destination, its there! and I've even tried installing using Grub Customizer still no luck :(


npm init does not forward options to create-wagmi

CLI options passed to npm init options are applied to npm exec. To forward options to create-wagmi, the command in the docs should include a --.
npm init wagmi -- --template next-with-connectkit

Here's a screenshot demonstrating the issue (the --template option is not getting passed to create-wagmi, hence the prompt)

(pnpm create seems to automatically forward options, not sure about yarn create)

Fixed! Thanks.


[SEDONA-212] Rework dependency management

Did you read the Contributor Guide?

Yes, I have read Contributor Rules and Contributor Development Guide

Is this PR related to a JIRA ticket?

Yes, the URL of the assoicated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-212. The PR name follows the format [SEDONA-XXX] my subject.

What changes were proposed in this PR?
Using the problem of shading to rethink how dependencies are managed. Definitely trying to start a discussion and this is a WIP, finally got the tests to pass.
The general way things are setup now is "everything is a provided dependency, except for python-adapter where everything is shaded". This presents a few problems mentioned in the ticket:

It's very difficult to deal with dependency conflicts if one of the conflicts is in a shaded jar. You can't simply exclude the transitive dependency
It's very difficult to actually use the package. What I assume most people do is default to just using the python-adapter module so they get all the things (assuming they don't have problems with the shading). This is very awkward, especially if you aren't using Python. For example, we purely use the SQL functions in the sql module, but without knowing what sub-dependencies I need, I just have to default to the python-adapter module so I have the dependencies I need.
The python-adapter module has all the dependencies shaded, plus they are still compile scope dependencies in the result pom, resulting in double including all the dependencies when using Java based build tools or the spark --packages option. This is a bug due to the resolved-pom-maven-plugin and the maven-shade-plugin not playing nice together, so the dependency-reduced-pom doesn't end up as the actual pom for the module.

Because of all that, I'm proposing a few changes in this PR:

Anything that should be a compile dependency is scoped as such, except for geotools for the licensing reasons.
Dependencies are defined in a dependencyManagement section in the parent pom instead of directly defining dependencies for all modules that might only be relevant to one. Each module includes just the relevant dependencies it needs.
Scala plugins are all opt-in to make it clear/sure that the common module does not have any odd Scala dependencies even for testing.
python-adapter still includes shading, but in a separate target used for the Python tests.

I did have to work through various exclusions to get the tests to work. I was able to remove the defining the jackson version for all testing purposes.
Questions to answer would be:

Is there any reason to actually publish a shaded module? Anything Spark related can either:

Java/Scala: use their Java build tool of choice to include the right dependencies in their subsequent jar
Python: use the --packages feature to automatically pull all required transitive dependencies

I don't know anything about Flink and if there is a use case for that needing a shaded module
What to do with the new edu.ucar module? It looks like it's in its own private repo, so for those behind a proxy that don't have access to every repo on the internet, this could cause dependency resolution to fail.

How was this patch tested?
Existing tests.
Did this PR include necessary documentation updates?

There may have to be documentation updates if this route is accepted, would need to look at what the current examples do.

@Kimahriman
Please feel free to correct me if I am wrong since I am not 100% confident about the current POM setting.

The reason why we provide a shaded jar for python-adapter is that some Sedona users actually manually download the jar from ASF dist and manually upload it to its environment. Since this step has no maven involved, a shaded jar will be helpful for them. This happens to both Scala/Java/Python users in Spark and Flink.
The majority of Flink users are using Java and pure SQL. Some of them might use Scala. Few of them are using Python.
I can create something like edu-ucar wrapper to bring it to the Maven Central. But I don't want to put it to compile scope because (1) it depends on the Google guava which might have incompatible API across versions (2) it is quite large (3.3 MB itself) and only a few people use it.

BTW, in Sedona doc, we explain that what dependency should be called if you want to use Sedona jar with others: https://sedona.apache.org/setup/maven-coordinates/#use-sedona-and-third-party-jars-separately
Your new proposal
Based on your proposal, users will now interact with the following jars. Can you please confirm?
All Spark / Flink dependency must be provided in any cases.
Spark users:

Scala/Java user option 1: use Maven to manage dependency

sedona-core: with some compile scope dependencies but not shaded
sedona-sql: with some compile scope dependencies but not shaded
sedona-viz: with some compile scope dependencies but not shaded
Users no longer need to manually add other dependencies (jts, geojson2jts, geotools-wrapper). geotools-wrapper is now a compile scope dependency.

Scala/Java user option 2: manually download jar and upload jar, no Maven

sedona-python-adapter: a shaded jar like what we have now
geotools-wrapper: a shaded jar that consists of all geotools dependency

Python user option: follow Scala/Java user option 2

Flink users:

Scala/Java user option 1: use Maven to manage dependency

sedona-core: with some compile scope dependencies but not shaded
sedona-flink: with some compile scope dependencies but not shaded

Scala/Java user option 2: use Maven to manage dependency

sedona-python-adapter: a shaded jar like what we have now
geotools-wrapper: a shaded jar that consists of all geotools dependency

Final thoughts
It was a headache for me to get the POM right for publishing a release. Before we accept such a big change to the POM, we need to test by publishing SNAPSHOTS (https://sedona.apache.org/community/snapshot/) and try with the existing projects in example folder

Yeah I think that mostly covers it. We can keep a shaded jar for Spark and/or Flink for people who need it, and that can either be the python-adapter module or a new specifically shaded module since there's no reason the python-adapter needs to be shaded and it might be better to have an explicit module named "shaded". But for people who are using dependency management systems (either by building custom jars or using --packages in Spark), which should be what most people are doing and the common case, we use properly compile scoped dependencies where possible, while providing whatever shaded artifacts we need for the edge cases where users don't have the network connections available to load all the dependencies automatically.
Definitely will need to do a lot of test publishing with this to verify the resulting poms, but I hope it will start make the dependencies easier to manage and understand over time, and be less likely to have issues with conflicting scala versions and such.
I am not a pom or maven expert by any means (learned a lot of this as I went), so definitely looking for any feedback. This is how I see a lot of other projects structured, and I tried to pull a lot of things from how the Spark poms themselves were structured.

Nice work! Over all this looks good to me. Just a few notes:

Dependencies with compile scope are inherited. So python-adapter doesn't need to depend on sql, core and common. Only sql is needed. Same goes for the other modules. Maybe there is a reason why you had to repeat the dependencies that I'm missing. If so, ignore this comment :)
I think that separate shaded modules is a good idea. It would be nice to be able to opt out of shaded modules if you want to. In python and R projects you can just add the --packages flag to spark-submit or set the configuration property spark.jars.packages. Then spark will download any artifacts and their dependencies for you. Shading is never needed in Spark, regardless of which language you use, but it might be convenient depending on how you deploy your jobs. See https://spark.apache.org/docs/latest/submitting-applications.html#advanced-dependency-management

If you're not that familiar with maven, the command mvn dependency:tree is a nice way to verify transitive dependencies.
Verifying the shaded artifacts is harder. I would probably run jar -tf sedona-spark-shaded.jar |  sort before and after this patch and diff the output.
@jiayuasu publishing snapshots sounds lika a good idea

Dependencies with compile scope are inherited. So python-adapter doesn't need to depend on sql, core and common. Only sql is needed. Same goes for the other modules. Maybe there is a reason why you had to repeat the dependencies that I'm missing. If so, ignore this comment :)

This was mostly intentional, I tried to include everything that was directly imported by the package to be more explicit, and not rely on expecting transitive dependencies to be there. That being said I'm sure this isn't 100% true across the whole codebase right now. I feel like there are maven plugins you can use to check that potentially?
For the shaded modules do you think completely separate modules, like sedona-spark-shaded and sedona-flink-shaded? Or just like a classifier for the python adapter like this currently has I think of org.apache.sedona:sedona-python-adapter-3.0_2.12:1.3.1-incubating-SNAPSHOT:shaded

This was mostly intentional, I tried to include everything that was directly imported by the package to be more explicit, and not rely on expecting transitive dependencies to be there. I feel like that's the recommended practice? That being said I'm sure this isn't 100% true across the whole codebase right now. I feel like there are maven plugins you can use to check that potentially?

I think you are right. Sorry! I checked spark. They include dependencies explicitly. In https://github.com/apache/spark/blob/master/sql/core/pom.xml the dependency on sql-catalyst already pulls in core but they have listed it explicitly any way.

For the shaded modules do you think completely separate modules, like sedona-spark-shaded and sedona-flink-shaded? Or just like a classifier for the python adapter like this currently has I think of org.apache.sedona:sedona-python-adapter-3.0_2.12:1.3.1-incubating-SNAPSHOT:shaded

For shading I'm thinking separate modules. I don't know what the pros and cons are but it feels more natural to me. With qualifiers you probably have to build twice to get both the shaded and non-shaded jars.

@Kimahriman @umartin Thank you both for the great suggestions.
@Kimahriman Let's proceed with your proposal. In addition, let's create two completely separate modules sedona-spark-shaded (for both Scala 2.12 and Scala 2.13) and sedona-flink-shaded (only for Scala 2.12)
After this, Adam you can try to publish SNAPSHOTs to ASF repo. You are a Sedona PMC so you have the permission to upload SNAPSHOTs. I can provide some instruction and scripts for you to upload SNAPSHOTs.

Got an initial version of the shaded modules working. Need to see if tests still pass (mostly python ones, using the shaded spark module to run those now). After seeing how that works I'll look into publishing snapshots

I think I have this in a good place and builds working, except for the examples. It looks like those don't use any local builds of sedona to build the examples, and just relies on a snapshot version being published? Is that right?
Ready for anyone to review, and I can publish a snapshot version whenever. Do I just need to add a distribution management section to the pom temporarily? I think I have all my creds setup correctly.
Only other thing would be updating docs, could try to do that here or in a separate PR.

Couriser dependencies for each module now:
common:
com.fasterxml.jackson.core:jackson-annotations:2.12.2:default
com.fasterxml.jackson.core:jackson-core:2.12.2:default
com.fasterxml.jackson.core:jackson-databind:2.12.2:default
org.apache.sedona:sedona-common:1.3.2-incubating-SNAPSHOT:default
org.locationtech.jts:jts-core:1.19.0:default
org.wololo:jts2geojson:0.16.1:default

core:
commons-lang:commons-lang:2.6:default
org.apache.sedona:sedona-common:1.3.2-incubating-SNAPSHOT:default
org.apache.sedona:sedona-core-3.0_2.12:1.3.2-incubating-SNAPSHOT:default
org.locationtech.jts:jts-core:1.19.0:default
org.scala-lang:scala-library:2.12.15:default
org.wololo:jts2geojson:0.16.1:default

sql:
commons-lang:commons-lang:2.6:default
org.apache.sedona:sedona-common:1.3.2-incubating-SNAPSHOT:default
org.apache.sedona:sedona-core-3.0_2.12:1.3.2-incubating-SNAPSHOT:default
org.apache.sedona:sedona-sql-3.0_2.12:1.3.2-incubating-SNAPSHOT:default
org.locationtech.jts:jts-core:1.19.0:default
org.scala-lang:scala-library:2.12.15:default
org.scala-lang.modules:scala-collection-compat_2.12:2.5.0:default
org.wololo:jts2geojson:0.16.1:default

viz:
commons-lang:commons-lang:2.6:default
org.apache.sedona:sedona-common:1.3.2-incubating-SNAPSHOT:default
org.apache.sedona:sedona-core-3.0_2.12:1.3.2-incubating-SNAPSHOT:default
org.apache.sedona:sedona-sql-3.0_2.12:1.3.2-incubating-SNAPSHOT:default
org.apache.sedona:sedona-viz-3.0_2.12:1.3.2-incubating-SNAPSHOT:default
org.beryx:awt-color-factory:1.0.0:default
org.locationtech.jts:jts-core:1.19.0:default
org.scala-lang:scala-library:2.12.15:default
org.scala-lang.modules:scala-collection-compat_2.12:2.5.0:default
org.wololo:jts2geojson:0.16.1:default

python-adapter:
commons-lang:commons-lang:2.6:default
org.apache.sedona:sedona-common:1.3.2-incubating-SNAPSHOT:default
org.apache.sedona:sedona-core-3.0_2.12:1.3.2-incubating-SNAPSHOT:default
org.apache.sedona:sedona-python-adapter-3.0_2.12:1.3.2-incubating-SNAPSHOT:default
org.apache.sedona:sedona-sql-3.0_2.12:1.3.2-incubating-SNAPSHOT:default
org.locationtech.jts:jts-core:1.19.0:default
org.scala-lang:scala-library:2.12.15:default
org.scala-lang.modules:scala-collection-compat_2.12:2.5.0:default
org.wololo:jts2geojson:0.16.1:default

flink:
com.fasterxml.jackson.core:jackson-annotations:2.12.2:default
com.fasterxml.jackson.core:jackson-core:2.12.2:default
com.fasterxml.jackson.core:jackson-databind:2.12.2:default
commons-lang:commons-lang:2.6:default
org.apache.sedona:sedona-common:1.3.2-incubating-SNAPSHOT:default
org.apache.sedona:sedona-core-3.0_2.12:1.3.2-incubating-SNAPSHOT:default
org.apache.sedona:sedona-flink_2.12:1.3.2-incubating-SNAPSHOT:default
org.apache.sedona:sedona-sql-3.0_2.12:1.3.2-incubating-SNAPSHOT:default
org.jheaps:jheaps:0.14:default
org.locationtech.jts:jts-core:1.19.0:default
org.scala-lang:scala-library:2.12.15:default
org.scala-lang.modules:scala-collection-compat_2.12:2.5.0:default
org.wololo:jts2geojson:0.16.1:default

spark-shaded:
org.apache.sedona:sedona-spark-shaded-3.0_2.12:1.3.2-incubating-SNAPSHOT:default

flink-shaded:
org.apache.sedona:sedona-flink-shaded_2.12:1.3.2-incubating-SNAPSHOT:default

These should be what get included by using the --packages option in spark or by building your own fat jar

@Kimahriman I have updated the example projects. If you pull the latest change, it will pass the CI.
I suppose you have read: https://sedona.apache.org/1.3.1-incubating/community/release-manager/
Now you can try to publish the snapshots: https://sedona.apache.org/1.3.1-incubating/community/release-manager/
Once you publish the snapshots, you can try them in the example projects by using sedona-1.3.2-incubating-SNAPSHOT as the version.

@Kimahriman I have updated the example projects. If you pull the latest change, it will pass the CI.
I suppose you have read: https://sedona.apache.org/1.3.1-incubating/community/release-manager/
Now you can try to publish the snapshots: https://sedona.apache.org/1.3.1-incubating/community/release-manager/
Once you publish the snapshots, you can try them in the example projects by using sedona-1.3.2-incubating-SNAPSHOT as the version.

Published 1.3.2-incubating-SNAPSHOT to the snapshot repo

@Kimahriman Did you try the SNAPSHOT in example projects?

Had an old shaded jar in my spark jars folder still, examples are working off of the published snapshot versions now

For what it's worth and from a user's perspective, I think this looks awesome and I love the idea of an explicitly named shaded jar over the python adapter one. I just noted several comments about only needing Spark for dependency management (like using --packages), and wanted to advocate for projects that cannot use Spark in that way.
The simplest example is a cluster that is disconnected from the internet in general and can only rely on the jars in the local system. In that case, a shaded jar is a very pleasant thing to have. Especially when the build pipeline is only setup for python or R.


Update graveyard.json - Add Stream, Live Events and Yammer

Hi @fabianoriccardi I added three entries: Yammer, Teams Live Events and Stream (classic).

2 issues: dateClose of Stream seems wrong (should be February and not April) and I cannot find any close date for Yammer in your links (neither in the web).

Hi Fabiano,
good catches.
Stream has an inconsistency in documentation. The first link has February,
the second with the timeline for decommissioning has April and is the one
accurate.
Yammer has date only available in internal documents - can share a
screenshot if needed but cannot be linked directly - and public documents
just refers to "within 2023".
Best regards,
Raffaele Sgherri
On Fri, Dec 15, 2023, 18:41 Fabiano Riccardi @.***>
wrote:

2 issues: dateClose of Stream seems wrong (should be February and not
April) and I cannot find any close date for Yammer in your links (neither
in the web).
—
Reply to this email directly, view it on GitHub
https://github.com/fabianoriccardi/killed-by-microsoft/pull/95#issuecomment-1858247545,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEUR3B7QAB4EF27ZASDUNSLYJSDUJAVCNFSM6AAAAABAWQWA7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJYGI2DONJUGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

That's fine, and if they should change any date in their roadmap, we can quickly fix it.


Genfors blank votes

Updated the genfors-app, so it works again. Changed how blank votes affect the result, and how blank votes are represented on the page. Also changed vote verification so it disappears if option is changed.

Also, have a look at the failing Flake8 tests :)

Calculation of votes does not yet account for (/subtract) blank votes.


Limits docker agent requirement for build

Thanks for the idea @lemeurherve.
Description
This is only to make sure that we are getting a docker agent when we building the JAR binary of the application.

Testing done
None. This is a change in the CI build instructions.
### Submitter checklist
- [ ] If an issue exists, it is well described and linked in the description
- [x] The description of this pull request is detailed and explain why this pull request is needed
- [x] The changeset is on a specific branch. Using `feature/` for new feature, or improvements ; Using `fix/` for bug fixes ; Using `docs/` for any documentation changes.
- [ ] If required, the documentation has been updated
- [ ] There is automated tests to cover the code change / addition or an explanation why there is no tests in the description.

I tried to remove the docker agent with a replay on infra.ci.jenkins.io but unfortunately tests are using Docker.

I would close this PR as moving the agent declaration from the pipeline to the main stage doesn't change anything AFAIK.


[EDA] Prevent Deletion of Address Record if There are Associated Child Records

Note: FOR INTERNAL USE ONLY. For support questions, please use the EDA Chatter group in The Power of Us Hub.
For feature requests, please use the Ideas tab in The Power of Us Hub.

Do you want to request a feature or report a bug?
Feature

What is the current behavior?
When a user attempts to delete an Address record that is associated with child records, the system deletes the address record, leaving the child Contact and/or Account records intact with the Current Address field cleared.

What is the expected behavior?
When a user attempts to delete an Address record that is associated with child records, the system will utilize a new custom setting field (Prevent Address Deletion) to determine whether to allow the deletion.  If selected, attempts to delete an Address record with associated child records will be blocked and an error message displayed to the user.  If unchecked, the functionality will remain the same as outlined in the current behavior section.

What is the motivation / use case for changing the behavior?
From previous github requests and investigations of deletion of parent records with child records, it was determined that we need to implement the functionality to allow users the ability to control if an Address record with related child record can be deleted.

Acceptance Criteria

Given: The “Prevent Address Deletion” checkbox in Hierarchy Settings (Custom Setting) is unchecked.

When: A user clicks “Delete” button on an Address record that has child related records.

Then: The Address record is successfully deleted, no error message is displayed to the user and the child records are not deleted.

Given: The “Prevent Address Deletion” checkbox in Hierarchy Settings (Custom Setting) is checked.

When: A user clicks “Delete” button on an Address record that has child related records.

Then: An error message is displayed to the user and the user is unable to delete the Address record.

**lurch: attach W-040721

Tracking W-040721


masters statement in zone config is too strict

Hi,
It seems there is a parsing error on masters statement in zone declaration.
following this config : http://www.zytrax.com/books/dns/ch7/zone.html#masters
from bind9_parser import *
zone = """
zone "example.com" in {
    type slave;
    file "slave/example.com";
    masters mymaster {<IP_ADDRESS>;};
};
"""
result = clause_statements.parseString(zone)
print(result)

result is, as expected :
[['"example.com"', 'in', 'slave', '"slave/example.com"', ['mymaster', [['<IP_ADDRESS>']]]]]
but with
zone = """
zone "example.com" in {
    type slave;
    file "slave/example.com";
    masters {<IP_ADDRESS>;};
};
"""

I got a parsing exception :
pyparsing.ParseException: Expected {W:(ABCD...) | W:(ABCD...) | <master_name>}, found '{'  (at char 83), (line:5, col:13)
Also with
zone = """
zone "example.com" in {
    type slave;
    file "slave/example.com";
    masters port 1127 {<IP_ADDRESS>; <IP_ADDRESS> key zt-key; 2001:db8:0:1::15 port 1128;};
};
"""

that is the example from zytrax, I got
pyparsing.ParseException: Expected "{", found '1'  (at char 88), (line:5, col:18)
It appears that, after a masters statement, the parsers looks for a word, and a {, but description is optional, and other statements can be present.
Both 3 examples here are valid with named-checkconf bind tool.

OH, one other thing:  The EBNF syntax is drastically different between

zone-specific masters statement (introduced in v9.0)
top-level masters clause (introduced in v9.3)

EBNF for masters statement (inside the zone) is initially:
masters [ port ip_port ] { ip_addr; [ ip_addr; ... ] };

EBNF for masters clause (top-level) is (since v9.3):
masters <string> [ port <integer> ] { ( <masters> | <ipv4_address> [ port
    <integer> ] | <ipv6_address> [ port <integer> ] ) [ key <string> ]; ... };

Ergo
So, using the master label is only limited to the clause (top-level).
If you wanted to use the actual master label inside the zone, (that was defined at the top-level), then you would do this:
masters my_master_label { <IP_ADDRESS>; };

zone "example.test" {
    masters port 123 { my_master_label; };
};

I am closing this without a fix.


Setup Repo Actions and external tools

These repo uses the cookie cutter which offers a lot of tools.
We need someone (@MartinThoma or @Lucas-C) who has acces to the repo/ organization setting, to setup these tools.

[ ] Set codecov token for repo #62
[x] Activate/Setup dependabot
[x] Setup Release drafter
[ ] Please make sure the relase to pypi using gh action is configured as discussed in old repo
[ ] Setup Test Pypi

I enabled Dependabot:

Release drafter is already enabled: https://github.com/py-pdf/pypdf_table_extraction/actions/workflows/release.yml

Regarding CodeCov, I posted a comment there: https://github.com/py-pdf/pypdf_table_extraction/issues/62#issuecomment-2310762570

I've marked the test pypi as completed. As it is not being used in this repo.
As we work our way to a new release, it would be good to know if publishing to pypi is correctly setup.


Use SDR serial number?

Some systems have two (or more) RTLSDRv3 attached.
Some time back we have used rtl_eeprom -s to set each devices serial number. This helped the usual SDR software to use the correct device when they each started up.
With SDRReceiver is there a way to specify the dongle serial number in the ini file?
We'd like to use one dongle for C-Band and the other for L-Band.

Not at the moment but I have thought about it and will have a look at it. You can use multiple dongles as it is right now though, I have run 3 instances without issues. So long as you dont unplug or move the devices around my experience has been that they will keep the same index number in the dropdown. Currently I have 2 dongles running on one PC for 25E and 54W and the SDRs have the autostart options with dongle indexes 0 and 1 set. Has been working well for ages with everything auto starting on reboot.

finally had some time to add a few things so this is now an option, see readme for details.

This is fantastic. Thank-you very much.
I see in the readme that you are looking to tweak a few things for C-Band. Looking forward to that. All three of us C-Band guys (143E, 98W and 25E) have spent hours and failed to get SDRReceiver working on that band. We are all still using VAC and getting the usual BAD CRC errors.

Closing this one.


[Macros] "Expand" builtin macros for magic literals.

Introduce an experimental option BuiltinMacros that takes the magic
literals (#file, #line, #function, etc.) after type checking and
processes the original source for the expression using the build
syntactic macro system in the swift-syntax library. At present, the
result of expansion is printed to standard output, and type checking
is otherwise unaffected.
This serves primarily to make sure that, given a C++ AST node,
we can find the corresponding syntax node (as parsed by the new
parser) and perform expansion on it.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


Create a Name Service: OnInit

Code before "Test it",
"implements OnInit" should be removed.

Yes, either that or explain lifecycle hooks and override ngOnInit().


Auto Detection of Field Types

I can define auto type detection for timestamp as follows:
"timestampSpec" : {
     "format" : "auto",
     "column" : "ts"
}

In similar manner, I cannot detect field type via parseSpec. I mean:
{"ts":"2018-01-01T03:35:45Z","app_token":"guid1","eventName":"app-x","properties-key1":"123"}
{"ts":"2018-01-01T03:35:45Z","app_token":"guid2","eventName":"app-x","properties-key2":123}
Both properties-key1 and properties-key2 are indexed as String. I expect to index properties-key2 as Integer at Druid.
We should implement auto field type detection into Druid for a newly created field.
PS: I've started a conversation about this task at mail list and than created an issue for it: Druid Auto Field Type Detection

Currently, all fields are threaten as String when dimensions field is empty:

Schema-less dimensions
If the dimensions field is left empty in your ingestion spec, Druid will treat every column that is not the timestamp column, a dimension that has been excluded, or a metric column as a dimension. It should be noted that because of #658 these segments will be slightly larger than if the list of dimensions was explicitly specified in lexicographic order. This limitation does not impact query correctness- just storage requirements.
Note that when using schema-less ingestion, all dimensions will be ingested as String-typed dimensions.

However we should have work similar to that: Solr Schemaless Mode.

I've started to work on this issue. I have 3 possible solutions on undefined schema fields:

If value can be convertible to Float than convert to Float, otherwise try with Long, otherwise go with String.

If field name ends with _l, and is not defined at scheme, and a config value of schemeless mode is enabled then convert to Long, so on so forth.

Create a regex defined field. Accept a regex value and make transformation on it which is a generic solution of 2. i.e.:

{ "pattern": "*_l", "type": "long" },
{ "pattern": "*_f", "type": "float" }

@gianm what do you think?

Hi @kamaci, thank you for raising this issue.
I’m not sure what solution you are considering to implement. Are you thinking to pick one of them or support all of them?
Also, would you please write a proposal before you start implementation? It would make clear what your idea is and what you want to implement. You can write a proposal by opening a new issue and choosing the proposal template.

Hi @jihoonson
These are possible solutions. I can go with 3th one but I've wanted to talk about it before doing implementation. I can create a proposal with template.

+10000
Awesome!! : ) This feature is exactly what I was waiting for. I think the 3th option will be a good option for users

I've close this issue since I submitted https://github.com/apache/incubator-druid/issues/7255


Make the plot_3d_jumps plot rotatable in the browser

I think plotly can be a good candidate for this, but the matplotlib to plotly conversion function seems to be broken for this figure at the moment.
  File "/home/vikko/local_projects/GEMDAT/.venv/lib/python3.11/site-packages/plotly/matplotlylib/mplexporter/exporter.py", line 289, in draw_collection
    offset_order = offset_dict[collection.get_offset_position()]

The issue is well known and because of a deprecation in matplotlib: this very ugly fix works:
https://github.com/mpld3/mpld3/issues/477
But then again it does not seem to understand more than 2 dimensions, so this is not the way to go.
If we want to do this it is probably best to re-implement it fully in plotly (see also comment below)

I see that there is already an effort for this here: https://github.com/janosh/pymatviz#structure maybe we can somehow contribute there?

It's already rotatable in a jupyter notebook if you switch to an interactive backend ('notebook', 'ipympl').

Agreed, better to use a javascript/html renderer from the start. 3D in matplotlib is always laggy, whatever backend you use.
I also listed a few dedicated libraries here:
https://github.com/GEMDAT-repos/GEMDAT/issues/23#issuecomment-1619664566
Otherwise, the code for plotting the lattices / atom sites is quite trivial. So any generic renderer will work. It would be nice if it can also show volumes.

I tried it out at least in a jupyter-lab notebook, but I get no interactivity with:
%matplotlib widget
import matplotlib

from pathlib import Path

from gemdat import SimulationData, plot_all, plot
from gemdat.sites import SitesData
from gemdat.io import load_known_material
from gemdat.plots.jumps import plot_jumps_3d

data = SimulationData.from_vasprun(Path('vasprun.xml'))
extra = data.calculate_all(equilibration_steps=1250, diffusing_element='Li')

structure = load_known_material('argyrodite', supercell=(2,1,1))

sd = SitesData(structure)
sd.calculate_all(data=data, extras=extra)
plot_jumps_3d(sites=sd, data=data)

And %matplotlib notebook?

nope, might be my setup, but it really does not want to work

We should fix this in #23 then.


Add Section 8 voucher as a filter

See notes from meeting with HRD https://app.box.com/integrations/googledss/openGoogleEditor?fileId=848588914566&trackingId=3#
Maybe blocked on whether we have this data available in the backend?
Assigned to wrl@ to ask about this column, how do we filter

Safiya said that the data doesn't exist yet, this is a piece that will be collected by the property manager survey. I'm going to mark as blocked by the importing of that data and move this back to M12.

This functionality currently exists