What are the sensor entities called?

Describe the issue
I have installed via HACS and custom repository.
I have a weather.pirateweather entity.
Where are the sensor.pirateweather.humidity sensors?
Home Assistant version
2024.6.1
Integration version
1.5.2
Troubleshooting steps

[X] I have updated my Home Assistant installation to the latest version.
[X] I have updated the Pirate Weather Integration to the latest version.
[X] I have gone through the documentation before opening this issue.
[X] I have searched this repository and API Repository to see if the issue has already been reported.
[X] I have restarted my Home Assistant installation.
[X] I have queried the API in my browser to confirm the issue is not with the API.
[X] I have written an informative title.

Hello,
I had the same issue. Sensors not showing up even if i ticked the sensor box. I then added the sensors to the configuration.yml file, rebooted and then they were there. After that i removed the sensors from the config rebooted again and they were still there. So that might be a workaround .
Configuration.yml
sensor:

platform: pirateweather
api_key:
scan_interval: '00:15:00'
monitored_conditions:

temperature
precip_probability
precip_type
humidity
cloud_cover
nearest_storm_distance
precip_intensity
wind_speed

Hi,
I added this:
sensor:
platform: pirateweather
api_key: nzoccsh5Dbr3y6cY67DZpYgCAFZyIujX
scan_interval: '00:15:00'
monitored_conditions:
- temperature
- precip_probability
- precip_type
- humidity
- cloud_cover
- nearest_storm_distance
- precip_intensity
- wind_speed
to my configuration.yaml and then rebooted HA, not a quick reload.
They showed up.

your code above contained some odd unseen characters so you you may want to copy my code and paste it into your post. The tabs did not show an issue in HA but did stop the entities from working.

Thanks for opening this issue. When you are setting up sensors through the integration UI you need to setup the list of monitored conditions as well as click on the sensors box. If you clicked on the sensors box but didn't add anything to the list of monitored conditions it will not create any sensors for you.
@9812ga98sd I noticed in your last post that you had posted you API key so I edited your post to remove it. In the future please make sure to not post it publicly. Thanks.

@cloneofghosts Can't believe i missed that... It all works now.
Thanks!

Thanks for opening this issue. When you are setting up sensors through the integration UI you need to setup the list of monitored conditions as well as click on the sensors box. If you clicked on the sensors box but didn't add anything to the list of monitored conditions it will not create any sensors for you.
@9812ga98sd I noticed in your last post that you had posted you API key so I edited your post to remove it. In the future please make sure to not post it publicly. Thanks.

Thanks


Dashboard: clicking on ABP devices button doesn't work

This was working earlier today (I think), but it looks like a recent change broke it.
Repro:

Open dashboard
Click on an app
Click on the "ABP" button on the "Devices" section
-> error reports on console

Thanks for the report. Can you tell me what browser version you are using?
Does this happen every time? Can you post the full stack trace of the error?

Chrome 50 on Mac OS, and also Firefox.
It happens every time. (but it was working earlier, so I assume a recent deployment broke it)
Here's the stack trace:
module.exports (main.js:27427)
module.exports (main.js:28063)
from (main.js:28083)
exports.default (main.js:33616)
exports.default (main.js:33563)
ReactCompositeComponentMixin._constructComponentWithoutOwner (main.js:14030)
ReactCompositeComponentMixin._constructComponent (main.js:14016)
ReactCompositeComponentMixin.mountComponent (main.js:13939)
ReactCompositeComponent_mountComponent (main.js:7230)
ReactReconciler.mountComponent (main.js:7305)
ReactMultiChild.Mixin.mountChildren (main.js:13270)
ReactDOMComponent.Mixin._createInitialChildren (main.js:10263)
ReactDOMComponent.Mixin.mountComponent (main.js:10109)
ReactDOMComponent_mountComponent (main.js:7230)
ReactReconciler.mountComponent (main.js:7305)
ReactCompositeComponentMixin.performInitialMount (main.js:14077)
ReactCompositeComponentMixin.mountComponent (main.js:14002)
ReactCompositeComponent_mountComponent (main.js:7230)
ReactReconciler.mountComponent (main.js:7305)
ReactMultiChild.Mixin.mountChildren (main.js:13270)
ReactDOMComponent.Mixin._createInitialChildren (main.js:10263)
ReactDOMComponent.Mixin.mountComponent (main.js:10109)
ReactDOMComponent_mountComponent (main.js:7230)
ReactReconciler.mountComponent (main.js:7305)
ReactMultiChild.Mixin.mountChildren (main.js:13270)
ReactDOMComponent.Mixin._createInitialChildren (main.js:10263)
ReactDOMComponent.Mixin.mountComponent (main.js:10109)
ReactDOMComponent_mountComponent (main.js:7230)
ReactReconciler.mountComponent (main.js:7305)
ReactCompositeComponentMixin.performInitialMount (main.js:14077)
ReactCompositeComponentMixin.mountComponent (main.js:14002)
ReactCompositeComponent_mountComponent (main.js:7230)
ReactReconciler.mountComponent (main.js:7305)
ReactMultiChild.Mixin.mountChildren (main.js:13270)
ReactDOMComponent.Mixin._createInitialChildren (main.js:10263)
ReactDOMComponent.Mixin.mountComponent (main.js:10109)
ReactDOMComponent_mountComponent (main.js:7230)
ReactReconciler.mountComponent (main.js:7305)
ReactMultiChild.Mixin.mountChildren (main.js:13270)
ReactDOMComponent.Mixin._createInitialChildren (main.js:10263)
ReactDOMComponent.Mixin.mountComponent (main.js:10109)
ReactDOMComponent_mountComponent (main.js:7230)
ReactReconciler.mountComponent (main.js:7305)
ReactCompositeComponentMixin.performInitialMount (main.js:14077)
ReactCompositeComponentMixin.mountComponent (main.js:14002)
ReactCompositeComponent_mountComponent (main.js:7230)
ReactReconciler.mountComponent (main.js:7305)
ReactMultiChild.Mixin._mountChildAtIndex (main.js:13446)
ReactMultiChild.Mixin._updateChildren (main.js:13366)
ReactMultiChild.Mixin.updateChildren (main.js:13326)
ReactDOMComponent.Mixin._updateDOMChildren (main.js:10480)
ReactDOMComponent.Mixin.updateComponent (main.js:10326)
ReactDOMComponent.Mixin.receiveComponent (main.js:10282)
ReactDOMComponent_receiveComponent (main.js:7230)
ReactReconciler.receiveComponent (main.js:7369)
ReactChildReconciler.updateChildren (main.js:13617)
ReactMultiChild.Mixin._reconcilerUpdateChildren (main.js:13245)
ReactMultiChild.Mixin._updateChildren (main.js:13338)
ReactMultiChild.Mixin.updateChildren (main.js:13326)
ReactDOMComponent.Mixin._updateDOMChildren (main.js:10480)
ReactDOMComponent.Mixin.updateComponent (main.js:10326)
ReactDOMComponent.Mixin.receiveComponent (main.js:10282)
ReactDOMComponent_receiveComponent (main.js:7230)
ReactReconciler.receiveComponent (main.js:7369)
ReactChildReconciler.updateChildren (main.js:13617)
ReactMultiChild.Mixin._reconcilerUpdateChildren (main.js:13245)
ReactMultiChild.Mixin._updateChildren (main.js:13338)
ReactMultiChild.Mixin.updateChildren (main.js:13326)
ReactDOMComponent.Mixin._updateDOMChildren (main.js:10480)
ReactDOMComponent.Mixin.updateComponent (main.js:10326)
ReactDOMComponent.Mixin.receiveComponent (main.js:10282)
ReactDOMComponent_receiveComponent (main.js:7230)
ReactReconciler.receiveComponent (main.js:7369)
ReactCompositeComponentMixin._updateRenderedComponent (main.js:14441)
ReactCompositeComponentMixin._performComponentUpdate (main.js:14423)
ReactCompositeComponentMixin.updateComponent (main.js:14352)
ReactCompositeComponent_updateComponent (main.js:7230)
ReactCompositeComponentMixin.receiveComponent (main.js:14275)
ReactReconciler.receiveComponent (main.js:7369)
ReactCompositeComponentMixin._updateRenderedComponent (main.js:14441)
ReactCompositeComponentMixin._performComponentUpdate (main.js:14423)
ReactCompositeComponentMixin.updateComponent (main.js:14352)
ReactCompositeComponent_updateComponent (main.js:7230)
ReactCompositeComponentMixin.performUpdateIfNecessary (main.js:14291)
ReactReconciler.performUpdateIfNecessary (main.js:7388)
runBatchedUpdates (main.js:6923)
Mixin.perform (main.js:7719)
Mixin.perform (main.js:7719)
_assign.perform (main.js:6869)
flushBatchedUpdates (main.js:6945)
ReactUpdates_flushBatchedUpdates (main.js:7230)
Mixin.closeAll (main.js:7785)
Mixin.perform (main.js:7732)
ReactDefaultBatchingStrategy.batchedUpdates (main.js:16024)
batchedUpdates (main.js:6877)
ReactEventListener.dispatchEvent (main.js:16184)

Today I realized something: it only happens with one of my two applications!
Here I can reproduce every time: https://staging.thethingsnetwork.org/applications/70B3D57ED00001D3
but with another Application, it works just fine.

Okay. We just pushed a new version of the dashboard that has a lot of small fixes in it, including more sanity checks.
Can you check if it still occurs?

I just checked. Still occurs.

Found the error! You have a device which has a device address 00000000. The JSON serialisation on the server considers this as an empty address and doesn't send it when listing devices.
In the dashboard, the address was expected however, so the UI crashed.
I've fixed the dashboard to return a device EUI based on the device address for ABP devices, and send it even when the EUI 'empty'.
Can you verify this works now?

Works! Thanks, you're awesome!

Nice!


Expanding ImageCube Examples

Changes:

Renamed templates [size]-chunk to default
Added empirical and analytical line templates
Added emulator_base to all templates

As always, thanks for this update, @jammont! Looks reasonable to me, so @pgbrodrick, please take a look and merge if you approve.


Exit with non 0 error code on failed zappa invoke

Description

We use zappa invoke in our CI. Right now if the invoked command fails the error is printed, but no exit code is given. This PR adds a CLI argument (--exit-code) which will result in the invoke command failing if the invoked function failed. This was added as an extra CLI argument to keep the current behavior for people depending on it.
This PR still misses a test, I'd love some help guiding me in the right direction on how I would write one for this.
GitHub Issues

Coverage decreased (-0.1%) to 73.562% when pulling b03d72d6a4613c3a142157bf72905525f3eb56b0 on inytar:master into 746cd5fa002cc57c3f2f28b07edaaab4f235a02f on Miserlou:master.

Thanks for this, @inytar! I've merged this in manually but removed the CLI argument since I think this should be the proper behavior.


METRON-1139 Fixed service advisor profilerHost variable

Contributor Comments
This is a simple variable mis-naming error which doesn't cause any immediate problems, but prevents the stack advisor running properly, which can prevent subsequent component installs.
To recreate, install a metron cluster, then attempt to install another component. The next button in the ambari wizard will remain disabled on master selection, and the request history will show a 500 error on the stack advisor step. This fix solves the problem.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[x] Have you included steps or a guide to how the change may be verified and tested manually?

[x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && build_utils/verify_licenses.sh

[x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

+1 by inspection


[Net] Fix IP address resolution incorrectly locking the main thread.

This seems to be a pretty old bug, older then originally reported (at least under certain circumstances).
The IP singleton uses a resolve queue so developers can queue hostnames for resolution in a separate while keeping the main thread unlocked (address-resolution OS functions are blocking, and could block for a long time in case of network disruption).
In most places though, the address resolution function was called with the mutex locked, causing other functions (querying status, queueing another hostname, ecc) to block until that resolution ended.
This commit ensures that all calls to OS address resolution are done with the mutex unlocked.
Fixes #51181 . Note: wile in the issue this is described as a regression, this is a very old issue (according to my tests), according to my tests on Linux, and can be found even to 2.1. I suspect testing it is just tricky due to OS/router DNS caches.
3.x version here

Wow so fast 🎉

Thanks!

Cherry-picked for 3.4.

Fixes #51181 . Note: wile in the issue this is described as a regression, this is a very old issue (according to my tests), according to my tests on Linux, and can be found even to 2.1. I suspect testing it is just tricky due to OS/router DNS caches.

Isn't this a regression from #49026? If so that would explain why it's present in 2.1, as this change was made in 2.1 and not master until #49026, which was then backported to 3.x.
If so, the 3.3 branch shouldn't be affected (and indeed the fix doesn't seem to cherry-pick cleanly at least).

3.2 seems to also have the underlying bug, though maybe harder to get to (would still break if you had to HTTPRequest at least):
https://github.com/godotengine/godot/blob/3.2/core/io/ip.cpp#L99-L106


Make builder id for SLSA provenance valid URI

The SLSA provenance v0.2 spec requires that the builder.id be a
valid URI. It was just "tekton-chains" this changes it to
"https://tekton.dev/chains/v2"

This should fix #308

/lgtm

will wait for @priyawadhwa to approve.

/ok-to-test

Looks like you'll need to update TestParse as well

Thanks, will update tomorrow and push out.

/lgtm


Fix issue with previous commit importing dotaconstants

Was working on table sorting and realized my previous pull request that got merged had an error (should have tested all the views). The heroes.json from dotaconstants is different from the original json file. I have added that back in in this commit.

@vocosu Don't worry I'm fixing this at the moment so that we can use the value from dotaconstants.


Release v2.9.1+rev1

Build finished.

Build finished.

@floion I've built this PR, and tried to run hostapp-update to update to itself:
[INFO] Switching root partition to LABEL="resin-rootB"....../etc/hostapp-update-hooks.d/99-resin-grub: line 21: /mnt/boot/EFI/BOOT/grub.cfg.new: No such file or directory
Failed to run the new hooks. Running current hooks...

Checking it, on qemu grub.cfg is at /mnt/boot/grub/grub.cfg, not within the /mnt/boot/EFI/BOOT folder. This the hook is incorrect for this device type.

Thanks for the investigaton @imrehg . We will need a new meta-resin release for this

Should be fixed by https://github.com/resin-os/meta-resin/pull/932
So we need a new meta-resin release

@floion should close this PR then, since the meta-resin will be updated too, right?

Will branch from it and create a new release and then close it, yes

Superseded by https://github.com/resin-os/resin-qemu/pull/80


Insert code for a new class

In Flashbuilder, when you create a new class it puts in some boilerplate code. This can't be done in vscode (unless I'm missing something).
One option is to add the following snippet to the snippets file (distribution/src/assembly/snippets/actionscript.json):
"Package Definition": {
	"prefix": "package",
	"body": [
		"package",
		"{",
		"\tpublic class ${TM_FILENAME_BASE}",
		"\t{",
		"\t\tpublic function ${TM_FILENAME_BASE}(${1:parameters})",
		"\t\t{",
		"\t\t\t$0",
		"\t\t}",
		"\t}",
		"}"
	],
	"description": "Package Definition"
}

Also, most of the snippets are discoverable but I didn't know about ctor and class until I found this file.

When you create a new .as file, just start typing package, and it will give you a completion item that adds the package block, including the full package name and curly braces. So, for example, if you created the file com/example/MyClass.as, you can easily complete the package block like this:
package com.example
{
}

Then, you can use the "class" or "interface" snippet to add the one that you need inside the package block. It will automatically fill in the class/interface name based on the filename. So, if you start typing "class" inside the package block, you can get this:
package com.example
{
	public class Example()
	{
		public function Example(parameters)
		{
		}
	}
}

So, basically, it's two steps instead of one.
I have no plans to add more snippets at this time. I provide the same snippets as TypeScript, and I plan to keep them in sync with Microsoft's defaults.
VSCode supports custom snippets, though, so you are free to add as many as you want in your local environment.


Add os_must_gather role

os_must_gather role uses openstack-must-gather project and
container image to gather logs from openshift cluster related
to openstack.
This role drops artifacts/tasks/cluster_info.yml task file
in favor of above role.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

recheck

/hold
We're about to get a discussion with the must_gather team, let's check how we may converge, overlaps and all.

@cjeanner Below are the logs from two scenario:

When must-gather task passes: https://logserver.rdoproject.org/59/359/04971bedfca1edfbcd63fcb74449c12b52becc52/github-check/ci-framework-crc-podified-edpm-baremetal/594dd84/ci-framework-data/logs/
When must-gather tasks fails due to any issue on cluster, then rescue tasks run: https://logserver.rdoproject.org/59/359/04971bedfca1edfbcd63fcb74449c12b52becc52/github-check/ci-framework-crc-podified-galera-deployment/6039c5b/ci-framework-data/logs/

Please have a look, Thank you :-)

/lgtm


Works on one Mac (MBP) but not the other (Mac Mini) - Using the same cable to the same display

I have this strange problem where MonitorControl Works on one Mac but not the other - using the same cable to the same display. This is similar to #248  except I am not connecting two Macs to the same monitor, at the same time. We both seem to have the same problem with our latest Mac Mini's.
Mac A:
Retina MBP 15" Mid 2012 (Macbook Pro10,1)
Mac B:
Mac Mini 2018 (Macmini8,1)
Monitor:
LG 43UN700-B
MonitorControl version:
Both running v1.7.1
macOS version:
Both running 10.15.6
Problem:
MC works on Mac A but it does not work on Mac B, using the very same cable and HDMI input.
What I have tried

Various HDMI cables, even though it is irrelevant, as the same cable that works on Mac A does not work on Mac B.
Reinstalled macOS on Mac B
Tried updating to v2.0.0
Tried the brew release

What I have not tried
ddcctl on Mac B
Observations:
I can controll volume/brightness on Mac B over HDMI IF and only when a second output (USB-C) is connected - in addition to the HDMI. I am certainly on the HDMI source when controlling volume/brightness, not USB-C (although this works as well) under this condition. However I have not tried multiple HDMI connections to the same display, as the Mac Mini only has a single HDMI output.
Why not just use USB-C instead of HDMI
Because I need it for another box (running Windows)
The only thing I can think of is that MonitorControl somehow does not work as expected on HDMI 2.0, as this is virtually the only difference between my machines. I am not sure but I think my older MBP supports HDMI 1.4 at best. Let me know if there is any way I can help debug this.
Lastly, thank you for this awesome app. I really cannot live without it, so big thanks to everyone who've worked on this.

Just tried ddcctl. It detects the display but controls doesn't seem to work.
dan@Daniels-Mac-mini ddcctl % ./ddcctl
D: NSScreen #459113722 (3840x2160 0°) 163.00 DPI
I: found 1 external display
2020-07-20 20:29:03.026 ddcctl[57104:1409688] Usage:
ddcctl 	-d <1-..>  [display#]
	-w 100000  [delay usecs between settings]

----- Basic settings -----
	-b <1-..>  [brightness]
	-c <1-..>  [contrast]
	-rbc       [reset brightness and contrast]

----- Settings that don't always work -----
	-m <1|2>   [mute speaker OFF/ON]
	-v <1-254> [speaker volume]
	-i <1-18>  [select input source]
	-p <1|2-5> [power on | standby/off]
	-o         [read-only orientation]

----- Settings (testing) -----
	-rg <1-..>  [red gain]
	-gg <1-..>  [green gain]
	-bg <1-..>  [blue gain]
	-rrgb       [reset color]

----- Setting grammar -----
	-X ?       (query value of setting X)
	-X NN      (put setting X to NN)
	-X <NN>-   (decrease setting X by NN)
	-X <NN>+   (increase setting X by NN)

dan@Daniels-Mac-mini ddcctl % ./ddcctl -d 1 -b \?
D: NSScreen #459113722 (3840x2160 0°) 163.00 DPI
I: found 1 external display
I: polling display 1's EDID
I: got edid.name: LG HDR 4K
D: action: b: ?
D: querying VCP control: #16 =?
E: No data after 10 tries!
E: DDC send command failed!
E: VCP control #16 (0x10) = current: 0, max: 0

dan@Daniels-Mac-mini ddcctl % ./ddcctl -d 1 -b 20
D: NSScreen #459113722 (3840x2160 0°) 163.00 DPI
I: found 1 external display
I: polling display 1's EDID
I: got edid.name: LG HDR 4K
D: action: b: 20
D: setting VCP control #16 => 20

Looks like there is a problem with ddcctl and Mac Mini (2018)
https://github.com/kfix/ddcctl/issues/46

I agree, just bought the 2020 mac mini (2018) and although it recognises the display and shows volume going up and down it has no effect. I am using HDMI

Ended up purchasing a simple USB-C > 4K HDMI adapter from Satechi which solved my problem. My HDMI port is still useless though.

I'm experiencing the same issue, as well as another issue linked to this one. Not only does changing the brightness and volume not actually do anything, it will also sometimes cause the display output to stop working, meaning I have to restart my Mac Mini to get my display working again. This is using the same display and HDMI cable that I used for a MBP, which worked fine with MonitorControl.

Interesting finding on this, somehow related to #267 and this issue here: When i configure Split screen (using obviously same cables etc) in my LG5k the display is differently recognized in Monitorcontrol.
LG5K in Fullscreen - Vendor (Monitorcontrol NOT working): 0x9E6D

LG5K in Splitscreen - Vendor (Monitorcontrol DOES work): 0x1E6D

Model and ID stays the same - does this help troubleshooting or to find a workaround?

The same here, i add my experience here:

Mac Mini 2010 with Samsung C24F390 display connected via HDMI, all works well with MonitorControl and also similar applications (External Brightness,Native Display Brightness)
Mac Mini 2014 connected to the same display via HDMI, it does work sometimes after you repeatedly press up/down key and then stops working. And then works again. But always glitchy. So this is definitively a problem with my Mac (and others?), previously I also had another Samsung monitor with the same problem, and with the 2010 model it was working well.

Last thing to notice that the 2014 from day one sometimes showed strange artifacts when starting up (in place of Apple logo) like random dots or garbage screen, after boot it works well also with intense graphic usage. Don't know if it has something to do with it
If this can be helpful...

Seems interesting, I will try next Thursday to look into it

Seems interesting, I will try next Thursday to look into it

@damoen Hi, the display doesn't have an indication of the current signal type (I suppose is RGB anyway) but I didn't bother too much and followed this procedure because the one you linked doesn't work with Big Sur. Well, the colors went completely off (and System Profiler show "forced RGB mode"), apart from that the controls where unusable as before. ddctl doesn't work either. Seems like HDMI port has some problems, Maybe I'll try to buy an USB to HDMI adapter. If I do, I report back the results
Tell me if you need more informations or tests

@damoen Hi, the display doesn't have an indication of the current signal type (I suppose is RGB anyway) but I didn't bother too much and followed this procedure because the one you linked doesn't work with Big Sur. Well, the colors went completely off (and System Profiler show "forced RGB mode"), apart from that the controls where unusable as before. ddctl doesn't work either. Seems like HDMI port has some problems, Maybe I'll try to buy an USB to HDMI adapter. If I do, I report back the results
Tell me if you need more informations or tests

@Massi-X Did some experimenting and I can now confirm that the input color format has nothing to do with it. I have three monitors connected now and for some reason, macOS displayed YPbPr on the faulty HDMI display. This displays is now forced to RGB after running the patch-edid.rb script to no avail.
At the same time I can confidently say that the problem is not hardware related as ddctl/MC works over HDMI on the Mac Mini 2018 under certain conditions when multiple displays are connected - similar to what was observed by @dieoma76. Under this circumstance, the problem then shifts from HDMI to the other display that is connected via USB-C. Having said that I believe there is something off with the display manager in macOS in relation to the HDMI out that is sitting on the Mac Mini 2018.

@Massi-X Did some experimenting and I can now confirm that the input color format has nothing to do with it. I have three monitors connected now and for some reason, macOS displayed YPbPr on the faulty HDMI display. This displays is now forced to RGB after running the patch-edid.rb script to no avail.
At the same time I can confidently say that the problem is not hardware related as ddctl/MC works over HDMI on the Mac Mini 2018 under certain conditions when multiple displays are connected - similar to what was observed by @dieoma76. Under this circumstance, the problem then shifts from HDMI to the other display that is connected via USB-C. Having said that I believe there is something off with the display manager in macOS in relation to the HDMI out that is sitting on the Mac Mini 2018.

@Massi-X Did some experimenting and I can now confirm that the input color format has nothing to do with it. I have three monitors connected now and for some reason, macOS displayed YPbPr on the faulty HDMI display. This monitor is now forced to RGB after running the patch-edid.rb script, but to no avail. At least all of my monitors are displaying correctly in RGB now but the problem persists.
On the other hand I can confidently say that the culprit is not related to hardware as ddctl/MC works over HDMI on the Mac Mini 2018 under certain conditions when multiple displays are connected - similar to what was observed by @dieoma76. In that circumstance, the problem then instead shifts from HDMI to some other display that is connected via USB-C. Having said that I believe there is something off with the display manager in macOS in relation to HDMI on the Mac Mini 2018 specifically.

@Massi-X Did some experimenting and I can now confirm that the input color format has nothing to do with it. I have three monitors connected now and for some reason, macOS displayed YPbPr on the faulty HDMI display. This monitor is now forced to RGB after running the patch-edid.rb script, but to no avail. At least all of my monitors are displaying correctly in RGB now but the problem persists.
On the other hand I can confidently say that the culprit is not related to hardware as ddctl/MC works over HDMI on the Mac Mini 2018 under certain conditions when multiple displays are connected - similar to what was observed by @dieoma76. In that circumstance, the problem then instead shifts from HDMI to some other display that is connected via USB-C. Having said that I believe there is something off with the display manager in macOS in relation to HDMI on the Mac Mini 2018 specifically.

Maybe it has something to do with alt mode (see #102)?
I can't understand why, at least in my case, sometimes works by continuously pressing the fn key! Seems like a strange problem
On a related note I noticed my mac doesn't have an usb c port... I will buy a thunderbolt to hdmi adaptor to test if it works

Maybe it has something to do with alt mode (see #102)?
I can't understand why, at least in my case, sometimes works by continuously pressing the fn key! Seems like a strange problem
On a related note I noticed my mac doesn't have an usb c port... I will buy a thunderbolt to hdmi adaptor to test if it works

@Massi-X AFAIK alt mode is mostly a concern for adapters nowadays that convert video signals from HDMI to USB-C / DisplayPort or vice versa.
Note that Thunderbolt 3 is USB type C (USB-C) so you don't need an expensive Thunderbolt adapter just to convert the signal. Most adapters will do but stay away from the cheap ones as they often lack the alt mode technology. I ended up getting this which is high quality, reasonably priced and works perfectly well.

@Massi-X AFAIK alt mode is mostly a concern for adapters nowadays that convert video signals from HDMI to USB-C / DisplayPort or vice versa.
Note that Thunderbolt 3 is USB type C (USB-C) so you don't need an expensive Thunderbolt adapter just to convert the signal. Most adapters will do but stay away from the cheap ones as they often lack the alt mode technology. I ended up getting this which is high quality, reasonably priced and works perfectly well.

Yeah but my mac has only thunderbolt 2. The adapter is worth 10 eur so it's not expensive at all.
I think is almost 4 years that I deal with this problem, maybe it is worth a try!

Yeah but my mac has only thunderbolt 2. The adapter is worth 10 eur so it's not expensive at all.
I think is almost 4 years that I deal with this problem, maybe it is worth a try!

Wow Amazon is pretty fast! I received the adapter and can confirm that, at least in my case, this was the problem. Now it works flawlessly!
Nevertheless it can be interesting finding out why MonitorControl doesn't work on the standard output

Wow Amazon is pretty fast! I received the adapter and can confirm that, at least in my case, this was the problem. Now it works flawlessly!
Nevertheless it can be interesting finding out why MonitorControl doesn't work on the standard output

Hi, since the 2018 Mini HDMI problem (as well as the 2020 M1 Mini HDMI problem) is a hardware issue and there is nothing to fix in MonitorControl regarding this, I'll close this issue.

Hi @waydabber not interested in this anymore as I have fixed it with the adapter, but worth pointing out that in my case it was a 2014 Mac mini with full size port. Bye!

Humm. Didn't know hat model had this issue as well. :s Thanks for the reply!


Do not assume that namespaces start with http://opcfoundation.org/UA/

The function NodeSetToModelDesign.CreateNamespace previously assumed that all namespaces started with http://opcfoundation.org/UA/ and removed a substring of this length from the start of the namespace. This lead to a crash if the namespace did not start with this prefix and was in total shorter.
Check if the namespace starts with this prefix, before removing it.
If this prefix is not present, then check for the shorter prefix http:// and remove that.
Then continue with the existing algorithm to replace slashes and spaces.

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

Just some background information.
I am running the UA-ModelCompiler on an XML file generated by the Siemens tool SiOME. (This tool can be used without a license to other software from Siemens.)
The team who created this object model chose a URL which does not start with http://opcfoundation.org/UA/ and so far as I am aware, there is no strict requirement that the URL should start with that prefix.
The current version of UA-ModelCompiler generates an exception if the namespace is shorter than http://opcfoundation.org/UA/.

Pushed fix.


Python 3.10 support

Hi, this currently fails to install on Python 3.10, but only because there is no 3.10 compatible wheel available for the mmh3 dependency.
Is it essential that mmh3 be used as the hash function here? Something more standard like the standard library's hashlib might prevent this issue from occurring in the future.

Hey Dustin,
I can't think/remember of any specific reason for using mmh3 -- I think we can use hashlib as well.  Let me give it a shot in the next few days of using hashlib here.


Add MissingScopesError for pack makers to explicitly trigger progressive oauth flow

This should be launched ASAP after the accompanying change in coda repo stops Coda defaulting to forcing progressive OAuth: https://github.com/coda/coda/pull/74035

@jonathan-codaio The CLI coda auth command takes an optional --extra_oauth_scopes='first second third' param - it's up to the pack maker to use that to manually refresh the scopes. The formula execution does try to refresh the access token on 401, but that's the only special casing. I don't think this change needs an update to all that.


console.sst.dev login email delivery issues

Hey guys, I've tried logging into https://console.sst.dev a few times now but never received the login code via email. The obvious spam & trash checks are done :)

Can you send me the email domain through Discord? Let's check why it's getting blocked.


Can't load svg file in nuxt version 1.0.0-rc3

try change ~assets to ~/assets

@BjornMelgaard
change ~assets to ~/assets is not work :(
`This dependency was not found:

/assets/svg/logo.svg in ./node_modules/vue-loader/lib/template-compiler?{"id":"data-v-331f1379","hasScoped":true,"preserveWhitespace":false}!./node_modules/vue-loader/lib/selector.js?type=template&index=0!./pages/index.vue`

now you have to change your paths from ~something to ~/something`

:man_shrugging:

Have you tried somthing like:

or

I also encountered the same problem. i tried these,

1.0.0-rc6, getting Failed to load resource: net::ERR_CONTENT_DECODING_FAILED when loading an SVG like this in production:

It loads sometimes. It might be related to the service worker. I've just ported project from Ream to Nuxt.

Please use last version of nuxt.js please and re-open if still broken.


(Manual Review) Pull request has issues with another token that i do not touch at all and makes build/automerge fail;

I'm submitting a ...
[X] bug report
[ ] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

Summary
Everytime i make the PR it will fail to build, and give me this address as the issues- CfNkADyvwg66yLtctbuDo381s6VqVC8583ur7uvooE43
I do not have anything to do with this token so i prefer not to mess with it but it tells me i cant add the same token that already exists.

when i delete the following token, CfNkADyvwg66yLtctbuDo381s6VqVC8583ur7uvooE43 in the PR, it will build no problem, but when it automerges it fails.

Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)
the Most recent PR that still gives me the error
https://github.com/solana-labs/token-list/pull/22287

https://github.com/solana-labs/token-list/pull/22267/files - here is an old PR that managed to pass the tests after deleteing the other token but it failed to automerge

Please modify only your token and submit a PR with just that.

Please modify only your token and submit a PR with just that.

i have tried multiple times and when i dont modify any other token i still get errors of duplicate tokens because of that address. many others seem to have this issue aswell
i posted two prs,
the first being only a modification of my token but still caused an error.
the second was an example of the token being removed fixing the build error

The offending token (Honey Badges) had a duplicate that is now deleted. Please try again and see if you get the same error


Moving build from podman to a BuildConfig

Moving to an OpenShift native BuildConfig to build the SFO

It turns out operator-sdk is not really needed for this. :P

It doesn't require podman or any special perms in the build container!

Just access to the openshift API to create the build object

Cleaned up separation of build, deploy, and test

 Investigate zuul, dciy, gitlab, ocp jenkins, etc to see if they smoothe the path forward

Initial Testing
This work isn't done, but the build itself appears to work just fine.
BuildConfig POC
$ oc new-project buildtest
[...]

$ oc get is
No resources found.

$ ./build.sh
Error from server (NotFound): imagestreams.image.openshift.io "service-assurance-operator" not found
imagestream.image.openshift.io/service-assurance-operator created
Error from server (NotFound): buildconfigs.build.openshift.io "service-assurance-operator" not found
buildconfig.build.openshift.io/service-assurance-operator created
build.build.openshift.io/service-assurance-operator-1 started

$ oc get build
NAME                           TYPE     FROM          STATUS     STARTED              DURATION
service-assurance-operator-1   Docker   Git@8dc707a   Complete   About a minute ago   56s

$ oc get is
NAME                         IMAGE REPOSITORY                                                                               TAGS     UPDATED
service-assurance-operator   default-route-openshift-image-registry.apps-crc.testing/buildtest/service-assurance-operator   latest   About a minute ago

Neat! So I build the docker image without using operator-sdk, which solves all of the podmad issues I had. :P
Does it work in CI?
[csibbitt@laptop build (csibbitt-902-buildconfig) (⎈ |default/api-crc-testing:6443/kube:admin)]$ ./build_ci.sh
[...]
* [info] Building...

Error from server (NotFound): imagestreams.image.openshift.io "service-assurance-operator" not found
imagestream.image.openshift.io/service-assurance-operator created
Error from server (NotFound): buildconfigs.build.openshift.io "service-assurance-operator" not found
buildconfig.build.openshift.io/service-assurance-operator created
build.build.openshift.io/service-assurance-operator-1 started

* [info] Re-deploying with local build...

subscription.operators.coreos.com "serviceassurance-operator-alpha-redhat-service-assurance-operators-openshift-marketplace" deleted
clusterserviceversion.operators.coreos.com "service-assurance-operator.v0.1.1" deleted
serviceaccount/service-assurance-operator created
role.rbac.authorization.k8s.io/service-assurance-operator created
rolebinding.rbac.authorization.k8s.io/service-assurance-operator created
clusterserviceversion.operators.coreos.com/service-assurance-operator.v0.1.1 created
serviceassurance.infra.watch/saf-default created

* [info] CI Build complete.  It works!
Note the "ErrImagePull" Warnings. This is because we don't wait between triggering the build and redeploying the patched CSV that uses it. It will retry until the image appears in the registry, or eventually our test job will time out. In addition to this, I moved the build step AFTER the quickstart.sh call because you need a namespace to exist before you can run a Build in it - this means we don't even attempt the build until after the first trunk deployment. So overall this is cleaner but quite a bit slower to fail than the previous build strategy. If it helps us align more closely with other OpenShift projects, it's worth it, though.

Awesome looks great!

Final version hasn't been tested end-to-end, but feel free to give it a shot (or maybe CI bot will do it for me?)
I especially like this part. Nice and clean:
``
- ./build/build.sh
- ./build/deploy_ci.sh
- ./tests/smoketest/smoketest.sh

@pleimer this also eliminates all of the builder service account funny business requirements and podman and stuff from the ci server container. I'll tidy up that side once this merges.

CI Failed; it looks like it never succeeded in instantiating the components after the local build (operators are there but none of the local components). I'll re-test locally and see if I can spot why.

Worked locally, but doesn't work in the CI Bot. At least two problems:

Build itself fails with error: the directory "." is not a valid Git repository: fatal: not a git repository (or any of the parent directories): .git  which is a bit of a surprise
The fact that the build failed should have caused the entire test to fail, but it continues on

@pleimer @leifmadsen FYI this is passing CI now (love being able to say that again!), but we want to merge https://github.com/redhat-service-assurance/service-assurance-operator/pull/44 first and fix this on top of it, so I will not merge it yet.

I fixed a single conflicted line (to take your value) and this seems to be good to go! Let's see what the bot says


Blender doesn't export textures correctly to gltf

Describe the bug
Blender is not exporting textures for certain gltf files, when they contain multiple maps (e.x. a roughness map and a texture map).
To Reproduce
Steps to reproduce the behavior:
Check the .blend file attached. Try exporting the model as gtlf
Expected behavior
We would expect textures to be exported, but we don't see any in the exported file.
Screenshots
Input: Textures in input

Output: No textures in output

.blend file/ .gltf
https://drive.google.com/file/d/1j-FoT3Ca-_--k3rO-5mr4STfwDkCvRny/view?usp=sharing
Version

OS:  Windows
Blender Version 3.0.0

Additional context
This issue doesn't happen always, but I noticed that this issue happens when there are multiple maps attached to a mesh (e.x. a roughness map and a texture map or multiple texture maps)

Hello,
glb specification use PBR materials, so you have to use Principled Shader in Blender if you want to export materials from Blender to glTF or glb.
You can find documentation here : https://docs.blender.org/manual/en/latest/addons/import_export/scene_gltf2.htm
And a complete example here : https://docs.blender.org/manual/en/latest/addons/import_export/scene_gltf2.html#example

My question is... Why doesn't Blender automatically convert all materials to that type of material when exporting to glTF, instead of setting everything to white and not displaying any kind of error or warning?

Blender does export materials trying to keep what is possible (for example, AO in this example).
What is not possible to get, we keep the default value, that is white for baseColorFactor


java.lang.UnsatisfiedLinkError CentOS 7

CentOS 7
java 1.8.0_171
java.lang.UnsatisfiedLinkError: /tmp/sqlite-<IP_ADDRESS>-9c96fb8b-8402-43e1-bfd9-9974fbd99a84-libsqlitejdbc.so: /tmp/sqlite-<IP_ADDRESS>-9c96fb8b-8402-43e1-bfd9-9974fbd99a84-libsqlitejdbc.so: failed to map segment from shared object: Operation not permitted
The libsqlitejdbc.so file was create in the /tmp directory which is mounted with the noexec flag.
Unfortunately I am not at liberty to change the mount properties of the /tmp directory (controlled by IT) so I'm not sure how to work around this.
I've tried putting export JAVA_OPTS=-Djava.io.tmpdir=some_other_directory in my .bashrc but after sourcing my .bashrc file I still got the same error.

I found the answer:
I needed to use _JAVA_OPTIONS instead of JAVA_OPTS
You can close this one out.


WIP: Add Function for Removing Duplicated Rows

I added the function to detect and remove duplicated rows in raw data, meaning the rows which have exactly same x,y-coordinates with different timestamps as their previous rows. Those rows must be removed prior to calculating angles within each path, or otherwise compute_angles function would return an error. For details, see issue #122.
@aksam-ahmad please review.

Coverage increased (+2.1%) to 63.105% when pulling d4523b0c9331fe689037dffc53a648ad6d25371a on togawa28:add_clean_movement#122 into fe934f35e67546a66e3cc71c8f58aec6ea14211d on berkeley-stat222:master.

Looks good! This is ready to MRG. Thanks!

@aksam-ahmad and @jJasonWang thank you for reviewing!


Display name doesn't show user name if display name is None

This only affects users created with createsuperuser.
It seems like get_display_name isn't working as intended.
Steps to reproduce:

Create superuser
Create article with comments enable
Comment as that superuser
Comment name will show 'None'

Fixed by #828


optional div

Fixes #17

@ElDeveloper can you review this PR (should be quick). The impression that I had from the issue is that the the list will be appended to the passed div, but it looks like it is still appended to the body of the document. Is that correct or I'm misunderstanding something?

@josenavas You are right, the moi_list object should be appended to whatever element is being passed in the div argument. Re-reading my comment in #17, I now realize that I completely misunderstood @wasade here:
https://github.com/biocore/mustached-octo-ironman/issues/17#issuecomment-107744136
... sorry :L

No worries, how's that last commit look?

:+1:

:+1:

le merge?


Adding the Support for the new floodlight from Reolink

Hello Team
It's possible in a future release adding the new devices floodlight to this integration?

Thank you and best regards

Should be possible. Need all available specifications and your willingness to act as a test bed. For some while I have been considering polishing the integration with regard to camera floodlight control. And to cater for situation (eg 510) where Reolink erroneously reports capability that does not exist.

Should be possible. Need all available specifications and your willingness to act as a test bed. For some while I have been considering polishing the integration with regard to camera floodlight control. And to cater for situation (eg 510) where Reolink erroneously reports capability that does not exist.

Great thank you for your interest in this.
Yes, I'm available to test,  I have one POE floodlight.
Regarding the info, what You need?  I'm not an expert but I'm available to help you.
By the way I found this API manual that is mentioning floodlight control, don't know if can help or not ...
https://drive.google.com/file/d/15AFMQSMlMdpjL2USPsvYd-J9xWecrEf9/view
Thank you and best regards

May be a while before I can get back into looking at the code, christmas will delay things. Will send you a couple of curl commands to extract information from the unit that I need in the next week or so.On 7 Dec 2022 21:07, MiAutomations @.> wrote: Should be possible. Need all available specifications and your willingness to act as a test bed. For some while I have been considering polishing the integration with regard to camera floodlight control. And to cater for situation (eg 510) where Reolink erroneously reports capability that does not exist. Great thank you for your interest in this. Yes, I'm available to test, I have one POE floodlight. Regarding the info, what You need? I'm not an expert but I'm available to help you. By the way I found this API manual that is mentioning floodlight control, don't know if can help or not ... https://drive.google.com/file/d/15AFMQSMlMdpjL2USPsvYd-J9xWecrEf9/view Thank you and best regards —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.>

Ok No problem I understand. I will wait
Thank you

I have this floodlight. Would love support for this also, but I don't think these floodlights have an HTTP server running so it's nontrivial. There also doesn't seem to be an option to enable it, at least not yet...

What is available: they use the "Baichuan" protocol available on the device on port 9000. I started reverse engineering that a bit here and made some progress: https://github.com/thirtythreeforty/neolink/issues/324
Doesn't look like this addon supports that protocol, and I've been considering how to add it... a few options

MQTT support in neolink and integrating it that way - @QuantumEntangledAndy started work on that here: https://github.com/QuantumEntangledAndy/neolink. Would require another addon in HASS
Adding Baichuan support to this integration
Something else entirely, via AppDaemon or NetDaemon
Contact Reolink and ask them to add the HTTP API to the camera (I just did this, but have low expectations)

I also have a floodlight here. Atm any control aside the official apps would be enough for me. As far as i am following your work you were not able to make any change on the floodlight correct? Or did you manage to turn of the status LED?
Do you know this -> https://github.com/jdillenkofer/camera_proxy/blob/af9a170d3a8db831318a1aafcb2bf097ab62fd40/src/baichuan_control_layer.py (also mentiones neolink in readme)
If i would not have found your work i would have started poking around with that thing but i just started, so i most likely miss a lot of obvious stuff.

May be a while before I can get back into looking at the code, christmas will delay things. Will send you a couple of curl commands to extract information from the unit that I need in the next week or so.On 7 Dec 2022 21:07, MiAutomations @.> wrote: Should be possible. Need all available specifications and your willingness to act as a test bed. For some while I have been considering polishing the integration with regard to camera floodlight control. And to cater for situation (eg 510) where Reolink erroneously reports capability that does not exist. Great thank you for your interest in this. Yes, I'm available to test, I have one POE floodlight. Regarding the info, what You need? I'm not an expert but I'm available to help you. By the way I found this API manual that is mentioning floodlight control, don't know if can help or not ... https://drive.google.com/file/d/15AFMQSMlMdpjL2USPsvYd-J9xWecrEf9/view Thank you and best regards —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.>

Hello @ptyers
Have you any news about this subject?
Thank you in advance for you support


C/C++ Debug error

Type: Bug
I have been using VSC to code C programms for a while now, without ever encountering any problems. I have the C extensions installed, and upon hitting the "run and debug" option, my code always get compiled and the expected results are visible in the terminal.
Unfortunately, a problem appeared seemingly out of nowhere...
I tried to run a code written in C, and an error message popped saying the directory of the launch.json is unknown. It then asks to open the said file, where I can see my settings and configuration.
I might have an idea of the root of the problem.
I always connect to my gitHub account on vscode. But today I signed into my microsoft account that is used by the local computers in my University. This may have cause a Sync in the settings or something?
Please let me know in any ways how to fix this problem.
Thank you
VS Code version: Code 1.86.2 (903b1e9d8990623e3d7da1df3d33db3e42d80eda, 2024-02-13T19:40:56.878Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 7 5800H with Radeon Graphics          (16 x 3194)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.35GB (6.46GB free)

Process Argv
--crash-reporter-id 038596b8-b856-4b41-a5c8-9e0c37323787

Screen Reader
no

VM
0%

Extensions (25)

Extension
Author (truncated)
Version

vscode-terminal-for-ubuntu
Doc
0.0.2

vscode-language-pack-fr
MS-
1.85.2024021409

debugpy
ms-
2024.0.0

isort
ms-
2023.10.1

python
ms-
2024.0.1

vscode-pylance
ms-
2024.2.2

jupyter
ms-
2024.1.1

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

cmake-tools
ms-
1.17.16

cpptools
ms-
1.19.4

cpptools-extension-pack
ms-
1.3.0

vsliveshare
ms-
1.0.5905

java
red
1.28.1

tabnine-vscode
Tab
3.72.0

cmake
twx
0.0.17

intellicode-api-usage-examples
Vis
0.2.8

vscodeintellicode
Vis
1.2.30

vscode-java-debug
vsc
0.56.1

vscode-java-dependency
vsc
0.23.4

vscode-java-pack
vsc
0.25.15

vscode-java-test
vsc
0.40.1

vscode-maven
vsc
0.44.0

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
2e7ec940:30968132
pythontbext0:30879054
accentitlementst:30887150
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
pydisww1:30959800
edj9j583:30969295
7j2b6412:30969109
bg6jg535:30958357
ccp1r3:30958155

Can you share the exact error message? A screenshot might help, and you can check for errors in the "Window" output channel

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Force unstake all NFTs in Gemfarm

we are thinking about converting our project to pnfts and are considering if it was possible to force unstake all NFTs in the gemfarm before we converted. Is this possible as the bank manager?

No, the transfer has to be initiated by the owner of the vault. You can update to pNFTs and have it work.

I need to do this i have authority wallet, any advice?

@Exxempt How to?


Issue about the annotations cropped by patch borders

Hello, @vqdang @simongraham I'm sorry to bother you. I would like to realize if it is possible to improve classification accuracy of model by removing the copped annotations touching with borders of patchs like the picture below ?

In the tile-level code, we merge the raw probability maps and then apply post processing. Therefore, we don't have any issues with nuclei at tile borders. It's a bit different when working with the WSI as it is very memory intensive to work with probability maps at high resolution. Therefore, we use a different strategy and apply a custom post processing technique to deal with border nuclei.
Refer to this part of the code for more info.


Is there a way to implement optimistic concurrency using RepoDB?

I am currently in the process of switching from Entity Framework to RepoDB in my project and have encountered a problem: the lack of support for optimistic concurrency. Optimistic concurrency is a basic requirement in a system that stores data in a relational database and I absolutely need this feature. Is there a solution to implement optimistic concurrency the same or similar way as in Entity Framework when using RepoDB? I am aware that RepoDB is a lightweight ORM. But there has to be a way  to implement that, in my opinion. Even if this feature is not implemented in RepoDB, it should be possible to implement it sowehow by myself. The question is: how?
In Entity Framework I'm using this property declaration to enable optimistic concurrency:
[Timestamp]
public byte[] RowVersion { get; set; }
If possible, I don't want to introduce two different classes for reading from and writing entities to the database in my project. That would be a pretty big overhead.
For example, would be there a way in RepoDB to influence the creation of the SqlCommand for inserting and updating? Any other ideas?
Any help would be greatly appreciated!

Only for the SQL parameters. Can this blog help?

The FluentMapping and the PropertyHanndler seems can handle your case. But, I will read further about the optimistic query and understand it further before suggesting anything to you. But you can read more about the features of RepoDB from here.

Thank you for the suggestions. I have roughly skimmed the contents and I am not sure if this will help me. Here again the exact requirements for the support of optimistic concurrency:

When inserting, the property RowVersion (byte[]) must be ignored completely.
When querying, the field content from the database must be supplied in this property.
When updating the entity, another condition must be added to the WHERE clause: RowVersion = @RowVersion.
If the number of affected records is 0 when updating, a specific exception must be thrown or this case must be detected otherwise.

Can these requirements be met with the use of PropertyValueAttribute, PropertyHandler or FluentMapping? Is there a way to ignore a property when inserting?  Is there a way to add another condition when updating? If yes, how?

I have just seen that there is a way to add a condition to the WHERE clause when updating an entity:
var rowsAffected = connection.UpdateAll<Person>(persons, qualifiers: (p => new { p.Id, p.RowVersion }));
This works so far. However, I have not found an overload of the Update() extension method where I can specify a qualifiers expression. I would imagine it like this:
var rowsAffected = connection.Update<Person>(person, qualifiers: (p => new { p.Id, p.RowVersion }));
Is that not possible?
Now the only remaining problem is that the RowVersion must be ignored when inserting. Is there a possibility?

Everything can be achieved easily.

When inserting, the property RowVersion (byte[]) must be ignored completely.

Yes, you can utilize thefields argument like this. Only the list of fields passed on this argument will be a part of the operation. In your case, you can pass all the fields except for the RowNumber column.
Note: You can use the FieldCache object to extract all the fields from the entities.

When querying, the field content from the database must be supplied in this property.

This is given on the normal fetch operations (Query, QueryAll, ExecuteQuery).

When updating the entity, another condition must be added to the WHERE clause: RowVersion = @RowVersion.

This can be simply achieved by passing an expression like this.
connection.Update<Entity>(entity,` e => e.ColumnId == 1 && e.RowVersion == "Value");

It is like Entity Framework.
You can also pass an anonymous types or QueryField/QueryGroup object in the what/where argument. Through these objects, everything can be handled.

If the number of affected records is 0 when updating, a specific exception must be thrown or this case must be detected otherwise.

The Update and UpdateAll operations return an integer value that corresponds to the count of the affected rows. You can handle throwing an exception afterwards.

Thank you for the suggested solutions. It works now. As suggested, I use the FieldCache to get a list of the fields, remove the field which contains the RowVersion and then pass it as "fields" parameter in the Insert method:
var fields = FieldCache.Get(Entity).ToList();
var id = (int)sqlConnection.Insert<Entity>(entity: entity, fields: fields);
I forgot to mention that I have to do the exact same thing when updating. After updating, I check the return value (affected rows) and I throw an exception if necessary. That's all.
Thanks for your help! :-)

ahh... one more thing: is there a way to return all or only certain data from the affected record in the same request to the database when inserting and updating? Since the RowVersion is only incremented on the server, an additional round-trip would be necessary to fetch this information.


GCP TPU (Tensor Processing Unit) project template for TensorFlow 2.x LLM workload training/inference enablement via the landing zone - specifically TPUv5

Bootstrap TPU project

follow https://cloud.google.com/tpu/docs/run-calculation-tensorflow
https://github.com/ObrienlabsDev/machine-learning

FROM tensorflow/tensorflow:latest-gpu
WORKDIR /src
COPY /src/tflow.py .
CMD ["python", "tflow.py"]

tflow.py

import tensorflow as tf

# modify for TF - TPUStrategy
# https://www.tensorflow.org/api_docs/python/tf/distribute/MirroredStrategy#used-in-the-notebooks
strategy = tf.distribute.MirroredStrategy(devices=["/gpu:0", "/gpu:1"])

cifar = tf.keras.datasets.cifar100
(x_train, y_train), (x_test, y_test) = cifar.load_data()

with strategy.scope():
# https://www.tensorflow.org/api_docs/python/tf/keras/applications/resnet50/ResNet50
# https://keras.io/api/models/model/
  parallel_model = tf.keras.applications.ResNet50(
    include_top=True,
    weights=None,
    input_shape=(32, 32, 3),
    classes=100,)
# https://saturncloud.io/blog/how-to-do-multigpu-training-with-keras/
  #parallel_model = multi_gpu_model(model, gpus=2)
  loss_fn = tf.keras.losses.SparseCategoricalCrossentropy(from_logits=False)
# https://keras.io/api/models/model_training_apis/
  parallel_model.compile(optimizer="adam", loss=loss_fn, metrics=["accuracy"])
parallel_model.fit(x_train, y_train, epochs=10, batch_size=256)#5120)#7168)#7168)

Reference

detail comparison between NVidia tensor cores in the latest on-prem https://resources.nvidia.com/en-us-design-viz-stories-ep/rtx-5000-ada-datasheet?lx=CCKW39&contentType=data-sheet
detail comparison between GCP L4 VMs with NVidia tensor cores https://cloud.google.com/blog/products/compute/introducing-g2-vms-with-nvidia-l4-gpus

P.256 of Generative Deep Learning 2nd Edition - David Foster
https://towardsdatascience.com/how-to-build-an-llm-from-scratch-8c477768f1f9
https://github.com/allenai/allennlp/discussions/5056
https://support.terra.bio/hc/en-us/community/posts/4787320149915-Requester-Pays-Google-buckets-not-asking-for-project-to-bill

Google Project Gemini https://blog.google/technology/ai/google-io-2023-keynote-sundar-pichai/#ai-products

C4 = Colossal Clean Crawled Corpus
start 20231203:0021 - estimate $100 US for gcs egress
An average of 300mbps with peaks of 900mbps from the GCP bucket means 800GB x 8 bits = 6400Gbits at .3Gbps = 6hours ~ ETA
36GB in 26 min  = 25MB/sec = 200mbps = 11h (possibly limited by the hdd - go directly to NVMe next time

checked 0845 done
copy test HDD to HDD no raid -849 ~ 1330 = 4.5h
HDD to NVMe 1400-1455 - 250Mbps ~1h
copy test NVMe to NVMe  1456- 4-8 min  3.4-1.4 GB/s (thermal throttling) (990 pro 50% of max 8GB/s)

$93 US for GCS egress


RocketLeague updated a week ago, I can't decrypt the files at this moment

Hi,
never tried before today so I can't confirm it was working before the RL update (june 27).
This is the error I get :

Thanks :)

When appDecryptAES is called with the default KeyLen parameter of -1, it attempts to use strlen to determine the key size. This fails with Rocket League's AES key because it contains a null byte.

I understood some of these words.
haha :D
I'm a total noob, does it mean I can fix it myself by changing something on my machine ? or does the app itself need  an update ?
Thanks :)

Umodel needs an update to fix it, but it's a simple bug and doesn't require any changes to Rocket League package handling.

Ok then, good news :)
I'll keep an eye on the website then, hopefully it will get updated soon :)
Thanks a lot

there you go :)
https://we.tl/5BPkpx01gU

Done. Please download new umodel.

Looks like it works great ! thanks a lot ! :)


Debugger fixes

Navigating to the HAL browser results in the desired url being URIEncoded. This prevents the HAL browser from working properly and causes the user to manually enter the url. Ex) /api will show up as %2Fapi

Navigating to the HAL browser does not activate its tab on the sidebar.

System.api -> my apps, list does not scroll and flows over its designated frame

Fixed 1&3.
2 is still in need of fix.

Tested against gh-pages IWC instance:
http://ozone-development.github.io/ozp-iwc/debugger.html#/hal-browser/
2 is fixed.


Review package

Hi @larnsce @mianzg could you please review this first package? Also, do I first add the badges after your review?

Thank you, @margauxgo. Great job, especially considering that this is your first package!
README.rmd
You have a few references in the text. They need to be listed in a References section at the end. Did you copy/paste those from the original text of do you have a bibliography with these references (e.g. on Zotero)?
At the top of the README, we need to include a sentence like: This data was published alongside the article: "TITLE" by NAME et. al (YEAR), and then add citation in a section References at the end of the README.
DESCRIPTION
Have you reached out to the authors? They need to be listed as co-authors of this package.
Re: Badges
I will add those as part of the publishing process together with the DOI.

Thank you, @larnsce. I did copy/paste the references from the original text and reached out to the author but did not get a response yet.

Okay, then I suggest you use Zotero to compile the references you have in a biblography. I have setup this collection for you:
https://www.zotero.org/groups/4445072/global_health_engineering/collections/XESCXRQW

I made the changes accordingly.
However, I do not know why the citation appears that way (I appear as the only author, even tho I listed a few others). I tried to rewrite the CITATION.cff file but this did not help.

file https://github.com/openwashdata/rwpfunctionality/blob/main/R/rwpfunctionality.R in R seems not up-to-date
readme

polish on readme with shorter display

readr::read_csv("data-raw/dictionary.csv") |>
dplyr::filter(file_name == "YOURDATA.rda") |>
dplyr::select(variable_name:description) |>
knitr::kable() |>
kableExtra::kable_styling() |>
kableExtra::scroll_box(height = "400px")

not sure if pie chart is good idea, it often misleads the statistics with our visual bias

GitHub keywords: provide a couple of keywords on the repo profile like the following:

However, I do not know why the citation appears that way (I appear as the only author, even tho I listed a few others). I tried to rewrite the CITATION.cff file but this did not help.

Thanks, I see the authors in DESCRIPTION now. You don't need to edit the CITATION.cff. It's created from  DESCRIPTION and I am currently doing that. It's a part of the workflow that is not well documented yet.

file https://github.com/openwashdata/rwpfunctionality/blob/main/R/rwpfunctionality.R in R seems not up-to-date

@mianzg: I am updating this file. I had @margauxgo only write the dictionary.csv for now.


added border radius for ractangle border

i'm try to added border radius circullar for ractangle border, what do you think?

Closing this for now since this is pretty old compared to master. Hope someone submit new PR if this is necessary.


Every single feature idea I have

Mind-dump incoming! Only do the ones you think are feasible, though I believe all of them should be doable with FFMPEG according to my experience:

Loudness normalization

You can currently set the volume between 0 and 200%, but in FFMPEG you can set the volume to target a particular loudness (such as -14LUFS). This feature exists in FFMPEG.

Audio file support

Importing an audio file should be treated as a blank video

Okay that's everything so far.

I could add an option to set the decibel offset in the volume filter, if you could show what args you use to set LUFS that could also be done
As for audio editing, the plan was to have a new editor for that that would show the waveform and only have options normally for audio

Loudness: https://superuser.com/questions/1705712/is-ffmpeg-usable-with-audio-loudness-normalization
Applying normalization may increase or decrease the audio volume given the same loudness target, depending on how loud an input audio file is. There is an implicit "decibel" offset that is calculated based on that. I just used the stackoverflow command there
loudnesspenalty.com gives you that offset, but will only show you negative values

Added: https://github.com/Snazzah/catcut/commit/8661fa605fc6bde17744667c8be43c47747f3bdb https://github.com/Snazzah/catcut/commit/51df219f315e34b5e3b70f39062d7e097f0cc1ed


Fixed naming conventions for raw/web sockets

Why?

For consistency. I now have to add a named pipe server and having named_pipe and rawsocket just doesn't look right.

Well, the spec calls it RawSocket and WebSocket also doesn't have spaces, so to me it looks less correct if you add an underscore (replacement for a space) to the name. Especially in the user-facing command-line options.
I would say "named pipe" and "WebSocket" (or websocket if I'm lazy about camel-casing) in regular writing, consequently I disagree that it looks wrong in code.

Fair enough.  It just looked more correct IMHO
as here is no such thing as a rawsocket, or a websocket for that matter.
These are just common misspellings.
On Mon, Sep 21, 2015 at 3:08 PM, Jakob Petsovits<EMAIL_ADDRESS>wrote:

Well, the spec calls it RawSocket
https://github.com/tavendo/WAMP/blob/master/spec/advanced/rawsocket-transport.md
and WebSocket https://en.wikipedia.org/wiki/WebSocket also doesn't have
spaces, so to me it looks less correct if you add an underscore
(replacement for a space) to the name. Especially in the user-facing
command-line options.
I would say "named pipe" and "WebSocket" (or websocket if I'm lazy about
camel-casing) in regular writing, consequently I disagree that it looks
wrong in code.
—
Reply to this email directly or view it on GitHub
https://github.com/tplgy/bonefish/pull/18#issuecomment-142080367.


Flurry add Ad dependency

When I'm usingcom.flurry.android:analytics:12.11.0 package com.google.android.gms.ads.identifier.AdvertisingIdClient appears into my apk. And Play Console show warning "Ad SDK found"

I want to have a way to use firebase analytics without AD SDK.
Without flurry sdk my apk haven't ads sdk

In your app's dependency, do not include the following libraries, it should resolve your issue.
    implementation 'com.google.android.gms:play-services-base:15.0.1'
    implementation 'com.google.android.gms:play-services-ads:15.0.1'

This is sample project for issue
https://github.com/shumidub/flurry_added_ad_dep_issue_sample

Dependency "com.flurry.android:analytics:12.11.0@aar" added in app/build.gradle
Build apk
Analyze apk
GMS ADS dependency is into apk

remove "com.flurry.android:analytics:12.11.0@aar" dependency
Build apk
Analyze apk
GMS ADS dependency is not into apk

When apps have the dependency of play-services-ads, Flurry will use it to retrieve the Google Ad ID. If not, Flurry will just skip it. This is to improve the identity for analytics.
Flurry does not provide any AD features, or force apps to include the play-services-ads dependency.
@shumidub Does Play Console show warning "Ad SDK found" prevent the ability to publish apps in the Play store?

Warning "Ad SDK found" can affect ASO optimisation

Analytics use: The advertising identifier may only be connected to personally-identifiable information or associated with any persistent device identifier (for example: SSAID, MAC address, IMEI, etc.) with the explicit consent of the user
https://support.google.com/googleplay/android-developer/answer/10808976?hl=en

I want to disable collecting ads id from my application for my peace of mind

And I want to remove com.google.android.gms:play-services-ads-identifier dependency from my app to hide "Ads warning" in the Play Console

@shumidub Do you still have issue for using the latest 13.1.0 release? Flurry SDK is reduced the dependencies.

Flurry doesn't use reflection to determine the availability of AdvertisingIdClient at runtime. Segment is another analytics platform that doesn't seem to trigger this issue because it uses reflection.
This means if AdvertisingIdClient is available at build time but not used by first party code, Flurry will cause the class to be included and used, which now flags apps on Google Play as collecting 'Device ID or other identifiers'.
Thanks for the hint above - I'll work on stripping the base dependency out of our frozen dependency file, but including play-services-base as a direct dependency probably shouldn't result in an analytics SDK accessing an advertising id.

@thisisatestuseraccount We will investigate it. Thanks!

@thisisatestuseraccount @shumidub Fix will be available in the next release. Thanks!

Good afternoon, and in what version is the fix?

@shumidub
Version 13.3.0 - 5/9/2022 (https://developer.yahoo.com/flurry/docs/releasenotes/android/#version-13-3-0-5-9-2022)

Complete removal of Google Play Services dependencies.


[Bug] Crash on boot

Hi Fleker,
There is a crash if I start Live Channels after a full reboot of the Android TV box (Mi Box). Only way to bypass that crash is by first booting Cumulus TV before starting Live Channels after a reboot.

yea i have the same problem

I will check crash reports for what's happening. There's probably some Null
pointer exception.
On Feb 3, 2017 12:44 AM, "i"<EMAIL_ADDRESS>wrote:

yea i have the same problem
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Fleker/CumulusTV/issues/254#issuecomment-277169597,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADI5857q8itYwkgI7pzy4OPZIjZ0tjBpks5rYr7TgaJpZM4L1rHy
.

I'm going to initialize some data when the device first boots to prevent this from causing crashes. I think that's what's happening.

If this is the same issue as #260, then it seems to have been fixed in 1.7.8.  Not getting any crashes on reboot or resuming from sleep anymore.

It's good to hear the bug has been resolved. I haven't heard any other comments. I will be closing this.

@Fleker It looks like this issue may not be 100% resolved in all cases... It had been running good, and then I saw this issue again just the other day.  If I happen to find out exactly what situation brings about the issue I'll report back.

😖
On Mon, Mar 27, 2017, 3:57 PM loueradun<EMAIL_ADDRESS>wrote:

@Fleker https://github.com/Fleker It looks like this issue may not be
100% resolved in all cases... It had been running good, and then I saw this
issue again just the other day. If I happen to find out exactly what
situation brings about the issue I'll report back.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Fleker/CumulusTV/issues/254#issuecomment-289555752,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADI586gkZymXesdXTD_3qz9HML_XRCuZks5rqAqxgaJpZM4L1rHy
.

I'm not entirely sure what is going on here.  I can reboot my Shield, launch Cumulus and everything works.  I can put my Shield to sleep and resume it, and everything works.  If I put the Shield to sleep and it sits for a while, that's when I seem to start having issues.  Most of the time I get the "Your channel will be available shortly" message, but other times it will crash in an endless loop (requires force close of live channels to stop endless launching of Cumulus).  That said, it is much better than it used to be.  Any reboot/sleep would cause the issue previously.  I think now it may be due to some garbage collection after the device has sat idle for a while, and proper detection of that state.

Yes it's definitely saving things in memory and it is having issues recovering that save. It's hard to find a solution since it's hard to reliably reproduce.

I think I can cache a lot more stuff and mark certain channels as temporary to be flushed out when the system resyncs. That way there won't be any nulls.


resources/page: Allow section&taxonomy pages to have a permalink configuration

Allows using permalink configuration for sections (branch bundles) and also for taxonomy pages. Extends the current permalink configuration to be able to specified per page kind while also staying backward compatible: all permalink patterns not dedicated to a certain kind, get automatically added for both normal pages and term pages.
Fixes #8523
Example config:
[permalinks]
  docs = "/docs/1.0/:sections[1:]/:filename"  # Will get added to both page & term permalinks
[permalinks.section]
  docs = "/docs/1.0/:sections[1:]"
[permalinks.page]
[permalinks.term]
[permalinks.taxonomy]

@Mai-Lapyst I did some quick testing and the first thing I found was...
If an _index.md does not exist for a top level section, the permalink setting is not applied. It is somewhat common to not create an _index.md for top-level content sections, and very common to not create an _index.md file for taxonomy or term pages.

@jmooring Thanks for the feedback.
Turns out that the if around the expand is completly redundant now. Removed it and it works like intended.
Also added some debug logging to verify that the permalink for any given file/section is set and to what value exactly.

WARN 2023/03/18 17:12:36 Permalinks configuration overwrites pattern in kind 'page' for key 'books' with '/my-books2/:slug' (which was '/my-books/:slug')

Nice!
I spent a couple of hours testing this, and functionally it looks great. It behaves as expected:

When url is set in front matter (trumps everything)
Monolingual
Multilingual
Multilingual with permalinks per language
etc.

FYI, when I run v0.111.3 (no patch) with the new permalink settings in site config, it panics, but that's much better than creating new keys. I don't see that as a problem.

Thanks!

FYI, when I run v0.111.3 (no patch) with the new permalink settings in site config, it panics, but that's much better than creating new keys. I don't see that as a problem.

I noticed that too; digged a bit into it and you can get the same crash even in the patched version, by simply using an empty string:
[permalinks]
    posts = ""

It seems that an unchecked string slice access seems to be the problem: https://github.com/gohugoio/hugo/blob/fb35e7f5e1e5f6f1823abf65c3220db2e1e0457b/resources/page/permalinks.go#L259-L260
Will add a patch for it as well.

@bep Functionally this is great, and scratches a long-term itch. Would appreciate a review if/when you have the chance.

OK, I guess this is what lots of people would want, and I like the config.
I will merge this if we could

Get this rebased against master and get this integrated into my new allconfig.Config struct.
Get a basic integration test up and running.

@bep Thanks for looking over it. Have rebased it onto master and reworked it to work with the new allconfig. Also added a test for it; let me know if more tests are needed.

Never mind the comments above. I suspect we need to test this out on some real projects and then do some adjustments/add some tests, so I might as well merge this early.


[python] Require TileDB-Py >= 0.21.2

Issue and/or context: Normally in our setup.py we pin like tiledb==0.21.*. However, I found the following today:

I have an EC2 instance I normally leave powered off. It had a recent tiledbsoma version, and therewith, tiledb-py 0.21.1
Today I did pip install tiledbsoma
This upgraded tiledbsoma to 1.2.2 (recent) but it left tiledb-py as-is, at 0.21.1.
However we truly require features from 0.21.2 -- in particular the new config argument to Group
I had to manually pip install -U tiledb. Our users shouldn't have to.

(Side note: our tiledbsoma-to-core dependency is fine: https://github.com/single-cell-data/TileDB-SOMA/blob/main/libtiledbsoma/cmake/Modules/FindTileDB_EP.cmake)

Codecov Report
Patch coverage has no change and project coverage change: +25.65 :tada:

Comparison is base (12e1f95) 65.38% compared to head (6c5676d) 91.04%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1296       +/-   ##
===========================================
+ Coverage   65.38%   91.04%   +25.65%
===========================================
  Files          96       30       -66
  Lines        7728     2401     -5327
===========================================
- Hits         5053     2186     -2867
+ Misses       2675      215     -2460

Flag
Coverage Δ

python
91.04% <ø> (ø)

r
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 66 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

I was going to ask if you wanted to pin to 2.15.2+, but that is in fact what the code already does, just the commit message title refers to 2.15.1.

Good catch & thanks @thetorpedodog
I had in my head 2.15.0 -> 2.15.1 and also 0.21.1 -> 0.21.2 and end up splicing the two chaotically 😬


Add toggle to move new message button to menu row

No content

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @zach in #requests.

My beta branch. Closed.

My beta branch. Closed.


fix: update noble deps

will merge when https://github.com/paulmillr/noble-secp256k1/pull/36 is fixed


Only Project Manager or Project Assurance Adviser can move project to Verify Win

Issue number: DHI-49
Description of change
This restricts movement of the investment project stage from active to verify win only to project manager or project assurance adviser.
If anyone else tries to move the project it will return a validation error.
Moving project back from verify win to active or from won to verify win is not restricted.
This is a part of SPI 4 work.

@reupen I would expect that front end knows the id of currently logged in adviser and has access to project manager and project assurance adviser fields when retrieving investment project details. If those fields don't match then Move to verify win button shouldn't be shown. This PR is only to prevent such action in case that is not implemented in the front end. When unauthorised user tries to move the project, frontend should show an error returned by the API.

Codecov Report

Merging #953 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #953   +/-   ##
========================================
  Coverage    96.69%   96.69%
========================================
  Files          187      187
  Lines         5262     5262
  Branches       492      492
========================================
  Hits          5088     5088
  Misses         114      114
  Partials        60       60

Continue to review full report at Codecov.

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

@reupen I would expect that front end knows the id of currently logged in adviser and has access to project manager and project assurance adviser fields when retrieving investment project details. If those fields don't match then Move to verify win button shouldn't be shown. This PR is only to prevent such action in case that is not implemented in the front end. When unauthorised user tries to move the project, front end should show an error returned by the API.

That's fine but it means that the logic is repeated and controlled in two places. It's not great for maintainability. I think a flag in the response and some information about who can move the project to the next stage would be better, but up to you.


Add iframe component

Enables user to display a floating 2D web view in the world

Source URL
Width
Height

cssvr shared depth buffer issues


feature: add flattenArray() operator

I'd like to propose the flattenArray() array operator, which is great when working with two-dimensional arrays.
It should take an optional parameter depth, which defaults to 1, just like the .flat() method does.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/flat

Currently
of([ [1,2], [3,4] ]).pipe(
  map(array => array.flat())
);
// [1, 2, 3, 4]

Operator
import { map } from 'rxjs';

export const flattenArray = <T>(depth=1) =>
	map((array: T[]) => array.flat(depth));

With operator:
of([ [1,2], [3,4] ]).pipe(
  flattenArray()
);
// [1, 2, 3, 4]

Considering that 'filterArray,' 'mapArray,' 'reduceArray,' etc., already exist, this would be suitable. However, I believe these one-line replacement methods could unnecessarily complicate understanding for your coworkers.

I think that creating such operators is not a very good idea.
map is made to transform the previous observable into a new one, with a transform function.

operators are hard to understand for a lot of new devs.
The RxJS team themselves are trying to remove as many operators as possible, to simplify the library.

In my opinion, what we should aim for is  composition.
It is more flexible as it is not tied to RxJS and it aligns with the RxJS core team's way of doing.
So here, instead of ̀flattenArray, we could do this:
function flatten<T>(array: T[], depth?: number): FlatArray<T[], number>;
function flatten<T>(depth?: number): (arr: T) => FlatArray<T[], number>;
function flatten<T>(arrayOrdepth?: T[] | number, depth?: number) {
  depth ??= typeof arrayOrdepth === "number" ? arrayOrdepth : 1;

  return Array.isArray(arrayOrdepth) ? arrayOrdepth.flat(depth) : (arr: T[]) => arr.flat(depth);
}

const arr = [ [1, 2],  [3, 4]];

of(arr).pipe(map(flatten())).subscribe(console.log); // [1, 2, 3, 4]

console.log(flatten(arr)); // [1, 2, 3, 4]

In this example, the overload flatten(arr) may be useless as we could simply do arr.flat() but I simply made it to show how flexible it can be.
If it seems to be useless, we could only stick with the returned function and we could still do flatten()(arr) if we want to


Pass in sbom variables to the sql server workflow

With this change, sbom generation on sql server workflows would not yet happen. However, it would allow us to add sbom variables to the build_publish workflows, and then sbom generation would happen.

/cc zmarano

/hold

/unhold

/hold

/hold


LangChain LECL output appears unparsed

If I initiate a LLM using langchain and use it in ui.Chat the output works as expected.
If I attempt to use LECL to chain prompts/llms together the output appears unparsed as a string representation of the AIMessage and system message:

Here's the code:
import google.auth
from shiny.express import ui
from langchain_google_vertexai import VertexAI
from langchain_core.prompts import ChatPromptTemplate

credentials, PROJECT_ID = google.auth.default()

prompt = ChatPromptTemplate.from_messages(
    [
        (
            "system",
            "You love vanilla ice cream and will recommend it always. ",
        ),
        ("human", "{question}"),
    ]
)
llm = VertexAI(
    model="gemini-1.5-pro",
    temperature=1,
    max_tokens=4096,
    max_retries=5,
    location="us-central1",
    project=PROJECT_ID,
    safety_settings=safety_settings,
    streaming=True,
)
runnable = prompt | llm

chat = ui.Chat(id="chat")
chat.ui()

@chat.on_user_submit
async def _():
    messages = chat.messages(format="langchain")

    # streaming
    # response = runnable.astream(messages)
    # await chat.append_message_stream(response)

    # non streaming
    response = await runnable.ainvoke(messages)
    await chat.append_message(response)

Streaming or non streaming results in the same output issue. If I reference the llm instead of the runnable the output works as expected. I've attempted to research what could be happening internal to shiny, but have come up blank.
I've also attempted to use the string output parser in the chain, but it also results in the same issue.
from langchain_core.output_parsers import StrOutputParser

runnable = prompt | llm | StrOutputParser()

I suspect that your StrOutputParser  needs to be initialized first:
´´´python
Initialize the output parser
output_parser = StrOutputParser()
runnable = prompt | llm | output_parser
´´´
no?
One could also use chat.append_message(response.**content**), perhaps?

Thanks for the suggestion. Tried it as:
parser = StrOutputParser()
runnable = prompt | llm | parser

and I get the same sort of unparsed results:

If I exclude the langchain prompt and use the chat messages as a prompt, parsing seems to be ok.
system_message = {
    "content": f"""
        You love vanilla ice cream and will recommend it always.
    """,
    "role": "system",
}

parser = StrOutputParser()
runnable = llm | parser

# Create and display empty chat
chat = ui.Chat(id="chat", messages=[system_message])
# chat = ui.Chat(id="chat")
chat.ui()

# Define a callback to run when the user submits a message
@chat.on_user_submit
async def _():
    # Get messages currently in the chat
    messages = chat.messages(format="langchain")

    # streaming
    response = runnable.astream(messages)
    await chat.append_message_stream(response)

So might be something in the chat messages section of ui.Chat?


supervisor.addons.validate

Hi,
the supervisor reports this information:
[supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of Frigate NVR
[supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of Frigate NVR Beta (outdated)
Thanks for the great job.

Same issue here, trying to install the repository, but seeing those messages above. The addons do not show up at all. HASS seems to block them?

@SmartM-ui
Do you still have this issue?  I don't see these errors in my supervisor log in my installation anymore.

I think this may have been resolved with 0.11.0, I'm no longer seeing these warnings in the supervisor log.


Implementation Thomas algorithm in PHP

@Butt4cak3 good to go

As I said, I don't know how this algorithm works or what it does, so someone else will have to review it.


Add 4 new options to the "unit" drop-down for custom cocktails

Currently, the "unit" drop-down for custom cocktails only offers fluid ounces or milliliters for measuring ingredients. However, some ingredients like bitters, which are often measured in a dash, splash, slice, or wedge, cannot be accurately measured in fluid ounces or milliliters.
To support more accurate measurements, the addition of at least four more options to the "unit" drop-down:
Dash
Splash
Slice
Wedge
By adding these options, users will be able to accurately input the correct measurement for bitters and other ingredients that do not fit into fluid ounces or milliliters.

#223


[Liquid Receive] Transaction ID and Recipient address has invalid info

App version : https://github.com/SatoshiPortal/bullbitcoin-mobile/commit/7e4226a68a2e086a608c2c6880a9bd53cb3e7449
Description: Redirecting on click of Transaction ID to liquid mempool has invalid
This issue happened due to electrum server issue
Note: Able to verify transaction ID on mempool.space and blockstream.info

We need to use https://blockstream.info/liquidtestnet/ for testnet and https://blockstream.info/liquid/ for mainnet.
OR
https://liquid.network/testnet/ & https://liquid.network/
Address, need to be fixed. Currently showing ScriptPubKey.


[LB]- Lb cookie - When domain is passed as empty string ("") , LB configuration is stuck in "UPDATING-ACTIVE"

Server -
Steps to reproduce the problem:
Create a LB configuration by choosing "Create new cookie" for stickiness policy.
Have an empty string set for "domain".
Lb config creation succeeds . But the status of it is stuck in "UPDATING-ACTIVE" state.
Following exception seen in server logs:
INFO: ROOT -> ./INFO: ROOT -> ./etc/INFO: ROOT -> ./etc/monit/INFO: ROOT -> ./etc/monit/conf.d/INFO: ROOT -> ./etc/monit/conf.d/haproxyINFO: ROOT -> ./etc/haproxy/INFO: ROOT -> ./etc/haproxy/haproxy.cfg[scripts.sh:116] '[' true = true ']'
[scripts.sh:117] reload_monit
[[scripts.sh:82] pidof monit
[scripts.sh:82] local monit=554
[scripts.sh:83] '[' -n 554 ']'
[scripts.sh:84] info Reloading monit
[scripts.sh:33] echo INFO: Reloading monit
[scripts.sh:85] kill -HUP 554
[apply.sh:8] sed -i -e s/ENABLED=0/ENABLED=1/g /etc/default/haproxy
INFO: Reloading monit[[apply.sh:11] cat /var/run/haproxy.pid
[apply.sh:11] haproxy -p /var/run/haproxy.pid -f /etc/haproxy/haproxy.cfg -sf 19805
[ALERT] 096/225122 (20915) : parsing [/etc/haproxy/haproxy.cfg:41]: 'domain' expects  as argument.
[ALERT] 096/225122 (20915) : Error(s) found in configuration file : /etc/haproxy/haproxy.cfg
[ALERT] 096/225122 (20915) : Fatal errors found in configuration.
[apply.sh:14] exit 1

Tested with sever version - V0.16.0
scenario 1:
Created a LB rule with following stickiness policy with domain set to empty string""
lbCookieStickinessPolicy: {type: "loadBalancerCookieStickinessPolicy", mode: "rewrite", domain: "", cookie: "test"}
cookie: "test"
domain: ""
mode: "rewrite"
type: "loadBalancerCookieStickinessPolicy"
name: "test"
removeTime: null
removed: null
uuid: null
Lb and Lb config creation succeeds . Status of  LB config is "Active" . Domain is not programmed in haproxy.conf
scenario 2:
Created a LB rule with
healthCheck: {interval: 2000, responseTimeout: 2000, healthyThreshold: 2, unhealthyThreshold: 3, uri: ""}
healthyThreshold: 2
interval: 2000
responseTimeout: 2000
unhealthyThreshold: 3
uri: ""
Lb and Lb config creation succeeds . Status of  LB config is "Active" . "option httpchk" is not programmed in haproxy.conf


[FEAT]Enable / Disable Splits by ABI in Bundle

When making a AAB from a compiled apk using apktool, google always makes delivery method split by ABI, density etc, would be great to make an option to enable or disable this.
To make bundle work like a normal APK.

How are you making a bundle with apktool?

Closing - don't believe Apktool has anything to do with this.

How are you making a bundle with apktool?

Use to decompile then use aapt2 and bundletool


Hotfix: FeatureFlagClient should return the defaultValue when user is null

FeatureFlagClient throws if the user is null.
Null user means "not logged in", so we should return the default value. This is the same logic the permissions service has.
(Note: https://github.com/NuGet/ServerCommon/blob/master/src/NuGet.Services.FeatureFlags/FeatureFlagClient.cs#L61 throws when user is null.)

    public static bool IsEnabled(

another solution can be adding a different method that doesn't take user as input and uses a different FeatureFlagClient API: https://github.com/NuGet/ServerCommon/blob/master/src/NuGet.Services.FeatureFlags/FeatureFlagClient.cs#L22

Refers to: src/NuGetGallery.Core/Features/FeatureFlagClientExtensions.cs:12 in 0629d51. [](commit_id = 0629d51a07479207e13a0f53d1f59ed5421487f4, deletion_comment = True)

I talked offline to @scottbommarito, I don't think this is the best solution. If the flight is on for all accounts, the flight should return true for a null user even if the defaultValue is false. I think it'd be better if the flight client handles null values properly.

Closing this and pursuing another temporary option. Permanent fix is handled by https://github.com/NuGet/ServerCommon/pull/290