IPHONE CAN'T SERARCH THE BRIDGE

THE HASS.IO VERSION IS 49.1 and the homebridge is successsfully runing. the raspberry and iphone is on the same network. but both my iphone 6s(IOS 11) and iphone 5(IOS 10) can't find the bridge.
starting version 3.2.1
Linking the homebridge config directory
Launching DBUS daemon…
Launching avahi daemon…
Launching homebridge…
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister
[7/30/2017, 10:11:52 AM] Loaded plugin: homebridge-homeassistant
[7/30/2017, 10:11:52 AM] Registering platform 'homebridge-homeassistant.HomeAssistant'
[7/30/2017, 10:11:52 AM] ---
[7/30/2017, 10:11:52 AM] Loaded config.json with 0 accessories and 1 platforms.
[7/30/2017, 10:11:52 AM] ---
[7/30/2017, 10:11:53 AM] Loading 1 platforms...
[7/30/2017, 10:11:53 AM] [HomeAssistant] Initializing HomeAssistant platform...
[7/30/2017, 10:11:53 AM] [HomeAssistant] Fetching HomeAssistant devices.
[7/30/2017, 10:11:53 AM] Loading 0 accessories...
[7/30/2017, 10:11:53 AM] [HomeAssistant] Received event: ping
[7/30/2017, 10:11:53 AM] [HomeAssistant] Initializing platform accessory 'yeelight_white_34ce00811368'...
[7/30/2017, 10:11:53 AM] [HomeAssistant] Initializing platform accessory 'SRS-X88 F1842D'...
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘

[7/30/2017, 10:11:53 AM] Homebridge is running on port 51826.
[7/30/2017, 10:12:30 AM] [HomeAssistant] Received event: {"event_type": "state_changed", "data": {"entity_id": "sun.sun", "old_state": {"entity_id": "sun.sun", "state": "above_horizon", "attributes": {"next_dawn": "2017-07-30T21:52:33+00:00", "next_dusk": "2017-07-30T12:07:12+00:00", "next_midnight": "2017-07-30T16:59:33+00:00", "next_noon": "2017-07-30T04:59:35+00:00", "next_rising": "2017-07-30T22:17:33+00:00", "next_setting": "2017-07-30T11:42:09+00:00", "elevation": 50.54, "azimuth": 92.89, "friendly_name": "Sun"}, "last_changed": "2017-07-30T01:03:44.705369+00:00", "last_updated": "2017-07-30T02:11:30.073834+00:00"}, "new_state": {"entity_id": "sun.sun", "state": "above_horizon", "attributes": {"next_dawn": "2017-07-30T21:52:33+00:00", "next_dusk": "2017-07-30T12:07:12+00:00", "next_midnight": "2017-07-30T16:59:33+00:00", "next_noon": "2017-07-30T04:59:35+00:00", "next_rising": "2017-07-30T22:17:33+00:00", "next_setting": "2017-07-30T11:42:09+00:00", "elevation": 50.76, "azimuth": 93.02, "friendly_name": "Sun"}, "last_changed": "2017-07-30T01:03:44.705369+00:00", "last_updated": "2017-07-30T02:12:30.073664+00:00"}}, "origin": "LOCAL", "time_fired": "2017-07-30T02:12:30.073806+00:00"}
[7/30/2017, 10:13:20 AM] [HomeAssistant] Received event: ping
[7/30/2017, 10:13:30 AM] [HomeAssistant] Received event: {"event_type": "state_changed", "data": {"entity_id": "sun.sun", "old_state": {"entity_id": "sun.sun", "state": "above_horizon", "attributes": {"next_dawn": "2017-07-30T21:52:33+00:00", "next_dusk": "2017-07-30T12:07:12+00:00", "next_midnight": "2017-07-30T16:59:33+00:00", "next_noon": "2017-07-30T04:59:35+00:00", "next_rising": "2017-07-30T22:17:33+00:00", "next_setting": "2017-07-30T11:42:09+00:00", "elevation": 50.76, "azimuth": 93.02, "friendly_name": "Sun"}, "last_changed": "2017-07-30T01:03:44.705369+00:00", "last_updated": "2017-07-30T02:12:30.073664+00:00"}, "new_state": {"entity_id": "sun.sun", "state": "above_horizon", "attributes": {"next_dawn": "2017-07-30T21:52:33+00:00", "next_dusk": "2017-07-30T12:07:12+00:00", "next_midnight": "2017-07-30T16:59:33+00:00", "next_noon": "2017-07-30T04:59:35+00:00", "next_rising": "2017-07-30T22:17:33+00:00", "next_setting": "2017-07-30T11:42:09+00:00", "elevation": 50.98, "azimuth": 93.15, "friendly_name": "Sun"}, "last_changed": "2017-07-30T01:03:44.705369+00:00", "last_updated": "2017-07-30T02:13:30.075642+00:00"}}, "origin": "LOCAL", "time_fired": "2017-07-30T02:13:30.075783+00:00"}
[7/30/2017, 10:14:20 AM] [HomeAssistant] Received event: ping
[7/30/2017, 10:14:30 AM] [HomeAssistant] Received event: {"event_type": "state_changed", "d

It looks like main reason is that avahi-daemon is unable to create connection:
Launching avahi daemon…
Jul 30 14:14:48 addon_75f7ddb0_homebridge syslog.info syslogd started: BusyBox v1.25.1
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Found user 'avahi' (UID 86) and group 'avahi' (GID 86).
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Successfully dropped root privileges.
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: avahi-daemon 0.6.32 starting up.
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.warn avahi-daemon[30]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Successfully called chroot().
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Successfully dropped remaining capabilities.
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Loading service file /services/sftp-ssh.service.
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Loading service file /services/ssh.service.
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.warn avahi-daemon[30]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Joining mDNS multicast group on interface docker0.IPv4 with address <IP_ADDRESS>.
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: New relevant interface docker0.IPv4 for mDNS.
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Joining mDNS multicast group on interface wlan0.IPv4 with address <IP_ADDRESS>.
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: New relevant interface wlan0.IPv4 for mDNS.
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Network interface enumeration completed.
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Registering new address record for <IP_ADDRESS> on docker0.IPv4.
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Registering new address record for <IP_ADDRESS> on wlan0.IPv4.
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Withdrawing address record for <IP_ADDRESS> on wlan0.
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.warn avahi-daemon[30]: Host name conflict, retrying with addon75f7ddb0homebridge-2
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Registering new address record for <IP_ADDRESS> on docker0.IPv4.
Jul 30 14:14:49 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Registering new address record for <IP_ADDRESS> on wlan0.IPv4.
Jul 30 14:14:50 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Withdrawing address record for <IP_ADDRESS> on wlan0.
Jul 30 14:14:50 addon_75f7ddb0_homebridge daemon.warn avahi-daemon[30]: Host name conflict, retrying with addon75f7ddb0homebridge-3
Jul 30 14:14:50 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Registering new address record for <IP_ADDRESS> on docker0.IPv4.
Jul 30 14:14:50 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Registering new address record for <IP_ADDRESS> on wlan0.IPv4.
Jul 30 14:14:51 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Withdrawing address record for <IP_ADDRESS> on wlan0.
Jul 30 14:14:51 addon_75f7ddb0_homebridge daemon.warn avahi-daemon[30]: Host name conflict, retrying with addon75f7ddb0homebridge-4
Jul 30 14:14:51 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Registering new address record for <IP_ADDRESS> on docker0.IPv4.
Jul 30 14:14:51 addon_75f7ddb0_homebridge daemon.info avahi-daemon[30]: Registering new address record for <IP_ADDRESS> on wlan0.IPv4.

And it continues like that for a long time. I'm currently trying to figure out what is the reason, but it's slow process.

@olivierguerriat most probably related to https://github.com/lathiat/avahi/issues/117

I have this problem in hassbian with home assistant 050.

ME too！Sometimes when I restart homebridge in hassio , suddenly I can find it , but I had restarted.

ME too！Sometimes when I restart homebridge in hassio , suddenly I can find it , but I had restarted.

ME too！

@olivierguerriat I think the issue is related to the avahi daemon binding to ipv6 instead of ipv4
You might want to change the avahi config to not bind to ipv6...
maybe it will work if you put this in the run.sh:
sed -i "/^use-ipv6=/s/=.*/=no/" /etc/avahi/avahi-daemon.conf

@marcelveldt How would I access the run.sh of homebridge? Enable the developer ssh and find it that way?

Thanks for your suggestions, I tried them all but still couldn't make it work. However, Franck Nijhof did!
Please uninstall this add-on and use his add-on instead. Your configuration should be transferred transparently.


add api endpoint for sub region data

Uses mock data currently, but data looks deficient of some data though, like the micronutrient the data concerns

Pushed changes to:

add api endpoint for dietary sources
Also change the way the api.service.ts is structured to minimize eslint disabling

Build failed due to budgets, probably because of the mocked up data files in the assets.
There's no knock on effects with deployment if I up this to 6mb until the API is up and running and we can clean up assests is there @Fuhji ?

add api endpoint for household histogram data

Build failed due to budgets, probably because of the mocked up data files in the assets.
There's no knock on effects with deployment if I up this to 6mb until the API is up and running and we can clean up assests is there @Fuhji ?

No immediate problem if we are serving mock data alongside the project

More changes added:

replace mdns options mock api data with mock data from local file
increase maximum build size budget to accommodate mock data files

If the PR is still being worked on you can mark it as Draft (equivalent of GitLab WIP), under the reviewers section

Ready for merge now @Fuhji :

add api endpoint for sub region data
add api endpoint for dietary sources
Also change the way the api.service.ts is structured to minimize eslint disabling
add api endpoint for household histogram data
replace mdns options mock api data with mock data from local file
increase maximum build size budget to accommodate mock data files


Implement configurable text for table with no data

Adds a UX enhancement that shows text inside the table when there is no data to display.
This text is shown either if the table is initialized without any data or if the table is filterable and there are no matches with the current filter input text.
The content of the message is configurable with the noDataText prop and provides a default message in defaultProps.

Oops, hang on, going to push up another change with stuff for the README...

Updated.

I hate to say it, but I'm actually not a fan of Reactable doing this for you. This seems much more like the job of whatever happens to be calling Reactable.

@glittershark So how does the calling code know if the reactable filter isn't capturing any records?

hmm, didn't think of that.

Also note that this is a feature of other JS table libraries like DataTables https://datatables.net/examples/plug-ins/range_filtering.html

My seething hatred of DataTables in particular is what originally drove me to write Reactable :stuck_out_tongue:

Same here, that's what what brought us to this library :)

But yeah, without this, we basically can't use the built-in filtering.

Right, so in light of the filtering thing I'm conceptually cool with this

:+1: besides the handling of null and the couple of test grammar nits (the latter feel free to leave alone if you like)

No problem, updating those now.

Thanks for the feedback, updated.

Which, I think I'm just going to implement it that way (without a defaultProp), it makes more sense.

Sweet! thanks for bearing with my nitpicks.

@glittershark I appreciate it! Thank for merging.


Backport 8c952371 into v1.8.x and release 1.8.2

New versions of netCDF4 have removed date2num from the netcdftime module. A fix was put onto the Iris master branch, but this is not in a released version yet. I suggest we backport 8c9523715492db7af5bccd31858df47daa611874 into v1.8.x and do a quick release of 1.8.2 to allow iris to be compatible with newer netCDF4 versions.
FYI @shoyer

Seems reasonable provided we can keep the scope of v1.8.2 down to a minimum.

I was imagining the scope of the release being just this commit + a what's new entry describing which bug it fixes.

There never was a v1.8.2 release. This ticket is now obsolete with v1.9.2 released and v1.10 incoming.


Bug: I cant upload mp4 files

Describe the bug
when I try to upload a mp4 file, I get invalid file error . I try to check :

codeigniter config mime file type
try fix problem with change validation parameters
change php.ini settings
etc
I can upload any files like photos , office and pdf file format with same logic and different validation. but I think it's not possible with mp4 files.

function code :
{
        //uploaded file address = https://coverr.co/videos/happy-young-girl-texting-near-the-sea-KwV5cuJ0lr
	$photo = $this->request->getFile($input_name);
	dd($photo);
	//result:
	//protected error -> integer 1
	//protected hasMoved -> boolean false
	//protected name -> string (47) "coverr--06-20-young-girl-at-the-bay-11-3419.mp4"
	//protected originalMimeType -> string (0) ""
	//protected originalName -> string (47) "coverr--06-20-young-girl-at-the-bay-11-3419.mp4"
	//protected path -> string (0) ""
	//protected size -> integer 0

	$validation = $this->validate([
	$input_name => [
				"uploaded[$input_name]",
				"max_size[$input_name,10096]",
				"mime_in[$input_name,video/mp4,video/mp,video/webm'']
		]);
		if(!$validation)
		{
			dd($this->validator->getError($input_name));
		}
	// result:
	// myfile is not a valid uploaded file.

}

CodeIgniter 4 version
4.0.4
Affected module(s)
request , file
Context

OS: [e.g. windows 10]
Web server  wamp 2.4.33
PHP version [7.2.4]

You have an error code of 1, which is UPLOAD_ERR_INI_SIZE. You need to adjust the upload_max_filesize directive in your php.ini


FE Team Report

Team Project Board: https://github.com/thenewboston-developers/Website/projects/4
Salaries:
Justin Kim - 80000
James - 40000
Sanjeev - 33600
Vyz - 64000
Rajput - 24000
Total Salary Amt: 241600
Bounties:
Tomijaga - Wrong Documentation displayed for clean and craw post request - 500
IvanDanilov - Add TNB Blog - 20000 (note, this one is not being merged in, but Ivan will still get paid)
Total Bount Amt: 20510 (10 extra for the transaction fees)
Total Amount Needed: 262,100
FE Wallet: 1345375a4d25452ab0e702df2467b1fd575bcaae7d7fce49423dfce4811e1580

Team members have been paid directly and just sent over the bounty funds.

the two bounties have been sent


Support LinearCombination as an observable

Describe the feature you'd like
In v0.36.0 of PennyLane, the new LinearCombination is used in favour of the legacy Hamiltonian, which should also be supported as an observable.
Additional context
There are two classes now to represent a Hamiltonian: qml.ops.Hamiltonian, and qml.ops.LinearCombination. The latter is now used by default in favour of the former. With new opmath enabled, qml.Hamiltonian will refer to LinearCombination, and with new opmath disabled, qml.Hamiltonian will refer to the old Hamiltonian class.
Solution

In braket_device.py, line 169 should be updated to return base_observables.union({"Hamiltonian", "LinearCombination"})
Update all isinstance(..., Hamiltonian) checks to isinstance(..., (qml.ops.Hamiltonian, qml.ops.LinearCombination)), such as line 230 of braket_device.py, line 561 and 691 of translation.py
Update line 584-585 of translation.py to:

@_translate_observable.register(qml.ops.Hamiltonian)
@_translate_observable.register(qml.ops.LinearCombination)
def _(H: Union[qml.ops.Hamiltonian, qml.ops.LinearCombination]):
    ...

Thanks for pointing this out @astralcai, we will take a look into this.


Error: Get http://unix.socket/1.0: EOF

Required information

Distribution:
Distribution version:
The output of "lxc info" or if that fails:

Kernel version:
LXC version:
LXD version:3.0.3
Storage backend in use:

Issue description
Hello,
when i change my internet network, my lxd stop working
Every time i use lsc or lxd commands, i have the same error :
Error: Get http://unix.socket/1.0: EOF
when i checked my lxd.log i have:
"Cannot listen on https socket, skipping..." err="listen tcp <IP_ADDRESS>:8443: bind: cannot assign requested address"
"Failed connecting to global database: failed to create dqlite connection: no available dqlite leader server found"
with :journalctl -u lxd.service
I have
lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored."
even if my config is
BOOT_IMAGE=/vmlinuz-4.18.0-20-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash swapaccount=1 vt.handoff=1
and i have also
lvl=eror msg="Dqlite: aborting (fd=21 state=header msg=(null))"
lvl=warn msg="Raft: Heartbeat timeout from "" reached, starting election"
someone would know where the issue could be?

This suggests that your system currently doesn't have the IP address that you configured for your LXD daemon.
LXD on your system is configured to listen on <IP_ADDRESS> and the error suggests that your system currently doesn't have it. Configure that address and try starting LXD again.

If your system is on dynamic addresses, a better value for core.https_address is :8443 so that it listens on whatever address is available and won't fail if your system doesn't have the expected address.

Hello,
thanks for the answer
i try : lxc config set core.https_address '[::]:8443'
but i don"t have any access to lxd or lxc commands
do you know an an other way to change the address
ps: it's my first time wuth lxd :)

You'll need to add that IP to your system so that LXD will start again:

ip addr add <IP_ADDRESS>/32 dev lo
systemctl restart lxd
lxc config set core.https_address :8443
ip addr del <IP_ADDRESS>/32 dev lo

T'y for help

If your system is on dynamic addresses, a better value for core.https_address is :8443 so that it listens on whatever address is available and won't fail if your system doesn't have the expected address.

Hi, I believe it's the same issue Im having here:
The lxd network config is this:
$ lxc network show lxdbr0
config:
  ipv4.address: <IP_ADDRESS>/24
  ipv4.dhcp.ranges: <IP_ADDRESS>-<IP_ADDRESS>
  ipv4.nat: "false"
  ipv6.address: none

Core http address is set to the same IP lxd should care about.
$ lxc config show
config:
  core.https_address: <IP_ADDRESS>:8443

But after reboot we have this issue
Mar 19 04:11:57 server lxd[903]: t=2020-03-19T04:11:57+0100 lvl=eror msg="Cannot listen on https socket, skipping..." err="listen tcp <IP_ADDRESS>:8443: bind: cannot assign requested address"
Is there a way to maybe wait until lxdbr0 is up and then bind to its address? Maybe via systemd somehow?

there's no waiting possible as LXD itself creates that bridge so if LXD can't start, the IP will never show up

there's no waiting possible as LXD itself creates that bridge so if LXD can't start, the IP will never show up

That is the thing, LXD starts normally, IP is up, but LXD cannot assign "core.https_address" to this address <IP_ADDRESS>. And to make it work I have to first "lxc config unset core.https_address" and then set it again.
Should I create a separate issue though?


feat(migrations): support for running database migrations manually

Changes proposed in this pull request

Introduce new environmental variable ENABLE_MANUAL_MIGRATIONS through which end user can decide if he/she wants to run migrations automatically (default flow as it always was) or manually (pnpm run knex -- migrate:latest --env production
In knexfile.js use env variable from the ENV for setting connection string for production environment
In dockerfile, copy knexfile.js from source to container

With this in place, if Rafiki is installed on kubernetes cluster, it is possible to leverage initContainers for database migrations. This should be backward compatible or in other words, should not change how Rafiki deals with database migrations when default values for this environment variable is set.
Context

fixes #2621
After this PR is merged, we will need to implement this ENV into helm charts. After this ENV is added to helm charts, we need to set value to true, and we will also need to specify initContainer that will run this migrations "manually" or in other words, automatically in initContainer.
Checklist

[x] Related issues linked using fixes #number
[ ] Tests added/updated
[x] Documentation added
[x] Make sure that all checks pass
[ ] Bruno collection updated

This PR has been approved, however, I am not authorized to merge this pull request.


[fp] add fp functions & curry & compose & state

Add Function1 ... Function5
Add Fn0 ... Fn5
Add Compose1 ... Compose5
Add State & FuncState

Codecov Report

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

@@            Coverage Diff            @@
##             master       #2   +/-   ##
=========================================
  Coverage          ?   71.58%
=========================================
  Files             ?       16
  Lines             ?      542
  Branches          ?        0
=========================================
  Hits              ?      388
  Misses            ?      150
  Partials          ?        4

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 7e26999...a8aceca. Read the comment docs.


fix: support throw render error when ssr in production

Vue version
3.3.4
Link to minimal reproduction
https://play.vuejs.org/#eNp9U8tu3DAM/BVWF2sBx0aRW7Ab9IEAbYE+0ATtRRfD5tpKbcml5N0tDP97KQn7SBvkZnGG5HBIz+LtOBa7CcWNWLua9OjBoZ/GW2X0MFryMAPhFhbYkh0gY2qmjDK1Nc7D4FrYBFxmH7DvLfy01DevspUy6zKV40L88DiMfeWRXwDr7vXtPMfkZVmX/IpRbcbJw+5qsA32GyUYV4KhdXnKFrnwjltvdVs8OmtY9RxylajtMOoe6evoNUtT4gYiErCKle0/xZinCfNjvO6w/vVM/NEdQkyJb4QOaYdKnDBfUYs+wXf3X/DA3yeQlU89s18Av6Oz/RQ0Jtq7yTQs+4IX1X6M3mvTPri7g0fjjkMFoYG5RL4SvI/3L4x+lntdXMc8ZRZ2UTs3IVvIBqZNztDl0OBWm1jPGjQ+h5qQbecT4f2HPf+eNKGMR8ArPl5BuBDTID3Ye0+s+Sn5DbPLaCNdJR7SZfbnP6eGnPaPBBknSTIauToOFjJtj0VvW9nYehqYyiWPtqQ2ZzrxRZOBTmaN3mU5pGPN4ceE8VaTLReaKp54c55eXmiMrKfzSqavCt+hkbLzQ7+CzW1qfakzIqFNUVe+7qREIkv/c2NYZs4RxE/Wm5iBVJbQWHB2QN8Fp/fadxzZm5aqBsFbqDkv/EFpILH8BWncUH8=
Steps to reproduce
I want to catch some errors during vue server-side rendering in node.js instead of defining error handlers inside vue such as app.config.errorHandler. When I use the following code to catch an error, in the development environment vue will throw the error, but in the production environment vue swallows the error, which makes it impossible to catch the error with a catch
const { h, defineComponent, createApp } = require('vue')

const { renderToString } = require('@vue/server-renderer')

const MyComponent = defineComponent({
  created() {
    console.log(document)
  },
  render() {
    return h('div', 'Hello, Vue!')
  }
})

const app = createApp(MyComponent)

renderToString(app).then((html) => {
  console.log(html)
}).catch((error) => {
  console.error('ssr error', error)
  // do something with downgrade to csr mode
})

How to test
$ node issue.js // error can be caught
$ NODE_ENV=production node issue.js // error cannot be caught

The reason for the error is that vue handles error objects differently in development and production environments.
// vue/runtime-core.cjs.js
    if (appErrorHandler) {
      callWithErrorHandling(
        appErrorHandler,
        null,
        10,
        [err, exposedInstance, errorInfo]
      );
      return;
    }
  }
  logError(err, type, contextVNode, throwInDev);
}
function logError(err, type, contextVNode, throwInDev = true) {
  {
    const info = ErrorTypeStrings[type];
    if (contextVNode) {
      pushWarningContext(contextVNode);
    }
    warn(`Unhandled error${info ? ` during execution of ${info}` : ``}`);
    if (contextVNode) {
      popWarningContext();
    }
    if (throwInDev) {
      throw err;
    } else {
      console.error(err);
    }
  }
}

In production environments vue will not throw error
// vue/runtime-core.cjs.prod.js

    const appErrorHandler = instance.appContext.config.errorHandler;
    if (appErrorHandler) {
      callWithErrorHandling(
        appErrorHandler,
        null,
        10,
        [err, exposedInstance, errorInfo]
      );
      return;
    }
  }
  logError(err, type, contextVNode, throwInDev);
}
function logError(err, type, contextVNode, throwInDev = true) {
  {
    console.error(err);
  }
}

What is expected?
We can use try catch some error during vue rendering process
What is actually happening?
try catch cannot catch some error during vue rendering process
System Info
No response
Any additional comments?
For the reasons mentioned above，Perhaps a configuration could be added here to decide whether or not to throw an error in the production environment

similar to #7876

I'm not even using SSR, but I just ran into this same issue when trying to add in a global unhandledrejection listener to show errors in my app. Bizarre behavior to have this functionality change between dev and prod!

Just to chime in: I was bitten by this as well, trying to handle unhandledrejection globally. Everything worked right up until I did a production build.

I have the same issue about unhandledrejection. It has different behavior between dev and prod. Error from vue will not be t trigger unhandledrejection in prod. Any solution?

see https://github.com/vuejs/core/issues/7876#issuecomment-2232196747


Incorrect handling of empty number input

Describe the bug
When saving an entry with a number field, with the Number widget, if the field is empty, the value saved on the frontmatter will be myNumberField: .nan - as previously reported in https://github.com/netlify/netlify-cms/issues/1450
To Reproduce

Add an entry on a collection with a Number field.
Write a value on the aforementioned field (so the field is tracked in the state of the entry).
Publish your entry and witness the incorrect handling of the '' value of the number input.

Expected behavior
The value for the field should persist as for other fields, i.e., myNumberField: ''.
Applicable Versions:

Netlify CMS version: 2.3.3
Git provider: ALL

Additional context
The problem lies in: https://github.com/netlify/netlify-cms/blob/master/packages/netlify-cms-widget-number/src/NumberControl.js#L24-L34
If the value is '', then both parseInt('', 10) and parseFloat('') will return NaN which ends up causing this behaviour. The solution is to simply filter out for the empty value and call onChange with it before trying to parse it as a number.

I found this while working on https://github.com/netlify/netlify-cms/issues/2017. I'll be submitting a PR to fix this bug asap.


Nullable embedded documents not initialized

Bug Report

Q
A

BC Break
no

Version
2.2.x (498478488c7d8539239e697b2260b4944b2d7b7a)

Summary

When using <embed-one ... nullable="true"/>, hydration fails due to a missing nullable check in the generated hydrator.
Current behavior

When using <embed-one ... nullable="true"/> in combination with typed, uninitialized properties, then these properties are not correctly initialized to null. This works for regular fields due to the following generated condition in the hydrator:
if (isset($data['theField']) || (! empty($this->class->fieldMappings['theField']['nullable']) && array_key_exists('theField', $data))) {

For embedded fields, however, the following condition is generated:
if (isset($data['theField'])) {

As you can see, the check for the nullable property is missing, hence the field is not initialized.
How to reproduce

class Container {
    private int $id;
    private ?Embedded $embedded;

    public function __construct(int $id, ?Embedded $embedded)
    {
        $this->id = $id;
        $this->embedded = $embedded;
    }

    public function getId(): int
    {
        return $this->id;
    }

    public function getEmbedded(): ?Embedded
    {
        return $this->embedded;
    }
}

class Embedded {
    public int $value;

    public function __construct(int $value)
    {
        $this->value = $value;
    }

    public function getValue(): int
    {
        return $this->value;
    }
}

<?xml version="1.0"?>
<doctrine-mongo-mapping xmlns="http://doctrine-project.org/schemas/odm/doctrine-mongo-mapping"
                        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                        xsi:schemaLocation="http://doctrine-project.org/schemas/odm/doctrine-mongo-mapping
                    https://doctrine-project.org/schemas/odm/doctrine-mongo-mapping.xsd">
    <document name="Container">
        <id type="integer" strategy="NONE"/>
        <embed-one field="embedded" target-document="Embedded" nullable="true"/>
    </document>
    <embedded-document name="Embedded">
        <field name="value" type="integer"/>
    </embedded-document>
</doctrine-mongo-mapping>

$container = new Container(10, null);

$documentManager->persist($container);
$documentManager->flush();
$documentManager->clear();

$container = $documentManager->find(Container::class, 10);

var_dump($container->getEmbedded());

// => Fatal error: Typed property Container::$embedded must not be accessed before initialization

Expected behavior

var_dump($container->getEmbedded());

// => null

Thanks for the report. I've taken a crack at fixing this in #2302. As evidenced in the tests, you can set a default value on the property as a workaround until we have a release:
class Container {
    private int $id;
    private ?Embedded $embedded = null;

    // ...
}

@alcaeus Wow, that's quick! Thanks! :)

Wow, that's quick!

I have my moments 😊


architectural drivers

https://docs.google.com/document/d/1S6HdbpFXYHIL7XCQ80UzRSUGGDz6Fijy6DqO_CfRCWc/edit?usp=sharing


Support thrust reversal for vtol back transition

This enables active braking during back transition by reversing thrust.
It relies on ESC's that have a channel to control motor direction like the Hobbywing Platinum pro series.
Currently it has only been bench tested, flight test will be performed soon.
/cc @AndreasAntener @tumbili

Awesome! Very interested to see a side-by-side comparison.
Thrust reversal (airbrakes) is common in real planes and this would fit into the FW controller nicely alongside flaps. Then VTOL would simply set apply_airbrakes at the appropriate time (https://github.com/PX4/Firmware/blob/master/msg/vehicle_attitude_setpoint.msg#L21) during back transition. Planes could then consider using it for braking during landing at the appropriate time.
It's the same solution, just moved to a different part of the codebase to enable wider usage.

@dagar The one corner case I see is that I could see us wanting to brake using this completely even with multicopter engaged. That would be much smoother.

@sanderux Could you add the same into the fixed wing controller and fix the circle CI error?

@dagar Implementing this for FW is a good idea, but that cannot be implemented the way i have done now. Currently it applies a fixed reversed throttle for the duration of the back transition without any control on airspeed or velocity. Doing so to slow down a fixed wing will surely lead to problems.
After a chat with lorenz the current proposal is to leave it in the vtol attitude controller for now and replace it with a velocity controlled method in the FW controller as soon as we find the time to implement that properly.
Do you agree?

Yes a velocity controller would be preferred, but what I was proposing was simply moving the same implementation into fw_att_control, and enabling with a bool in the attitude setpoint (similar to flaps). During back transition vtol_att would set apply_airbrakes = true, otherwise it would be false. This is actually of limited utility initially, however it accomplishes a few things.

Gives a base for expanding the usage with pure FW.
Avoids parameter churn later on.
Doesn't further entrench the current vtol architecture. This is a much larger discussion, but it's not actually necessary to hijack each controllers published actuator controls, make minor changes, and republish. Everything we need to do in vtol can be accomplished with FW and MC controllers maintaining ownership of their respective actuator controls and appropriate mixing.

Yet another idea is to find a way to do this at the mixer level. The idea of an actuator output with a direction controlled by another output seems even more general than vtol or fw airbrakes. Then you could simply publish a negative thrust during back transition. We'd have to find a way to make a negative thrust correspond to a fixed 20% output on the additional pwm + positive pwm output, but overall it would be much cleaner.
All that is to say, I'm not opposed to this implementation right now if you're willing to tolerate some churn (and likely retesting) later on.

I agree with @dagar that the best place to put this would be in the mixer itself and then simply be able to publish a negative value.

Wouldnt that then require a different mixer for every esc?

Yet another idea is to find a way to do this at the mixer level. The idea of an actuator output with a direction controlled by another output seems even more general than vtol or fw airbrakes. Then you could simply publish a negative thrust during back transition. We'd have to find a way to make a negative thrust correspond to a fixed 20% output on the additional pwm + positive pwm output, but overall it would be much cleaner.

Is the current mixer capable of doing this? The esc requires a constant PWM between 1000 and 1200 on the reversal channel for normal rotation and a PWM > 1200 for reverse rotation. If the signal goes below 1000 the esc goes into failsafe mode

It would require a new mixer class that steals 2 outputs and sets the second output according to the sign of the control input received. That way the system can just work with negative thrust to activate it and is independent of the ESC. In that case, any breaking logic implemented works as well with ESCs that support reversal below the midpoint (and have a simple mixer).

Tested in fairly heavy wind, works: http://logs.px4.io/plot_app?log=f4ab18cc-a717-4a34-a8d5-13b5b24ef86a
It does need a fair amount of tuning as the prop in reverse seems to stall if the trust is too high.
There are 2 things that would be good to change in relation to this;

Base acceptance radius on configured deceleration deceleration speed
Make the current back transition time a max time and consider back transition complete when MPC_XY_MAX is achieved

@dagar @AndreasAntener I added the 2 improvements i suggested based on my flight tests.
I will perform another flight test soon

Do you need both mixers? The reason I ask is that this precludes usage of the usual camera triggers, and a VTOL that doesn't have payload is not particularly interesting.

For this solution you do. How many do you need for cam? There is one left

I use 3 and 4 on the deltaquad for pusher and reserse so that should work

@dagar so how do you propose we deal with this?

Flight tested, this gave fantastic back transitions in wind conditions that would normally result in very eratic behavior.
tail wind: https://review.px4.io/plot_app?log=3b1cfd23-f41e-4b57-b13b-6c0a9ed6bfdf
nose wind (vt_b_dec_mss was a little too high): https://review.px4.io/plot_app?log=b7c4f3ec-20cd-46e1-a719-b31917e5f20e
@dagar @LorenzMeier Please review, i consider this ready to merge

@LorenzMeier i dont know why semaphoreci keeps failing. Can you review and merge?

Need to add:

check if velocity is valid
change description of VT_B_DEC_MSS

@dagar points addressed. Please review

I'm still concerned that with the current implementation the parameter naming implies more functionality than actually exists outside of a very specific setup.
VT_B_REV_THR: reverse thottle output during back transition
This is simply the pusher throttle value during back transition right? There's nothing special about it that makes it a reverse throttle. A regular user (without the special ESC) is going to see this and enter a number expecting it to reverse somehow. If you describe (and name) what it actually does that removes some of the ambiguity.
What about "vtol standard pusher throttle during back transition" with an allowed range [-1, 1]? I think it would then be obvious to most it should be 0. Users with setups that support commanding negative thrust could also use it.
VT_B_REV_OUT: Output on reverse channel during back transition
This is the INDEX_AIRBRAKES value during back transition right? Why don't we just say what it actually is with a note that it isn't going to do anything unless you have AIRBRAKES in your mixer.

@dagar addressed your comments, please review

@dagar I address a couple more things. can you review again?

Flight tested new changes, works very well: https://logs.px4.io/plot_app?log=bd8740e0-f43b-418b-8f10-f27f50e9f989


Add spanish language to constants

Hi, I had to start a fresh repo here: https://github.com/fsondej/autocorrect
and this one is deprecated.
Please make this pull request again to the new repo. Sorry for the trouble.
As for the change. If you have created es.tar.gz, please put it in optional_languages directory and add that.
Also, add some short unit test, analogous to the tests for other languages in unit_tests/test.py.
Last thing, in this regex: r'[A-Za-záéíóúüñ]+', add uppercase special letters.
Then I will merge.
Thank for contributing ^^

I noticed you started working on this new repo. I'm sorry, but I had to start a new one again, because I had some problems with LFS. The final one is again at https://github.com/fsondej/autocorrect and this time it's final ;)
Sorry for that.

ack


Fix bug in populate, sending wrong params

Summary
Fix bug using empty params in populate hook, causing for example a remove after hook on populated item to be ignored even if called from non-internal provider.

PR looks good. Thanks @danieledler! ❤  Nice catch 😄

released in v2.0.1


in the comment box, use a fixed-width font

requirements

a plus would be a dark theme

a plus plus would be a configurable theme
specs
add .comment-form-textarea: { font-family: monospace; }

@francescogior @gabro is this issue relevant? are people really interested in this? If no quorum/decision on feature requests is made after a few months I thing issues should be closed :)

I'd like to have it but I'm the only one maybe. Sure, it may be configurable / hidden for who doesn't want it

I don't see this as related to buildo's workflow and it would be extra code (not much, but still) to maintain.
You can always build your own style using something like https://chrome.google.com/webstore/detail/styler/bogdgcfoocbajfkjjolkmcdcnnellpkb?hl=en

Ok you won I like styler

💅


Add SimpleLogin

Project URL
https://github.com/simple-login/mac-app
Category
Extensions, Productivity, Security
Description
Protect your email with aliases and more. Its Safari Extension helps you create aliases on the fly without leaving Safari.
Why it should be included to Awesome macOS open source applications  (optional)
Checklist

[x] Edit applications.json instead of README.md.
[x] Only one project/change is in this pull request
[x] Screenshots(s) added if any
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          2 Warnings

:warning:
Please rebase to get rid of the merge commits in this Pull Request

:warning:
Found 1 link issue, a project collaborator will take care of these, thanks :)

Link issue by awesome_bot

Line
Status
Link

7862
Dupe
https://github.com/simple-login/mac-app

  Generated by :no_entry_sign: Danger

@ntnhon It's already in this list.


Prettier is throwing error on NoteList.tsx file line number 30

To Reproduce
go to this src/client/containers/NoteList.tsx line number 30
prettier is throwing this error

Expected behavior
There should be no prettier error
Actual behavior

Notes

@rohit-saluja I can fix this please assign me this work


Some YouTube embedded videos not showing thumbnails

Describe the bug
I posted a YouTube video, and the thumbnail is not showing in the card. However, I have seen other users post videos where the thumbnail does show.
To Reproduce
Steps to reproduce the behavior:

See another user's video with thumbnail: https://bsky.app/profile/tedunderwood.me/post/3khhukekhjy2d
See another user's video with no thumbnail: https://bsky.app/profile/adamatic.bsky.social/post/3khi3o2wdpr2z
See my post, with no thumbnail: https://bsky.app/profile/adamatic.bsky.social/post/3khi3o2wdpr2z
See my other test post, with a thumbnail: https://bsky.app/profile/adamatic.bsky.social/post/3khi6juow6a25

Expected behavior
There should be a thumbnails in 2. and 3., above.
My theory is that only videos which were uploaded a long time ago successfully capture the thumbnail.  I don't know the YT API, but maybe this is thumbnail format/version related.
https://developers.google.com/youtube/v3/docs/thumbnails
Screenshots
screenshots of 3. & 4. above:

Details

Platform: Windows Firefox & MacOS Firefox & MacOS Chrome

Additional context
As a bonus, it would be cool if on the bottom of the card, instead of the the URL to the video, the card instead displayed the Channel Name: Video title, or just video title to save space.

Actually, while I thought that the issue was related to upload date, the link in 1. is only 6 months ago... so maybe the date of upload is not related to the issue.

I thought maybe it was magically related to the new YT tracking info which I forgot to remove in post 1., but I removed it and the video data was still not extracted: https://bsky.app/profile/adamatic.bsky.social/post/3khibejef7p2t

Last effort at helping:
"I have a react native app that makes a media card for youtube videos which a user posts.
But only some video posts extract the video thumbnail, and title.. why could this be?"
https://chat.openai.com/share/b1ced529-b18b-4284-8a72-682c5596ee88

https://github.com/bluesky-social/social-app/pull/2328 Should fix this, as well as some updates by hailey to handle more URL types (m.)


Installing Pthon+Jupyter kernel picker does not work until reloading VSCode

After being first prompted to install Python + Jupyter extensions the kernel picker does not prompt for anything other than remote kernels (with Codespaces extension installed too). Reloading the window fixed it so I could pick from the kernel picker use Codespaces kernel.

No longer an issue


[DOCS] Add Flink DataStream API demo in Flink Guide.

Change Logs
Describe context and summary for this change. Highlight if any code was copied.
Impact
Describe any public API or user-facing feature change or any performance impact.
Risk level: none | low | medium | high
Choose one. If medium or high, explain what verification was done to mitigate the risks.
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Thanks for the contribution @hechao-ustc , i have left one small comment.

Thanks for the contribution @hechao-ustc , i have left one small comment.
@danny0405 hi danny，Thanks for your comment，I have updated the content：

Thanks, can we also add the doc for archived release 0.12.0 ?

I have added the doc，please help me with code review again, thank you very much.


Try fixing linux crashes by emitting the StopWork event in the UI thread

I have uses PyCommandEvent to forward the information about a finished thread to the UI thread.
This PR partially fixes #17. On Linux the app now no longer inconsistently crashes in random places (race condition?).
It now crashes on building the TreeView in plugins though, but this seems to be a separate issue.

Uh, the lint is complaining about files I didn't touch, hmmm


Long screenshots are forced to scale

Describe the bug
Screenshots that are long enough to modify are scaled to an extremely blurry resolution
This bug appears in versions after 3.0.0, and ci builds don't fix it either
--DeepL translation
To Reproduce
Select a long enough screenshot, say 1080 x 18259, and when making changes it will somehow scale to 242 x 4096
Expected behavior
The resolution should be normal.
Screenshots

Smartphone (please complete the following information):

Device: OnePlus Ace Racing Edition
OS: ColorOS 14

It's not a bug, just defense from crashing, you can set normal resolution and it will be okay, anyway, which version are you used in the latest screenshot? It should load at least the size of the original

Now is https://github.com/T8RIN/ImageToolbox/commit/027f6108bc2c57dc0849c8a81ef8914214c1e015, Still not loading the original size

--- DeepL translation

I think it's the key

Should be ok now

It's OK now. Thanks.


Checkbox is not working on ionic template.

I created one field to recieve array of string with this code:
dias: {
type: [String],
optional: true,
autoform: {
type: "select-checkbox",
'label-type': 'placeholder',
placeholder: 'Dias',
options: function () {
return [
{label: "Segunda-Feira", value: 'Segunda-Feira'},
{label: "Terça-Feira", value: 'Terça-Feira'},
{label: "Quarta-Feira", value: 'Quarta-Feira'},
{label: "Quinta-Feira", value: 'Quinta-Feira'},
{label: "Sexta-Feira", value: 'Sexta-Feira'},
{label: "Sábado", value: 'Sábado'},
{label: "Domingo", value: 'Domingo'}
];
}
}
},
Then in QuickFOrm the checkbox fields looks like this:

Have some way to fix it or it is a bug?

Hmm yeah looks like we haven't implemented select-checkbox correctly. I'll see if I can get some time this weekend to take a look at it.

I ran into this, too, and worked around it by adding label=false on the afQuickField.

Fixed in 1.0.5


Concept for history of Digital Twins >> implementation part

TBD

child of https://github.com/eclipse-tractusx/sig-release/issues/635

Obsolete for now


Which theme is used in Neovim ??

Check my nvchad repo

In nvchad there are lots of themes bro, looks like onedark. But which is this one in the screenshot?

Nordchad

Thanks


Support for manganelo/mangakakalot

I would really like to see support added for this site, or I would like some help trying to figure out how to add it myself, as it said in the readme to ask for help.

yeah would love support for mangakakalot aswell, it should be possible because every img is on the page, i just dont know how to do it.


(litmus): Update the docker pull count with chaos-operator

Signed-off-by: Chandan Kumar<EMAIL_ADDRESS>
Proposed changes

Update the docker pull count with chaos-operator instead of ansible-runner which is depreciated

Types of changes
What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

[ ] New feature (non-breaking change which adds functionality)
[x] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation Update (if none of the other choices applies)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the commit for DCO to be passed.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have added necessary documentation (if appropriate)

Please don't merge this PR. I am testing this PR for auto-merge bot

/merge

/merge

/merge

/merge

/merge

/merge

/merge


Remove peerDependency

Having a side effect of npm i pre-commit -D where it adds which as a dependency to my library is crazy.
Let's not use peer dependencies.

 Unfortunately, this patch would break : https://github.com/observing/pre-commit/pull/15 (windows support)

@3rd-Eden you require which. Just depend on it.

This should be good to merge.

Merged this in, but it would require an fix to the installation process to ensure that node is always capable of resolving the which module. Instead of copying the hook i'm going to create a symlink to the hook file. After that, i'll publish a new 0.2

Oh shit, the hook imports which. you do need a peer dependency :(
Does a symlink also fix it ?

@Raynos That was exactly the reason why we had it as a peerDependency which was an awful hack.
I've tested symlinks on my local machine and they work like a charm. This is a much cleaner solution than copy and pasting a file in the .git directory. As this a potential breaking change i'm not going to bump to 0.2 but to 1.0 directly. Currently refactoring the contents of the actual hook file so I can write some tests against this. I hope to have it all done this evening.
Sorry for the long delays!

@3rd-Eden no worries.
We could also copy the entire which module (https://github.com/isaacs/node-which/blob/master/which.js) into the hook. its only a 100 lines.

@Raynos It was in need of much needed refactor anyways.


audacity: 2.4.2 -> 3.0.2

The XGD-config patch is removed since it conflicts with the new version of audacity, as it was not merged upstream.
Audacity now requires their own fork of wxWidgets, according to https://wiki.audacityteam.org/wiki/Building_On_Linux - this is the cause of current trouble since I am new to nix and unsure how to integrate it. I copied the current 3.1.4 nixpkgs version of wxWidgets found at pkgs/development/libraries/wxwidgets/3.1/default.nix and modified it to retrieve the forked version, but that's it so far.

Motivation for this change
Audacity has not been updated to the latest major version (3) on any linux distribution that I found. That includes Ubuntu (of course), but also even Arch and Gentoo. This update is filled with bug fixes and should set us up to more easily update in the future as well.
Things done

The essence of the changes so far are noted in the commit message - this will not build. I am setting this up as a draft in order to invite help/suggestions to pull in wxWidgets correctly as a build dependency. I believe that this will be the only change needed to build this update correctly.

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

cc: @lheckemann @peterhoeg
note: I closed the pull request that was from my master branch; this is a reopening with its own branch following what I have observed to be convention. The previous version was here: https://github.com/NixOS/nixpkgs/pull/121618 and it had two relevant comments that I left.

I'm not sure if this might be relevant, but https://github.com/audacity/audacity/blob/master/cmake-proxies/wxWidgets/CMakeLists.txt#L76 might be helpful to look at.

For wxgtk, can't we just override it with the patches from audacity instead of copying the whole definition?

For wxgtk, can't we just override it with the patches from audacity instead of copying the whole definition?

That is a good idea, I'm just not sure how to apply it. Does this look good?
# https://github.com/wxWidgets/wxWidgets/compare/v3.1.3...audacity:audacity-fixes-3.1.3
patches = [
  (fetchpatch {
    url = "https://github.com/wxWidgets/wxWidgets/compare/v3.1.3...audacity:07e7d832c7a337aedba3537b90b2c98c4d8e2985.patch";
    sha256 = "047xl6hwfpwr6j7yxrkwh1akf7cjch3lnk4jnwq29sgdq8s5s2wi";
    name = "audacity_wxWidgets_fixes.patch";
  })
];

It says that this works, but it won't build on my computer because I'm getting patch failures for some reason for https://github.com/wxWidgets/wxWidgets/compare/v3.1.3...audacity:07e7d832c7a337aedba3537b90b2c98c4d8e2985.patch

An alternative is to override src to point to the audacity "fork" instead of adding the patches. Less error prone.

I didn't even consider that lol, trying it now

Nice to see my work being put to good use.

I applied this:
47 | let
48 |   wxGTK-audacity = wxGTK.overrideAttrs (oldAttrs: rec {
49 | -     patches = (oldAttrs.patches or []) ++ [
50 | -       (fetchpatch {
51 | -         url = "https://github.com/wxWidgets/wxWidgets/compare/v3.1.3...audacity:07e7d832c7a337aedba3537b90b2c98c4d8e2985.patch";
52 | -         sha256 = "00sgc7amgmymlgx8l3m9ls0cghmnbcfwbnslikridw6vlsp0bg08";
53 | -         name = "audacity_wxWidgets_fixes.patch";
54 | -       })
55 | -     ];
49 | +     src = fetchFromGitHub {
50 | +       owner = "audacity";
51 | +       repo = "wxWidgets";
52 | +       rev = "07e7d832c7a337aedba3537b90b2c98c4d8e2985";
53 | +       sha256 = "1mawnkcrmqj98jp0jxlnh9xkc950ca033ccb51c7035pzmi9if9a";
54 | +       fetchSubmodules = true;
55 | +     };
56 |   });
57 | in
58 | stdenv.mkDerivation rec {

and got this error in the middle of compilation:
/build/source/src/FileNames.cpp:815:10: fatal error: /usr/include/linux/magic.h: No such file or directory
  815 | #include "/usr/include/linux/magic.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~

Add linuxHeaders to nativeBuildInputs and substituteInPlace that path in src/FileNames.cpp to just "linux/magic.h". Or you could substitute it with ${linuxHeaders}/include/linux/magic.h instead but it really shouldn't be this hardcoded in the first place.

I have a successful build on my nixos desktop now

LGTM :+1:

Thank you everyone


publish opensource dataset to SAAS

Current Behavior
only a few datasets
Proposed Behavior
Solution Proposal

same as #760


events.json

What is your question?
I just wanna know if events.json is meant to load with the source code, since I moved a bunch of stuff from the mods folder to the source code preloads. Everything works except for the events not loading.

Yeah it also loads in source code, so its kinda weird that it isn't working for you...

i tried redoing the events and it still didn't work so im kinda confused
there isn't anything showing up in command prompt either

Nevermind it suddenly works again??


drivers: nrf: Fix UART TX hanging when using both polling and async API.

Fix UART TX hanging when using both polling and async API.
Signed-off-by: Mieszko Mierunski<EMAIL_ADDRESS>fixes #22264

@JordanYates Please check if your issue is fixed

I can confirm that the core problem is fixed, thanks @Mierunski
There is just my comment on my pre-emptibility to resolve, and I am happy.

@ioannisg ping


:honeybee: remove border from last row and reduce padding

:rocket: deployment of profiles succeeded (http://profiles-pr-148.dev.beta.nhschoices.net)

@alex-colbeck please can you take a look at the two specific profiles, mentioned by @beseven on trello:

http://profiles-pr-148.dev.beta.nhschoices.net/gp-surgeries/36036
http://profiles-pr-148.dev.beta.nhschoices.net/gp-surgeries/42056

We'll have to manipulate the data to see the fix for the issue raised. Let me know when you want to do this.

@st3v3nhunt wrote:

Given the tests were broken with no changes to the underlying data I assume that they will start to break again from 00:01 Tuesday 30th?

Raised an issue


Handling of field that contains multiple lines

Description
The CSV editor does not properly handle fields that contain multiple lines. This results in the editor either not recognizing the file as a valid CSV and not displaying an "Edit CSV" button, or rendering a blank screen when the button is pressed. =
Expected behavior
The CSV editor should recognize a field wrapped with double quotes that contains multiple lines as a single field in a row and render it correctly. Additionally, the enclosing double quotes should be preserved when saving the file.
Steps to reproduce

Create a CSV file with the following content:

Name,Age,Address
Alice,30,"123 Main St,
New York, NY"
Bob,25,"456 Elm St,
Los Angeles, CA"

Open the CSV file in the CSV editor.
Observe the following possible behaviors:
a. The editor does not recognize the file as a valid CSV.
b. The "Edit CSV" button is not displayed.
c. The "Edit CSV" button is displayed, but a blank screen appears when the button is pressed.

Can't reproduce this. I opened a new file, pasted your example switched language (bottom right) to CSV and clicked the Edit csv button -> works.
What language is displayed in the bottom right status bar?

Disabling Rainbow CSV solved my problem, thanks for pointing me in the right direction. Apologies for taking up your time!

@janisdd I reenabled Rainbow Edit and while it plays nice with some CSVs, others trigger Dynamic CSV. I have been unable to figure out why.
When I try and change the format to CSV it doesn't seem to stick, but changing it to CSV (Semicolon) does. Can't share current CSVs as the data is sensitive.
CSV0.7.4 and Rainbow v3.6.0.

@case-inlite I think this is now fixed in version 0.7.5. The "command" was working but the button was just not displayed.

@janisdd thanks seems to be working reliably now


chainntnfs+lntest: fix TestInterfaces

This flake has popped up multiple times,
2024/07/18 08:06:20 Running ChainNotifier interface tests for: btcd
--- FAIL: TestInterfaces (67.92s)
    --- FAIL: TestInterfaces/btcd_historical_spend_dispatch (30.06s)
        test_interface.go:872: spend ntfn never received
FAIL
FAIL	github.com/lightningnetwork/lnd/chainntnfs/test/btcd	67.937s
FAIL

Turns out it's failing here, where we rescan blocks to find the relevant spending tx,
https://github.com/lightningnetwork/lnd/blob/6dea86428d031171af30119e3f6599820dc5454a/chainntnfs/txnotifier.go#L1310-L1315
It's also easy to reproduce - need to run it multiple times tho,
case=TestInterfaces/btcd_historical_spend_dispatch_with_script_dispatch
pkg=chainntnfs/test/btcd
go clean -testcache | make unit-debug log="stdlog trace" pkg=$pkg case=$case timeout=10s

And the relevant logs,
2024-06-28 06:10:19.764 [CRT] NTFN: Found spending tx for outpoint=0000000000000000000000000000000000000000000000000000000000000000:0, but the transaction f78dafeb14b356ae7f2aefacc725b8700b6e9b206fdaa1d43d52d4a26a5cde63 does not have witness
2024-06-28 06:10:19.764 [ERR] NTFN: Unable to process transaction f78dafeb14b356ae7f2aefacc725b8700b6e9b206fdaa1d43d52d4a26a5cde63: witness stack is empty

Since we don't ever allow pre-segwit utxos to be used, we now update the tests to always create segwit v0 txns.

Hmm, I wonder if we need to increase some timeouts in other tests that use the lntest/unittest code?
I see the routing/chainview and chainntnfs/bitcoindnotify packages becoming a bit more flakey.
Here's an example:
 --- FAIL: TestHistoricalConfDetailsNoTxIndex (0.00s)
    --- FAIL: TestHistoricalConfDetailsNoTxIndex/rpc_polling_disabled (11.58s)
        bitcoind_test.go:241: timed out in syncNotifierWithMiner, got err=<nil>, minerHeight=430, bitcoindHeight=0

Since it says bitcoindHeight=0, I think maybe the notifier is not even started in this case. Pushed a commit to add debug logs. Will find out more in the CI.

Since it says bitcoindHeight=0, I think maybe the notifier is not even started in this case. Pushed a commit to add debug logs. Will find out more in the CI.

Thanks! But of course the tests don't fail anymore now :see_no_evil: Should I re-trigger the CI to run the unit tests again?
Or should we just merge and  look into the new flakes in a new PR?

Or should we just merge and look into the new flakes in a new PR?

Cool I'd prefer we merge this and investigate it in a new PR - have a trivial PR cooking locally to update the github action versions, we can then figure it out there, or whenever we see the flakes again in other PRs.


on selecting image in gallery my activity gets destroyed

@Lionertic This is the expected behavior of the app when working on low memory. You need to work on saving the UI state.
Please refer this: saving-states


A Roughly Implementation of SRL-Python

Hey, Guys.
I did not notice the discussion on https://github.com/SimpleRegex/SRL-PHP/issues/22 and has working on a roughly implementation of SRL-Python
Hoping to avoid the conflict of development of this library and to merge some of the implementation into this repo.
Current State:

Builder is done
Passed All the Features described in https://simple-regex.com/documentation

TODO:

Write DSL parser
Applying Rules described in https://github.com/SimpleRegex/Test-Rules

@mhbashari @KarimGeiger I would appreciate it if you guys review this issue :)

Hi @soasme,
thanks for your great work, looks pretty decent. As far as I know are you the first one to contribute, so I'd say first come, first serve.
I'll give you access to this repository, and if you like, you can join our developer Slack team as well.

I am willing to maintain this repository :)
It's my honor!

I will clean up the code and merge the first version code into this repo a few hours later :shipit:


Android usb tethering to HooToo TM02 openwrt

Hello! I've successfully installed openwrt on the tripmate nano but can't seem to get it to talk to my android phone when i set it to usb tether. I've tried creating different interfaces and following a few guides like these...
https://wiki.openwrt.org/doc/howto/usb.tethering
http://lgallardo.com/en/2011/05/26/usando-el-anclaje-de-red-tethering-de-android-en-openwrt/
...with no success. I was able to connect the hootoo to a wifi as a client in case it needed to download a package. Any advise?

You have to use packages matching to your version,
https://github.com/wingspinner/HooToo-Tripmate-HT-TM02-OpenWRT/tree/master/ramips_openwrt


The arrow error

If I set 10 items, the arrow and spin wheel do not show the chosen item.
Like image
https://imgur.com/a/A3mXjfc

Please take a look at this issue in order to understand how the landing slice is chosen: https://github.com/tapptitude/TTFortuneWheel-iOS/issues/1


Sporadic test failure: scan::appmaker::scan_workflow_from_git_url

Describe the bug
Sometimes, rarely, the scan::appmaker::scan_workflow_from_git_url test case fails.
To Reproduce
🥴
Expected behavior
The test case should always succeed
Actual behavior
See this CI run log:
failures:

---- scan::appmaker::scan_workflow_from_git_url stdout ----
thread 'scan::appmaker::scan_workflow_from_git_url' panicked at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:250:5:
Unexpected stdout, failed var.is_match((?m)^Scanned (549.97|550.05) MiB from 7,92[68] blobs in .*; 23/23 new matches$)
├── var: Scanned 550.05 MiB from 7,927 blobs in 1 second (729.58 MiB/s); 23/23 new matches
│
│    Rule                         Total Findings   Total Matches
│   ─────────────────────────────────────────────────────────────
│    AWS API Key                               3               3
│    AWS S3 Bucket (path style)                3              13
│    Amazon Resource Name                      3               3
│    Generic Secret                            3               3
│    AWS Secret Access Key                     1               1
│
│   Run the `report` command next to show finding details.
└── var as str: Scanned 550.05 MiB from 7,927 blobs in 1 second (729.58 MiB/s); 23/23 new matches

     Rule                         Total Findings   Total Matches
    ─────────────────────────────────────────────────────────────
     AWS API Key                               3               3
     AWS S3 Bucket (path style)                3              13
     Amazon Resource Name                      3               3
     Generic Secret                            3               3
     AWS Secret Access Key                     1               1

    Run the `report` command next to show finding details.

command=`"/home/runner/work/noseyparker/noseyparker/target/release/noseyparker-cli" "scan" "--datastore=/tmp/.tmpexTCIC/datastore" "--git-url=https://github.com/mozilla-appmaker/appmaker" "--ruleset=all"`
code=0
stdout=\```
Scanned 550.05 MiB from 7,927 blobs in 1 second (729.58 MiB/s); 23/23 new matches
error: test failed, to rerun pass `-p noseyparker-cli --test test_noseyparker`

 Rule                         Total Findings   Total Matches
─────────────────────────────────────────────────────────────
 AWS API Key                               3               3
 AWS S3 Bucket (path style)                3              13
 Amazon Resource Name                      3               3
 Generic Secret                            3               3
 AWS Secret Access Key                     1               1

Run the `report` command next to show finding details.
\```

stderr="2024-04-26T16:38:47.0[527](https://github.com/praetorian-inc/noseyparker/actions/runs/8851458936/job/24308038487#step:9:528)03Z ERROR noseyparker_cli::cmd_scan: Failed to read blob 803c41c9e0c0bd42ef1d430001f994af24a7c535 from Git repository at /tmp/.tmpexTCIC/datastore/clones/https/github.com/mozilla-appmaker/appmaker: An object with id 803c41c9e0c0bd42ef1d430001f994af24a7c535 could not be found\n"

stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: assert_cmd::assert::AssertError::panic::panic_cold_display
   3: core::ops::function::FnOnce::call_once
   4: test_noseyparker::scan::appmaker::scan_workflow_from_git_url
   5: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

failures:
    scan::appmaker::scan_workflow_from_git_url

test result: FAILED. 70 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 7.60s

Error: Process completed with exit code 101.

Output of noseyparker --version
noseyparker 0.18.0-dev

Build Configuration:

    Build Timestamp:    2024-04-26T16:38:12.626689961Z

    Commit Timestamp:   2024-04-26T12:30:46.000000000-04:00
    Commit Branch:      main
    Commit SHA:         0cce95910be38058cc0cf00b548a892e3ed5dc35

    Cargo Features:     default,disable_trace,log,mimalloc,release
    Debug:              false
    Optimization:       3
    Target Triple:      x86_64-unknown-linux-gnu

Build System:

    OS:                 Ubuntu
    OS Version:         Linux 20.04 Ubuntu

    CPU Vendor:         AuthenticAMD
    CPU Brand:          AMD EPYC 7763 64-Core Processor
    CPU Cores:          2

    rustc Version:      1.77.2
    rustc Channel:      stable
    rustc Host Triple:  x86_64-unknown-linux-gnu
    rustc Commit Date:  2024-04-09
    rustc Commit SHA:   25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04
    rustc LLVM Version: 17.0

Additional context
I think I've only ever seen this in GitHub Actions CI, though I'm not certain.
I suspect there is some race condition in the gix library.

I was able to reproduce locally!
I ran the following in a loop on a 14-core M3 MacBook Pro, and after 99 attempts, saw a similar error message:
$ i=0; while true; do ((i = i + 1)) && echo "### take2.$i ###" && rm -rf appmaker.np && cargo run -F release -r -q -- scan -d appmaker.np appmaker.git -j20; done
...
### take2.99 ###
2024-04-26T17:05:48.307767Z ERROR noseyparker_cli::cmd_scan: Failed to read blob 0413e897ddb651d58e86dc2363c631b6b7909820 from Git repository at appmaker.git: An object with id 0413e897ddb651d58e86dc2363c631b6b7909820 could not be found
Scanned 549.96 MiB from 7,925 blobs in 0 seconds (2.09 GiB/s); 4/4 new matches

 Rule                    Total Findings   Total Matches
────────────────────────────────────────────────────────
 Generic Secret                       3               3
 AWS Secret Access Key                1               1

Run the `report` command next to show finding details.
...

This is difficult to reproduce. I've had to run hundreds or thousands of times in a loop to see that error message again.

Interestingly, the appmaker.git clone — which I obtained with git clone --bare https://github.com/mozilla-appmaker/appmaker appmaker.git — contains only a single packfile:
% tree appmaker.git
appmaker.git
├── HEAD
├── config
├── description
├── hooks
│   ├── applypatch-msg.sample
│   ├── commit-msg.sample
│   ├── fsmonitor-watchman.sample
│   ├── post-update.sample
│   ├── pre-applypatch.sample
│   ├── pre-commit.sample
│   ├── pre-merge-commit.sample
│   ├── pre-push.sample
│   ├── pre-rebase.sample
│   ├── pre-receive.sample
│   ├── prepare-commit-msg.sample
│   ├── push-to-checkout.sample
│   └── update.sample
├── info
│   └── exclude
├── objects
│   ├── info
│   └── pack
│       ├── pack-fd9127ec007dda804dc00ea7a61b1cfa0ba55921.idx
│       └── pack-fd9127ec007dda804dc00ea7a61b1cfa0ba55921.pack
├── packed-refs
└── refs
    ├── heads
    └── tags

9 directories, 20 files

The version of git on my laptop, where I've been able to reproduce very rarely:
$ git --version
git version 2.39.3 (Apple Git-146)

@Byron FYI, there appears to be a race condition somewhere in gix, either its reading code or a caching layer somewhere, which I can intermittently trigger in Nosey Parker.
Specifically, when scanning a Git repository, Nosey Parker first enumerates all object IDs, building a vector of blob IDs. Then in a later stage, that vector of blob IDs is used in a Rayon pipeline to read each blob and scan it, in parallel. At the rate of around one in every few hundred attempts when using multiple worker threads, I see gix failing to read one of those blob objects whose ID was previously enumerated.
Last week I tried isolating where the behavior is coming from by trying to disable all caching mechanisms in gix, but that didn't make the problem go away. Either it's in the core ODB reading code, or (more likely) I failed to effectively disable all of the gix caching mechanisms.
This is not a super high priority Nosey Parker issue for me right now, but I wanted to make you aware of it. I'm happy to do further investigation if you have suggestions to better debug this. Thank you!

@Byron Thank you! I could look at this more next week. Let me know if I can help.

Thank you! I am slowly getting back into it and noticed something interesting: The code to get the initial set of objects also uses a parallel implementation that calls odb.header(), which is when multiple threads trigger loading all the packs right after the indices have been pre-loaded to support the iteration. From what I can tell, this never hits a race-condition, for some reason that I try to figure out (btw, I didn't reproduce it yet).
After the initial iteration, the whole ODB would be loaded, but here it seems the repository is re-opened so it starts at zero. Now find_object() runs into the problem occasionally even though its implementation (also in regards to how it deals with concurrency) should be exactly the same. What I am saying is that in theory, re-using the same repository instance that was used for counting could possibly fix the issue.
Chances are that the underlying issue in somewhere in the code that dynamically loads indices, as all of the sudden it fails to find an index with the object, at least in one thread (maybe another did successfully load it, or is in the process of doing so and somehow one thread doesn't get to wait for that).
Hopefully I will have a repro soon.

After the initial iteration, the whole ODB would be loaded/memmapped, indices and packs, but here it seems the repository is re-opened so it starts at zero.

Yes, you're right — Nosey Parker enumerates repos in one phase, and then in the next phase reopens each repo and reads the blobs from it. This re-opening is done to avoid running out of memory, as otherwise it might need to keep thousands of repos open at once.
I intend to rework this scheme eventually, to start scanning immediately rather than first enumerating everything and then scanning it. But that's a medium-term project for me.

Great news! I could reproduce the issue and can do so consistently. Having less packs seems to be the key here, and from what I can tell, this situation will put threads into a waiting-loop and it's my guess that something there goes wrong so they don't actually pickup newly loaded indices.
❯ hyperfine -m100 './target/release/gix -r boto -t10 --trace odb stats --extra-header-lookup' --show-output
Benchmark 1: ./target/release/gix -r boto -t10 --trace odb stats --extra-header-lookup
 18:04:54 counting done 41.4k objects in 0.01s (4.4M objects/s)
 18:04:54  tracing ERROR    🚨 [error]: Object that is known to be present wasn't found | err: NotFound { oid: Sha1(2558c83eb8f313829b7573f70081c2c7ab1581c4) }
 18:04:54 re-counting done 41.4k objects in 0.10s (394.8k objects/s)
 18:04:54     tracing INFO     run [ 116ms | 98.39% / 100.00% ]
 18:04:54     tracing INFO     ┝━ ThreadSafeRepository::discover() [ 1.59ms | 0.09% / 1.37% ]
 18:04:54     tracing INFO     │  ┕━ open_from_paths() [ 1.48ms | 1.22% / 1.28% ]
 18:04:54     tracing INFO     │     ┕━ gix_odb::Store::at() [ 70.0µs | 0.06% ]
 18:04:54     tracing INFO     ┕━ ThreadSafeRepository::open() [ 277µs | 0.06% / 0.24% ]
 18:04:54     tracing INFO        ┕━ open_from_paths() [ 208µs | 0.15% / 0.18% ]
 18:04:54     tracing INFO           ┕━ gix_odb::Store::at() [ 38.2µs | 0.03% ]
Only JSON is implemented - using that instead
Error: At least one object couldn't be looked up even though it must exist
Error: Command terminated with non-zero exit code: 1. Use the '-i'/'--ignore-failure' option if you want to ignore this. Alternatively, use the '--show-output' option to debug what went wrong.

With the latest modification, I cannot reproduce the issue anymore even after a thousand runs, where previously it would trigger after less than 50 iterations usually.
❯ hyperfine -m1000 './target/release/gix -r boto -t10 --trace odb stats --extra-header-lookup'
Benchmark 1: ./target/release/gix -r boto -t10 --trace odb stats --extra-header-lookup
  Time (mean ± σ):     124.9 ms ±   2.2 ms    [User: 157.1 ms, System: 15.8 ms]
  Range (min … max):   116.3 ms … 137.4 ms    1000 runs

The only unfortunate thing here is that I wasn't able to fix it in a way that avoids re-reading the state on disk to pick up newly added packs, which shouldn't be needed here. On the bright side, it's quite a rare issue in the first place so this inefficiency probably doesn't matter much for most.

Thank you @Byron for the speedy response! I will give the main branch of gitoxide a try in Nosey Parker.

Gix v0.63 was just released, and it should fix this issue for good :).

Yes, upgrading gix from 0.62 to 0.63 seems to fix this problem for me. Thank you @Byron!


rocksdb: always ref state and explicit snapshot lengths

depends on https://github.com/holepunchto/hypercore-storage/pull/41


[type: refactor] shade some dependencies in agent to solve conflict

// Describe your PR here; eg. Fixes #issueNo

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #2749 (187322b) into master (cc2d590) will decrease coverage by 0.58%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #2749      +/-   ##
============================================
- Coverage     60.12%   59.53%   -0.59%
+ Complexity     4404     4376      -28
============================================
  Files           681      681
  Lines         19613    19611       -2
  Branches       1743     1743
============================================
- Hits          11792    11676     -116
- Misses         6823     6949     +126
+ Partials        998      986      -12

Impacted Files
Coverage Δ

...ache/shenyu/plugin/grpc/cache/GrpcClientCache.java
68.75% <0.00%> (-31.25%)
:arrow_down:

...n/alibaba/dubbo/cache/AlibabaDubboConfigCache.java
43.75% <0.00%> (-31.25%)
:arrow_down:

...gin/apache/dubbo/cache/ApacheDubboConfigCache.java
43.03% <0.00%> (-29.12%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
44.68% <0.00%> (-19.15%)
:arrow_down:

...a/org/apache/shenyu/common/utils/VersionUtils.java
67.85% <0.00%> (-10.72%)
:arrow_down:

...apache/shenyu/admin/utils/ShenyuDictH2Trigger.java
63.63% <0.00%> (-9.10%)
:arrow_down:

...ache/shenyu/admin/utils/PluginHandleH2Trigger.java
63.63% <0.00%> (-9.10%)
:arrow_down:

...che/shenyu/sync/data/http/HttpSyncDataService.java
70.58% <0.00%> (-7.36%)
:arrow_down:

.../apache/shenyu/admin/model/dto/BatchCommonDTO.java
50.00% <0.00%> (-7.15%)
:arrow_down:

...apache/shenyu/admin/model/dto/AuthPathWarpDTO.java
57.14% <0.00%> (-7.15%)
:arrow_down:

... and 26 more

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 cc2d590...187322b. Read the comment docs.

LGTM


Support adding/removing metadata Responsible Parties

Description
As a catalog author, I want to add/remove Responsible Parties in regard to metadata.
Acceptance Criteria

Additional Responsible Parties can be added
Responsible Parties can be removed

Proposed Solution
No response
Additional Notes
No response
Implementation

[ ] I can (or plan to) submit a pull request to implement this
[ ] Implementing this may result in a breaking change

Depends on https://github.com/EasyDynamics/oscal-react-library/issues/795


be able to remove from cart in mass as well

on same page as the add to cart (ie, in the table)

We should add cart items to the serializer for the user to do this more easily.


quickstart basic - missing qa/llm_tests:?

Ran:
llmtune generate config
llmtune run ./config.yml
Things worked well (once I fixed my mistake with Mistral/huggingface repo permissions).    The job ran very fast and put results into the "experiment" directory.   But the experiment/XXX/results/ directory only has a "results.csv" file in it.  I expected there to be results from the qa/llm_tests section in the config.yml file, which looks like this:
qa:
llm_tests:
- jaccard_similarity
- dot_product
- rouge_score
- word_overlap
- verb_percent
- adjective_percent
- noun_percent
- summary_length
Do I have to do something extra to get the qa to run?

Hi @richardehughes, we decided to take little pause in adding new features to the CLI until we finish our test suite (for the program, that is). This should be done by today -- and we'll release the LLM tests integration under a new minor version next week.
But you can still run all the test by importing the module directly like so:
from src.qa.qa import LLMTestSuite
from src.qa.qa_tests import LengthTest, JaccardSimilarityTest

# Load prompts, ground_truths, and model_preds from the results.csv file
# Your code here

# Running LLM Tests
tests = [LengthTest(), JaccardSimilarityTest()]
test_suite = LLMTestSuite(tests, prompts, ground_truths, model_preds)
test_suite.run_tests()
test_suite.print_test_results()
test_suite.save_test_results("path/to/save/test_results.csv")

This is addressed in release v0.2.2
https://github.com/georgian-io/LLM-Finetuning-Toolkit/releases/tag/v0.2.2


Create health checks for app

https://pypi.org/project/py-healthcheck/
https://nickjanetakis.com/blog/create-a-health-check-url-in-your-web-app-and-monitor-its-uptime


creating HostConfig at container start deprecated by docker

i think we still support this and if not this should be closed, but this was deprecated as of docker 1.10.0.
https://docs.docker.com/engine/deprecated/

No, I don't think that is the case anymore. All configuration is done during container create, with start only firing up the container --> https://github.com/rhuss/docker-maven-plugin/blob/782fa9364022bbcac19e9e69f344b17a94548773/src/main/java/org/jolokia/docker/maven/access/hc/DockerAccessWithHcClient.java#L169-L177


Alistairbntl/velocity block pc

@cekees - I think this is good to go in.  I could add a test to increase the diff coverage, but I don't think it would be that valuable.  This PR is really just small maintenance stuff anyway.


Use RRU red for package names

You have them using green now. Let's use the red from this palette. The hex value is #ec3325.

assigned  #ec3325 as .rrured[] in the styling css file and replaced for all package names in all slide decks


Linux kernel driver support

Similarly to ChaosKey, support for Infnoise by the Linux kernel would be appreciated. In that case Infnoise's random data should be feeded into kernel's LRNG which does the PRNG via ChaCha20 and alike.

I'm interested in having a look at how this might be done. Right now by default, the FT240XQ's ID 0403:6015 causes it to get picked up by the ftdi_sio in order to allow it to be used by the userspace driver libftdi. @manuel-domke would you happen to have a leetronics USB VID and suggested PID that could be used to reprogram existing Infnoises with?

Looks like I can use 1209:3701 according to https://pid.codes/1209/3701/. Now it should be a matter of intercepting the URBs eventually fired off by libinfnoise since the FTDI protocol isn't well documented (https://krinkinmu.github.io/2020/09/05/ftdi-protocol.html) and recreating them in the kernel driver.
From what I can tell from a cursory glance over the libinfnoise source, there would be control URBs for setting things such as baud rate, pin mode mask and synchronous bitbang mode, and bulk URBs for writing the bitbang clock for the switches and reading from the comparators

@AidanGG Any progress on this?

Sadly not, unfortunately. I have mostly stopped using the infnoise.

@AidanGG what did you switch to ?

In case anyone else wanted to write a kernel driver for the infnoise, here's one approach - https://github.com/tectrolabs/swiftrng/blob/master/linux/swrandom/swrandom.c


CC0120: Suggest Case Else for Select Case statements (VB)

A lot of bugs are caused by non-exhaustive matching in select statements.
If there is no Case Else one should be added that throws an exception.
Before:
Select Case A
  Case B
    DoSomething
  Case C
    DoSomethingElse
End Select

After:
Select Case A
  Case B
    DoSomething
  Case C
    DoSomethingElse
  Case Else
    Throw New Exception("Unexpected Case")
End Select

Should not raise for boolean if true and false are already handled:
Dim a = True
Select Case a
    Case True
    Case False
End Select

Diagnostic Id: CC0120
Category: Design
Severity: Warning

The second part of this request (not suggesting case else if all options are exhausted) may be quite difficult to evaluate, particularly if we consider the case of pattern matching options coming with future versions as well.


docs, rsu: updates for IOFS refactor of rsu.py

Signed-off-by: Tim Whisonant<EMAIL_ADDRESS>

Coverage remained the same at 67.318% when pulling 1069fae2bc9b829328d956366b046fcd54673ddf on tswhison/rsu_doc into 700730de005a9704c6034edc7a6a40af2594f5d5 on master.

Doing a manual "Build RPMs" passes


null_safety

fix #54, need test.

@ReinBentdal

Changed. I tested it in my project and everything is normal. I think you'd better test it again to make sure it can be used normally. THX.

@ReinBentdal

Any chance this could landed soon?

Anything anyone can do to help this along? Wanting to update a couple apps to full nullsafety and this is the only outlier. And I really love using this package.

well, I unfortunately doesn't have the time at the moment to go through the entire package and verify the changes made. I see two possibilities to get it out fast. Either I can trust the code and push it out, or have someone else test and verify the changes.

I did a quick review and it does look pretty safe. Basically every single property was nullable already, so it's just a pass declaring everything as explicitly nullable and passing them unchanged to the flutter widgets.
Is there any sort of test suite you use internally?

I have been trying to use it for nearly half a month and have not found any problems so far

@ReinBentdal

@esDotDev i don't use any specific test suite. Since there have been some users of this, and since most of the properties anyways is nullable, I will accept the pull request and push a new version


Adds PanelChart widget

Closes #40
Todo

[x] Proof of concept
[ ] Clean up, Refactor, test
[ ] Add documentation
[ ] Review
[ ] Implement Feedback

Assets
https://github.com/louisnw01/lightweight-charts-python/assets/42288570/b7cbb351-1dd5-4226-955e-184839a23f63
https://github.com/louisnw01/lightweight-charts-python/assets/42288570/dcea7b74-cd94-4133-8a84-a4e3fcea3829


feat: allow for multiple cli commands

Description
We add the option to have multiple commands in notary. For now we only implement the start command with the same usage as the initial root command:
notary start -config config.yaml

Rationale
We will soon add a version command which should be handled differently from starting the server and will not require a config file for instance. Here we will want to run:
notary version
notary start --config config.yaml

And those two commands should be handled independently.
This is a breaking change
This is a breaking change, and will require changes in the charm. Here we only bump the minor version as Notary is not yet released and we don't want the first released version to be 32.51.1.
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[ ] I validated that new and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

What about adding a version field to the /status API endpoint? It's a bit more cumbersome to use, but I just can't imagine us having any other commands in the CLI. notary is a web application after all, and this is its binary.

What about adding a version field to the /status API endpoint? It's a bit more cumbersome to use, but I just can't imagine us having any other commands in the CLI. notary is a web application after all, and this is its binary.

If someone is running notary on their system and quickly want to know which version they are running, I don't think we want to ask them to make an API call. Though I agree it could be surfaced in the UI somewhere.
I can definitely imagine it having a cli to communicate with the notary server. I'm not saying we will, but I can see some value in something like:
notary login <my token>
notary request certificate <my csr>
notary version
notary help

I can definitely imagine it having a cli to communicate with the notary server. I'm not saying we will, but I can see some value in something like:
notary login <my token>
notary request certificate <my csr>
notary version
notary help

that may be nice actually

Moving to draft as I am improving this


Cvalencia/vldb pool replica count update

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

@christianvalencia7  It looks like the recording files are not checked in. The CI is complaining about this.

@m-nash Can you please merge the PR?


0.2.12: load directory with hugging-face embeddings fails

Describe the bug
I am trying to use hugging-face embeddings with an embedding model that has 1024 dimensions.
When I run memgpt load directory --recursive ... it fails with an assertion (lines 123..125 of cli_load.py):
        assert (
            len(node.embedding) == user.default_embedding_config.embedding_dim
        ), f"Expected embedding dimension {user.default_embedding_config.embedding_dim}, got {len(node.embedding)}: {node.embedding}"

It expected 1024 dimensions, got 384. I think this is because of the fallback that I put into place "at the last minute" in order to merge my PR that partly fixed memgpt load.
If I instead use local embeddings then everything works.
Please describe your setup

[ ] MemGPT version
0.2.12

[ ] How did you install memgpt?
poetry

[ ] Describe your setup
MacOS Sonoma
Terminal

Screenshots
N/A
Additional context
N/A

If you're not using OpenAI, please provide additional information on your local LLM setup:
Local LLM details
If you are trying to run MemGPT with local LLMs, please provide the following information:

[ ] The exact model you're trying to use (e.g. dolphin-2.1-mistral-7b.Q6_K.gguf)
[ ] The local LLM backend you are using (web UI? LM Studio?)
[ ] Your hardware for the local LLM backend (local computer? operating system? remote RunPod?)

I believe this is the same issue as #814?


Improve styling of inventoryDisplay and toolbarDisplay

Description
Task: Improve styling of inventoryDisplay and toolbarDisplay.
Feature: Complete Inventory
Currently the inventoryDisplay and toolbarDisplay do not match the style of the game and are not consistent. This ticket seeks to resolve this issue.
Dependencies

[ ] Window skin needs to be created(#xx)

Milestones
List of steps that need to be completed for this task.

[x] Improve Styling of inventoryDisplay (Oct. 08)
[x] Improve Styling of toolbarDisplay (Oct. 08)
[x] Add number to inventory to show respective slot number and selection
[x] Remove need for the ItemFrame and Selection Image, use Libgdx Rectangle Instead
[ ] Verify skin satisfies design committee's design (Oct. 10)

Completion Deadline: Oct. 11
Documentation

Inventory

Member

Tristan Duncombe (@tristanduncombe) Tristan Duncombe

It seems as though the Skin will not be completed. May need to be merged with the new skin.


Cross-platform support for test infrastructure

Having looked into this a bit, ava (which we currently use) seems like a poor backend for a cross-platform test toolkit because it is so tightly coupled to the test source code. On test failure ava will print the source code that the assertion stack trace points to, which if abstracted will always just be some internal piece of code. Jest seems like it would suitable as a JS backend.
@bordoley has the same need, and has made reUnit as a quick and dirty cross-platform test framework and has plans to integrate it with Jest. We could perhaps build further on that, but should in any case try to consolidate our efforts. Also see bs-jest
cc @dorafmon

I have no problem with switching to bs-jest for test backend, the choice of using ava is made before there is bs-jest. So if I understand you correctly, what we are proposing here is:

Have a unified test interface, like reUnit.rei
For this interface we have two separate implementations, one uses a native backend, probably improve upon reUnit.rei and then also have a JS backend, built around bs-jest?

Also, do you think it is possible for us to support some kind of source map for bs-jest so when a test fail it reports back the location in ml/re file, not the JS file (although it is fairly easy to find out, because BS output is quite readable.)

The js backend certainly doesn't have to be bs-jest, it might be simpler to just copy or define the externals needed internally. But I think Jest is a suitable js backend. Also, bs-jest is designed in a way that makes it easy to swap out the assertion library (but not the test runner) and could be useful as inspiration.
I don't think source mapping will be very useful when the assertions are abstracted, since the stack traces will just point to internals. You'd have to provide LOC for each and every test I think, which really doesn't seem worth it to me. I just use the test name, which works fine if you have good test names and a well-ordered test suite.

I'm very supportive of any solution that cleanly integrates with jest for unit testing and would be willing to take it on as a dependency in imm.re. Beyond jest's top notch test runner, the code coverage reports would be of significant value.
My only real requirement is that the test dsl be decoupled from jest itself so that a minimal test runner such as ounit's can be used for native testing.

I've created a POC of a cross platform test framework here: https://github.com/glennsl/poc-xtest
It's based on ocamlbuild and bsb, with each build process including a separate platform-specific Impl module that does the actual work. Note that in the Jest implementation the run function is a no-op since jest runs each test file separately, while the native implementation needs a main function that collects and runs the tests, which could cause some tests to be skipped by mistake.

@glennsl could you open a PR to integrate bs-containers with poc-xtest? Thanks.

There's a couple things I think we should sort out first:

The problems that might be caused by jest and native tests being collected and run differently
The style of assertions. Should it be like jest to better match its output: expect true |> toEqual false, or the simpler assertEqual true false, or something else?
How to print native test values? This might require some design changes.
Should we integrate with OUnit instead of rolling our own native runner?

Is ounit actively maintained? Looking at the test runner, it doesn't appear to do anything particularly fancy. I'll admit a preference to focus on Jest integration first, as it is far more advance afaict (parallelized test runs, code coverage reports, etc.).
Re: assertion style, I originally implemented ReUnit to use  expect true |> toEqual false, but quickly started to find it annoying and instead switched to an Expect module of assertions tests. see:  https://github.com/facebookincubator/immutable-re/blob/master/reUnit/src/ReUnit.rei#L18
Here are some examples in use: https://github.com/facebookincubator/immutable-re/blob/master/test/IterableTest.re#L21

I've zero experience with OUnit, I've just been told that's the thing to use. I have a hard time trusting code from a repo that throws TypeErrors at me though. I'm fine with rolling our own.
Also fine with either assertion style, though the reunit style does seem simpler to both implement and use. And it doesn't require an open. So maybe I should try that then :)


Add cornerPoints to text-recognition

What's New
This PR adds the cornerPoints attribute which is present in TextBlock, TextLine, and TextElement.
cornerPoints is useful if you want to draw accurate highlights over the block/line/element that follows the perspective in which the photo is taken.
Reference Documentation
iOS: https://developers.google.com/ml-kit/reference/ios/mlkittextrecognitioncommon/api/reference/Classes/MLKTextBlock#/c:objc(cs)MLKTextBlock(py)cornerPoints
Android: https://developers.google.com/android/reference/com/google/mlkit/vision/text/Text.TextBlock#getCornerPoints()
Testing
Built the example app, successfully compiled and ran the app on both iOS and Android, and logged the resulting result and saw that the cornerPoints attribute was indeed present in each block/line/element.

Thanks for submitting this PR! I'll look into it and review it in the upcoming days.


Ameerul / FEQ-2448 Refactor AvailableP2PBalanceModal

Used Modal component from deriv-com/ui
Refactored the styles

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.001%) to 85.447%

Totals

Change from base Build<PHONE_NUMBER>:
-0.001%

Covered Lines:
5322

Relevant Lines:
5784

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.001%) to 85.447%

Totals

Change from base Build<PHONE_NUMBER>:
-0.001%

Covered Lines:
5322

Relevant Lines:
5784

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.001%) to 85.447%

Totals

Change from base Build<PHONE_NUMBER>:
-0.001%

Covered Lines:
5322

Relevant Lines:
5784

💛  - Coveralls


Expose metrics to Prometheus

A common set of Camel-K related metrics could be exposed to Prometheus for monitoring purpose.
Besides, It would be cool if it'd be possible to define some custom Prometheus metrics, directly in the custom resource.
Problably the JMX Prometheus Java agent would have to be enabled (configurably) and fragments would look like:
rules:
  - pattern: 'fis.metrics<name=os.(.*)><>(.+):'
    name: os_$1
    help: some help

  - pattern: 'org.apache.camel<context=camel, type=routes, name=\"(.*)\"><>LastProcessingTime'
    name: camel_last_processing_time
    help: Last Processing Time [milliseconds]
    type: GAUGE
    labels:
      route: $1

The Prometheus trait has been created and should be available in next release (a priori 0.3.0).


Webpack 3 docs confused

Note: for support questions, please use one of these channels: Chat: AngularClass.slack or Twitter: @AngularClass

I'm submitting a ...
[ *] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Do you want to request a feature or report a bug?
Problems with dependencies requiring webpack 3, but despite the docs the package.json shows the project is build with webpack2.x

What is the current behavior?

Here is what happens: Installing preload-webpack-plugin ^1.2.2 as set in package json, actually installs 1.2.3 which has a breaking change of having webpack 3.2 as peer dependency instead of webpack 2.x.

What is the expected behavior?

upgrade webpack to v3, or fix the version of preload-webpack-plugin

What is the motivation / use case for changing the behavior?

webpack 2 is outdated and unsupported

Please tell us about your environment:

Angular version: 4.3
Browser: not browser related

thanks, the repo has been updated to webpack 3


Add Check Attribute(s) Instructions (Upload)

Add instructions for user that say:
"Is this (are these) the correct URI(s) for the Attribute(s) you have in your Excel file?"
Followed by a list of [Attribute Label(s) returned by the backend API]
"If it is (these are) not the correct URI(s), please type the correct URI(s) in the corresponding text boxes"
Time estimate: 1D
Check story #36 for more details/context.

Done.