Failed to start

Hello,
Do you have any idea why is this happening?
2023-06-02 16:32:58,648 INFO RPC interface 'supervisor' initialized
2023-06-02 16:36:19,536 INFO RPC interface 'supervisor' initialized
2023-06-02 16:32:58,648 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2023-06-02 16:32:58,649 INFO supervisord started with pid 1
2023-06-02 16:32:59,732 INFO exited: monitor (exit status 1; not expected)
2023-06-02 16:32:59,653 INFO spawned: 'api' with pid 7
2023-06-02 16:32:59,656 INFO spawned: 'monitor' with pid 8
2023-06-02 16:32:59,660 INFO spawned: 'mqttwatcher' with pid 9
2023-06-02 16:32:59,809 INFO exited: mqttwatcher (exit status 1; not expected)
2023-06-02 16:33:00,137 INFO exited: api (exit status 1; not expected)
2023-06-02 16:33:01,149 INFO spawned: 'monitor' with pid 11
2023-06-02 16:33:01,143 INFO spawned: 'api' with pid 10
2023-06-02 16:33:01,152 INFO spawned: 'mqttwatcher' with pid 12
2023-06-02 16:33:01,223 INFO exited: monitor (exit status 1; not expected)
2023-06-02 16:33:01,304 INFO exited: mqttwatcher (exit status 1; not expected)
2023-06-02 16:33:01,593 INFO exited: api (exit status 1; not expected)
2023-06-02 16:33:03,598 INFO spawned: 'api' with pid 13
2023-06-02 16:33:03,605 INFO spawned: 'monitor' with pid 14
2023-06-02 16:33:03,609 INFO spawned: 'mqttwatcher' with pid 15
2023-06-02 16:33:03,748 INFO exited: monitor (exit status 1; not expected)
2023-06-02 16:33:03,774 INFO exited: mqttwatcher (exit status 1; not expected)
2023-06-02 16:33:04,058 INFO exited: api (exit status 1; not expected)
2023-06-02 16:33:07,067 INFO spawned: 'api' with pid 16
2023-06-02 16:33:07,071 INFO spawned: 'monitor' with pid 17
2023-06-02 16:33:07,074 INFO spawned: 'mqttwatcher' with pid 18
2023-06-02 16:33:07,147 INFO exited: monitor (exit status 1; not expected)
2023-06-02 16:33:07,202 INFO gave up: monitor entered FATAL state, too many start retries too quickly
2023-06-02 16:33:07,226 INFO exited: mqttwatcher (exit status 1; not expected)
2023-06-02 16:33:07,426 INFO gave up: mqttwatcher entered FATAL state, too many start retries too quickly
2023-06-02 16:33:07,516 INFO exited: api (exit status 1; not expected)
2023-06-02 16:33:08,518 INFO gave up: api entered FATAL state, too many start retries too quickly
2023-06-02 16:34:10,600 WARN received SIGTERM indicating exit request
/usr/lib/python3/dist-packages/supervisor/options.py:474: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
self.warnings.warn(
2023-06-02 16:36:19,529 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2023-06-02 16:36:19,530 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
Br,

Hello!
I would greatly appreciate it if you could assist me by providing the following information:

The configuration file: If possible, please include any relevant details or sections of the configuration file for the application.

The Docker Compose file: This will help me understand how the services are configured to run together. Please ensure that any sensitive information is redacted.

The exact command or series of commands you are using: This will allow me to replicate your process and identify any potential issues.

The architecture of the system you are running this on: You can obtain this by running the uname -a command in the terminal.

Your assistance with these details will significantly contribute to resolving this matter efficiently. Thank you for your cooperation.

I kindly ask you to review the MQTT connection parameters you're using, including the user, password, and host details. The accuracy of these details is critical for establishing a successful connection with the MQTT broker.
Please note that host.docker.internal refers to the Docker host machine. If your MQTT broker is not located on this machine, the host address would need to be replaced with the correct one. It is essential that the host address accurately reflects the machine on which your MQTT broker resides.
Your careful attention to this matter is greatly appreciated. Thank you for your cooperation.

Hello,
<IP_ADDRESS> is the docker host machine, and mosquito MQTT broker running under another container on the same host.
Is there any other log somewhere than the default container log what can add extra info?
Thanks.

/opt/blauberg-homeassistant$ ls -l
total 8
-rw-r--r-- 1 mike root 286 jún    2 18:28 config.ini
-rw-r--r-- 1 mike root 334 jún    2 21:07 docker-compose.yml
/opt/blauberg-homeassistant$ cat config.ini
[Vent]
ip = 1<IP_ADDRESS>
[MQTT]
user = homeassistant
topic = Blauberg
homeassistant_topic = homeassistant
password = redacted
host = <IP_ADDRESS>
port = 1883
scrape_interval = 15
[Blauberg]
api_token = 123
api_port = 8006
/opt/blauberg-homeassistant$ cat docker-compose.yml
version: "2"
services:
blauberg-homeassistant:
image: gracingpro/blauberg-homeassistant:1.0.1
container_name: blauberg-homeassistant
network_mode: bridge
extra_hosts:
- "<IP_ADDRESS>:host-gateway"
ports:
- "8006:8006"
volumes:
- ./config.ini:/opt/blauberg/config.ini
restart: always
/opt/blauberg-homeassistant$ uname -a
Linux 5.19.0-42-generic #43~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 21 16:51:08 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
/opt/blauberg-homeassistant$ docker version
Client: Docker Engine - Community
Version:           20.10.17
API version:       1.41
Go version:        go1.17.11
Git commit:        100c701
Built:             Mon Jun  6 23:03:23 2022
OS/Arch:           linux/amd64
Context:           default
Experimental:      true
Server: Docker Engine - Community
Engine:
Version:          20.10.17
API version:      1.41 (minimum version 1.12)
Go version:       go1.17.11
Git commit:       a89b842
Built:            Mon Jun  6 23:01:15 2022
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          1.6.6
GitCommit:        10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1
runc:
Version:          1.1.2
GitCommit:        v1.1.2-0-ga916309
docker-init:
Version:          0.19.0
GitCommit:        de40ad0
/opt/blauberg-homeassistant$

It appears there might be a typographical error in your vent IP address configuration. Based on your description, the correct configuration should be:
[Vent]
ip = <IP_ADDRESS>

Please double-check and adjust accordingly. Also, I'd like to inform you that we're working on improving the logging functionality in our service. We plan to include these enhancements in our next release, aiming to provide a better user experience and easier troubleshooting. Thanks for your understanding and patience.

Dear User,
Thank you for reaching out and bringing this to our attention. We have implemented enhanced logging in our most recent release to better assist with issues like these.
We kindly request you to update to the latest version by pulling the newest Docker image using the following command:
docker pull gracingpro/blauberg-homeassistant:latest

Then, restart your container. The new logging mechanism will provide more detailed insights into the application workflow, which will help us diagnose and troubleshoot more efficiently.
After running the latest version, could you please share the log output with us if the problem persists? Your feedback is crucial in helping us improve.

OMG. Indeed :)
Looks much better now.
2023-06-03 18:10:41,854 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2023-06-03 18:10:41,854 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2023-06-03 18:10:41,867 INFO RPC interface 'supervisor' initialized
2023-06-03 18:10:41,867 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2023-06-03 18:10:41,867 INFO supervisord started with pid 1
2023-06-03 18:10:42,873 INFO spawned: 'api' with pid 7
2023-06-03 18:10:42,877 INFO spawned: 'monitor' with pid 8
2023-06-03 18:10:42,881 INFO spawned: 'mqttwatcher' with pid 9
2023-06-03 18:10:43,883 INFO success: api entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-03 18:10:43,885 INFO success: monitor entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-03 18:10:43,886 INFO success: mqttwatcher entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
and lot of MQTT topic arrived to mosquito.
Thank you for you help and responsiveness and sorry for bothering you with my bold mistake :)

Thank you for your kind words! I'm glad to hear that the issue has been resolved and that everything is working better now. No need to apologize for any mistakes or for reaching out for help – that's what I'm here for. If you have any further questions or concerns in the future, don't hesitate to ask. Have a great day!


upgrade amberdb.

This request upgrade amberdb from java 7 to java 8.  It also adds the loadWorks method to help with reporting of a list of diverse work records whether connected or not.

@scoen @jrixon @ninhnguyen @m-r-c could you please review?  Thanks.

SonarQube analysis reported 3 issues

 AmberSession.java: This file has 1,113 lines, which is greater than 1,000 authorized. Split it into smaller files.
 AmberSession.java#L325: Define a constant instead of duplicating this literal "collection" 3 times.
 AmberSession.java#L360: Define a constant instead of duplicating this literal "bibId" 3 times.

Build finished.

👍


ByteArrayModelBinder should return null only when type is not matched

#2456
visible behaviours now match MVC 5
prevent CollectionModelBinder from converting no value to byte[0]
prevent TypeConverterModelBinder from converting empty value to byte[] { '\0' }

nit:

remove additional delegates ModelBindingTestHelper.GetOperationBindingContext() calls
a few left despite #2625 cleanup

/cc @harshgMSFT @rynowak
Similar to prior PR but with a bit of cleanup and checking only visible behaviours in byte[] integration tests.

related to this PR issue #2633

:shipit:

:shipit:

e31eab0


Datepicker header height increases when a disabled next or previous year button is displayed

Correct header height

Increased header height when disabled Next Year button is shown (same with Previous Year)

You cannot demonstrate this in the demo page because it does not allow you to set the :minimum or :maximum args.

This issue seems to be caused by padding from re-com.css applied to rc-datepicker-disabled and rc-datepicker-unselectable classes.
The padding would also be applied to disabled dates but is overwritten by padding from bootstrap.css  as shown in the diagram below. Simply, the padding is only used by the following classes in re-com; rc-datepicker-prev-year, rc-datepicker-prev-month, rc-datepicker-next-month and rc-datepicker-next-year which are the icons that cause this issue. I would suggest removing the padding from re-com.css.

Pushing a fix for this.


upower: 0.99.10 -> 0.99.11

Motivation for this change
https://gitlab.freedesktop.org/upower/upower/-/tags/UPOWER_0_99_11
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Could you move the following to nativeBuildInputs:
intltool
libxslt
docbook_xsl
gobject-introspection

and replace intltool by gettext as suggested in the news?

@dtzWill Did that and then some :+1:

Given that we hard depend on libgudev, which is glib wrapper around udev, which is part of systemd, useSystemd = false does not make sense anymore.

Given that we hard depend on libgudev, which is glib wrapper around udev, which is part of systemd, useSystemd = false does not make sense anymore.

It seems that polkit and pulseaudio have a useSystemd as well. Wonder if the situation is similar to this one.

@worldofpeace :heart_eyes: thanks, this is great! \o/


RFC: API Change: Mesh: Add return value for opcode callback

Problem description
The current Mesh API is missing a return value for opcode callbacks to get meaningful information from the callback. One example of such information is message length check. Some Mesh messages have fixed length while others have variable length. Current Mesh implementation only verifies that the incoming message is not shorter than the minimum length. According to Mesh Profile Specification, the implementation should verify the message length and ignore those of invalid length. Fixed-length messages can be verified by the Access layer while variable-length messages can only be checked by callback implementation. This is why we introduce two new macros BT_MESH_LEN_EXACT(len) and BT_MESH_LEN_MIN(len). The former shall be used when defining a fixed-length message and will be verified by the Access layer. The latter is for the variable-length messages and additional checks must be done inside callback implementation. This change is backward compatible, so not using these macros is the same as using BT_MESH_LEN_MIN(len).
Proposed change
PR https://github.com/zephyrproject-rtos/zephyr/pull/34606 implements the proposed change and adjusts in-tree opcode definitions.
Dependencies
Steps for out-of-tree users to adjust to this API change:

Change return type of each callback function used inside struct bt_mesh_model_op definition.
Add return statements inside callback implementations.
Update len field inside struct bt_mesh_model_op and use BT_MESH_LEN_EXACT(len) or BT_MESH_LEN_MIN(len) macros.
Add message length verificaiton inside variable-length message callbacks.

API meeting: no objections raised.

Closed by #34606


Split parsing into a new module

Some initial clean-up before coming back to make a better attempt at parsing subproject commands. The parser should not live amongst the core logic, since it is an entirely separate concern. As a bonus, I moved tests which are to do with parsing into a new test module.

@OpsBotPrime merge

Pull request approved for merge by @alex-mckenna, rebasing now.

Rebased as 8b242f0a064c28a37bd0da2b3d572873ec5123fe, waiting for CI …

CI job :yellow_circle: started.


[Bug] Empty Form Field Toggle State Defaults to On When Blueprint is Imported

Issue
Empty page form fields marked toggleable: true are defaulting to enabled in admin. When the icon partial was tested on its own as a module empty fields defaulted to disabled. I have posted the relevant blueprints below.
All related code
The entire Grav installation used can be found at: https://github.com/memtech3/Duck-Picnic-Development-Environment
The theme code used can be found at: https://github.com/memtech3/duck-picnic on the icon-partial branch
Blueprints with import:
modular/statpanels.yaml
title: Stat Panels
'@extends': default

form:
  fields:
    tabs:
      fields:
        statpanels:
          type: tab
          title: Stat Panels
          fields:
            header.statpanels:
              name: statpanels
              type: list
              label: Stat Panels
              fields:
                .icon:
                  type: section
                  title:
                  import@:
                    type: partials/icon
                .header:
                  type: text
                  label: Statistic
                .text:
                  type: editor
                  label: Text

partials/icon.yaml
form:
  fields:
    .icon:
      type: iconpicker
      label: Icon
      toggleable: true
    .color:
      type: colorpicker
      label: Icon Color
      toggleable: true
    .image:
      type: mediapicker
      folder: 'user/pages/images'
      label: Select an image to use as an icon
      preview_images: true
      toggleable: true
    .imageurl:
      type: text
      label: Input a url to use as an icon
      toggleable: true
    .header:
      type: text
      label: Header
      toggleable: true
    .link:
      type: text
      label: Link
      toggleable: true

Blueprints for module without import:
modular/icon.yaml
title: Icon
'@extends': default

form:
  fields:
    tabs:
      fields:
        header.icon:
          type: tab
          title: Icon
          fields:
            .icon:
              type: iconpicker
              label: Icon
              toggleable: true
            .color:
              type: colorpicker
              label: Icon Color
              toggleable: true
            .image:
              type: mediapicker
              folder: 'user/pages/images'
              label: Select an image to use as an icon
              preview_images: true
              toggleable: true
            .imageurl:
              type: text
              label: Input a url to use as an icon
              toggleable: true
            .header:
              type: text
              label: Header
              toggleable: true
            .link:
              type: text
              label: Link
              toggleable: true

Maybe a similar issue: https://github.com/getgrav/grav-plugin-admin/issues/2217
I think I've fixed it for me.

Maybe a similar issue: https://github.com/getgrav/grav-plugin-admin/issues/2217
I think I've fixed it for me.

I tried adding your code between line 72 and 73 but that doesn't seem to change the behavior even after I remove the keys and values saved as null from the page frontmatter.
{% if default_layout != 'key' %}
{% set originalValue = child_value %}
{% endif %}

@memtech3 I've created a modular/statpanels.yaml and a partials/icon.yaml with your content, but I cannot reproduce your issue. I did not changed anything in the code (Grav v1.7.25). The fields are still empty even after I've saved the form.

This is what the frontmatter looks like:
title: Test
body_classes: modular
statpanels:
    -
        header: null
        text: null

I just downloaded the latest version of grav+admin (<IP_ADDRESS>, <IP_ADDRESS>), installed my theme in it, and I am still having the issue. Can you try installing my theme? The relevant code is on the main branch https://github.com/memtech3/duck-picnic. The module is called statpanels.
Some other info: I am running php -S localhost:8000 system/router.php on Ubuntu 21.10 with PHP 8 and the PHP 8 versions of all the required PHP extensions
maybe this is a php 8 issue? maybe there are issues with the PHP 8 versions of the extensions?

I just noticed that the imageurl field toggle does not automatically toggle on like the rest of the fields

Ok I am hoping that I am understanding the problem and what you are trying to return but I ended up with a few little tweaks
statpanels.yaml
title: Stat Panels
'@extends': default

form:
  fields:
    tabs:
      fields:
        statpanels:
          type: tab
          title: Stat Panels
          fields:
            header.statpanels_section:
              type: section
              title: Page Headings
              underline: true
            header.statpanels:
              type: list
              collapsed: true
              import@:
                type: partials/icon

icons.yaml
form:
  fields:
    .icon:
      type: iconpicker
      label: Icon
      toggleable: true
    .color:
      type: colorpicker
      label: Icon Color
      toggleable: true
    .image:
      type: mediapicker
      folder: 'user/pages/images'
      label: Select an image to use as an icon
      preview_images: true
      toggleable: true
    .imageurl:
      type: text
      label: Input a url to use as an icon
      toggleable: true
    .header:
      type: text
      label: Header
      toggleable: true
    .smalltext:
      type: text
      label: Small Text
      toggleable: true
    .link:
      type: text
      label: Link
      toggleable: true

which returned the data to statpanels.md

---
title: statpanels
body_classes: modular
statpanels:
    -
        icon: 'fa fa-file-o'
        color: '#992828'
        header: Testing
        smalltext: Small
    -
        icon: 'fa fa-arrow-circle-o-down'
        color: '#593e3e'
        header: 2nd
---

Is this your required result ?


kMeans clustering error

Hi, I'm trying to run kmeans clustering but I got an error : 'unexpected keyword argument n_jobs'.  I'm working with a 4D image.
Thanks for your help
OS: Windows 10
Python: 3.9

Fixed by d9fe93f05383e7d08ac21cbd7102778e10da0b32


Integrate Backend with Static File Approach

This is going to be my new front end as I am scrapping the use of React. This issue will integrate a new login frontend as well as integrating the game chat into the main backend

Skeleton game is now fully integrated with static front end and login registration. This issue just needs the chat to be integrated now.

The chat is not integrated yet, but this issue can now be closed as I have integrated the main things besides the chat. I want to get this merged and integrate the chat on an other issue. Issue can now be closed.


Script in multiple languages

Hi,
thank you for developing this plugin, I have a question: how do I load different banners according to the selected language? the cookie policy id changes for each language even if the site id is the same, I couldn't figure out a way to do this with your plugin,
Thank you
Alessio

Hello @vervelover,
Thanks for reaching out. As a matter of fact, we are just experiencing the same problem. We need to adjust the script based on the active locale, using the nuxt/i18n module.
In the coming weeks we will look for a solution. I'll keep you posted.

Any news?

Any news on i18n support and the Nuxt 3 version?   I'm open to collaborate

Hi @vernaillen.
As we are most likely discontinuing our Nuxt development, we won't be upgrading this module to support Nuxt 3.
Feel free to create a PR if you want, I'd be happy to merge.


harbor_project_member_group resources not  deleted

Hello there, hope you could help me with this - or if we can manage to work on it together
Describe the bug
Given an OIDC (Keycloak) group name + permission and its linked project, the harbor_project and the subsequential harbor_project_member_group resources are correctly created, but after executing a terraform destroy the groups are still on the Harbor. This happens with any group/project name and any group role.
To Reproduce
terraform apply and then terraform destroy on:
terraform {
  required_providers {
    harbor = {
      source = "goharbor/harbor"
    }
  }
}

provider "harbor" {
  url      = var.server_harbor_url
  username = var.server_harbor_username
  password = var.server_harbor_password
  insecure = var.server_harbor_insecure_connection
}

resource "harbor_project" "my_project" {
  name                        = "test_project"
}

resource "harbor_project_member_group" "my_project_group" {
  project_id = harbor_project.my_project.id
  group_name = "test_group"
  role       = "guest"
  type       = "oidc"
}

Expected behavior
After executing terraform destroy both resources should be deleted.
The project is correctly deleted, the group isn't.
Additional context

Provider Version v3.10.12 (atm latest)
Terraform Version v1.7.5 and v.1.9.0 (atm latest)
Harbor Version v2.10.0-6abb4eab

Hello,
harbor_project_member_group handle the membership not the group itself.
the creation (and deletion) of group is handle by harbor_group, but with OIDC you can't use it.
i think it's not the goal of harbor_project_member_group to check if the group is still used or not, if we do this, it means for each membership deletion, the harbor provider will need to check all the projects to check if there is the group as member or not
it should be probably handle by harbor itself in the garbage collect feature
(same as #437)

Hello,
thanks for the answer
I just ran both Garbage Collection and Garbage Collection enabling Allow garbage collection on untagged artifacts but groups are still there.
I'm questioning then, if checking group's uselessness it's not the goal of harbor_project_member_group and I can't "assign permissions on projects" to harbor_group managed groups, how am I going to automate their deletion?

I worded my sentence badly, Garbage collection does not currently delete groups. But I think it should be, at least for OIDC. Can you create an issue on the Harbor project if you need it ? https://github.com/goharbor/harbor/issues
You can import groups you want to delete as harbor_group resources before the deletion of the harbor_project_member_group
And for next creation of harbor_project_member_group, you can create groups with terraform before you create the membership.


ecc: 1.0.12 -> 1.0.27

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/eunomia-bpf/eunomia-bpf/releases.
meta.description for ecc is: the eBPF compile toolchain for eunomia-bpf
meta.homepage for ecc is: https://eunomia.dev
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.16 with grep in /nix/store/3zmp7y2qd4ssiai9m2fj03hp83g8f3hd-ecc-1.0.16
found 1.0.16 in filename of file in /nix/store/3zmp7y2qd4ssiai9m2fj03hp83g8f3hd-ecc-1.0.16

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
ecc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3zmp7y2qd4ssiai9m2fj03hp83g8f3hd-ecc-1.0.16 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ecc https://github.com/r-ryantm/nixpkgs/archive/c348d9e878a74534c5e0776e16046f01fb13a731.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c348d9e878a74534c5e0776e16046f01fb13a731#ecc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3zmp7y2qd4ssiai9m2fj03hp83g8f3hd-ecc-1.0.16
ls -la /nix/store/3zmp7y2qd4ssiai9m2fj03hp83g8f3hd-ecc-1.0.16/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ecc

Maintainer pings
cc @oluceps for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/eunomia-bpf/eunomia-bpf/releases.
meta.description for ecc is: the eBPF compile toolchain for eunomia-bpf
meta.homepage for ecc is: https://eunomia.dev
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.19 with grep in /nix/store/lpbpss23jlclk5mrcr6cn6siis8a7lxz-ecc-1.0.19
found 1.0.19 in filename of file in /nix/store/lpbpss23jlclk5mrcr6cn6siis8a7lxz-ecc-1.0.19

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
ecc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lpbpss23jlclk5mrcr6cn6siis8a7lxz-ecc-1.0.19 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ecc https://github.com/r-ryantm/nixpkgs/archive/3691c8896035ed8abed337a45a20ec03029b1bc0.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/3691c8896035ed8abed337a45a20ec03029b1bc0#ecc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lpbpss23jlclk5mrcr6cn6siis8a7lxz-ecc-1.0.19
ls -la /nix/store/lpbpss23jlclk5mrcr6cn6siis8a7lxz-ecc-1.0.19/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ecc

Maintainer pings
cc @oluceps for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/eunomia-bpf/eunomia-bpf/releases.
meta.description for ecc is: the eBPF compile toolchain for eunomia-bpf
meta.homepage for ecc is: https://eunomia.dev
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.20 with grep in /nix/store/xsvgdb75gvyq41hvm3w4irdzh6k7syr7-ecc-1.0.20
found 1.0.20 in filename of file in /nix/store/xsvgdb75gvyq41hvm3w4irdzh6k7syr7-ecc-1.0.20

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
ecc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xsvgdb75gvyq41hvm3w4irdzh6k7syr7-ecc-1.0.20 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ecc https://github.com/r-ryantm/nixpkgs/archive/f0f2ccc074420c07cce184bab9187638b82f7e72.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/f0f2ccc074420c07cce184bab9187638b82f7e72#ecc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xsvgdb75gvyq41hvm3w4irdzh6k7syr7-ecc-1.0.20
ls -la /nix/store/xsvgdb75gvyq41hvm3w4irdzh6k7syr7-ecc-1.0.20/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ecc

Maintainer pings
cc @oluceps for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/eunomia-bpf/eunomia-bpf/releases.
meta.description for ecc is: the eBPF compile toolchain for eunomia-bpf
meta.homepage for ecc is: https://eunomia.dev
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.21 with grep in /nix/store/pzqignbd2ny013021rnl78n4j32wbbhh-ecc-1.0.21
found 1.0.21 in filename of file in /nix/store/pzqignbd2ny013021rnl78n4j32wbbhh-ecc-1.0.21

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
ecc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pzqignbd2ny013021rnl78n4j32wbbhh-ecc-1.0.21 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ecc https://github.com/r-ryantm/nixpkgs/archive/a1502137a27eaa75c47f86b3ec3268db984b5f4a.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a1502137a27eaa75c47f86b3ec3268db984b5f4a#ecc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pzqignbd2ny013021rnl78n4j32wbbhh-ecc-1.0.21
ls -la /nix/store/pzqignbd2ny013021rnl78n4j32wbbhh-ecc-1.0.21/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ecc

Maintainer pings
cc @oluceps for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/eunomia-bpf/eunomia-bpf/releases.
meta.description for ecc is: EBPF compile toolchain for eunomia-bpf
meta.homepage for ecc is: https://eunomia.dev
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.22 with grep in /nix/store/8xhkdyg8b1wr61byk8vgrbkaspf9hypv-ecc-1.0.22
found 1.0.22 in filename of file in /nix/store/8xhkdyg8b1wr61byk8vgrbkaspf9hypv-ecc-1.0.22

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

ecc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8xhkdyg8b1wr61byk8vgrbkaspf9hypv-ecc-1.0.22 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ecc https://github.com/r-ryantm/nixpkgs/archive/b80d591892566b461a98f7ea96d890cccfa3bb10.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b80d591892566b461a98f7ea96d890cccfa3bb10#ecc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8xhkdyg8b1wr61byk8vgrbkaspf9hypv-ecc-1.0.22
ls -la /nix/store/8xhkdyg8b1wr61byk8vgrbkaspf9hypv-ecc-1.0.22/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ecc

Maintainer pings
cc @oluceps for testing.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/eunomia-bpf/eunomia-bpf/releases.
meta.description for ecc is: EBPF compile toolchain for eunomia-bpf
meta.homepage for ecc is: https://eunomia.dev
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.26 with grep in /nix/store/3h1s6dfbmk9ssf3d14m26q8vxvv0ivh0-ecc-1.0.26
found 1.0.26 in filename of file in /nix/store/3h1s6dfbmk9ssf3d14m26q8vxvv0ivh0-ecc-1.0.26

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

ecc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3h1s6dfbmk9ssf3d14m26q8vxvv0ivh0-ecc-1.0.26 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ecc https://github.com/r-ryantm/nixpkgs/archive/ec672b6c10f053812110baa1303c09a1976c0ad4.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ec672b6c10f053812110baa1303c09a1976c0ad4#ecc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3h1s6dfbmk9ssf3d14m26q8vxvv0ivh0-ecc-1.0.26
ls -la /nix/store/3h1s6dfbmk9ssf3d14m26q8vxvv0ivh0-ecc-1.0.26/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ecc

Maintainer pings
cc @oluceps for testing.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/eunomia-bpf/eunomia-bpf/releases.
meta.description for ecc is: EBPF compile toolchain for eunomia-bpf
meta.homepage for ecc is: https://eunomia.dev
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.27 with grep in /nix/store/x2wyh3shaj7bpxgh1aq18kcx5zp68zrf-ecc-1.0.27
found 1.0.27 in filename of file in /nix/store/x2wyh3shaj7bpxgh1aq18kcx5zp68zrf-ecc-1.0.27

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

ecc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/x2wyh3shaj7bpxgh1aq18kcx5zp68zrf-ecc-1.0.27 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ecc https://github.com/r-ryantm/nixpkgs/archive/6504eee8e06eaca10927f355d87c4ecb2dc25ddf.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/6504eee8e06eaca10927f355d87c4ecb2dc25ddf#ecc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/x2wyh3shaj7bpxgh1aq18kcx5zp68zrf-ecc-1.0.27
ls -la /nix/store/x2wyh3shaj7bpxgh1aq18kcx5zp68zrf-ecc-1.0.27/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ecc

Maintainer pings
cc @oluceps for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 274222 run on x86_64-linux 1

1 package built:

ecc


Fixes vanity URL routing #trivial

The type of this PR is: bugfix

Description

Discussed in Slack: https://artsy.slack.com/archives/CN8S32FJR/p1599244547186900
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)

@brainbicycle Yeah, that's not a bad idea. But you're right, #3771 will migrate this, and its new approach guarantees type safety for routes.


Updating the analyzers for Visual Studio 2015 RC

I updated the NuGet packages and project files for Visual Studio 2015 RC.
I have verified that all tests pass and the analyzers work when debugging the VSIX.

@stebet Thanks for doing this! Can you squash your commits into one (fc5d832)? After that I will merge this.

Thanks for doing this!


Bump dependencies

This is a breaking change as reqwest is publically exposed via HttpRequest::client and maybe other fields.

Thanks for keeping an eye on this!


Adding contributors in the readme

We can add the list of contributors who contributed to this repository similar to this :

@diyajaiswal11
I would like to work on this.

@diyajaiswal11
I would like to work on this.

Go ahead @m-code12


Pre-release version of Copilot Chat v0.12.2023122001 is not using GPT-4

I'm using the latest VS Code insider version (1.86.0-insider).
With the newest pre-release version (v0.12.2023122001), my requests are not being resolved by GPT-4, but by GPT-3.5:
2024-01-05 17:40:51.440 [info] [auth] Got Copilot token for PeterDraex
2024-01-05 17:41:00.578 [info] [chat fetch] url https://api.githubcopilot.com/chat/completions
2024-01-05 17:41:00.579 [info] [chat fetch] modelMaxTokenWindow 8192
2024-01-05 17:41:00.579 [info] [chat fetch] chat model gpt-3.5-turbo
2024-01-05 17:41:01.887 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 1307 ms
2024-01-05 17:41:01.892 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-01-05 17:41:01.893 [info] [streamChoices] request done: requestId: [f5fb6707-e71e-41c5-97a0-44b6c1bd29d8] responseId: [3796c246-44ae-4dae-9980-17d409926e40] model deployment ID: [x338b9c029b38]
2024-01-05 17:41:01.902 [info] [chat fetch] url https://api.githubcopilot.com/chat/completions
2024-01-05 17:41:01.902 [info] [chat fetch] modelMaxTokenWindow 8192
2024-01-05 17:41:01.902 [info] [chat fetch] chat model gpt-3.5-turbo
2024-01-05 17:41:02.748 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 847 ms
2024-01-05 17:41:02.750 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-01-05 17:41:02.751 [info] [streamChoices] request done: requestId: [ed079819-4d92-4a07-815a-02d6cfd56940] responseId: [c04e5302-5ba2-4aa7-8033-cc6440e5e956] model deployment ID: [x338b9c029b38]

If I downgrade to a release version v0.11.1, the chat correctly uses GPT-4:
2024-01-05 17:45:28.205 [info] [auth] Got Copilot token for PeterDraex
2024-01-05 17:45:54.447 [info] [chat fetch] engine https://api.githubcopilot.com/chat
2024-01-05 17:45:54.447 [info] [chat fetch] modelMaxTokenWindow 4096
2024-01-05 17:45:54.447 [info] [chat fetch] chat model gpt-4
2024-01-05 17:45:56.633 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 2185 ms
2024-01-05 17:45:57.230 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-01-05 17:45:57.231 [info] [streamChoices] request done: requestId: [73a9dc31-d1e1-44ed-b467-623b5e3bf0e1] responseId: [e0e77fcb-e96c-467b-86d5-3fe778f78ad8] model deployment ID: [x8d3c95500d67]
2024-01-05 17:45:57.341 [info] [chat fetch] engine https://api.githubcopilot.com/chat
2024-01-05 17:45:57.341 [info] [chat fetch] modelMaxTokenWindow 8192
2024-01-05 17:45:57.342 [info] [chat fetch] chat model gpt-3.5-turbo
2024-01-05 17:45:58.027 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 685 ms
2024-01-05 17:45:58.028 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-01-05 17:45:58.029 [info] [streamChoices] request done: requestId: [c4b6686a-ded7-4fba-ba57-2ad1c37f7239] responseId: [ebd4a3b9-48d8-44a1-a85f-d046239426d5] model deployment ID: [x338b9c029b38]

Is this intentional? Is there any way to make sure GPT-4 is always used?

I'm not seeing the same. Do you have any settings related to copilot in your settings.json?
Are you using the panel or inline chat?

I've now commented out the settings I had, restarted VS and tested again. No change.
It behaves the same for the panel and for inline chat - GPT-4 on Release version and GPT-3.5 on pre-release.
My settings.json:
{
    "editor.inlineSuggest.enabled": true,
    // "github.copilot.enable": {
    //     "*": true,
    //     "plaintext": false,
    //     "markdown": true,
    //     "scminput": false
    // },
    "editor.accessibilitySupport": "off",
    "git.autofetch": true,
    "git.confirmSync": false,
    // "github.copilot-labs.showBrushesLenses": true,
    // "github.copilot-labs.showTestGenerationLenses": true,
    // "github.copilot-labs.advanced": {},
    "dotnet.preferRuntimeFromSDK": true,
    "razor.trace": "Verbose",
    "git.enableSmartCommit": true,
    "diffEditor.ignoreTrimWhitespace": false,
    "github-actions.workflows.pinned.workflows": []
}

I've now tested the combination of:

VS Code 1.85.1 - current release version
Copilot Chat extension v0.12.2023120701 - pre-release, but not as recent as is available for VSCode Insiders

On that, GPT-4 with 8192 token window is working for me.

Hmm nobody on my team can repro. We had a small experimenting running where a super small percentage of users would still receive GPT 3.5 turbo so we could determine request quality across the two models. However, I've just gone ahead and stopped that experiment so lets see if the issue resolves over the weekend as there has been no code changes.

It seems like I was part of the experiment. After VS Code restart, I am getting GPT-4 (on 1.86-insider + v0.12.2023122001).
However, I am still getting only 4096 token window and @workspace is not working. Is that intended?
#file is working okay.
2024-01-06 11:44:27.834 [info] [chat fetch] chat model gpt-4
2024-01-06 11:44:29.945 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 2110 ms
2024-01-06 11:44:31.587 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-01-06 11:44:31.587 [info] [streamChoices] request done: requestId: [b3925d61-b8d3-4e5b-8a6d-f239bde6117a] responseId: [075e70f7-6117-4758-9c8c-e698be5467e6] model deployment ID: [x8d3c95500d67]
2024-01-06 11:44:31.590 [info] [chat fetch] url https://api.githubcopilot.com/chat/completions
2024-01-06 11:44:31.590 [info] [chat fetch] modelMaxTokenWindow 8192
2024-01-06 11:44:31.590 [info] [chat fetch] chat model gpt-3.5-turbo
2024-01-06 11:44:32.080 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 490 ms
2024-01-06 11:44:32.081 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-01-06 11:44:32.082 [info] [streamChoices] request done: requestId: [b6420983-27d9-43dc-86c5-d6fc19f41940] responseId: [6e98d977-52ed-40d2-8435-171066148bea] model deployment ID: [x338b9c029b38]

Your query must start with @workspace. 4,096 tokens is expected due to GPT 4. We're looking into raising the context window in the future.


Why the model does not go training?

Hello, I am a Chinese student.
I have pre-processed the dataset, and use the train_MUSIC.sh to train the default model.
But the result is not what I supposed.  The metrics is all 0.
Even I directly use the eval_MUSIC.sh (I have downloaded the trained model), I also get the 0 metics(SDR ,SIR, .etc).
I don't change the code that you submit in github.
So how can I find what the problem is?

I am getting the same result - all metrics are 0. @avis-ma Did you solve this?
EDIT: This bug, if it is indeed a bug - would be great if the authors confirmed this, might have come from line 129 in file dataset/base.py:
audio_raw *= (2.0**-31)
From the comment of the authors, this line is supposed to normalize the output of the torchaudio.load() function to the range [-1, 1]. However, this normalization is already done by the torchaudio.load() function itself (see https://pytorch.org/audio/#torchaudio.load). Therefore, what line 129 does is effectively making everything in audio_raw becomes zeros.
This all-zero audio_raw make all the metrics zeros as well, because later in the function calc_metrics() in file main.py, line 150, there is a check whether the ground truth audio is all-zero or not. If it is, then no metric calculation is carried out. Since the audio loaded from the dataset is always all-zero, this check is always true and hence the metrics were never calculated.
The fix is simple: comment out line 129 in file dataset/base.py. After doing so I got something like this:
[Eval Summary] Epoch: 0, Loss: 0.2974, SDR_mixture: 1.4887, SDR: 3.9951, SIR: 9.2085, SAR: 10.6352
Plotting html for visualization...

Thanks @ngmq , the data scale really matters. However, the training process still cannot converge. After 2 training epochs, the loss hovers around some value, say 0.20, and the predicted two masks are also similar. Did you encounter this problem before?

Thanks @ngmq , the data scale really matters. However, the training process still cannot converge. After 2 training epochs, the loss hovers around some value, say 0.20, and the predicted two masks are also similar. Did you encounter this problem before?
@zjsong That did not happen to me, my training went fine. Maybe checking the input data would help?

@ngmq Thanks for your reply. I just found if the training process takes enough steps forward (e.g., >25 epochs), it would show promising results accordingly.


Better lexing(and scanning) and parsing

There is currently an issue with the lexing strategy for unary operators. Because i have only partially implemented it, constructs that uses unary operators are note exactly recognised. For example
> -(1)
1  # should be -1

This is problematic because it affects expressions such as to give wrong the answer
> -1^2
1  # should be -1
> -(1^2)
1  # should be -1

The main reason for this is that unary operators are not actually lexed themselves, when an expression such as -1 is passed, the program checks if the immediately succeeding character is a number and immediately binds the sign to the number after it, a bracket/parentheses is not a number and thus the operator doesn't get lexed independently at all disabling the parser to not recognise have any knowledge of it.
Also note that + and - are always initially tokenised as Token.BINARY_OPs and I believe this should change.
see this line

One solution I can think of is to do a scanning pass to the whole program/expression, separating each valid characters one by one, before converting them into tokens. This would make lexing easier as now there are only valid characters to lex/tokenise.
This will also allow for the easier separation of binary and unary operators.

3be3d924ab3d9c126a10e860959e12b537760bfe now fixes unary operator precedence bug


AMD IPU error code 10 in windows KVM machine

Hello
I purchased an AMD 8845 HS processor computer (GMK K8).
The PVE virtualization system is installed, the IPU in the host BIOS has been turned on, and the IPU can be seen in the PVE, and then I have passed the IPU PCI device directly to the Win11 virtual machine.

The IPU device is also available in the win11 virtual machine, although the ipu driver has been followed in the virtual machine, but he keeps showing that the device cannot be started. (Code 10).

At the same time, I can see the error code 0xC00000E5 in the event
There is a issue with device PCIVEN_1022&DEV_1502&SUBSYS_15021022&REV_003&267a616a&0&88 on startup.

Driver name: oem31.inf
Class GUID: {4d36e97d-e325-11ce-bfc1-08002be10318}
Service: kipudrv
Low-level screening procedure:
High-level screening procedure:
Problem: 0x0
Status: 0xC00000E5

Any idea?

Virtualization is not supported

is there any update no this?


[PLAT-12017] lodash.template | CVE-2021-23337

Goal
Manually override @lerna/conventional-commits to remove vulnerable lodash.template package, resolving CVE-2021-23337
Design
Ideally, we should update the major version of lerna to resolve this and additional security vulnerabilities, but this requires additional work around CI pipelines and is out of scope for this PR.

has this completely resolved the alert? I can't remember for sure but I thought CodeQL would report a dependabot alert as resolved back to the PR

I've never seen that before, actually! it might be possible to do with dependabot but I don't think we've got it configured that way


sendMessage aborted

Hi,
the docu says:
`
If the request is not successful or the server tells us something isn't ok, then this method dies with the first available error message (either the error description or the status line). You can make this method non-fatal using eval:
my $response = eval { $api->api_request ($method, $args) }
or warn "Request failed with error '$@', but I'm still alive!";
`
I have used:
$av_std_RETVAL = eval  {   $av_obj_TGRAM->sendMessage (     {         chat_id => $av_loc_tgram_CHATID,         text    => $av_tmp_STRING,         disable_notification => 'false',         parse_mode => 'HTML',     }   ) } or warn "Request failed with error '$@', but I'm still alive!";
The string contains unsuported formatting tags:
Logfile: my test logfile xxx
xxx<www>xxxxxx
Error:
Request failed with error 'ERROR: code 400: Bad Request: can't parse entities: Unsupported start tag "www" at byte offset 53 at /usr/share/perl5/WWW/Telegram/BotAPI.pm line 224.         WWW::Telegram::BotAPI::api_request(undef, undef, HASH(0x55e57ea8da98)) called at ./av_perlre.pl line 268         eval {...} called at ./av_perlre.pl line 266 ', but I'm still alive! at ./av_perlre.pl line 266.
Is there any way to let the script still run and grab some error message?

Hello! Thanks for your report.
Could you clarify what problem do you have? Is the problem that your program still exits when the API returns an error even if you have the eval block, or that you would like to extract the error message?
If it's the former, it's weird since eval should trap the errors (and in fact yours looks like a warning, not a fatal). If it's the latter, you should be able to use parse_error to get more information about the message.
Let me know!

Hi,
I expected the program by using the eval to continue - but it aborts.
I am not a very experience programmer. Probably I have done something wrong on the eval statement.
But probably eval simply does not work in this environment - I don't know!
Probably you could do something inside your code that it is not aborted. I don't know!

Hey,
thanks for clarifying! This sounds very strange. The docs for eval are pretty explicative on the fact that they trap fatal errors that happen inside the block. Any chance you have a custom $SIG{'__DIE__'} that might interfere with it? If so, you could try with:
eval { local $SIG{'__DIE__'}; av_obj_TGRAM->sendMessage(...) }

Or maybe any chance you have made warnings fatal e.g. with use warnings FATAL => 'all'? That would also not work correctly with your code.
The last thing I can think of is that maybe you're doing something with $av_std_RETVAL when it fails even if it's undefined.
It would be helpful if you could share more of your code to figure more out!

Hi,
neither, nor. At least, not that I am aware of.
I have attached a testscript which I have used to play arround with the error.
It will not run, since the TELEGRAM settings are not complete. But I am sure you have own tokens and chat-IDs.
av_perlre_github.txt

Thanks for attaching the script! I gave it a spin without even changing the token (which errors out). I first ran the script as-is:
$ perl av_perlre_github.pl
alle optionen:
xxx
xxx
<
www>xxxxxx
Request failed with error 'ERROR: code 404: Not Found at /opt/homebrew/opt/perl/lib/perl5/site_perl/5.36/WWW/Telegram/BotAPI.pm line 224.
	WWW::Telegram::BotAPI::api_request(undef, undef, HASH(0x127c58a60)) called at /opt/homebrew/opt/perl/lib/perl5/site_perl/5.36/WWW/Telegram/BotAPI.pm line 92
	WWW::Telegram::BotAPI::AUTOLOAD(WWW::Telegram::BotAPI=HASH(0x127971170), HASH(0x127c58a60)) called at av_perlre_github.pl line 267
	eval {...} called at av_perlre_github.pl line 266
', but I'm still alive! at av_perlre_github.pl line 266.
$ echo $?
0

This doesn't tell us whether the script exited or not though, since there's nothing after the eval block. I tried to add this line after or warn "Request...":
print "Testing 123... if the script has died this should not print\n";

And I got this:
alle optionen:
xxx
xxx
<
www>xxxxxx
Request failed with error 'ERROR: code 404: Not Found at /opt/homebrew/opt/perl/lib/perl5/site_perl/5.36/WWW/Telegram/BotAPI.pm line 224.
	WWW::Telegram::BotAPI::api_request(undef, undef, HASH(0x144832278)) called at /opt/homebrew/opt/perl/lib/perl5/site_perl/5.36/WWW/Telegram/BotAPI.pm line 92
	WWW::Telegram::BotAPI::AUTOLOAD(WWW::Telegram::BotAPI=HASH(0x144a0df70), HASH(0x144832278)) called at av_perlre_github.pl line 267
	eval {...} called at av_perlre_github.pl line 266
', but I'm still alive! at av_perlre_github.pl line 266.
Testing 123... if the script has died this should not print

Which seems to imply that eval works here and is not killing the script!
To give it one last try I changed your invocation like this:
$av_std_RETVAL="";
unless (
  $av_std_RETVAL = eval { $av_obj_TGRAM->sendMessage ({
      chat_id => $av_loc_tgram_CHATID,
      text    => $av_tmp_STRING,
      disable_notification => 'false',
      parse_mode => 'HTML',
  }) }
) {
  my $err = $av_obj_TGRAM->parse_error;
  print "Oops! The request failed: ", Data::Dumper::Dumper($err), "\n";
}

print "... but the script is still alive!\n";

and I got this output:
alle optionen:
xxx
xxx
<
www>xxxxxx
Oops! The request failed: $VAR1 = {
          'msg' => 'Not Found',
          'code' => '404',
          'type' => 'api'
        };

... but the script is still alive!

Which again suggests that eval is doing its job here and not killing the script! Do you get a different behavior here?

Hi Roberto,
thanks for your testing!
My fault!
I ran the test-script in debug mode. The debug stopped and I misunderstood this as abortion of the script.
I now ran the test-script without debug and you are right, the script survived.
The production script had still a "die" instead of a "warn". I now changed this.
But anyhow I need to find a way to catch the error and eliminate the unsupported formatting string . But this is my problem.
I will close the ticket!


Project 2: Create a RAG + Vector DB + LLM pipeline

Create a pipeline that integrates Retrieval-Augmented Generation (RAG) based on the LPI dataset, a vector database, and a Large Language Model (LLM).

[ ] Use the vector database to provide the LLM model with context about the LPI dataset.
[ ] Ensure the LLM can answer questions about the LPI dataset and make recommendations.
[ ] Store the vector data (consider parquet files, QuadrantDB, SingleStore, ChromaDB, PGVector, or even MongoDB Vector DB)

Notebook showing a example using advance rag techniques such has auto retrieval  and hybrid search  on the LPI Dataset
using Llama Index, Gemini and weaviate vector database
https://www.kaggle.com/code/tacoman789/gemma-few-shot-learning-with-llamaindex?scriptVersionId=202917060

2nd version

using Gemma 2 2b variant instead of Gemma
More Metadata {course, source, model}
More prompt engineering
Summary:
I found that Gemma tends to copy my few shot example instead of using a the contextual information from the RAG. Emptying the table, and prompting the model to fill out the template achieve better results.  Furthermore using Gemma 2 instead of gemma provided better results which is expected since Gemma 2 has better reasoning capabilities

https://www.kaggle.com/code/tacoman789/gemma-few-shot-learning-with-llamaindex/notebook#Testing-a-different-prompt


Escape "like"

I have a table called "like". Should we escape "like" for example when using .from("like")?

Shouldn't be a problem. You can enable the autoQuoteTableNames and avoid any issues, see https://hiddentao.github.io/squel/api.html#cls_defaultquerybuilderoptions


Pipes does not work with jsforce 1.5

Right now package.json includes a lower bound of 1.4.1. That means running npm install will get you latest. For me, that was 1.5, and the pipes app no longer worked. I had to hardcode 1.4.1 explicitly.

Fixed in multi-connector branch. Specified exact version of 1.4.1 in package.json


Release Google.Cloud.BinaryAuthorization.V1 version 2.2.0

Changes in this release:
No API surface changes; just dependency updates.

Created release for Google.Cloud.BinaryAuthorization.V1-2.2.0


is checksum validation available ?

hello, github image generation team here.
we are looking into improving security of github runner images. are there checksum available ?
maybe other integrity validation  best practice ?
cheers

Hi @ilia-shipitsin here are our recommended data integrity/validation best practices. https://github.com/Azure/azure-storage-azcopy/wiki/Data-integrity-and-validation

sorry, we are looking for integrity validation of azcopy utility itself

Hi there, @ilia-shipitsin. We don't currently publish checksums for our releases. This is something we could do in the future. I'll bring it up at our next team standup.
In the meantime, could I ask what kind of checksum you're looking for (crc64, md5, etc.) and how you'd be looking to consume it? It sounds like you'd like to use it in a fairly automated scenario, so perhaps we could provide .md5 files or whatnot next to the actual zip containing the hash of the zip file. e.g.
https://azcopyvnextrelease.blob.core.windows.net/releases/release-10.21.0-20230928/azcopy_darwin_amd64_10.21.0.zip
https://azcopyvnextrelease.blob.core.windows.net/releases/release-10.21.0-20230928/azcopy_darwin_amd64_10.21.0.zip.md5

our security engineers approved us SHA256 or more stronger.
we are fine to download checksum from the any URL

@adreed-msft any updates on the checksum distribution?


Improve YAML serialization.

For #150.
Creates a custom_yaml object that has alternative "representers" registered to it to modify the default output structures.
Summary:

tuple is treated as a list
set is treated as a list, but is sorted to ensure that they're serialized in a deterministic way.
PurePath and subclasses are stringified
ReportType, ScheduleType, and SimTime have yaml_representer static methods and are registered to the custom_yaml object in the custom_yaml.py file.
A generic representer is registered on object and its subclasses to catch anything else that is passed in. It creates a WARNING-level log entry to prompt the user that an "implicit" serialization was performed.
ReportType had __lt__ defined so that a set[ReportType] could be deterministically serialized, as mentioned above.

Some mediocre testing was included.
NOTE: I believe that import yaml and from nrel...custom_yaml import custom_yaml as yaml both import the same object, so it's not clear to me if the unmodified yaml package would be available. The "package-local" import was still used to make it clear that it is modified.

The output .yml can not be directly imported because the code currently expects an input key, but the output includes an input_config key.
@nreinicke advised that outputing an input key rather than input_config was acceptable. I can try to investigate this change and include it in this PR.


Add Proteus (once it's on crates)

https://github.com/wireapp/proteus

that's not very webby – and still not on crates. closing for the time being.


[Request] split RadAway or Rad-X cooldown into individual config settings

It would be useful to have different values for these. For e.g. having one like 30 min or more for Radaway and a really expensive recipe for it (since its a cure), but a lower one for Rad-X since its kind of like Iodine.'
Thanks

Done!


KAFKA-2892: Consumer Docs Use Wrong Method

The KafkaConsumer docs use a non-existent method for assigning partitions (consumer.assign).
The JavaDocs show as:
String topic = "foo";
TopicPartition partition0 = new TopicPartition(topic, 0);
TopicPartition partition1 = new TopicPartition(topic, 1);
consumer.assign(partition0);
consumer.assign(partition1);

Should be:
String topic = "foo";
TopicPartition partition0 = new TopicPartition(topic, 0);
TopicPartition partition1 = new TopicPartition(topic, 1);
consumer.assign(Arrays.asList(partition0));
consumer.assign(Arrays.asList(partition1));

Good catch. assign doesn't actually allow incremental assignment though:
Manually assign a list of partition to this consumer. This interface does not allow for incremental assignment and will replace the previous assignment (if there is one).

It'd need to be consumer.assign(Arrays.asList(partition0, partition1)).

@ewencp Updated.

LGTM

LGTM, but I'm wondering if @eljefe6a didn't mean to submit this PR to Apache Kafka and not the Confluent copy?

@gwenshap  That's correct. I just found out that you can't fork repos with different sources.

ah, so because you already forked confluent's fork you can't fork apache?

Yup http://stackoverflow.com/questions/9644046/how-to-change-the-source-of-a-github-fork

so, afaik, all of us here do "apache first" flow - we have a fork of apache kafka, we do PRs there and we update confluent kafka from apache.
That said, if you don't want to go to the trouble of creating a new fork and re-doing your work, we can probably merge it here and do a PR to apache Kafka from here.

This was submitted to the Apache repo and merged some time ago.


Upstreams Aptos Labs patches

Summary
These changes were made by the Aptos Labs team from a fork of @novifinancial/serde-reflection. Pushing them upstream to remove dependency on forked version.

@ma2bd I'm planning to open this PR but I'm having issues with local testing, mostly reverse-engineering the packages to be installed on the system, and the fact that the .NET versions supported in serde-generate are out of support from Microsoft. Any tips on how to setup a local test environment? Also, should I provide a patch that targets .NET 7, the currently supported version? Thanks!

@gedigi Thanks for sharing your changes upstream. I think we could update the version of .NET in CI and officially in this repo.


failure to list milestones

The tool can produce the following error...
Fetching namespace/my-test-project MetaData (1s)2023/10/26 18:05:05 Failed to list milestones: Get "https://gitlab.teracloud.ninja/api/v4/projects/594/milestones?page=1&per_page=100": EOF

I'll try to get more details about how to reproduce this error.

@robandpdx can you provide some more details, this seems to be a permission issue, but with more details we can learn more.


Style details component correctly, use border-based triangles for marker.

This correctly sets the text colour for the disclosed text and adjusts the spacing so that the disclosed text is aligned with the summary.
It also styles the marker (arrow) using border-based triangles.
This allows us to consistently style the marker across browsers and resolves the issue with the Firefox marker disappearing because of our use of display: inline-block. For more details, see the implementation.md file added as part of this commit.
We also use clip-path to ensure that if browser colours are overridden the marker still appears as a triangle rather than turning into a square.
Chrome
Collapsed

Expanded

Focussed

IE9

IE10

IE11

Edge

Android

iOS

Windows Phone

Firefox (custom colours)

this looks very good. only point is if this shape can/should/will be used anywhere else, should we stick it in globals/objects/shapes?

We wouldn't be able to use it as an object in the traditional sense as you can't add a class to the pseudo element, but it might make a sensible helper mixin. However, I'd suggest we wait until we find ourselves duplicating the functionality and then abstract it, rather than doing it prematurely based on that assumption? (I think it's quite likely – I think we can use this approach for the back link, for example)


remove 2 extra queries from header

No reason to query the database if ems_id == [].
changing the order of the logic removes a (cached) query as well.

These are in the header and every page.
/cc @dmetzger57 negligible performance but 2 fewer queries per page is nicw. trivial changes

@chessbyte fixed


image quality not working

reproducing this example, on line 105, I added the quality option in 50 and the image saved is 2MB grater than the original...  if I changed to 100 or 1 same result.
https://github.com/NativeScript/sample-ImageUpload/blob/master/app/main-page.js#L105

This issue was moved to NativeScript/NativeScript#4404


More fixes

Please fix your problems in PR and add some meaningful comment about changes you made. Thanks.


Add Mutated query filter and DetectChanges::is_mutated

Objective
Closes #15070.
Solution
Added Mutated<T> query filter, and DetectChanges::is_mutated.
For reviewers: Changed<T> was used as a basis, and edited to also access the added ticks.
Testing

Added Mutated<T> assertions to the same tests for Changed<T> and Added<T>.

FWIW, I would prefer if Changed was implemented in terms of Added || Mutated, which I think gives much more intuitive behavior. If I remember the implementation work from many years ago though, this would be substantially more involved.

FWIW, I would prefer if Changed was implemented in terms of Added || Mutated, which I think gives much more intuitive behavior. If I remember the implementation work from many years ago though, this would be substantially more involved.
Please feel free to prove me wrong though!

I actually tried this first, but ran into some issues related to how best to represent Option<Tick> in a space-optimized way with either NonZero or NonMax. Overall it's a much more invasive change.

FWIW, I would prefer if Changed was implemented in terms of Added || Mutated, which I think gives much more intuitive behavior. If I remember the implementation work from many years ago though, this would be substantially more involved.

It can't be flipped around. Added and Changed test if the component's tick is newer than the asking system's tick. Since changed tick >= added tick, Changed naturally includes Added. Mutated can only be derived from changed and not added.
IMO changed = added or mutated only seems more intuitive because of the wording in the docs. If I described the filters to someone like this:

Added<T> => "Fire the first time a T is set."
Changed<T> => "Fire every time a T is set."

Mutated clearly looks like a composition of the two.

Mutated<T> => "Fire every time a T is set except the first time".

Hmm, overall, I think adding this filter will lead to more confusion and possibly bugs (like it did before). The difference between Changed and Mutated is pretty subtle. And, generally speaking, tracking changes exists for optimization. It's not a problem if we propagate a few transforms we didn't need to, but missing new transforms would be a bug.
Also, IIRC the past few times change detection was brought up in passing (in the #engine-dev or #ecs-dev channels on Discord), it seemed like there is a (growing?) consensus among ECS SMEs that they'd prefer if Bevy coarsened the default granularity of change tracking (e.g. archetype-level tracking) so that these filters don't slow down query iteration.
Coarsening makes sense if the purpose of change detection is increasing performance by opportunistically skipping work, but Mutated seems like it'd be significantly less useful without fine-grained tracking.


Updating deepsparse vni check to use hasattr

Catches edge case where if vni is not installed, error is thrown instead of warning

Great catch Ben, completely missed the spelling issue as well!


reduce cognitive complexity of async_set_hvac_mode

Breaking change

Proposed change

Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[ ] New feature (which adds functionality to an existing integration)
[ ] Deprecation (breaking change to happen in the future)
[ ] Breaking change (fix/feature causing existing functionality to break)
[x] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[x] The code change is tested and works locally.
[x] Local tests pass. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the development checklist
[ ] I have followed the perfect PR recommendations
[x] The code has been formatted using Black (black --fast homeassistant tests)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
[ ] Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

[ ] I have reviewed two other open pull requests in this repository.

Anton Ridderby Group 10
Rule 2: High cognitive complexity can make the code harder to under stand in the future when you want to add a new features.
By reducing the value it can potentially save time in the future.
Rule 3: By moving the HVAC toggle outside the function it becomes easier to read and easier to maintain.

looks good


Cloud[SPACE]7 to Cloud[NON-BREAKING SPACE]7

This is totally worth it.

Closing because this change is added in 88902f8


Cloning ViewModel now also clones it's variables if they are an object

Fixes #157

Thanks, @samuelnogueira! Cherry-picked to develop for release with 2.11.0.


feat(popup): move WM toggle Switch to global header

Context

Closes https://github.com/interledger/web-monetization-extension/issues/623
Closes https://github.com/interledger/web-monetization-extension/issues/471
Part of https://github.com/interledger/web-monetization-extension/issues/569

Changes proposed in this pull request

Move WM toggle switch to global header.
Visible only when wallet is connected, and in non-error state.
Screenshots:

Not visible in error state

Not visible when wallet not connected

Can toggle from any page

As of this PR, slider is still shown on payment page

This message can be improved

We decided to make this global switch to enable/disabled entire extension, not just continuous payments.


Add tool for scanning issues without area labels.

Fixes #3495

Cool!  It's be great if this can be setup using a GitHub API key rather than username/password (or at least read username/password from pexpect rather than having you put them on the command line), but I'll use this now to check how we're doing :).

@timabbott Updated :)

This seems to only work in Python 3, not Python 2, due to not using six.moves.configparser.
Otherwise, this is great and was super useful! (I just used it to add the label to everything missing it).
The cool thing about this is that we can build on it as well to ensure we add additional categories tags to issues in the future.  Let me know when you've fixed the Python 2 compatibility issue and then I can merge this.

@timabbott Updated :)

Merged, thanks @hackerkid!


Label colours on mobile too dark in some places - wrong colour

Only appearing on mobile. Colour should be Text/Secondary #9599A5
Please update across market page and all across portfolio
Example from build:

This is needed for v2 launch....too hard to read

update looks good. closing


How to show function name + function parameters with tagbar extension

Hey! I know how to show just the function name just by introducing let g:airline#extensions#tagbar#enabled = 1 in .vimrc.
I also saw the flags in the documentation, and the flag s is probably what i need, but after I use let g:airline#extensions#tagbar#flags = 's', it only shows functionname(), nothing more.
So basically, what am i doing wrong? I just want to show the complete function, that is function name + functiono parameters.
Thank you.

Nevermind, fixed it. Typo in second line.


Deploy OCS2 on the new robotic arm

Describe the bug
Hello everyone, I am a beginner in OCS2 and I would like to follow the tutorial of Manipulator to deploy MPC on my own robotic arm.
Based on my observation, I believe that deploying OCS2 on a new robotic arm mainly requires the following steps: ① creating a launch file ② creating an. info file ③ creating an. urdf file. (Directly copy the information file and launch file from the process and modify them according to their own URDF file)
I have completed the above steps, and after executing the launch file, the following error message will be generated (similar to the situation with issue60 )

And the node graph is as followed

I tried to solve the problem, but there was only one method that had a difference, which was to change the reference of URDF to the STL file in the mesh from a relative path to an absolute path. After the modification, the result is shown in the following figure

And the node graph is as followed

（I think it is worth noticing that when I use relative path，only 1 window is opened, but when I use absolute path, 2 windows are opened） Supposed to be 2 windows.
I have attached the URDF file,. INFO file, and launch file below. May I ask if anyone can provide feedback
SORRY for some reson I can only attach the urdf file but not the STL file
Thank you so much.
Desktop (please complete the following information):
Ubuntu 20.04 + ros noetic
Attached files
urdf.zip

For further step, I deploy ocs2 on a very very simple robot arm（even without mesh）.
For this simple robot arm, It is quiet easy to deploy, I just copy & modify the launch file, copy & modify the .info file, copy the urdf file.
After that, I run the launch file, and most of things goes well .
If someone need that simple arm, I can attach them too

oh no! I forget to mention. For the urdf files in the zip file.

narm1 is the urdf file with the relative path
narm2 is the urdf file with the absolute path

There is a bit process for this error.
① The absolute path and the relative path.
The function RobotInterface
`class MobileManipulatorInterface final : public RobotInterface {
public:
/**

Constructor

@note Creates directory for generated library into if it does not exist.
@throw Invalid argument error if input task file or urdf file does not exist.

@param [in] taskFile: The absolute path to the configuration file for the MPC.
@param [in] libraryFolder: The absolute path to the directory to generate CppAD library into.
@param [in] urdfFile: The absolute path to the URDF file for the robot.
*/`
After I changed the urdf and info and auto_generated path into absulote path. Something imporved
② The .stl file and .dae file
The speed of processing STL files in OCS2 is much slower compared to processing DAE files. Therefore, it is necessary to change the STL file format of the mesh to .dae in order to improve the speed.

Finally!
The issue is settled by setting the .info file like this:
set the "self collision" option from true into false


add wheel to publish

fix for package publication that failed
add wheel to publish
release: v2023.1.3

The version 2023.1.2 is because it's still the 2023-01 list of MeSH terms. It's the second patch though (to make clear the history and the code).


Switch from installing atomic-openshift-utils to openshift-ansible

Enables us to move forward on https://github.com/openshift/openshift-ansible/pull/4264

/hold
running a test


Append |...| to table should not work in 702

ref https://github.com/abapGit/abapGit/pull/4392
APPEND |MANDT = '{ sy-mandt }'| TO ls_config-where.

hmm, there is a unit test with a string template, https://github.com/abaplint/abaplint/blob/master/packages/core/test/abap/statements/append.ts#L56
can you help testing if APPEND |foo| && |bar| TO mt_code. works on 702?

hmm, there is a unit test with a string template, https://github.com/abaplint/abaplint/blob/master/packages/core/test/abap/statements/append.ts#L56
can you help testing if APPEND |foo| && |bar| TO mt_code. works on 702?

it is 731 in fact. But no, it doesn't

it is 731 in fact. But no, it doesn't

@sbcgua try again, 2.64.3

@sbcgua try again, 2.64.3

Cool, it works now. :+1:

Cool, it works now. :+1:


Improve requirement definition

After #5, I think I need a better, cleaner way to define the requirements. Perhaps something similar to how this Cookiecutter does it or how lifelines does it.

Solved in commit 8fab25d1897cb1a6dc2bec2027910c922ab2809e


Project Test Case 9_11

Summary
Any suggestions on how I can fix this?
My program seems to be mixing something up between my human and self checkout servers
Screenshots (if any):

hi weiyang you may wish to refer to my comment below for a similar post #751. for your ease of reference, i have copy pasted my response below, but put simply my very last point could perhaps be the explanation for your issue (mixing up human and scc) - when you update your servers, particularly your SCC, you are returning a Server object instead of an SCC object.
my response below:
i concur with @andhika2002, and to add on,

you should check your arrive -> serve,

in particular, how you determine if there are any free servers.
free servers should be those that can serve immediately.
hence your checking condition most likely is flawed as it is returning a wait instead of serve. More so as 0.035 is almost the start of the simulation, so iirc, im certain that SCC 2 is not serving anyone

on that note,
2. you might want to check your toString() for SCC, & how you update the serverList

for instance, your output shows that it waits at "1".
even if it is waiting, since in ur ss below it already shows "self-checkout 1", we can deduce there are no human servers, only SCC. So your output should be seeing waits at "self-checkout 1". (even if the free server logic is wrong)
this leads me to have the impression that the way you update your servers is also flawed. do check that when updating your SCC you return an SCC object.
for example, in my implementation, SCC is a subclass of Server. I initially made this error that i just mentioned, so even though i THOUGHT i was updating my SCC correctly, but because the event calls the update method from the Server (super) class, so the return type was a Server object, and consequently, that SCC object in the serverList became a Server object. So what i did to solve this was to @ Override the same update method in the SCC (sub) class and make it return an SCC object. This way, in any event where i perform some server function like server.updateServerList(), regardless of the server object being from Server class (super) or SCC class(sub), the return object type is as intended.

hope this helps. cheers.

thanks josh but I have finished, appreciate the insightful comment though


Compose version updated to beta-07.

@burnoo  Hi, Bruno! Please review and merge, currently I can't use library with JC-beta-07, I've update dependencies for 100% compatibility.

Hi, thanks for your PR!
I've just released version 0.3.1 which includes bunch of library updates. It updates compose to beta07, same as your PR.
Released version 0.3.1 is already published and should be available in Maven Central in a few hours.

Hi, @burnoo, thanks for update!


Perceptual Color Picker

As a data visualization designer, I want to be able to edit colors along three separate dimensions independently (hue, saturation, and luminance), so that I can come up with best color combinations for legible data visualizations.

Exactly this is the amazing design we need:

https://svg.wtf/?activeTab=gui&shapes=[["tag"%2C"attributes"%2C"metadata"%2C"id"%2C"children"%2C"path"%2C"a|0|1|2|3|4|5"%2C"svg"%2C"width"%2C"height"%2C"a|8|9"%2C"800"%2C"o|A|B|B"%2C"transform"%2C"inheritedAttributes"%2C"styles"%2C"a|D|E|F"%2C"matrix(1%2C0%2C0%2C1%2C0%2C0)"%2C"o|"%2C"o|G|H|I|I"%2C"root"%2C"circle"%2C"fill"%2C"cx"%2C"cy"%2C"r"%2C"a|M|N|O|P"%2C"%23ea87ee"%2C"n|6S"%2C"n|1w"%2C"o|Q|R|S|S|T"%2C"a|M"%2C"o|V|R"%2C"o|G|H|W|I"%2C"2024-07-24T16%3A59%3A42.017Z16"%2C"a|"%2C"root|2024-07-24T16%3A59%3A42.017Z16"%2C"o|6|L|U|X|Y|Z|a"%2C"%237891E1"%2C"n|6N"%2C"n|4w"%2C"o|Q|c|d|e|T"%2C"o|V|c"%2C"o|G|H|g|I"%2C"2024-07-24T18%3A45%3A51.641Z17"%2C"root|2024-07-24T18%3A45%3A51.641Z17"%2C"o|6|L|f|h|i|Z|j"%2C"a|b|k"%2C"o|6|7|C|J|K|l|K"%2C"a|m"]%2C"n"]

assign me!


As a player of the game, I want to be able to connect from my own device and join the lobby (as in Kahoot) using my username and the lobby pin.

[ ] Upon successfully joining a lobby, the user is able to enter a username. If the username is already taken by someone else in the lobby an error is displayed, and the player is redirected to the username enter page.
[ ] The username is saved to the database.
[ ] Upon failure (e.g., game pin does not exist), the user is redirected to the start page.
[ ] Players can only join a lobby via the “join lobby” button or by creating a lobby themselves.
[ ] Players can only join a lobby before a game has started.
[ ] A player can only join a lobby if the lobby isn’t full (6 players).

Development tasks in client


Teach VSM Generator to work linearly on the size parameter

@cseed I created this issue because I didn't see anything else that tracked this issue. If it's a dupe please close 😀

Thanks!


Enable all device orientation

This looks good to me. Thanks for making those changes.
Might be worth pulling in @theRealWardo since I can't give it a real code review at some point, but going to approve it so we can move forward.
Next time you're in the office I'll grab you for a minute to show me how to get the latest version on my phone. :)

sure. i will guide you in each step


Your requirements are not fine

I think you should mention all the required versions to compile your codes.
There is no version information of these below, as a result I can not compile your codes.
torch-scatter
torch-sparse
torch-cluster
torch-spline
You can see from the screenshot, torch-sparce is already installed but it still says there is an import error. I think this is because of the version issue. kindly state the correct versions. I want to use your work in my literature and paper.

Thanks for your interest on our work! Our work is built on PyG. Please refer to this link for installing all required packages. Also, we have provided a unified package for graph contrastive learning. Please check out this repository.


New issue institution_id registration of IIASA

institution_id = IIASA
institution = International Institute for Applied Systems Analysis (IIASA), Schlossplatz 1 - A-2361 Laxenburg, Austria

@gidden, it now seems alot more clear that IIASA will not be contributing model data to CMIP6, rather forcing datasets - is that correct? If yes, we should remove IIASA from these CVs
@MartinaSt

The original issue was generated when we assumed IIASA would be the organizational CV for ScenarioMIP model data. That is now IAMC. Which forcing datasets are you referring? UoM produces the concentration data, IAMC will be producing emissions data.

@gidden exactly, and these are contributors to the input4MIPs project (registered at input4MIPs-cmor-tables), which is a CMIP6 sub-project, which is the same as UoM who are also input4MIPs contributors.
So we're good to remove IIASA from the CMIP6_CVs


consume extension from nuget

    "predictor.Model.TrainedTreeEnsemble.ToDecisionTreeData(featureNames)"

Was there ever a plan for adding extra parameters into display()? That way a user can pass more information into display. In this case, we want to display(predictor.Model.TrainedTreeEnsemble), but we need to pass featureNames in as well.
/cc @jonsequitur

Refers to: NotebookExamples/csharp/DecisionTrees.ipynb:125 in 594d007. [](commit_id = 594d007818f3d5151c732dbf2e0337b7db116105, deletion_comment = False)


Alternative Get-CsExternalUserCommunicationPolicy

What is the Alternative for the Get-CsExternalUserCommunicationPolicy? Because it is not available anymore in version 4
Get-CsExternalUserCommunicationPolicy : This cmdlet is no longer supported, please consult public documentation.

@pbafna03
How about these? Get-CsOAuthConfiguration ?
With CsExternalUserCommunication I want to check if there is P2PFileTransfer enabled in Teams. But in the newest PowerShell module the cmdlet is no more.

@asterictnl-lvdw - the OAuthConfiguration is not relevant in Teams.

@asterictnl-lvdw Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Update User Information

Admin and owner of the user can modify the user information

[x] Ajv Input Validator
[x] DB Query
[ ] Function (PUT: /user/{username}
[ ] Test Codes

[Email-Add]
If someone add Email, but already exist,

in his/her Email list
in another user's list
How can we handle these?

[Email-Add]
When someone wants to delete an Email, if it doesn't exist, throw an error?

[Email-Add]
If someone add Email, but already exist,

in his/her Email list
in another user's list
How can we handle these?

For already existing username and email pairs, the change request will be ignored.
This is allowed.

[Email-Add]
When someone wants to delete an Email, if it doesn't exist, throw an error?

It is not an error. It just proceed but do not have any effects


Try Binding class

I'm trying to implement CRuby's Binding class.
Binding#local_variables is easy.
But I couldn't implement Binding#eval because it's too difficult.
It failed in this case.
class A
  class << self
    def b
      @a = 42
      b = 'local_variable'
      binding
    end
  end
end
p A.b.eval("[@a, b]")
# Expect: [42, "local_variable"]
# Actual(This branch): [42, []]

Does anyone have a good idea?

Maybe recording the struct RProc* and pc of the previous stack frame could save the binding.

@ksss, by saving the REnv object, the tests contained in your pull request will pass.
https://github.com/dearblue/mruby/tree/binding
This working branch is now the mruby HEAD (07224f8ed9aeb3b85bb0903adae04e8f3f60df5e).
Is it possible for you to continue the work you are planning?

@dearblue Hi.
Thank you for finding this PR.
But I've forgotten what this PR is all about and I have no motivation to continue with it.
I'm glad. If you will take over this project.

I see.
Perhaps there are some parts that can not be implemented due to mruby restrictions, but I will issue a new pull request someday by adding methods that are lacking compared to CRuby.
Thank you for your reply.

I have implemented anything but Binding#irb and created a pull request as #5362.
If you have any concerns, please ask them there.

@dearblue Great Job!!!! 🎉


decode breaks when implemening Format

when i implement this trait, i get an error from defmt:
impl defmt::Format for State {
    fn format(&self, fmt: defmt::Formatter) {
        use chrono::TimeZone;
        let dt = chrono::Utc
            .ymd_opt(self.year, self.month, self.day)
            .and_hms_opt(self.h, self.m, self.s)
            .map(|dt| dt + chrono::Duration::seconds(self.tz_offset as i64))
            .single();

        defmt::write!(
            fmt,
            "FIX: {} | SVs: {} | HDOP: {} | {}",
            self.fix,
            self.svs,
            self.hdop,
            match dt {
                Some(s) => s.to_string(),
                None => "INVALID".to_owned(),
            },
        );
    }
}

 INFO  FIX: 0
└─ pico_clock::__cortex_m_rt_main @ src/main.rs:293
(HOST) ERROR failed to decode defmt data: [0, 0, 0, 0, 2, 0, 0, 0, 0, 3, 7, 49, 4e, 56, 41, 4c, 49, 44]
Error: malformed data

However, if I use info! directly, it works fine:
impl State {
    fn print(&self) {
        use chrono::TimeZone;
        let dt = chrono::Utc
            .ymd_opt(self.year, self.month, self.day)
            .and_hms_opt(self.h, self.m, self.s)
            .map(|dt| dt + chrono::Duration::seconds(self.tz_offset as i64))
            .single();

        info!(
            "FIX: {} | SVs: {} | HDOP: {} | {}",
            self.fix,
            self.svs,
            self.hdop,
            match dt {
                Some(s) => s.to_string(),
                None => "INVALID".to_owned(),
            },
        );
    }
}

 INFO  FIX: 0 | SVs: 0 | HDOP: 0.0 | INVALID
└─ pico_clock::__cortex_m_rt_main @ src/main.rs:293
 INFO  FIX: 0 | SVs: 0 | HDOP: 0.0 | INVALID
└─ pico_clock::__cortex_m_rt_main @ src/main.rs:293

// ... and so on

I'm using defmt 0.2 with the alloc feature and defmt-rtt 0.2

Hello @devsnek,
Thank you for your report. What version of probe-run are you using?
And which exact version of defmt and defmt-rtt? You can check this in your Cargo.lock.

defmt is 0.2.3, defmt is 0.2.0. probe-run is from https://github.com/rp-rs/probe-run

Just for my understanding: Is your code no_std? Cause you are using .to_string.

Okay, I am able to reproduce it in no_std anyways.

my code is no_std but i have alloc enabled, which includes alloc::string::ToString

@japaric:

| is used in defmt internals for encoding enums; it shouldn't be used in user-facing write!
user-facing write! should reject format strings that contain | or kind of escape them so that the decoder doesn't interpret them as enums

Also we found that this issue was raised before: https://github.com/knurling-rs/defmt/issues/210

Rejecting | in write! calls is a lousy fix.
Since symbol names are JSON, why not encode whether an interned index is an enum or not using JSON? i.e instead of None|Some({}), store something like {"type": "enum", "variants": ["None", "Some({})"]}.

Rejecting | in write! calls is a lousy fix.
Since symbol names are JSON, why not encode whether an interned index is an enum or not using JSON? i.e instead of None|Some({}), store something like {"type": "enum", "variants": ["None", "Some({})"]}.

Interesting idea! Will look into that :)

alternative idea from @jonas-schievink : mark the defmt-internal Strings that use | as such [this marker already exists], only split on | if this marker is set. this way we wouldn't break the wire format (we wouldn't need to change the JSON string encoding).

fixed in #614