[FP]: org.apache.jackrabbit/oak-segment-tar is mistaken for node-tar

Package URl
<EMAIL_ADDRESS>CPE
cpe:2.3:a:apache:jackrabbit:1.42.0:*:*:*:*:*:*:*, cpe:2.3:a:apache:jackrabbit_oak:1.42.0:*:*:*:*:*:*:*, cpe:2.3:a:tar_project:tar:1.42.0:*:*:*:*:*:*:*
CVE
CVE-2021-32803, CVE-2021-32804
ODC Integration
{"label"=>"Maven Plugin"}
ODC Version
7.4.3
Description
No response

Not reproducible as can be seen in the report.

It links only to the jackrabbit CPEs surfacing only CVE-2015-1833, a valid CVE for jackrabbit < 2.0.6 at first glance. There is no trace of linkage against the NPM tar package CPE

Mh. I already disabled node and yarn analyzer (because of other reasons), why would there even be an npm match.
Will try to reproduce in a smaller environment tomorrow

It's likely some other package than pkg:maven/org.apache.jackrabbit/oak-segment-tar that is linked to npm tar in your project. From the automated run that a false-positive report triggers it's clear that v7.4.3 does not link that library to the npm tar package CPE (or it's CVEs)

The complete logged result was
oak-segment-tar-1.42.0.jar<EMAIL_ADDRESS>cpe:2.3:a:apache:jackrabbit:1.42.0:*:*:*:*:*:*:*, cpe:2.3:a:apache:jackrabbit_oak:1.42.0:*:*:*:*:*:*:*, cpe:2.3:a:tar_project:tar:1.42.0:*:*:*:*:*:*:*) : CVE-2021-32803, CVE-2021-32804
Therefore, I thought oak-segment-tar was the culprit. However, pulled out into a minimal project, I can't currently reproduce it either. I'll close here for now, maybe I'll find the problem eventually.


Expandable row

I add a ExpandRow function, now we can add our customize component as expand component by set enableExpand=true in <BootstrapTable>.

@droyuki, that's cool. I'll check this out. Thanks your contribution :)

@droyuki, I did some patchs on your PR and released on v2.6.0. Thank your contribution 👍
Following is the differences that I did, please check the commits between  Nov 25 and 26, 2016
https://github.com/droyuki/react-bootstrap-table/compare/expandRow...AllenFang:droyuki-expandRow


Removed use of tempArray

After updating my project to<EMAIL_ADDRESS>I experienced strange issue where position of handles would be wrong on initial load. After debugging I determined the issue is caused by re-use of tempArray to generate some arrays. As far as I know react uses simple object equality === when detecting changes of props and state. Because the array was re-used in some cases react would fail to detect changes in style object.

This fixes a bug when upgrading to React 16. Any chance of getting this merged?
The re-use of tempArray seems like an unnecessary optimisation anyway.

@mpowaga Hi, would it be possible to merge this fix? Because it is critical for supporting React 16.

The same issue has been solved in #121 but thanks for sending this PR @lukashlavacka!


Google.Cloud.Speech communication over grpc fails when using proxy server

When using the google api for speech recognition in an intranet that forces communication through a proxy server, the requests of the SpeechClient (Google.Cloud.Speech.V1) fail. The reason seems to occur in the grpc framework wich is responsible for the communication.
Interestingly, using the speech recognition in combination with an prior upload of the audio file to the google storage shows that the StorageClient (Google.Cloud.Storage.V1) takes care of the proxy setting.
If you define the proxy for this process via the "System.Net.WebRequest.DefaultWebProxy" Property, the Rest Api used by the StorageClient will respect this setting for the storage requests.
The SpeechClient (and maybe all APIs relying on grpc) are currently ignoring this setting. Is there a workaround? Tried to use some grpc known environment-variables but without success.

I wouldn't expect this to be anything that the client library has to do - I'd expect Grpc.Core to take care of this appropriately. I don't even know where I'd set a proxy in gRPC. Could I suggest you file an issue on https://github.com/grpc/grpc?

Ok, thank you - i will do that and keep this post updated for other people researching this problem.

If you could just link to the new gRPC issue from here, I think that'll be fine - folks can subscribe to that one easily enough. I'll close this issue here now.

I wouldn't expect this to be anything that the client library has to do - I'd expect Grpc.Core to take care of this appropriately. I don't even know where I'd set a proxy in gRPC. Could I suggest you file an issue on https://github.com/grpc/grpc?

have you got the solution for how to setup gRPC proxy? we are also trying to set up the same but couldn't find how to establish it. we have a simple server client connection with gRPC and need to establish the gRPC proxy server.

@MachauGames: It sounds like you're not actually using the Google Cloud .NET libraries - in which case this isn't really a suitable repo in which to ask for advice. You might want to create a new issue in https://github.com/grpc/grpc-dotnet, with a lot more details than you provided here.

@MachauGames This repo is for Google Cloud .NET Client Libraries.
If you are using gRPC directly, possibly Grpc.Core (https://github.com/grpc/grpc) or Grpc.Net.Client (https://github.com/grpc/grpc-dotnet), it's best if you file an issue directly with them.
Note there's a known issue for Grpc.Net.Client (https://github.com/grpc/grpc-dotnet/issues/1832) that although fixed, is yet to be released.
If you are using Google Cloud .NET Client Libraries, pleaese create a new issue, specifying which library and which version of the library you are using, which .NET version you are targetting, etc. But possibly, first go through #8834 which contains most of the relevant information.


$virus

Coverage increased (+2.2%) to 86.047% when pulling 6ed18a0a7d1ae2d81aaecd5e847d39cbeb5d8e28 on develop into 8150ca1e09afdc3cbb2cdcb78c8a45bc1a6f65c1 on master.


option qt5.platformTheme = "kde" breaks several packages

Describe the bugQSystemTrayIcon::setVisible: No Icon set
the following applications are broken due to repeatedly logging QSystemTrayIcon::setVisible: No Icon set:

kotatogram-desktop
flameshot
nheko (but only with a more complicated setup it seems)
vlc media player

the following applicatons just SEGVAULT:

krita

Steps To Reproduce
Steps to reproduce the behavior:

use the following minimal configuration.nix:

{config, pkgs, ...}:i
{
    imports = [ ./hardware-configuration.nix ];

    # bootloader TODO change this to fit your machine
    boot.loader.grub = {
        enable = true;
        device = "/dev/vda";
        useOSProber = true;
    };

    # networking
    networking.hostName = "nixos";
    networking.networkmanager.enable = true;

    # localization
    time.timeZone = "Europe/Berlin";
    i18n.defaultLocale = "en_US.UTF-8";
    console.keyMap = "us";

    # Xorg
    services.xserver = {
        enable = true;
        layout = "us";
        displayManager.sddm.enable = true;
        windowManager.i3.enable = true;
        # TODO try other wm's, i think i had the problem on hyprland with waybar a while ago too, but i gotta test this properly
        # desktopManagers i tried all clashed with platformTheme = "kde"
    };

    # user
    users.users.alice = {
        isNormalUser = true;
        extraGroups = [ "wheel" ];
        password = "123";
    };
    users.users.root.password = "123";

    # packages to test the bug
    environment.systemPackages = with pkgs; [
        # alternative tray
        trayer
        # don't work with tray running
        kotatogram-desktop
        flameshot
        nheko
        vlc
        # segvaults
        krita
    ];

    # qt the bug
    qt5 = {
        enable = true;
        platformTheme = "kde";
    };

    system.stateVersion = "22.11";
}

login into i3, i3bar should have a tray running by default
open xterm with alt + enter
try to run the problematic applications

you can also try the other tray application with pkill i3bar; trayer
you can also edit qt5.platformTheme to e.g "gnome" and see, that the applications work.
Expected behavior
Applications launch normally. Tray works.
Notify maintainers
@romildo @worldofpeace

Can anyone reproduce this on their machine?
Can anyone find more applications that have the same problem?

i added vlc

ok, so the tray problem seems to not occur on sway with waybar, but krita still segfaults

For me setting qt.platformTheme = "gnome" does break things as well (libreoffice-qt, VirtualBox).

Bumping this issue

Flameshot has issues when copy-to-clipboard (otherwise works)
VLC segfaults still

My current workaround, in my home-manager setup, is to set qt.platformTheme = null; (the default) .
 Why this works, I haven't fully investigated. But the module definition is here:
https://github.com/nix-community/home-manager/blob/master/modules/misc/qt.nix


In AppBar adding an option of Slides

if this is a valid code update i can work on this

yeah works


config file's self directory

Can't cope with setting feri-config.js parameter path.source/destination to its root (meaning where config file self is located). Weird thing i've tried out
'./',  '.',  '/',  ''
but none worked.

First, i hate to think that project's heading towards abandonment - too useful a tool )).
Actually feri-config.js lives in between my_defined_src & my_defined_dest. But my_defined_dist is not fully mine (use it inside symphony-2 project) and there are few other files/folders already existing which don't (and can't too) want to wipe out and therefore need ways for more precise definition of what & where to be compiled - most importantly - without touching other possible folders inside dest

And i wonder if the following config lines are applicable for purposes above:
//     feri.config.glob.watch.source = 'pages/theme/**/.{css,js}'
//     feri.config.glob.clean = 'assets/.{css,js}'
//     feri.config.glob.build = 'pages/theme/*.concat' // concat file combines few other assets another level down // the hierarchy - works ok
// To be substitute for either replace following lines:
feri.config.option.clean      = true
feri.config.option.build      = true
feri.config.option.watch      = true
// paths
feri.config.path.source = "pages/theme"
feri.config.path.dest   = "assets"
Pardon me for dummy questions, i'm not really good at this sort of tools but i believe that's all i'm gonna need to figure out for my basic tasks. Grunt and gulp seems too redundant

I update Feri every so often (few months) to bring in the latest dependencies. Bug fixes as needed of course.
Long term, I want to rewrite Feri to use Async/Await and remove more dependencies. That is not likely to happen until 2019 or beyond though.

A core concept of Feri is that the destination (or dest) folder is expected to be completely expendable at all times. Any files that need to get published to dest should live in the source directory. There are Feri options that will completely destroy the dest folder for things like a republish so keeping anything valuable in the dest folder is dangerous.
feri.config.glob.watch.source is only useful if you are using Feri in watch mode. If you are, setting this will allow you to choose which files trigger a build from source to dest. https://github.com/ForestMist/feri/blob/master/docs/api/config.md#configglobwatchsource
feri.config.glob.clean is useful if you only want to delete certain file extensions from the destination directory. Since Feri can delete your entire destination folder under certain circumstances, I would not recommend trying to use this to protect certain files in your destination folder. https://github.com/ForestMist/feri/blob/master/docs/api/config.md#configglobclean
feri.config.glob.build is useful if you want to restrict Feri so it only builds certain file extensions in source and outputs those to dest. https://github.com/ForestMist/feri/blob/master/docs/api/config.md#configglobbuild

Closing this issue since I like the current rules about where config files can be located.
Netlancer whether Feri ends up being a valid solution for you or not, thanks for trying it. :)


Setup .ston files and required items for FFI import

Closes #37

Hey, quick note cause I just saw this in my mails: your approach is a nice way to solve this, the recommended way of specifying dependencies is actually in this way:
https://github.com/hpi-swa-lab/tools-interactive-simulations/blob/9353eec66c3871e45a78c7f2b4bd2084f15c4bbd/packages/BaselineOfECS.package/BaselineOfECS.class/instance/baseline..st#L8
(if you have troubles with the package not being found, maybe also try this where they specify the exact URL to find the package: https://github.com/hpi-swa-teaching/Snarl/blob/36bb0472c498a16c91eecfacf59f801d591c588d/packages/BaselineOfProject10.package/BaselineOfProject10.class/instance/baseline..st )
You should already have a BaselineOfTelegramClient in your app's sources that smalltalkCI will use to install your app. This is also the way users would usually go about installing the app, so it's definitely worth considering this way instead of the preload. Did you find the preload solution recommended anywhere or did you come up with it yourselves?

@tom95 I saw it online after googeling for a while. I changed it to the recommended approach. You would not by chance also have a recommendation for including binary dependencies? Due to our reliance on the Telegram C client we have to ship binaries for every platform, which we simply did by copying them into our local squeak image. Is a mechanism in place for this as well?
Regards
Niklas

That's gonna be a bit more tricky. Pharo (a different Smalltalk version) has a support package for it, from where you could probably salvage some code of you want to go for the "big solution".
This is how they use it:
https://github.com/ronsaldo/abstract-gpu/blob/e501f904e8e41d8ba730c14a1d75bcc3374ced5b/tonel/AbstractGPU-CorePharo/AGPUCBindingsBase.class.st
Here is how they find a path to download the native file to: https://github.com/ronsaldo/phanapi/blob/master/tonel/PhaNAPI-Core/PhaNAPI.class.st#L54
The workflow is essentially this: dynamic libraries for each platform are available on bintray. The first time an FFI call is sent in Smalltalk, we check if it's already been used, otherwise if the file already exists, otherwise we try to download it. Then we can proceed.
You could probably also write to the swt slack channel and ask if someone has a recommendation on how to handle external file downloads for this type of dependency, there might prior art I'm unaware of :)


Automate deployment in CloudRun environment

REQUIREMENTS

[x] Be compliant with Hangar way of working.

SUBTASKS

[x] Automate deployment in CloudRun environment in Google Cloud
[ ] #240

esperamos que el package está claro


Improve Identity Metrics and Data Docs

[ ] Connecting with Matt Kim (PM data services) on their roadmap


fix type error in eq() call

At least for my setup (torch 1.0.1, numpy 1.15.4) this is needed.

Sorry, but the code is currently compatible with PyTorch 0.4.0 (see Requirements). I will hopefully try to move it over to 1.0.1 soon.


Estimated release dates need update

The estimated release dates listed in this page are in the past, should probably be updated.
https://docs.microsoft.com/en-us/power-bi/admin/service-premium-what-is#limitations-in-premium-gen2

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 18013a6f-b02d-30d4-3b6d-93295624f352
Version Independent ID: e307e1d7-e565-8742-e563-86d596d7d1e1
Content: What is Microsoft Power BI Premium? - Power BI
Content Source: powerbi-docs/admin/service-premium-what-is.md
Service: powerbi
Sub-service: powerbi-premium
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Hi @chrisweis ,
Thank you for your suggestion.  We've made the update and set the article to republish.
All the best,
The DOCS team


Should fix when the device is in sleep mode

Hello.
I have a problem when my laptop is in sleep, after waking up I see an error connecting to the Internet. I found out that when this condition is met,

  if ({{ $ageCheckInterval }} ) {
            setInterval(function () {
                if (new Date() - lastCheck >= {{ $ageCheckInterval + $ageThreshold }}) {
                    location.reload(true);
                }
            }, {{ $ageCheckInterval }});
     }

my page starts to reload, but since the laptop is in sleep mode, then it does not have access to the Internet, respectively.
I found a solution to this problem in correcting this part of the code

if ({{ $ageCheckInterval }} > 0) {
    setInterval(function () {
        if (new Date() - lastCheck >= {{ $ageCheckInterval + $ageThreshold }}) {
            setTimeout(function () {
                location.reload(true);
            },  Math.max(0, {{ $ageCheckInterval }} - 500) )
        }
    }, {{ $ageCheckInterval }});
}

When I added setTimeout I stopped getting infinite page reload and further connection error. Now my page reloads when my laptop wakes up.

This should now be in the latest release.


RTSP connection lost: [Errno 104] Connection reset by peer

Hello! I am trying to use my Eufy 2 pro cameras via RTSP, but the stream keeps crashing with this error:
Logger: homeassistant
Source: /usr/src/homeassistant/homeassistant/runner.py:100
First occurred: 21:50:48 (35 occurrences)
Last logged: 22:17:23

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 854, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
ConnectionResetError: [Errno 104] Connection reset by peer

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

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiortsp/rtsp/reader.py", line 97, in run_stream
    async with RTSPMediaSession(conn, self.media_url, transport=transport, logger=self.logger) as sess:
  File "/usr/local/lib/python3.10/site-packages/aiortsp/rtsp/session.py", line 66, in __aexit__
    await self.teardown()
  File "/usr/local/lib/python3.10/site-packages/aiortsp/rtsp/session.py", line 154, in teardown
    resp = await self._send('TEARDOWN')
  File "/usr/local/lib/python3.10/site-packages/aiortsp/rtsp/session.py", line 165, in _send
    return await self.connection.send_request(method, url or self.media_url, headers)
  File "/usr/local/lib/python3.10/site-packages/aiortsp/rtsp/connection.py", line 278, in send_request
    resp = await asyncio.wait_for(self.active_requests[cseq], timeout or self.default_timeout)
  File "/usr/local/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
    return fut.result()
aiortsp.rtsp.errors.RTSPConnectionError: RTSP connection lost: [Errno 104] Connection reset by peer

And such errors in WebRTC camera card.

Logger: custom_components.eufy_security
Source: custom_components/eufy_security/eufy_security_api/web_socket_client.py:86
Integration: Eufy Security ([documentation](https://github.com/fuatakgun/eufy_security), [issues](https://github.com/fuatakgun/eufy_security/issues))
First occurred: 09:31:45 (2 occurrences)
Last logged: 09:41:45

Unexpected error fetching eufy_security data:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 239, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 195, in _async_update_data
    return await self.update_method()
  File "/config/custom_components/eufy_security/coordinator.py", line 85, in _update_local
    await self._api.poll_refresh()
  File "/config/custom_components/eufy_security/eufy_security_api/api_client.py", line 160, in poll_refresh
    await self._send_message_get_response(OutgoingMessage(OutgoingMessageType.poll_refresh))
  File "/config/custom_components/eufy_security/eufy_security_api/api_client.py", line 343, in _send_message_get_response
    await self.send_message(message.content)
  File "/config/custom_components/eufy_security/eufy_security_api/api_client.py", line 352, in send_message
    await self._client.send_message(json.dumps(message))
  File "/config/custom_components/eufy_security/eufy_security_api/web_socket_client.py", line 86, in send_message
    raise WebSocketConnectionError()
custom_components.eufy_security.eufy_security_api.exceptions.WebSocketConnectionError

Also getting the Unexpected error fetching eufy_security data: log and wrong response on DESCRIBE in webrtc card.

Same issue here using a Indoor Cam Pan&Tilt 2K.
Logger: homeassistant.components.stream.stream.camera.kids_bedroom
Source: components/stream/init.py:434
Integration: Stream (documentation, issues)
First occurred: July 9, 2023 at 4:07:55 PM (113 occurrences)
Last logged: 8:43:06 PM
Error from stream worker: Stream ended; no additional packets
Error from stream worker: Error opening stream (HTTP_NOT_FOUND, Server returned 404 Not Found) rtsp://<IP_ADDRESS>/live0
Error from stream worker: Error demuxing stream: [Errno 110] Operation timed out: 'rtsp://<IP_ADDRESS>/live0'

FYI, I timed it today and noticed that this happens after exactly 5 mins of streaming. I created an automation that turns the camera off the on again every 5 minutes. It works but it's an annoying workaround, especially since I use my camera as a baby monitor (turning the camera off and on exits fullscreen).

probably the same issue, but different exception source:
 2023-08-19 22:55:51.700 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
 Traceback (most recent call last):
   File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 989, in _read_ready__data_received
     data = self._sock.recv(self.max_size)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 ConnectionResetError: [Errno 104] Connection reset by peer

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

 Traceback (most recent call last):
   File "/usr/local/lib/python3.11/site-packages/aiortsp/rtsp/reader.py", line 97, in run_stream
     async with RTSPMediaSession(conn, self.media_url, transport=transport, logger=self.logger) as sess:
   File "/usr/local/lib/python3.11/site-packages/aiortsp/rtsp/session.py", line 66, in __aexit__
     await self.teardown()
   File "/usr/local/lib/python3.11/site-packages/aiortsp/rtsp/session.py", line 154, in teardown
     resp = await self._send('TEARDOWN')
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   File "/usr/local/lib/python3.11/site-packages/aiortsp/rtsp/session.py", line 165, in _send
     return await self.connection.send_request(method, url or self.media_url, headers)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   File "/usr/local/lib/python3.11/site-packages/aiortsp/rtsp/connection.py", line 278, in send_request
     resp = await asyncio.wait_for(self.active_requests[cseq], timeout or self.default_timeout)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   File "/usr/local/lib/python3.11/asyncio/tasks.py", line 479, in wait_for
     return fut.result()
            ^^^^^^^^^^^^
 aiortsp.rtsp.errors.RTSPConnectionError: RTSP connection lost: [Errno 104] Connection reset by peer

Exact same problem here.
Homeassistant logs :
2023-10-22 00:54:34.744 INFO (MainThread) [aiortsp.rtsp.reader] try loading stream rtsp://<IP_ADDRESS>/live0
2023-10-22 00:54:34.750 INFO (MainThread) [aiortsp.rtsp.reader] connected!
2023-10-22 00:54:34.751 INFO (MainThread) [aiortsp.rtsp.reader] receiving interleaved RTP (0) and RTCP (1)
2023-10-22 00:54:34.754 INFO (MainThread) [aiortsp.rtsp.reader] session options: {'TEARDOWN', 'SETUP', 'PLAY', 'DESCRIBE', 'GET_PARAMETER', 'OPTIONS'}
2023-10-22 00:54:34.758 INFO (MainThread) [aiortsp.rtsp.reader] connection to RTSP server <IP_ADDRESS>:554 closed (error: None)
2023-10-22 00:54:35.262 INFO (MainThread) [aiortsp.rtsp.reader] try loading stream rtsp://<IP_ADDRESS>/live0
2023-10-22 00:54:35.268 INFO (MainThread) [aiortsp.rtsp.reader] connected!
2023-10-22 00:54:35.269 INFO (MainThread) [aiortsp.rtsp.reader] receiving interleaved RTP (0) and RTCP (1)
2023-10-22 00:54:35.273 INFO (MainThread) [aiortsp.rtsp.reader] session options: {'TEARDOWN', 'SETUP', 'PLAY', 'DESCRIBE', 'GET_PARAMETER', 'OPTIONS'}
2023-10-22 00:54:35.276 INFO (MainThread) [aiortsp.rtsp.reader] connection to RTSP server <IP_ADDRESS>:554 closed (error: None)
2023-10-22 00:54:35.780 INFO (MainThread) [aiortsp.rtsp.reader] try loading stream rtsp://<IP_ADDRESS>/live0
2023-10-22 00:54:35.785 INFO (MainThread) [aiortsp.rtsp.reader] connected!
2023-10-22 00:54:35.786 INFO (MainThread) [aiortsp.rtsp.reader] receiving interleaved RTP (0) and RTCP (1)
2023-10-22 00:54:35.789 INFO (MainThread) [aiortsp.rtsp.reader] session options: {'TEARDOWN', 'SETUP', 'PLAY', 'DESCRIBE', 'GET_PARAMETER', 'OPTIONS'}
2023-10-22 00:54:35.795 INFO (MainThread) [aiortsp.rtsp.reader] setting up using URL: rtsp://<IP_ADDRESS>/live0/trackID=0
2023-10-22 00:54:35.798 INFO (MainThread) [aiortsp.rtsp.reader] stream correctly setup: <Response status=200 msg="OK"" headers={'cseq': '3', 'transport': 'RTP/AVP/TCP;unicast;destination=<IP_ADDRESS>;source=<IP_ADDRESS>;interleaved=0-1', 'session': '123456902'} content-length=0>
2023-10-22 00:54:35.799 INFO (MainThread) [aiortsp.rtsp.reader] session id: 123456902, timeout: 60, keep_alive: 54
2023-10-22 00:54:35.799 INFO (MainThread) [aiortsp.rtsp.reader] playing stream...
2023-10-22 00:54:35.799 INFO (MainThread) [aiortsp.rtsp.reader] start playing rtsp://<IP_ADDRESS>/live0 at time `now` and speed `1`...
2023-10-22 00:54:35.834 INFO (MainThread) [aiortsp.rtsp.reader] stopping stream...
2023-10-22 00:54:35.834 INFO (MainThread) [aiortsp.rtsp.reader] stopping session/playback...
2023-10-22 00:54:35.890 INFO (MainThread) [aiortsp.rtsp.reader] connection to RTSP server <IP_ADDRESS>:554 closed (error: [Errno 104] Connection reset by peer)
2023-10-22 00:54:35.890 INFO (MainThread) [aiortsp.rtsp.reader] connection closed, error: RTSP connection lost: [Errno 104] Connection reset by peer
2023-10-22 00:59:07.475 ERROR (stream_worker) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 989, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionResetError: [Errno 104] Connection reset by peer

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

Traceback (most recent call last):
  File "/config/deps/lib/python3.11/site-packages/aiortsp/rtsp/reader.py", line 97, in run_stream
    async with RTSPMediaSession(conn, self.media_url, transport=transport, logger=self.logger) as sess:
  File "/config/deps/lib/python3.11/site-packages/aiortsp/rtsp/session.py", line 66, in __aexit__
    await self.teardown()
  File "/config/deps/lib/python3.11/site-packages/aiortsp/rtsp/session.py", line 154, in teardown
    resp = await self._send('TEARDOWN')
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/deps/lib/python3.11/site-packages/aiortsp/rtsp/session.py", line 165, in _send
    return await self.connection.send_request(method, url or self.media_url, headers)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/deps/lib/python3.11/site-packages/aiortsp/rtsp/connection.py", line 278, in send_request
    resp = await asyncio.wait_for(self.active_requests[cseq], timeout or self.default_timeout)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/asyncio/tasks.py", line 479, in wait_for
    return fut.result()
           ^^^^^^^^^^^^
aiortsp.rtsp.errors.RTSPConnectionError: RTSP connection lost: [Errno 104] Connection reset by peer
2023-10-22 00:59:39.808 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.camera_salon] Error from stream worker: Stream ended; no additional packets
2023-10-22 00:59:49.826 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.camera_salon] Error from stream worker: Error opening stream (HTTP_NOT_FOUND, Server returned 404 Not Found) rtsp://<IP_ADDRESS>/live0
2023-10-22 01:00:09.844 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.camera_salon] Error from stream worker: Error opening stream (HTTP_NOT_FOUND, Server returned 404 Not Found) rtsp://<IP_ADDRESS>/live0
2023-10-22 01:00:39.855 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.camera_salon] Error from stream worker: Error opening stream (HTTP_NOT_FOUND, Server returned 404 Not Found) rtsp://<IP_ADDRESS>/live0
2023-10-22 01:01:19.869 ERROR (stream_worker) [homeassistant.compo

Go2rtc logs:
00:54:54.917 INF [streams] create new stream url=rtsp://<IP_ADDRESS>/live0
00:54:54.921 INF [streams] create new stream url=rtsp://<IP_ADDRESS>/live0
00:55:36.909 INF [streams] create new stream url=rtsp://<IP_ADDRESS>/live0
00:55:36.911 INF [streams] create new stream url=rtsp://<IP_ADDRESS>/live0
00:59:28.686 INF [streams] create new stream url=rtsp://<IP_ADDRESS>/live0
00:59:28.686 INF [streams] create new stream url=rtsp://<IP_ADDRESS>/live0
00:59:39.744 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp <IP_ADDRESS>:43760-><IP_ADDRESS>:554: i/o timeout" url=rtsp://<IP_ADDRESS>/live0
00:59:39.744 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp <IP_ADDRESS>:39974-><IP_ADDRESS>:554: i/o timeout" url=rtsp://<IP_ADDRESS>/live0
01:01:10.358 INF [streams] create new stream url=rtsp://<IP_ADDRESS>/live0
01:01:10.361 INF [streams] create new stream url=rtsp://<IP_ADDRESS>/live0
01:01:10.525 INF [streams] create new stream url=rtsp://<IP_ADDRESS>/live0
01:01:10.831 ERR github.com/AlexxIT/go2rtc/internal/mjpeg/init.go:166 > error="streams: wrong response on DESCRIBE"
01:01:44.159 INF [streams] create new stream url=rtsp://<IP_ADDRESS>/live0
01:01:44.160 INF [streams] create new stream url=rtsp://<IP_ADDRESS>/live0
01:01:44.337 INF [streams] create new stream url=rtsp://<IP_ADDRESS>/live0
01:01:44.635 ERR github.com/AlexxIT/go2rtc/internal/mjpeg/init.go:166 > error="streams: wrong response on DESCRIBE"
01:02:31.417 INF [streams] create new stream url=rtsp://<IP_ADDRESS>/live0
01:02:31.424 INF [streams] create new stream url=rtsp://<IP_ADDRESS>/live0
01:02:31.589 INF [streams] create new stream url=rtsp://<IP_ADDRESS>/live0
01:02:31.900 ERR github.com/AlexxIT/go2rtc/internal/mjpeg/init.go:166 > error="streams: wrong response on DESCRIBE"

I don't even know if this is a problem related to the integration or to the camera itself.

@Guerric-P , original RTSP stream is managed by the hardware but not the integration. For some reason, sometimes, the stream is not accessible and all the consumers are not happy with it but I can do nothing about strength of hardware supported RTSP stream.


Location tracking in background, location watcher is not detecting location changes.

is there a detailed documentation for location's tracking in background?
there are several closed issues about it but it's not clear if the solutions are within the plugin or should i write a separate code?
Which platform(s) does your issue occur on?

Both
iOS >10
Android >7
device

Hey @karo-dc, the entire documentation of the plugin is in the README file.
Regarding tracking in background on Android, refer this file.
For iOS, there is an option iosAllowsBackgroundLocationUpdates, documented here.
This issue comment  could give you other hints as well.
Hope this helps!


Allow List param to have MinValue, MaxValue

AWS CloudFormation validates the List Number parameter value as numbers.
See:

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/parameters-section-structure.html

Hi, is there anything wrong about the PR?


Version 3 release schedule

when will version 3 release?

There isn't a firm release schedule, so unfortunately the best answer I can give is "when it's done." That being said, almost all of the new functionality is already implemented – most of the remaining work will just be bug fixes. Depending on when I get time to work on Jockey, the next beta release should be out by the middle of May, but I don't have a timeline in mind for the stable 3.0 release.


fix: update color

:tada: This PR is included in version 1.2.11 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Our DB is missing in dev branch. I will get my local copy and update it.

I think this might have been when @Itebbs2 tried to resolve conflict. So without replacing it, you might have just deleted it? Can you please check if you have a db in ur branch.

There is a db in the patient space that is merging into it. It will be replaced when approved?


chore: Modified logging context to have only requestId and userEmail

Description
We're modifying the response headers to not hold any info on context, and the logging pattern to only display requestId, userEmail, traceId and spanId.
Automation
/ok-to-test tags=""
:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

/build-deploy-preview skip-tests=true


Effect of the incorrect joint origin position in URDF?

Hello !
Explain the situation:
I just got the new robot arm series 6-550 and I'm working on setting up the manipulator arm for the pick-and-place task, so I need to start working for the environment around the robot arm because I will be using the MoveIt for motion planning and its functionality for my application.
But I noticed that the joint origin position for each link is not at the correct position (in this case, it should have been at the rotated joint position, but it is not). I have compared the URDF provided by the company with the panda robot URDF from moveit tutorial site. The panda robot's joint origin position shows out to be correctly positioned.
I have posted the image to compare between the utra 6-550 and panda robot URDF in this link
My question is:
If the joint origin position of each link is not at the rotated joint for the manipulator arm, what could be the effect/problem when using the motion planning in MoveIt?
If more information is needed or words are not clear, please let me know
Thank you in advanced !

HI gmp-prem.
We did make some simplification of the model, and this simplification is not affected by using moveit, the display is normal, and the kinematics of using moveit is also fine. However, there are some differences, some plugins need to use urdf files to automatically parse the relevant data may have problems: ikfast decoding urdf may not be able to parse.
Thanks for your feedback, we'll spend some time re-optimizing this bug later.
@gmp-prem

Hi !
Thanks for replying the issue.
If I have further question, I will create the issue
For now, I'm going to close this issue
Thank you !


Automatically set updates quotas

When booting up, the merchant requests the marketplace quotas and sets its update interval accordingly.
Please be aware, that we only request the quota on bootup of the merchant. Later changed quotas might crash the merchant.

@CarstenWalther: addressed your concerns.
Also, I found crashing the merchants when API limit was exceeded problematic. As this can potentially happen due to several reasons -- which would otherwise force us to use extremely conservatice update rates -- I added a simple sleep() of which I am not sure whether I really like it.
What do you think?

I also thought about the forwarding the timeout handling, but I could neither think of a decent way to do that (well,  there is but that a rather large rewrite) nor do I have to time to fix that now.

Whoops, I get an error here.
    return r['max_req_per_sec']
TypeError: 'Response' object is not subscriptable

Should be return r.json()['max_req_per_sec']


Set-Policy: An Example would be great especcialy how to set multiple permissions at once

az keyvault set-policy --name kv-name --certificate-permissions {backup, create} --upn<EMAIL_ADDRESS>does not work e.g

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 226e5769-f6c8-a480-db78-727fb96348ec
Version Independent ID: 8ee06a2a-6eda-11be-3c8e-6ad948be207e
Content: az keyvault
Content Source: src/azure-cli/azure/cli/command_modules/keyvault/_help.py
Service: key-vault
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

--certificate-permissions should be "space-separated list of certificate permissions to assign". Please test if this works:
az keyvault set-policy --name kv-name --certificate-permissions backup create --upn<EMAIL_ADDRESS>


List meta dependencies in meta packages

This one might be a little more controversial, but generally meta packages have little documentation. The only thing interesting is the list of packages, so we show them. I assume that no package.build_depends but existing package.exec_depends defines a meta package. Is that correct?
I changed the default --base-url value because I test existing packages with simply rosdoc2 build -p . and I wanted real meta packages to have links that could be tested. I tried it with 'soccer_interfaces' and it worked OK.

I assume that no package.build_depends but existing package.exec_depends defines a meta package. Is that correct?

Unfortunately, I don't think we can make that assumption.  Pure python packages, for instance, have no build_depends but exec_depends.  Further, I don't even think we can use build_type as ament_cmake to distinguish this case, as it is possible to have pure python packages that are installed via CMake.
We do have an existing tag called metapackage that packages can put in their export section.  But we do not enforce that flag is there, and in point of fact none of the core ROS 2 metapackages actually define that flag currently.

We have basically deprecated the metapackage as a formal designation. I think that the approach that we should look for on this is that the the full package.xml content is easily discoverable and viewable, independent of whether it's a package or a pseudo metapackge. The dependency list is just one element of that. The links added in #113 and the description in #112 are all getting the elements into the docs. Putting them all into a nice cohesive box that's moderately universal will be quite powerful. It could even be submitted to github to be rendered if we can keep it standalone in generating an rst or html block. And it would also be great if others who write a custom rst index etc can just do a directive like .. include_package_xml(./package.xml) kind of operation. And we can have that in the default template.

I have no problems including package.xml in the rosdoc2 output. I'd probably put in under "Standard Documents". I'll do a patch for that.
But I would still maintain that, for meta packages, it is useful to have a list of the included packages that can be easily clicked on to get to their documentation. Let me investigate a little more the possible ways that this could be detected, including looking at actual packages in use.
If there was a way to include this for most meta packages, even if it did not hit all of them, it could still be useful.

I did a review of packages that might be claiming to be meta packages (looking for 'meta' in package.description.lower(), and also matching "no package.build_depends but existing package.exec_depends". The additional common characteristic: all legitimate meta packages have no subdirectories, except 1: moveit also has a scripts directory. I'm going to look at packages that match that, but WITHOUT 'meta' in their description, to see how that looks.

Now reviewing a sampling of packages that do not have 'meta' in the description, but have no subdirectories (except perhaps 'doc'). The vast majority are legitimate meta packages (that is, a list of related packages that are part of a collection maintained by a single entity). A few are not meta packages of a larger collection, but include other packages. Examples:
vision_opencv: lists cv_bridge and image_geometry "Packages for interfacing ROS2 with OpenCV"
rosidl_runtime: action_msgs, service_msgs
moveit_resources: lists 5 moveit_resources_* packages, but also adds joint_state_publisher and robot_state_publisher
I'm going to modify the PR to match this plan.

Here we go with the subdirectory test. What's the downside to this? Maybe a handful of packages have their dependencies listed as a "meta package" when they are not true metapackages (if that even is well defined). For the vast majority of true metapackages, this adds useful documentation that should have links that can be followed by clicking.

I agree that this information would be useful. But I think that we shouldn't actually limit this to "meta" packages. ANd we're actively working to avoid using that as another official term. The dependencies are valuable to list and link for all packages not just meta-packages. We should think about how do we effectively render all the metadata about all the packages at in one compact format that is consistent.
One example where we're doing this that's been very successful is on the ROS wiki like this: https://wiki.ros.org/tf2

And we also have this information and more on ROS Index aka: https://index.ros.org/p/tf2/#rolling-overview
We can't currently get the full richness here because of the need for extra index information. But I think that we should look at creating a more homogeneous way to integrate this extra information. (Things like the reverse dependencies, and knowing if the links are alive, and the CI jobs. A lot of that information comes from the rosdistro.) And the version selector for generated docs, like our core docs and on the wiki and on index.ros.org would be highly valuable.

Rendering the raw xml like in #115 is a good first step. But lets do it in a way that's valid for all packages instead of specifically making up a heuristic for a meta package.

I count 62 packages in recent rolling that meet this definition of a meta package. The vast majority of those have no documentation except for the package.xml file. The vast majority of these are also clearly intended to be a meta package, in the sense that they are a collection of related packages, managed by a single entity, that can be deployed as a group.
So y'all may be avoiding the concept or name "metapackage" but it appears to me that this is a concept widely in use in existing packages. And I would argue that it is fundamentally different from other types of packages, where the dependencies are really more about what you need to make the package work, and after it is working (which is mostly a build issue), the package user doesn't really care about what the dependencies are.
rosindex has access to the distro, while so far rosdoc2 does not. The info in the distro would be valuable, but it requires an internet access step that so far rosdoc2 has avoided. But it might be needed in the future. We should probably discuss that issue independently of this meta dependency issue.
If you really don't like the word "meta" perhaps we could show execution dependencies when they exist. But I fear that would get confusing because people have been using the  tag that mixes issues.
I don't really have the standing or deep knowledge to push this perspective too strongly, but from what I have seen I think this should move forward. Reconsider but if you (or y'all) still don't like it, we can drop it.

I don't really have the standing or deep knowledge to push this perspective too strongly, but from what I have seen I think this should move forward. Reconsider but if you (or y'all) still don't like it, we can drop it.

So I think my big problem with the implementation here is that it is based on heuristics.  And given the thousands of packages that we have, those heuristics are inevitably going to be wrong for some subset of packages.
However, I do think that two good ideas have come out of this discussion: one is that we should show the dependencies of packages, and one is that metapackages are indeed a different "kind" of package.
For the first one, we have all of the metadata we need from the package.xml to display dependencies.  So I think we can just make a PR to add that information; mostly it is a problem on how to display it.
For the second one, I think that we should allow the user to opt-in to documenting a package as a metapackage.  That is, we add an option into rosdoc2.yaml (or similar) where a user can explicitly say that package so-and-so is a metapackage, and then we do special handling for it.  That way we will never inadvertently call something a meta-package when it isn't one, and users always have a way to "opt-out" by not including the metapackage flag in the configuration.  The downside here of course is that it isn't "automatic", and may be somewhat hard for users to discover, but I think that is preferable to heuristics.
Thoughts?

@clalancette Thanks for the input. I started to add some verbal comments, but it would be just as easy to prepare a revised PR that tries to respond to your concerns. I'll do that in the next couple of days.

I just saw this PR and read some of the feedback (but certainly not all) - but just wanted to note that I sort of manually did this for image_pipeline - https://docs.ros.org/en/rolling/p/image_pipeline/index.html - the side navigation was updated to jump to the individual packages (in a fairly hacky way I think), and the shared tutorials are in that package as they were on the old wiki

@mikeferguson Thanks for pointing out your work to me. Your work, particularly the 'fairly hacky way',  is actually fairly relevant to the issues I am facing with #137 I'm going to further comment there if you are interested.


Slider V2 does not recover from no results, breaks Instantsearch

I do not understand why the slider was replaced for V2. I could spend so many hours writing about the issues we run into with this alpha version of a slider that is unusable on a touch device if I would have the time.
Here is today's annoyance:
The slider does not recover if there are no results found in a search
Perfectly working example with V1: https://jsfiddle.net/rata5eeo/
Slider V1 works like a charm , type Sandra into the search box => No Results => Slider goes to min value and beautifully recovers if you type in eg Sarah or at least press backspace
Braindead V2 slider: https://jsfiddle.net/3xkz0vq1/
Type Sandra into the search box => Instantsearch breaks, no way to recover from no results. The page has to be reloaded.
No need to fix this bug, there are so many more, the slider is unusable. Please just replace it.

Thanks @mindbits for opening this issue. We'll work on it asap.


windows phone 8.1 long press

I have the problem that the long press triggers when I'm scrolling. This issue is also on windows phone 10.

I'm hoping you have set prevent-onscrolling="true". I've one windows phone 10 let me give it a try

Thx for the quick response. Yes I set it true.

Sorry for delayed response. Currently I don't have any windows 8 device and in windows 10 it was working fine . If you can point out any clue or event object it would be helpfull for me. Mean while I'm looking for event object type generated by windows 8.


Add a way to ignore CanceledError

What happened?
Following https://github.com/arthurfiorette/axios-cache-interceptor/issues/665
It doesn't seems to be solved, as I have this exact issue.
Is there a way to tell a-c-i to ignore CanceledError? Because currently if a request is cached but then the same request is done, but cancelled (because of react strict mode), the cache is deleted.
Also, it seems harmless to keep the cache associated to a request, when it's cancelled, regardless of react strict mode. What do you think?
Also thanks for this great library!
axios-cache-interceptor version
1.6.0
Node / Browser Version
N/A
Axios Version
1.7.2
What storage is being used
Memory Storage
Relevant debugging log output
N/A

Actually staleIfError is not called at all on cancelled request

Are you up to a PR?
remember to add unit tests :)


Boxed-list info rows

The projects tab shows these changes best, but the other tabs are also changed.
Before:

After:

The rows are no longer selectable/activatable, but the text inside them is selectable, so it is much easier to copy it. The asset description wasn't fully visible if it was over a certain length, which is fixed with these changes. The logs are much easier to scroll through since it expands all of them, instead of having a scroll window inside a scroll window. Even though this version takes up a bunch more space than before, I think the new rows improve legibility by a lot.
I'm not experienced with rust so it may be worth checking out the changes there for any programming war crimes. (the create_details_row function has been replaced by create_info_row and create_widget_row)
@aknarts This PR is mainly for you to get a look at and see if it breaks anything for the rewrite, not expecting it to get it merged right now.
(Also not sure why git counted 158 file changes)

I have just one question... why are there 158 modified files?:D

I'm guessing I've somehow accidentally changed chmod permissions from 644 to 755 (on every single file) :P
Found this blogpost, going to try to undo it now using his method, hopefully it won't make it worse


Add Newsletter Component to home page

Add the /components/Newsletter/Newsletter before the end of the Content div on the screens/Homepage/Homepage.js file

I think there's an issue preventing me from running the app currently-- noted in https://github.com/covid-projections/covid-projections/pull/145#issuecomment-602402419


PoC: ✨  authz: add warrants to default rule resolver

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/lgtm
/approve


Links direct to https

IMPROVE: Update links to https and update some redirected URLs

Thank You! 😇


fix(metrics): bound observers' value not been updated

Which problem is this PR solving?

bound observer's value not been updated, i.e. observer function not been called.

Short description of the changes

bound observers' observer result should be inherited from its original observer and been updated along with ObserverMetric.

Codecov Report

Merging #994 into master will decrease coverage by 21.00%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master     #994       +/-   ##
===========================================
- Coverage   94.90%   73.89%   -21.01%
===========================================
  Files         212       69      -143
  Lines        8676     1567     -7109
  Branches      791      270      -521
===========================================
- Hits         8234     1158     -7076
+ Misses        442      409       -33

Impacted Files
Coverage Δ

packages/opentelemetry-core/test/utils/url.test.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

...ckages/opentelemetry-core/test/platform/id.test.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

...pentelemetry-core/src/platform/node/performance.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

...pentelemetry-core/test/internal/validators.test.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

...ntelemetry-core/test/trace/NoRecordingSpan.test.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

...telemetry-core/test/platform/hex-to-base64.test.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

...elemetry-core/test/trace/spancontext-utils.test.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

...lemetry-core/test/trace/ProbabilitySampler.test.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

...try-core/test/trace/fixtures/test-package/index.js
0.00% <0.00%> (-100.00%)
:arrow_down:

...ry-api/test/noop-implementations/noop-span.test.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 142 more

This is not a bug as there should in fact be no concept of a "Bound Observer" according to the spec
https://github.com/open-telemetry/oteps/blob/master/text/0072-metric-observer.md#observer-calling-conventions

There is no equivalent of a "bound" observer instrument as there is with Counter, Gauge, and Measure instruments.

Closing this and opening an issue to remove the bound observer.


update coqPackages.mathcomp: 1.15.0 -> 1.160

Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Why was it closed ?

Wrong branch name (bad for keeping track on my side).
Reopened here #214024

git push -u my_fork mathcomp-1.16:mathcomp-1.17 so locally you have the right name without re opening PR


Blade: "if" highlighted without "@"

Fixed: https://github.com/tempestphp/highlight/releases/tag/2.9.0


Reformed: Profile/README.md

This pull request introduces the following changes:

A banner included at the start of the file.
A description about EddieHub organisation, Eddie's believes, and this place is welcome to all.
Links redirecting to Eddie's YouTube channel, Eddie's courses, raising issues for joining, Discord community.
A hello to the mascot - Hubber.
FAQs discussing 7 topics (redirect links included).

A preview of the reformed README.md can be seen on my forked repository for ease.

[x] Yes, I have read the Code Of Conduct.

Thank you for the reviews!

I don't think we need to add that much content to the org page.
+ For QnA, we have our support repo
Let see what other reviewers think about that :)

Agree with that

Looks good, I think there is too much in bold/big writing - I always recommend adding a small section at a time, so we can continually keep merging things in (little and often is better for you and the project)


Hyperparameters for results reproduction

I am trying to reproduce results for SplitCIFAR-100, I used the exact same hyperparameters mentioned in the code. I am getting average accuracy as 59.42, and forgetting as 6.41.
In the paper,average accuracy  is mentioned as 61.60.  Could you please provide hyperparameter settings for reproducing results?

I am sorry for misleading you for the default hyperparameter settings. There are several important hyperparameter settings in our experiments, including "--outer_iter" for outer optimization loops for sample weights, and "--inner_iter" for inner optimization loops for model parameters. We actually set "--outer_iter=10" for SplitCIFAR100 in our experiments rather than 5 default set in "main.py". You can find the details of hyperparameter setting in Table 7, page 20 (Appendix) of our paper. We use bilevel optimization algorithm to update the sample weights and model parameters, so the number of outer loops ("--outer_iter") and inner loops ( "--inner_iter") determines the selection of coresets and  the convergence results. The corresponding learning rates for inner and outer loops also have key impacts on the results. Our settings for theses hyperparameters may not be the best combinations, you could tune them carefully for your data and tasks. Another hyperparameter you should pay attention to is the "Q loops" (line 77 in bcsr_training.py), which is responsible for approximating the hessian-inverse-vector product. We set it to 3 by default, but feel free to tune it if necessary, typically less than 10.


The output time range from CALIPSO_L2_1km is weird.

Could anyone please confirm the code to extract time range attributes from CALIPSO_1km files? The code I'm talking about is at 'satellite_collocation/instrument.reader.py', Row 215, which is part of the function load_caliop_clayer1km_geoloc ():
So this is how I locate the problem. I used the function ir.load_caliop_clayer1km_geoloc() to read CALIPSO L2 data and the output time range is weird. Specifically, I input a CALIPSO granule with time range '2017-02-28T23:35:37 - 2017-03-01T00:02:59', but when I print the returned attribute 'Profile_Datetime', it prints date time ranges from 2017-02-28 to 2017-05-12. Here is the output:

array([datetime.datetime(2017, 2, 28, 23, 35, 37, 198520), datetime.datetime(2017, 2, 28, 23, 35, 37, 198520), ...,datetime.datetime(2017, 5, 12, 0, 2, 59, 198520), datetime.datetime(2017, 5, 12, 0, 2, 59, 198520)], dtype=object)

So I checked the code inside instrument.reader.py, and finally located at Row 215:
profile_deltas = (cal_utc - cal_utc[0]) * 3600. * 24.
As my understanding, we want to get how many days are past by the start date, and then transform it to seconds. However, it is wrong to calculate by (cal_utc - cal_utc[0]). For example, if the start date is 2017-02-28 and end date is 2017-03-01, then we will have:
cal_utc[-1]- cal_utc[0] =<PHONE_NUMBER>8008 -<PHONE_NUMBER>6943 = 72.01901065. And 72 days is wrong because actually, the time difference is only 1 day.
So the point is, the number before the decimal point and after the decimal point is not on the same scale, where the former is year-month-day and the latter is the percentage of a day.
Please let me know if my understanding is wrong or if this should be corrected. Thanks.

To provide better understanding, this is original code of Row 211 to Row 218:
      n_profile = cal_lon.shape[0]         prof_s = 0         prof_e = n_profile         profile_dts = list()         profile_deltas = (cal_utc - cal_utc[0]) * 3600. * 24.         for i_profile in range(0,n_profile):             profile_dt = cstart_dt + datetime.timedelta(seconds=int(profile_deltas[i_profile]))             profile_dts.append(profile_dt)
and I would like to replace it by:
n_profile = cal_lon.shape[0] prof_s = 0 prof_e = n_profile profile_dts = list() for i_profile in range(0,n_profile):     stime = datetime.datetime.strptime(str(int((cal_utc[0] + 20000000.))),'%Y%m%d')     current_time = datetime.datetime.strptime(str(int((cal_utc[i_profile] + 20000000.))),'%Y%m%d')     profile_delta = ((current_time - stime).days + (cal_utc[i_profile]%1 - cal_utc[0]%1)) * 3600. * 24.     profile_dt = cstart_dt + datetime.timedelta(seconds=int(profile_delta))     profile_dts.append(profile_dt)


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/155 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit ac15f17:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-10-09-08-58-45 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-10-09-08-58-45

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add a check for updated version before deployment

Description
"Successful" run: https://github.com/paulbalandan/CodeIgniter4/actions/runs/3369749982/jobs/5589787478
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[ ] Conforms to style guide

If we are going to follow Semantic Versioning, I think we cannot use <IP_ADDRESS> or 4.2.8-hotfix.
Also, we cannot remove the tags.
Am I wrong?

I think redoing the release is the best approach, but I'm not sure if the new tag's SHA will be picked up by packagist.

Packagist will update if you remove a tag and re-release it. This is my approach on small libraries when I make a mistake. We could do that here as well, just have to delete the tags from the distributable repos too.
Sticking with SemVer is best. It looks like we could append "build metadata" like v4.0.8+hotfix.1 but that seems more of a hack than a supported approach. So let's go with new release or removing tags.

When we use this PR,
if we forget to update the version number, the framework deploy will stop.
But in this repository the release was done already?

... But in this repository the release was done already?

Yes, because the release payload from this repo will be used in creating the respective releases in the 3 repos through actions/github-script

I think that's fine. Deleting tags isn't as big a deal as it seems, and if the Action stops it from happening on the distributables then we are pretty much guaranteed nobody has been affected.

Yes, this repository is not a Composer package.
Removing tags/releases is not a big deal if we do it quickly.


How to check version?

I can run foundation -v to get the command line version, but where in the framework is the version of the framework defined?

Look for package.json

You can also run Foundation.version in your browser's dev tools console.

Closing this issue now with above 2 comments as reference ....
@ob7 Please feel free to revert if something's left!

My package.json generated by foundation-cli does not actually list the version of the framework itself.
I believe I'm using Foundation 6.3.1.
As for running Foundation.version, that will only work if you are also using javascript, but I'm only using the CSS.

Reopening the issue
Can you brief about your workflow???

bower_components/foundation-sites/bower.json is what you are looking for.
The version can also be found at the top of these files:

Any unminified file in bower_components/foundation-sites/dist/css
bower_components/foundation-sites/scss/foundation.scss

Thank you Deckluhm all others.   The responses cover about every way to get the version.  My  specific need was answered by Deckluhm by showing me where I can find the foundation version in plain text throughout the files.


pip.venv and pip.packages do not seem to be idempotent

Describe the bug
Please consider the following code snippet. When run multiple times, installing the packages via pip.packages is reported as "changed" every run.
To Reproduce
from pyinfra.api import deploy
from pyinfra.operations import pip

@deploy("Venv")
def venv():
    pip.venv(
        python="python3",
        path="/tmp/clientvenv",
    )

    pip.packages(
        name="Install packages",
        packages=["boto3==1.26.27", "lucidity==1.6.0"],
        virtualenv="/tmp/clientvenv",
    )

venv()

Run via
pyinfra inventory_client.py deploy_client.py

All involved systems are Ubuntu 22.04.
Expected behavior
The packages are found in the given venv and not reported as changed every time.
Please tell me I am just not seeing something basic here... I feel dumb, this should be easy :D
Meta
    System: Linux
      Platform: Linux-5.15.0-56-generic-x86_64-with-glibc2.35
      Release: 5.15.0-56-generic
      Machine: x86_64
    pyinfra: v2.5.2
    Executable: /home/grndgdnke/lidl_render_backend/lidl_render_backend_venv/bin/pyinfra
    Python: 3.10.6 (CPython, GCC 11.3.0)

How was pyinfra installed (source/pip)?

venv + pip install

The reason this operation keeps showing as changed is because the package name in pypi is actually Lucidity.
Your deployment is using a lowercase version of the name so it's always returning that it needs to be installed.
The quick fix here is to change your deployment to use the actual package name:
    pip.packages(
        name="Install packages",
        packages=["boto3==1.26.27", "Lucidity==1.6.0"],
        virtualenv="/tmp/clientvenv",
    )

Whether or not this is a bug, or something that should be fixed is another discussion.

Oh good catch! Thank you.

So pyinfra did used to, depending on package manager, lowercase package names. However this behaviour was confusing and resulted in other bugs. That said PyPi's own pep-0426 clearly states package names should be compared insensitively, this would probably require lowercasing input names and fact names...


BASIC uin notworking

I'm sending stuff to the serial port.
In BASIC, if I use sload I can see the data I'm sending.
if I write
10 print uin 1
20 goto 10
nothing gets printed :(

Note: UIN works only if there is nothing in the buffer. So you need to start sending data only afterrunning the BASIC program

uin parameter decides whether the function is blocking or not, see documentation. Anyway, the uin function seems fishy, will take a look at it.

I checked again the uin functon in both blocking and non-blocking mode, it seems to work.
Baudrate for badge is fixd to 19200, no handshake, 3,3V levels.


Text "decorations" (\cancel, \underbrace, etc.) are sized incorrectly for Unicode text

Issue Summary
The "decorations" created by e.g. \cancel, \underbrace, and \overline are sized incorrectly when the command's argument contains unicode text.
Steps to Reproduce:

Go to https://www.mathjax.org/#demo
Enter $\underbrace{\text{你好}}$ in the box

Technical details:

MathJax Version: 3.2.2
Client OS: macOS 12.6
Browser: Microsoft Edge 113

Supporting information:

I am not able to reproduce your results using Edge 113.0.1774.57 on Mac OS 12.6.5.  Here is what I see:

Have you made any changes using the MathJax contextual menu that might be affecting the results?

Yes, I had {"scale":"1.8"} in MathJax-Menu-Settings. Sorry for the confusion.

Well, it should still work with that setting, so there may still be a problem with Edge, though I'm still not able to reproduce it.  I will leave this open to check into in the future.


[Enhancement] Code reuse is extracted as a method.[GrpcMessageProtocolResolver]

Search before asking

[X] I had searched in the issues and found no similar issues.

Enhancement Request

located at:
eventmesh-protocol-plugin/eventmesh-protocol-meshmessage/src/main/java/org/apache/eventmesh/protocol/meshmessage/resolver/grpc/GrpcMessageProtocolResolver.java line 68-95,98-125,159-186,189-216
analysis and explanation:
The code in these places is reused and can be extracted as a method.
Describe the solution you'd like

Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

@Alonexc,I worked on this issue. Please review and approve this PR - https://github.com/apache/eventmesh/pull/3876

Hey @Alonexc
is this issue available, i would like to work on it.

@sumitdethe27 OK！


Module not found error

Can you please help me with this?

Did you install gdspy on the same virtual environment you're trying to use it from? On the Command Prompt where you installed gdspy, does the following command work: python -c "import gdspy"?

No its not working

How did you install it the first time? On Windows, gdspy need a properly configures development environment for compilation of C extensions. If your environment is not configured correctly, it will appear to have been installed but it won't be. If that's the case, uninstall it with pip (as you did the first time) or manually remove all files from site-package and use one of the provided wheels (*.whl) in the releases page.

Thank you. It work.


adding react-dom and react-test-render to addon peer dependencies

Issue: There could be different versions of running in Storybook because some addons don't rely on peer dependencies to get the correct version number.
It could be related to this:
https://github.com/storybooks/storybook/issues/986
What I did
Updated some package.json
How to test
Please pull the branch and help me test this in your own storybook to see if there are any issues.

I don't understand this @danielduan -- if we aren't removing it from other dependencies, what exactly will it do? Also, do all those packages use react-test-renderer?

react-test-renderer has been specified by those packages already, whether we need it as a peer dependency could be up for debate.
As for adding react and react-dom to the peer dependencies, it will help us keep the react and related package versions throughout the project consistent when the user downloads it.
Say someone's project is on<EMAIL_ADDRESS>and<EMAIL_ADDRESS>and the main @storybook/react would use<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Since the addons have their own package.json, the peer dependency<EMAIL_ADDRESS>could be used with the dependency<EMAIL_ADDRESS>and cause a version mismatch. Also, there would be two react-dom versions running alongside each other.

react-test-renderer has been specified by those packages already. I'm not sure if there are actual implications of running two different version in the same project so whether we need it as a peer dependency could be up for debate.

I think if it's in devDependencies it's fine to leave it out of peerDependencies, if it is only used for test purposes.

As for adding react and react-dom to the peer dependencies, it will help us keep the react and related package versions throughout the project consistent when the user downloads it.

Can we talk through the exact scenario this helps with? The thing is that peer deps in npm are just pretty much broken (especially when you npm link), and I'm not sure adding a react: "*" peer dep actually achieves anything. Maybe it's worth doing as I'll discuss in a sec, but I suspect it won't help with the problem of multiple versions of react.
So as a illustrative example: The actions addon currently lists react in the devDependencies but nowhere else. This is bad because the addon imports react and theoretically the app it is in may not include react (although I guess this never happens). Also as a secondary badness there could be a version mis-match between react versions (i.e the app could be using a version of react the addon doesn't like).

When you npm install inside an app including the @storybook/addon-actions package, it (A) doesn't influence the version of react your app gets (if any) and (B) doesn't get its own version inside node_modules (this is the problem you are concerned about), because npm won't look at devDependencies in this case.

When you npm install in a checked out version of the package it does get a copy of react, and when you npm link it into an app, you'll now have 2 reacts, which is why npm link is broken, and @ndelangen created the test-cra app which uses file:// references. [<- an aside]. (Also a linked package can't require the react from the app anyway. Good times).

If we add the peerDependencies lines, then case 1 will change in the sense that now you'll get an error if your app doesn't use some version of react. This is good I suppose, but won't actually help in any real world scenarios (people are using react anyway, right?) . Restricting the version would be more interesting, if we are concerned about that. (In practice I suspect most users ignore peer dep warnings anyway).
Case 2 will be unaffected by the peer dep thing, sadly.
I'm not quite sure what my point is, probably just ranting about npm. I think I am saying (1) let's not add the react-test-renderer lines. (2) we can add the react and react-dom lines for correctness, but they won't do anything (3) if you were seeing an issue with multiple react versions, we should investigate further because I don't think this change will solve that problem.

Thanks for the really detailed analysis, really appreciate it. I'm not an expert in how npm resolves modules and this definitely helped my understanding.
I updated the branch to just include react-dom for formality and consistency's sake.

But do these package actually need react-dom? They don't import or require it anywhere?

Yeah, seems like they're extraneous. Should have checked to see if they actually used it first. Closing.


Better handle the concurrent execution of addAddress() and updateAllProfiles()

The ideal scenario for updating profiles would be to:

add all addresses via addAddress()
and then update all profiles via updateAllprofiles().

However, in reality these functions can be called concurrently, meaning that new addresses can be added to the queue of addresses that should be updated while the update function is still running, which messes up the logic.
Example:

updateAllProfiles() is called with 3 addresses,
while updateAllProfiles() is still executing, 5 new addresses are added concurrently via addAddress(),
however, updateAllProfiles() has already passed the step of requesting the data from Nostr relays for 3 addresses, so 5 new addresses are not actually updated,
at the end of updateAllProfiles() function, all addresses are cleaned from the queue (e.g., the queue for Nostr usernames is this.addresses.toBeCheckedFor.nostr.kind[0]),
updateAllProfiles() is finished,
updateAllProfiles() is called once again, but 5 new addresses have already been added and then cleaned from the queue during the previous execution of the updateAllProfiles() function alongside with the original 3 addresses, so now there are no addresses in the queue to be updated.

There are at least two possible solutions:
Refactor updateAllProfiles()

Make a deep copy of the queue object (this.addresses.toBeCheckedFor) using JSON.parse and JSON.stringify to save the state of the queue, which can be used during the update process.
Even if new addresses are added, they won't influence the deep copy of the queue.
At the end of the update process, execute a smart cleaning function which will delete already checked addresses (saved in the deep copy of the queue) from the current queue (this.addresses.toBeCheckedFor).

Only add addresses to the queue when the updateAllProfiles is not running.

If the update process is running when addAddress() is called (this.isUpdatingProfiles or this.isUpdatingProfilesNostr), then pause the execution and add a setInterval to check every 100ms for the next 10 seconds whether the update process is finished, and only then add the address to the queue.
However, this approach can lead to scenarios when the address is waiting to be added to the queue for e.g. 8 seconds already, and when the update function is finished, the new update function will be called before the address is added to the queue, meaning that the address won't be updated even after waiting for 8 seconds. We can decrease the setInterval from 100ms to 10ms, but that can increase the memory usage of the browser tab, especially if many addresses are waiting to be placed in the queue.

Implemented the first solution in commit 4e1fb1fb01e00506d15adefa42f26b8d2a2d9a08.

Refactor updateAllProfiles()

Make a deep copy of the queue object (this.addresses.toBeCheckedFor) using JSON.parse and JSON.stringify to save the state of the queue, which can be used during the update process.
Even if new addresses are added, they won't influence the deep copy of the queue.
At the end of the update process, execute a smart cleaning function which will delete already checked addresses (saved in the deep copy of the queue) from the current queue (this.addresses.toBeCheckedFor).


fix(sdk-metrics): update default Histogram's boundary to match OTEL's spec

Which problem is this PR solving?
Default HistogramAggergation's Boundary bucket is not matching OTEL's spec
Current bucket value: [0, 5, 10, 25, 50, 75, 100, 250, 500, 750, 1000]
Expected bucket value: [0, 5, 10, 25, 50, 75, 100, 250, 500, 750, 1000, 2500, 5000, 7500, 10000]
Fixes #3669
Short description of the changes
Update the default Boundary's bucket value to the correct version + update the unit test to match this new bucket value.
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Unit Test with npm run test

Checklist:

[x] Followed the style guidelines of this project
[x] Unit tests have been updated
[ ] Documentation has been updated

@pichlermarc I added the record in CHANGELOG.md and fix the lint issue.


Use toml++ to parse OQD hardware data toml file and send it to --quantum-to-ion pass

Context:
Description of the Change:
Benefits:
Possible Drawbacks:
Related GitHub Issues:
[sc-73705]

@mlxd @josh146 Where should the licensing of "we are using your project" be put?

@mlxd @josh146 Where should the licensing of "we are using your project" be put?

Lee was talking about the attribution list at the bottom of our readme.

Here is what they say

If you're using the single-header version of the library you don't need to explicitly distribute the license file; it is embedded in the preamble at the top of the header.

So in that case, that should be sufficient.

@joeycarter I think we are good to go!


[fix] Hotfix/wf simulator

Status
** DEVELOPMENT**
Description
#1495
I use boost::optional and add invalid values to the waypoints data and when the simulator recieved a invalid value, the simulator does not update car pose in z axis.
Before

After

Todos

[x] Tests
[ ] Documentation

Steps to Test or Reproduce

run runtime_manager
load vhicle_model in Setup tab
load pointcloud and vector map in Map tab.
launch all related nodes in runtime_manager in Computing tab.
(vel_pose_connect(simulation_mode), wf_simulator, lane_rule, lane_stop, lane_select,
obstacle_avoid, velocity_set, pure_puirsuit, twist_filter.)

In my environment(hotfix/wf_simulator with develop branch),
z position is always zero.
Please check on another map.

---
header:
  seq: 87
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 186693097
  frame_id: "map"
pose:
  position:
    x: -47295.9411573
    y: 57583.1006171
    z: 0.0
  orientation:
    x: 0.0
    y: 0.0
    z: -0.502845726434
    w: 0.864376177024
---


ICR | build and push failing

Steps to reproduce the problem
Execute ICR | build and push action
What is the current behavior?
ICR | build and push action fails
https://github.com/Qiskit-Extensions/quantum-serverless/actions/runs/5541059240/jobs/10113961001
What is the expected behavior?
The action must finish with success

ERROR: Could not install packages due to an OSError: ("Connection broken: ConnectionResetError(104, 'Connection reset by peer')", ConnectionResetError(104, 'Connection reset by peer'))

Might have just been a temporary failure... I'll rekick the job and see what happens.

Build succeeded, so I think we're good to go :tada:


It's working now---using Chinese corpus

the plot like

the train is very slowing

That is great to know, @maozhiqiang!
What exactly is slow? the training iteration or the time it takes to learn attention?
What is your setup?

@begeekmyfriend please move this comment and discussion here: https://github.com/NVIDIA/tacotron2/issues/12

@rafaelvalle I training useing one GPU ,so the training is so slowing !and the attention is not until the twenty thousand step begins to align！

Training time is probably dominated by computing mel-spectrograms on the CPU and can be amortized by pre-processing the mel-spectrograms and loading them from disk.
We're looking into speeding up the model such that the attention is learned faster.

@maozhiqiang What is your iterations per second time on average?

FYI: We've added the option to load mels from disk.

@rafaelvalle thanks! The following is training log
train_log.log

@maozhiqiang What GPU do you have?

P5000

To me, the iterations per second seem comparable to what I've seen with Taco 2 implementations.
It should be less of a hassle once we improve model to learn attention faster.

@rafaelvalle thanks!

@maozhiqiang please re-run your experiments on the branch below and and let us know what your convergence time is. In this branch, the model attends to the full mel-spectrogram instead of the prenet drop out mel: this should increase convergence time considerably.
https://github.com/NVIDIA/tacotron2/tree/attention_full_mel

@rafaelvalle thanks , I will try this

@maozhiqiang great. We'll soon add dropout as well.

@maozhiqiang Could you share what Chinese corpus you have used?

sorroy ! The data is not open!

Closing. Please re-open if the issues haven't been solved.

@maozhiqiang Would you please open your modification on this project for Chinese mandarin on your repo?

@begeekmyfriend  yes! i uploaded ! please go to https://github.com/maozhiqiang/tacotron2_pytorch.git

Hi, @maozhiqiang , could you share some synthesized speech samples in Chinese tacotron2 project?  What is the unit you used? How do you control the tone of the synthesized speech?

@maozhiqiang The link is missing

@maozhiqiang the link is missing too.

@maozhiqiang  could you share you hparams.py detail ?


⭐FEAT: Make the issues list dynamic

Would be nice to have a dynamic issues list.

We can use the Octokit API to handle all the requests for the issues.
I think since this will be a major change for the project is better to have a discussion first, I have already start working on this.
This is a code example for the API request using octokit, with pagination.
const octokit = new Octokit({
  auth: import.meta.env.VITE_GITHUB_TOKEN,
});

export const getRepoInfo = async () => {
  try {
    const parameters = {
      owner: "ArslanYM",
      repo: "StarterHive",
      sort: "updated",
      direction: "asc",
      per_page: 6,
    };

    const issuesPages = [];

    for await (const response of octokit.paginate.iterator(
      "GET /repos/{owner}/{repo}/issues",
      parameters
    )) {
      const issues = response.data;
      issuesPages.push(issues);
    }
    // This function returns an array that contains different arrays with a max of 6 issue objects.
    // This way we can handle the pagination easily.
    return issuesPages;
  } catch (error) {
    throw new Error(error);
  }
};

@ThGnommy Actually we will be soon working on this, The Find Issues section is supposed to show issues in projects or codebases of organizations that are actual companies. And can potentially hire people.


SDS with service https protocol availability

So, I created SDS Api to get services dynamically. One of the service object is like below
    "hosts": [
        {
            "ip_address": "<IP_ADDRESS>",
            "last_check_in": "22-08-2017",
            "port": 4444,
            "revision": "1",
            "service": "hydra_service",
            "service_repo_name": "node1",
            "tags": {}
        }
    ],
    "env": "production",
    "service": "hydra_service"
}

in the documentation https://lyft.github.io/envoy/docs/configuration/cluster_manager/sds_api.html#config-cluster-manager-sds-api it tells that you should provide hosts array and the structure like below
  "ip_address": "...",
  "port": "...",
  "tags": {
    "az": "...",
    "canary": "...",
    "load_balancing_weight": "..."
  }
}

I run my service above using docker container, the access should be via https protocol. Is there any other configuration that can be https protocol enabled? or can you provide it?
Thank's in advance

I'm not totally sure what behavior you are asking for. What access do you want to be via HTTPS?

the host access, so the point is in each host configuration you can have an option to access whether via http or https,  if I imagine it, you'll have a configuration like below
"hosts": [
        {
            "ip_address": "<IP_ADDRESS>",
            "protocol": "https" <-- https protocol option
            "last_check_in": "22-08-2017",
            "port": 4444,
            "revision": "1",
            "service": "hydra_service",
            "service_repo_name": "node1",
            "tags": {}
        }
    ]

Currently, Envoy assumes that all hosts in a cluster are the same. The way that you would handle this is to have a TLS cluster and a non-TLS cluster and route appropriately.

Closing as question has been answered. Feel free to reopen if there are additional questions.


AUR package

As I sen, maestral is heading for a 1.0.0 release. Presumably, this is considered stable (enough). I am opening this to discuss packaging for Arch Linux (and derivatives) through AUR.
There is already a git package, but it is missing some recent dependencies, etc. I have tried to get in touch with the owner, and potentially be co-maintainer. If this fails, I could start a new package with released versions.
Here is a sample PKGBUILD for the cli component, based on previous work:
_srcname='maestral-dropbox'

pkgname='maestral'
provides=('maestral')
conflicts=('maestral-git')
pkgver=0.6.4
pkgrel=1
pkgdesc='A light-weight and open-source CLI Dropbox client.'
arch=('x86_64')
url="https://github.com/SamSchott/${_srcname}"
license=('MIT')
source=("${url}/archive/v${pkgver}.tar.gz")
makedepends=('python-setuptools')
depends=(
    'python>=3.8'
    'python-atomicwrites'
    'python-blinker'
    'python-bugsnag'
    'python-click>=7.0'
    'python-dropbox>=9.4.0'
    'python-keyring>=19.0.0'
    'python-keyrings-alt>=3.0.0'
    'python-lockfile'
    'python-pyro5'
    'python-requests'
    'python-u-msgpack'
    'python-watchdog>=0.9.0'
    'python-systemd')
md5sums=('SKIP')

build() {
    cd "${srcdir}/${_srcname}-${pkgver}"
    python setup.py build
}

package() {
    cd "${srcdir}/${_srcname}-${pkgver}"
    # Run python setup function
    python setup.py install --root="${pkgdir}/" --optimize=1 --skip-build
    # Remove icons, unnecessary for the CLI
    rm -rf "${pkgdir}/usr/share/icons"
    # Install the licence
    install -Dm644 "${srcdir}/${_srcname}-${pkgver}/LICENSE.txt" \
    	"${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
}

I have tested, and it locally builds OK, but outside testing is always appreciated.
I have some questions for the long-run health of packaging:

The releases will follow the same pattern in the future, i.e., tar files appearing in the archive subfolder, etc?
I would prefer dependencies to be maintained "official" packages, outside of AUR. RIght now, the only ones that only appear in AUR (and are not official) are pyro5 and bugsnag. I will ask about plans to support pyro5, since right now pyro4 is officially maintained. I am less optimistic on bugsnag for the future. Since this does not look like a hard dependency, could it be removed in a stable version?
Minimum version dependencies are easy to handle in Arch, since the latest versions of packages are provided faster than other distros. I am worried about maximum version dependencies (such as dropbox<=9.5.0) because they can break packages easily.
If possible, mention in the changelog when dependencies change (add/remove) in order to ease the update of PKGBUILD, accordingly.
regarding package naming: one could go with maestral, maestral-cli, maestral-dropbox, maestral-dropbox-cli. Any preference?

Stability and performance have indeed improved significantly in the last few releases and a 1.0.0 release should hopefully come out some time this month. And thank you for taking the time to package this. I have found that packaging for Linux really is a tedious job while trying to create a snap and a deb package. I can imagine that the current maintainer may have run into similar issues such as missing dependencies.
To answer your questions:

Yes, releases will continue to follow the same pattern. The tar files are created automatically by Github on every release and Maestral uses github APIs to notify the user of new releases.

I agree that there are good chances for Pyro5 to be officially maintained, at least once the author guarantees API stability. Bugsnag has been invaluable in getting reports from those who do not have a github account and for catching corner cases. It is one of the reasons why I am confident about the stability. But you are right, it is not packaged for most Linux distros since it is a subscription service (with a free plan for open source projects). Is there any way of bundling bugsnag with maestral when packaging? I know it wouldn't be ideal...

The maximum version dependency is there to avoid breaking changes in the Dropbox SDK which have already occurred once. But I will aim to always test the newest Dropbox SDK as it is released.

This is a good point. I will explicitly list changed decencies in the future. In 1.0.0, at least u-msgpack will be dropped.

Definite preference for just maestral, following the Python package name. Naming the repository "maestral-dropbox" was bid for higher visibility which I am starting to regret...

Finally, I expect that the pace of releases will slow down from 1.0.0 onwards. That should make the job of maintaining a package easier :)

Many thanks for the prompt response, and for your great work on this. At this moment bugsnag is not a problem, as there is a further AUR package. But I am worried about the long-run health, as I mentioned. Another option is to make bugsnag an optional dependency, but bundle it by default in the deb, snap, etc packages that you will provide. Arch users will not have a problem to give you info through Github.
I will wait for 1.0.0 to be out and then create the packages.

As the maintainer; I'm waiting for stable release because I can't keep up with architectural/dependency changes. The project rapidly evolves, for the better.
I did add @coxackie as a comaintainer; but I am opposed to splitting isno 2 packages for cli and gui. I rather have one pkgbuild create 2 packages (split packaging) but I am waiting for a 1.0 version.

In my opinion, we should respect the fact the the cli and gui are separate now. We should further accommodate those who do not want to install gui and pull all the Qt dependencies that will come with it. For example, I do not have qt-base installed (and do not wish to, as well).

There are a few reasons for splitting gui and daemon + cli, at least for the Python packages:

As @coxackie notes, many users only require the daemon and don't want to install Qt / PyQt. This isn't a serious issue for python packages since PyQt5 used to be an optional dependency before the split.

A native Cocoa GUI for macOS is in development. Splitting GUI and daemon makes it easier to develop different GUIs independently.

Once the daemon API is stable, GUI development can progress at its own pace instead of being tied to daemon releases.

For the macOS app bundle, I have made the decision to package GUI and daemon together but this has a different target audience than Linux. I think it really comes down to accommodating the most frequent use cases so for Linux I would probably tend towards separate packages. But this is by no means set in stone.

In favor of maybe someone else providing other gui frontends (such as a web interface, or gtk) I think splitting the packages into maestral and maestral-qt makes sense. The current build script for the main daemon is up here; and I am adding the qt script once I confirm it is working.
I also submitted packages for pyro5 and bugsnag directly from their pypi counterparts. They are not shipped with archlinux at least that I know. For end users; i understand that bugsnag is free? And you have a subscription as a collector of bug reports?
Archlinux community repos usually keep packages as up to date as possible. However; for programs that do use old versions (I just finished packaging matlab as well; which uses gcc6 which is no longer provided in the archrepos) submitting AUR old version builds is an acceptable solution.

For reference, you can have a look at the packaging we do for NixOS: https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/networking/maestral/default.nix
It's been a part of NixOS since 0.2.6 and keeping it updated has been a breeze. But then again, packaging on NixOS is very pleasant to begin with... ;-)
On the issue of bugsnag, maybe not making it a hard requirement would be an option if that is the main barrier for distributions to start packaging it officially? Load it if it's there and otherwise just don't if it isn't.

Please refer to:
https://aur.archlinux.org/packages/maestral/
https://aur.archlinux.org/packages/maestral-qt/
for the packaging of maestral (cli and gui versions, respectively) in the AUR (for Arch-based distros)
This issue can be closed at any time - I leave it to @SamSchott.

Nice, thanks for the info. And for packaging of course!


fix affjax canceler

fixes #116 #112
see example from https://github.com/slamdata/purescript-aff#escaping-callback-hell

regarding https://github.com/slamdata/purescript-affjax/issues/116
I am still not getting my expected Oops error and am now getting a Uncaught TypeError: Cannot read property 'constructor' of null from the ffi.

Hm, not sure what could be an issue then.
Will leave this open if someone wants to investigate this.

oops missed #113


dashboard: unset labels also by value

It looks to be more intuitive for users to use #syz unset than #syz set subsystems: <new list>.
Adjust syzbot's command handling mechanism to support label unsetting by values.

We don't need it for now.


Fixes console for local development

Prior to this, resolving BUNDLE_GEMFILE was problematic plus we were
relying on the user having pry installed globally. Which may not be
the case.

:+1: thank you!


ACTIVATING THE BOT

ok so I followed ever step up until activating the bot itself I the batch file isn't running properly and I think I'm missing something
and I'm not even sure if this really will work or not so if anyone can help me take over chat zone that'd be great

@Flippy101mph start the bot through the console

where is the bot???

i cant download bot

I managed to get it working but then I got kicked from the server
On Sun, Apr 17, 2022 at 9:58 PM REAPERSDmise @.***>
wrote:

where is the bot???
—
Reply to this email directly, view it on GitHub
https://github.com/Barsik008/PossumBot/issues/125#issuecomment-1101044182,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVRBRAXO7MYJZ3J3GVBUJLLVFTFXBANCNFSM5DVSFTGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


mouse event not work

mouse event not work at windows 10 and macOS Sierra 10.12.6 , but working well at Ubuntu.
I use Nexus 5 with android 5.0 system. I use this kernek for nexus 5 .
Please help me.

I have fix this issue.As follows:
adb shell
su
echo -e -n "\x0\x{X}\x{Y}\x0" > /dev/hidg1
{X} is distance at X axis, {Y} is distance at Y axis

Hi there, do you think you can share how you worked this out and whether you got the mouse buttons to work please? I would very much appreciate it!

@michaeliwaikato Yes, i have fixed this successful. You should directly write bytes that contain 4 byte to  dest file (/dev/hidg1). Cmd as below, not use "./hid-gadget-test"。

There is a useful software named USB Monitor for widnows. You can capture the data send to windows. Hope to help you.

I have put some info in #135 if it is useful to anyone who finds this issue with the mouse


swift-format fails to run in swift-5.7 docker image "library is not compatible with this version of SwiftSyntax"

Hello,
This is how you can repeat it:
$ git checkout release/5.7

$ docker run --rm -it -v $PWD:/work swift:5.7 /bin/bash

# cd /work

# swift build -c release
Fetching https://github.com/apple/swift-system.git
Fetching https://github.com/apple/swift-tools-support-core.git
...
Building for production...
[40/40] Linking swift-format
Build complete! (289.44s)

# ./.build/release/swift-format format Package.swift
<unknown>: error: Unable to format Package.swift: The loaded '_InternalSwiftSyntaxParser' library is from a toolchain that is not compatible with this version of SwiftSyntax

It looks like this is the issue pointed out in the swift-syntax 0.50700.1 release notes:

⚠ Important: This release of SwiftSyntax is incompatible with the parser library included in the swift-5.7-RELEASE toolchain. On Linux, download a recent swift-5.7-DEVELOPMENT-SNAPSHOT toolchain to use this SwiftSyntax version. On macOS, this version of SwiftSyntax is compatible with any recent Swift or Xcode toolchain because it includes the parser library as a binary dependency.

Tracked in Apple’s issue tracker as rdar://126948261


fire rainlab.user.beforeRegister

Added beforeRegister in order to add custom validation logic as described herer https://github.com/rainlab/user-plugin/issues/226
In custom plugin boot method it can be used like this:
Event::listen('rainlab.user.beforeRegister', function($account, &$rules, &$data) {
            $rules['web'] = 'required';
            unset($rules['email']);
        });

As in #226, it is probably better to create your own onRegister handler in your own component. It is OK for your component to extend the native RainLab.User Account component, we do this all the time internally.
<?php

class MyAccount extends RainLab\User\Components\Account
{
    public function onRegister()
    {
        // Inherit parent
        parent::onRegister();

        //... or run any code required
    }
}

Otherwise we would need a compelling and common use case as to why this is needed.


TweetPublicMetrics model miss "impression_count" param

In the API doc:
public_metrics.impression_count | integer | Number of times this Tweet has been viewed.
But when use TweetsApi.findTweetById response miss "impression_count". See TweetPublicMetrics model miss "impression_count" param.

Are their any updates on this issue?

Given that no one is activley working on this repository anymore (and @zacmos doesn't work for them anymore), the best we can do is to ask on X/Twitter or on the developer forum, if they are planning to work on this sdk any time soon again.