Missing instruction for Spring Update

Hi all,
I understand this document is refering the Fall update. But is there a current version for the new spring release?
Thank you :)

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

ID: 0bd423d2-dba9-a2ef-5222-aeed7a064393
Version Independent ID: c07a6696-37fd-f026-c872-6c243dc45dcb
Content: Scale session hosts Azure Automation - Azure
Content Source: articles/virtual-desktop/virtual-desktop-fall-2019/set-up-scaling-script.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

Thanks for the question. We are currently investigating and will update you shortly.

@Heidilohr I couldn't find the document for Scaling session hosts for Spring release. Do you know if one exists? Thanks :)


Update Kotlin language compatibility and stdlib to 1.7

Goal

Testing

Release Notes

WHAT:
WHY:

#1057  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @bidetofevil and the rest of your teammates on  Graphite


How to delete all data in the table?

I want to delete all the data in a data table. I used the Delete() method, but this method seems to have to enter a condition to delete.
I checked the source code, it seems that you have judged whether there is a where condition, if not, it returns an error.
So which method should I use to clear the data?
我想删除一个数据表的全部数据,我使用了Delete()这个方法,但是这个方法好像是必须要输入一个条件才能删除.
我查看了一下源码,好像是里面你判断了是否有where条件,如果没有,就返回错误.
那我应该用哪个方法来清空数据呢?

比如主键大于0就可以

where id >0

@jaryf Delete is a sensitive method, so there should be Where condition given to make it rigorous.


Remove ARMv5 toolchain from JenkinsFile

ARMC6 is replacing ARMv5.
DO NOT MERGE!

This PR was just for testing new toolchain. Testing complete and this can be closed.


Enhancement completed locale wise channel settings

BUGS:
Link: https://github.com/bagisto/bagisto/issues/4380
STEPS:

Run composer dump-autoload.
Run php artisan optimize.
Run php artisan migrate.
Run php artisan db:seed.

Note
Channel seeder has been updated, so if someone use this pr will need to take a backup of their channels table because some columns are moved to channel_translations.

@devansh-webkul Kindly check the below mention point

Getting error when trying to change the locale from filter https://prnt.sc/w75b2q

remove this filter from the channel list https://prnt.sc/w75lo3

add the locale symbol with field which support localized data https://prnt.sc/w75osi

@vaishaliwebkul,
The mentioned changes have been fixed.


Update to monaco-vscode-api 1.83.16

Related to https://github.com/CodinGame/monaco-vscode-api/pull/276
This will be ready for review once the above PR is merged.

@CGNonofr this is ready and looks good from my POV.

Release preparation is included here as well now.


Fix Dotnet & Mono build warnings

Changed naming:
DOTNET_CORE to DotNetCore
MONO to Mono
Fixes the following warning in the windows build:
CMake Warning (dev) at C:/opt/ros/foxy/x64/Lib/site-packages/cmake/data/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273 (message):
The package name passed to find_package_handle_standard_args
(DOTNET_CORE) does not match the name of the calling package (DotNetCore).
This can lead to problems in calling code that expects find_package
result variables (e.g., _FOUND) to follow a certain pattern.
Same was for the Mono part.
Only changed the naming, tested it with Windows 11 + Humble & Ubuntu 22.04 + Humble

This MR should fix https://github.com/ros2-dotnet/ros2_dotnet/issues/75


[ERROR] error syncing 'cattle-system/helm-operation-62vfx ,rancher 2.6.9

2022/11/08 06:39:16 [INFO] dynamic schema for kontainerdriver amazonelasticcontainerservice updating
2022/11/08 06:39:17 [INFO] namespaceHandler: addProjectIDLabelToNamespace: adding label field.cattle.io/projectId=p-7f8fv to namespace=cattle-fleet-clusters-system
2022/11/08 06:39:17 [ERROR] namespaceHandler: Sync: error adding project id label to namespace err=Operation cannot be fulfilled on namespaces "cattle-fleet-clusters-system": the object has been modified; please apply your changes to the latest version and try again
2022/11/08 06:39:17 [INFO] namespaceHandler: addProjectIDLabelToNamespace: adding label field.cattle.io/projectId=p-7f8fv to namespace=cattle-fleet-clusters-system
2022/11/08 06:39:17 [ERROR] namespaceHandler: Sync: error adding project id label to namespace err=Operation cannot be fulfilled on namespaces "cattle-fleet-clusters-system": the object has been modified; please apply your changes to the latest version and try again
2022/11/08 06:39:17 [INFO] namespaceHandler: addProjectIDLabelToNamespace: adding label field.cattle.io/projectId=p-7f8fv to namespace=cattle-fleet-clusters-system
2022/11/08 06:39:26 [ERROR] Failed to read API for groups map[gitjob.cattle.io/v1:the server could not find the requested resource]
E1108 06:39:26.816630      33 gvks.go:69] failed to sync schemas: unable to retrieve the complete list of server APIs: gitjob.cattle.io/v1: the server could not find the requested resource
E1108 06:39:26.991658      33 gvks.go:69] failed to sync schemas: unable to retrieve the complete list of server APIs: gitjob.cattle.io/v1: the server could not find the requested resource
E1108 06:39:27.232415      33 gvks.go:69] failed to sync schemas: unable to retrieve the complete list of server APIs: gitjob.cattle.io/v1: the server could not find the requested resource
2022/11/08 06:39:28 [INFO] Watching metadata for fleet.cattle.io/v1alpha1, Kind=ImageScan
2022/11/08 06:39:28 [INFO] Watching metadata for fleet.cattle.io/v1alpha1, Kind=ClusterRegistrationToken
2022/11/08 06:39:28 [INFO] Watching metadata for fleet.cattle.io/v1alpha1, Kind=GitRepo
2022/11/08 06:39:28 [INFO] Watching metadata for fleet.cattle.io/v1alpha1, Kind=GitRepoRestriction
2022/11/08 06:39:28 [INFO] Watching metadata for fleet.cattle.io/v1alpha1, Kind=BundleNamespaceMapping
2022/11/08 06:39:28 [INFO] Watching metadata for fleet.cattle.io/v1alpha1, Kind=Content
2022/11/08 06:39:28 [INFO] Watching metadata for fleet.cattle.io/v1alpha1, Kind=BundleDeployment
2022/11/08 06:39:28 [INFO] Watching metadata for fleet.cattle.io/v1alpha1, Kind=ClusterRegistration
2022/11/08 06:39:28 [INFO] Watching metadata for fleet.cattle.io/v1alpha1, Kind=ClusterGroup
2022/11/08 06:39:29 [ERROR] error syncing 'cattle-fleet-system/helm-operation-nm8s6': handler helm-operation: an error on the server ("container not found ("proxy")") has prevented the request from succeeding (get pods helm-operation-nm8s6), requeuing
2022/11/08 06:39:29 [ERROR] error syncing 'cattle-fleet-system/helm-operation-nm8s6': handler helm-operation: an error on the server ("container not found ("proxy")") has prevented the request from succeeding (get pods helm-operation-nm8s6), requeuing
2022/11/08 06:39:29 [ERROR] error syncing 'cattle-fleet-system/helm-operation-nm8s6': handler helm-operation: an error on the server ("container not found ("proxy")") has prevented the request from succeeding (get pods helm-operation-nm8s6), requeuing
2022/11/08 06:39:29 [ERROR] error syncing 'cattle-fleet-system/helm-operation-nm8s6': handler helm-operation: an error on the server ("container not found ("proxy")") has prevented the request from succeeding (get pods helm-operation-nm8s6), requeuing
2022/11/08 06:39:29 [ERROR] error syncing 'cattle-fleet-system/helm-operation-nm8s6': handler helm-operation: an error on the server ("container not found ("proxy")") has prevented the request from succeeding (get pods helm-operation-nm8s6), requeuing
2022/11/08 06:39:29 [ERROR] error syncing 'cattle-fleet-system/helm-operation-nm8s6': handler helm-operation: an error on the server ("container not found ("proxy")") has prevented the request from succeeding (get pods helm-operation-nm8s6), requeuing
2022/11/08 06:39:30 [INFO] Watching metadata for gitjob.cattle.io/v1, Kind=GitJob
2022/11/08 06:39:35 [INFO] namespaceHandler: addProjectIDLabelToNamespace: adding label field.cattle.io/projectId=p-7f8fv to namespace=cluster-fleet-local-local-1a3d67d0a899
2022/11/08 06:39:36 [ERROR] namespaceHandler: Sync: error adding project id label to namespace err=Operation cannot be fulfilled on namespaces "cluster-fleet-local-local-1a3d67d0a899": the object has been modified; please apply your changes to the latest version and try again
2022/11/08 06:39:36 [INFO] namespaceHandler: addProjectIDLabelToNamespace: adding label field.cattle.io/projectId=p-7f8fv to namespace=cluster-fleet-local-local-1a3d67d0a899
2022/11/08 06:39:36 [ERROR] namespaceHandler: Sync: error adding project id label to namespace err=Operation cannot be fulfilled on namespaces "cluster-fleet-local-local-1a3d67d0a899": the object has been modified; please apply your changes to the latest version and try again
2022/11/08 06:39:36 [INFO] namespaceHandler: addProjectIDLabelToNamespace: adding label field.cattle.io/projectId=p-7f8fv to namespace=cluster-fleet-local-local-1a3d67d0a899
2022/11/08 06:39:40 [ERROR] defaultSvcAccountHandler: Sync: error handling default ServiceAccount of namespace key=cattle-fleet-local-system, err=Operation cannot be fulfilled on namespaces "cattle-fleet-local-system": the object has been modified; please apply your changes to the latest version and try again
2022/11/08 06:39:40 [INFO] namespaceHandler: addProjectIDLabelToNamespace: adding label field.cattle.io/projectId=p-7f8fv to namespace=cattle-fleet-local-system
2022/11/08 06:39:40 [ERROR] namespaceHandler: Sync: error adding project id label to namespace err=Operation cannot be fulfilled on namespaces "cattle-fleet-local-system": the object has been modified; please apply your changes to the latest version and try again
2022/11/08 06:39:40 [INFO] namespaceHandler: addProjectIDLabelToNamespace: adding label field.cattle.io/projectId=p-7f8fv to namespace=cattle-fleet-local-system
2022/11/08 06:39:50 [ERROR] error syncing 'cattle-system/helm-operation-62vfx': handler helm-operation: an error on the server ("container not found ("proxy")") has prevented the request from succeeding (get pods helm-operation-62vfx), requeuing
2022/11/08 06:39:50 [ERROR] error syncing 'cattle-system/helm-operation-62vfx': handler helm-operation: an error on the server ("container not found ("proxy")") has prevented the request from succeeding (get pods helm-operation-62vfx), requeuing
2022/11/08 06:39:50 [ERROR] error syncing 'cattle-system/helm-operation-62vfx': handler helm-operation: an error on the server ("container not found ("proxy")") has prevented the request from succeeding (get pods helm-operation-62vfx), requeuing
2022/11/08 06:39:50 [ERROR] error syncing 'cattle-system/helm-operation-62vfx': handler helm-operation: an error on the server ("container not found ("proxy")") has prevented the request from succeeding (get pods helm-operation-62vfx), requeuing
2022/11/08 06:39:50 [ERROR] error syncing 'cattle-system/helm-operation-62vfx': handler helm-operation: an error on the server ("container not found ("proxy")") has prevented the request from succeeding (get pods helm-operation-62vfx), requeuing
2022/11/08 06:39:50 [ERROR] error syncing 'cattle-system/helm-operation-62vfx': handler helm-operation: an error on the server ("container not found ("proxy")") has prevented the request from succeeding (get pods helm-operation-62vfx), requeuing
2022/11/08 06:39:50 [ERROR] error syncing 'cattle-system/helm-operation-62vfx': handler helm-operation: an error on the server ("container not found ("proxy")") has prevented the request from succeeding (get pods helm-operation-62vfx), requeuing
2022/11/08 06:39:51 [ERROR] error syncing 'cattle-system/helm-operation-62vfx': handler helm-operation: an error on the server ("container not found ("proxy")") has prevented the request from succeeding (get pods helm-operation-62vfx), requeuing
2022/11/08 06:41:37 [INFO] starting duplicate binding cleanup
2022/11/08 06:41:37 [INFO] [clean-dupe-bindings] starting bindings cleanup
2022/11/08 06:41:37 [INFO] [clean-dupe-bindings] total PRTB duplicate clusterRoleBindings 0, roleBindings 0
2022/11/08 06:41:37 [INFO] [clean-dupe-bindings] binding with deterministic name not found, will delete all except the oldest binding
2022/11/08 06:41:37 [INFO] [clean-dupe-bindings] binding with deterministic name not found, will delete all except the oldest binding
2022/11/08 06:41:37 [INFO] [clean-dupe-bindings] binding with deterministic name not found, will delete all except the oldest binding
2022/11/08 06:41:37 [INFO] [clean-dupe-bindings] binding with deterministic name not found, will delete all except the oldest binding
2022/11/08 06:41:37 [INFO] [clean-dupe-bindings] total CRTB duplicate clusterRoleBindings 0, roleBindings 0
2022/11/08 06:41:37 [INFO] successfully cleaned up duplicate bindings

hello @haodongz  please any tips on that ?
as facing same error:

FYI we have the same issue with the latest release of rancher on a AKS cluster, deployed the exact same way and having the exact same issue.
any updates on this ? 🤞

any updates ? we can't deploy rancher on AKS because of this issue :(

First time using Rancher, I get the same error. Fresh install of Alma 9.3. Unable to access the web GUI, just get a 404 page not found. Web server does seem to be running but that is it.
Docker version 24.0.7, build afdd53b
docker run --privileged -d --restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher
[ERROR] error syncing 'cattle-provisioning-capi-system/helm-operation-gpk25': handler helm-operation: an error on the server ("container not found ("proxy")") has prevented the request from succeeding (get pods helm-operation-gpk25), requeuing

hello @haodongz please any tips on that ?
as facing same error:
`````` `` [ERROR] namespaceHandler: Sync: error adding project id label to namespace err=Operation cannot be fulfilled on namespaces "cattle-fleet-clusters-system": the object has been modified; please apply your changes to the latest version and try again`

I have changed to a new version, thank you


[DOCFIX] Improve Minio docs

Minor improvements for style in Minio docs. Added a section on verifying the setup once the user has entered the configuration.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2114/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2176/
Test PASSed.


Error: Optimization error [main-*.js] TypeError: Cannot read properties of undefined (reading 'comments_before')

🐞 Bug report
Command (mark with an x)

[ ] new
[x] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?
Description
i am using angular 13.3.9
When i run angular ng build , i encounter with error on build time, it seems the error happens in terser package , but the ng serve works fine , here is the full error coded below :
🔬 Minimal Reproduction

🔥 Exception or Error

Error: Optimization error [main.99440f42c92dc940.js]: TypeError: Cannot read properties of undefined (reading 'comments_before')
#17 138.8     at AST_Return._do_print (/usr/src/app/node_modules/terser/dist/bundle.min.js:9867:47)
#17 138.8     at /usr/src/app/node_modules/terser/dist/bundle.min.js:9879:14
#17 138.8     at doit (/usr/src/app/node_modules/terser/dist/bundle.min.js:9296:13)
#17 138.8     at AST_Return. (/usr/src/app/node_modules/terser/dist/bundle.min.js:9303:13)
#17 138.8     at /usr/src/app/node_modules/terser/dist/bundle.min.js:10702:18
#17 138.8     at /usr/src/app/node_modules/terser/dist/bundle.min.js:8983:19
#17 138.8     at OutputStream.with_indent (/usr/src/app/node_modules/terser/dist/bundle.min.js:8948:38)
#17 138.8     at Object.with_block (/usr/src/app/node_modules/terser/dist/bundle.min.js:8982:9)
#17 138.8     at make_block (/usr/src/app/node_modules/terser/dist/bundle.min.js:10700:21)
#17 138.8     at /usr/src/app/node_modules/terser/dist/bundle.min.js:9671:9

🌍 Your Environment

Angular CLI: 13.3.9
Node: 16.15.1
Package Manager: npm 8.12.1
OS: win32 x64

Angular: 13.3.11
... animations, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, platform-server, router
... service-worker

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1303.9
@angular-devkit/build-angular   13.3.9
@angular-devkit/core            13.3.9
@angular-devkit/schematics      13.3.9
@angular/cdk                    13.3.9
@angular/cli                    13.3.9
@angular/fire                   7.4.1
@angular/flex-layout            13.0.0-beta.36
@angular/material               13.3.9
@nguniversal/builders           13.1.1
@nguniversal/express-engine     13.1.1
@schematics/angular             13.3.9
rxjs                            6.6.7
typescript                      4.6.4
webpack                         4.46.0

Anything else relevant?
the error refers to this library code function :

 /* -----[ exits ]----- */
    AST_Exit.DEFMETHOD("_do_print", function(output, kind) {
        output.print(kind);
        if (this.value) {
            output.space();
            const comments = this.value.start.comments_before; // here is error line
            if (comments && comments.length && !output.printed_comments.has(comments)) {
                output.print("(");
                this.value.print(output);
                output.print(")");
            } else {
                this.value.print(output);
            }
        }
        output.semicolon();
    });

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out our submission guidelines to understand why we can't act on issues that are lacking important information.
If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template.


Add findAllocationRecord(ptr)

This feature is needed for integration with MFEM.

I think this could be a useful PR, but it might be better to expose a const version of the AllocationMap, so that users can perform there own introspection?
@robinson96 has something similar in #61

Should be ready to merge.

Looking good, thanks @jdahm


MAINT: Use prerelease SciPy 1.4.0 for speed boost

I suspect that part of the reason some examples take a long time is due to the FFTs being used, which should be faster with scipy.fft. Let's try using the prerelease wheels of SciPy to speed up CircleCI. If it does, we can just live with this for a few months until SciPy 1.4.0 is released.

Didn't have much effect


docs: fix typo

Small typo in guide for migrating from Zwave2MQTT.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 28.366%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3712

Relevant Lines:
13772

💛  - Coveralls


alignment and responsiveness

#686
I have successfully implement responsiveness in every single page . please review it and if any further improvement needed please let me know else merge it.
Thankyou!
Before:

After:

there are conflicts, resolve

I have successfully resolved all the conflicts that were present in the codebase. Additionally, I noticed that in the updated repository the index.html page was not responsive, so I took the initiative to also make it responsive across all devices.
https://github.com/user-attachments/assets/478970c0-c13e-4812-acb6-f3e69bf3f0f6
https://github.com/user-attachments/assets/90e9175d-8d69-4c90-802e-68fc6dbebf30
Please let me know if you have any feedback or if there are other areas you would like me to focus on.

resolved, please merge.

This PR has been merged by the GSSoC team
here - https://github.com/sanjay-kv/Open-source-Practice/pull/1416
Don't add labels to it now.
You'll get the points in the leaderboard update.


Add externs file for the compiler

Ensure that closure compiler does not do away with names that are needed for users using the EventProcessor/Storage interfaces by using an externs file.

The @export tag is used to export a function defined inside of the library for use outside of a library. The @externs tag is for calling functions defined outside of the library for use inside of the library. Any @extern function can be an @export function, but
@export compresses the name of a function to a single letter until it exports it, saving more space. On the other hand, @externs can't ever compress the name of a function since it is defined elsewhere, and so it takes up more space in the library.
In this case, someone could write their own custom event processor, so we have to use the @externs tag to integrate their code with the library.
https://developers.google.com/closure/compiler/docs/api-tutorial3


avoidance ignores pedestrian if there is a bus behind

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
In behavior_path_planner module, it is possible to disable avoidance for some obstacles, such as pedestrian.
For example in the following situation, a pedestrian is on the path and the vehicle does not try to avoid it:

However, if there is another obstacle that can be avoided behind the pedestrian, then the vehicle tries to avoid both:

I guess "unavoidable" obstacles have been introduced to avoid risky manoeuver (e.g. the pedestrian will likely not stay on the middle of the road, so it is better to simply wait). In such case, the vehicle should stop in front of the pedestrian like in the first screenshot.
Expected behavior
The vehicle never avoid non-target obstacle.
Actual behavior
non-target obstacle is avoided under some circumstances
Steps to reproduce
see pictures above
Versions
No response
Possible causes
No response
Additional context
No response

In the second stage, it does seem like to non-target obstacle was ignored. But just in case, can you run
ros2 topic echo /planning/scenario_planning/lane_driving/behavior_planning/behavior_path_planner/debug/avoidance_debug_message_array

I think for the pedestrian ObjectIsNotType will be printed in the second
avoidance_info:
- object_id: ''
  allow_avoidance: false
  longitudinal_distance: 0.0
  lateral_distance_from_centerline: 0.0
  to_furthest_linestring_distance: 0.0
  max_shift_length: 0.0
  required_jerk: 0.0
  maximum_jerk: 0.0
  failed_reason: ObjectIsNotType
- object_id: 6cee772d36247e61b13266516b53093b
  allow_avoidance: true
  longitudinal_distance: 24.38448885981013
  lateral_distance_from_centerline: 1.5808671530619405
  to_furthest_linestring_distance: 5.532324530608035
  max_shift_length: 4.684824530608035
  required_jerk: 0.005692831476198248
  maximum_jerk: 1.0
  failed_reason: ''

If it is so, then the pedestrian object was ignored.

Yes, the avoidance_info contains one entry for the pedestrian with ObjectIsNotType. So if I understand correctly it means the avoidance does not try to avoid the pedestrian. In practice however, the pedestrian is avoided.

Yes, pedestrians are avoided indirectly.If you consider avoiding dangerous operations,additional rules need to be added.

Yes, if pedestrian is registered as non avoidable object, the generated avoidance path will be consider them. In your second case, it just happens that the pedestrian is nearby the bus and it "seems" as if it is avoiding the pedestrian.
By default, if it is not avoidance's object, if it is still blocking ego's route, ego will decelerate and stop.

Yes, I understand how the avoidance logic is implemented.
My point is whether it makes sense for the avoidance to "ignore" some class of obstacles. If this is for the safety of the operation, then it totally makes sense in the 1st scenario, however it is counter-productive in the 2nd scenerio.
Indeed, because the pedestrian is ignored by the avoidance algorithm in the 2nd scenario, it can make the ego vehicle drive super close to the pedestrian, which is certainly not safe at all:

I see. My apologies, before proceeding, let me correct my understanding as follows

Based on your report, the current behavior is similar to the Expected Behavior since the vehicle never avoid non-target obstacle, which in this case is the pedestrian.
However, your concern is about why the parameter doesn't set pedestrian as avoidable object as default.

Is these correct?

Based on your report, the current behavior is similar to the Expected Behavior since the vehicle never avoid non-target obstacle, which in this case is the pedestrian.

I think I have confused everyone with the word "avoid", because we understand different things:

The avoidance algorithm does not take into account the pedestrian when it generates the avoidance trajectory. From this point of view, the planner does not avoid the pedestrian
In practice, the vehicle generates a trajectory that goes around the pedestrian. From this point of view, the planner does avoid the pedestrian. <- this is what I mean.

So when I say the expected behavior is that the vehicle should never avoid non-target obstacles, I mean no trajectory should be able to go around the object, even if it is unintentional.
It is maybe just the way I interpret the target_object parameter, but I think it does not make much sense to have any target_object.xxx=false if the current behavior is current. In other word, we should either:

remove the target_object option, and have the avoidance planner avoid everything
make the car stop in front of the pedestrian in my 2nd scenerio.

I see.
I think we cannot assume that all user always have access to good perception inputs, therefore it make sense to allow the object type to be configurable.
On the other hand, since we also have the run out module in the behavior_velocity_planner that suppose to handle the pedestrian's scenario.

@VRichardJP @zulfaqar-azmi-t4
I think there are limited things we can do in behavior_path_planner(bpp) when we consider its coverage. Also run_out module in behavior_velocity_planner is  not sufficient in this scenario. What it can be done might be an improvement in obstacle_stop_planner. I prepared some videos to explain why I think so:

1) In the first case, there are a static pedestrian and a parked bus behind it. In this scenario ego vehicle avoids the parked bus -not the pedestrian-  but at the end it drives very closely to the pedestrian anyway.
https://user-images.githubusercontent.com/48479081/199532222-822ae50d-093f-4f6c-ad41-c9479b724594.mp4
This is not what we want so as @xmfcx suggested in ASWG meeting yesterday; in bpp when it is deciding for shift points (in avoidance module) it can be checked if there are any objects on the path -which we don't wanna avoid such as pedestrians- existing closer than the target obstacle. And it would work on this case.

2) However if pedestrian appears next to the path after avoidance is done then there is nothing can be done in bpp layer. Because the pedestrian is not on the path. At the end ego vehicle would drive closely to the pedestrian.
https://user-images.githubusercontent.com/48479081/199532909-d130331c-c5b6-4d7f-af4c-ca36eb9e8bbb.mp4

3) We can launch run_out module as @zulfaqar-azmi-t4 suggested. However it wouldn't solve the problem. Ego vehicle would drive closely to the pedestrian anyway.
https://user-images.githubusercontent.com/48479081/199533613-f97f1e4f-c787-4244-b33b-b998d0009859.mp4

As a solution we could increase lateral_margin parameter in obstacle_stop_planner:
https://github.com/autowarefoundation/autoware.universe/blob/d10310ddbbf5aaba20858173cb26e7fdcb30ea49/launch/tier4_planning_launch/config/scenario_planning/lane_driving/motion_planning/obstacle_stop_planner/obstacle_stop_planner.param.yaml#L17
However it would be valid for all the obstacle points and ego vehicle would stop for the cases we don't want it to stop (narrow roads, close vehicles on the opposite/neighbor lane). So what we can do is that in obstacle_stop_planner for the points belong to the selected objects (pedestrians in this case) lateral_margin can be larger. I believe it would solve this problem.
What are your opinions on this?

I want to work on this approach. I will create an issue and PR about it.

@mehmetdogru
Eventually, I think the planner should be able to reassess the situation and invalidate an avoidance path if it does not make sense anymore. For example, if the avoidance path is now blocked half-way, the vehicle should stay on its lane (or go back to it), and wait until the path is clear.
In your second video, if a pedestrian appears on the path (or if lateral_margin is high enough), the vehicle will stop in front of it and wait like this in the middle of the road. It is definitely better than driving 10cm away from the pedestrian, but it is not an ideal situation either.

@VRichardJP
I agree. Maybe avoidance path can be reverted in such cases.
Although, I am afraid just checking around the path will not be enough considering even though path is reverted, ego vehicle sometimes won't have time to go back to it and stay in the middle of the road anyways. Maybe something like run_out module can be implemented in bpp which considers the predicted paths of target objects or in such scenarios bvp can send a message back to bpp so the avoidance path can be reverted on time.

@satoshi-ota
Could you kindly provide your ideas about the issue. I learnt that you are working on avoidance module for further improvements. I would really like to hear your opinion about this as well.

@VRichardJP @mehmetdogru @beyzanurkaya @shulanbushangshu  @zulfaqar-azmi-t4
Thanks for the discussion. Let me check one thing.
You do not want the vehicle to drive near the pedestrian only when the vehicle is in avoidance maneuver, right ? Or, you don't want not only when the vehicle is in avoidance maneuver but also when the vehicle is driving lanes without avoidance.
If it is the former, then we have the following options:

Add a special obstacle stop function to the avoidance function as @mehmetdogru said here For example, if there are obstacle between the avoidance target and the Ego, the Ego stops on the spot.
Implement features to avoid pedestrians

In the latter case, then we have the following options:

Tuning parameters of obstacle_stop_planner or improve obstacle_stop_planner feature as @mehmetdogru said here
Use obstacle_cruise_planner.The behavior of obstacle_cruise_planner is basically the same as the function of obstacle_stop_planner with respect to obstacle stopping, but by default it determines if the Ego should stop based on not pointcloud but object recognition.

In the current architecture, the feature that generates avoidance paths is separated from the feature that stops for obstacles, and I do not want to merge those features, so I think it is better to fix this issue by improving the obstacle stop functions (obstacle_stop_planner, obstacle_cruise_planner, run_out).

@satoshi-ota
I think the vehicle behavior should be consistent over the several scenarios. For example:

if during normal lane driving we must keep a lateral safety distance of 1.0 meter, we must keep the same safety distance of 1.0 meter during avoidance (I think it is what obstacle_stop'planner already does)
if the planner is not allowed to avoid pedestrian, it should not matter what is behind the pedestrian (this ticket issue)
generally, I think avoidance manoeuver should work as a whole: either we can avoid everything and we go, or we can't do he manoeuver and we wait. I think it is not the case yet: autoware always goes as far as it can, even if it means stopping in the middle of the road
the consequence of the previous point is that if a non avoidable appears halfway our manoeuver, we should avoid it to finish our manoeuver. In other words, the avoidable/non-avoidable does only make sense when autoware has to decide whether to avoid or not. Once you are manoeuvering, I think it is best to finish the manoeuver as soon as possible (even if it means avoiding "non-avoidable" objects)
another consequence is that an obstacle should not become a "launch ramp" to avoid another obstacle. For instance, if a vehicle is parked on the side of the road (=can be avoided), and right behind we see another vehicle in the middle of the lane (which should not be avoided), then autoware should avoid none (I am not sure whether autoware does this or not)
it should be resilient to detection noise. Unless detection suddenly improves a lot, the sad truth is that "small" objects (pedestrian, bikes, cycles...) are not recognized by autoware from very far, and late classification is definitely a thing. So it is best if autoware's behavior does not change radically when the obstacle is just a few points, then an "unknown" obstacle, then a "pedestrian", then disappear because it is merged into another "car" obstacle, and so on.

Sorry it's just a bunch of disorganized ideas, but I guess it gives a good idea of the behavior I would expect from autoware in the avoidance situation. I think it shouldn't be too difficult to add the few extra rules above to make the avoidance more predictable/human-like.


Python command for Iris example won't run (Pandas not found), no commit created

datalad run -m "analyze iris data with classification analysis"
--input "input/iris.csv"
--output "prediction_report.csv"
--output "pairwise_relationships.png"
"python3 code/script.py"
[INFO   ] Making sure inputs are available (this may take some time)
get(ok): input/iris.csv (file) [from web...]
[INFO   ] == Command start (output follows) =====
Traceback (most recent call last):
File "code/script.py", line 2, in
import pandas as pd
ModuleNotFoundError: No module named 'pandas'
[INFO   ] == Command exit (modification check follows) =====
[INFO   ] The command had a non-zero exit code. If this is expected, you can save the changes with 'datalad save -d . -r -F .git/COMMIT_EDITMSG'
CommandError: 'python3 code/script.py' failed with exitcode 1 under /home/jovyan/tutorials/notebooks/paper-remodnav/remodnav/myanalysis

Hi @dkp, thanks for logging the issue! I was able to reproduce this on my side too (using the the Explore DataLad - an intro Binder instance, available from this repo: https://github.com/datalad/tutorials.). There are two possible fixes for this:

update the datalad-binder repo (specifically the environment.yml file) to include the required packages (pandas, seaborn, scikit-learn)
update the tutorial notebook itself to install the packages with pip.

I think option 2 is the better option because the packages are specific to this particular tutorial, and installing them in the binder instance would make them (unnecessarily) available for all notebooks using the datalad-binder setup.
If you're interested, you're welcome to create a PR to add these few lines to the tutorial. notebook. But definitely no problem if not :)

We went for option 1: https://github.com/datalad/datalad-binder/commit/65e0d62b78e7e5c988467e1d865f6af3d084dbfc


Add support for JSHint within HTMLDjango files

This PR copies syntax_checkers/html/jshint.vim to syntax_checkers/htmldjango/jshint.vim, and replaces references to html with htmldjango

This is the wrong approach for at least two reasons.  First, because syntastic can handle composite filetypes (see :help syntastic-composite).  Thus if you set the filetype for your file to html.django, you can check it with jshint directly.  And second, because you should never copy checkers like this.  Sorry, but no.


GUI fails to start

Checklist

[X] The problem is not listed in the hardware support matrix as a known limitation
[X] I've included a debug snapshot if the issue is related to hardware configuration

Bug description
The GUI fails to start after some updates. lactd.service appears to run fine.
$ lact

(lact:4810): Gtk-WARNING **: 08:13:18.220: Unknown key gtk-modules in /home/aegis/.config/gtk-4.0/settings.ini
2024-09-23T06:13:18.279445Z  INFO lact_client::connection::unix: connecting to service at "/var/run/lactd.sock"
Gdk-Message: 08:13:18.279: Error 71 (Protocol error) dispatching to Wayland display.

System info
- LACT version: 0.5.6
- GPU model: AMD Navi 31
- Kernel version: 6.10.10-arch1
- Distribution: Arch Linux x64
- DE: KDE Plasma on Wayland

Do other GTK4 applications work? Like gtk4-demo from the gtk4-demos package

Same error, seems to be a larger GTK issue. Thanks for the tip!


Vim tabs are hard to read with the white background

Really love this theme! However I find the tabs hard read with the white background. I've tried with a stripped down vim.init to check it wasn't a conflict with another package.  My setup is iterm2 and neovim with both color schemes installed.
" setup vim plug
call plug#begin('~/.config/nvim/plugged')
  Plug 'vim-airline/vim-airline'
  Plug 'trevordmiller/nova-vim'
call plug#end()

colorscheme nova

Mine looks the same. I have to agree, that it's a bit hard to read on the light grey background. This is a low contrast color scheme, but this seems lower contrast than normal. I'm not sure what options we have here. @trevordmiller Is this something you've noticed? I don't use tabs a lot myself, so I didn't really notice.

@maximmcnair Good catch, that is a bug I haven't noticed because I don't use Vim tabs either. This should be updated to match the other "toggle" styles across Nova:

So the tab bar background should be uiGroups.backgroundShade, with the foreground being uiGroups.gray3 unless active then it should be uiGroups.userCurrentState.
If either of you want to submit a PR, go for it. Otherwise I'll get to this :)
Thanks for using Nova!

Also of note, the Vim airline doesn't have the best contrast; here is what non-airline (native status bar) looks like:

We have discussed updating airline to match in https://github.com/trevordmiller/nova-vim/issues/75, but I left the decision to @alexlafroscia to keep it as is since he built it and I don't use airline; but the more I see it the more I think it should be updated with the backgroundShade setup like the native status bar. @alexlafroscia, would you be ok if I reopen that issue and make the change? I can take care of it since I know you are busy.

Created a PR #82 to match above conversation


Make a new release (2.6)

Nothing major, but a small few fixes were added here and there.
Also need to notify vcpkg and Conan precipice maintainers that the repo address has changed so that they can update it.

Would it be a good time to deal with recent deprecations added around Dear ImGui version 1.88? Try:
  #define IMGUI_DISABLE_OBSOLETE_FUNCTIONS
  #define IMGUI_DISABLE_OBSOLETE_KEYIO

It's always good time to deal with them. PRs are appreciated. :)

I'd help out if it weren't for the fact that I've only just started using ImGui so my experience level is dangerously low :(

Would also love to see a new release. There have been hundreds of changes and improvements to imgui since version 1.80 - the version imgui-sfml uses. They're now at 1.89.3.

@cosmicr FYI, imgui-sfml doesn't depend on a specific version of Dear ImGui. You can use the latest version if you want to.
If you use Conan/vcpkg package, you should ask maintainers to update the dependencies.

@eliasdaler  Yeah I would do that but my own project is using CMake to fetch imgui-sfml, which in turn fetches the 1.80 version of imgui:
https://github.com/SFML/imgui-sfml/blob/f0d8f72f073b367e9506b8794158cc91f015252e/CMakeLists.txt#L60
I guess I could make a pr for changing this, or there might be another way to get the latest imgui version first, but I'm terrible at writing cmake files lol.
I'm happy to wait for a new version to reference the latest imgui

This only specifies the minimal version of Dear ImGui which can be used.
It doesn't fetch anything - you still need to tell ImGui-SFML where to find Dear ImGui and it will happily use whatever version you provide as long as it's >=1.80.

Doh you are right, I had forgotten I included a FetchContent_Declare in my cmake to download imgui - I'm already using v1.89 lol. For some reason I thought the imgui-sfml cmake file was magically downloading it. Sorry for wasting your time.

No problem :)

Now is a great time for a 2.6 release now that SFML 2.6 is out.

https://github.com/SFML/imgui-sfml/releases/tag/v2.6


Release v1.0.8

Part of release process.

❗Trojan found on Win 10 Defender

@monikasmolarek that seems to be your local "state" I think
https://www.virustotal.com/gui/url-analysis/u-dcb7d19ed928f45ad231880dd526c9f91489876d8b0471f28b7553c718f7684d-1690411154


Pass the version of the client to the API.

When calling the rest API, send a new header that will state the client version. Parameter name proposition : X-algoliaclient-version

[x] in V3
[ ] in V2

Introducing a new X-Algolia-ClientVersion (or X-Algolia-Version ?) looks good! cc @Nagriar

This will help us get some stats about client version usage. It would be good to have it set in both V3 and release a new V2 (V2 branch) also.
So we can hopfully see a decrease in V2 usage.

This was solved in V3, we send a x-user-agent on the query string or headers (node)

done and released in 2.9.7


Version 21.38.6

What
Releases https://github.com/alphagov/govuk_publishing_components/pull/1438

Thanks! I've made that change.


Relax containers, deepseq bounds

This is required for GHC-9.8.1 compatibility. See: https://github.com/commercialhaskell/stackage/issues/7217.
I've checked that it builds and that the test suite runs successfully.

Thank you!
Locally confirmed on my side, too, that the test passes and the benchmark runs for GHC-9.8.

New revision is uploaded to Hackage

Thanks for the quick response!


Cannot rename binary in Table View

9.1.2 / windows 10
If the projects window is in in Table View, the rename option on a binary does not work, works as intended in Tree View

fixed by https://github.com/NationalSecurityAgency/ghidra/commit/49ac34e31e5f56523484da946413b7221bf5ca45 looks like, thanks @dragonmacher


How can I use this on a Raspberry Pi ?

I would want do use it on a RPI4 using the GrovePi Hat

https://github.com/CRImier/python-MLX90614，  It's already been done, and the code is relatively simple.

Hello,
I'm going to close this issue, feel free to re-open it if you have any other questions.


Add configuration support for the color blocks

I found this a useful configuration to have: it was simple, and it allows for multiple shells/users/programs to run the same fet.sh and avoid issues with Unicode block rendering.
All it does is allow for a colorblock variable to be set to change the characters in the color line. It does not break any existing functionality.

Thanks!

(Also I changed it to colourblocks, sorry not sorry.  🇬🇧)


[GitHub Release] Could you create a new release from latest develop branch.

Hi, Thank you so much for your development of PR-Agent.
We've noticed significant improvements in output recently and would like to leverage these advancements in our project.
Currently, our update process involves specifying branches, which may lead to updates with unstable versions. Stability is paramount for our team, and we prefer updating our dependencies by specifying tags for this reason.
Given this context, we have two requests:

Could you please release a new stable version reflecting recent improvements?
If possible, introducing a regular release schedule would greatly assist projects like ours in planning and integration.

Thank you all.

@psbss
regular PR-Agent will have "Stable" releases once a month. We plan to do one next week
you can choose whether to use the "Stable" version, or a nightly updated "latest" version.
if you want "stability" + "nightly updated" (along with other benefits), I recommend using PR-Agent PRO. We guarantee there both.
https://github.com/Codium-ai/pr-agent?tab=readme-ov-file#pr-agent-pro-

Thank you for your reply.
I will consider to use PR-Agent Pro👍


Stuck on Convert to Audio 0/1

As the tile suggest, on the latest, I am getting this error, it just hangs on this.
Is it working for others?

It's working for me. :)
If aws-tts hangs during the "Convert to Audio" step, it's probably a network issue. Please make sure you can connect to AWS outside of aws-tts -- try going to https://polly.us-east-1.amazonaws.com/v1/speech (or whatever AWS region you're using) or using the AWS CLI to run a command.
If there is an error, then aws-tts should eventually quit with an error (it may take 30 seconds or more with a networking error). Please provide additional info: the exact command you are running, and the output with any eventual error message you get.

That would make sense, when I trued npm to reinstall, I got a host not reachable.
I have no idea what caused it. But, I rebooted today and seems to work right now.
Thanks for the advice!
I'm not a coder, so this has been super fun to play with!


issues/48: Fix superfluous response.WriteHeader call

When http.ResponseWriter.WriteHeader() is called more than once, it always produces the error;
http: superfluous response.WriteHeader call from github.com/komuw/ong/middleware.(*logRW).WriteHeader (log.go:121)
And the stack trace always points to the ong log middleware. But that does not mean that ong has any issues.
That error is always produced irrespective of if ong is used. It's how net/http works[2]
Also note that; if http.ResponseWriter.WriteHeader is not called explicitly, the first call to Write
will trigger[3] an implicit WriteHeader(http.StatusOK).
So this PR does not fix the issue(since it is an actual feature of net/http), rather it clarifies that understanding.

Fixes: https://github.com/komuw/ong/issues/48
https://github.com/komuw/ong/issues/48#issuecomment-1260654535
https://github.com/golang/go/blob/go1.20.5/src/net/http/server.go#L141-L159

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.01 :tada:

Comparison is base (ff0b7f8) 73.37% compared to head (b63d4ac) 73.39%.

:exclamation: Current head b63d4ac differs from pull request most recent head 5aae181. Consider uploading reports for the commit 5aae181 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #302      +/-   ##
==========================================
+ Coverage   73.37%   73.39%   +0.01%
==========================================
  Files          42       42
  Lines        4782     4792      +10
==========================================
+ Hits         3509     3517       +8
- Misses       1021     1022       +1
- Partials      252      253       +1

Impacted Files
Coverage Δ

middleware/log.go
68.67% <100.00%> (+4.29%)
:arrow_up:

... and 1 file with indirect coverage changes

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


Rewrite Efficient-ViT-SAM TensorRT inference with torch2trt to make the code a lot simpler

Rewrite Efficient-ViT-SAM TensorRT inference with torch2trt to make the code a lot simpler (without the need for pycuda).
The speed is faster too.

That makes the code simpler. Thanks for your contribution!


FileSystemProvider: certain workspace folders break the integrated terminal

VSCode Version: Version 1.18.0-insider (1.18.0-insider) 65c08338e4bece35fb53f5a1cdf56d30b7706157, c1be82537d9fda852a258851f48ea78b7fc8a7a3
OS Version: mac 10.12.6

Steps to Reproduce:

Create a FileSystemProvider
Have a certain provided folder in the workspace
Observe that createTerminal({name: 'foo', shellPath: 'bash', shellArgs: ['-l', '-i']}) fails with this error message:

The terminal process command `bash -l -i` failed to launch (exit code: 1)

Try to open an integrated terminal (ctrl + ~) and observe:

The terminal process command `/bin/bash -l` failed to launch (exit code: 1)

Pretty much every call to createTerminal (i.e. trying different programs to run) will fail if certain provided folders are loaded in the workspace. I've not yet found a pattern to which folders cause this issue, but it's consistent for the affected folders. It does not matter which order the folder appears in the workspace (I've unsuccessfully tried setting a local folder as the first in hopes that vscode was trying to pick up the cwd or something from it).

I can sometimes see this very briefly appear in the integrated terminal:
chdir(2) failed.: No such file or directory

@jrieken this might also need a "remote" label

@Tyriar The terminal might miss a check that the selected workspace folder is a folder on disk, file-uri

@jrieken tracked in https://github.com/Microsoft/vscode/issues/17450

closing as duplicate of #17450 then


Default path redirect?

I can't figure out how to have the typical '/' path redirect to something. I don't particularly need a landing page on my current app, so I want to redirect to a particular route if they have access. Here is my route config:
export const routes: Routes = [
    {
        path: '/',
        redirectTo: '/user/add',
    },
    {
        path: '/user/add',
        guards: [ AuthGuardLevel1 ],
        component: AdduserComponent
    },
    {
        path: '/user/update',
        guards: [ AuthGuardLevel2 ],
        component: UpdateuserComponent
    },
    {
        path: '/unauthorized',
        component: UnauthorizedComponent
    },
    {
        path: '/**',
        component: NotfoundComponent
    },
]

This is what I get in the console when navigating to '/':
zone.js:260 Uncaught TypeError: pathToRegexp.compile is not a function
I'm sure I'm missing something simple, but I haven't figured it out yet.

Sounds like you might be using the angular-cli. If that's the case, there's a dependency conflict that you can resolve by installing path-to-regexp manually:
npm i path-to-regexp --save

That did the trick, thanks!


[feat] 2.0: decouple Rust build from iOS Xcode Script phase

Describe the problem
like many issue e.g. #6573
folks are facing many Xcode related problems because by default Xcode is using /bin/sh which is far from commonly used shell.
Meanwhile, it is hard to find out a way to build the static lib first then use Xcode to build the host app only.
> tauri "ios" "build" "-h"

Build your app in release mode for iOS and generate IPAs

Usage: pnpm run tauri ios build [OPTIONS]

Options:
  -d, --debug                        Builds with the debug flag
  -v, --verbose...                   Enables verbose logging
  -t, --target [<TARGETS>...]        Which targets to build [default: aarch64] [possible values: aarch64, aarch64-sim, x86_64]
  -f, --features [<FEATURES>...]     List of cargo features to activate
  -c, --config <CONFIG>              JSON string or path to JSON file to merge with tauri.conf.json
      --build-number <BUILD_NUMBER>  Build number to append to the app version
  -o, --open                         Open Xcode
      --ci                           Skip prompting for values [env: CI=]
  -h, --help                         Print help (see more with '--help')
  -V, --version                      Print version

Describe the solution you'd like
Allow two modes:

Integrated build with zero configuration: current state

Separate Rust static lib build (.a) and the host app build

Alternatives considered
No response
Additional context
No response

I'll give this a go, it would help my current project at work tremendously

@mrguiman thanks!

best course of action because xcode will provide a bunch of information required to compile the library

I don't think there're a lot information required. in the worse case, we can always assume some env vars for the "standalone" mode of compilation.
This could address many pain points. For example, the current blocker for me to upload the release build of .ipa to the App Store is that it is not properly signed

@imWildCat for this you can use the --open option (cargo tauri ios--open). it does require manual steps but it will allow you to go through with uploading to the app store, we just released that way this week

cargo tauri ios build --open

🫡 thank you so much, @mrguiman !

interesting it does not seem to work in my case

oh never mind!
the Xcode project previously included the .a from debug builds...

I'll close this issue, as mentioned before decoupling causes all sorts of issues and would degrade the DX. Using the --open flag is the recommended way to use Xcode and Android Studio.
Let us know if you face any other issue :)

make sense! thank you!


fix: Correct route for game/reject-stalemate policy config

Please check the following

[x] Do the tests still pass? (see Run the Tests)
[x] Is the code formatted properly? (see Linting (Formatting))
For New Features:

[ ] Have tests been added to cover any new features or fixes?
[ ] Has the documentation been updated accordingly?

Please describe additional details for testing this change
Made changes to policies config to fix correct route for game/reject-stalemate to game/stalemate-reject

Fixes cuttle-cards/cuttle#80


[Feature Request]: opacity option for drawText() method

I want to draw text with opacity 50% but i can see i cannot pass alpha value in rgb()
function.
export const rgb = (red: number, green: number, blue: number): RGB => {
  assertRange(red, 'red', 0, 1);
  assertRange(green, 'green', 0, 1);
  assertRange(blue, 'blue', 0, 1);
  return { type: ColorTypes.RGB, red, green, blue };
};

 drawText(text: string, options: PDFPageDrawTextOptions = {}): void {
    assertIs(text, 'text', ['string']);
    assertOrUndefined(options.color, 'options.color', [[Object, 'Color']]);
    assertOrUndefined(options.font, 'options.font', [[PDFFont, 'PDFFont']]);
    assertOrUndefined(options.size, 'options.size', ['number']);
    assertOrUndefined(options.rotate, 'options.rotate', [[Object, 'Rotation']]);
    assertOrUndefined(options.xSkew, 'options.xSkew', [[Object, 'Rotation']]);
    assertOrUndefined(options.ySkew, 'options.ySkew', [[Object, 'Rotation']]);
    assertOrUndefined(options.x, 'options.x', ['number']);
    assertOrUndefined(options.y, 'options.y', ['number']);
    assertOrUndefined(options.lineHeight, 'options.lineHeight', ['number']);
    assertOrUndefined(options.maxWidth, 'options.maxWidth', ['number']);
    assertOrUndefined(options.wordBreaks, 'options.wordBreaks', [Array]);

    const [originalFont] = this.getFont();
    if (options.font) this.setFont(options.font);
    const [font, fontKey] = this.getFont();

    const fontSize = options.size || this.fontSize;

    const wordBreaks = options.wordBreaks || this.doc.defaultWordBreaks;
    const textWidth = (t: string) => font.widthOfTextAtSize(t, fontSize);
    const lines =
      options.maxWidth === undefined
        ? cleanText(text).split(/[\r\n\f]/)
        : breakTextIntoLines(text, wordBreaks, options.maxWidth, textWidth);

    const encodedLines = new Array(lines.length) as PDFHexString[];
    for (let idx = 0, len = lines.length; idx < len; idx++) {
      encodedLines[idx] = font.encodeText(lines[idx]);
    }

I cannot see how i can set opacity value.
Does this library support?
If not, it would be really nice if you consider it.

Hello @akaanish! pdf-lib does not currently provide an API for changing text/shape/image opacity. However, I agree that this would be a useful feature to offer.
If anybody would like to work on this, I'd be happy to merge a PR implementing this feature. Otherwise I'll look into it when I get some more pressing issues taken care of.

I desperately need opacity for svgpaths, how could I help implementing it? I don't know anything about PDFs, I'm more of a WebGL guy, where should I start?

Hello @soadzoor!
I'd suggest taking a look at the PDF spec and how other PDF libraries implement transparency. Here's a link to the transparency implementation in pdfkit: https://github.com/foliojs/pdfkit/blob/master/lib/mixins/color.js#L109-L144.
Some sections of the spec I'd recommend taking a look at:

Table 52 in section 8.4.1 defines the alpha constant
Table A.1 in Annex A defines the gs operator
Section <IP_ADDRESS> explains the CA and ca graphics state parameters that define opacity (you can see them used in the pdfkit implementation I linked to above)

Hello @Hopding !
Thank you for all these information. I've started studying this thing, although it feels like drinking from the firehose. It's a huge ocean I've dived into. I'm pretty sure I'd need a deeper understanding of the spec to be able to do this. This is how far I got so far:
I've added these to your operations.ts:
`export const setFillingOpacity = (opacity: number | PDFNumber) =>
PDFOperator.of(Ops.SetGraphicsStateParams, [asPDFNumber(opacity)]);
export const setStrokingOpacity = (opacity: number | PDFNumber) =>
PDFOperator.of(Ops.SetGraphicsStateParams, [asPDFNumber(opacity)]);`
Although, as the spec says:

While some parameters in the graphics state may be set with individual operators, as shown in Table 57, others may not.  The latter may only be set with the  generic graphics state operators(PDF  1.2).  The operand  supplied to this operator shall be the name of a graphics state parameter dictionary whose contents specify the values of one or more graphics state parameters. This name shall be looked up in the ExtGState subdictionary of the current resource dictionary.

And I believe, this is one that doesn't have its individual operator. Unfortunately, I can't see an example in your project where you use ExtGState, or even dictionaries, so this is where I got stuck.
Could you please help?

@soadzoor I can certainly relate to feeling overwhelmed by PDFs and the spec. There's a ton of information in there. It took me a long time to digest it all, and I'm still learning little bits and pieces here and there. But on the bright side, you don't need to know everything to get started. And, generally speaking, pdf-lib provides most of the tricky primitives to get you moving quickly.
You'll need access to the PDFContext of your document in order to create a dictionary and get a reference to it. Here's a basic example:
const pdfDoc = await PDFDocument.create();
const myDict = pdfDoc.context.obj({
  Type: 'Foo',
  Qux: 21,
  Baz: [{ Bar: 45 }],
});
const myDictRef = pdfDoc.context.register(myDict);

You may also find the FileEmbedder to be a useful reference. It creates and embeds some dictionaries and streams. There are a number of other examples strewn around the codebase as well.
Here's a rough example to show how you might create a dictionary and add it to the ExtGState of a particular page. (Note that it doesn't necessarily handle all edge cases and I haven't actually tested it).
const pdfDoc = await PDFDocument.create();
const page = pdfDoc.addPage();
const { Resources } = page.node.normalizedEntries();

const extGState = pdfDoc.context.obj({
  GS1: { Type: 'ExtGState', ca: 0.7, CA: 0.5 }
});

// Note: we shouldn't override this if it already exists!
Resources.set(PDFName.of('ExtGState'), extGState);

page.pushOperators(
  pushGraphicsState(),
  // Push an operator that sets the graphics state to `GS1`
);
page.drawSvg(...);
page.pushOperators(popGraphicsState());

You can use the PDFPage.pushOperators(...) method to push your graphics state operators to the page before drawing your SVG to test everything. Of course, ideally the API would expose an opacity option that takes care of all this behind the scenes for you.

Thank you @Hopding ! I'll try to play around with this on Monday, and will let you know how it goes! Cheers!

Hey @Hopding ,
Thank you for the explanations and the examples, you're super helpful! Something is happening with the opacity, but it's not what I'd expect, so I need your help (again, sorry.. :( )
Here's what I'd expect:

And here's the actual result:

So, it seems, the opacity is changed, but it only affects the "original PDF's" parts, which I load as an arraybuffer. Which is strange, because I change the graphic state only after it's already loaded (I guess..?). Do you have any idea what's happening, and why?
My code (rougly) looks like this:
const arrayBuffer = await fetch(pdfFileURL).then((res) => res.arrayBuffer());
const pdfDoc = await PDFDocument.load(arrayBuffer);

const pages = pdfDoc.getPages();
const page = pages[0];

this.addIcons(page); // Add pacman, and computer icons (embedding PNGs). No issues here, so I won't bother you with the details

//
// Add polygons
//
const extGState = page.doc.context.obj({
	GS1: {
		Type: 'ExtGState',
		ca: 0.1, // filling
		CA: 0.1 // stroking
	}
});

page.node.normalizedEntries().Resources.set(PDFName.of('ExtGState'), extGState);
page.pushOperators(pushGraphicsState());

for (const polygon of polygons)
{
	const colorObject = polygon.color;
	page.drawSvgPath(polygon.svgPath, {
		x: polygon.x,
		y: polygon.y,
		borderColor: rgb(colorObject.r, colorObject.g, colorObject.b),
		color: rgb(colorObject.r, colorObject.g, colorObject.b),
		borderWidth: 1
	});
}

page.pushOperators(popGraphicsState());

@akaanish There are three steps required to change the opacity:

Create an external graphics state dictionary (with the desired values)
Add that dictionary to the page
Apply the graphics state dictionary via an operator

You appear to be doing the first two steps, but not the third. In my example I left a comment where you need to push the operator, though I suppose it wasn't clear enough. It should be placed directly after pushGraphicsState():
page.pushOperators(
  pushGraphicsState(),
  // Replace this comment with an operator that sets the graphics state to `GS1`
);
page.drawSvg(...);
page.pushOperators(popGraphicsState());

Something like this should work (I haven't tested it though):
const setGraphicsState = (state: string | PDFName) =>
  PDFOperator.of(Ops.SetGraphicsStateParams, [asPDFName(state)]);

...

page.pushOperators(
  pushGraphicsState(),
  setGraphicsState('GS1')
);

@Hopding Oh, I missed that, you're right! Now it works, almost as expected! Thank you very much!
Although the original PDF's lines are still affected with the modified CA value, which makes me a little bit anxious. Maybe if I push another graphic state initally, that should solve it..? I'm not sure

@soadzoor That's probably because the original PDF already has a graphics state called GS1 and you are overwriting it. Recall this snippet of my example:
const extGState = pdfDoc.context.obj({
  GS1: { Type: 'ExtGState', ca: 0.7, CA: 0.5 }
});

// Note: we shouldn't override this if it already exists!
Resources.set(PDFName.of('ExtGState'), extGState);

As I mentioned, my example does not handle all edge cases. There are two such scenarios that can occur here that you'll need to handle:

The page's Resources dict may already have an ExtGState defined. If it does, then you should add your graphics state dictionary ({ Type: 'ExtGState', ca: 0.7, CA: 0.5 }) onto it, rather than overwriting it with a new one.
It isn't sufficient to just hard code the key GS1 for your graphics state dictionary. This is highly likely to conflict with the name of an existing graphics state dictionary. Instead, you need to generate a random name that has a much higher probability of uniqueness. Generating a random suffix of 10 digits should do the trick. This is what we do for embedded images and fonts:
https://github.com/Hopding/pdf-lib/blob/9b6fb96deaaeb4381c573e0e5f8e9d56629ced4a/src/api/PDFPage.ts#L959-L960

@Hopding I admire you're patience and persistence towards me! You're fantastic ❤

@soadzoor I'm happy to help! If you're able to get it working, I hope you'll consider submitting a PR to add opacity and borderOpacity options to pdf-lib's API so this is easier for everybody to do in the future.

@Hopding Sure, I plan to do that!

Version 1.8.0 is now published. It contains opacity and borderOpacity options for all page drawing methods (thanks @soadzoor!). The full release notes are available here.
You can install this new version with npm:
npm install<EMAIL_ADDRESS>
It's also available on unpkg:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
As well as jsDelivr:

<EMAIL_ADDRESS><EMAIL_ADDRESS>


going commercial?

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

I see the development is going on at full scale at Travis but no updates here.
Was this repo abandoned in favour of a commercial ng2-admin version?

Hi @homofortis, not really sure what you mean :) The development branch is dedicated to have raw and untested changes (as we are trying to keep master branch as stable as possible). At the moment of this message, the development branch is one commit behind master.
So no worries at all, this project is free forever and built for the community.

Hey @nnixaa, It's good to hear you'll keep the project free. You are my Angular 2 heroes :) and your projects helps me in a great way to learn the framework as well as the coding style.
Keep it up and running!


Error: Cannot find module 'eslint' which is already installed

Describe the bug
Going into the Output > Prettier ESLint tab, I get Error: Cannot find module 'eslint' every time I save the file.
Prettier, ESLint and prettier-eslint are all installed globally on my machine, and the problem persists even when I install them as a dev dependency in my project.
Versions:

VS Code Prettier ESLint extension 5.1.0
VSCodium: 1.84.2
Node: 20.9.0
pnpm: 8.10.5
prettier: 3.1.0
eslint: 8.54.0

System Specifications:

OS: Windows 10 22H2
Processor: Intel Core i5 4-core 3.5GHz
RAM Size: 16 GB

I couldn't find any information on what could cause this issue and how to fix it. If it's out there then I'm terribly sorry.

Prettier 3.0 switched entirely to ESModules. Try downgrading prettier to version 2.8.8
pnpm remove prettier && pnpm add<EMAIL_ADDRESS>

The same here.
Versions:
VS Code Prettier ESLint extension 5.1.0
VSCodium: 1.85.0 (Universal)
Node: 18.18.2
npm: 9.8.1
prettier: 2.8.8
eslint: 8.15.0
System:
macOS 13.6.1 (22G313)
Chip Apple M2
Require stack:
- /Users/[MY_USER]/.vscode/extensions/rvest.vs-code-prettier-eslint-5.1.0/dist/extension.js
- /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js
- /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-amd.js
- /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-fork.js

Look at this, it might help you @wysok


Drag bug in dashbord v1

1, open https://almsaeedstudio.com/themes/AdminLTE/index.html in Chrome.
2, scroll it a little.
3, drag "Sales" or "Chat" or any other panel.
the position of these panels are wrong.

Due to some neglect in my part, many issues weren't addressed for some time. Some of these issues are no longer relevant since a solution might have been found. Therefore, we decided to close all issues that are over a month old. However, if the issue still persists and you'd like help, then by all means repost your issue and we will consider it again. In the mean time, we will close this post.
Thanks for your understanding and we apologize for any inconvenience <3.


feat(cicd): added miranum-forms to release pipeline and refactoring

Issue
Description

Added Miranum-Forms to release pipeline

Checklist

Code is easy to understand
No obvious errors or bugs
CI/CD Pipelines did run successfully
Tests were implemented
Documentation was created

Codecov Report
Patch and project coverage have no change.

Comparison is base (2fd5bb0) 63.27% compared to head (186b6fa) 63.27%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #96   +/-   ##
=======================================
  Coverage   63.27%   63.27%
=======================================
  Files          14       14
  Lines         305      305
  Branches       40       40
=======================================
  Hits          193      193
  Misses         72       72
  Partials       40       40

Flag
Coverage Δ

unittests
63.27% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Differnce between no-avg and avg in Step 5 of QSOanalysis

I feel that no-avg and avg are analyzed differently. I feel that some functions are omitted in no-avg. Or, this is correct???

This will not be fixed.


monaco-editor version not latest

when i install react-monaco-editor,
monaco-editor version is
  "monaco-editor": "^0.10.0",

in /node_modules/react-monaco-editor/package.json.
why??

Because pre 1.0 versions may break compatibility with minor versions as well. We have to test very version. Can you send a pull request to update to the latest version?

Actually, https://github.com/superRaytin/react-monaco-editor/pull/111/files will fix this. I just need to resolve one issue with webpack.

Fixed


feature(webpack4) Migrate project to webpack4. Prepare for React 16

Migrate to webpack 4
Deprecate redundant plugins/loaders
ready to migrate to react ^16..

Possibly fixes #1924
Unblocks #1967

@jeremenichelli @montogeek guys can you review this one? LGTM so far

This is great, now I don't know if we should merge it since @skipjack has been working on a infrastructure change in the rebuild branch.
@EugeneHlushko can you connect with him about this? I want to make sure that merging this doesn't affect the improvements Greg has done or if you can bring some of this changes to that branch.

I have been working on rebuild branch, these PR changes won't affect it, We still need to upgrade to webpack 4, specially webpack website :D. We could merge later or even better make these upgrade against rebuild branch, It is possible you will find some blockers with 2 plugins that are new and may not been migrated to webpack 4	.

So I don't think any of these changes will be a huge problem for the rebuild branch but they will create some conflicts to resolve. Here's some notes on the rebuild branch:

It's already on React/ReactDOM 16
We haven't done any preact / inferno replacement as the bundles are already ~75kb gzipped
Antwar and it's utilities are no longer used on rebuild, it's pure webpack
We may be able to leverage the RedirectWebpackPlugin
For a full list of notes and TODOs, see the DISCUSSION.md file on that branch
We discussed waiting to port rebuild to webpack v4 until after the remaining TODOs are finished. Few of the remaining items relate to webpack and the build process and trying to do the port now would just add more complexity. With more control over configs and the site in general, it'll be much easier for us to do targeted updates of dependencies faster and in isolation.

I would say if you all see improvements here and get the build to pass, then feel free to merge. After this though, if the plan is to finish and merge rebuild, let's not make any more conflicting changes and instead just focus on finishing rebuild. If you see something in the DISCUSSION.md file you'd like to tackle, please ping me to discuss so we can agree on plan and don't overlap work. The ones @montogeek and I are working on are already marked at the bottom of the list.

This is a shame that there was a branch with changes in this direction, i did look the issues section before starting the work :( Would be a shame to drop it for me:

as its ready to go
removes preact
seems to not have too much conflict on rebuild (wish i knew it existed)

But yes please decide @montogeek @skipjack

As a side note to think about, i really would like to see more incremental changes vs big branches. Especially considering such good CI and CD integrations, it would make it easier and more transparent not only for team members but also for the community

I agree with you on your last point @EugeneHlushko, but to be fair the site had no maintainers at all when Greg started its work on rebuild branch and I'm not expecting to have a refactor every year. So yeah, incremental work for the win.

@jeremenichelli If you mean continuous-integration/travis-ci/pr it unfortunately fails due to api limit exceeded error :(
[Error: {"message":"API rate limit exceeded for <IP_ADDRESS>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://developer.github.com/v3/#rate-limiting"}]

@EugeneHlushko This branch have latest master changes?

We are hitting this Travis Security measure: https://docs.travis-ci.com/user/pull-requests#Pull-Requests-and-Security-Restrictions.
Maybe we could use cache artifacts, need investigation

@EugeneHlushko You are a member, Move your branch to this repo :)

This is a shame that there was a branch with changes in this direction, i did look the issues section before starting the work

I thought there was a mention of it in #1525, I'll double check and add one now if there's not. Sorry about that.

Would be a shame to drop it for me...

I understand, I wasn't saying it should be dropped.

As a side note to think about, i really would like to see more incremental changes vs big branches. Especially considering such good CI and CD integrations, it would make it easier and more transparent not only for team members but also for the community

Totally agree. I started the rebuild branch as more of an experiment but I (mistakenly) let it get bigger than it should have. It does build the site extremely quick however and makes tackling a lot of our dev-related issues much easier since it's pure webpack (giving us more direct control). Recently, I made a short list of the absolute minimum we need to do to complete it and, with other folks like @montogeek helping, I think we'll be able to get it done soon. Finishing #1582 would also be good so we can better test the site for link and missing page issues.
I discussed this with @montogeek and @jeremenichelli and it seems like they are interested in pushing it forward since it's fairly close and offers a lot of what we want. We may still port to gatsby or another PWA/SS generator that requires less local config down the road but that port should be much easier after this one. Certain aspects of Antwar's API, e.g. the Interactive component (as well as our use of preact, led to non-standard React code that we can move away from on the rebuild branch (and hopefully stay away from in any other generator we choose).
On a side note, @EugeneHlushko seeing as you've submitted a lot in the last few months, I'd be happy to add you as a contributor to the project. We can also ping @TheLarkInn to add you to the slack channel.

it unfortunately fails due to api limit exceeded error

Yeah I thought @montogeek had fixed that in #1963 but it sounds like it may be another issue. I think faster builds will also help us run up avoid hitting Travis limits.

Nice! no more forks here for me in that case @montogeek 👍
Thank you @skipjack appreciate everything said above! Will join slack when Sean invites

CC @montogeek @jeremenichelli i've just rebased it and resolved conflicts

@montogeek there is another conflict now, does it worth resolving?

@EugeneHlushko Yes

@montogeek i can resolve too np 👍  just wanted to check if we are merging this soon because last one was resolved yesterday :)

@montogeek its good again

Thank you @EugeneHlushko !


Add support for aarch64-apple-darwin

Currently fails building rpmalloc.c on inline assembly

https://github.com/mjansson/rpmalloc/pull/219


Conform to OSCAR conventions

Change function naming to conform to OSCAR style guide

Codecov Report
Base: 95.48% // Head: 90.62% // Decreases project coverage by -4.87% :warning:

Coverage data is based on head (198ce33) compared to base (bc8deb6).
Patch coverage: 80.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
- Coverage   95.48%   90.62%   -4.87%
==========================================
  Files           8        8
  Lines         288      288
==========================================
- Hits          275      261      -14
- Misses         13       27      +14

Impacted Files
Coverage Δ

src/TateModels/attributes.jl
100.00% <ø> (ø)

src/TateModels/properties.jl
100.00% <ø> (ø)

src/WeierstrassModels/attributes.jl
100.00% <ø> (ø)

src/WeierstrassModels/properties.jl
100.00% <ø> (ø)

src/TateModels/constructors.jl
82.22% <75.00%> (-15.56%)
:arrow_down:

src/WeierstrassModels/constructors.jl
80.95% <75.00%> (-16.67%)
:arrow_down:

src/auxiliary.jl
91.33% <100.00%> (ø)

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

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


Update Octicons

Octicons v8.5.0

Coverage remained the same at 82.007% when pulling 9e12be53ea3e828e361d8b8c9f4bfa8252cb058c on update-octicons into 4f7cabdc627e740db630063eea7ec0557bd163c4 on master.


net: coap: migrate to standard buffers

In order to make the CoAP library more useful in a generic way, this patch series remove all references to net_buf and net_pkt and instead allow usage of standard char-based buffers which will hold generated packet data or be passed for parsing.
Highlights:

Works with any networking backend in that it's merely a parsing / packet building library
Supports standard buffers needed for sockets
Doesn't make a copy of the existing library
Drops about 800 lines of code in Zephyr

NOTE: This does not include the changes for LwM2M.

@rveerama1 I know you are also working on this and I really hate that we are duplicating, but this was a blocker for the work on LwM2M so I went forward a bit.
I'm very partial to this approach for many reasons, but I think if you look at the tests/net/lib/coap/src/main.c changes it really highlights the "why" I did it this way.
Please consider, thanks.

Also, this isn't really WIP code.  It has been actually tested a bit.  The tests/net/lib/coap passes, and the coap_client / coap_server are acting normally as far as I can tell.   I don't know that I have the right setup to test rpl_* and leds_demo samples, but they compile.
I'm sure sanity will find some nice issues for me tho.

@pfalcon the "flat buffer handling" change is purely a design choice and could be changed if you feel that it doesn't add value.   The code itself can also be relocated into an actual .c file somewhere else behind a Kconfig which can be selected by CoAP and LwM2M.

Codecov Report

Merging #10110 into master will increase coverage by 0.03%.
The diff coverage is 56.18%.

@@            Coverage Diff             @@
##           master   #10110      +/-   ##
==========================================
+ Coverage   52.48%   52.51%   +0.03%
==========================================
  Files         213      214       +1
  Lines       26135    26158      +23
  Branches     5633     5629       -4
==========================================
+ Hits        13718    13738      +20
- Misses      10160    10169       +9
+ Partials     2257     2251       -6

Impacted Files
Coverage Δ

include/net/coap.h
100% <ø> (ø)
:arrow_up:

subsys/net/lib/coap/coap_link_format.c
16% <0%> (+0.25%)
:arrow_up:

subsys/net/lib/coap/coap.c
60.86% <63.43%> (+0.2%)
:arrow_up:

include/flat_buffer_util.h
75% <75%> (ø)

subsys/net/buf.c
57.82% <0%> (-0.28%)
:arrow_down:

Continue to review full report at Codecov.

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

@rveerama1 I know you are also working on this and I really hate that we are duplicating, but this was a blocker for the work on LwM2M so I went forward a bit.
I'm very partial to this approach for many reasons, but I think if you look at the tests/net/lib/coap/src/main.c changes it really highlights the "why" I did it this way.
Please consider, thanks.

@mike-scott I just created my WIP PR https://github.com/zephyrproject-rtos/zephyr/pull/10121. Your first version was completely different. This version looks similar to my changes except "flat_buf_util". I am not against about that, but these helpers will become soon de-facto standard for socket based protocols and sample applications.
There is a reason for creating separate folder for CoAP changes. We can deprecate current CoAP over net_pkt in this release and make sure every user modified according to updated CoAP library and then we can safely remove net_pkt based after release. Same thing happened when ZOAP converted to CoAP (+support for multi-fragments changes).
I am also adding extra functionality to coap_client to verify coap_server functionality. Current coap_client is very simple. That's why I am taking some time.


Laravel 11.x Compatibility

This is an automated pull request from Shift to update your package code and dependencies to be compatible with Laravel 11.x.
Before merging, you need to:

Checkout the l11-compatibility branch
Review all comments for additional changes
Thoroughly test your package

If you do find an issue, please report it by commenting on this PR to help improve future automation.

:alembic: Using this package? If you would like to help test these changes or believe them to be compatible, you may update your project to reference this branch.
To do so, temporarily add Shift's fork to the repositories property of your composer.json:
{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/laravel-shift/blade-fontawesome.git"
        }
    ]
}

Then update your dependency constraint to reference this branch:
{
    "require": {
        "owenvoke/blade-fontawesome": "dev-l11-compatibility",
    }
}

Finally, run: composer update


How to change color for a effect by using the color wheel?

Hi toblum,
first of all I want to say thank you for the great project.
I would like to change the color on a effect by using the color wheel. The color change by clicking the wheel will remove the effect and only change the color. I tried to edit the .js file but without a result.

Choose the color first then the effect.

Hi @xeetdp,
yes, this is the way the UI works at the moment.
@cjs1502 : Good idea!
Maybe you want to try out the new "next-gen" UI: https://github.com/toblum/McLightingUI
Just upload the file as index2.htm and call it.
Regards
Tobias

@cjs1502 Thanks for the quick answer. But I want more dynamic. When I want change the effect from green to red the effect will disappear so I have to go back and click again.
@toblum Also thanks for the response. The new UI looks exactly what I was searching for, but I use more then one stripe at the moment. What I did in the old version is to build a submenu and send ws command to differend IPs by using more then one JS files.
For the index.html I use more then one implementation.
Regards
Max

Hi!
The new one has an experimental feature that allows you to enter multiple IPs in the settings to control more than one strip.
Tobias


[Feature] Unified connector and udf management

Search before asking

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

Description
It is not reasonable to add maven and jars to sql tasks. It is recommended to manage the connector and udf in a unified manner to avoid relying on jars in tasks through maven, which causes low reuse.
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

+1 Very good to note


langchain_ollama.embeddings.OllamaEmbeddings throws "invalid input type" error with ChromaDB

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
from langchain_ollama import OllamaLLM
from langchain_core.output_parsers import StrOutputParser

from langchain_chroma import Chroma as LangchainChroma
from langchain_ollama.embeddings import OllamaEmbeddings
embed_model = OllamaEmbeddings(model='mxbai-embed-large')
vector_store = LangchainChroma(collection_name = 'some-collection,
                               embedding_function = embed_model)
llm = OllamaLLM(model='llama3')
chain = (
    {
        "docs": vector_store.as_retriever()
        "question": RunnablePassthrough(),
    }
    | SOME_PROMPT
    | llm
    | StrOutputParser()
)

Error Message and Stack Trace (if applicable)
Traceback (most recent call last):
File "/path/lib/python3.10/site-packages/chainlit/utils.py", line 44, in wrapper
return await user_function(**params_values)
File "/path/lib/python3.10/site-packages/chainlit/callbacks.py", line 118, in with_parent_id
await func(message)
File "/path/rag_poc/main.py", line 25, in on_message
async for chunk in runnable.astream(
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 5537, in astream
async for item in self.bound.astream(
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 3432, in astream
async for chunk in self.atransform(input_aiter(), config, **kwargs):
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 3415, in atransform
async for chunk in self._atransform_stream_with_config(
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 2308, in _atransform_stream_with_config
chunk = cast(Output, await py_anext(iterator))
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 3385, in _atransform
async for output in final_pipeline:
File "/path/lib/python3.10/site-packages/langchain_core/output_parsers/transform.py", line 84, in atransform
async for chunk in self._atransform_stream_with_config(
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 2261, in _atransform_stream_with_config
final_input: Optional[Input] = await py_anext(input_for_tracing, None)
File "/path/lib/python3.10/site-packages/langchain_core/utils/aiter.py", line 76, in anext_impl
return await anext(iterator)
File "/path/lib/python3.10/site-packages/langchain_core/utils/aiter.py", line 125, in tee_peer
item = await iterator.anext()
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 1455, in atransform
async for ichunk in input:
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 1455, in atransform
async for ichunk in input:
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 3916, in atransform
async for chunk in self._atransform_stream_with_config(
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 2308, in _atransform_stream_with_config
chunk = cast(Output, await py_anext(iterator))
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 3903, in _atransform
chunk = AddableDict({step_name: task.result()})
File "/path/.pyenv/versions/3.10.14/lib/python3.10/asyncio/futures.py", line 201, in result
raise self._exception.with_traceback(self._exception_tb)
File "/path/.pyenv/versions/3.10.14/lib/python3.10/asyncio/tasks.py", line 232, in __step
result = coro.send(None)
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 3886, in get_next_chunk
return await py_anext(generator)
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 3415, in atransform
async for chunk in self._atransform_stream_with_config(
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 2308, in _atransform_stream_with_config
chunk = cast(Output, await py_anext(iterator))
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 3385, in _atransform
async for output in final_pipeline:
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 4943, in atransform
async for output in self._atransform_stream_with_config(
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 2261, in _atransform_stream_with_config
final_input: Optional[Input] = await py_anext(input_for_tracing, None)
File "/path/lib/python3.10/site-packages/langchain_core/utils/aiter.py", line 76, in anext_impl
return await anext(iterator)
File "/path/lib/python3.10/site-packages/langchain_core/utils/aiter.py", line 125, in tee_peer
item = await iterator.anext()
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 1473, in atransform
async for output in self.astream(final, config, **kwargs):
File "/path/lib/python3.10/site-packages/langchain_core/runnables/base.py", line 1018, in astream
yield await self.ainvoke(input, config, **kwargs)
File "/path/lib/python3.10/site-packages/langchain_core/retrievers.py", line 317, in ainvoke
raise e
File "/path/lib/python3.10/site-packages/langchain_core/retrievers.py", line 310, in ainvoke
result = await self._aget_relevant_documents(
File "/path/lib/python3.10/site-packages/langchain_core/vectorstores/base.py", line 1101, in _aget_relevant_documents
docs = await self.vectorstore.asimilarity_search(
File "/path/lib/python3.10/site-packages/langchain_core/vectorstores/base.py", line 651, in asimilarity_search
return await run_in_executor(None, self.similarity_search, query, k=k, **kwargs)
File "/path/lib/python3.10/site-packages/langchain_core/runnables/config.py", line 588, in run_in_executor
return await asyncio.get_running_loop().run_in_executor(
File "/path/.pyenv/versions/3.10.14/lib/python3.10/asyncio/futures.py", line 285, in await
yield self  # This tells Task to wait for completion.
File "/path/.pyenv/versions/3.10.14/lib/python3.10/asyncio/tasks.py", line 304, in __wakeup
future.result()
File "/path/.pyenv/versions/3.10.14/lib/python3.10/asyncio/futures.py", line 201, in result
raise self._exception.with_traceback(self._exception_tb)
File "/path/.pyenv/versions/3.10.14/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/path/lib/python3.10/site-packages/langchain_core/runnables/config.py", line 579, in wrapper
return func(*args, **kwargs)
File "/path/lib/python3.10/site-packages/langchain_chroma/vectorstores.py", line 582, in similarity_search
docs_and_scores = self.similarity_search_with_score(
File "/path/lib/python3.10/site-packages/langchain_chroma/vectorstores.py", line 679, in similarity_search_with_score
query_embedding = self._embedding_function.embed_query(query)
File "/path/lib/python3.10/site-packages/langchain_ollama/embeddings.py", line 164, in embed_query
return self.embed_documents([text])[0]
File "/path/lib/python3.10/site-packages/langchain_ollama/embeddings.py", line 159, in embed_documents
embedded_docs = self._client.embed(self.model, texts)["embeddings"]
File "/path/lib/python3.10/site-packages/ollama/_client.py", line 262, in embed
return self._request(
File "/path/lib/python3.10/site-packages/ollama/_client.py", line 75, in _request
raise ResponseError(e.response.text, e.response.status_code) from None
ollama._types.ResponseError: invalid input type
Description
from langchain_ollama.embeddings import OllamaEmbeddings
from langchain_community.embeddings import OllamaEmbeddings

It seems like the newer version of OllamaEmbeddings have issues with ChromaDB - throws exception. Swapping to the older version continues to work
Doing some digging i found out that, with the same code but swapping just the embedding class from legacy to new, the submitted api to Ollama's /api/embed is different:
with: langchain_community.embeddings.OllamaEmbeddings the legacy code, you get the following payload:
{'json': {'model': 'mxbai-embed-large',
          'prompt': "query: {'input': 'What is OTEL SIP, what are its features and benefits?'}",
          'options': {'mirostat': None, 'mirostat_eta': None, 'mirostat_tau': None, 'num_ctx': None, 'num_gpu': None, 'num_thread': None, 'repeat_last_n': None, 'repeat_penalty': None, 'temperature': None, 'stop': None, 'tfs_z': None, 'top_k': None, 'top_p': None}}}

-> this works fine
With langchain_ollama.embeddings.OllamaEmbeddings - the newer one, you get
{'json': {'input': [{'input': 'Some question'}],
          'keep_alive': None,
          'model': 'mxbai-embed-large',
          'options': {},
          'truncate': True}}

-> this blows up
notice the different in 'input' key vs 'prompt'
System Info
langchain                                0.3.6
langchain-chroma                         0.1.4
langchain-cli                            0.0.24
langchain-community                      0.3.2
langchain-core                           0.3.15
langchain-ollama                         0.2.0
langchain-text-splitters                 0.3.0

I guess you are passing a dict as your input. Please see the code below, that might help (I tested it and it works):

from langchain_chroma import Chroma as LangchainChroma
from langchain_ollama.embeddings import OllamaEmbeddings
from langchain_ollama.chat_models import ChatOllama
from langchain_core.runnables import RunnablePassthrough
from langchain_core.output_parsers import StrOutputParser
from langchain_core.prompts import PromptTemplate
embed_model = OllamaEmbeddings(model='mxbai-embed-large')
vector_store = LangchainChroma.from_texts(["Harrison Lives in New York"], embedding=embed_model)
llm = ChatOllama(model='llama3')
SOME_PROMPT = PromptTemplate.from_template("""
Answer the following question: {question}
using the given context:
{docs}
""")
chain = (
    {"docs": vector_store.as_retriever(), "question": RunnablePassthrough()}
    | SOME_PROMPT
    | llm
    | StrOutputParser()
)

thank you for the help
it seems like the dict as input used to work. Strange.


Connect watch list with backend

[x] Add heart functionality to all carousels in index.js
[x] Make hearts work as intended in movies.js
[x] Make hearts work as intended in tv.js

getTrendingMovies() does same thing as getMovies() so we can rename getMovies() to be getTrendingMovies()

I also removed the arrows to move carousels since they conflicted with placing hearts correctly. We can add that part after class is over if needed.

Great work! Nice job Manan!


Add badge pointing to the actual outcome of GitHub actions

It would be nice having a badge pointing to the actual outcome of GitHub actions.

we should also add other badges (one for each action)

Are the badges here what you expected?
(Badges Run tests and Publish Package matching the names of our workflows)

Are the badges here what you expected?
(Badges Run tests and Publish Package matching the names of our workflows)

awesome! just the first GH badge should redireect to the actual GH action (currently it points there: https://github.com/ivadomed/ivadomed/workflows/Python package/badge.svg)

Right! except this workflow is an old one (not used for 7 month now) Maybe we can discard it? (the badge was already there before my modification)
here is the workflow

Right! except this workflow is an old one (not used for 7 month now) Maybe we can discard it? (the badge was already there before my modification)

ah! yes, let's discard it, it is distracting


Added slack notifier

Hey!
My team uses Slack so I decided to extend Stoplight with another notifier. Does it look good to go?

This looks great! Thank you for opening this pull request. I left a few line notes, but this is basically good to go. The only other thing that needs to change is the notifiers section of the readme; I will do that after merging this PR.

@tfausak thanks for the feedback! I updated the PR. The only thing left to do is to decide if we want to pass options to the Notifier. Waiting for you opinion :)

It looks great as is! Thanks again for submitting this pull request. This is a nice feature to have.
I'll update the documentation and make a new release today.

:+1: