log(header): Add detailed error for non-adjacent header attempt

resolves https://github.com/celestiaorg/celestia-node/issues/1077

Codecov Report

Merging #1123 (ddd9497) into main (1803ca0) will increase coverage by 5.11%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1123      +/-   ##
==========================================
+ Coverage   56.11%   61.22%   +5.11%
==========================================
  Files         136      159      +23
  Lines        9169     9632     +463
==========================================
+ Hits         5145     5897     +752
+ Misses       3484     3211     -273
+ Partials      540      524      -16

Impacted Files
Coverage Δ

header/interface.go
100.00% <100.00%> (ø)

header/sync/sync_head.go
81.66% <100.00%> (+22.89%)
:arrow_up:

header/verify.go
83.33% <100.00%> (+1.11%)
:arrow_up:

service/rpc/config.go
60.00% <0.00%> (-40.00%)
:arrow_down:

service/rpc/das.go
26.66% <0.00%> (-23.34%)
:arrow_down:

das/daser.go
68.60% <0.00%> (-13.22%)
:arrow_down:

cmd/env.go
65.38% <0.00%> (-11.09%)
:arrow_down:

service/share/testing.go
75.17% <0.00%> (-7.59%)
:arrow_down:

cmd/flags_header.go
40.67% <0.00%> (-5.76%)
:arrow_down:

cmd/flags_node.go
61.40% <0.00%> (-5.27%)
:arrow_down:

... and 122 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Crash using installer vertion

there is a problem with the installer vertion you sent me

Not related to Elite: Dangerous profile. Most likely it's because this build is based on the Dev version of Aurora.


Update parent task's state even if the task fails

The problem is that when certain tasks (calcfunction, normal) fail, it does not update their parent state thus the workgraph engine goes into an infinite loop.
In case a task fails, we also need to update the state of its parent task.

Codecov Report
Attention: Patch coverage is 83.67347% with 8 lines in your changes missing coverage. Please review.

Project coverage is 80.66%. Comparing base (5937b88) to head (f19ae0f).
Report is 73 commits behind head on main.

Files with missing lines
Patch %
Lines

aiida_workgraph/engine/workgraph.py
83.67%
8 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #311      +/-   ##
==========================================
+ Coverage   75.75%   80.66%   +4.91%
==========================================
  Files          70       66       -4
  Lines        4615     5084     +469
==========================================
+ Hits         3496     4101     +605
+ Misses       1119      983     -136

Flag
Coverage Δ

python-3.11
80.66% <83.67%> (+4.99%)
:arrow_up:

python-3.9
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


String extraction unexpected result

Is this a problem with SwiftyJSON or my implementation?
In my app I'm trying to extract the "comments" field of the following subJson.
{"operation_id":"12648",
"dataset_id":"0",
"date":"0000-00-00 00:00:00",
"operation_year":"2015",
"operation_type":"",
"equipment_id":"2",
"tractor_id":"1",
"description":"",
"number_of_passes":"1",
"number_of_tractor_operators":"1",
"number_of_workers":"1",
"comments":"this is a test operation",
"tractor_operator_name":""}

Here's my code for that task:
self.comments = subJson["comments"].stringValue

But self.comments is always an empty string.
I think I'm correctly following the example in the SwiftyJSON readme. Any help with this would be greatly appreciated. Thank you.

@ndmeiri it'd be helpful if you show how your subJson variable came to be.  I couldn't reproduce the issue you describe in storyboard:

First, I get a JSON response from an Alamofire POST request. Then I break that JSON into parts and pass each part to an initializer for my Operation class.

Alamofire.request(.POST, URLString, parameters: parameters, encoding: .JSON).responseJSON { (_, _, possibleJsonObject, error) in

    if let jsonObject: AnyObject = possibleJsonObject {
        let json = JSON(jsonObject)
        var operations: [Operation] = []

        // parse out each subJson into an Operation
        for (index: String, subJson: JSON) in json {
            operations.append(Operation(json: subJson))
        }

        completion?(operations: operations, error: error)
    } else {
        println(error)
    }
}

This is what that initializer looks like.

convenience init(json: JSON) {
    self.init()

    println(json)
    self.identifier = json["operation_id"].uIntValue

    self.startDate = NSDate(timeIntervalSince1970: json["startTimestamp"].doubleValue)
    self.seasonalYear = json["year"].intValue

    self.comments = json["comments"].stringValue
    //println(self.comments)
    println(json["number_of_workers"].intValue)
    println(json["number_of_workers"].stringValue)
}

Please let me know if any other information would be helpful.

You should do this:
    for (index: String, subJson: JSON) in json.arrayValue {
        operations.append(Operation(json: subJson))
    }

Sry 4 late reply, plz feel free to reopen it if needed


CoPilot limitation details

Hi -
The documentation states "Due to current limitations, the Copilot control can answer questions for Dataverse tables that are smaller in size."
In my test it only looks at about 18-20 records in a table of 3.120 items.
This seems like very few records and then the otherwise very interesting feature seems to limited to use
BR
Erik Svensen

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

ID: b23b4520-df38-e5a5-01f2-69879db2895e
Version Independent ID: b23b4520-df38-e5a5-01f2-69879db2895e
Content: Add Copilot control to a canvas app - Power Apps
Content Source: powerapps-docs/maker/canvas-apps/add-ai-copilot.md
Service: powerapps
Sub-service: canvas-maker
GitHub Login: @mduelae
Microsoft Alias: tapanm

Thanks for your comment, @donsvensen. This issue has been assigned to the doc author for review.


Bump TargetRubyVersion in rubocop configs to 2.5 (#54)

closes #54

This is still pending

We probably should bump this to 3.0?

Bumping to 3.1 instead, as 3.0.6 will be EOL soon, according to ruby lang's official site:

Thanks guys!


Feature/s3

thanks @brainstorm !
@andersleung , let's at least allow for multiple AWS regions (which you may have already covered).
Regarding credentials, signed URLs, etc, there are 2 scenarios where we'd want the server to behave slightly differently in each case.

The DRSObject and bytes are not access controlled, but the S3 bucket is private. Any unauthenticated client can access the data in S3, but must go through the DRS server. This case doesn't require user auth, the credentials to access the S3 bucket can be stored on the server itself.

The DRSObject and bytes are access controlled, the S3 bucket is private and only the authorized users should be able to access it. This case requires user auth, so credentials need to be passed to the DRS server. In this case, we will use passports somehow to facilitate the authorization evaluation (and subsequent access to the bytes).

Any access control is out of scope for this PR, as we are just getting up and running with completely public data.

Just to clear one thing up, the default AWS region is just the region that the server will try first when trying to access an S3 bucket. If the access fails, the server will inspect the error and try again with the right region, which is more or less how amazon's own libraries handle "multi" region support. There isn't really an AWS region associated with the DRS server itself, but if you think being able to configure the default region would be useful, it should be easy to support.

@brainstorm this AWS multi-region discussion raises an important issue that we need a more sophisticated means of specifying various types of data sources (e.g. local files vs s3 buckets). Connected S3 bucket data sources require unique properties to be specified (region, bucket name, etc.). We've started #21 to be able to handle this in the configuration and startup.


Undefined line:column in some projects

ansi-regex

  package.json:undefined:undefined
  ✖  Specify AVA config in package.json instead of passing it through via the CLI.  ava

  1  error

anybar

  package.json:undefined:undefined
  ✖  Property dependencies should occur before property devDependencies.  pkg-property-order

  1  error

Will look into it tomorrow.

Oh ok, this is added by eslint-formatter-pretty. Why are these actually added and made invisible?

Oh, right. It's so you can just click the title in iTerm (and other terminals supporting that) and have it open in your editor on the correct line. You need to add a conditional there too about the missing line:column.

Wow, very nice feature :). Will do a PR this evening.

Should be fixed after reinstalling because of<EMAIL_ADDRESS>


Replace raw files popup with a table

In the current UI, clips and raw segment file download are treated pretty equally, which is pretty confusing since most user just want a clip. At the same time, I think we can improve the raw file download experience. I propose making the file popup into a useradmin-style table with all the segments.

I'd like to work on this

I started tinkering with this one a few days ago.  I was wondering if you could offer some clarification, though.  Did you mean replacing the Log Data download button in the Files popup menu with a modal window that provides the table?


Scrollbar Missing

Describe the bug
The content of the page exceeds the viewport height.
Expected behavior
Content on page will not  be visible to users completely.
Screenshots (Mandatory)

Additional Context (Mandatory )
in above img the login page is going out of box. i would like work on this issue.please assign me .
Thank You!
Are you contributing under any open-source program ?
GSSoC'24

Hello I am Gargi from IIT Kharagpur! I work with html,css,js,react.js and so on and am eager to learn more. I'd appreciate being assigned this task for GSSoC 24.

hello i can work on this issue please assigned this for me it will be helpful

@apu52 I am interested in contributing for this issue

Hello i am harsh from GGSIPU University. After carefully reviewing the issue description and requirements, I believe that my skills and experience make me well-suited to tackle this challenge. Allow me to outline why I am particularly excited about this opportunity.


fix: improve http error handling

fix serialization in multiprocessing by implementing __reduce__
handle non API response error in limiters
generally improve error handling

coverage: 93.996% (-0.7%) from 94.698%
when pulling 2fc560bdba0ab7397b42d40b3909a99f686506e7 on 0-fix-http-error-handling
into 918a08de422cfe68e8a9653ef3f0610970c334e4 on main.


[Academic consult] Prior information to the GP model

Hi Dr. Felix,
I am Hejun, a big fan of your work about GP and control theory. You can validate it based on the following statements.
During reading your publications, a vital question comes naturally, that is what kind of data can be chosen as the input information for a GP, to construct the learning state model better, i.e.,

Measurements of the state trajectory $psi(t;x)$ starting from a random point inside the region of attraction;
Measurements of the system state $[(x_1, \dot x_1), (x_2, \dot x_2), ..., (x_n, \dot x_n)]^{\mathrm{T}}$ over the domain.

I’d thought that (a) and (b) can be used to construct a state model equalitively. Would you please leave some comments and discussion at convenience? Thanks!

Thank you, Dr. F. Berkenkamp. Yes, both of these two types of data can be used to construct the GP for learning dynamical systems. I cannot recognize the difference between them. It was a pleasure to learn from you. Your theorems and codes have helped me be familiar with GP and safe learning a lot. I wish you great success in your next period.


Jupyter toolbar not visible for some VSCode color themes

There are some unorthodox VSCode color theme extensions that have a panel and sidebar that have a DARK background while the editor and Interactive Window use a LIGHT background (see below screenshot).  In a case like this, the VSCode's base UI theme (and respective icons) are either going to be compatible with a DARK panel and sidebar background OR be compatible with a LIGHT editor/Interactive Window background, not both.
I'd like to know if there's any way at all to explicitly tell Jupyter to use VSCode's LIGHT base UI theme (and respective icons) even if VSCode's theme is using a DARK base UI theme (specified in the theme extension's package.json as vs-dark).  That way, Jupyter's toolbar icons will visible in cases like this.
If the theme extension uses a base UI theme that's LIGHT in packge.json, icons in Jupyter will be visible, but then icons in VSCode's panel and sidebar and won't be visible.
It would be great if someone here could tell me how to explicitly use the LIGHT base UI theme for Jupyter; overriding what's specified in the color theme extension's package.json via a setting or workaround.  If it's absolutely impossible currently, I'd like to kindly ask for a python setting for settings.json that lets people specify a DARK or LIGHT base UI theme for Jupyter.
I've spent a great deal of time on this.. .so, I'm really hoping someone would be kind enough to shed some light on this and offer some kind of solution.

@mkanet Thanks for bringing up this issue! We tried to support the custom themes, but unfortunately there're limitations in what we can do within the Interactive window. We ended up with this setting @IanMatthewHuff pointed out above as a way to support custom themes. Closing the issue for now.

@IanMatthewHuff @ronglums No worries.  Thank you for considering my request.  I am hoping it's okay to ask a related question here.  I'm not sure where else to ask this question... I tried to customize .menubar CSS element within:  ../out/datascience-ui/history-react/menuBar.css_.
From:
.menuBar {
    margin-top: 2px;
    margin-bottom: 2px;
    display: flex;
    flex-direction: row-reverse;
   justify-content: right;
}

To:
menuBar {     margin-top: 2px;     margin-bottom: 2px;     display: flex;     flex-direction: row-reverse;     justify-content: right;     background-color: #b9b8b8; }
However, the line I added get's ignored after restarting VSCode.  Could you please tell me what I need to do in order to effectively modify the CSS for this element as an example?  This would REALLY help me to figure out how to make custom CSS's for Jupyter on my own.  If this is not the best place to ask this question, I'd really appreciate putting me in touch with the group that would be able to help me go in the right direction.  Thanks a million!

@mkanet. I don't think that going down the path of tweaking the .css file individually is going to give you the best results here. If you want to take a look at how the theming for the webview works I recommend starting with this file here:
https://github.com/microsoft/vscode-python/blob/master/src/client/datascience/codeCssGenerator.ts
It contains two things of interest, first off you can see how we scan the vs theme files to try to pull the correct files and surface them to our webview. And second, you can see the DefaultCssVars which is what we use for that "ignore theme" setting.

Thanks so much, Ian!  What is the easiest way to override the isDark: boolean variable to = false?  I would like to override this value regardless if I'm using a dark or light theme.  This should do what I want.  I just don't know where to specify this value manually.  Ideally/eventually, I'd like to specify this value programmatically in my VSCode extension.


Add simple CPU utilization output

This only works for linux and will output a simple error message for other OS instead of crashing. Utilizes info from /proc/loadavg

Cool. Thanks for sending this over!
I'm wondering if this information should pulled into uptime.  For example, here's the current uptime implementation, what cpu returns, and what the real version of uptime prints.
iex(1)> uptime
4 seconds
iex(2)> cpu
"load_1_min: 1.02, load_5_min: 0.93, load_15_min: 0.55, running_tasks: 2/1495, last_pid: 61590"
iex(3)> cmd("uptime")
 19:11:08 up 7 days, 23:54,  4 users,  load average: 1.02, 0.93, 0.55

How about the uptime looking something like:
iex> uptime
up 7 days, 23:54, load average: 1.02 0.93, 0.55

Don't worry about the time format that uptime prints out. I didn't realize that it was so dissimilar to the real version of uptime and don't want it complicating the PR.
The other suggestion is that if not on Linux, rather than printing an error, how about not printing the load average.
Thoughts?

Closing - please reopen if you want to push this forward.


NetStandard Project Build - AppVeyor

@jrummell available version in NuGet is 2.0.33.
Thanks for the enhancement!

No problem!


Task stops working after 3 minutes on android 14

Hi guys, I'm trying to set up a task that can be done every 30 seconds, the idea is to run constantly. The problem is that in versions prior to Android 14 it works fine, but in Android 14 it works for 3 minutes and the application stops working. I think it may be because of the declared service type android:foregroundServiceType="shortService", maybe if I change the service type the task could run for longer, did anyone have the same problem?
Thank you very much!

I am also facing the same issue, I have changed to foregroundServiceType, it's working for the first time but not everytime. Did you found any solutions @Beckmann0o ?

same issue here 😕

Hi guys, I'm trying to set up a task that can be done every 30 seconds, the idea is to run constantly. The problem is that in versions prior to Android 14 it works fine, but in Android 14 it works for 3 minutes and the application stops working. I think it may be because of the declared service type android:foregroundServiceType="shortService", maybe if I change the service type the task could run for longer, did anyone have the same problem?
Thank you very much!

Can you show your adb logs?

También tengo el mismo problema. Cambié a closeupServiceType y funciona la primera vez, pero no siempre. ¿Encontraste alguna solución?@Beckmann0o?

Hello bro, I was able to make it run continuously by adding foreground type in the Android manifest, the problem is that when the screen is turned off for several hours the OS kills the service. Did you have any progress? I leave how to configure the manifest:
 <service              android:name="com.asterinet.react.bgactions.RNBackgroundActionsTask"             android:foregroundServiceType="connectedDevice|dataSync|location">

Hola chicos, estoy intentando configurar una tarea que se pueda realizar cada 30 segundos, la idea es que se ejecute constantemente. El problema es que en versiones anteriores a Android 14 funciona bien, pero en Android 14 funciona durante 3 minutos y la aplicación deja de funcionar. Creo que puede ser por el tipo de servicio declarado android:foregroundServiceType="shortService", tal vez si cambio el tipo de servicio la tarea podría ejecutarse por más tiempo, ¿alguien tuvo el mismo problema?
¡Muchas gracias!

¿Puedes mostrar tus registros adb?
Creo que puedes intentar cambiar tu fouregroundServiceType a syncData para que tarde más en realizar una tarea.

Hello, I already have it configured as follows:

It works fine as long as the screen does not remain off for several hours, at which point the OS kills my service.

También tengo el mismo problema. Cambié a closeServiceType y funciona la primera vez, pero no siempre. ¿Encontraste alguna solución?@Beckmann0o?

Hello, I changed the service type in the Android manifest and got it to work continuously but when the screen is off for several hours the OS kills the service, I am trying to solve that problem. I'll give you my current configuration in the manifest for the type of service.
<service              android:name="com.asterinet.react.bgactions.RNBackgroundActionsTask"             android:foregroundServiceType="connectedDevice|dataSync|location">


Packages/stacks could not have their rosdep keys resolved to system dependencies (Ubuntu20.04 in WSL, ROS Humble, Ign Fortress)

Environment

OS Version: Ubuntu 20.04 Focal in WSL
ROS2 Humble + Ignition Fortress
Source build

Description
I cannot install ros_gz either via binary or source. I need to use Ubuntu 20.04 and install Humble+Ignition Fortress. I installed Humble via source and used the Fortress binary.
However, I encountered difficulties when installing the bridge.
In particular, trying to install via source the humble branch packages I encourred problems in managing dependencies with rosdep:
rosdep install -r --from-paths src -i -y --rosdistro humble

ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
ros_gz_sim_demos: No definition of [xacro] for OS version [focal]
ros_gz_bridge: No definition of [actuator_msgs] for OS version [focal]
Continuing to install resolvable dependencies...
#All required rosdeps installed successfully

Clearly trying to build the packages I consequently get the following error in relation to the lack of actuator messages:
colcon build

Starting >>> ros_gz_interfaces
Starting >>> ros_gz_sim
[Processing: ros_gz_interfaces, ros_gz_sim]
Finished <<< ros_gz_sim [52.0s]
Starting >>> ros_ign_gazebo
Finished <<< ros_gz_interfaces [52.5s]
Starting >>> ros_gz_bridge
Starting >>> ros_ign_interfaces
--- stderr: ros_gz_bridge
CMake Error at CMakeLists.txt:81 (find_package):
  By not providing "Findactuator_msgs.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "actuator_msgs", but CMake did not find one.

  Could not find a package configuration file provided by "actuator_msgs"
  with any of the following names:

    actuator_msgsConfig.cmake
    actuator_msgs-config.cmake

  Add the installation prefix of "actuator_msgs" to CMAKE_PREFIX_PATH or set
  "actuator_msgs_DIR" to a directory containing one of the above files.  If
  "actuator_msgs" provides a separate development package or SDK, be sure it
  has been installed.

---
Failed   <<< ros_gz_bridge [17.6s, exited with code 1]
Aborted  <<< ros_ign_gazebo [18.3s]
Aborted  <<< ros_ign_interfaces [25.3s]

Summary: 2 packages finished [1min 18s]
  1 package failed: ros_gz_bridge
  2 packages aborted: ros_ign_gazebo ros_ign_interfaces
  1 package had stderr output: ros_gz_bridge
  7 packages not processed

Steps to reproduce

Install Ubuntu 20.04 in WSL
Install ROS2 Humble via source
Install Ignition Fortress
Try to build ros_gz package

It's wierd, the dependency is listed in the package.xml in the humble branch https://github.com/gazebosim/ros_gz/blob/humble/ros_gz_bridge/package.xml#LL16C11-L16C24.
anywho you can compile actuator_msgs from source

I have the same problem. What about instead for "ros_gz_sim_demos: No definition of [xacro] for OS version [focal]" ?

It's wierd, the dependency is listed in the package.xml in the humble branch https://github.com/gazebosim/ros_gz/blob/humble/ros_gz_bridge/package.xml#LL16C11-L16C24.
anywho you can compile actuator_msgs from source

Thank you for your suggestion. I tried to add manually actuator_msgs (https://github.com/rudislabs/actuator_msgs) and xacro (https://github.com/ros/xacro/tree/ros2) packages to my workspace but i had other problems that i don't understand, here's the log:
colcon build

Starting >>> ros_gz_interfaces
Starting >>> actuator_msgs
Starting >>> ros_gz_sim
Starting >>> xacro
Finished <<< ros_gz_sim [0.89s]
Starting >>> ros_ign_gazebo
Finished <<< ros_ign_gazebo [0.56s]
Finished <<< ros_gz_interfaces [8.26s]
Starting >>> ros_ign_interfaces
Finished <<< xacro [10.8s]
Finished <<< actuator_msgs [13.0s]
Starting >>> ros_gz_bridge
Finished <<< ros_ign_interfaces [22.0s]
[Processing: ros_gz_bridge]
[Processing: ros_gz_bridge]
[Processing: ros_gz_bridge]
[Processing: ros_gz_bridge]
[Processing: ros_gz_bridge]
[Processing: ros_gz_bridge]
[Processing: ros_gz_bridge]
[Processing: ros_gz_bridge]
[Processing: ros_gz_bridge]
--- stderr: ros_gz_bridge
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [CMakeFiles/ros_gz_bridge_lib.dir/build.make:441: CMakeFiles/ros_gz_bridge_lib.dir/generated/factories/geometry_msgs.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [CMakeFiles/ros_gz_bridge_lib.dir/build.make:480: CMakeFiles/ros_gz_bridge_lib.dir/generated/factories/ros_gz_interfaces.cpp.o] Error 1
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [CMakeFiles/ros_gz_bridge_lib.dir/build.make:519: CMakeFiles/ros_gz_bridge_lib.dir/generated/factories/std_msgs.cpp.o] Error 1
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [CMakeFiles/test_ros_subscriber.dir/build.make:151: CMakeFiles/test_ros_subscriber.dir/generated/test/geometry_msgs_subscriber.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:487: CMakeFiles/test_ros_subscriber.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:321: CMakeFiles/ros_gz_bridge_lib.dir/all] Error 2
make: *** [Makefile:141: all] Error 2
---
Failed   <<< ros_gz_bridge [4min 57s, exited with code 2]

Summary: 6 packages finished [5min 11s]
  1 package failed: ros_gz_bridge
  1 package had stderr output: ros_gz_bridge
  7 packages not processed

something is wrong, probably with the amount of memory that you have in your system.
c++: fatal error: Killed signal terminated program cc1plus

If you are running this in VM increase the virtual memory or you can add this option to colcon --parallel-workers 1

ROS Humble officially only supports Ubuntu 22.04 (https://docs.ros.org/en/humble/Installation.html). That's why the actuator_msgs package is missing. When building from source, I agree with @ahcorde, I think you're running out of memory.  Try adding --parallel-workers=1 --executor sequential to your colcon command to ensure only one instance of the compiler is running at a time.

ROS Humble officially only supports Ubuntu 22.04 (https://docs.ros.org/en/humble/Installation.html). That's why the actuator_msgs package is missing. When building from source, I agree with @ahcorde, I think you're running out of memory. Try adding --parallel-workers=1 --executor sequential to your colcon command to ensure only one instance of the compiler is running at a time.

Thank you @azeey @ahcorde for helping me, I was able to build all the packages correctly by increasing the amount of RAM. I will try to run some tests to make sure everything is working!

For anyone else who might run into this issue:
On Ubuntu 20.04 focal, ROS 2 Humble, Ignition Fortress when having the following error
--- stderr: ros_gz_bridge
CMake Error at CMakeLists.txt:81 (find_package):
  By not providing "Findactuator_msgs.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "actuator_msgs", but CMake did not find one.

  Could not find a package configuration file provided by "actuator_msgs"
  with any of the following names:

    actuator_msgsConfig.cmake
    actuator_msgs-config.cmake

  Add the installation prefix of "actuator_msgs" to CMAKE_PREFIX_PATH or set
  "actuator_msgs_DIR" to a directory containing one of the above files.  If
  "actuator_msgs" provides a separate development package or SDK, be sure it
  has been installed.

---
Failed   <<< ros_gz_bridge [17.6s, exited with code 1]

Simply
cd src
git clone git@github.com:rudislabs/actuator_msgs.git
cd ../
colcon build

fixed the issue.
I was then able to confirm ros and ignition fortress working correctly by doing the following:
following this guide with modifications for an Ubuntu 20.04 local installation of ROS2 Humble and gazebo fortress
cd ~/dev/gazebo_fortress_ws/
source ~/dev/ros2_humble/install/local_setup.bash
source ./install/local_setup.bash
ros2 run ros_gz_bridge parameter_bridge /keyboard/keypress<EMAIL_ADDRESS>
In a second terminal
ign gazebo sim empty.sdf

Note replace the gz command with ign gazebo since the gz command was not yet introduced for fortress
In the simulator window click the dropdown in the top right
and add Key Publisher

In a third terminal
source ~/dev/ros2_humble/install/local_setup.bash
ros2 topic echo /keyboard/keypress

Press buttons on the keyboard when focused in the simulator and see the keypressed logged in the third terminal

Fixed by #431.


Auth fix for #687

Can we get a test in place for this?

I've updated the current batch transfer test to use a capital repo name.
I've verified the test fails with 1.0 and passes with the fix,

Still didn't work. We need to downcase all gitconfig keys.

I'm pretty sure gitconfig keys are downcased when we load the config--they were only uppercase when we modified the config in-process after it had already been loaded.
Do we have a tracking issue with a repro of the failure?

Do we have a tracking issue with a repro of the failure?

Nah, but that would've been good :)
I was a little frustrated when I wrote that comment after dealing with what I thought were more casing issues. People were having auth issues, and I instructed them to set the access value to force auth. Doing so can lead to issues if multiple git config keys are written:
$ git config --list
lfs.https://github.com/github/git-lfs-test.git/info/lfs.access=ntlm
lfs.https://github.com/GitHub/Git-LFS-Test.git/info/lfs.access=whatevs

$ git lfs env
git-lfs/1.0.2 (GitHub; darwin amd64; go 1.5.1; git 090222f)
git version 2.4.9 (Apple Git-60)

Endpoint=https://github.com/GitHub/Git-LFS-Test.git/info/lfs (auth=whatevs)

Which one is right?
I think having Git LFS write config values with lower cased keys is technically correct, or at least better, but it wouldn't stop people from writing their own access keys. Maybe the fix is to have git lfs env warn if duplicate keys are found.
$ git config -l
# added by git-lfs
lfs.https://github.com/GitHub/Git-LFS-Test.git/info/lfs.access=basic
# added by the user
lfs.https://github.com/GITHUB/GIT-LFS-TEST.git/info/lfs.access=none

$ git lfs env
Endpoint=https://github.com/GitHub/Git-LFS-Test.git/info/lfs (auth=none)

# HELLO AUTH LOOP
$ git lfs pull

I had a branch to enforce lowercase config keys. After writing this reply out, I decided to delete that branch and added the warning to https://github.com/github/git-lfs/pull/837 instead.
$ git config --list
lfs.https://github.com/GitHub/Git-LFS-Test.git/info/lfs.access=basic
lfs.https://github.com/GITHUB/GIT-LFS-TEST.git/info/lfs.access=none

$ git lfs env
WARNING: Reading LFS config from ".gitconfig", not ".lfsconfig". Rename to ".lfsconfig" before Git LFS v2.0 to remove this warning.
WARNING: These git config values clash:
  git config "lfs.https://github.com/GitHub/Git-LFS-Test.git/info/lfs.access" = "basic"
  git config "lfs.https://github.com/GITHUB/GIT-LFS-TEST.git/info/lfs.access" = "none"
git-lfs/1.0.2 (GitHub; darwin amd64; go 1.5.1; git 265feee)
git version 2.4.9 (Apple Git-60)

Endpoint=https://github.com/GitHub/Git-LFS-Test.git/info/lfs (auth=none)

Ahh makes sense. Glad you found a fix :+1:


Fixed unit tests crashes and a WGL deadlock

Description of Change
I wasn't able to run the unit tests in dev/update-skia dbfa12b644099e78cc4e46e226daba332f204f01
Got random crashes and deadlocks.
Bugs Fixed
Fixed the crashes and the deadlock I encountered.

Related to issue #1227

API Changes
No public changes, but I removed the bool refNew = false argument in the GetObject method, since it was always passed as false, so it felt redundant. This can of course change, but the owns and refNew arguments felt conflicting: should a reference ever be incremented if the wrapper doesn't own the object in the first place? Felt wrong.
Behavioral Changes
It is possible we now have memory leaks, I didn't check that...
PR Checklist

[x] Has tests (if omitted, state reason in description)
[x] Rebased on top of dev/update-skia at time of PR
[ ] Changes adhere to coding standard
[ ] Updated documentation

My original patch doesn't seem to work anymore with the latest version

Thanks for this!
It was merged in from #1237 and is now included in master (v1.68) and develop (v2.80).


Don’t understand how true_score and false_score are represented in logits

factscore/factscorer.py lines 219-220, in _get_score:
true_score = logits[5852]
false_score = logits[7700]
Is there any intuition about these particular logit indices and how logits are formed?

Hi @rubaha96, these are vocab ids for True and False (in LLAMA tokenizer). So these scores represent how likely the model will complete the sequence with True or False.


More then one school

Have 2 kids, going to 2 different schools, therefor I declared 2 sensors in configuration.yaml
Somehow it only adds the 2nd sensor as an entity. The first one is ignored.
Is this a limitation or a bugg?

Skolmat integration

sensor:

platform: skolmat
name: Tage # Name of school here
rss: "https://skolmaten.se/kinnarummaskolan/rss/weeks" # your rss here

sensor:

platform: skolmat
name: Algot # Name of school here
rss: "https://skolmaten.se/daltorpskolan-f6-k2/rss/weeks" # your rss here

@ekalle-swe My config looks like this and it works
sensor:
  - platform: skolmat
    name: Nyvång
    rss: "https://skolmaten.se/nyvangskolan/rss/weeks/"
  - platform: skolmat
    name: Spyken
    rss: "https://skolmaten.se/spyken-gymnasieskola/rss/weeks/"

Have 2 kids, going to 2 different schools, therefor I declared 2 sensors in configuration.yaml Somehow it only adds the 2nd sensor as an entity. The first one is ignored. Is this a limitation or a bugg?
Skolmat integration
sensor:

platform: skolmat
name: Tage # Name of school here
rss: "https://skolmaten.se/kinnarummaskolan/rss/weeks" # your rss here

sensor:

platform: skolmat
name: Algot # Name of school here
rss: "https://skolmaten.se/daltorpskolan-f6-k2/rss/weeks" # your rss here

It seems you redefine the "sensor" list in your config. The last definition overwrites the previous one. Put the whole configuration under a single "sensor:" section, as shown in the reply by @agent-ost
/Anders

Thank you for your answers.
Yes, I figured that out.
As I'm a bit new to HA I found it more logical to declare one sensor at the time but that's not how it works, is it.
Anyway, works brilliantly now, so many thanks!


Oculus Touch (Quest 2) controllers not working with Village while controller is plugged in

Someone else who had this issue just closed their post for some reason, but this issue hasn't been fixed, although a work-around has been posted (unplugging controller).
But here's the thing, RE2R works fine with my controller plugged in, so why would this have issues?

Same here


pmDrag's addLayer method leaking

Hi there,
I think pmDrag subplugin should have a method for resetting mutated leaflet's events. If you change routes in a React project and import "./pmDrag"; is run again, project throws an error: Maximum call stack size exceeded, because addLayer method will run in a loop.
codesandbox.io

I was able to fix that like this:
const defaultLeafletAddLayerEvent = React.useRef(null);

React.useEffect(() => {
		return () => {
			L.LayerGroup.prototype.addLayer = defaultLeafletAddLayerEvent.current;
		};
}, []);

React.useEffect(() => {
		defaultLeafletAddLayerEvent.current = L.LayerGroup.prototype.addLayer;
		const pmDrag = new L.PMDrag(mapRef, { overwriteLayerGroup: true });
		pmDrag.setMode(1);
}, [mapRef]);

I am not sure if this is the best way to fix this. I will this issue opened.

I think / hope that pmDrag is not longer needed after the next release.

@Falke-Design great news, thank you.


A ton of warnings

I have been using several macros for this expansion They have performed well. After your latest update I have all kinds of compile issues. The macros are priority type and relatively short (I know what does short mean ). No more then 8 lines mostly castsequence.
no special calls to other macros.  They are calling out compile errors for length -350-1800
I like the block concept but am afraid to change or test just yet

Each block works as an individual element.  A WOW Macro can have a total of 255 actions (command blocks) before it breaks.  If you have a Priority loop with 5 lines in it and repeat that 20 times your macro is when compiled for execution 1050 actions long plus anything outside of the loop.  This is past the 255 limit.  Prior to this and as noted in #900 WoW would just spew out a bunch of errors and your macro would not work.
If your macro is just priority and 8 lines long - set the repeat to 1 and the warnings will go away.

Sorry did not mention I am not using the loop function on any of them nor am I using pre or post macro. The macros worked fine in pre 3.0 .  Would shortening and chaining the sequence solve it

Can you give me an example?  It's kinda hard to see what's in your macro or what it compiles to without something to work from.

hey @woodgray
Is this still an issue for you?

No as a matter of warnings except creating a click block with delay
Get Outlook for iOShttps://aka.ms/o0ukef

From: Timothy Minahan @.>
Sent: Monday, July 5, 2021 7:21:20 PM
To: TimothyLuke/GnomeSequencer-Enhanced @.>
Cc: woodgray @.>; Mention @.>
Subject: Re: [TimothyLuke/GnomeSequencer-Enhanced] A ton of warnings (#907)
hey @woodgrayhttps://github.com/woodgray
Is this still an issue for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/TimothyLuke/GnomeSequencer-Enhanced/issues/907#issuecomment-874365692, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AF2U77G2CFGWON7TY4X7AJTTWI47BANCNFSM47V7CTGA.

Going to close this out for now - yell if i need to look at this again


Windows - some scripts have compilation errors

Hello,
The example scene won't run on Windows 10. I have attached the output from the make file, and a screenshot from Unity.
make_file_log.txt

Please run make install before starting Unity Editor.

closes because the build command has changed.


feat: Add developer quality of life changes

I don't think this belongs into the extension repos.

I don't think this belongs into the extension repos.

I've removed the IDEA-related configuration. How's this? The editor configuration is useful for anyone using a compatible editor, and the newline at EOF means Git shows nicer diffs.

What do you think, @emmanuelmathot ?

As best practices, I have always been told that IDE or dev software related config should not be in a shared repo. Now .editorconfig file is a more generic file even supported by github so this may be accepted IMO.


Fix: Update html2text dependency to ^2024.2.26 to fix image src error

Description
Updated the html2text dependency from ^2020.1.16 to ^2024.2.26. This update addresses an issue where an error was encountered if an image on the page did not have a src tag.
Fixes #14645
New Package?
Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

[ ] Yes
[x] No

Version Bump?
Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

[x] Yes
[ ] No

Type of Change

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

[x] I have run the existing unit tests to ensure the updated dependency does not introduce new issues.
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

@zeloras can you bump the package version of llama-index-reader-web as well?

@logan-markewich Good evening! done, could you check please?

merging on behalf of @logan-markewich :) thanks @zeloras!


feat: Validate cache size before updating cache with informative err message

Currently the error look like the following if the size exceeds etcd limit:
time="2021-05-06T09:07:55Z" level=error msg="Failed to save node outputs to cache" error="error creating cache entry: ConfigMap \"reuse-task\" is invalid: []: Too long: must have at most 1048576 characters" namespace=argo nodeID=xxx workflow=xxx

With this PR, the error is now more informative so users know what to do and we can save update API calls (imagine if many nodes are using the same cache, they'll make that many API calls that turn out to fail, which would increase load of k8s apiserver).
Signed-off-by: terrytangyuan<EMAIL_ADDRESS>Checklist:

[x] My organization is added to USERS.md.

Note that we could potentially allow a larger size and perform compression similar to workflow but that's a separate topic and could be fixed by https://github.com/argoproj/argo-workflows/issues/3587.

Can I suggest a simpler approach? The error message contains a link to the documentation? That way we can update the documentation with having to release anything.

Do you mean modifying the error message with a link when there's error from the UPDATE API call?

I don't think you even need to check the size.

The main benefit of checking the size earlier is that we can save UPDATE API calls (imagine if many nodes are using the same cache, they'll make that many API calls that turn out to fail, which would increase load of k8s apiserver).


Re-export default export with a name

There is the module babel-plugin-transform-export-extensions for babel which allows re-exporting a module's default export with a name (https://github.com/leebyron/ecmascript-more-export-from#proposed-additions):
export v from "mod";

Example:
Panel.js:
export default class Panel {
   ...
}

index.js:
export Panel from './Panel';

Swc currently does not support this syntax and throws an error:
error: Expected LBrace, got Some(Word(Panel)):
1 | export Panel from './Panel';
  |        ^^^^^

Oh! nevermind, adding "exportDefaultFrom" makes it work... I wish I could find a full list of these options though. Nice work! :)


Preserve distribution when converting from Nextjs to StaticSite

I have an application deployed to AWS using new sst.aws.Nextjs("MyApp").
I converted it to a static app, thus I replaced with new sst.aws.StaticSite("MyApp"), keeping all other settings (e.g. domain, cdn) the same.
This results in SST creating a new CloudFront distribution, but failing because it tries to create an OriginAccessPolicy with the same name as the old distribution.
This also fails if you are using an alternate domain name, as the old distribution still has the domain, and you can't have two distributions with same alternate domain name.
Is it possible to switch from Nextjs to StaticSite while keeping the same distribution, rather than creating a new one?

Yeah you can't switch it while having the same name. Either create a new one with a different name. Or remove the old one, deploy, then add the new one.


The generator does not use templates installed in node_modules

The bug
This installs  @asyncapi/html-template twice.
npm i -D @asyncapi/generator  @asyncapi/html-template
./node_modules/.bin/ag src/simple.yaml @asyncapi/html-template --force-write

repro: https://github.com/laat/repro-asyncapi-generator
Expected behavior
It should reuse installed templates. This lets me pin templates at a specific version
The repro has a patch
This solves the issue for me. Essentially require.resolve does the heavy lifting and should support the intended uses of the replaced code.
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 841af20..dc62139 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -320,31 +320,12 @@ class Generator {
     return new Promise(async (resolve, reject) => {
       if (!force) {
         try {
-          let installedPkg;
-
-          if (isFileSystemPath(this.templateName)) {
-            const pkg = require(path.resolve(this.templateName, PACKAGE_JSON_FILENAME));
-            installedPkg = require(path.resolve(DEFAULT_TEMPLATES_DIR, pkg.name, PACKAGE_JSON_FILENAME));
-          } else { // Template is not a filesystem path...
-            const templatePath = path.resolve(DEFAULT_TEMPLATES_DIR, this.templateName);
-            if (await isLocalTemplate(templatePath)) {
-              // This "if" is covering the following workflow:
-              // ag asyncapi.yaml ../html-template
-              // The previous command installs a template called @asyncapi/html-template
-              // And now we run the command again but with the resolved name:
-              // ag asyncapi.yaml @asyncapi/html-template
-              // The template name doesn't look like a file system path but we find
-              // that the package is already installed and it's a symbolic link.
-              const { resolvedLink } = await getLocalTemplateDetails(templatePath);
-              log.debug(`This template has already been installed and it's pointing to your filesystem at ${resolvedLink}.`);
-            }
-            installedPkg = require(path.resolve(templatePath, PACKAGE_JSON_FILENAME));
-          }
-
+          const pkgJsonPath = require.resolve(path.join(this.templateName, PACKAGE_JSON_FILENAME))
+          const installedPkg = require(pkgJsonPath)
           return resolve({
             name: installedPkg.name,
             version: installedPkg.version,
-            path: path.resolve(DEFAULT_TEMPLATES_DIR, installedPkg.name),
+            path: path.dirname(pkgJsonPath),
           });
         } catch (e) {
           // We did our best. Proceed with installation...

@laat Hey, I need more details to fully understand the issue.

What is the use case for using generator like this npm i -D @asyncapi/generator  @asyncapi/html-template ./node_modules/.bin/ag src/simple.yaml @asyncapi/html-template --force-write
This lets me pin templates at a specific version what do you mean, now you can use a specific version of the template too, it is described here https://github.com/asyncapi/generator#generator-version-vs-template-version
the change that you suggested, in what scenarios did you test it? did you also test scenario where you do not install a remote template but use it from local sources? it is a common scenario used during development

At the moment, when installing @asyncapi/html-template puppeteer is installed which is about 130 mb. With my workflow it gets installed twice.
I want reproducible builds, and to do that I need all dependencies declared in pacakge-lock.json. By specifying a version on the commandline the build can fail the next day, without me changing anything, because a transitive dependency broke.
The code change I've suggested should work with npm link, because it uses the nodejs require mechanism which supports it. When reading the code I replaced, it looks like a partial implementation of the require algorithm. I have not tested the symlink case.

I want reproducible builds, and to do that I need all dependencies declared in pacakge-lock.json

ok, that makes sense
would you mind opening a PR, I'd love to help with testing different scenarios. I would work on your PR for a couple of days to make sure all works well

@derberg I created a PR :)

@laat yeap, noticed. Will write down all possible test scenarios that need to be checked and starting from that point we will see how to approach testing. I don't want to throw responsibility for writing missing tests on you, but if you want to work on them, I will not stop you 😄

@laat wouldn't it be better for you to just install with PUPPETEER_SKIP_CHROMIUM_DOWNLOAD="true" and avoid duplicated chromium installation?

It still does not solve the reproducible builds issue. Because package-lock.json is ignored.

@laat are you 100% sure it is ignored? the installation logs show 200 or rather different code (302 I think)?

Yes.
 "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" environment variable was found.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.

+<EMAIL_ADDRESS>added 67 packages from 88 contributors in 16.511s

65 packages are looking for funding
  run `npm fund` for details

Done! ✨
Check out your shiny new generated files at /Users/wookiee/sources/generator/output.

local html-template without node_modules and local generator with html-template in node_modules
./cli.js test/docs/dummy.yml ../html-template --force-write -o output

Something went wrong:
Error: Cannot find module 'rimraf'
Require stack:
- /Users/wookiee/sources/html-template/hooks/01_removeNotRelevantParts.js
- /Users/wookiee/sources/generator/lib/hooksRegistry.js
- /Users/wookiee/sources/generator/lib/generator.js
- /Users/wookiee/sources/generator/cli.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
    at Function.Module._load (internal/modules/cjs/loader.js:725:27)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/Users/wookiee/sources/html-template/hooks/01_removeNotRelevantParts.js:3:16)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Module.require (internal/modules/cjs/loader.js:952:19)

local html-template with node_modules and local generator without html-template in node_modules
./cli.js test/docs/dummy.yml ../html-template --force-write -o output

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.

+<EMAIL_ADDRESS>added 1 package from 1 contributor in 5.747s

85 packages are looking for funding
  run `npm fund` for details

Done! ✨
Check out your shiny new generated files at /Users/wookiee/sources/generator/output.

local html-template without node_modules and local generator without html-template in node_modules

./cli.js test/docs/dummy.yml ../html-template --force-write -o output -i

result like step 1

local html-template without node_modules and local generator with html-template in node_modules

./cli.js test/docs/dummy.yml ../html-template --force-write -o output -i

/Users/wookiee/sources/generator/lib/utils.js:38
  const [nameWithVersion, pkgPath] = result[result.length-1];
                                                   ^

TypeError: Cannot read property 'length' of undefined
    at utils.beautifyNpmiResult (/Users/wookiee/sources/generator/lib/utils.js:38:52)
    at /Users/wookiee/sources/generator/lib/generator.js:373:17
    at /Users/wookiee/sources/generator/node_modules/npmi/npmi.js:164:37
    at /Users/wookiee/.nvm/versions/node/v14.15.0/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:123:16
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)

local html-template with node_modules and local generator without html-template in node_modules

./cli.js test/docs/dummy.yml ../html-template --force-write -o output -i

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.

+<EMAIL_ADDRESS>added 1 package from 1 contributor in 5.558s

85 packages are looking for funding
  run `npm fund` for details

Done! ✨
Check out your shiny new generated files at /Users/wookiee/sources/generator/output.

The question would be what is wrong with html-template symlink in generator in node_modules that makes scenario 2 not work the same as scenario 1. And how come can this require https://github.com/asyncapi/generator/blob/master/lib/generator.js#L329 trigger scenario 1 to work.
now some other question, did you try just this:
npm i -D @asyncapi/generator  @asyncapi/html-template
./node_modules/.bin/ag src/simple.yaml node_modules/@asyncapi/html-template --force-write

Cool, it's good to have the use cases documented. 👍
It still ignores the package-lock.json versions.

Ok, right, I did npm cache clean --force.
I created a project where I installed latest generator and old version of html-template without pdf generation support:
  "dependencies": {
    "@asyncapi/generator": "^1.0.0-rc.13",
    "@asyncapi/html-template": "^0.13.0"
  }
}

I run<EMAIL_ADDRESS>http://bit.ly/asyncapi ./node_modules/@asyncapi/html-template --force-write -o output -p pdf=true
and I got error but also the template was downloaded fresh, with lots of 200s

come one bot, can't you see I'm working on it, doh!

@laat hey, it took some time, but it is finally here https://github.com/asyncapi/generator/pull/517
if you want and have time, please have a look at this PR
your use case will be fixed + I've added the integration tests that we were always missing

Release 1.2 enables support for latest node and npm and fixes all known installation issues. In case you see some other issues, please create a new issue. Please use --debug flag when you experience issues with the generator and in the issues mention the troubleshooting logs. Thanks!


Make Find page Mobile Friendly

The Find page needs to work on mobile devices.

Add a button that toggles between the map and list views of properties
Make the property card list appear in one column
When someone clicks on a property on the map it should switch to the property detail view

Here's a link the the prototype in Figma. https://www.figma.com/file/NAFkgq34abW6uJ0R7PW24T/Prototype---Clean-%26-Green-Philly?type=design&node-id=2421%3A22712&mode=design&t=EYanZQnoOdgWCTls-1

NOTE design is updated but doesn't impact the requested changes

Hello! I would like to be assigned to this issue if it's available. :)


Windows 11 Issues

Windows 11 Home 64bit 22H2 OS Build 22621.819
Chrome 107.0.5304.107
Microsoft Edge 107.0.1418.42
Using the examples at https://mozilla.github.io/pdf.js/examples/index.html#interactive-examples
The HelloWorld example works but not the Previous/Next jsFiddle example, the pdf is very distorted, unreadable.

Duplicate of #14641, which is a best guess given the lack of screen-shots illustrating what you mean.


no state mode in prompt line with oh-my-zsh and powerlevel10k

General information

Basic examination
tty from ssh access on FeeBSD-12.2
zsh used with Oh-my-zsh and antigen (installed from freebsd packages)
zsh-5.8
add to oh-my-zsh as indicated (and also before from antigen pugin) with git cone inside ZSH_CUSTOM (plugins recognized by ohmyzsh)

[x] I have read through the README page
[x] I have the latest version of zsh-vi-mode
[x] I have tested with another terminal program
I can not test with another because my FreBSD system is installed on a VPS and i don't want any X service running... it is full tty ssh access. But the terminal emulator used to remote access is Alacritty under Fedora-34 (both from Gnome and Awesome WM tested, and with other emulator it has the same result)

Problem description
From my ohmyzsh powerlevel10k prompt shell, i can not see any zsh-vi-mode indication of state mode (normal mode/insert mode/replace mode, etc...).
But the plugin is working... i should miss a point to configure ohmyzsh or maybe powerlevel10k (as i can not see any powerlevel10k indication).

Reproduction steps

install the plugin from antigen
clone it on oh my zsh custom directory
enable the plugin in .zshrc

Expected behavior
see in the prompt line somewhere the zsh-vi-mode mode state

Hi @jerome-diver
Thanks for the issue, actually, the vi mode state should be supported by your theme, but this plugin has also provided several aspects for you to configure your custom prompt of vi mode state, you can refer to here.
Here are some examples for you:

gkapfham/dotfiles
jenra-uwu/.dotfiles
gabrielzschmitz/dotfiles
pjg/dotfiles
kelly-lin/dots
radixm46/dotfiles
...

Thanks and Regards

Hi @jeffreytse and thank you for your help.
Actualy, i read amll examples and i can not figure how to config my .p10k file to get a segment to show a zsh-vim-mode event status change.
the configuration is inside powerlvele10k zsh file and there is a "example" segment able to print a segment (but this one only operate at prompt build time, then after to RETURN a command.
I try to use the event zsh-vi-mode cfunction in both my .zshrc and .p10k file without any success (the segment is still not returned at event time, not sure if the function is working out of .zshrc file.
My ZSH script knowledge is not enough to undertstand good how  it is working, so i'm locked.
There is, inside powerlevel10k plugin theme, a 'vi-mode' segment existing (this one reflect only vi-mode as normal or insert or visual, not replace mode or any other.

@jeffreytse thank you

REPLACE mode still not showing properly in Powerlevel10k v1.20.0

Mode
Behavior
Working as expected

INSERT

yes

NORMAL

yes

REPLACE

no

VISUAL

yes


No built-in support for 'internal/network' in Archlinux Linux

Arch linux default builds lack libiw.so and its header file. I built polybar and not once did it fail but after configurations i still get these errors
error: Disabling model "wlan" (reason: No built-in support for 'internal/network')
error: Disabling model "eth" (reason: No built-in support for 'internal/network')

Did you have wireless_tools installed during the build?

No wireless_tools is now deprecated and thus was not included in my build

Do both wired and wireless module depend on the same lib? So i cant get just the wired status for now patching polybar?

Well there is your problem, polybar requires wireless_tools for network module support. So you'll have to have it installed when you build and run polybar

From what I can tell, only the support for wireless interfaces depends on wireless_tools (as the name suggests). So you'd probably be able to remove all wireless functionality from polybar and force-enable the network module during compilation to get only wired functionality

Waiting on #1009 to apply suggested fixes, which should completely fix this issue as it replaces wireless_tools with nl80211. If it is not fixed in a reasonable amount of time, I might do the changes myself.

I have used up my free time today reading the source. Tried replacing wireless_tools and i broke the bar thats the flaw with objected oriented programing. Thinking of a  rewrite for both modules but if you can patch it @NBonaparte please publish in yaourt so i can version build.


[Question] Is Harvester 1.1.x supported with Rancher 2.7.0?

Rancher 2.7.0 was released 13 days ago so after Harvester 1.1.0 but before Harvester 1.1.1.  I know Rancher 2.7.0 introduces extensions and I'm keen to play with Elemental.
Am I likely to run into issues if I use Rancher 2.7.0 with Harvester 1.1.0 or 1.1.1 (when released and I upgrade my home lab cluster).

I'm running Rancher 2.7.0 mamagement cluster with Harvester 1.0.3 without any issues, so I would guess that it should run without issues...  But just to make sure, you are talking about the Management Rancher cluster - not the actual Rancher version bundled within harvester correct?  I wouldn't try to upgrade the rancher version in harvester separately from Harvester...

Yes I'm asking about the separate, "management" Rancher (the one we should install ourselves to manage Kubernetes and Harvester) and not anything built into Harvester itself.

Then like I said, I'm using Rancher 2.7.0 to manage my current 1.0.3 Harvester cluster with no issues I didn't have on 2.6.9

In my case Rancher 2.7.0 works with Harvester 1.1.0 - but obviously I could not test "everything" ;-)


[showcase] improvements

As per the comments on IRC:

[x] vertical-align: top for each showcase item.
[x] make the app icons link to the app store link
[x] center the h1 tag
[x] 4 items per line if possible.

Was this resolved in versions > 9.0?

@jaygarcia - hmm not sure, can you create a separate issue with some more details?

looks awesome @brentvatne :+1:


Feature interpolation

Looks like there is a meta file from an empty folder AssetStoreTools

Looks good to me!


update max connections to 30

Signed-off-by: Sherin Varughese<EMAIL_ADDRESS>Related Issue: https://issues.redhat.com/browse/ACM-3071
Description of changes

/retest

/retest


Node-Red Editor: bug Inject-Node

What are the steps to reproduce?
What happens?
If i want to change the Interval of the Inject Node i select Interval and nothing appeares...

the HTML Element is "hidden" !

If i delete the "hidden" in the Inspector the option appears

What do you expect to happen?
If i select Interval i expect that it appears automaticaly!
Please tell us about your environment:

[x] Node-RED version: 1.03
[x] Node.js version: v10.18.0
[x] npm version: 6.13.4
[x] Platform/OS: Client is Win10 and Node-Red runs on Linux (RevPi Connect+) Rasbian Stretch
[x] Browser: Mozilla Firefox 76.0.1 (64-Bit) / Microsoft Edge 44.17763.831.0 / Google Chrome
Version 83.0.4103.61 (Offizieller Build) (64-Bit)

Not been able to reproduce this here and haven't had any similar reports from the community.
I assume there aren't any associated errors in the browser developer console?

first line appears on droping the inject node and second line on opening the node config tab!

on changing to interval nothing happens...  hope its what you asked for!

I was hoping for something in English I can read... but I don't think either of those are relevant from what I can pick out.

sorry about that german os / browser installation...

Error processing value for cursor. Declaration ignored.
Password fields are available on an insecure (http: //) page. This is a security risk and credentials can be stolen.

atm i am running it in container and it workes but not on the native Rasbian Stretch
sudo docker run -it -p 1880:1880 --name mynodered nodered/node-red
container version of node v10.22.0 node-red v1.1.3
i mean this workaround works but it made some things more complex

I can't think we had any changes in this area but I note the Pi version is 1.0.3 vs the newer 1.1.3 in docker.

i have managed to figure out when it happens... finaly ^^
it happens always if i flash a backup on the revPi so after flashing the bug appears! if i just start with a blank os and install everything fresh everything is fine, then if i make a image of the revpi and reflash it, the bug appears again...
does that sound familiar to anyone? i am kind of lost on that issue...

So it's fine if you install clean on the rev-pi ?
We don't have the ability to test on devices like that so anything extra it may be doing during backup/restore is going to be hard to diagnose remotely.

tbh it does not matter if i use the rev-pi or just a raspi3, i assume its happening while flashing...

UPDATE:
somehow its gone in the latest version!
thanks


Update README.md

Thank you for your merge request.
You may prefer to use the original project (I forked it from vBahKoo), unless you need to support a different cache directory (see pull request https://github.com/BahKoo/ChocolateStore/pull/9).
AFAIK the original project does not support such configuration (yet).


[CLI & Move] refactor the move explain

Refactor the move explain, and provide a explain library.
https://github.com/rooch-network/rooch/blob/e9037b6582c920c3a721f415715cd2142c1fc421/moveos/moveos/src/vm/vm_status_explainer.rs#L61-L71
https://github.com/rooch-network/rooch/blob/e9037b6582c920c3a721f415715cd2142c1fc421/crates/rooch/src/commands/move_cli/commands/explain.rs#L120-L124

We deprecate the error code category in #1184, so the explain command is useless.


Key Mismatch / ID doesn't exist

So I've installed my self hosting RustDesk Server via Linux - Ubuntu with PM2.
When I write down the server configs in the client side of both computers I get "Key mismatch or ID doesn't exist".
The thing is my keys is from the id_ed25519.pub and they're exactly the same. I'm sometime able to get in from my phone to my laptop but never somewhere else. This issue has been bugging me for so long because I just want to setup my own server and it's literally less efficient than the public server.
Thank you for your time whoever decides to help me it's much appreciated!

PM2 isnt using our script


Hi i have an edge function deployed, till yesterday i was getting 200 but today i am only getting 500 when i am hitting the url. so it happening with anyone too??

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
Rerun the failing command with --create-ticket flag.

Ticket ID: [e.g. ab1ac733e31e4f928a4d7c8402543712]
Version of OS: [e.g. Ubuntu 22.04]
Version of CLI: [e.g. v1.60.0]
Version of Docker: [e.g. v25.0.3]
Versions of services: [output from supabase services command]

Additional context
If applicable, add any other context about the problem here.

Browser [e.g. chrome, safari]
Version of supabase-js [e.g. v2.22.0]
Version of Node.js [e.g. v16.20.0]

transferring because it affects the hosted platform

@piyush672 I am getting 500 for a function of mine when it is running deployed. It has an npm include. If I take out the npm include it works fine. It also fine with supabase function serve locally but deployed it gives 500 with no errors in the log not even a function boot. Is your function including an npm package?

@piyush672 @chreds These looks like hosted platform related issues. Can you please open support tickets via https://supabase.help?


Dev

Option to delete video during incomplete thumbnail/video download + package update + Vertical Video Preview Issue


Recursive rewrite of rendering datasources for subitems of branch item

Hi Kam! Big fan of the all the work you do on Sitecore tools, always elegantly written and extremely useful!
I recently found myself in need of local rendering datasources for a particular branch template. A quick google and I found this gem, works like a charm for the instance of the branch item! However, I needed to do the same for subitems, so I extended your software a bit and made it recursively handle rendering datasources for all subitems of the branch item as well.
Hope you have time to look at it and maybe merge it into your branch!
Best wishes,
Bonny

Hi there! Thanks for the contribution. #2 I believe implemented the same thing, and I've merged that PR. If yours adds capabilities that that merge didn't, please feel free to adapt your PR to fit in with it and I'll merge it :)


bug: vs code now constantly auto switching to the output panel on multiline messages

Check the following:

[X] I have checked the behavior after setting "vscode-neovim.neovimClean" in VSCode settings.
[X] I have read the vscode-neovim docs.
[X] I have searched existing issues.

Neovim version (nvim -v)
0.10.0
Operating system/version
MacOS 14.4
Describe the bug
In recent versions of this extension (> v1.13.1) the output panel gets focused whenever neovim outputs multiline messages. This behavior does not happen in v1.13.1, and is probably related to the "revamp messages output channel" PR (https://github.com/vscode-neovim/vscode-neovim/pull/2024) introduced in v1.14.
I use a neovim plugin (pounce) with this extension, and that plugin outputs multiline messages in the course of normal use, which has made this extension near unusable because it's now constantly covering up the terminal window or otherwise refocusing things against my will.
VS code's focusing behavior is quite aggressive and is not configurable (there are lot of longstanding issues about this in the vs code repo) so it would be nice to have a setting to disable this behavior in vscode-neovim
Related to: https://github.com/vscode-neovim/vscode-neovim/issues/2046 and https://github.com/vscode-neovim/vscode-neovim/issues/1812
Steps To Reproduce

emit a multi-line message in neovim (:echom "test\n").
The ouput panel pops up, taking over focus from whatever was visible previously

Expected Behavior
The extension behaves the same as it did in v1.13.1 and shows multiline output in the status bar area rather than the output channel

I use a neovim plugin (pounce) with this extension, and that plugin outputs multiline messages in the course of normal use,

So... why not configure that plugin to disable that behavior? If Nvim displays a multiline message, then vscode-neovim displays it. It makes no sense to expect anything different.

Related but without any plugins, I'm getting very annoyed when doing a search that don't exist like /foobar and getting the vscode panel open with the messages:
search hit BOTTOM, continuing at TOP
E486: Pattern not found foobar

This is builtin and I would expect this to work without disrupting the UI and my current focus.
Could you please reopen and change back this behavior?

Yes, as @bew explained, this issue is larger than just the issue I have with the pounce plugin, as shown by the related issues I linked (https://github.com/vscode-neovim/vscode-neovim/issues/1812 and https://github.com/vscode-neovim/vscode-neovim/issues/2046).
While I may be able to configure pounce to not output multiline messages, that does not solve the larger issue: there should be a less intrusive way to display multiline messages. While you are correct that neovim does display multi-line output, neovim does not take up half the available screen real estate to display two line messages.
Additionally, this is a regression in this repo, versions of nscode-neovim before 14 do not have this usability breaking behavior.

I can't reproduce that issue (with my personal config as well as with vscode-neovim.neovimClean), messages are not focused when a search fails

this issue is easily reproducible with vscode-neovim.neovimClean by doing :echom "test\n" as I wrote in the original report

by doing :echom "test\n" as I wrote in the original report

By echoing a multiline message you are literally asking Nvim (and vscode-neovim) to show a message. The messages Output channel is how multiline messages are displayed.

In version 13.1 they were displayed in the status bar without focusing the Output panel.

The statusbar can only show one line.
It might be the case that we need to adjust a threshold so that the Output channel is only shown if there are >=2 EOL chars.
Thus this does not focus the Output channel:
:echom "test\n"

but this does:
:echom "test\ntest\n"

That would help, thank you for reopening the issue, much appreciated. Would making the threshold configurable via a user setting increase the complexity significantly? I'd be interested in contributing to make that happen if helpful

This behavior has existing for at least 1 year. Most likely just the threshold needs to be adjusted.
We don't need a setting. I have yet to see any explanation about why you think it makes sense for an Nvim plugin to display a long message but you expect vscode-neovim not to show it.
So far, the only cases mentioned here are about 2-line messages. That shouldn't exceed the threshold. But if a 3-line message is displayed by Nvim, it makes no sense to insist that vscode-neovim should not display it. Fix your plugins, in that case.

I was also looking just now to see how to stop the output panel from keeping on opening.
Is there a way to prevent it from opening if I don't want to see any multi line messages that may be being outputted?
Similar to @bew the panel is distracting and taking up space. I would like to choose for it not to open by itself.
Any help would be greatly appreciated :) thanks

I'm having the same experience here. When the search does not find anything the output panel pops out to show the message. This did not happen previously, so it looks like some recent change to vscode-neovim is causing it.
Adjusting the threshold up would work to fix the immediate annoyance.

This behavior has existing for at least 1 year. Most likely, a recent PR may have regressed the threshold.

Does that mean there is a plan to fix that threshold?

We don't need a setting. I have yet to see any explanation about why you think it makes sense for an Nvim plugin to display a long message but you expect vscode-neovim not to show it.

Personally I don't mind it showing it once (similar to debug opening the panel when started), but then I would like it to respect my decision to close the panel and stay closed for future messages if I choose not to read the messages, rather than continuing to open after being closed.

So far, the only cases mentioned here are about 2-line messages. That shouldn't exceed the threshold. But if a 3-line message is displayed by Nvim, it makes no sense to insist that vscode-neovim should not display it. Fix your plugins, in that case.

Messages should be displayed, but it should be the user's choice to read them and not to have a panel automatically open.
Many messages go into the output or sql console or debug console, but they don't automatically open up the panel. I can choose to open the panel and read them if I desire.

@justinmk

This behavior has existing for at least 1 year. Most likely, a recent PR may have regressed the threshold.

Yes, I decreased the threshold from 3 to 2 because it seemed like an accident. Before, it would show the logs panel, which is way more than any user would really need to show a message. I suppose I could have filtered out empty lines in that count...

rolled it back and 1.13.0 seems quite to me :)
thanks

Set cmdheight to a higher value

I am getting something similar in current version(1.18.12) where when i yank multiple lines in visual studio mode.
@xiyaowong

@mike-rambil, I've test now, and adding ':set cmdheight=10' to my init file solved it for me. Did you try that?


Allow to build the docs without RTD theme

I don't really understand the 1/0 bit, but I suppose it is a debugging leftover.
Anyway. In RHEL 9, py3c-doc is the only package that seem to require sphinx_rtd_theme on runtime. This should allow us to not use it there.
https://tiny.distro.builders/view-rpm--view-eln--python3-sphinx_rtd_theme.html

Indeed, it all looks like a debugging leftover. Thanks!


Add a link for translation

I saw some issues about translating reactjs.org so I think it makes sense to add a link of Crowdin into README.md.
Thanks!

Thank you, there are lots of translation requests 😄

Thanks!


deserializeUser not triggering through browser, but working with postman

In my MEAN project, I have used passport authentication and calling login service from angular 5 service. When I hit the login service from browser I am getting success response but userdata coming as null, but userdata coming properly when I hit service through postman.
I have consoled  in deserializeUser but this deserializeUser not triggering when I tried through browser.

Perhaps your browser differently distinguishes data, you need to write a language-platform-independent serialization code.


using the behavex-images, image icons are missing for failed scenarios in the html report generated

Hello hrcorval,
Could you please help me fix this, below are details of before_all and after step definitions
def before_all(context):
run_type = os.getenv('RUN_TYPE', 'dry')
if run_type == 'parallel':
if hasattr(context, 'driver'):
image_attachments.set_attachments_condition(context.driver, AttachmentsCondition.ONLY_ON_FAILURE)
else:
pass
def after_step(context, step):
run_type = os.getenv('RUN_TYPE', 'dry')
if run_type == 'parallel' and step.status == 'failed':
screenshot_name = f"{step.name}_{threading.get_ident()}.png"
screenshot_path = os.path.join(os.getcwd(), f'screenshots/', screenshot_name)
# create_folder(screenshot_path)
thread_local.driver.save_screenshot(screenshot_path)
with open(screenshot_path, "rb") as image_file:
image_attachments.attach_image_binary(context, image_file.read())
# image_attachments.attach_image_binary(context, context.driver.get_screenshot_as_png())
if step.status == 'failed':
if not hasattr(thread_local, 'driver'):
thread_local.driver = context.driver
screen_shot_name = getattr(step, 'name', 'Unnamed Step')
try:
screenshot = context.driver.get_screenshot_as_png()
allure.attach(screenshot, name=screen_shot_name, attachment_type=AttachmentType.PNG)
except Exception as error:
print(f"Failed to take screenshot: {error}")
is the report generated with out image icon

could you please guide

Hi @Yaswanthbobbu, I was checking your code and I see some things:
1- In the following line:
image_attachments.set_attachments_condition(context.driver, AttachmentsCondition.ONLY_ON_FAILURE)
You should only pass the context variable, instead of context.driver. Like this:
image_attachments.set_attachments_condition(context, AttachmentsCondition.ONLY_ON_FAILURE)
2- You don't need to check if the scenario passed or failed, the attachments condition will do it for you, so this statement is not necessary:
if run_type == 'parallel' and step.status == 'failed'
In the same line, the screenshots from previous steps will not be stored if you are storing the screenshots only if a step failed.
When setting AttachmentsCondition.ONLY_ON_FAILURE, if the scenario failed, it will store the screenshots from the failing and the previous steps and show them in the gallery, and if the scenario passed, all the screenshots will be discarded.
Please, keep me posted on this.
Thanks!

Hello hrcorval,
Thanks a ton for your kind response.. still i couldnt see any image in the html report
im now simply using
def before_all(context):
image_attachments.set_attachments_condition(context, AttachmentsCondition.ONLY_ON_FAILURE)
def after_step(context, step):
try:
image_attachments.attach_image_binary(context, context.driver.get_screenshot_as_png())
except Exception as error:
print(f"Failed to take screenshot for parallel run: {error}")
After successful execution no images are stored in img_attachement_utils folder and nothing in html report.
could you please help me

Hi @Yaswanthbobbu , thanks for the feedback you provided, it was very useful to identify a bug in the behavex-images library. The bug was fixed and the release version 3.0.7 is ready to use.
You can update the library in your project. Not sure which tool you use to install all libraries, but here you have a couple of examples with pip, and also pipenv:

pip install behavex-images  --upgrade
pipenv update behavex-images

I hope that with this change you start seeing the image gallery. Otherwise, we can continue working to ensure it works.
Thanks,

Hello @hrcorval
Thank you very much.. for taking some time to respond.. I have upgraded but still i doesnt work
below are the snippets of code for your ref
bdd_runner.py file has below command
def parallel_run_tests(tag, result_dir, num):
parallel_results_dir = os.path.join(result_dir, "allure-results")
parallel_reports_dir = os.path.join(result_dir, "allure-report")
command = [
'behavex',
'tests/bdd',
f'-t={tag}',
'--tags=~@wip',
'--tags=~@skip',
'--tags=~@ok-to-fail',
f'--parallel-processes={num}',
'--parallel-scheme=feature',
'-o', parallel_results_dir
]
subprocess.run(command, stdout=subprocess.PIPE, stderr=subprocess.PIPE, text=True)
subprocess.run(['allure', 'generate', parallel_results_dir, '-o', parallel_reports_dir, '--clean'], shell=True)
subprocess.run(['allure', 'open', parallel_results_dir], shell=True)     # >> using parallel_report_dir doesnt generate behavex html report

environment.py file has
def before_all(context):
if hasattr(context, 'driver'):
image_attachments.set_attachments_condition(context, AttachmentsCondition.ONLY_ON_FAILURE)
def after_step(context, step):
run_type = os.getenv('RUN_TYPE', 'dry')
screenshot = context.driver.get_screenshot_as_png()
if run_type == 'dry':
screenshot_name = getattr(step, 'name', 'Unnamed Step')
allure.attach(screenshot, name=screenshot_name, attachment_type=AttachmentType.PNG)
if run_type == 'parallel':
image_attachments.attach_image_binary(context, screenshot)
    image_attachments_utils doesnt have any images stored.

adding screenshots..

when open index.html

Hi @Yaswanthbobbu, your feedback is very important to determine the root cause of the issue. Considering you are seeing the "image_attachments_utils" folder empty and the "Another program is using the files in path..." message when performing a retry, I can infere the issue is relate with the write privileges on the executing processes over the output folder.
The behavex-images library, executes the following command to copy all assets into the image_attachments_utils folder:
shutil.copytree(image_attachments_path, destination_path) (https://github.com/abmercado19/behavex-images/blob/master/behavex_images/extend_environment.py#L261)
Also, when you get the "Another program is using the files in path..." message when performing a retry, this is because the files generated from previous execution could not be removed, due to there is another process still using the files from previous executions or the test execution process does not have privileges to remove the files.
Considering your evidence, I would take the path of reviewing the read/write privileges of the test execution processes over the output folder.
Please, keeps us posted on that.
Thanks!

Hi @hrcorval
Firstly thanks for your response..
and slight correction (to avoid any misleading please)  I have told  image_attachments_utils doesn't have any images stored.
but not empty ( it has all support/generic files that are present by befault)
attached screenshot

Hi @Yaswanthbobbu, we have been busy with our daily activities, and I just wanted to know if you were able to see the screenshots as expected.
Thanks,

Hi @hrcorval,
No couldnt see the screenshots for failed scenarios.

Hello @hrcorval, @prasanmgc
Now able to see screen shots
have upgraded numpy and added np.float = float
This issue can be closed

Hello @Yaswanthbobbu, I just wanted to let you know that we have released a new version of behavex-images library (3.0.8), that contains the fixes you need.
I'm glad to see the root cause was identified and fixed.
Thanks!


Ghidra cannot recognize pointer type in decompiler

Describe the bug
I analyzed a single function in both IDA and Ghidra, IDA can recognize pointer type of a variable, but Ghidra can't, both of them know that type exists.
To Reproduce
unfortunately I don't know how you can reproduce this, I analyzed a malware
Expected behavior
Ghidra should recognize pointer type and cast that value to that type
Environment (please complete the following information):

OS: Windows 11
Java Version: 18
Ghidra Version: 10.3.2
Ghidra Origin: GitHub distro

There is not enough information here for us to be able to act on anything.  We would need some screen shots of the difference and the binary attached to proceed.

@ryanmkurtz I cannot attach the binary, because it's somehow private.
But I'll share the screenshots.

Ghidra:

IDA pro:

Any thoughts on this ?

The poor decompilation is the result of user error because the type of m_pCoverEntity is probably not defined. However, if this information should have come from debug information then there may be a bug in that processing.


Emit createRequire for require calls when compiling to module targets

Describe the feature
This was previously reported in #4101 and a PR was opened in #4850.
Calls to require() aren't transpiled when compiling to module targets. This causes module bundles with dependencies that use require() to fail at runtime due to fail with ReferenceError: require is not defined.
As reported in #4101 and the reason it was closed, require calls are transpiled when used with export import, but not in other cases:
export import path1 = require("path");
const path2 = require("path")
const path3 = (() => require("path"))()

This results in the following output with only the first require call changed:
import { createRequire as _createRequire } from "module";
const __require = _createRequire(import.meta.url);
export const path1 = __require("path");
const path2 = require("path");
const path3 = (()=>require("path"))();

SWC Playground URL
Babel plugin or link to the feature description
No response
Additional context
This behavior breaks minimatch on Windows as it gets the path separator from a require call at runtime, with swc creating the following output:
var minimatch_1$1 = minimatch$1;
minimatch$1.Minimatch = Minimatch$1;
var path$8 = function() {
    try {
        return require('path');
    } catch (e) {
        console.error(e);
    }
}() || {
    sep: '/'
};

TS does same

and doc says
https://www.typescriptlang.org/docs/handbook/modules/reference.html#summary

ESM emit transforms import x = require("...") to a require call constructed from a createRequire import.

The transform is for the import ... calls.
Do you have a ts repro that works as you mentioned?


[util] Added Python script to generate a status report of the DIFs.

This utility can be used to generate the table(s) shown below that:

Cross reference commit dates between hardware and DIF software to indicate which DIFs may need updating.
Determine who the main authors are for both hardware IP and DIF software to track down implementation details of each.
Indicate if a DIF API is currently incomplete, based on the function definitions in the DIF header file.

Usage: check_dif_statuses [-h] [--show-unimplemented] repo_top
Example DIF Status Table:

Example Unimplemented DIF Functions Table:

Signed-off-by: Timothy Trippel<EMAIL_ADDRESS>

@tjaychen @cfrantz @mcy please review

Hey @timothytrippel , I have noticed couple small mistakes. DIF_UART was actually written by me, and I think (but might be wrong) that DIF_GPIO was written by @alphan (but worth double checking with him).

Hey @timothytrippel , I have noticed couple small mistakes. DIF_UART was actually written by me, and I think (but might be wrong) that DIF_GPIO was written by @alphan (but worth double checking with him).

Yes, I guess this is due to the renames/updates that @mcy did (thanks). Didn't check which metric you are using to figure out the author but you may want to list two names (maybe github usernames to keep it shorter) if it won't be a big change, may be helpful when folks are OOO or move on to something else. Not a big deal though.

Hey @timothytrippel , I have noticed couple small mistakes. DIF_UART was actually written by me, and I think (but might be wrong) that DIF_GPIO was written by @alphan (but worth double checking with him).
P.S.
Pretty cool tool, thanks! :)

@silvestrst  My apologies! The current way the tool computes the main "HW/DIF Authors" is based on most lines of code (LOC) committed, where  LOC = additions + deletions. As @alphan noted, the reason @mcy is showing up as the main author is because he must have done some refactoring.
Another thing @alphan noted was that I should be careful to makes sure that "author" is not confused with "committer".
Additionally, @imphil good point, I will see if I can work that into the tool too.
---TL;DR---
To address all of the above, I will:

[ ] alter the way main authors are determined to list the top two authors if there are two authors that contribute more than 5-10% of the LOC. (This should at least give an interested party a general point-of-contact for a potential DIF owner.)
[ ] switch author names to github usernames for brevity
[ ] add DIF lifecycle state to table
[ ]  look into if it is possible to indicate author's status as active contributor to the project (not sure if the backend tools I am using expose such information or if there is a way to retrieve it.)

In addition to completing the above checklist items, I also:

verified authors, not committers, are indeed listed (the python module I am using, git-fame, uses the git blame command under the hood which make this distinction).
removed the "completed?" column, as this information is redundant given the color coding scheme/legend
added multi-line cells to table for width reduction and better displaying in the terminal

One thing to note: when I was grabbing the DIF lifecycle states from the .prj.hjson files, if the IP had multiple revisions, I simply grabbed the latest.

In addition to completing the above checklist items, I also:
* verified authors, not committers, are indeed listed (the python module I am using, git-fame, uses the `git blame` command under the hood which make this distinction).

* removed the "completed?" column, as this information is redundant given the color coding scheme/legend

* added multi-line cells to table for width reduction and better displaying in the terminal

One thing to note: when I was grabbing the DIF lifecycle states from the .prj.hjson files, if the IP had multiple revisions, I simply grabbed the latest.

This seems like a really useful tool, and I think given the constraint of pulling metadata just from the repository is doing a good job of presenting information. In terms of future development, we might think about whether it would be useful to add more metadata to the repository (perhaps reflecting what is tracked in external spreadsheets / project planning software). For instance, knowing the authors/contributors via git blame is useful, but you could also imagine adding something to prj.hjson to track the current "maintainer".
Perhaps bikeshedding a bit, but maybe for both "DIF Author" and "HW Author" a more neutral term might be "Contributors" (which feels like it more naturally includes the possibility of someone running up lots of LOC changes through refactoring).

In addition to completing the above checklist items, I also:
* verified authors, not committers, are indeed listed (the python module I am using, git-fame, uses the `git blame` command under the hood which make this distinction).

* removed the "completed?" column, as this information is redundant given the color coding scheme/legend

* added multi-line cells to table for width reduction and better displaying in the terminal

One thing to note: when I was grabbing the DIF lifecycle states from the .prj.hjson files, if the IP had multiple revisions, I simply grabbed the latest.

This seems like a really useful tool, and I think given the constraint of pulling metadata just from the repository is doing a good job of presenting information. In terms of future development, we might think about whether it would be useful to add more metadata to the repository (perhaps reflecting what is tracked in external spreadsheets / project planning software). For instance, knowing the authors/contributors via git blame is useful, but you could also imagine adding something to prj.hjson to track the current "maintainer".

Agreed. This would reduce ambiguity around who is actively responsible for various components (especially if someone leaves the project).
Additionally it may be useful for this tool include another flag that quickly returns the git log between when the hardware was last updated to when the software (DIF) was, so one does not have to manually cross-ref the dates listed in the table with the commit log.

Perhaps bikeshedding a bit, but maybe for both "DIF Author" and "HW Author" a more neutral term might be "Contributors" (which feels like it more naturally includes the possibility of someone running up lots of LOC changes through refactoring).

Fixed.

This looks great, thanks! Could we add a shortcode to generate the table inline in the https://docs.opentitan.org/sw/ area?

Yes! I can definitely do that (I'm using the tabulate module to generate the table so we can output several formats, Markdown being one). However, would this would be a better location?

This looks great, thanks! Could we add a shortcode to generate the table inline in the https://docs.opentitan.org/sw/ area?

Yes! I can definitely do that (I'm using the tabulate module to generate the table so we can output several formats, Markdown being one). However, would this would be a better location?

Added arg. to specify table format.  All of which are forms of Markdown.

@cfrantz Added type annotations and docstrings.

If there are no more comments/concerns could we merge this? Thanks!

This looks great, thanks! Could we add a shortcode to generate the table inline in the https://docs.opentitan.org/sw/ area?

Yes! I can definitely do that (I'm using the tabulate module to generate the table so we can output several formats, Markdown being one). However, would this would be a better location?

Yes, that's indeed a better location. Thanks!

This looks great, thanks! Could we add a shortcode to generate the table inline in the https://docs.opentitan.org/sw/ area?

Yes! I can definitely do that (I'm using the tabulate module to generate the table so we can output several formats, Markdown being one). However, would this would be a better location?

Yes, that's indeed a better location. Thanks!

Script argument (--table-format) added. Will address adding to table to website in a separate PR.

Merging since this PR received multiple approvals and all review feedback has been addressed.


Unable to read EDF file

Hello
I'm working on an EEG signal but even after trying several ways, I'm unable to read the dataset.
There is an error  of null values in the header while reading with mne
I have around 200 edf files in the dataset all have the same issue. Can you please identify the issue.

Can you share one of the problematic files with us?

Zipped two files.Please check.Hope you can figure out
Thankyou
edffiles.zip

Both files work for me with the latest 0.20.1 release - please update MNE and try again.

Thankyou for your reply
Im using same version but get this error (check attached)
My script is
import mne
f='0000002.edf'
edf_file = mne.io.read_raw_edf(f, preload = True)
If you can please check my script
Thankyou

Got it, you're using the current dev version and I can reproduce the error with the current master. I'll try to figure out what change introduced the regression.

 In fact, current master still works and correctly loads your example file. Same for 0.20.1. I guess you are referring to the issue reported and fixed in #7641. Prior to 0.20.1, I can indeed reproduce the error.
 Please either pull the latest changes from upstream (your remote might also be called origin depending on how you cloned the repo):
git pull upstream

However, I'd recommend to work with a release version which you can install with pip:
pip install -U mne

Thanks for investigating and explaining @cbrnr

@cbrnr can you please share script with me


Miscellaneous tidying from reading through

No functional changes intended

Whoops, failed to see that two unrelated hunks were sufficiently proximate that git merged them together.  Let's try that again.


Package installed in dev mode should be seen differently in venv view

I installed a package using pip install -e .:
> pip freeze | grep msrest
-e git+https://github.com/Azure/msrest-for-python.git@362e7c175828ceb35d1122fa74314a9c19ac3459#egg=msrest
-e git+https://github.com/Azure/msrestazure-for-python.git@b1e58c329a988042737ca159b3b5b4704cb3d8d1#egg=msrestazure

On PTVS, this is shown as a regular package:

I would like something to tell me that it's installed in dev mode (color, text, etc.)
Not super critical of course, but I had to "pip freeze" from a console to check they were installed in dev mode, and I should just be able to see it right away.

We use pip list --format=json to list these packages, so if that doesn't display them any differently then I'm not sure what we can do. I guess we could go back to doing pip freeze and parsing the output manually, but I'd rather not...

@zooba You can use this command to get the installed editable in JSON:
> pip list -e --format=json
[{"version": "0.4.11", "name": "msrest"}, {"version": "0.4.10", "name": "msrestazure"}]


[plot] Rework ROI signal

PR #2584 adds a setVisible to ROI items with no signal associated.
Plot ROI items signals needs to be reworked at least to add a signal for the visibility (and eventually at a larger scale to provide the different kind of updates).
Some ideas for the visibility (initially proposed in PR #2584): Either a sigItemChanged as for other plot items (maybe the best), or a sigVisibleChanged, or eventually through the already exisiting sigRegionChanged...

BTW inheriting from plot item could make sense. Which could be taken into account to decide what to do with the signal.

Yes, that's what I had in mind.

setEditable also has no associated signal, btw. I noticed that a programmatic call of this method does not update the checkbox in RegionOfInterestTableWidget
I'm reporting this just for info. I personally don't need this feature.

Thaks for the report, I've opened a separate issue for it : #2595


[ROX-12403][FE] Send cve names to suppress/unsupress API

Description
Pulled required FE changes from #2849.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
See

/retest

Verified the changes again with and without postgres.


DB test data

It would be nice for development to have some fake data in DB. It can be some gradle task that fill DB with such data.
Faker library can be used for that.

Since we are using flyway for DB migration. We can utilize this interface and which offeres oportunity to implement custom hooks https://flywaydb.org/documentation/api/javadoc/org/flywaydb/core/api/callback/FlywayCallback. After implementing you can just add fully qualified name to config under callback directive @see https://flywaydb.org/documentation/gradle/migrate.