Failure when executing AddIPPoolInSdaVirtualNetwork with dnacenter_sda_virtual_network_ip_pool

Prerequisites

[x] Do you have the latest Terraform provider version?
[x] Review the compatibility matrix before opening an issue.

Describe the bug
terraform apply of 'dnacenter_sda_virtual_network_ip_pool'  fails with Failure when executing AddIPPoolInSdaVirtualNetwork,
after waiting for a few minutes and running again terraform apply it works.
see below debugs:
first_run.txt
second_run.txt
Expected behavior
It should work with one run of terraform apply
Environment (please complete the following information):

Cisco DNA Center version and patch:  <IP_ADDRESS>
Terraform version: 1.4.6
Cisco DNA Center provider version: 1.1.4-beta
OS Version: MacOS 13.3.1

Also tested with 1.1.6-beta and have the same issue.

Hi @artur-tekieli
On DNAC version <IP_ADDRESS> +, the execution status changed from

FAILURE to failed
IN_PROGRESS to pending

We still use the previous status values, so we did not wait correctly for the execution to change.
I am currently working on a fix.

The new Terraform provider for dnacenter is up, v1.1.10-beta.
Please, try again with the new version.

Your Cisco DNA Center version is <IP_ADDRESS>; according to our Compatibility Matrix your "dnacenter" provider version should be 1.0.19-beta.
I recommend, however that you upgrade DNA Center to a newer release, at least for the following reasons.

There have been multiple improvements and fixes in DNA Center APIs
Our Terraform provider "dnacenter" development effort moves towards supporting the last DNA Center versions on the Compatibility Matrix (for now, <IP_ADDRESS>) rather than those below.

@artur-tekieli , update us if it works now, or ticket is going to be closed in next 24 hours due inactivity.


[Enhancement]: Improve Clarity of Instructions and Descriptions of Different Game Modes

Do you want to have the enhancement of existing game ? 😀 Describe yourself..
The current website lacks clear instructions and descriptions for various game modes, which can be confusing for new users.
https://github.com/GameSphere-MultiPlayer/PACKABUNCHAS/assets/153659573/ff53885b-fb36-4d92-a1da-78af278269da
Describe the solution you'd like
The game should offer clear descriptions for each game mode to ensure users understand the purpose and objectives of each mode.
I am a GSSoC'24 contributor and want to contribute to this issue.
Select program in which you are contributing
Other
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Could you please explain more what you want to do, if possible you can also add screenshot.

If you have any doubt you can directly send message on our discord (https://discord.gg/rZb46cCMmK), we have created separate channals for all projects...
Thank you :)

@Durgesh4993  The game offers various modes such as CLASSIC, PENTA, MIX, KIDS, and EZPZ. However, it currently lacks descriptions for these modes, leaving users uncertain about the features and gameplay each mode provides. Instead of only providing names, an "i" button (ⓘ) should be included. When users hover over the "i" button, it will display detailed information about each game mode. By adding these descriptions, users will be able to understand the differences and choose the mode that best suits their preferences, enhancing their overall gaming experience.


Number Parse not working

I'm trying to parse numbers but 1 comes up as 45.

Thanks for your report. Can you you create C# sample which reproduces the issue?

I think might be because of char.ToString();
This doesn't work
This gives me 50.
string value = "";
char toSetTo = (char)('1' + 1);
value += toSetTo;
Console.Log(value);
This Works
This gives me 2.
string value = "";
char toSetTo = (char)('1' + 1);
value += toSetTo.ToString();
Console.Log(value);

Thanks for test case. The issue was already reported and fixed
Issue: https://github.com/bridgedotnet/Bridge/issues/538
Commit: https://github.com/bridgedotnet/Bridge/commit/95f7d71f77bab261e2b8318391f67d99bb3f033f
The pull request is not merged yet with master branch.
The fix will be included to upcoming 1.10 release


'Unknown identifier' with /var/const

Compiling /vg/station, an error occurs:
Error at code\datums\supplypacks.dm:337:40: Unknown identifier "access_engine_minor"
here:
330	/datum/supply_packs/sacidtank
331		name = "Sulphuric acid tank"
332		contains = list(/obj/structure/reagent_dispensers/sacid)
333		cost = 15
334		containertype = /obj/structure/closet/crate/secure/large/reinforced/shard/empty
335		containername = "sulphuric acid tank crate"
336		group = "Supplies"
337		one_access = list(access_engine_minor, access_science)

access_engine_minor is defined in /code/game/jobs/access.dm as:
/var/const/access_engine_minor = 11	// Engineering Foyer
This error only started occurring fairly recently.

@Altoids1 Seems like something your PR should have fixed?

god

I got the same error on a version of OD with the const PR rolled back; might be a novel error caused by changes in VGstation codebase itself. This is not a regression, just something I didn't fix.
Stuff like this probably could've been in the const PR, but was not, since late evaluation of expressions is completely unimplemented. The concept of late-evaluation did not even meaningfully exist in the codebase prior.
For the record, the const PR fixed late evaluation of the left side of an override assignment. The right side remains a TODO.

I don't think this is due to an underlying change in the /vg/station codebase; the format of the access-related stuff involving /code/game/jobs/access.dm has been the same for years. Rather I think it's likely due to a change that occurred in how /var/const are processed some time over the last few months (not as recent as @Altoids1's recent changes), because I remember trying to compile after pulling the latest version of OpenDream and there were more errors than before the pull. At the time I thought maybe it was just being more verbose about errors that previously had been silently occurring, or something. I'm not sure exactly when this started happening but I may be able to check a rough date in a little bit.

I'm not exactly sure when it happened but I think it may have been around the time #706 was fixed, as I remember that error stopped appearing but then this error appeared. Could be wrong though.


Enter does not de-select current selection

I have found when using this component everything seems to work based upon selections except for when I want to remove the item from being selected.  I am not allowing multiple selections but when a single item is listed in the drop down and I expand the contents it says hit enter to remove, however hitting enter does not remove the selection.
Is it possible to remove the selected item when I am using the select for a single value and not using muliple?
I have googled and found that due to using Objects the track_by has to be in place for the component to know which one you are de-selecting and I have verified that all 4 of my drop downs have this attribute but NONE of them will allow me to deselect the selection value.

The above images show the select element where it says I can hit enter to remove and the other two images are the props passed down to the MultiSelect component.
I have even tried to see if close-on-select was set to false if it would work and it does not.  I have compared my props to the props on your example page for the first example which works but the props look to be the same.  The only difference is that your example is using an array of strings for options and mine is using an array of objects.
I have also added multiple elements to it and checked if i arrow to the next and hit enter the selection changes, it just does not de-select the already selected option when selected and enter is hit on the keyboard.

@jcrawfordnexant What was the issue? Having this as well


Add fixed to platform services and support for discovery server

Looks like a network glitch in the build caused the verify failure. kicking it off again.

recheck

recheck


Trim out more legacy projections fallback paths

This PR just allows completely trimming out some fallback paths for legacy projections. These should never be reached when using NativeAOT, and even if they were, old projections are not supported in AOT scenarios anyway, so no point in keeping this.

Looks like there are new authoring test failures:
[  FAILED  ] AuthoringTest.Arrays
[  FAILED  ] AuthoringTest.CustomVectorImplementations
[  FAILED  ] AuthoringTest.ExplicitInterfaces

All green, and only 1 failing authoring test now, which was already failing before too:


Do I have to migrate?

Hi there,
I love the interface and features of this implementation of Task. In particular, the ability to run tasks concurrently using ap() is fantastic.
May I continue to use this library and will it be maintained, or must I migrate to folktale/concurrency/task? With folktale v2, I loose the ability to chain/ap concurrently.
Thanks,
Mike

Folktale 1 may receive some bug fixes if they're important, but won't get any new features/etc.
I'd recommend against using data.task's ap and chain together, though, since they're not compatible (see https://github.com/origamitower/folktale/pull/50#issuecomment-254042714 for details). The new library will eventually have separate types for sequential and parallel tasks, but you can construct a parallel type for task with concurrify today: https://github.com/fluture-js/concurrify


Sync action for table listing (no tables)

If I have no tables in db, table listing ends with err.
An Error occurred fetching table listing

[2017-11-09 15:51:24] ex-db-snowflake.ERROR: Failed to get tables: 'odbc_prepare(): SQL error: SQL compilation error: syntax error line 2 at position 34 unexpected ')'., SQL state 37000 in SQLPrepare' [] []

sorry, this was resolved same day as reported:) https://github.com/keboola/db-extractor-snowflake/commit/6094c20c8a2239544de5f0a105939f52711adec8


fix(eslint-config): switch to new babel parser

Summary
babel-eslint is deprecated now. We should use the new Babel parser.
Changelog

[General] [Fixed] - Use new Babel parser for ESLint config
Test Plan
Ensure lint is working as expected.

Thanks for sending this over @Kerumen
This is sadly not sufficient. Please check another other similar attempt here:

#33949

We need to update all the references of babel-eslint in the codebase

@cortinico I don't see a lot of reference. Maybe I should also update the test here?

@cortinico I don't see a lot of reference. Maybe I should also update the test here?

A quick grep returns this:
rg "babel-eslint"
CHANGELOG.md
2835:- Upgrade babel-eslint to 9.0.0 ([44dc283bcd](https://github.com/facebook/react-native/commit/44dc283bcd0a75826d9be86cdc727e32d5697ef2) by [@rafeca](https://github.com/rafeca))
2966:- Upgrade babel-eslint to v9.0.0-beta.2 with better support for Flow ([abf1188de2](https://github.com/facebook/react-native/commit/abf1188de225e4b7d36ecbad316af92ca29c85c2) by [@rubennorte](https://github.com/rubennorte))

yarn.lock
<EMAIL_ADDRESS>1782:  resolved "https://registry.yarnpkg.com/babel-eslint/-/babel-eslint-10.1.0.tgz#6968e568a910b78fb3779cdd8b6ac2f479943232"

repo-config/package.json
19:    "babel-eslint": "^10.1.0",

packages/eslint-config-react-native-community/yarn.lock
<EMAIL_ADDRESS>405:  resolved "https://registry.yarnpkg.com/babel-eslint/-/babel-eslint-10.1.0.tgz#6968e568a910b78fb3779cdd8b6ac2f479943232"

packages/eslint-config-react-native-community/package.json
17:    "babel-eslint": "^10.1.0",

packages/eslint-config-react-native-community/index.js
39:      parser: 'babel-eslint',

packages/eslint-plugin-react-native-community/__tests__/eslint-tester.js
15:  parser: require.resolve('babel-eslint'),

packages/eslint-plugin-specs/__tests__/eslint-tester.js
15:  parser: require.resolve('babel-eslint'),

Should I update them? I don't know what repo-config is doing.

Yeah the should all be updated.
repo-config is the yarn workspace for the whole repository

@cortinico Done! ✅

The CI is green now! 🟢
Here is what I did:

I added requireConfigFile: false as it's needed since Babel v11
I added @babel/preset-flow for eslint-plugin-specs as it tests Flow code with some Flow syntax
I added missing @babel/core in eslint-config

The CI is green now! 🟢
Here is what I did:

I added requireConfigFile: false as it's needed since Babel v11
I added @babel/preset-flow for eslint-plugin-specs as it tests Flow code with some Flow syntax
I added missing @babel/core in eslint-config

Awesome stuff! We'll re-import this and we should be fine merging it 👍

Any progress here? 🚀

Sadly not. I've been trying to merge this PR internally, but our setup related to babel is quite intricate and it's more challenging than expected.

Kudos to @jacdebug for unblocking this 👍


macdriver: add NSUserDefaults bindings

This is the result of:

running macschema pull foundation/nsuserdefaults
editing ./gen/cmd/gen.go
running go run ./gen/cmd
adding core/NSUserDefaults.go
adding an example

fixes #115

I tried to do what you did but Macschema doesn't work for me. It always gives me this output:
=> Fetching sub-topics...
=> Waiting for workers to finish...
=> Generating schema...
2023/07/03 22:23:47 schema not supported for
Which version of Macschema are you using?

Don't use the release. It's actively being developed and updated so you have to build from main until things settle for a new release.


Fix a minor 404 link to the VDOM section

Fixes a typo where the link pointed to vdoom instead of vdom

@SahAssar Thanks! 💯

@SahAssar Hey man! Fancy seeing you here!  👋 Small world... 😄

@zaceno hehe, I've been tinkering with hyperapp a bit and it looks awesome... I might have some questions to pester you with tomorrow though 😉

@SahAssar Np you're welcome to pester me all you want :)  but you'll have to wait till monday. I'm in Stockholm today and tomorrow.


Long filenames when adding via append<R: Read>

It would be great if the logic that automatically prepends a long filename header was also available for the append method. Currently the code is not reusable and has to be copy-pasted if one wants to pass in Read implementations associated with long file names as opposed to Path.

Seems fine to me! I'd be ok adding a new append_*-style method to use this logic.


Use shutil.which("aflow") to detect aflow executable

Closes #15.

thanks for doing this, maybe need a try except in the get_aflow_from_aflow to catch when alfow isn't in $PATH

@CompRhys Good call. Now raising FileNotFoundError in get_aflow_label_aflow if both default "aflow" and possible user-defined path to aflow don't point at an executable binary.


Decimal values

I'm trying to set up a slider that allows to select a value between 0 and 5 with increments of 0.5
So 0.5 should be a value being returned.
Visually it works. Unfortunately the value is rounded. Ideally the value is returned as 0.5
Settings:

Result:

APEX version 21.1.6

No I didn't. It works though. Tough, I was hoping this could have been done declaratively, not by adding JS.


Each image present in module subfolder increases memory usage by 1MB, even when unused

I am making dangerous assumption in the following description of the problem. However, I am fairly confident for them to be accurate.
I've been having an issue with memory bloat. After a bunch of days of investigation I can definitively say that it is linked with the amount of image present in each CEEvents submodules. The image themselves don't matter, could be a single pixel and it wouldn't change anything. The issue at core lies with how the mod loads the images, and how it is stored within memory.
The following is how images are currently loaded: list them all, then assign them to a texture, then store that texture into persistence.
https://github.com/BannerlordCE/CEEvents/blob/57b44716f9790cdb263b032ea0925bf18b00ef03/CESubModule.cs#L327-L360
Issue happens with how heavy the texture object is. To know that, we need to use the command profiler.generate_performance_report. That will generate a bunch of files under Mount & Blade II Bannerlord/bin/Win64_Shipping_Client/profiling_results/. The one we want to take a look at is gpu_memory.txt — btw, this is a report done while in the start menu of the game. In it, you'll see a section named Gpu data textures memory usages., which presumably highlight the issue. Memory consumption rises relative to the texture resolution:

75x75: 0.021458MB
445x805: 1.366520MB
890x1610: 5.466080MB

Which means that with a submodule such as Hot Buttered Girls that has more than 2000 images, the space used by the simple listing of image will be over 2 GiB.
Possible resolution
Do not create a texture object right away, instead store the list of files as string. Create the texture when a module request the image, then discard the object once unneeded. The cost of creating the texture object per request is minimal given the context these textures are used. There's literally no intensive work dependent on their existence.

A way to keep a limited cache is to implement the least recently used cache policy. Keep the last 10 pictures in memory, if a new one appear, override the oldest element. Caveat: animations sequences should be exempt from the cache, as they tends to have a greater amount of images.
A LRU will help during normal gameplay (vanilla game), where often time the same image is displayed over and over again.

Been trying to figure out how to unload these textures.

@bicobus Thank you for your report, should be solved now! I hope you report any other problems or any new features you will like to see implemented!

I'll duplicate what I wrote on the discord.
https://github.com/BannerlordCE/CEEvents/blob/development/CESubModule.cs#L202-L207
Dictionary aren't ordered, so asking for the first might not return the oldest element. You may want to used a linked list instead. Linked list store the key as a str, you always AddFirst for new images.
To then trim the persistent storage: get the last entry from the list then remove it RemoveLast. Then remove the element from the dictionary with the retrieved key.
See: https://learn.microsoft.com/en-us/dotnet/api/system.collections.generic.linkedlist-1?view=net-7.0


update pretty_name for all datasets

This PR updates pretty_name for all datasets. Previous PR #3498 had done this for only first 200 datasets

Pushed the lastest changes!


Distro support

Are there any plans to update this operator to work with RHEL/CentOS? Conceptionally there doesn't seem much CoreOS specific about it. Perhaps it works already?

CLUO does end up being pretty Container Linux specific, particularly in the way that it ties into update_engine to poll for updates. Since CLUO doesn't have any real control over the underlying update process, it's really just locksmith running as a daemonset in kubernetes. In general, we are preferring newer tools that have much more direct control over the update process, such as the machine config daemon, which ties into rpm-ostree directly to update the operating system. That one is specifically for Red Hat CoreOS right now.
There was some early exploratory work that integrated this codebase directly with rpm-ostree (https://github.com/ashcrow/container-linux-update-operator/tree/spike) but the focus has been on the MCD system. As far as I know, there is no equivalent tool that integrates with dnf or any other package management systems.

What about a yum plugin that called 'locksmithctl send-need-reboot' on any change? It may reboot more then needed, but could work? Alternately, could you just buypass the locksmith and label the node directly? would the rest of the reboot logic work in that case?

Sorry for the confusion. I meant that it is architecturally and behaviorally like locksmith, not that it is literally locksmith. The CLUO agent hooks directly into update_engine through it's exposed DBUS API (https://github.com/coreos/container-linux-update-operator/blob/4bb1486f482bc9c365c71e126129e806b5a0fc97/pkg/updateengine/client.go#L61) and whenever update_engine applies a new update (entirely out of band, like on any container linux instance), the reboot coordinator component confirms that only one gets rebooted at a time. The reboot logic might work, but again, there is nothing in CLUO that actually triggers an update, and it's not architected to do that.

I think we always intended Fedora/RHEL would be designed quite differently, as a different reboot coordinator app.

Do you see the logic around picking nodes, draining, rebooting, and uncordoning as being distro specific? I could see the node agent being specific. Does the reboot manager pay attention to any other state then needs upgrading?
I was thinking of trying to set up ansible to point yum at the new version repo (we version mirror snapshots), yum upgrade, and trigger the locksmith and let the operator reboot things safely. cicd would trigger ansible to upgrade the nodes and the operator would reboot them as needed safely? Alternately, it could maybe skip locksmith entirely and just set node labels directly?


Investigate species filter for the metadata search

The Species filter in the metadata search is getting ignored.
Steps to reproduce:

Go to the metadata search in Single Cell Expression Atlas
Type a search term into the Search term box. For example: liver
Select a value from the Species dropdown. For example: Mus musculus

Expected result:
The cell type wheel only shows the result for the selected species.
Actual result:
The cell type wheel shows the result for all the species.
Steps:

[ ] Investigate for max 1 day whether the fix is easy to do
[ ] According to the previous step

[ ] Yes: Do the fix
[ ] No: Remove the Species filter from the display temporary, but only the display item and leave all the functionality in the code.

During my investigation, I found that  we are supporting from the backend - but we are not passing species param from the frontend I believe as per the code:
@GetMapping(value = "/json/cell-type-wheel/{searchTerm}",
                produces = MediaType.APPLICATION_JSON_UTF8_VALUE)
    public String jsonCellTypeWheel(@PathVariable String searchTerm,
                                    @RequestParam(name = "species", defaultValue = "") String species) {
        return GSON.toJson(
                highchartsSunburstAdapter
                        .getCellTypeWheelSunburst(searchTerm, cellTypeWheelService.search(searchTerm, species)));
    }

In the Atlas components repo - file name - CellTypeWheelExperimentHeatmap.js
 <CellTypeWheelFetchLoader
              host={props.host}
              resource={URI(props.searchTerm, props.cellTypeWheelResource).toString()}
              fulfilledPayloadProvider={cellTypeWheelData => ({ data: cellTypeWheelData })}
              searchTerm={props.searchTerm}
              onCellTypeWheelClick={onCellTypeWheelClick}
            />

I believe we need to pass species here from the dropdown when user chooses a species along with search term

Bugs we observed for now related to cell type wheel gene expression page:

From home page to cell type wheel page, species is not passed by routing/URL.
In the cell type wheel page

Search boxes

species box is not always working: it is not working when you change the species but is working when you change the species and then followed by search term changes
search term box is not always working: when you select from user free typing section, for example liver, no cell type data responded; when you select from metadata section, search button is not trigerring any requests.

Cell type wheel

it doesn't take species parameter from the search box
when there are a lot of data loaded, it doesn't display by giving info like no data

Based on the previous comment by @lingyun1010 I created the following separate tickets:

Species parameter is not passed from homepage
Search button not working after an initial metadata search

and we already had this ticket:

Wrong message when cell type wheel got too much data to display

I won't delete the above comment, just to have it if we need it, but that comment does not belong to this current ticket.


[UNIDENTIFIED] on pub.dev

pub.dev says in red that the package is "[UNIDENTIFIED]"

Not exactly sure what that means, but the red background makes it slightly scary looking like something is wrong. Wondering if we can fix that and show something more useful there?

pkg:flutter_lints also shows this:

/fyi @jonasfj @mit-mit

Hmm, I'm guessing we need to tweak pana, because it doesn't have any libraries...
I guess it's harmless to claim compatibility with everything.

Thanks!  Should we open an issue on pana?


Pending pytest PRs

Hey there,
I don't mean to cause hysteria as I completely understand that you all have plenty of things to do apart from Cookiecutter!
Most of my PRs that impact the test suite are still pending. By now I am a bit worried that it's gradually getting harder to merge them. I noticed that there is at least one PR which causes a confict with the current master :worried:
I think that these changes greatly improve our test suite, so I kindly want to ask you if there is anything that I can do to aid you in this matter. I'll be happy to help!!! :blush:
https://github.com/audreyr/cookiecutter/pulls/hackebrot
:bell: @audreyr @pydanny @pfmoore @michaeljoseph

@hackebrot Thanks for responding to my request to point me back on track. I'm trying to work out a plan so I can get back to reviewing pull requests again on a daily basis. I'll start going through PRs right now.

Cool! :heart_eyes: Ping me if you need any help!

@hackebrot Just 2 PR left needing rebase...

All done


Port laz/ply extractors: las2height

Task to do
Port las2height ~and panicle_detection~ extractors to transformers (for Eric's class as well)
Reason
Giving higher precedence to these so they can be used by the class
Result
Dockerized transformers

Dependent upon drone-pipeline/#101 porting of plotclip


Open folder is unresponsive on remote SSH host

Lapce Version
v0.4.0
System information
Windows 11, connecting to Raspberry Pi OS Bookworm
Describe the bug
Trying Lapce for the first time, very excited to get it to work. When I connect to the remote host with SSH, it connects fine and the terminal is usable. However, when I try "Open Folder", it gives me a prompt that I can type something in, but after hitting enter, it doesn't open the folder. The text that I've entered disappears, but nothing else happens. I've tried all sorts of combinations of relative and absolute paths.
"Open Folder" appears to be working fine for local directories.
Additional information
I don't see anything relevant in the log file on the local side (is there a log file for the remote side?). I did notice a bunch of spam about lapce_app::keypress::loader: Keymap ignored, but that doesn't sound related. I don't know what other diagnostics are available to run, but I'd be happy to gather more info if it would help.

Duplicate of https://github.com/lapce/lapce/issues/3241

Thanks for the quick response! For future reference, I was able to use the workaround mentioned in that other ticket, but there's a small catch... you need to run lapce <path> in the remote terminal (you're instructing the remote backend to open the folder)


Viewsonic VG2455

Brightness control don't working, just sound

Ok now with Usb-c to Display Port adapter...

Hi, hope this issue has been resolved. If not, please try the 3.0.0 version as it might change things. If not, please provide us with a little more information by filling out a new Issue using the Issue Template. Thank you for your help! I'll close this issue for now.


finch compose not supported --platform？？

finch  compose --platform=amd64 up
FATA[0000] unknown flag: --platform
FATA[0000] exit status 1

The platform has to be specified in the docker-compose.yaml, not in the CLI flag
https://github.com/containerd/nerdctl/blob/330a9166052246e98235b088e911cfde9c8e343e/examples/compose-multi-platform/docker-compose.yaml#L4
services:
  svc0:
    build: .
    platform: s390x
    ports:
      - 8080:80
  svc1:
    build: .
    platform: ppc64le
    ports:
      - 8081:80

Thanks for the response Akihiro. Using the platform property in the compose YAML itself is the correct way to run a container on a specific platform.
I can't find where the compose --platform=amd64 up pattern is coming from, is there another tool which you use that uses this syntax?


Question about the result of the forwardNet

Thanks for the excellent work, but I have some questions about the result of the forwardNet.
I think the result of the forwardNet should be batch_size * channel * output_res * output_res, and we should use result[:,:17,:,:] for detection loss and result[:,17:34,:,:] for embedding loss.
However, in models/posenet.py line 52, the author uses dets = preds[:,:,:17] and tags = preds[:,:,17:34]
It seems like the result of forwardNet is output_resoutput_reschannel.
Way? Does this has anything to do with line 49 in posenet.py?

@anewell

I think I may find the answer, preds[:,:,:17] is equal to preds[:,:,:17,:].
Sorry for bothering.


Adding script to pull list of running hubs and display it

This ports over the code to generate a list of running hubs in this repository. It currently generates the table in the team compass, but I think it'd be better to keep the code here. This way we know that the table is up-to-date, and also know if we change the config in a way that breaks the table. We also don't need authentication to grab the data from GitHub directly since the YAML files are already in this repository.
Here's the list of running hubs:
https://2i2c-pilot-hubs--376.org.readthedocs.build/en/376/reference/hubs.html

So, are you planning to remove the relevant code from the team-compass repo?

@damianavila yep, if this is merged I will remove that section and cross link it to here

sounds good!


fix: only set cluster_api_url when dataplane_api not nil

Is there a particular context where this happened?

Is there a particular context where this happened? Meaning a cluster without a dataplane url

Most often when a cluster is deleting or wasn't destroyed correctly. I'm not sure if I've ever gotten it on a Serverless cluster but figured I'd fix it everywhere just in case and to have the same pattern.


Add my first file

I have created a new branch, created a file, and made a commit!

I have created a new branch, created a file, and made a commit!

...


Gemspec updated

There are multiple PRs to update the Gemspec, but they missed that it's generated with Thor. Here an updated version:

Declare License: #72 , #89, #90
Remove Gemfile.lock from the repository: #81

Also, it declares all development dependencies (including the missing thor & git) in the gemspec, not the Gemfile & removed the like to the late rubyforge project.

Partial dupe of #72

@iGEL Thank you for your pull-request.
As information, rack-test.gemspec license part  of this PR was merged today.
https://github.com/rack-test/rack-test/commit/fed7b5d6b6143847401870ec7d441806d00fb903
We will check other parts in your PR too to continue.

@iGEL your other parts also merged at https://github.com/rack-test/rack-test/pull/181 .
So, I would close this ticket.
If you have something, let me know. Thank you.


Remove CNAME setup mention on child setups

Please squash and merge due to some bad commit histories

Hi Christopher. Thanks for bringing this up.
I had seen it but have talked to Hannes about it and the reason I have not merged this yet is that, as it is, steps that refer TXT verification record become disconnected/ can cause confusion. We can assume users have a TXT verification record bc we previously told them to convert to partial.
Have created PCX-7471 to look into it later, but if you have the chance/want to go for it as well (or want to add more context/comment on that ticket), always welcome.


[AT-2924] configure poetry

Jira ticket here.
Scope:

Removed setup.py and all requirements.txt file
Removed twine as dependency (instead, using poetry to publish)
updated CircleCI context
use poetry to publish docs
upgraded base image to python 3.11

NOTE: Tested that publication works by publishing on test.pypi.org. I created a new account. Credentials can be found in 1Password --> test.pypi.org credentials
Items:

[ ] Ran test & live-tests
[ ] Implemented (new) unit tests
[ ] Removed credentials
[ ] Removed argument pointing to staging
[ ] Updated documentation

For release:

[ ] Bumped version
[ ] Added changelog
[ ] Updated announcement banner

When you publish, can you make sure that reading the sample geometries is still working?
I mean, the below configuration in setup.py made sure that the aoi_berlin.geojson and aoi_washington.geojson were copied in the published version. We also had to add this in conda. I am not sure if by default these are added in poetry. (_version.txt should be removed)
package_data={"": ["_version.txt", "data/aoi_berlin.geojson", "data/aoi_washington.geojson"]}

I verified this.
It's working. Since the data folder is inside up42 folder, these files are added in the package.
Just in case you want to play around, you can check test it out here :)

https://python-poetry.org/docs/pyproject/#license - can be just "MIT"

I prefer to redirect to proper license file rather than just adding a string "MIT".
I will skip this one.


Expected Behavior

Expected Behavior
Actual Behavior
Steps to Reproduce the Problem

Specifications

Version:
Platform:

I need my phone to be faster


[Master] Add default namespaces with attributes in xml to record generation

Purpose
$title.
Fixes #43043
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

During our offline discussion, we decided that it's not the correct behavior to add the default namespace as mentioned in the issue. Hence, we are closing this PR.


preferences: Allow to set the color preferences for routing and accessibility map

Seems good! However, I am not sure it is wise in the long term to allow different colors for each user/mode for routing. Using the same color for distinct mode in alll instances of Transition would bring some standards and make comparisons easier. Needs dicussion I think.


Can't install Ubuntu from either prebuilt or downloaded images on MacOS

Describe the issue
Can't finish the install of Ubuntu 22.04 from either prebuilt or directly downloaded images on MacOS. Every time I try a new install I get to the featured server snaps, then the "Install Complete" screen (attached) and "Reboot Now". Rebooting just gives me a blank, black screen and my only option is to restart the VM which takes to GRUB, which takes me to the Welcome screen all over again.
If I reboot again and go to the EFI shell I see FS0: Alias(s):CD0h0a0a:;BLK1:
Typing fs0:\efi\boot\bootaa64.efi and selecting Ubuntu Server again takes me to the Welcome Screen as if nothing happened.
Thanks for any insights.
Configuration

UTM Version: 4.4.5 (94)
macOS Version: Sonoma 14.4.1
Mac Chip (Intel, M1, ...): M1 Pro

Crash log
No crashes.
Debug log
The system log is clean.
Upload VM
The first one is for the prebuilt installation and the second one from the downloaded one directly from Ubuntu.system log
config.plist.zip
config 2.plist.zip

Solved by using the


Using com.azure.resourcemanager.frontdoor to retrieve cname from routingRule

Describe the bug
Frontdoor API does not inject cname data and routeConfiguration under routingRule. Both values are null.
Tested with Azure rest API, both value is working fine.
Code Snippet

Expected behavior
Successfully provide cname and routeConfiguration data

@yungezz could you please follow up with @dyhomsft ?

add @weidongxu-microsoft to help

@dyhomsft
Would you enable logging https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/resourcemanager#enabling-logging
and attach the request/response?

To Frontdoor service, please fix either spec or service response
Spec is "cname" https://github.com/Azure/azure-rest-api-specs/blob/master/specification/frontdoor/resource-manager/Microsoft.Network/stable/2020-05-01/frontdoor.json#L963-L967
But in response the property is "cName".
{
  "value" : [ {
    "id" : "/subscriptions/###/resourcegroups/rg62789/providers/Microsoft.Network/frontdoors/fd37244",
    "type" : "Microsoft.Network/frontdoors",
    "name" : "fd37244",
    "location" : "Global",
    "tags" : { },
    "properties" : {
      "routingRules" : [ {
        "id" : "/subscriptions/###/resourcegroups/rg62789/providers/Microsoft.Network/Frontdoors/fd37244/RoutingRules/rule1",
        "name" : "rule1",
        "type" : "Microsoft.Network/Frontdoors/RoutingRules",
        "properties" : {
          "routeConfiguration" : {
            "customForwardingPath" : null,
            "forwardingProtocol" : "HttpsOnly",
            "cacheConfiguration" : null,
            "backendPool" : {
              "id" : "/subscriptions/###/resourceGroups/rg62789/providers/Microsoft.Network/frontdoors/fd37244/backendPools/backend1"
            },
<EMAIL_ADDRESS>: "#Microsoft.Azure.FrontDoor.Models.FrontdoorForwardingConfiguration"
          },
          "rulesEngine" : null,
          "resourceState" : "Enabled",
          "frontendEndpoints" : [ {
            "id" : "/subscriptions/###/resourceGroups/rg62789/providers/Microsoft.Network/frontdoors/fd37244/frontendEndpoints/frontend1"
          } ],
          "acceptedProtocols" : [ "Http", "Https" ],
          "patternsToMatch" : [ "/*" ],
          "enabledState" : "Enabled",
          "webApplicationFirewallPolicyLink" : null
        }
      } ],
      "rulesEngines" : [ ],
      "frontdoorId" : "d9df268b-2b99-4fc3-a3ab-1ed8fd1f9fd4",
      "resourceState" : "Enabled",
      "loadBalancingSettings" : [ {
        "id" : "/subscriptions/###/resourcegroups/rg62789/providers/Microsoft.Network/Frontdoors/fd37244/LoadBalancingSettings/loadbalancing1",
        "name" : "loadbalancing1",
        "type" : "Microsoft.Network/Frontdoors/LoadBalancingSettings",
        "properties" : {
          "resourceState" : "Enabled",
          "sampleSize" : 4,
          "successfulSamplesRequired" : 2,
          "additionalLatencyMilliseconds" : 0
        }
      } ],
      "healthProbeSettings" : [ {
        "id" : "/subscriptions/###/resourcegroups/rg62789/providers/Microsoft.Network/Frontdoors/fd37244/HealthProbeSettings/healthprobe1",
        "name" : "healthprobe1",
        "type" : "Microsoft.Network/Frontdoors/HealthProbeSettings",
        "properties" : {
          "resourceState" : "Enabled",
          "path" : "/",
          "protocol" : "Https",
          "intervalInSeconds" : 30,
          "enabledState" : "Enabled",
          "healthProbeMethod" : "Head"
        }
      } ],
      "backendPools" : [ {
        "id" : "/subscriptions/###/resourcegroups/rg62789/providers/Microsoft.Network/Frontdoors/fd37244/BackendPools/backend1",
        "name" : "backend1",
        "type" : "Microsoft.Network/Frontdoors/BackendPools",
        "properties" : {
          "backends" : [ {
            "address" : "fd37244.blob.core.windows.net",
            "httpPort" : 80,
            "httpsPort" : 443,
            "priority" : 1,
            "weight" : 50,
            "backendHostHeader" : "fd37244.blob.core.windows.net",
            "enabledState" : "Enabled",
            "privateLinkAlias" : null,
            "privateLinkResourceId" : null,
            "privateLinkLocation" : null,
            "privateEndpointStatus" : null,
            "privateLinkApprovalMessage" : null
          } ],
          "resourceState" : "Enabled",
          "loadBalancingSettings" : {
            "id" : "/subscriptions/###/resourceGroups/rg62789/providers/Microsoft.Network/frontdoors/fd37244/loadBalancingSettings/loadbalancing1"
          },
          "healthProbeSettings" : {
            "id" : "/subscriptions/###/resourceGroups/rg62789/providers/Microsoft.Network/frontdoors/fd37244/healthProbeSettings/healthprobe1"
          }
        }
      } ],
      "frontendEndpoints" : [ {
        "id" : "/subscriptions/###/resourcegroups/rg62789/providers/Microsoft.Network/Frontdoors/fd37244/FrontendEndpoints/frontend1",
        "name" : "frontend1",
        "type" : "Microsoft.Network/Frontdoors/FrontendEndpoints",
        "properties" : {
          "resourceState" : "Enabled",
          "hostName" : "fd37244.azurefd.net",
          "sessionAffinityEnabledState" : "Disabled",
          "sessionAffinityTtlSeconds" : 0,
          "webApplicationFirewallPolicyLink" : null,
          "customHttpsProvisioningState" : null,
          "customHttpsProvisioningSubstate" : null,
          "customHttpsConfiguration" : null
        }
      } ],
      "backendPoolsSettings" : {
        "enforceCertificateNameCheck" : "Enabled",
        "sendRecvTimeoutSeconds" : 30
      },
      "enabledState" : "Enabled",
      "cName" : "fd37244.azurefd.net",
      "friendlyName" : null,
      "provisioningState" : "Succeeded"
    }
  } ]
}


Error when upgrading from 2.7.0 to 2.8.0: Token retrieval failure

Hi All,
We encountered an error after upgrading the league/oauth2-client library from version 2.7.0 to version 2.8.0. The error occurs when running a command that interacts with a third-party service to retrieve a token.
Steps to reproduce:

Use version 2.8.0 of the library.
Execute a request to a third-party service to retrieve a token using the following method:

With version 2.7.0, the command works correctly and retrieves a valid token.
Actual behavior:
Starting from version 2.8.0, the described error is triggered.

Discussion to be continued in https://github.com/thephpleague/oauth2-client/pull/1030 please.

Can you try if  https://github.com/thephpleague/oauth2-client/pull/1053 fixes your issue?


[Enhancement] Support many-to-many on the same table

Add support for many-to-many against the same table. For example:
@Table(database = Database.class) @ManyToMany(referencedTable = User.class)
public class User {
    @PrimaryKey @Unique @Column int id;

    List<User> followers;  //Many-to-many
}

Currently the generated code will create a 2 foreignkey with the field names. A good enhancement would be to either: (1) append a number to the generated variable name as the default behavior, or (2) allow the relationship name to be specified.

you want to create a @ManyToMany on itself? that's fine I can do that.

now you can do that, also control the generated table class name if you dont like User_User hahahaha.

Sweet! :100:


Navigation links scroll to top before transitioning to next page.

Steps to reproduce

Scroll down on the homepage of my Gatsby-universal CodeSandbox example
Click a navigation link

Expected result
Page transitions to next page.
Actual result
Page scrolls to top before transitioning to the next page.

@rafaelderolez,
In case you haven't already resolved this on your own I encountered a similar issue and a solution was proposed here:
https://github.com/gatsbyjs/gatsby/issues/5213#issuecomment-428368131

@ryanwiemer I ended up not needing page transitions on the project I used this on but that solution looks promising, thanks!

Hey! Thanks for opening this.
Yes, that seems like a Gatsby-core issue. Closing :)


network issues

Job fails due to NETWORK_CONNECTION issue.
https://github.com/bcgov/CE_integratedroads/actions/runs/8697514765/job/23852882501#step:4:46
I'm not sure whether the issue is on the GHA end or the object store end.
Not really an issue for this job, it can easily be re-triggered... but worth looking into more closely if re-using this workflow pattern

Job repeatedly fails when overwriting existing /vsis3/bucket/integratedroads_.parquet files.
But it seems to succeed when files do not exist.
Easier to work around than to try and debug for now.

Using -overwrite option does not work at all, just remove the parquet file before writing and all is fine.


Support for GBM regression

I've learned a GBM regression tree model in R and tried loading it into ruby using scoruby and seems like it's not supported.
The r2pmml package produces a v4.3 .pmml that does not contain any OutputField I only see.
<Targets>
  <Target field="target" rescaleConstant="4.107037612571389"/>
</Targets>

The pmml package produces a v 4.4 pmml with something like this
  <Output>
   <OutputField name="Predicted_target" optype="continuous" dataType="double" feature="predictedValue"/>
   <OutputField name="GaussianPrediction" feature="transformedValue" dataType="double">
    <Apply function="+">
     <FieldRef field="Predicted_target"/>
     <Constant>4.10703761257139</Constant>
    </Apply>
   </OutputField>
  </Output>

I've looked at the source of scoruby and seems like the logic for detecting gbm needs an OutputField. How can I help to add support for regression GBM?
Great work so far!

@asafschers sorry for the late reply. Here are two models learned in R, using standard gbm message. First is exported to pmml using pmml library, second using r2pmml library. Both fail with RuntimeError (model not supported)
irb(main):003:0> m = Scoruby.load_model('out2.pmml')
Traceback (most recent call last):
        7: from /home/johno/.rbenv/versions/2.6.5/bin/irb:23:in `<main>'
        6: from /home/johno/.rbenv/versions/2.6.5/bin/irb:23:in `load'
        5: from /home/johno/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/irb-1.0.0/exe/irb:11:in `<top (required)>'
        4: from (irb):3
        3: from (irb):3:in `rescue in irb_binding'
        2: from /home/johno/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/scoruby-0.3.3/lib/scoruby.rb:21:in `load_model'
        1: from /home/johno/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/scoruby-0.3.3/lib/scoruby/model_factory.rb:21:in `factory_for'
RuntimeError (model not supported)

models.zip
Pretty standard stuff in R e.g.
t = gbm(Sepal.Length ~ ., data = iris, verbose = TRUE, interaction.depth = 5, cv.folds = 5, train.fraction = 0.9, n.trees=50)

Btw this seems to work find in master. Any chance for a version bump on rubygems?

However this line looks extremely suspicious https://github.com/asafschers/scoruby/blob/master/lib/scoruby/models/gradient_boosted_model/model.rb#L23 for basic regression there should be no transformation. Is this for logistic regression only?

Btw this seems to work find in master. Any chance for a version bump on rubygems?

+1 on this, @asafschers.


[Bug] Fake Field Attributes on Relation Entity

Bug report
What I did
Tried to upgrade Laravel Backpack from version 4.1 to 5 and encountered issues on a relation entity field while using fake field attributes. It seems like the support for this feature has been dropped.
What I expected to happen
I expect to be able to save fake field attributes on a relation entity.
What happened
I've created a checkbox field to specify if the location does require a COVID entry pass, this specification is stored in the relation table called LocationMeta. This table has a field called extras which contains all the fake field attributes.
$this->crud->addField([
    'name' => 'covid_entry_pass',
    'label' => __('Requirement for a COVID entry pass on location'),
    'type' => 'checkbox',
    'entity' => 'meta',
    'model' => LocationMeta::class,
    'fake' => true,
    'store_in' => 'extras',
    'wrapper' => [
        'class' => 'form-group col-md-4',
    ],
    'tab' => __('labels.general'),
]);

I'm not sure if the support for fake field attributes on a relation entity is dropped on purpose. Whenever I perform a create or update operation I get the following error:

What I've already tried to fix it
This is created by the dropped support since #4127 and is caused by line 99 of the app/Library/CrudPanel/Traits/Create.php file: $relation = $item->{$relationMethod}();. I have tried to update the $relationMethod to the entity specified on the item which did resolve the undefined method error, but that did create other issues.
Is it a bug in the latest version of Backpack?
Yes
Backpack, Laravel, PHP and DB version
### PHP VERSION:
PHP 8.0.16 (cli) (built: Mar  3 2022 08:44:31) ( NTS )
Copyright (c) The PHP Group
Zend Engine v4.0.16, Copyright (c) Zend Technologies
    with Zend OPcache v8.0.16, Copyright (c), by Zend Technologies

### LARAVEL VERSION:
v9.10.1@93414b1c7c0a56081d96c060bb850ac192d3d323

### BACKPACK VERSION:
5.0.15@ec24c10ff3ee69cf0aafef9f16ec1d90c9ba9d7a

Hello @jordinbrouwer thanks for the report and sorry for the bad experience.
Can you please provide me with: the meta() relation definition? is it a belongsTo ?
If it is a belongsTo you should use the inline_create to create  the related entries. If it's an hasOne you should use either dot.notation or the new HasOne container for the relation.
https://backpackforlaravel.com/docs/5.x/crud-how-to#what-field-should-i-use-for-a-relationship-1
Let me know, if there is some bug I want to kill it 🗡 !! hehe 🙃
Cheers

Hello @pxpm,
Thanks for the quick response. It seems that I'm indeed using a hasOne relation.
public function meta(): HasOne
{
    return $this->hasOne(LocationMeta::class);
}

I've updated the name specification with the dot.notation.
$this->crud->addField([
    'name' => 'meta.covid_entry_pass',
    'label' => __('Requirement for a COVID entry pass on location'),
    'type' => 'checkbox',
    'fake' => true,
    'store_in' => 'extras',
    'value' => isset($extras) && isset($extras->covid_entry_pass) ? $extras->covid_entry_pass : false,
    'wrapper' => [
        'class' => 'form-group col-md-4',
    ],
    'tab' => trans('labels.general'),
]);

Now the functionality seems to work as expected. Sorry for the inconvenience.


Refacto validation process

Context
add a clear validation function for all forms
User flow
Describe the user flow using user stories so the end result is super clear - PM
How to

[ ] refacto sendInputs functions with clearers functions
[ ] use them in the sendForm
[ ] in the advanced (fees) input
[ ] in the generate a Link form

Technical details
Give the technical insights so anyone in the team can tackle the tasks - Dev
QA testing
The validation process should work the same way as before

done here


chore(master): release 1.1.30

:robot: I have created a release beep boop
1.1.30 (2023-04-21)
Miscellaneous

deps: update dependency @types/node to v18.15.13 (0adcfd5)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/keywind/releases/tag/v1.1.30 :sunflower:


refactor to private with getters when needed.

The puzzle 67-e1e6d488 from #67 has to be resolved:
https://github.com/ammaratef45/Attendance/blob/b7cf719a727f8994adf0d4e4942f48e010118f7a/attendance/lib/backend/scan_model.dart#L23-L23
The puzzle was created by Ammar Atef on 30-Apr-19.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@ammaratef45/z please, pay attention to this issue

The job #75 assigned to @ammaratef45/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

Job gh:ammaratef45/attendance#75 already assigned to @ammaratef45, can't assign to @ammaratef45

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @ammaratef45/z

The puzzle 67-e1e6d488 has disappeared from the source code, that's why I closed this issue.

@0pdd the puzzle #84 is still not solved.

Job was finished in 26 hours, bonus for fast delivery is possible (see §36)

The job #75 is now out of scope

Order was finished: +35 point(s) just awarded to @ammaratef45/z

@0pdd the only puzzle #84 is solved here.


Transparent background broke

Describe Your Issue
I was using the none color as described here https://github.com/bhilburn/powerlevel9k/issues/240#issuecomment-200072402 to get transparent background color but when I upgraded from 0e3c1924fe40835dfe189227b8a165de147e65a1 to afcb1b7f84466898c632f47a75d7f1cdf5334f13 it stopped working and my background is now dark grey
Is there a way to continue to have a transparent background?
Have you tried to debug or fix it?
I think it comes from the change functions/colors.zsh between these two commits.
Before (0e3c192): https://github.com/bhilburn/powerlevel9k/blob/0e3c1924fe40835dfe189227b8a165de147e65a1/functions/colors.zsh
After (afcb1b7): https://github.com/bhilburn/powerlevel9k/blob/afcb1b7f84466898c632f47a75d7f1cdf5334f13/functions/colors.zsh
https://github.com/bhilburn/powerlevel9k/compare/0e3c1924fe40835dfe189227b8a165de147e65a1...afcb1b7f84466898c632f47a75d7f1cdf5334f13
Environment Information
ZSH version: 5.5.1
Oh-My-ZSH: Yes
P9k install: cloned in ~/.oh-my-zsh/custom/themes/powerlevel9k
Terminal emulator: Terminator

I have a similar problem recently but only with the left prompt.

At the end of the left prompt first's line background become dark

I found a way to solve the problem. I open a pull request

@JulienPivard Thanks a lot for that


Rebuild against protobuf 4.25.3

Destination channel: defaults
Links

{ticket_number}
Upstream repository
Upstream changelog/diff
Relevant dependency PRs:

...

Explanation of changes:

...

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_10unqqcxc7/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:155: host_section_needs_exact_pinnings: output "pytorch": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:156: host_section_needs_exact_pinnings: output "pytorch": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:159: host_section_needs_exact_pinnings: output "pytorch": Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 3 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_29ca36c8jm/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:162: host_section_needs_exact_pinnings: output "pytorch": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: output "pytorch": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:159: host_section_needs_exact_pinnings: output "pytorch": Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 3 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_bf8jlcwl7q/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:157: host_section_needs_exact_pinnings: output "pytorch": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: output "pytorch": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:161: host_section_needs_exact_pinnings: output "pytorch": Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 3 Warnings were found


Ollie: Watch pughomelovers.com

Ollie requests the watch of the watch_keyword pughomelovers\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by cigien in Charcoal HQ

pughomelovers\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.


Doesn't decrypt?

I followed the guide and tried to decrypt a app.psvimg file from my QCMA backup.
I got my key from http://cma.henkaku.xyz and extract with psvimg-extract -K d63bb030284610e641f8cefe460be8cb8e6efac75a25e55a...... app.psvimg out.
But if i check the extracted files they are still encrypted. The tipical headers of ELF and images are not there.
That i am doing wrong?

Never mind, it decrypts afterwars in the emulator.


HDDS-2018. Handle Set DtService of token for OM HA.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
48
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1
mvninstall
593
trunk passed

+1
compile
369
trunk passed

+1
checkstyle
76
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
891
branch has no errors when building and testing our client artifacts.

+1
javadoc
171
trunk passed

0
spotbugs
432
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
652
trunk passed

_ Patch Compile Tests _

+1
mvninstall
535
the patch passed

+1
compile
407
the patch passed

+1
javac
407
the patch passed

-0
checkstyle
46
hadoop-ozone: The patch generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
709
patch has no errors when building and testing our client artifacts.

+1
javadoc
188
the patch passed

-1
findbugs
187
hadoop-hdds in the patch failed.

_ Other Tests _

+1
unit
342
hadoop-hdds in the patch passed.

-1
unit
2355
hadoop-ozone in the patch failed.

+1
asflicense
49
The patch does not generate ASF License warnings.

8275

Reason
Tests

Failed junit tests
hadoop.ozone.container.common.statemachine.commandhandler.TestCloseContainerByPipeline

hadoop.ozone.TestOzoneConfigurationFields

hadoop.ozone.TestStorageContainerManager

hadoop.ozone.TestSecureOzoneCluster

hadoop.ozone.client.rpc.TestWatchForCommit

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1371/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1371

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 4a0c294be6fc 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 872cdf4

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1371/2/artifact/out/diff-checkstyle-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1371/2/artifact/out/patch-findbugs-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1371/2/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1371/2/testReport/

Max. process+thread count
4386 (vs. ulimit of 5500)

modules
C: hadoop-ozone/common U: hadoop-ozone/common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1371/2/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
35
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1
mvninstall
609
trunk passed

+1
compile
365
trunk passed

+1
checkstyle
74
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
922
branch has no errors when building and testing our client artifacts.

+1
javadoc
166
trunk passed

0
spotbugs
429
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
628
trunk passed

_ Patch Compile Tests _

+1
mvninstall
539
the patch passed

+1
compile
372
the patch passed

+1
javac
372
the patch passed

-0
checkstyle
40
hadoop-ozone: The patch generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
732
patch has no errors when building and testing our client artifacts.

+1
javadoc
168
the patch passed

+1
findbugs
697
the patch passed

_ Other Tests _

+1
unit
283
hadoop-hdds in the patch passed.

-1
unit
1623
hadoop-ozone in the patch failed.

+1
asflicense
48
The patch does not generate ASF License warnings.

7489

Reason
Tests

Failed junit tests
hadoop.ozone.om.TestSecureOzoneManager

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1371/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1371

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux eae18d9bf983 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 915cbc9

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1371/3/artifact/out/diff-checkstyle-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1371/3/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1371/3/testReport/

Max. process+thread count
4993 (vs. ulimit of 5500)

modules
C: hadoop-ozone/common U: hadoop-ozone/common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1371/3/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

Thank You @xiaoyuyao for the review.
Addressed review comments.

+1 pending CI.

Thank You @xiaoyuyao for the review.
I will commit this to the trunk.


Prepare for custom channels (lnd v0.18.4-beta)

This is the mother of all PRs for the custom channel saga. Merging this PR will be the final step for bringing custom channels to a non-experimental version of litd. There are many dependencies (see list/graph below), so it will remain in draft for a bit.
Most of the code in these PRs have already been reviewed on the 0-19-staging branch and have just been squashed down into easy-to-review pieces.
The following list is an ordered list of dependencies that need to be resolved before this PR can be merged (cc @dstadulis):

[x] Review and merge https://github.com/lightninglabs/lndclient/pull/192
[x] Review and merge https://github.com/lightningnetwork/lnd/pull/8960
[x] Create release branch PR with stable commits (https://github.com/lightningnetwork/lnd/pull/9183)
[x] Push tag lndclient v0.18.4-0 that points to release branch with stable commits
[x] Update https://github.com/lightninglabs/pool/pull/488 to point to lndclient v0.18.4-0 (and with it also bumping the lnd version), take out of draft
[x] Review and merge https://github.com/lightninglabs/pool/pull/488
[x] Update https://github.com/lightninglabs/loop/pull/828 to point to lndclient v0.18.4-0 (and with it also bumping the lnd version), take out of draft
[x] Review and merge https://github.com/lightninglabs/loop/pull/828
[x] Update https://github.com/lightninglabs/taproot-assets/pull/1130 to point to lndclient v0.18.4-0 (and with it also bumping the lnd version), take out of draft
[x] Review and merge https://github.com/lightninglabs/taproot-assets/pull/1130
[ ] Code, review and merge https://github.com/lightningnetwork/lnd/issues/9176
[ ] Wait for lnd v0.18.4-beta to be tagged (at least an RC tag) https://github.com/lightningnetwork/lnd/issues/9173
[ ] https://github.com/lightninglabs/lndclient/issues/194 point to the tagged version of lnd
[ ] Push tag lndclient v0.18.4-1
[ ] Create and merge Pool PR to reference lndclient v0.18.4-1
[ ] Create and merge Loop PR to reference lndclient v0.18.4-1
[ ] Create and merge Taproot Assets PR to reference lndclient v0.18.4-1
[ ] Update this PR to point to all the above projects and their merged commits (loop, pool, tapd)

NOTE: This PR includes all recent changes to litd's 0-19-staging branch, including the new liquidity tests from https://github.com/lightninglabs/lightning-terminal/pull/842. There haven't been any other in-flight PRs to the staging branch when writing this.

Similar to https://github.com/lightninglabs/loop/pull/828, I bumped to lndclient v0.18.4-0 which references https://github.com/lightningnetwork/lnd/pull/9183 (commit https://github.com/lightningnetwork/lnd/pull/9183/commits/ca3bde901eb86638256a72fd17b75ce5951d119f) which should remain stable, so we can start the main review work here.
We will want to wait with merging this until the full dependency chain above is resolved. But once lnd v0.18.4-beta is tagged, that should only entail bumping the versions in go.mod.

Need to add https://github.com/lightninglabs/lightning-terminal/pull/861.

@jamaljsr I tagged you for review on this with the intention of asking you to run a full manual test run of this version within Polar (all the tests you've run previously).
Do you think you'll have time for that this or next week? Thank you!

@guggero Thanks for the clarification. I wasn't sure how I should test this or if it was ready. I will try it out in Polar by early next week at the latest, hopefully sooner. Excited to see this functionality getting mainlined 🙌

This PR now contains all the recently merged PRs of the 0-19-staging branch up to commit 2194f1e8.

Thank you very much for testing, @jamaljsr!!! :pray:
Yes, I did add some more commits. Most of them are fixes for the CI and Go module bumps.
But because the final merged tapd PR (https://github.com/lightninglabs/taproot-assets/pull/1130) was on top of the RFQ changes, some rounding and precision related calculations now work slightly differently (e.g. with better precision and fewer rounding losses).
So I don't think a full test suite run is necessary. But perhaps some of the multi-hop scenarios with bigger asset values would be beneficial. Thank you!
This PR now contains all changes of the staging branch, most notably the following PRs (and everything before those):

https://github.com/lightninglabs/lightning-terminal/pull/871
https://github.com/lightninglabs/lightning-terminal/pull/865
https://github.com/lightninglabs/lightning-terminal/pull/861
https://github.com/lightninglabs/lightning-terminal/pull/842
https://github.com/lightninglabs/lightning-terminal/pull/838

So I don't think a full test suite run is necessary. But perhaps some of the multi-hop scenarios with bigger asset values would be beneficial. Thank you!

I've been testing large asset payments and came across something that I'm not sure is expected behavior, so I figured I flag it just in case.
I am using the same network structure I mentioned in https://github.com/lightninglabs/lightning-terminal/pull/848#pullrequestreview-2385209814 except now the assets channels have 10M PUSD and the sats channel has 10BTC. When I make a 5M PUSD multi-hop invoice payment from alice to dave, the resulting channel asset balances between alice and bob has 4,999,990 local and 5,000,010 remote. Whereas, the channel asset balances between carol and dave are 5,000,000 on both local & remote as expected.
 Are fees paid for using the asset instead of sats and factored into the exchange rate?
BTW, I'm using --taproot-assets.experimental.rfq.mockoracleassetsperbtc=1000000 so there is a 100 sats to 1 PUSD exchange rate.
Here are the logs from all 4 nodes: polar_large_pmt_logs.zip.
I also took a screen capture of the behavior in Polar, if it's helpful.
https://github.com/user-attachments/assets/434d5884-2b8f-47b5-b6ab-686ecb9282ac

Thank you for flagging, @jamaljsr.
This is indeed correct. The routing fees are paid with assets. By default, the fees are 1ppm (and 1 sat base fee) for each hop, so things add up. 1ppm of 5 million units is 5 units, with 2 hops that's 10 units. The base fee is truncated because of the inaccuracy of the asset unit (1 unit represents multiple satoshi instead of the other way around).
Coincidentally I just finished a PR today that does the conversion rate and balance accounting down to the single satoshi in https://github.com/lightninglabs/lightning-terminal/pull/883. So I'm quite confident everything is correct now and some of the previous inaccuracies of the RFQ system have been resolved.

Of course the routing fees are actually paid in sats to the two routing nodes, calculated from the satoshi amount of the forwarded payment. But expressed in asset units, those fees add up to 10 units for the specific payment.

Thanks so much for the explanation. Now it totally makes sense.
I just have one follow-up question, for my own information, in the cases when sending smaller asset payments. If I only send 500 PUSD, how are the routing fees distributed? I assume the equivalent sats value is too small to be represented as an asset unit. Are the fees then added to the sats amount of the HTLC?

There is a certain amount of "underpayment" allowed when the conversion from asset to sats is off due to the precision. Currently 1 asset unit per HTLC (and up to 16 asset units per invoice, due to the MPP default max shard amount of 16) is allowed. That precision loss is basically paid by the edge node.
To avoid those precision losses to be significant amounts, the asset precision (decimal display) should be chosen correctly (a value of 6 for example, see the RFQ doc in the tapd repo).

See:
https://github.com/lightninglabs/lightning-terminal/issues/907

I tried to build the latest commit (dff9b28) today and ran into this error
$ make install
go: downloading github.com/lightninglabs/aperture v0.3.2-beta.0.20241015115230-d59b5514c19a
/Users/jamal/gocode/pkg/mod/github.com/lightninglabs/loop@v0.28.8-beta.0.20241022072406-1e8ae31ddc27/client.go:15:2<EMAIL_ADDRESS>invalid version: unknown revision d59b5514c19a

Thanks for the report. Looks like a temporary commit of aperture is no longer reachable but was still cached for me.
Fixed it by pushing an updated loop version. Hope it works for you as well now.

Thanks for the quick turnaround. Unfortunately I'm still getting a similar build error with the updated loop version when using commit 27316c8
go install -v -trimpath -tags="litd autopilotrpc signrpc walletrpc chainrpc invoicesrpc watchtowerrpc neutrinorpc peersrpc" -ldflags " -X github.com/lightningnetwork/lnd/build.Commit=lightning-terminal-v0.14.0-alpha.rc1-1-g27316c8281be5bb1036d1cf60254ff27378cbefc -X github.com/lightningnetwork/lnd/build.CommitHash=27316c8281be5bb1036d1cf60254ff27378cbefc -X github.com/lightningnetwork/lnd/build.GoVersion= -X github.com/lightningnetwork/lnd/build.RawTags=litd,autopilotrpc,signrpc,walletrpc,chainrpc,invoicesrpc,watchtowerrpc,neutrinorpc,peersrpc -X github.com/lightninglabs/lightning-terminal.appFilesPrefix= -X github.com/lightninglabs/lightning-terminal.Commit=v0.14.0-alpha.rc1-1-g27316c8281be5bb1036d1cf60254ff27378cbefc -X github.com/lightninglabs/loop.Commit=v0.28.9-beta.0.20241121150838-d198bb8230a8 -X github.com/lightninglabs/pool.Commit=v0.6.5-beta.0.20241015105339-044cb451b5df -X github.com/lightninglabs/taproot-assets.Commit=v0.5.0-rc1" github.com/lightninglabs/lightning-terminal/cmd/litd
go: downloading github.com/lightninglabs/aperture v0.3.2-beta.0.20241015115230-d59b5514c19a
/root/go/pkg/mod/github.com/lightninglabs/loop@v0.28.9-beta.0.20241121150838-d198bb8230a8/client.go:15:2<EMAIL_ADDRESS>invalid version: unknown revision d59b5514c19a
Makefile:145: recipe for target 'go-install' failed
make: *** [go-install] Error 1

Okay, I see what's going on. The wrong version comes from taproot-assets. Pushed a temporary replace, will create a permanent fix in tapd.

Yup, that resolved the issue. Thank you for the fix 🙏


PHP: Add version 8.3

Add PHP 8.3 ts and nts

/verfiy

I noticed that I'm having a typo in the version number in my branch name, is this a problem?


Integrate Global Search API with Search Bar

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #171
Test URLs:

Before: https://main--icicidirect--aemsites.hlx.live/research/equity

After: https://globalsearchv2--icicidirect--aemsites.hlx.live/research/equity

[ ] New Blocks introduced in this PR
If yes, please provide details below

Block Name
Documentation

NA

Original Site does not perform search on single character ? its happening here https://globalsearchv2--icicidirect--aemsites.hlx.live/research/equity
is it possible to fix this ?

Original Site does not perform search on single character
Okay I can add this, we can check with ICICI once if they want to allow 1 char search since the API is supporting it.


revise definition for mitotic spindle assembly, (and child terms)

After discussion with Takashi Toda:
Current Def
The aggregation, arrangement and bonding together of a set of components to form the spindle that contributes to the process of mitosis.
Revised Def
Mitotic bipolar spindle assembly begins with spindle microtubule nucleation from the separated spindle pole body, includes spindle elongation during prometaphase, and is complete when all kinetochores are stably attached the spindle, and the spindle assembly checkpoint is satisfied.
This means that
i) GO:0061804 mitotic spindle elongation during mitotic prophase
should be part of spindle assembly.
However Takashi also says that the "spindle midzone assembly" term might be problematic  because it is possible that this occurs after bipolarity is achieved, at which point the spindle is considered to be assembled.
It might seem odd for "mitotic spindle midzone assembly" not to be descendant of "mitotic spindle assembly"
Perhaps the primary term name could be should renamed to "mitotic spindle polar microtubule interdigitation"?
and  remove it as a descendent of "mitotic spindle assembly"
@mah11  may have knock on effects for FYPO?

Takashi also thought that "aggregation" sounded a bit odd so maybe that can be moved from the textual definition?

This one seems fairly straightforward. Let me know if you have any questions can discuss on Tues if so.

I'm going to transfer this one to
https://github.com/geneontology/go-ontology/issues/13461
because it deals with the same terms


DisplayServer: Don't fallback to headless

Unless users requested the headless driver specifically, they expect to either
see a window, or that the process terminates if there's an error.
Currently it would fallback to headless so they'd unexpectedly get a valid headless
instance if their DisplayServer failed initializing (e.g. missing Vulkan support).

Fixes #58414.
Supersedes #59074.

Depends on #62555, otherwise it's crashing on exit in the case where it couldn't initialize a DisplayServer.
With #62555, it prints an error instead (which itself is likely a bug that could be fixed independently):
$ VK_ICD_FILENAMES= godot-git
Godot Engine v4.0.alpha.custom_build.e7197cb6f - https://godotengine.org
ERROR: No surface extension found, is a driver installed?
   at: _initialize_extensions (drivers/vulkan/vulkan_context.cpp:353)
ERROR: Could not initialize Vulkan
   at: DisplayServerX11 (platform/linuxbsd/display_server_x11.cpp:4684)
ERROR: Unable to create DisplayServer, all display drivers failed.
   at: setup2 (main/main.cpp:1700)
ERROR: BUG: Unreferenced static string to 0: interface_added
   at: unref (core/string/string_name.cpp:131)

The last ERROR here is printed using the fallback.

How does this PR compare to https://github.com/godotengine/godot/pull/59074?

How does this PR compare to #59074?

Ah thanks, I knew I remembered a PR that did something like this but couldn't find it again.
I think my solution is more elegant, poke @RandomShaper for cross-review.

To do a recap on how this PR compares to mine:

This one assumes that headless will always correspond to the highest index. Mine checks by name, but to do that it has first to create and destroy it if turned out to the headless one, since there's no API to check the name beforehand.
Mine adds an abrupt exit (exit(255);) in case no display driver works. If I remember correctly, that was to avoid the engine startp ending in a crash that could cause further confusion to the user.

Regarding 1), I can't really tell which approach is better. Regarding 2), if it's still relevant for its purpose, I'd include it in whatever PR we end up merging.

For 1., this is seems to be the intended design that headless should always be last:
https://github.com/godotengine/godot/blob/20d4c660667e6515e7a623b6eb9fe876c55ddad6/servers/display_server.cpp#L793
But might need double checking.
For 2., I had a crash but I fixed it with #62555. I think it's nicer to let Godot try to exit gracefully than doing a hard exit, so we can properly do finalize steps.

Fair enough.
If we can somehow check under DEV_ENABLED that headless is the last one, cool. If not possible, I'm happy as well now I know it's like a design rule.

Added a couple DEV_ASSERT checks to validate that the headless DisplayServer is the last entry, and likewise for the dummy AudioDriver.


⚠ Mobitopup has degraded performance

In 2411002, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 6135 ms

Resolved: Mobitopup performance has improved in cbf9688.


how to map lidar bounding box coordinate on the map

I am using the waymo perception dataset v1.4.2 that comes with map. The tfrecord file has a field:
laser_labels {
box {
center_x: 39.862915373549185
center_y: 37.57924021856002
center_z: 3.9028802750369778
width: 2.07522034497737
length: 3.6631732945601687
height: 1.7400000000000038
heading: 1.563768235771243
}
metadata {
speed_x: -8.445226685916751e-29
speed_y: 0.0
accel_x: 1.0556533986614397e-28
accel_y: 0.0
speed_z: 1.6494583370931155e-31
accel_z: -2.0618230442606244e-31
}
type: TYPE_VEHICLE
id: "-HJlbwWGxigWVjAFBBdTxA"
num_lidar_points_in_box: 52
most_visible_camera_name: "FRONT_LEFT"
camera_synced_box {
center_x: 39.859376980729586
center_y: 37.582941913788076
center_z: 3.902378373465603
width: 2.07522034497737
length: 3.6631732945601687
height: 1.7400000000000038
heading: 1.563768235771243
}
num_top_lidar_points_in_box: 53
}
I want to use center_x and center_y in the box field above and plot it on the map of the scenario.

But box coordinate doesn't seem to be consistent with the map. Is there some offset values I need to use to adjust the coordinates?
Am I thinking about this the right way. Can the box coordinates be plotted like this? I want to do motion prediction if I can visualize trajectory of bounding box on the map. I know there is a separate motion dataset but I still want to do motion prediction with this dataset.

Hi,
The issue is that the labels are in the local vehicle frame coordinates but the map data is in global frame coordinates. For each frame you need to use the pose field to transform the label points.  Here is some example code to visualize the map data along with the vehicle box centers:
import numpy as np
import plotly.graph_objs as go
from waymo_open_dataset import dataset_pb2
from waymo_open_dataset import label_pb2
from waymo_open_dataset.utils import frame_utils
from waymo_open_dataset.utils import plot_maps

def plot_map_with_boxes(frames: list[dataset_pb2.Frame])->None:
  """Plot the point clouds within the given frames with map data.

  Map data must be populated in the first frame in the list.

  Args:
    frames: A list of frames to be plotted, frames[0] must contain map data.
  """

  # Plot the map features.
  if len(frames) == 0:
    return
  figure = plot_maps.plot_map_features(frames[0].map_features)

  def get_transform(frame_num: int):
    tform = []
    for v in frames[frame_num].pose.transform:
      tform.append(v)
    tform_tensor = tf.transpose(tf.reshape(tf.convert_to_tensor(tform, dtype=tf.float32), [4, 4]))
    return tform_tensor

  for object_index in range(len(frames[0].laser_labels)):
    # Get the box centers for a single object.
    label = frames[0].laser_labels[object_index]
    if label.type != label_pb2.Label.Type.TYPE_VEHICLE:
      continue
    id = label.id
    points_global = []
    for i in range(1, len(frames)):
      for label in frames[i].laser_labels:
        if label.id == id:
          # Transform the point into global coordinates.
          transform = get_transform(i)
          point = tf.convert_to_tensor([label.box.center_x, label.box.center_y, label.box.center_z, 1.0], tf.float32)[tf.newaxis, :]
          point_global = tf.matmul(point, transform)[0, 0:3].numpy()
          points_global.append([point_global[0], point_global[1], point_global[2]])

    # Plot the box center points.
    points_global = tf.convert_to_tensor(points_global, tf.float32)
    figure.add_trace(
        go.Scatter3d(
            x=points_global[:, 0],
            y=points_global[:, 1],
            z=points_global[:, 2],
                        mode='markers',
                marker=dict(
                    size=4,
                ),
            )
        )

  figure.show()

Example output:

@scott-ettinger  Thank you for the above code. It worked for me. Just one more issue, I also need heading of vehicles for motion prediction. does this transformation from local to global frame also apply to heading? If so, how would I apply pose to transform heading? There seems to be more than three values in the pose field.

The pose field as used in the code above is a standard 4x4 transformation matrix.  You can use it to either transform a unit 3 dimensional vector representing the heading or you can use the individual rotation components from the transform to compute the rotation angle in 2D.


Update virtual-machines-linux-dockerextension.md

Fix typos.

Hi @alexandair, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

@alexandair : Thanks for your contribution to the Azure documentation! The author, @iainfoulds, has been notified to review your proposed change.

Thanks for the updates! These look good to me.
@tysonn #sign-off
I'm on vacation this week, but there's also https://github.com/Azure/azure-content/pull/7441 that's still outstanding - there's a merge conflict as I'd already made some updates to that doc. I'd noted in that PR that you can either resolve the errors in that PR, or close it out and pull the latest changes before submitting a new PR. Thanks again!


update document for storage/transport secret names

Refers: https://issues.redhat.com/browse/ACM-4732

/cc @clyang82 @morvencao


Fix ts deployment

My bad, I broke the workflow last second :D https://github.com/joschahenningsen/TUM-Live/actions/runs/1736543074

Finally. @alexanderstephan
Now as soon as the action removes the label, the server is deployed.


fix: Fixed receive screen bugs

Fixes #526 , #552 and #540

@UncleSamtoshi I've made your suggested change and responded to your comments.  I'll leave the comments for you to resolve if you feel like I've addressed them appropriately.


feat: convert to PaymentExitGame.getInFlightExitIds(bytes[])

Will do this in https://github.com/omisego/ex_plasma instead. Thanks @boolafish!


[Statie] Add output path support on generator items

---
id: 202
title: "Is Zend Dead? CakePHP on the Rise? Trends of PHP Frameworks in Downloads"
outputPath: trends
---

This should work, but doesn't. Many great bloggers use custom short links, easy to read and remember:

https://zenhabits.net/focus-antidote/
https://sivers.org/n

Comparing to:

http://localhost:8000/blog/2019/04/08/what-you-lose-by-switching-to-symfony/

There is a workaround, I use following generator configuration:
parameters:
    generators:
        posts:
          route_prefix: ''

It's not the cleanest way, but it's working.


[C++][CMake][Windows] Don't use .dll suffix for system libraries such as ws2_32

Describe the bug, including details regarding any error messages, version, and platform.
We should use import library (.lib) no DLL (.dll) to link with system libraries. So target_link_libraries(... ws2_32.dll) is wrong. (But it seems that it works with MSVC...)
We should use target_link_libraries(... ws2_32.lib) (use .lib) or target_link_libraries(... ws2_32) (no extension).
See also: https://cmake.org/cmake/help/latest/command/target_link_libraries.html#command:target_link_libraries

A plain library name: The generated link line will ask the linker to search for the library (e.g. foo becomes -lfoo or foo.lib).

See also: https://github.com/microsoft/vcpkg/pull/38295/files#r1574568441
Component(s)
C++

So target_link_libraries(... ws2_32.dll) isn't wrong. (But it seems that it works with MSVC...)

This isn't true: https://github.com/microsoft/vcpkg/issues/38305 is the original issue from vcpkg users.
The key problem is that the ws2_32.dll is published to the link interface for static library linkage. You won't notice until you consume the CMake config.

Ah, sorry. The "isn't" is a typo... It should be "it".

Issue resolved by pull request 41341
https://github.com/apache/arrow/pull/41341


Zoom bug

If inner zoom is enabled it pops to the middle when click and has zoomed in if outer enabled then pops middle if u zoomed out!

https://gyazo.com/27195b6a9cd1ce8160239ccf98e23a24

Fixed in #1416


First Time Run - No module named 'ruamel'

Describe the bug
pluGET-v1.7.2
From Windows CLI when performing first time run to generate config yaml, it throws an error "No module named 'ruamel'"

Traceback (most recent call last):
File "C:\Minecraft\Sandbox\pluGET-v1.7.2\pluget.py", line 10, in
from src.handlers.handle_config import check_config, validate_config
File "C:\Minecraft\Sandbox\pluGET-v1.7.2\src\handlers\handle_config.py", line 7, in
import ruamel.yaml
ModuleNotFoundError: No module named 'ruamel'

To Reproduce

Install Windows python 3.10.4 x64
Run install_requirements_WINDOWS.bat
(Using Windows CLI) run py pluget.py

Expected behavior
Generation of pluGET_config.yaml
Desktop (please complete the following information):

OS: Windows 10

Re-running install_requirements_WINDOWS.bat resolved issue and I was able to successfully generate config

I’m having this issue, and no matter how many times I run the install requirements batch file, it still gives this error


Skip buffer setup process when not necessary

With the following settings, it is not necessary and can be skipped:
let g:gutentags_generate_on_new = 0
let g:gutentags_generate_on_missing = 0
let g:gutentags_auto_set_tags = 0
set tags=./tags;/

It will still be triggered on write and if the global config switches
get changed.

Hi, thanks for the patch!
What are you exactly trying to fix here? Given the following configuration settings, Gutentags should already do nothing, unless there's a bug, or unless you're trying to increase performance?
Also, I'm not sure how it can gracefully re-enable functionality when the global config switches are changed since it completely skipped the setup? I think you'd have to reload each buffer with something like :e<cr> no?

Would this potentially fix #25 and this vim-go issue?
I'm thinking the b:gutentags_files buffer var may not be set up between when the quickfix window for a linter is displayed and when :UpdateTags is run, causing the undefined variable error. Thoughts?

@bruschill : As you've probably seen by now, issue #25 was something else and is now fixed.
@blueyed : It looks to me like you want to use Gutentags in a "manual way", i.e. make it not do anything automatically, and use GutentagsUpdate by hand instead? If that's the case, there may be better plugins out there for you -- the whole premise of Gutentags is to let you not have to think about tags at all anymore. If you're trying to do something else, what is it?
The GutentagsUpdate command is really meant for edge cases like debugging or forcing an update after you pull/update your repo while Vim is still running.


[FD] General Small Changes

Removes the AssaultSetFightRadius for nuke titans, this prevents them from stopping and shooting at things, now they head straight for the harvester without distractions
Removes the damage scaling on self-inflicted damage to more accurately mimic vanilla
scip -> skip

I believe it gets set to 0 when they are spawned, however I also remember that the console complained that it was below the minimum value for nuke titans (32), so we should probably be using that instead of 0 really?

I believe it gets set to 0 when they are spawned, however I also remember that the console complained that it was below the minimum value for nuke titans (32), so we should probably be using that instead of 0 really?

hmm I don't believe nuke titans ever stop moving to shoot at something tho, think its safer to keep it at 0


Fix prices containing commas

Fixes #12
Note: This also includes the code from #11 so that PR should be looked at first. The diff for this PR becomes more to-the-point with those changes already merged.

Since this includes the code of #8 #9 #10 and #11 you could just merge this one and #13 and that would be all the PRs. The reason I did multiple was because I like to keep each PR to a specific change. However there was some groundwork to do to setup unit testing for these PRs which is why they all contain code form earlier PRs

Since this includes the code of #8 #9 #10 and #11 you could just merge this one and #13 and that would be all the PRs. The reason I did multiple was because I like to keep each PR to a specific change. However there was some groundwork to do to setup unit testing for these PRs which is why they all contain code form earlier PRs

Thanks for all the cleanup, tests, documentation, and fixes!

Thanks for all the cleanup, tests, documentation, and fixes!


docs: need update documentation for better experience

Missing sections

[x] Getting started
[x] Environment variables
[x] Handlers
[x] Rules
[x] BotApi
[x] Datatypes (deprecated)
[x] Properties (enhancement)

Commentary
Maybe in future I'll add some sections (i.e. builders #6).

Completed in #13 .


Added convention option support to pydocstyle

Implemented the convention option that lets the user select their preferred documentation style (pep257, numpy, google).
It's been done in a similar way to how pydocstyle does internally: filtering the errors using a preset for that convention.

Coverage remained the same at 78.269% when pulling 05b2ee1ea34769122ec8d66bf79c66d5218c5f0e on DaniGuardiola:patch-1 into f436ccc6b55b33381a295ded753e467953cf4379 on klen:develop.

@DaniGuardiola Thank you for the PR!


USD Ar2 Katana demo

What
Use OpenAssetIO USD plugin to load a assetized USD document into katana, and show resolution behaviour occuring via OpenAssetIO.
Why
A selling point of OpenAssetIO is the ability to write a single plugin that works across multiple hosts.  A "host" can include multiple components in a single application. One example is the UsdIn node in Katana alongside Katana itself, where the UsdIn node will use a USD Ar2 shim and the rest of Katana will use an Katana AssetAPI shim.
As a first step in proving out this possibility, we should investigate making our usdOpenAssetIOResolver work with the USD bundled within a Katana release; and then prove that it works to resolve assets within a Katana session.
Notes
A decent demo might be something like :

Load a USD document with 2 identical objects, one has an assetized texture and one has no texture.
In katana, "oh no we forgot to texture this", use the katana gui to set the same texture on the other object via the entity reference.
Thus showing that the same plugin and data is in use for the two different flow

Also, consider hacking BAL so it can reload the database somehow, such that we can show changing the data on the backend flowing through to katana.
Acceptance Criteria

Find a decent USD example document appropriate for a demo in katana
AR2 plugin is used to load assetized paths from a USD document when loaded into katana.
Show the same OpenAssetIO plugin being used in a different katana node with the same data/manager.
Do all this against the latest Katana release.
Cut a demo

Got a basic demo working. Added https://github.com/OpenAssetIO/usdOpenAssetIOResolver/issues/42 because I hit a problem that too aages to debug.
The key to making our Ar2 resolver work with Katana was to re-use the CMake helpers in https://github.com/TheFoundryVisionmongers/KatanaUsdPlugins.
I.e. CMake variables
-DKATANA_API_LOCATION=/path/to/katana
-DCMAKE_MODULE_PATH=/path/to/KatanaUsdPlugins/cmake/modules;/path/to/KatanaUsdPlugins/cmake/macros"

then a tweak to the root usdOpenAssetIOResolver CMakeLists.txt
if (KATANA_API_LOCATION)
    set(USE_KATANA_THIRDPARTY_LIBS ON)
    include(Support)  # <-- this is in KatanaUsdPlugins
else()
    find_package(pxr REQUIRED)
endif ()

and then launching Katana then needs some env vars
FNPXR_PLUGINPATH=/path/to/usdOpenAssetIOResolver/conda-vfx23-katana/dist/resources
LD_LIBRARY_PATH=/path/to/OpenAssetIO
OPENASSETIO_DEFAULT_CONFIG=/path/to/openassetio_config.toml
OPENASSETIO_PLUGIN_PATH=/path/to/OpenAssetIO-Manager-BAL/plugin
PYTHONPATH=/path/to/OpenAssetIO/lib/python3.10/site-packages:/path/to/OpenAssetIO-MediaCreation/lib/python3.9/site-packages


ERROR    multiprocessing.pool.RemoteTraceback

Hi all,
I am running into an issue during the refinement stage. I have all the dependencies installed with the right version according to the tensorflow table:
Python 3.7.11
Tensor flow 2.6.2
cuDNN <IP_ADDRESS>-h90431f1_0
CUDA 11.2
Would you know what is causing the following error?
many thanks!
isonet.py refine ./subtomo.star  --gpuID 0,1,2,3

######Isonet done extracting subtomograms######

11-10 20:12:55, INFO
######Isonet starts refining######

11-10 20:13:11, INFO     Done preperation for the first iteration!
11-10 20:13:11, INFO     Start Iteration1!
11-10 20:13:27, INFO     Noise Level:0.0
11-10 20:13:28, ERROR    multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
  File "/lmb/home/cvhoorn/miniconda3/envs/isonet/lib/python3.7/multiprocessing/pool.py", line 121, in worker
    result = (True, func(*args, **kwds))
  File "/lmb/home/cvhoorn/miniconda3/envs/isonet/lib/python3.7/multiprocessing/pool.py", line 44, in mapstar
    return list(map(*args))
  File "/lmb/home/cvhoorn/IsoNet/preprocessing/prepare.py", line 147, in get_cubes
    with mrcfile.open(current_mrc) as mrcData:
  File "/lmb/home/cvhoorn/miniconda3/envs/isonet/lib/python3.7/site-packages/mrcfile/load_functions.py", line 139, in open
    header_only=header_only)
  File "/lmb/home/cvhoorn/miniconda3/envs/isonet/lib/python3.7/site-packages/mrcfile/mrcfile.py", line 108, in __init__
    self._open_file(name)
  File "/lmb/home/cvhoorn/miniconda3/envs/isonet/lib/python3.7/site-packages/mrcfile/mrcfile.py", line 125, in _open_file
    self._iostream = open(name, self._mode + 'b')
FileNotFoundError: [Errno 2] No such file or directory: 'results/TS_010_iter00.mrc'
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/lmb/home/cvhoorn/IsoNet/bin/refine.py", line 25, in run
    run_whole(args)
  File "/lmb/home/cvhoorn/IsoNet/bin/refine.py", line 143, in run_whole
    get_cubes_list(args)
  File "/lmb/home/cvhoorn/IsoNet/preprocessing/prepare.py", line 189, in get_cubes_list
    res = p.map(func,inp)
  File "/lmb/home/cvhoorn/miniconda3/envs/isonet/lib/python3.7/multiprocessing/pool.py", line 268, in map
    return self._map_async(func, iterable, mapstar, chunksize).get()
  File "/lmb/home/cvhoorn/miniconda3/envs/isonet/lib/python3.7/multiprocessing/pool.py", line 657, in get
    raise self._value
FileNotFoundError: [Errno 2] No such file or directory: 'results/TS_010_iter00.mrc'

Hi,
We ran into this problem before, it was because the tomogram file name contains a dot sign.
Please tell me whether this is also your case.

That fixed it! thank you

quick script which I used to fix this for my subtomo filenames which included two leading '.' characters, might save someone some time
import starfile
import os

star = starfile.read('subtomo.star')
for src, dest in zip (star['rlnImageName'], star['rlnImageName'].str.replace('.','_', 2)):
       	os.symlink(src, dest)
star['rlnImageName'] = star['rlnImageName'].str.replace('.','_', 2)
starfile.write(star, 'subtomo_nodot.star')

I'm still running into this at the refinement step despite the subtomo names having no dots.
To be clear:

my tomogram names have dots
deconvolution and extraction work as expected
I modify my subtomo.star file and symlink the files with the script above
-I run isonet.py refine subtomo_nodot.star --gpuID 0,1,2,3 --iterations 30 --noise_start_iter 10,15,20,25 --noise_level 0.05,0.1,0.15,0.2
I get the following traceback

Traceback (most recent call last):
  File "/lmb/home/aburt/isonet/IsoNet/bin/refine.py", line 25, in run
    run_whole(args)
  File "/lmb/home/aburt/isonet/IsoNet/bin/refine.py", line 109, in run_whole
    args = prepare_first_iter(args)
  File "/lmb/home/aburt/isonet/IsoNet/preprocessing/prepare.py", line 115, in prepare_first_iter
    res = p.map(func, settings.mrc_list)
  File "/lmb/home/aburt/mambaforge/envs/isonet/lib/python3.8/multiprocessing/pool.py", line 364, in map
    return self._map_async(func, iterable, mapstar, chunksize).get()
  File "/lmb/home/aburt/mambaforge/envs/isonet/lib/python3.8/multiprocessing/pool.py", line 771, in get
    raise self._value
FileNotFoundError: [Errno 2] No such file or directory: 'subtomo/TS_009_mrc_8_80Apx_000000.mrc'

I confirm that the file does indeed exist

(isonet) hal.lmb.internal ➜  isonet  ls subtomo/TS_009_mrc_8_80Apx_000000.mrc
subtomo/TS_009_mrc_8_80Apx_000000.mrc


check for path values before indexing into objects

Hi @rfdearborn , I believe it's possible for catalog_nodes[model_name] to not have all the sub-fields. This change checks for keys in the path and returns the final value
e.g.
Traceback (most recent call last):
  File "/Users/austingibbons/stytch/dbt/notion.py", line 481, in <module>
    main()
  File "/Users/austingibbons/stytch/dbt/notion.py", line 177, in main
    col_names_and_data = list(catalog_nodes[model_name]['columns'].items())
KeyError: 'model.stytch.test_monthly'

Traceback (most recent call last):
  File "/Users/austingibbons/stytch/dbt/notion.py", line 470, in <module>
    main()
  File "/Users/austingibbons/stytch/dbt/notion.py", line 386, in main
    "number": catalog_nodes[model_name]['stats']['num_rows']['value']
KeyError: 'num_rows'

(replacing https://github.com/rfdearborn/dbt-docs-to-notion/pull/6 )

Looks great. Thanks!