C3 Screen Too Bright @ Night

Describe the bug
Since installing 0.9.7 screen brightness at night on the C3 has been way too bright. Usually the night compensation for brightness works well, seems to have changed w/ 0.9.7.
Route below is an example of a bad screen brightness at night.
Whole route has the issue happening.
Provide a route where the issue occurs
4ecfcac756318cbf/00000035--99d3637ece
openpilot version
0.9.7, release3
Additional info
Fixing the brightness compensation is good but I would suggest adding an alternative brightness toggle. The user would be able to easily override screen brightness settings if they do not like stock brightness settings.

It's not an intermittent issue at all, for me at least. Pick any route at night with this dongle 149d6f706527cfe1
Here's 1 example 149d6f706527cfe1/00000115--907e342143
Essentially just stuck at 100% brightness it seems, I only notice it at night (every time) but possibly any route just not being noticeable during the day.

Night driving only possible with manual brightness setting currently

Commenting to say I am having this issue as well recently.
Blinding at night.   Manually turn down.  Then during day, can't see screen unless I shade it from the sun to turn it back up again because I cranked it down the night before.

Can you guys test installer.comma.ai/commaai/fix-too-bright?

@adeebshihadeh looks like that helped! Not as dim as I personally keep my infotainment, but it was enough that it wasn't blinding. Route: 5130484aa8069bad/000000c9--4b7e4e53c6

@adeebshihadeh are you looking for any other users to test, or any other routes to merge this?

So that isn't a mergable branch, it's just a test. Now that it's been tested, I'll come up with a mergable branch for you guys to test soon.

I can also test in a couple of days. Just really busy the last week...

Worked well on this route today 4ecfcac756318cbf/00000000--abb1191d75/0

The more I use this branch the more it seems like it's just darkening the input from the cameras and not the actual screen. If I open the sidebar or go into settings it's just as bright as not being on this branch.
Looking back at old footage from previous releases, the screen was a lot darker. Is there a way to reinvestigate this as an auto brightness issue instead of the gamma input on the cameras?

Looking back at old footage from previous releases

What footage? You can't tell this from the device's logs, unless you mean recording a video of the device with your phone?

Yes looking at old footage I recorded of the comma 3 and from my own memory, it was a lot dimmer.

Can confirm the UI is bright. Screen is still bright at night.

Also confirming.   Lol, does it not get dark in San Diego?  It's unusable at night without cranking it way down.   Then you can't see it in the morning without covering it with your hand to make it dark enough to see the settings to turn it back up.

The screen is the brightest at midnight. This was at 2400-0100 w. Screen-Too-Bright. 4ecfcac756318cbf/00000016--7005cf51a2/0

Here's an example of auto brightness mostly working. Seems to work best when there's changes to the brightness. In this route we start in my garage, then go to a sunset drive into twilight. It starts to dim with the sunset correctly until I get on the highway in which it full brights for a mile or two, then starts to auto dim again correctly: 5130484aa8069bad/0000012a--3c9d04250a

@adeebshihadeh confirmed this bug is fixed by #33984!


No OpenCL devices found after creating OpenGL context

Since updating to the latest AMD Radeon Software for Linux, our software, Zivid Studio, is unable to find any AMD OpenCL device.
In debugging this issue, I found that if clGetDeviceIDs is called after an OpenGL context is initialized it returns CL_DEVICE_NOT_FOUND. When this happens, the following is written to the kernel log:
[Mon Oct  9 14:28:21 2023] amdgpu: Failed to create process VM object
[Mon Oct  9 14:28:21 2023] amdgpu: Failed to create process VM object

Here is a minimal example that reproduces the issue on my system:
#include <GL/glut.h>
#include <CL/cl.h>
#include <stdio.h>
#include <string.h>

void listOpenCLDevices() {
    cl_uint num_platforms;
    clGetPlatformIDs(0, NULL, &num_platforms);
    cl_platform_id platforms[num_platforms];
    clGetPlatformIDs(num_platforms, platforms, NULL);

    printf("OpenCL Platforms:\n");
    for (int i = 0; i < num_platforms; i++) {
        char name[128];
        clGetPlatformInfo(platforms[i], CL_PLATFORM_NAME, 128, name, NULL);
        printf("  Platform %d: %s\n", i, name);

        cl_uint num_devices;
        clGetDeviceIDs(platforms[i], CL_DEVICE_TYPE_ALL, 0, NULL, &num_devices);
        cl_device_id devices[num_devices];
        clGetDeviceIDs(platforms[i], CL_DEVICE_TYPE_ALL, num_devices, devices, NULL);

        printf("  Devices:\n");
        for (int j = 0; j < num_devices; j++) {
            char device_name[128];
            clGetDeviceInfo(devices[j], CL_DEVICE_NAME, 128, device_name, NULL);
            printf("    Device %d: %s\n", j, device_name);
        }
    }
}

int main(int argc, char **argv) {
    if (argc == 2 && strcmp(argv[1], "nogl") == 0) {
        listOpenCLDevices();
        return 0;
    }

    // Initialize GLUT and create a window
    glutInit(&argc, argv);
    glutInitDisplayMode(GLUT_DOUBLE | GLUT_RGB);
    glutInitWindowSize(640, 480);
    glutCreateWindow("Test");

    // List OpenCL devices
    listOpenCLDevices();

    return 0;
}

And here is a Makefile to compile it:
CC = gcc
CFLAGS = -Wall -Wextra -O2
LIBS = -lGL -lGLU -lglut -lOpenCL

all: program

program: main.c
	$(CC) $(CFLAGS) -o program main.c $(LIBS)

clean:
	rm -f program

output:
❯ ./program
dlerror: /usr/lib/x86_64-linux-gnu/intel-opencl/libigdrcl.so: cannot open shared object file: No such file or directory
OpenCL Platforms:
  Platform 0: AMD Accelerated Parallel Processing
  Devices:
  Platform 1: Intel(R) OpenCL
  Devices:
    Device 0: AMD Ryzen 9 7950X3D 16-Core Processor

When running without OpenGL:
❯ ./program nogl
dlerror: /usr/lib/x86_64-linux-gnu/intel-opencl/libigdrcl.so: cannot open shared object file: No such file or directory
OpenCL Platforms:
  Platform 0: AMD Accelerated Parallel Processing
  Devices:
    Device 0: gfx1034
    Device 1: gfx1036
  Platform 1: Intel(R) OpenCL
  Devices:
    Device 0: AMD Ryzen 9 7950X3D 16-Core Processor

System Information:
CPU: AMD Ryzen 9 7950X3D 16-Core Processor
GPU: AMD Radeon rx 6500 xt
OS:  Ubuntu 22.04.3 LTS (Kernel 6.2)
Sorry if this is the wrong place to report this issue.

Hi @johningve! Apologies for the lack of response. Internal ticket has been created to investigate your issue. Thanks!

Hi @johningve, thank you for reach out! We weren't able to reproduce the issue on ourside...would you mind adding the  -L/opt/rocm/lib to your gcc commands just to make sure the correct OpenCL is used? Thanks!

Hi @tcgu-amd. In our Zivid Studio software we are using the ICD Loader library instead of linking with system OpenCL. When compiling the reproducer I am not sure which libOpenCL.so is used. In either case the reason you see the Intel OpenCL libraries in the output is simply because we have that OpenCL platform installed on the system also. I do not know if it is related to the issue or not.
Unfortunately I am no longer able to reproduce this issue myself. I do not know what changed to fix it, but I did upgrade to Ubuntu 24.04 and the latest drivers.

Hi @tcgu-amd. In our Zivid Studio software we are using the ICD Loader library instead of linking with system OpenCL. When compiling the reproducer I am not sure which libOpenCL.so is used. In either case the reason you see the Intel OpenCL libraries in the output is simply because we have that OpenCL platform installed on the system also. I do not know if it is related to the issue or not.

Ah that makes sense. It is likely a problem with linking the wrong OpenCL library then. I have taken a quick look at ICD Loader library; it might help next time to uninstall conflicting OpenCL libraries and run ROCm post-installation instructions again after setting up a custom loader like this.

Unfortunately I am no longer able to reproduce this issue myself. I do not know what changed to fix it, but I did upgrade to Ubuntu 24.04 and the latest drivers.
Edit: I have also replaced the dedicated AMD GPU with a NVIDIA GPU, maybe that is also related.

Unfortunately, I am unable to offer further assistance in this case. I am glad that your issue is resolved, and please feel free to reach out to us again if you ever encounter similar issues in the future.
In the meantime, would you mind if I close this issue for now? Thanks!

Hi @tcgu-amd. In our Zivid Studio software we are using the ICD Loader library instead of linking with system OpenCL. When compiling the reproducer I am not sure which libOpenCL.so is used. In either case the reason you see the Intel OpenCL libraries in the output is simply because we have that OpenCL platform installed on the system also. I do not know if it is related to the issue or not.

Ah that makes sense. It is likely a problem with linking the wrong OpenCL library then. I have taken a quick look at ICD Loader library; it might help next time to uninstall conflicting OpenCL libraries and run ROCm post-installation instructions again after setting up a custom loader like this.

Unfortunately I am no longer able to reproduce this issue myself. I do not know what changed to fix it, but I did upgrade to Ubuntu 24.04 and the latest drivers.

Edit: I have also replaced the dedicated AMD GPU with a NVIDIA GPU, maybe that is also related.

Unfortunately, I am unable to offer further assistance in this case. I am glad that your issue is resolved, and please feel free to reach out to us again if you ever encounter similar issues in the future.
In the meantime, would you mind if I close this issue for now? Thanks!


Update the Snap version of scrcpy to v2.0

[ Y ] I have checked that a similar feature request does not already exist.

Is your feature request related to a problem? Please describe.
The Snap version of scrcpy is only at v1.25, see https://snapcraft.io/scrcpy.
Describe the solution you'd like
Update the Snap version to v2.0.
Describe alternatives you've considered

Build the latest version from the source, as shown here.

Install from OBS for openSUSE users, as shown here.

Additional context

@sisco311 your repo seems up-to-date, do you know why it is not available in snap?
Side-note: I noticed that you added a scrcpy.desktop file, now there is one in the official version (but maybe you need a different one for snap?).

I tried it but it downloaded 1.25 instead of 2.0

Hi @rom1v
I did not push v2.0 to the Snap Store because it crashes (instead of defaulting to noaudio) if it has no access to ALSA.

scrcpy 2.0 https://github.com/Genymobile/scrcpy
/usr/local/share/scrcpy/scrcpy-server: 1 file pushed. 1.3 MB/s (52867 bytes in 0.040s)
[server] INFO: Device: motorola moto g(30) (Android 12)
INFO: Renderer: opengl
INFO: OpenGL version: 3.0 Mesa 21.2.6
INFO: Trilinear filtering enabled
INFO: Initial texture: 720x1600
ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
ALSA lib conf.c:4732:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4732:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4732:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5220:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2642:(snd_pcm_open_noupdate) Unknown PCM default
ERROR: Could not open audio device: ALSA: Couldn't open audio device: No such file or directory
ERROR: Demuxer error
WARN: Killing the server...

OK. Btw, it should not use alsa directly, but rather PulseAudio or PipeWire.
Does it work with another audio driver? https://github.com/Genymobile/scrcpy/issues/3864
Also see:

https://snapcraft.io/docs/audio-playback-interface
https://snapcraft.io/docs/alsa-interface

Hi @sisco311 - Will you be updating the Snap Store with the latest version of scrncpy? Version 1.25 of scrncpy does not work with Android 14. Thanks!

@sisco311

I did not push v2.0 to the Snap Store because it crashes (instead of defaulting to noaudio) if it has no access to ALSA.

In the current architecture (and with the initialization order), it is difficult to disable features if they do not work on the client side.
Accepting audio failure on the device side was done for two reasons:

I wanted audio to be enabled by default (so that users do not think that audio is not transmitted while it can be)
It is expected to fail on Android < 11~12, so I still wanted scrcpy to work as usual on these devices

But I think it is reasonable that not having a working audio output is an error if audio is enabled.
Anyway, SDL should use pipewire by default now: https://github.com/libsdl-org/SDL/issues/7541
Also, IMO, it is probably more important to get the latest version, 1.25 just does not work on many devices.

Thanks for your help, Romain! Fingers crossed....
Nathan
On Wed, Dec 6, 2023, 2:35 AM Romain Vimont @.***> wrote:

@sisco311 https://github.com/sisco311
I did not push v2.0 to the Snap Store because it crashes (instead of
defaulting to noaudio) if it has no access to ALSA.
In the current architecture (and with the initialization order), it is
difficult to disable features if they do not work on the client side.
Accepting audio failure on the device side was done for two reasons:

I wanted audio to be enabled by default (so that users do not think
that audio is not transmitted while it can be)
It is expected to fail on Android < 11~12, so I still wanted scrcpy
to work as usual on these devices

But I think it is reasonable that not having a working audio output is an
error if audio is enabled.
Anyway, SDL should use pipewire by default now: libsdl-org/SDL#7541
https://github.com/libsdl-org/SDL/issues/7541
Also, IMO, it is probably more important to get the latest version, 1.25
just does not work on many devices.
—
Reply to this email directly, view it on GitHub
https://github.com/Genymobile/scrcpy/issues/3916#issuecomment-1842610023,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIWFODTOSCL7MCXEA2RQ3IDYIBC63AVCNFSM6AAAAAAW5X2EAOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBSGYYTAMBSGM
.
You are receiving this because you commented.Message ID:
@.***>


"/assets" links in _Layout not compatible with LinkRoot setting

The /assets links in the _Layout file of this theme is not correct when using the LinkRoot setting. I believe they should be rendered via Context.GetLink.

Right you are!


TIS v3.7.0 Roadmap

[ ]  #155
[ ]  #156
[ ] #157
[ ]  #150
[ ] #158
[ ] #161

issue implement:https://github.com/qlangtech/tis/commit/92cd2d21d8eeb7c768f9bcb0b0b6062d32f25691


COBOL EBNF Grammar parsing

What is your question?
Is Lark is capable of COBOL EBNF Grammar?
Try to be accurate and concise.
Cobol Program has normally 4 divisions and sections/paragraph/statements.
Below is the website which provide most of the COBOL-85 Grammar rules in EBNF format.
https://www.cs.vu.nl/grammarware/vs-cobol-ii/
If you're having trouble with your code or grammar
Provide a small script that encapsulates your issue.
The below statement I was trying to get the parser statement of as DISPLAY which is KEYWORD in cobol and TEST which is a user_defined variable.
from lark import Lark
import re

cobol_parser = Lark(r"""
            statement: display_statement

            display_statement:	"DISPLAY"  identi | literal

            literal: SIGNED_NUMBER
            identi: string
            string: /[a-z0-9]([_a-z0-9\-]*[a-z0-9]+)?/

            %import common.SIGNED_NUMBER
            %import common.ESCAPED_STRING
            %import common.WS
            %ignore WS

            """, start= 'statement')

text = "DISPLAY TEST."
print(cobol_parser.parse(text).pretty())

Explain what you're trying to do, and what is obstructing your progress.
Not sure if I am doing everything correct. But I wanted to get an idea from the community. I am sure it is possible as the documentation of the Lark says it is possible to even parse Java, Python and most of the languages. Need help or guidance on this.

If COBOL can be expressed as EBNF, then Lark can parse it.
You might have better luck asking at our gitter: https://gitter.im/lark-parser/Lobby

Thank you so much for your kind reply. I will definitely try something out and come to the gitter with specific example or challenges for solution.


How can I contract a url like https://api.github.com/gists/:id?

The :id is a value indicating that id of the gist.
I solved this problem by creating an endpoint closure where the target's base url is api.github.com and the target's path is /gists:
let endpointClosure: MoyaProvider.EndpointClosure = {
    (target: GistRouter) -> Endpoint<GistRouter> in

    let url = target.baseURL.appendingPathComponent(target.path).absoluteString + "/xxx"

    let endpoint = Endpoint<GistRouter>(url: url, sampleResponseClosure: { .networkResponse(200, target.sampleData) }, method: target.method, parameters: target.parameters)

    return endpoint
}

Is there a better solution?

Am I missing something or could the same be achieved with:
(Slightly modified example)
extension MyService: TargetType {
    ...
    var path: String {
        return "endpoint/xxx"
    }
    ...
}

I mean it really depends on your enum. If you have associated value with your enum, then you can grab it just like in the Basic Example

@bjarkehs Oh, I forget this, thx so much.

You're welcome.


[deps] Added support for djangorestframework<=3.15.1

Checklist

[x] I have read the OpenWISP Contributing Guidelines.
[x] I have manually tested the changes proposed in this pull request.
[ ] I have written new test cases for new code and/or updated existing tests for changes to existing code.
[ ] I have updated the documentation.

Description
Added support for djangorestframework<=3.15.1

coverage: 97.784%. remained the same
when pulling ad9609543faa59d81ad001fc05ec61669c175dc5 on drf-3.15
into bbfdbdb94824b2cffc46a4665bb5fdb15b31c3fb on master.


Property wrappers

By adding @propertyDelegate to our existing auto-injection wrappers instead of
let client = Injected<Client>()

in Swift 5.1 we can write
@Injected var client: Client? = nil

~Note: as of Xcode 11 beta 1 () are needed after property delegate name~
Not an issue any more with refactoring of property wrappers into structs, but still requires initial nil value provided explicitly when using property wrapper (example updated) in class (not needed in structs)

hey @ilyapuchka, thoughts on this? I might be able to pick it and see what is left


2024.4.0: Fix for display Off

https://github.com/lubeda/EspHoMaTriXv2/issues/222

Tested and working!
thx


ci: split off test of doc code snippets

To make the whole CI a bit faster through parallelism

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 68.814%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
3760

Relevant Lines:
5464

💛  - Coveralls


[pybind11] update to 2.6.2

Library name:pybind11
New version number: 2.6.2
https://github.com/pybind/pybind11/releases

Duplicate of #17885


Moves to Jitpack for service manager and cleans logs

This makes logging more succinct and clear, especially when grepping for 'since'
pinot                   | 08:46:22,986 INFO  [main] command.StartServiceManagerCommand (StartServiceManagerCommand.java:285) - Starting a Pinot [SERVICE_MANAGER] at 0.007s since launch
pinot                   | 08:46:27,220 INFO  [main] command.StartServiceManagerCommand (StartServiceManagerCommand.java:287) - Started Pinot [SERVICE_MANAGER] instance [ServiceManager_20da8f16c3fb_7098] at 4.242s since launch
pinot                   | 08:46:27,246 INFO  [main] command.StartServiceManagerCommand (StartServiceManagerCommand.java:285) - Starting a Pinot [CONTROLLER] at 4.268s since launch
pinot                   | 08:46:32,430 INFO  [main] command.StartServiceManagerCommand (StartServiceManagerCommand.java:287) - Started Pinot [CONTROLLER] instance [Controller_20da8f16c3fb_9000] at 9.452s since launch
pinot                   | 08:46:32,432 INFO  [Start a Pinot [BROKER]] command.StartServiceManagerCommand (StartServiceManagerCommand.java:285) - Starting a Pinot [BROKER] at 9.453s since launch
pinot                   | 08:46:32,432 INFO  [Start a Pinot [SERVER]] command.StartServiceManagerCommand (StartServiceManagerCommand.java:285) - Starting a Pinot [SERVER] at 9.453s since launch
pinot                   | 08:46:35,755 INFO  [Start a Pinot [BROKER]] command.StartServiceManagerCommand (StartServiceManagerCommand.java:287) - Started Pinot [BROKER] instance [Broker_20da8f16c3fb_8099] at 12.777s since launch
pinot                   | 08:46:35,972 INFO  [Start a Pinot [SERVER]] command.StartServiceManagerCommand (StartServiceManagerCommand.java:287) - Started Pinot [SERVER] instance [Server_20da8f16c3fb_8098] at 12.993s since launch
pinot                   | *** Starting schema installation at 15s since container launch
pinot                   | *** Completed schema installation at 17s since container launch

adding more specific logs to CI so we aren't accidentally counting time spent pulling kafka

LGTM

GitHub Action:
sut                | *** Completed schema installation at 33s since container launch

CircleCI
*** Completed schema installation at 52s since container launch

ok I think this will help us debug. I noticed on my laptop, if I only allocate 2GB to docker, startup takes almost a minute sometimes longer. If I allocate 6GB it is quite fast.
Merging so we can use similar debugging in hypertrace/hypertrace


'Image' has no propType for native prop 'RCTImageView.overlayColor' of native type 'number'

I'm getting this error. I'm using version 0.20
I'm not using Image in my code. I'm just running the "Welcome to React Native" program.

Uninstalled the app from the phone and reinstalled all the npm modules again. Now, It is working fine.


[common] Support bitmap file index

Purpose
support bitmap file index

Tests

API and Format

Documentation
Introduce bitmap file index

+1

+1


new Raspotify , no sound on HDMI with Pi Zero

Compatible OS

[X] I'm running Raspotify on a compatible OS

Latest Version

[X] I'm running the latest version of Raspotify

Due Diligence

[X] I have done my due diligence

What happened?
I installed Raspotify on Pi Zero W with only HDMI Cable Output.
But there is no Sound.
On Speaker-Test there is no such Device
Relevant log output
No response

There's a section in the wiki that will walk you though how to configure your default sound device for your Pi.
Look under the part that says:

My Raspberry Pi does not use my USB sound card!

I know you're trying to get sound to work over HDMI but the steps are same.

Hi,
i do these steps. , but there’s no sound.
It’s an PiZero W 2 and connected via HDMI to an AVR which is on.
Von: Jason Gray @.>
Gesendet: Donnerstag, 27. Januar 2022 00:11
An: dtcooper/raspotify @.>
Cc: andiandi69 @.>; Author @.>
Betreff: Re: [dtcooper/raspotify] new Raspotify , no sound on HDMI with Pi Zero (Issue #505)
There's a section in the wiki https://github.com/dtcooper/raspotify/wiki/Troubleshooting  that will walk you though how to configure your default sound device for your Pi.
Look under the part that says:
My Raspberry Pi does not use my USB sound card!
I know you're trying to get sound to work over HDMI but the steps are same.
—
Reply to this email directly, view it on GitHub https://github.com/dtcooper/raspotify/issues/505#issuecomment-1022687245 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOWTQZ3B2QDUOD7V64PKTDUYB5RLANCNFSM5MYCFYWA .
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675  or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AXOWTQZB3SGWA5VOTVD7DWTUYB5RLA5CNFSM5MYCFYWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHT2PQDI.gif Message ID: @.*** @.***> >
--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

I would look into this thread:
https://forums.raspberrypi.com/viewtopic.php?t=313124
This is not a Raspotify specific issue, but rather a general audio configuration issue.


Use the ament_cargo build type

The rclrs_crate_config_generator is superseded by colcon-ros-cargo.
The ament_cmake_export_crates mechanism is subsumed by creating entries in the ament index directly in the rosidl_generator_rs and cargo-ros-install.

@esteve @jhdcs @mxgrey This is waiting on https://github.com/colcon/colcon-ros-cargo/pull/1, but I expect no major changes to this part, so I'm inviting reviews.

@jhdcs for first time contributors, we need to run the CI manually, I've just triggered it.
@nnmm thanks for this amazing work, I'll try to run this today or tomorrow at the latest

@nnmm CI is failing, could you update the CI config to skip the packages that no longer exist? Thanks

@nnmm t's not about missing packages, but the two-stage build process (colcon-ros-cargo needs to be built & sourced first).

You're right. We can install the colcon plugins via pip and then use the GitHub action with the repos file as it was, if you're ok with that, I'll make a couple of changes to the CI and see if it works.

@esteve You're right. We can install the colcon plugins via pip and then use the GitHub action with the repos file as it was, if you're ok with that, I'll make a couple of changes to the CI and see if it works.

@nnmm turns out I can't install colcon-ros-cargo directly with pip because the setup.py file in the repo is not in the root directory. Would you be ok with moving colcon-ros-install to its own repo in the ros2-rust organization and have colcon-ros-cargo only for the Python package? I've noticed that all the other colcon plugins have that directory structure (e.g. https://github.com/colcon/colcon-ros, https://github.com/colcon/colcon-gradle, etc.)

@nnmm I've added a step in the CI to install cargo-ament-build now that it's available in crates.io, this should fix any issues in the CI

@nnmm one more commit to remove ament_cmake_export_crates and colcon-ros-cargo as dependencies from the package.xml files to make rosdep happy

@esteve Can you mark the rolling job as allowed to fail? Jacob wanted to land the fix for that after this PR.

@nnmm I've disabled the Rolling job because even if a job is marked as continue-on-error, the workflow will still be marked as failing. We can reenable Rolling once the rcl issue is fixed.

I'll take a look at that error. I also think a failed cargo build shouldn't throw an uncaught exception, so I'll fix that.

@esteve Could I get permission to kick off workflows?

@nnmm bravo! :clap:  :clap:  :clap:


Getting error "rule.params.trim is not a function"

When we run our less files through stylelint, we were getting an error about mixin rules.  We updated to the latest version of all our npm packages and got a different mixin rule error.  After adding your recommended postcss config (mixinsAsAtRules: true, innerMixinsAsRules: true), we're now getting an error that says "rule.params.trim is not a function"
It still appears to render warnings from stylelint, so I think it's more of an annoyance at the moment.
Let me know how I can help track that down, if it's not already a known issue.

@bdukes, thank you! This issue is related to https://github.com/webschik/postcss-less/issues/25


Idva6 1147 update and role and remove

Short description outlining key changes/additions
Added PATCH /acsp-members/{id}
JIRA Ticket Number
IDVA6-1147
Type of change

[x] Bug fix
[x] New feature
[ ] Breaking change
[ ] Infrastructure change

Pull request checklist

[x] I have added unit tests for new code that I have added
[x] I have added/updated functional tests where appropriate
[x] The code follows our coding standards

An exhaustive list of peer review checks can be read here

CI: Security warnings found!

CI: Security warnings found!


UnmarshalFromString can't Unmarshal empty string.

for example:
func Test_customize_field_by_extension(t *testing.T) {
	should := require.New(t)
	cfg := jsoniter.Config{}.Froze()
	cfg.RegisterExtension(&testExtension{})
	obj := TestObject1{}
	err := cfg.UnmarshalFromString(``, &obj)
	should.Nil(err)
}

expect: err is nil, but err: "Read: unexpected value type: 0, error found in #0 byte of ...||..., bigger context ...||..."。
can't understand this error is a valid case?

An empty string is not valid json. The stdlib throws an error as well: unexpected end of JSON input.

can't understand this error is a valid case?

To answer your question, yes this error is valid.


binary search fixes

Closes #443
Closes #362

Fixes an infinite loop due to floating-point roundoff when distance to nearest neighbor is greater than tolerance.
Removes the tolerance argument, because the algorithm terminates when the argument stops changing.
Bounds on binary_search have been made optional via exponential search
Exponential search bounds increase magnitudes incrementally, which avoids issues with overflow
Exponential search bounds should converge in fewer steps, under the assumption that ideal parameters are typically distributed closer to zero
Added a T argument to specify expected type

T is also inferred by catching TypeErrors and "No match" FFI errors
Replaces AssertionErrors that have to do with typing with more informative TypeErrors

Looks great; thanks!!

BTW, would it be possible to get a release for this?  I would like to up the dependency for our synthesizers, since it looks like we are running into the issue when people use large epsilon


WIP: Networks drivers to persist endpoints

And reserve again their port bindings (bridge only)
Signed-off-by: Alessandro Boch<EMAIL_ADDRESS>

Closing in favor of #1244 which will include al lthe changes needed in libnetwork for the daemon restart case.


when select side menu item than canter view issue

it's only happen in iOS 11 and above

using safe area.

@test-ineed
There appears to be a critical range with the contentScale property of the TransitionOptions that causes the odd behavior. When using a contentScale of 0.87 - 0.90, there seems to be an issue with the content controller's view not getting its safeAreaInsets set properly. From testing, I can only see it affecting those four values in that range.
I will continue to look into the issue but, for now, I will update the default value of the contentScale to be outside of this range so that the library works on iOS 11 by default
For now, you can change the transitionOptions to be outside of that range and you should see things improve.

@test-ineed
Try using 2.2.1.  The default contentScale was changed to be outside of the affected range that causes the safeAreaInsets not to be set properly on the content controller.
I will still be looking into this issue to see how I can make things work no matter the contentScale setting but this is the best I can do for now.


Private addresses in log4j.txt

Hi! Thanks for dealing with the private addresses in #3.
I noticed this morning that a few more have snuck in.
https://github.com/CriticalPathSecurity/Public-Intelligence-Feeds/blob/92faf0015b87eea95446832d4d1059e89b4f3be8/log4j.txt#L7511-L7513

Thank you, @iainelder for notifying me!
I've adjusted the filter and you should see those removed going forward.


CKS: remove details when delete a cks cluster

Description
This PR removes the cks cluster details from kubernetes_cluster_details table, when the cluster is removed.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[x] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

@blueorangutan package

@rohityadavcloud a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 5327

@blueorangutan test keepEnv

@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-5907)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 39610 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7104-t5907-kvm-centos7.zip
Smoke tests completed. 100 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_08_upgrade_kubernetes_ha_cluster
Failure
562.41
test_kubernetes_clusters.py

tested in a lab env, details are removed, merging


Support multiple network interfaces

I want to help with developing this plugin.  Specifically I want to add support for dehumidifier I bought.  I made a start by forking a different project and made significant updates to it (so it can work entirely on LAN and not need to connect to Midea cloud servers).  That work is here... homebridge-midea-lan.
But I much prefer how you are going about it (not having a dependency on the midea-beautiful-air python package for a start). So want to help improve your plugin with some of the things I learned.  First step is this... if you have multiple network interfaces then you cannot broadcast to <IP_ADDRESS>, you need to broadcast to each subnet separately. This pull request does that.
Thanks!

not ready to merge


d1: Update local-development.md

This PR:

Makes it clearer how to test D1 programmatically (as a start)
Links out to the unstable_dev docs at https://developers.cloudflare.com/workers/wrangler/api/

Spell check is wrong :)


filterlist doesn't display when severside option is set to true

Expected Behavior
When table option serverside is true and added some filterList on column options - I should be able to see it when rendered.
Current Behavior
filterList doesn't display when rendered.
Steps to Reproduce (for bugs)
https://codesandbox.io/s/muidatatables-custom-toolbar-kosjv

When serverSide is true, you have to use serverSideFilterList to designate which filters show in the interface. See the serverside-filters example. The code needed some way to split how to treat filters, and the single flag for serverSide wasn't enough because filters are currently serving double duty (they both designate what is filtered and show it visually, but with serverside, you don't want to show it before the requests are successful).

Closing this, thanks @gabrielliwerant


594% pledge in aid packages view

[ ] 594% pledge in aid packages view. Should only be able to pledge 0-100% of the aid package value / need.

so if the pledge is more than 100% should it show 100%? cuz the percentage is correct, right? It has received more than the pledge.

It should only allow 100 percent of the funds to be pledged and display a message for anything over the 100per cent value.

@anjula-sack I think this has to be validated in the backend (the frontend is already validating it)
What might have happened is some have updated values from the database.
@anupama-pathirage @AmilaJ @manuranga
Can we clean up those values for now?

Agree, let's clean this up for the demo please.

Still showing  the error. Take a look at the Goal figure. The goal is $20,000 USD, but when you add up the total cost of the medicines in the automatic post is 148,000+ Check this as the source of the error (why the percentage is 724%.

[ ] Validation: we should not let users come up with a total value that is less than the received amount
[ ] Extra field for 'total value' @nshamit to speak to business stakeholders about this one.
[ ] Should not let users edit values after closing the package

We need backend validations for the above.

@manuranga Please assign someone from the BE team

We keep getting Already done Pledges amount exceeds the Aid Package Item Quantitiy Update for any quantity update.

as recorded in #468


Silencing more MSVC warnings

Since sol2 already silences some MSVC warnings, these might also make sense to silence:

C4702, unreachable code. Can be triggered by sol::optional.
C4503, the decorated name was longer than the compiler limit (4096), and was truncated. You will get this pretty quickly already with a small API and the generated warnings are super long, so they just make the build noisy.

I already silence C4503, but it's based on where the user generates the templates (outside of my code). You'd need to silence that one.
C4702, I haven't gotten that warning. Can you give me an example?

I already silence C4503, but it's based on where the user generates the templates (outside of my code). You'd need to silence that one.

I'm aware that silencing it in sol.hpp alone does not get rid of all generated warnings, but some. I cannot exactly tell when it helps and when it doesn't, it probably depends on functions are exactly being used. So I think it wouldn't hurt.

C4702, I haven't gotten that warning. Can you give me an example?

There is one that's trivial to fix in static int real_index_call_associative(std::false_type, lua_State* L) because it has an if..then..else block that returns something in all cases, but then there's another return afterwards.
The other warnings I get from OPTIONAL_MUTABLE_CONSTEXPR T& value() & in sol::optional. I'm not using SOL_NO_EXCEPTIONS.
This is with Visual Studio 2015.

I'll add these around the library's code.


JumpBoxConvig.ps1 compilation issue

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ X ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Deploy terraform-azurerm-vnet-app

Any log messages given by the failure

Job was suspended due to an internal error. Please retry after sometime.

Expected/desired behavior

Configuration should apply with no errors.

OS and Version?

Windows Server 2022

Versions

#AzureSandbox v2.10.1

Mention any other details that might be useful

There are breaking changes in Azure Automation DSC which is causing DSC compilations to fail.

This was a transient issue with Azure Automation DSC service health that resolved after 48 hours.

Issue has re-appeared due to an Azure Automatino DSC regression. Permanent mitigation required.

Need to apply these same changes to extras/terraform-azurerm-vnet-onprem


Deprecate HttpSensorAsync

Deprecate HttpSensorAsync

Note: bump http provider too https://github.com/astronomer/astronomer-providers/blob/main/setup.cfg

Ran example DAG to verify DAG is doing in deferred state


SIMPLE CAT MOBILE APP

Challenge Add Images to your Website has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
 Your code seems to be correct.
Here are a couple suggestions:

Reload the page and run the tests again. A script may have crashed, preventing the tests from running.
Try the challenge in incognito mode. A plugin might be interfering with the tests.
Try the challenge in a different browser. There may be an issue with your version of browser.

Please try these things in order and let us know what did and didn't work. I can't reproduce your issue right now, so any extra information will be helpful in finding out what's causing your issue.

Its fine! It was just a break due to internet failure.
Thanks for the prompt response!


add kubeadm cluster support to kne deploy

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

6 of 102 (5.88%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.9%) to 65.565%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

deploy/deploy.go
6
102
5.88%

Totals

Change from base Build<PHONE_NUMBER>:
-0.9%

Covered Lines:
4343

Relevant Lines:
6624

💛  - Coveralls

TODO: add tests


Update README.md

I signed it!
On Fri, Jun 14, 2019 at 9:34 PM googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project (if not, look below for help).
Before we can look at your pull request, you'll need to sign a Contributor
License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here (e.g. I
signed it!) and we'll verify it.
What to do if you already signed the CLA Individual signers

It's possible we don't have your GitHub username or you're using a
different email address on your commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.

Corporate signers

Your company has a Point of Contact who decides which employees are
authorized to participate. Ask your POC to be added to the group of
authorized contributors. If you don't know who your Point of Contact is,
direct the Google project maintainer to go/cla#troubleshoot (Public
version https://opensource.google.com/docs/cla/#troubleshoot).
The email used to register you as an authorized contributor must be
the email used for the Git commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
The email used to register you as an authorized contributor must
also be attached to your GitHub account
https://github.com/settings/emails.

ℹ Googlers: Go here
https://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Fgoogle-research%2Ffootball%2Fpull%2F15
for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google-research/football/pull/15?email_source=notifications&email_token=AEZOISTGQC2ZPOWRVXEG7RDP2O6RXA5CNFSM4HYJGH72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXXHLGQ#issuecomment-502166938,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEZOISUXSQHIMGNNXNEHRE3P2O6RXANCNFSM4HYJGH7Q
.

Thanks a lot Sahil!  To merge this change (since it's the first pull request to football repo) we need to make sure our import workflow works.  I plan to verify it on Mon/Tue.


[DO NOT MERGE] add categories

fix #13

rename groups to categories
rename categories
add categories to singlepage view5

I would like to add the categories to the front page as well but I suggest we wait until the other PRs are merged so that we really see how it would look like.

please do not merge this PR until the Home app is modified accordingly.

@yakutovicha Alright.
By the way, let me know how you want to have the categories - I can easily add it at the top level of the apps_meta.json output of the app registry (currently only has one key "apps").
This way you don't have to deal with multiple files.

By the way, let me know how you want to have the categories - I can easily add it at the top level of the apps_meta.json output of the app registry

The apps_meta.json file generated by app-registry I don't really touch/need. The apps_meta.json which is used by the App Store is generated on AiiDA lab directly.
However, the question still remains: do we need to merge the information from apps.json and categories.json. Probably yes, if we need to pull this information by HTTP request - better to have a  single file. Having one HTTP request and one file that will be cached is better then two. I do not see an advantage in pulling two files.

I do not see an advantage in pulling two files.

In getting the file there is no advantage, but it does make sense to keep the metadata of description and the metadata of apps separate (rather than putting both in one file and introducing an additional nesting in the json).
Combining 2 GET requests into 1 does not really matter when you have N times ... get requests for fetching metadata from every app.

@yakutovicha Should be ready for you to merge

@yakutovicha Should be ready for you to merge

Looks like you did the other way around: you removed  space symbols instead of 'Tab'. Could you please redo it? Just replace 'Tab' with 8 spaces.
Thanks

thanks @ltalirz


Allow for 'DEBUG' statement when running the tests

Having an environment variable similar to ALMIGHTY_RESOURCE_DATABASE or ALMIGHTY_DEVELOPER_MODE_ENABLED to set the logger level to DEBUG would be interesting, especially when working on tests that fail.

This seems to be related to the tests initialization, I can fix that

Great! Thanks, @hectorj2f !

This can be closed. It was addressed in #1192


Update secretserver-on-premises-tutorial.md

This doc calls out that this integration works only for on-prem Secret Server. That is inaccurate and this works for both on-prem and Cloud versions of Secret Server

@jeevansd
Can you review the proposed changes? Note that the validation warnings must be resolved before merging.
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@Court72 @jeevansd can this be merged?

Hi @tylerezimmerman, Please submit an update request in our portal to remove (on-premises) from the application name in your gallery listing first then once the listing is renamed in entra, our team will update it in the tutorial as well. If you face any access related issues for submission, please reach out to SaaS apps team or App workflow team

Hi @tylerezimmerman, Please submit an update request in our portal to remove (on-premises) from the application name in your gallery listing first then once the listing is renamed in entra, our team will update it in the tutorial as well. If you face any access related issues for submission, please reach out to SaaS apps team or App workflow team

Gentle reminder, Please see my comment above.
#please-close


API Request - id_changed_object_type/action

Environment

Python version:  3.5.2
NetBox version:  2.5.8

Proposed Functionality
From what I can tell, there is no way to pull possible values for "id_changed_object_type" ("content_type") for the changelog via API (/api/extras/object-changes/), and the "action" field only lists available ids without a description of said id (e.g. 1 = Created, 2 = Updated, 3 = Deleted)
I propose, if possible, to add the available options for "changed_object_type" and/or "action" under "/api/extras/_choices/", or a new "/api/extras/object-changes/_choices/" path with both an id and description/name.
Also, the "content_type" does not show up with a Get request on "/api/extras/object-changes/", so you cannot filter after the fact based on object type.

Use Case
Currently, in order to determine the id value of the object type for a change log entry, you would have to go to "/extras/changelog/" (not the API), select the object type you want to filter by, and look at the URI for "changed_object_type=#" (or inspect the dropdown field) for possible options.
It would be beneficial to gather the options via API, rather then hard coding the options and having them change.

It looks like the content type values I would be looking for are pulled via the SQL table: django_content_type.

Corrected action to use ChoiceField serialization and added its key/value pairs to the _choices endpoint.
While the serializer had a content_type field defined, it was not being included in serialized output for some reason. I've changed this to changed_object_type and it now includes the content type of the changed object. (The content types are not included under the _choices endpoint.)

Thank you for correcting/adding these. However, it appears their may be a bug with the new changed_object_type field, specifically when trying to pull records that are of a "template" object type (power port template and interface template are two I seemed to have narrowed it down to, possibly others).
When trying to pull these types records from the generic [/api/extras/object-changes/] and directly via [/api/extras/object-changes/id/] I receive the following server error (code 500):

Server Error

                            Server Error

                            There was a problem with your request. Please contact an administrator.

                        The complete exception is provided below:

<class 'utilities.api.SerializerNotFound'>
Could not determine serializer for dcim.InterfaceTemplate with prefix 'Nested'

                        If further assistance is required, please post to the NetBox mailing list.

                        Home Page

Should I open a new issue for this?

Please open a new issue for this


A Readme update

Description
This changes the instruction on how to set the BotFramework-Composer on a local machine using the command line from $ cd Composer to $ cd BotFramework-Composer because I tried the former and it didn't work for me.
Type of change

[x] Doc update (document update)

Checklist

[x] I have added tests that prove my fix is effective or that my feature works
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have functionally tested my change

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


Add a test tagging system and mark some tests important

The "important" subset is roughly 4x faster than the whole test suite. Note the command-line option only works on Python 3.4+.
This PR also takes the opportunity to remove some duplicate or irrelevant tests (for example all tests of type-specific ufunc loops in object mode).

I like the idea of defining subsuites of tests, in particular in conjunction with more advanced CI use-cases. However, I'm not quite sure that tagging tests themselves for this is the best approach - it doesn't scale well. Wouldn't it be possible to define synthetic test suites that contain the desired tests ? Then, instead of running runtests.py --tags=... one would simply invoke runtests.py my_special_test_suite.
Either way, I think this feature is useful enough to be part of numba.testing (rather than just numba.tests), in case we want to use it elsewhere, too.)

I think a separate synthetic test suite would be even more work. In any case, both approaches need some maintenance.
As for putting the feature in numba.testing, yes, will do!

OK, the general infrastructure looks good. I have no opinion on the individual attribution of the 'important' tag to tests.


Dark Mode

Assign this issue to me i will add darkmode feature to the app

@sainiteshb Dark Mode is already available in the app. You can create a new issue which is not already assigned. Closing this issue as mentioned.


Feature: Config script

Great browsers you've made! But it would be nice to see a config file where keybindings, download location , etc can be configured. It would be even better if the values configured can be the stdout of a command to be executed. Also,I also want support for additional plugins which may choose to support configuration via config script , like adblockers,  which was mentioned in another issue. Thanks for the great work! Edit:I also want a small bar at the bottom where URL is displayed but commands can also be typed.

Thanks for bringing this up. At some point I intended on adding scripting by using Deno, but it greatly increased the size and the amount of work involved was a little too much for a hobby project like this that I don't often have time for.

Is it possible you bring in some other devs? This project would be very useful. Also, how do you go back and forth in history, view history, etc? What are the keybindings for that? Also, when given a non valid URL could you make it search in a search engine and display everything text based for the search only.

This is a hobby project but it is open source, so anyone with the time and ability can contribute.
The keybindings are the default keybindings in Chromium.
This wasn't intended to be used as a primary browser, more like a complementary tool that can display modern web pages, like displaying Markdown, documentation, etc. That said, you're welcome to provide a pull request that does these things.

Okay. thanks!


To be able to get the html of the body text extraction section

Allows the user to retrieve the original HTML of the markdown after the body text is extracted.

Please come up with a better function name idea.


Add and prefer OSSL_HASH instead of lh_ prefix?

Should OpenSSL stop using lh_ to stop namespace collision?  There's about 120 used internally, and we could keep the lh_ names for compatibility.

BTW sk_ is over 2500 uses, so that's a bigger issue if you want to address it.

A question, are you talking about actual observed collision, or is that hypothetical? That will affect how this gets prioritized.

I suspected that, obviously.
The understanding so far is to use OSSL_ as a prefix for new modules... I'm frankly apprehensive of converting already existing APIs unless there are actual clashes (also, we can argue that "we were there first" 😉).
But not to be entirely dismissive, it's still something to consider some time...

I would do it by adding the new names and then later on removing the old ones.
If you're willing, i can make a PR to do part 1.

seems like this won't get planned
marking as inactive, to be closed at the end of 3.4 dev barring further input

No interest and I don't care since apparently it's not affecting any downstream users. Closing this.


Mopping brokey as of today

you can no longer mop as a player, you can mop as an aghost

Likely dupe of https://github.com/space-wizards/space-station-14/issues/11736#issuecomment-1270854435


Why is a descriptor.ts generated?

Hello, when I run
npx protoc --ts_out . --proto_path proto proto/project.proto
I get

project.client.ts
project.ts
descriptor.ts

descriptor.ts doesn't seem to be needed by either project.ts or project.client.ts. My question is why is it generated? Is there a role for this file that I'm not seeing?

Hey Eric,
I just ran the quickstart and end up with this tree:
$ tree -L 2 --noreport
.
├── msg-readme.ts
├── node_modules
│   ├── @protobuf-ts
│   └── typescript
├── package-lock.json
├── package.json
└── protos
    └── msg-readme.proto

I don't know where descriptor.ts is coming from in your case. If you think it is a bug, we'll need a bit more details 🙂

So I ran the quick start, then used my project.proto and annotations.proto. In annotations.proto, it uses some of the google api stuff. I'm assuming its just the way protobuf-ts parses and generates the .ts files, but I don't really need the descriptor.ts that it generates.
.
├── node_modules
│   ├── @protobuf-ts
│   └── typescript
├── package-lock.json
├── package.json
└── protos
    ├── annotations.proto
    ├── google
    │   └── api
    │       ├── annotations.proto
    │       └── http.proto
    └── project.proto

This might be related to the logic here: https://github.com/timostamm/protobuf-ts/blob/3a7ce47d43113d1a80cacd0ae70630b3727eda3e/packages/plugin/src/protobufts-plugin.ts#L348-L373
It should omit descriptor.proto in your case.
This needs more investigation.

Just a little bit more info that may help.
I installed npm install @protobuf-ts/plugin
Command I use: npx protoc --ts_out out --proto_path . project.proto
This gives me:

project.client.ts
project.ts
google/protobuf/descriptor.ts (this is the unnecessary one)

In project.proto, there is a
syntax = "proto3";

import "annotations.proto";
...

Then in annotations.proto, there is a
syntax = "proto3";

package google.api;

import "google/api/http.proto";
import "google/protobuf/descriptor.proto";

option go_package = "google.golang.org/genproto/googleapis/api/annotations;annotations";
option java_multiple_files = true;
option java_outer_classname = "AnnotationsProto";
option java_package = "com.google.api";
option objc_class_prefix = "GAPI";

extend google.protobuf.MethodOptions {
  // See `HttpRule`.
  HttpRule http = 72295728;
}

The generated project.client.ts, has what's expected like so
import type { RpcTransport } from "@protobuf-ts/runtime-rpc";
import type { ServiceInfo } from "@protobuf-ts/runtime-rpc";
import { ApiService } from "./project";
...

Finally in project.ts, it has this
import { ServiceType } from "@protobuf-ts/runtime-rpc";
import type { BinaryWriteOptions } from "@protobuf-ts/runtime";
import type { IBinaryWriter } from "@protobuf-ts/runtime";
import { WireType } from "@protobuf-ts/runtime";
import type { BinaryReadOptions } from "@protobuf-ts/runtime";
import type { IBinaryReader } from "@protobuf-ts/runtime";
import { UnknownFieldHandler } from "@protobuf-ts/runtime";
import type { PartialMessage } from "@protobuf-ts/runtime";
import { reflectionMergePartial } from "@protobuf-ts/runtime";
import { MESSAGE_TYPE } from "@protobuf-ts/runtime";
import { MessageType } from "@protobuf-ts/runtime";
...

For now I'm just ignoring the file, but yeah need to investigate the logic you posted to see why its generating an unnecessary file.

We need to switch our plugin from @protobuf-ts/plugin-framework to @bufbuild/protoplugin.  This will provide much better capabilities to detect what needs to be generated, and better capabilities to conditionally generate.
Given time constraints, it makes little sense to put work into a fix right now with the current plugin.


Why batch_size =1 ?

I would like to ask why batch_size=1?I believe this may be the best result of tuning parameters, Is it because the model has an image with a gray background?

We do not crop the train data to fixed size when training, the size are different that can't batch to together, so we forward one image each iteration. Here, we adopt the itersize=10 which analogs to batchsize=10, ie, forward 10 times and then update the weights.

I couldn't agree with you more.But why did you choose this way instead of resizing the image.Cropping the image size also increases the batchsize and reduces training time.Is the method you used the best result of the experiment?Thank you very much for your answer


URL Format change, site Myhentaicomics.com

Ripme version:1.7.95
Java version:
Operating system: windows 10 (Verison as of 10/10/2023)

Exact URL you were trying to rip when the problem occurred: Expected old URL format (index.php/albumname) got new one instead.
Please include any additional information about how to reproduce the problem: Just copy and paste a link from a comic on there. I found a engaging comic on there that I can't find anywhere else called Limerence, it's the only reason I'm even on the sight.
Curios to see if i can find alternative sources to the gumroad uploads before I get them. This is for those who can't afford to buy the comic up-front. Thanks again for looking over the issue.

Expected Behavior:
download page images
Detail the expected behavior here.
mentioned above
Actual Behavior
Said error message about link format.
Detail the actual (incorrect) behavior here. You can post log snippets or attach log files to your issue report.

it works from here: https://github.com/ripmeapp2/ripme/releases ?


Hack/Tip and a proposal

For my purposes, I needed to dynamically provide the content of drop down lists.
Adding drop down content to the form would not be as nice as just having a function call in the form definition. So I created a file, forms.js in literal JS notation instead of JSON:
var a = {
        key: "groups",
        title: "Groups",
        description: "The groups the user belongs to.",
        add: "New",
        remove: "Delete",
        style: {
          add: "btn-success"
        },

        items: [
            {
                key: "groups[]",
                type: "select",
                titleMap: (scope.groups)
            }
        ]
    }
return a;

and loaded and executed it in the current context with $scope as a parameter;
return $http.get('forms.js').then(function (data) {
        var _form_data = new Function("scope", data.data).call(this, $scope)
}

and voilà, I could load the list of groups or whatever from $scope.groups or wherever.
However, this is not really dynamic as it happens before I click the drop down box, and until that time, there is a much greater risk that groups may have been added and removed. And worse, it is not valid JSON, hence not serializeable unless sent as a strings, which need generation and so forth.
So I looked at the titleMap and the onChange code and came to the conclusion that it should not be terribly difficult to either add an onPopulate attribute to provide data for selects and similar multiple choice widgets. Or just interpret a plain string value for titleMap as an expression to be run in the angular $scope.
That expression could then be called by the UI, populating the widget when used. Any thoughts?

Hi @nicklasb,
I'd rather solve it by creating an addon/custom type, it feels a bit cleaner and doesn't complicate the simple field types. Especially doing some kind of async call would complicate todays implementation. Better to encapsulate that in it's own form type.
It should be pretty straight forward though and it seems like @stevehu is working on something like that here: https://github.com/networknt/angular-schema-form-strapselect

Ok, I will check that out.
Hm, with regards to the async call, you are right, I didn't think about that at all.


Add apps trigger

Toward giantswarm/giantswarm#16664
Adding /test apps into prow.

Also when you roll out: You might need to restart prow / deck pods for this to take effect.


PurgeSiteLog does nothing if portal's SiteLogHistory setting is set to 0

The scheduler PurgeSiteLog does nothing if the portal's SiteLogHistory setting is set to 0.
IMHO the scheduler should remove the existing site log records even if SiteLogHistory is set to 0. Imagine the scenario where the site log was enabled (SiteLogHistory > 0) for some time and site log records were created and the admin disabled the site log by setting SiteLogHistory = 0. With the current implementation the scheduler would not remove the existing records.
I will create a pull request to fix this problem.
This issue was migrated from DNN-7245

I assume you know about https://github.com/dnnsoftware/Dnn.Platform/pull/639

Yes.

I cannot reproduce this issue with current code, if still reproducible after 8.0.1 (tonight or in a few days) release, please open a new issue.


remove checkbox from core

Summary
This is part of the lean core effort. Checkbox was moved into its own package in the community org, and once published, it can be removed from core.
Changelog

[Android] [Removed] - Remove android checkbox from core
Test Plan
CI passes, RN tester works without the example screen for checkbox (I still need to verify this - works locally)

As discussed on discord, I'll likely have to do this from the Facebook side because we probably use this component somewhere so unfortunately I won't be able to merge this PR. Thanks for starting it though, I can base my work off of it later :)


fix(iOS): don't automatically prefix the domain with at . in set() method

Summary
#45 introduced a change for the set() method on iOS to always include a trailing . for the domain (to be in-line with Android).
While this might make sense - it is not intended behavior for iOS and can cause issues.
I use this package to sync cookies from NSHTTPCookieStorage to WKHTTPCookieStore and this change caused issues since the cookie values aren't actually the same anymore.
Example:
export const syncCookies = async ({ url }) => {
  if (IS_IOS) {
    try {
      const cookies = await CookieManager.get(url);
      for (const cookieName in cookies) {
        await CookieManager.set(url, cookies[cookieName], true);
      }
    } catch (error) {
      return false;
    }
  }

  return true;
};

I think we should stick to the default platform behavior and leave this up to the users
Checklist

[x] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

Thanks for the PR @jackmu95!
Any thoughts on this @YoliFD?

@safaiyeh Any update on this?
I still think this is a major bug and should be resolved ASAP.
Running this fix in production for over a month now; without issues :)

Sounds good @jackmu95 thanks for making the PR. I have to move the CI pipeline to this new org first before I can merge it in, ill merge this in once I can

:tada: This PR is included in version 6.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 6.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

@safaiyeh is there any reason that we still add a trailing . on Android ? I pretty much have the same issue than @jackmu95 where I wanna get cookies, clear all of them, and re-set some of them (it's actually the only way to remove only some cookies as clearByName is iOS only), and they end up not being the same because of the trailing . at the beginning, shouldn't this be up to the user ?


[Suggestion] How about a Slack or Gitter group ?

I feel this way a lot of us can help each other

While I don't really like the idea of Slack for Open Source projects, there is an IRC channel on Freenode #staytus. I'm usually around in there.

Haha. Well Slack looks cool. IRC is way too old man. How about we use Raspchat if I can get in configured on a server ?

It might be old but it does the job pretty well. I have an existing IRC client open. I'll never be there if I have to open another. This article explains my feelings about it :)
http://sircmpwn.github.io/2015/11/01/Please-stop-using-slack.html
Adam Cooke
Managing Director
tel. 01202 912 446 email. adam<EMAIL_ADDRESS>web. https://atech.media
This e-mail has been sent by aTech Media Limited (or one of its assoicated group companys, Dial 9 Communications Limited or Viaduct Hosting Limited). Its contents are confidential therefore if you have received this message in error, we would appreciate it if you could let us know and delete the message. aTech Media Limited is a UK limited company, registration number 5523199. Dial 9 Communications Limited is a UK limited company, registration number 7740921. Viaduct Hosting Limited is a UK limited company, registration number 8514362. All companies are registered at Unit 9 Winchester Place, North Street, Poole, Dorset, BH15 1NX.

@maxpert


Fix Segmentation sample nightly testing failure

Fix the Segmentation failure in #7797
It was not seeing the nanopb in SpecsDev required by the podspecs in master.

Yes. The sample test should always build in CI and we depend on the other repos if we want to integration dependent pods like nanopb, GDT, and GoogleUtilities.


Sometimes scrollbar in cash flow disappears

When toggling between pages, the page scrollbars on the cashflow don't always appear.  To make them reappear, you can unmaximize and remaximize the window, which indicates this is probably an event issue.

Related issue from a user:

I’m in PV, Detailed, Commercial Distributed and sometimes am not be able to see the bottom of the System Costs tab. I just clicked around to check other tabs, and when I returned to System Costs I could see the bottom. Just a heads up that it’s buggy I suppose. Thanks for all your work!

This is fixed. See https://github.com/NREL/SAM/issues/405.


Feature Request: Support asymmetric kernel sizes in conv2d()

Title is self-explainatory: Is there any way to get asymmetric (e.g. non-nxn) Kernels in the conv2d op?

This will be fixed today by https://github.com/PAIR-code/deeplearnjs/pull/67.
We'll be releasing 0.2.0 today once this PR is done (Daniel is writing unit tests now).


CrateDB Caching behaviour

There's almost no documentation about the CrateDB caching behavior, still it has a huge impact on the performance of CrateDB and the experience of its users.
As this is mostly inherited from lucene and elasticsearch components, there is documentation available.
In CrateDB the Node Query Cache is a thing:
https://www.elastic.co/guide/en/elasticsearch/reference/7.x/query-cache.html
Also the Shard Request Cache
https://www.elastic.co/guide/en/elasticsearch/reference/7.x/shard-request-cache.html
At one point there was an overview for elasticsearch 2.x
https://www.elastic.co/guide/en/elasticsearch/guide/2.x/filter-caching.html

Also the Shard Request Cache
https://www.elastic.co/guide/en/elasticsearch/reference/7.x/shard-request-cache.html

CrateDB does not implement a shard request cache


Configuration for Kasa TP-Link KP303 smart power strip

Hi,
First TP-Link device for me.  Ran the default installation.  Reboot etc.
Homebridge logs don't throw any errors.  It initializes the plugin it would seem.
But no devices magically appear in Homebridge accessories.
They do show up on the KASA app just fine.  And seems to work.
My other Homebridge WEMO and Harmony plugins work fine.
Now thinking I may need to update the Config for homebridge-tip-link-powerline with more information.
It only shows the below from the boot log (the MAC and SN listed below has been XX for paranoia).
I've tried to find some documentation, or examples to get started.
Hints?  Help?
Here is my JSON config:
            "name": "TP-Link Powerline",
            "devices": [
                {
                    "mac": "XX-XX-B8-94-36-85",
                    "serialNumber": "2213338000XXX",
                    "model": "KP303"
                }
            ],
            "platform": "TpLinkPowerline"

I think this is not the plugin you're looking for. Try this instead?
https://github.com/plasticrake/homebridge-tplink-smarthome

Absolutely correct!  Thank you very much.  I installed this plugin and it works.  Just like magic.  Made my day.


Unhandled exception: PathNotFoundException: Directory listing failed, path = 'android/app/src/main/kotlin*' (OS Error: The system cannot find the path specified. , errno = 3)

If there is no any kotlin folder, it's throwing error:
Unhandled exception:
PathNotFoundException: Directory listing failed, path = 'android/app/src/main/kotlin*' (OS Error: The system cannot find the path specified.
, errno = 3)
Screenshot of the error:

i have same error

I created a Kotlin folder inside the main folder, and it worked.

Are you using the latest version of this package? This sequence of output should not occur in the latest version and I previously added checks to handle these scenarios where kotlin directory does not exist.


add support for tokenized access on engine image pull

https://github.com/perftool-incubator/crucible/pull/388

https://github.com/perftool-incubator/crucible/pull/390

Another step forward: https://github.com/perftool-incubator/crucible/pull/416

Remotehosts support has been resolved by https://github.com/perftool-incubator/rickshaw/pull/568.  Still need to handle other endpoints.


[Community] Nominating Xiaozheng Zhang (GithubID: zhang-x-z) for Fluid committer

Dear Fluid TOC members and maintainers,
I am proposing to have Xiaozheng Zhang (GithubID: zhang-x-z) as a new Fluid committer.
Xiaozheng Zhang, now is a master student in Nanjing University, focusing on distributed stream processing engine. He is working on acclerating states access in cloud-native stream processing system with distributed cache.
The commit history:  Commits · fluid-cloudnative/fluid · GitHub
Part of his recent commits:
Mar 1, 2024
fix mount point validation for vineyard runtime
Jan 21, 2024
Integrate Fluid with Kubeflow Pipline
Jan 12, 2024
Fix incorrect conversion between integer types
Dec 25, 2023
validate the env variable MOUNT_ROOT
Talks/Presentations/Blogs
How to use Fluid in Kubeflow Pipelines - YouTube
Major contributions
Bug Fix:
Fix alluxio dataload bug
Optimization:
fix mount point validation for vineyard runtime
Fix incorrect conversion between integer types
Feature:
Integrate Fluid with Kubeflow Pipline
Security:
OS Command Injection for Fluid Users with JuicefsRuntime · Advisory · fluid-cloudnative/fluid
Fluid 0.9.0:
Adapt to libfuse 3

+1

+1

+1

+1

+1


FEAT: Adding crescendo

Description
Adding the code for Crescendomation to PyRIT

Tests and Documentation

Closing in favor of this: https://github.com/Azure/PyRIT/pull/275


Added Two more Search Technique

Update the Searching section by adding two most popular Searching technique for non-linear Data.

Depth First Search
Breadth First Search

Hi, Please read the Important Announcement.
PR can only be made after the issue is assigned to you.


Return JS Date instances instead of UNIX timestamps

I would like to discuss whether it would be better for the API to return JS date instances instead of UNIX timestamps. While this may make it slightly slower, it would also make it more convenient to use. In reality, it shouldn't have a significant impact since, on the JS side, timestamps would likely be converted into JS dates regardless. What was the main reason for choosing UNIX timestamps in the first place?

This is a good question.
I choose timestamp instead of Date object because I don't like the way Date object is used in NPM's rrule package. It's obviously doesn't work well with rrule spec, since it doesn't support time zones.
I was thinking about adding luxon, or creating own simple date object with some useful conversion methods like:
class RRuleDate {
  day: number;
  month: number;
  year: number;
  hour: number;
  minute: number;
  second: number:

 toDate(): Date {}

 toUTCDate(): Date {}
}


Fix: Optimize product page static generation

#391
This pull request includes changes to fix the error caused by generateStaticParams in src/app/[countryCode]/(main)/products/[handle]/page.tsx.
Problem:

Production build fails with DYNAMIC_SERVER_USAGE error
Multiple unnecessary API calls during static generation

Fix:

Single optimized SDK call for product handles
Improved error handling
Maintains Next.js caching patterns

LGTM, thanks for the contribution!


Service Fabric -Stateless ASP.Net Core - Support for ASP.Net Core 3.0 gRPC

I had created a Service Fabric project called "Stateless ASP.Net Core" with ASP.Net Core 3.0 WebAPI. I replaced WebAPI code with ASP.Net Core 3.0 gRPC middlewear based on MSDN documentation.
MSDN Documentation link : https://docs.microsoft.com/en-us/aspnet/core/grpc/aspnetcore?view=aspnetcore-3.0&tabs=visual-studio
Is it technically possible to use ASP.Net Core 3.0 gRPC with Stateless ASP.Net Core? If yes, how to configure and use it?

@sansindia85  Please report this to https://github.com/microsoft/service-fabric-aspnetcore/issues.

Moved to Kubernetes. I'm no longer looking into Service Fabric.

when will you complete the private deployment on linux on-premises!


no output on Adafruit LCD

Hello,
is this code compatible with the Adafruit 16x2 LCD backpack?  this uses an MCP23017 decoder.
I'm running on a raspberry pi Zero with Node 19.7.0.
The npm install worked without errors, the code runs without error, but nothing happens on the display.
i2cdetect -y 1 finds the board at 0x20.  my code:
const LCD = require('raspberrypi-liquid-crystal');
const lcd = new LCD( 1, 0x20, 16, 2 );

console.log('Starting');

try {
  lcd.beginSync();
} catch (e) {
  console.log(e);
}
console.log('beginSync');

try {
  lcd.clearSync();
} catch (e) {
  console.log(e);
}
console.log('clearSync');

try {
  lcd.printSync( 'Hello' );
} catch (e) {
  console.log(e);
}
console.log('Hello');

try {
  lcd.setCursorSync(0, 1);
} catch (e) {
  console.log(e);
}
console.log('setCursorSync');

try {
  lcd.printSync( 'World' );
} catch (e) {
  console.log(e);
}
console.log('World');

console.log('Done');

Output is:
Starting
beginSync
clearSync
Hello
setCursorSync
World
Done

hello, this library works with PCF8574 I2C port expander, so I think it's not compatible with the hardware you mentioned, sorry


group related wallet CLI commands together

Use subcommands to group related wallet CLI commands

Closed in favor of #1437


Add QtCore.QSortFilterProxyModel to PyQt5 in _misplaced_members

QtCore.QSortFilterProxyModel was removed from _misplaced_members['PyQt5'] in the latest release.

Thanks!


Emit note when --future-incompat-report had nothing to report

r? @ehuss
(rust-highfive has picked a reviewer for you, use r? to override)

I would personally think that this wasn't necessary (e.g. rustc doesn't print anything saying "there were 0 warnings"). Could you elaborate a bit on why this should be added? (having a blank PR description and a commit message which is simply the PR title isn't too helpful...)

Sorry, I forgot to link to the discussion on the tracking issue: https://github.com/rust-lang/rust/issues/71249#issuecomment-795795706 and https://github.com/rust-lang/rust/issues/71249#issuecomment-795996468
Both @ehuss and @jyn514 had wanted an explicit '0 future-incompat warnings' message when --future-incompat-report is passed, to make it clear that the command is working.

Ok thanks for the link, if it's ok with y'all I figure we can discuss it here rather than continuing on the issue over there?
In my opinion there should be no need to print something out like this (e.g. rustc doesn't print out "0 warnings were found"). Could y'all elaborate, though, as to why you feel like a message is necessary? I could see that while testing you might expect it to have a bug and not work, but for a final form of the feature which is expected to work I would think that no output is translateable to "nothing that I need to do"

I could see that while testing you might expect it to have a bug and not work, but for a final form of the feature which is expected to work I would think that no output is translateable to "nothing that I need to do"

My understanding is that the final product won't have this option at all, and will print out future-incompat warnings unconditionally. I agree at that point printing "0 errors" isn't helpful. But I think explicitly opting into the warnings should confirm that yes it works.

I believe the (stable) experience is intended to be:

Use runs cargo build. This prints a notice that there are future-incompat warnings.
User has two options here:
2a. Run cargo describe-future-incompatibilities --id=xyz
2b. Run cargo build --future-incompat-report

The concern is someone runs cargo build --future-incompat-report, and it doesn't display anything, that could be confusing.
Personally, I still think the --future-incompat-report flag doesn't seem like the right UX. I'm not entirely clear what the use case is for that where the report command doesn't suffice.
If the intent is that people always pass --future-incompat-report, then yea, printing 0 doesn't make sense. But I don't know why someone would always pass that flag.

I'm not entirely clear what the use case is for that where the report command doesn't suffice.

The use case is running this on CI, which may build dependencies that a user machine typically does not (e.g. platform-specific dependencies like winapi). Instead of making scripts try to extract the report id from a human-readable message, we provide a flag that can be added to every command invocation.

I was not under the impression that Cargo would print "you have future incompat warnings" by default. I thought that users would have to opt-in to the notifications. Seems like it would be best to clarify that point about the expected usage before continuing this discussion since that likely heavily influences this!

Sorry about the confusion.  RFC 2834 describes the behavior where Cargo will always check for future-incompat warnings and print a small notice informing the user. The user can then run the describe command to get a full report. The intent is to warn the developer that one of their dependencies may stop compiling soon, and they need to do something about that.  If it isn't enabled all the time, it likely won't have the intended impact of getting projects updated.
A concern is the inability to silence the warning, since it may take a while to resolve it.  The RFC included an "Annoyance Modulation", but I'm not sure if that specifically is how it should work.

Ok thanks for the link, I had forgotten this part of the original RFC. If that's the case then this seems fine since it'll likely be rarely run anyway (seems like the majority of what happens is you run cargo build and get a short message to run cargo describe-future-incompat at  the end).

I'm going to go ahead and merge this.  I'm also uncertain about the overall UX here, but I think this will be less confusing.
@bors r+

:pushpin: Commit f9512ff822b6b1dcd22bf1641f9fde727f79af44 has been approved by ehuss

:hourglass: Testing commit f9512ff822b6b1dcd22bf1641f9fde727f79af44 with merge 58a961314437258065e23cb6316dfc121d96fb71...

:sunny: Test successful - checks-actions
Approved by: ehuss
Pushing 58a961314437258065e23cb6316dfc121d96fb71 to master...


Error turning sample into Python. Python AWS Lambda sample?

I'm trying to adapt the s3 sample based on node.js to python. I tried by modifying the lambda section of the config.yml:
lambda:
  name: S3PythonSample
  zipfile_name: S3PythonSample.zip
  description: Testing S3 Lambda Python handler
  path: examplefolder/
  handler: hello_lambda.lambda_handler
  runtime: python

However, I get this error after running `kappa ./config.yml create':
$ kappa ./config.yml create
creating...
/Library/Python/2.7/site-packages/botocore/vendored/requests/packages/urllib3/connection.py:251: SecurityWarning: Certificate has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/shazow/urllib3/issues/497 for details.)
  SecurityWarning
/Library/Python/2.7/site-packages/botocore/vendored/requests/packages/urllib3/connection.py:251: SecurityWarning: Certificate has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/shazow/urllib3/issues/497 for details.)
  SecurityWarning
        Unable to upload zip file
Traceback (most recent call last):
  File "/Library/Python/2.7/site-packages/kappa/function.py", line 162, in create
    MemorySize=self.memory_size)
  File "/Library/Python/2.7/site-packages/botocore/client.py", line 258, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/Library/Python/2.7/site-packages/botocore/client.py", line 312, in _make_api_call
    raise ClientError(parsed_response, operation_name)
ClientError: An error occurred (ValidationException) when calling the CreateFunction operation: 1 validation error detected: Value 'python' at 'runtime' failed to satisfy constraint: Member must satisfy enum value set: [nodejs]
        Unable to add permission
Traceback (most recent call last):
  File "/Library/Python/2.7/site-packages/kappa/function.py", line 141, in add_permissions
    response = self._lambda_svc.add_permission(**kwargs)
  File "/Library/Python/2.7/site-packages/botocore/client.py", line 258, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/Library/Python/2.7/site-packages/botocore/client.py", line 312, in _make_api_call
    raise ClientError(parsed_response, operation_name)

I have been working on adding Python support for quite a while in a separate branch but I have just merged that branch into develop.  There are many, many changes and quite of few of them are breaking changes but I think the end result is better.  We have been using it every day for our own deployment process.
I will work on making sure all of the samples have been converted but in the mean time you can look at https://github.com/garnaat/kappa/tree/develop/samples/simple for a super-simpler Python example.

This should be fixed in the latest released version.


OTBR used for TE2 is not answering to Dynamic Update Queries

I am trying to test NXP ELock Demo application with mDNS. The problem is that the OTBR does not reply to the Dynamic Update Request initiated by the SRP client on the Thread device. The queries look valid so the issue seems to be on the OTBR side.
There is also a strange UDP Checksum Error in the OTBR Logs but not sure if this is relevant.
Also, please see attached the Wireshark capture (unzip it first).

no_dynamic_update_response_wireshark.zip

I've also analyzed the otbr logs: it seems that there are some mDNS logs but these are related to IPv4 (so maybe Ethernet traffic). So mDNS is enabled on OTBR. I would expected to see mDNS logs also for IPv6 (Thread) traffic but I don't see. What I see is those UDP Checksum errors: so maybe the mDNS queries originated from the Thread device are dropped due to UDP checksum errors?

It might be something else, but please verify that you provisioned a full Thread Dataset to the device. The Error UDP Checksum appears usually when you have a different Mesh Local Prefix on the Border Router and on the Thread device.
Explanation: The Mesh Local Prefix is compressed on 6LoWPAN layer with Context ID 0. Because of that the prefix is not sent over the air, and devices need to have the same address to properly calculate the checksum. Note that UDP Checksum for IPv6 includes both source and destination address.

Thanks, Lukasz, that was the problem: a different ML prefix.


chore: set min chrono

@bconn98 fix lint then we're gtg

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

Comparison is base (d4e6cbe) 62.99% compared to head (45c682c) 63.01%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #346      +/-   ##
==========================================
+ Coverage   62.99%   63.01%   +0.01%
==========================================
  Files          24       24
  Lines        1562     1560       -2
==========================================
- Hits          984      983       -1
+ Misses        578      577       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@estk looks to be all set. I'll re-release once it's in.


PBL-24917 log window improvements

Instead of #175, this PR makes a number of small changes to the logs window on a cleaned up branch:

PBL-24918 improve scrolling behavior: the log window now remembers its scroll position, and only sticks to the bottom
PBL-24918 fix spurious HRs: < hr >s were added to the logs when switching back to the log window. Now they are only added if the last log wasn't also a < hr >, to prevent a clutter of < hr >s when switching back and forth.
PBL-24918 deleting and saving logs: 'Delete logs' and 'Download logs' buttons have been added. ( #100 #187 )

OK, changes made


Add serving to docs site

Codecov Report

Merging #1715 (361c7e1) into master (bb5073f) will decrease coverage by 1.60%.
The diff coverage is 69.76%.

@@             Coverage Diff              @@
##             master    #1715      +/-   ##
============================================
- Coverage     72.08%   70.48%   -1.61%
- Complexity     5126     5524     +398
============================================
  Files           473      524      +51
  Lines         21970    24517    +2547
  Branches       2351     2652     +301
============================================
+ Hits          15838    17280    +1442
- Misses         4925     5921     +996
- Partials       1207     1316     +109

Impacted Files
Coverage Δ

api/src/main/java/ai/djl/modality/cv/Image.java
69.23% <ø> (-4.11%)
:arrow_down:

...rc/main/java/ai/djl/modality/cv/output/Joints.java
71.42% <ø> (ø)

.../main/java/ai/djl/modality/cv/output/Landmark.java
100.00% <ø> (ø)

...main/java/ai/djl/modality/cv/output/Rectangle.java
72.41% <0.00%> (ø)

...i/djl/modality/cv/translator/BigGANTranslator.java
21.42% <ø> (-5.24%)
:arrow_down:

...odality/cv/translator/BigGANTranslatorFactory.java
33.33% <0.00%> (+8.33%)
:arrow_up:

...nslator/InstanceSegmentationTranslatorFactory.java
14.28% <0.00%> (-3.90%)
:arrow_down:

.../ai/djl/modality/cv/translator/YoloTranslator.java
8.33% <0.00%> (-0.50%)
:arrow_down:

.../modality/cv/translator/YoloTranslatorFactory.java
8.33% <0.00%> (-1.67%)
:arrow_down:

...i/djl/modality/cv/translator/YoloV5Translator.java
5.38% <0.00%> (-0.31%)
:arrow_down:

... and 288 more

Continue to review full report at Codecov.

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


Support for ANSI Standard SQL Dialect

It seems only T-SQL is supported in VSCode. I am looking for similar support for ANSI Standard SQL Dialect because I am primarily editing SQL queries that run on Azure Databricks.

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.
Happy Coding!


NotFound errors on M2 Macbook Air with Fedora 40 Asahi Remix

From https://github.com/probe-rs/probe-rs/issues/2731 to here. OpenOCD seems unaffected (obviously using libusb)
I noticed while trying to use probe-rs, nusb seems to have problems if busnum is missing at some spot in the sysfs.
Log:
DEBUG nusb::platform::linux_usbfs::enumeration: probe device SysfsPath("/sys/bus/usb/devices/1-1.1")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/busnum": Ok("1\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/devnum": Ok("5\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/idVendor": Ok("2e8a\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/idProduct": Ok("000c\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/bcdDevice": Ok("0201\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/bDeviceClass": Ok("00\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/bDeviceSubClass": Ok("00\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/bDeviceProtocol": Ok("00\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/speed": Ok("12\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/manufacturer": Ok("Raspberry Pi\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/product": Ok("Debug Probe (CMSIS-DAP)\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/serial": Ok("E6616408432F7133\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/1-1.1:1.2/bInterfaceNumber": Ok("02\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/1-1.1:1.2/bInterfaceClass": Ok("0a\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/1-1.1:1.2/bInterfaceSubClass": Ok("00\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/1-1.1:1.2/bInterfaceProtocol": Ok("00\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/1-1.1:1.2/interface": Err(Os { code: 2, kind: NotFound, message: "No such file or directory" })
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/1-1.1:1.0/bInterfaceNumber": Ok("00\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/1-1.1:1.0/bInterfaceClass": Ok("ff\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/1-1.1:1.0/bInterfaceSubClass": Ok("00\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/1-1.1:1.0/bInterfaceProtocol": Ok("00\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/1-1.1:1.0/interface": Ok("CMSIS-DAP v2 Interface\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/1-1.1:1.1/bInterfaceNumber": Ok("01\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/1-1.1:1.1/bInterfaceClass": Ok("02\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/1-1.1:1.1/bInterfaceSubClass": Ok("02\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/1-1.1:1.1/bInterfaceProtocol": Ok("00\n")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1/1-1.1:1.1/interface": Ok("CDC-ACM UART Interface\n")
DEBUG nusb::platform::linux_usbfs::enumeration: probe device SysfsPath("/sys/bus/usb/devices/1-1.1:1.0")
DEBUG nusb::platform::linux_usbfs::enumeration: sysfs read "/sys/bus/usb/devices/1-1.1:1.0/busnum": Err(Os { code: 2, kind: NotFound, message: "No such file or directory" })
DEBUG nusb::platform::linux_usbfs::enumeration: failed to probe, skipping: No such file or directory (os error 2)

Full log:
nusblog.txt

The paths with : in them are actually USB interfaces, not devices, so failing to read their busnum and skipping them is expected (though it could probably ignore them based on the path, rather than trying to read device properties).
The lines
DEBUG list_cmsisdap_devices: probe_rs::probe::cmsisdap::tools: Found 1 CMSIS-DAP probes using nusb, searching HID
DEBUG list_cmsisdap_devices: probe_rs::probe::cmsisdap::tools: Found 1 CMSIS-DAP probes total

and
DEBUG probe_rs::probe::cmsisdap::tools: Attempting to open 2e8a:000c in CMSIS-DAP v1 mode

seem to indicate that nusb::list_devices successfully returned the device to probe-rs, and the failure happened later. Are you sure this is not a permissions issue or other failure opening the device as suggested by the message?

I doubt the problem is with permissions, as my x86_64 machine required no permission changes. I did add my user on the arm64 machine to the plugdev group per some suggestion I found in probe-rs and rebooted. But that didn't fix it.

https://github.com/kevinmehall/nusb/pull/72 cleans up the benign "No such file or directory" errors and adds logging when opening a device or claiming an interface fails. (It's on probe-rs for ignoring such errors without displaying any information about them, but at least it will be in the nusb log for situations like this).
For further troubleshooting, you'll need to find why opening the device fails, either using the logging now on nusb main or by patching probe-rs to do something with the error here: https://github.com/probe-rs/probe-rs/blob/6bcbeca7eb71f92413cf9c3fd3c8b55eb1c942a9/probe-rs/src/probe/cmsisdap/tools.rs#L152

I did add my user on the arm64 machine to the plugdev group

I think plugdev is a Debian/Ubuntu thing. It would work to add a plugdev group, add your user, and add udev rules that grant it permission, but it's possible you're missing one of those steps. I think the Fedora way is a udev rule with TAG+="uaccess" but IIRC there are some rule ordering dependencies that can result in it being silently ignored.

Updating probe-rs seems to have somehow fixed this?


create a containers directory for our Dockerfiles, add an initial example of a Dockerfile for Red

@thibauthourlier creating a new repository just for Genebuild's (or even all Ensembl's) Dockerfiles is a good idea. Is there a plan to do that in the near future? If we don't go ahead with that soon, I think this PR should be merged instead of staying in limbo.

I am not sure of the reasons for having the "make" image and the binary image. Maybe the make image should have the possibility of passing the CPU architecture if someone wants to use all the features from their CPU

I'm adding some more context about this in the README.


[CT-1885] [Feature] Remove flags.py

Describe the feature
Moving to the new Flags module instead of old flags.py

@ChenyuLInx I saw you added to the GH project for merging the feature branch, so I added to https://github.com/dbt-labs/dbt-core/issues/6631 as well — let me know if that was a mistake / feel free to remove it


[Question]: sparsity of minference

Describe the issue

Will the kernel affect the sparsity? When i read the chapter 3 of the paper and intuitive code implementation of index building, i thought that vertical / slash lines are selected just token by token, namely with 1*1 token mask. But the attached image showed that "Slash lines use 64 × 64 blocks, while vertical lines use 1 × 64 blocks.". Then the sparsity has decreased a lot?
Will it be the reason why @iofu728 said that the pattern all replaced by "vertical_and_slash" works better? Since the sparsity is different? https://github.com/microsoft/MInference/issues/17#issuecomment-2210652320

Hi @susu1210, thank you for your question. The block-wise computation is designed with a kernel-oriented approach.
To align different patterns with their corresponding sparsity, we adjust the offline search space. You can find the details in Section 3.2 and Appendix C.2. Additionally, the actual sparsity in the kernel is approximately 80%-95%, as shown in Figure 12. This level of sparsity is necessary to achieve a high end-to-end speedup.
Furthermore, I believe that replacing all patterns with "vertical_and_slash" works well mainly because it retains more dynamism than the A-shape pattern while still capturing most of the block-sparse information. We will continue to analyze this aspect further.