text:
[FEAT] Implement Email-Based Support Ticket Submission

Issue: Support Ticket Opened
Title
[FEAT]  Implement Email Confirmation for Support Ticket Submission (Opened)

Description
The feature allows users to open support tickets for technical issues, requests, or feedback via an email-based system. This includes a backend system to process emails, generate tickets, and a mechanism to track and manage the opened tickets.

Purpose
To streamline the process of users reporting issues or requests through email and ensure efficient handling and resolution of these support tickets by the support team.

Requirements

Email Interface:

Process incoming emails to create new support tickets.
Extract necessary details: Subject, Description, Priority, Category.
Handle attachments included in emails.

Backend:

API Endpoint:

POST  /v1/tickets/acknowledgement

Description: Endpoint to send an acknowledgement email to users when they submit a support ticket.

Request Body:
{
  "name": "string",
  "email": "string",
  "subject": "string",
  "description": "string",
  "priority": "enum (Low, Medium, High)",
  "category": "string",
  "attachment": "file (optional)"
}

Success Response:
{
  "message": "Acknowledgement email sent successfully"
}

Error Response:
{
  "error": "Failed to send acknowledgement email",
  "details": "Description of the error"
}

Database Schema:

Tickets Table:

ticketId (UUID, Primary Key)
name (String)
email (String)
subject (String)
description (Text)
priority (Enum: Low, Medium, High)
category (String)
attachment (String)
status (Enum: Open, In Progress, Closed)
createdAt (Timestamp)
updatedAt (Timestamp)

Notifications:

Email confirmation service to send a detailed confirmation email to the user upon successful ticket submission.
Email should include the ticket ID, subject, description, priority, category, and any attachments.

Expected Outcome

Users receive an email confirmation upon submitting a support ticket, including all details of the submitted ticket.

Checklist/Acceptance Criteria

API Endpoint Functionality:

[ ] API endpoint retrieves the correct ticket details for the email confirmation.
[ ] Proper error messages are returned if the ticket is not found.

Email Confirmation:

[ ] Users receive a detailed confirmation email upon ticket submission.
[ ] Email includes ticket ID, subject, description, priority, category, and any attachments.

Integration Testing:

[ ] End-to-end tests ensure the email confirmation process works from ticket submission to email receipt.
[ ] Data is correctly retrieved and emails are sent accurately.

We are not doing ticketing in this app

We are not doing ticketing in this app

It's been revised now, please take a look at it

Creating another ticket

authors: Oluwaseg markessien


text:
🛑 Laravel 10x on Render is down

In 6cd1c2e, Laravel 10x on Render (https://laravel-10x.onrender.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Laravel 10x on Render is back up in 81d5f89 after 8 minutes.

source: gharchive/issue

repo: hoangsvit/uptime

license: MIT

license_type: permissive

license_source: github-api


text:
Add divider

@startuml
== Initialization ==
Alice -> Bob: Authentication Request
Bob --> Alice: Authentication Response
== Repetition ==
Alice -> Bob: Another authentication Request
Alice <-- Bob: another authentication Response
@enduml

PR #30

repo: hokorobi/plantuml-syntax

license: Vim


text:
ShaderGlow broken on UE5.1+

When using the ShaderGlow version on  UE5.1 and above the MF_VertexGlow function appears to be broken. For a few reasons:

Input Rectangle need a bool connected to the Preview
The custom shader code with the comment Get HMD position, not eye position contains a few errors.

I've fixed the issues in here: https://github.com/hollowdilnik/GlowingQuad/pull/3

repo: hollowdilnik/GlowingQuad


text:
OpenAPI Tool fails to read certain OpenAPI specs.

Description
The OpenAPI tool doesn't always success in parsing an openapi spec (yaml).
Example spec that fails: https://api.drymergeqa.com/test-openapi
Steps to reproduce

Create an agent
Add a OpenAPI tool with the following schema: https://api.drymergeqa.com/test-openapi
Run the agent

Acknowledgements

[X] My issue title is concise, descriptive.
[X] I have searched the existing issues to make sure this bug has not been reported yet.
[X] I am using the latest version of superagent.
[X] I have provided enough information for the maintainers to reproduce and diagnose the issue.

@elisalimli would you mind having a look at this?
The issue currently is that some OpenAPI specs don't work with the LangChain openapi agent/chain. Perhaps there is a better way to do this. Please research and fix this isssue!

I think OpenAPI Tool's failing to read certain OpenAPI specs is an intended implementation by langchain. The current implementation can call the endpoints derived from the given openapi spec.
Closing this issue for now.

authors: elisalimli homanp

repo: homanp/superagent


text:
CodeNotary signature missing from most recent image

$ docker image ls
REPOSITORY                              TAG         IMAGE ID       CREATED        SIZE
homeassistant/home-assistant            stable      cceebd7b1c95   25 hours ago   1.17GB
ghcr.io/home-assistant/home-assistant   2021.12     cceebd7b1c95   25 hours ago   1.17GB
ghcr.io/home-assistant/home-assistant   2021.12.7   cceebd7b1c95   25 hours ago   1.17GB
ghcr.io/home-assistant/home-assistant   latest      cceebd7b1c95   25 hours ago   1.17GB
ghcr.io/home-assistant/home-assistant   stable      cceebd7b1c95   25 hours ago   1.17GB
ghcr.io/home-assistant/home-assistant   <none>      f7eb691068a1   26 hours ago   1.17GB
ghcr.io/home-assistant/home-assistant   2021.12.6   575a57d856f8   2 days ago     1.16GB

$ vcn authenticate --org home-assistant.io docker://ghcr.io/home-assistant/home-assistant:2021.12.6

Your assets will not be uploaded. They will be processed locally.

Looking for blockchain entry matching the organization (home-assistant.io)...

Name:           docker://homeassistant/aarch64-homeassistant:2021.12.6
Hash:           575a57d856f8f397c00a76ea0d5dbf1e7032ec72f32a5b5a5ba3877eceacead0
Visibility:     PUBLIC
Signer:         not***@hom***********.io
Company:        Home Assistant
SignerID:       0xc7ada38e353d48452d63a65c8c10a89e666e2d46
Level:          3 - ID_VERIFIED
Date:           2021-12-27T23:12:55Z
Status:         TRUSTED

$ vcn authenticate --org home-assistant.io docker://ghcr.io/home-assistant/home-assistant:2021.12.7

Your assets will not be uploaded. They will be processed locally.

Looking for blockchain entry matching the organization (home-assistant.io)...

Kind:           docker
Name:           docker://homeassistant/home-assistant:stable
Hash:           cceebd7b1c9533c31e2b477461800ca6b58bd79ae8cd0d625bf1c761d469df9e
Size:           1.2 GB
Metadata:       architecture="arm64"
                platform="linux"
                version="stable"
                docker={
                    "Id": "sha256:cceebd7b1c9533c31e2b477461800ca6b58bd79ae8cd0d625bf1c761d469df9e",
                    "RepoTags": [
                        "homeassistant/home-assistant:stable",
                        "ghcr.io/home-assistant/home-assistant:2021.12",
                        "ghcr.io/home-assistant/home-assistant:2021.12.7",
                        "ghcr.io/home-assistant/home-assistant:latest",
                        "ghcr.io/home-assistant/home-assistant:stable"
                    ],
                    "RepoDigests": [
                        "homeassistant/home-assistant@sha256:e516e3cc51c5b10d7a99b704dc806787ab0a173919ebcd7f574405e15a76bf40",
                        "ghcr.io/home-assistant/home-assistant@sha256:e516e3cc51c5b10d7a99b704dc806787ab0a173919ebcd7f574405e15a76bf40"
                    ],
                    "Comment": "",
                    "Created": "2021-12-29T19:52:12.075543888Z",
                    "DockerVersion": "20.10.11+azure-3",
                    "Author": "",
                    "Architecture": "arm64",
                    "Os": "linux",
                    "VirtualSize": 1165723398,
                    "Size": 1165723398,
                    "Metadata": {
                        "LastTagTime": "0001-01-01T00:00:00Z"
                    }
                }
Status:         UNKNOWN
Error: cceebd7b1c9533c31e2b477461800ca6b58bd79ae8cd0d625bf1c761d469df9e was not notarized by "home-assistant.io"

I guess this was a problem of me using an old tool (vcn)? Using cas instead, I get the expected "TRUSTED" output for both images:
$ cas authenticate --signerID notary@home-assistant.io docker://ghcr.io/home-assistant/home-assistant:2021.12.6
UID:            1640646766216506557
Kind:           docker
Name:           docker://homeassistant/aarch64-homeassistant:2021.12.6
Hash:           575a57d856f8f397c00a76ea0d5dbf1e7032ec72f32a5b5a5ba3877eceacead0
Size:           1.2 GB
Timestamp:      2021-12-27 23:12:46.216506557 +0000 UTC
Metadata:       GITHUB_ACTION="__home-assistant_builder"
                GITHUB_JOB="build_base"
                GITHUB_REPOSITORY="home-assistant/core"
                docker={
                    "Architecture": "arm64",
                    "Author": "",
                    "Comment": "",
                    "Created": "2021-12-27T23:12:45.021304376Z",
                    "DockerVersion": "20.10.11+azure-3",
                    "Id": "sha256:575a57d856f8f397c00a76ea0d5dbf1e7032ec72f32a5b5a5ba3877eceacead0",
                    "Metadata": {
                        "LastTagTime": "2021-12-27T23:12:45.754153464Z"
                    },
                    "Os": "linux",
                    "RepoDigests": [],
                    "RepoTags": [
                        "homeassistant/aarch64-homeassistant:2021.12.6",
                        "homeassistant/aarch64-homeassistant:latest",
                        "ghcr.io/home-assistant/aarch64-homeassistant:2021.12.6",
                        "ghcr.io/home-assistant/aarch64-homeassistant:latest"
                    ],
                    "Size": 1164687749,
                    "VirtualSize": 1164687749
                }
                platform="linux"
                CI="true"
                GITHUB_EVENT_NAME="release"
                GITHUB_RUN_ID="1628487359"
                version="2021.12.6"
                CAS_CI_ENV="github"
                GITHUB_ACTIONS="true"
                GITHUB_ACTOR="frenck"
                GITHUB_GRAPHQL_URL="https://api.github.com/graphql"
                GITHUB_SERVER_URL="https://github.com"
                GITHUB_SHA="dfe193b2776f5ab915ea89ca2b88fca0b3a07f7b"
                GITHUB_WORKFLOW="Build images"
                GITHUB_API_URL="https://api.github.com"
                GITHUB_REF="refs/tags/2021.12.6"
                GITHUB_RUN_NUMBER="377"
                GITHUB_WORKSPACE="/home/runner/work/core/core"
                architecture="arm64"
SignerID:       bm90YXJ5QGhvbWUtYXNzaXN0YW50Lmlv
Apikey revoked: no
Status:         TRUSTED

$ cas authenticate --signerID notary@home-assistant.io docker://ghcr.io/home-assistant/home-assistant:2021.12.7
UID:            1640807533481637037
Kind:           docker
Name:           docker://homeassistant/aarch64-homeassistant:2021.12.7
Hash:           cceebd7b1c9533c31e2b477461800ca6b58bd79ae8cd0d625bf1c761d469df9e
Size:           1.2 GB
Timestamp:      2021-12-29 19:52:13.481637037 +0000 UTC
Metadata:       GITHUB_REF="refs/tags/2021.12.7"
                GITHUB_RUN_NUMBER="380"
                GITHUB_WORKFLOW="Build images"
                CAS_CI_ENV="github"
                CI="true"
                GITHUB_ACTION="__home-assistant_builder"
                GITHUB_ACTIONS="true"
                GITHUB_WORKSPACE="/home/runner/work/core/core"
                GITHUB_GRAPHQL_URL="https://api.github.com/graphql"
                GITHUB_RUN_ID="1634806915"
                GITHUB_SERVER_URL="https://github.com"
                GITHUB_SHA="92066d2a6272a29eb9ed1783800d686a99813934"
                docker={
                    "Architecture": "arm64",
                    "Author": "",
                    "Comment": "",
                    "Created": "2021-12-29T19:52:12.075543888Z",
                    "DockerVersion": "20.10.11+azure-3",
                    "Id": "sha256:cceebd7b1c9533c31e2b477461800ca6b58bd79ae8cd0d625bf1c761d469df9e",
                    "Metadata": {
                        "LastTagTime": "2021-12-29T19:52:12.91249457Z"
                    },
                    "Os": "linux",
                    "RepoDigests": [],
                    "RepoTags": [
                        "homeassistant/aarch64-homeassistant:2021.12.7",
                        "homeassistant/aarch64-homeassistant:latest",
                        "ghcr.io/home-assistant/aarch64-homeassistant:2021.12.7",
                        "ghcr.io/home-assistant/aarch64-homeassistant:latest"
                    ],
                    "Size": 1165697080,
                    "VirtualSize": 1165697080
                }
                GITHUB_ACTOR="frenck"
                GITHUB_API_URL="https://api.github.com"
                GITHUB_EVENT_NAME="release"
                version="2021.12.7"
                GITHUB_JOB="build_base"
                GITHUB_REPOSITORY="home-assistant/core"
                architecture="arm64"
                platform="linux"
SignerID:       bm90YXJ5QGhvbWUtYXNzaXN0YW50Lmlv
Apikey revoked: no
Status:         TRUSTED

Also, sorry for raising the issue in this repo instead of https://github.com/home-assistant/core/issues where it more likely belongs.

repo: home-assistant/builder


text:
Wildcard capitalization issues during recognition

Fixtures:
entities:
  - name: "Joseph"
    id: "person.jospeh"
    state: "home"
  - name: "Ada"
    id: "person.ada"
    state: "Work"
  - name: "John"
    id: "person.john"
    state: "not_home"

Sentences and tests:
lists:
  zone:
    wildcard: true
intents:
  HassGetState:
    data:
      - sentences:
          - "is anyone [<in>] [the] {zone:state}"
        response: any
        slots:
          domain: person
tests:
  - sentences:
      - "is anyone at Work"
    intent:
      name: HassGetState
      slots:
        domain: person
        state: Work
    response: "Yes, Ada"

produces
E                           AssertionError: Expected work, got Work for slot state for: is anyone at Work
E                           assert 'Work' == 'work'
E                             - work
E                             ? ^
E                             + Work
E                             ? ^

tests/test_language_sentences.py:143: AssertionError

I think this issue here might also be the reason why the shopping_list_item slot in the intents is always transformed to lowercase when matched.
I am sure there are use cases where ignoring upper-/lowercase make sense, but for some it produces problems (especially in other languages).
maybe this can be achieved with an optional config like preserve_case, defaulting to False?

although having a quick look at the code it doesn't seem straight forward, as casefold can change the length of the text and therefore the index of the wildcard match in the original text.

authors: super-qua tetele

repo: home-assistant/hassil


text:
Incorrect cert expiry date in DuckDNS addon

Home Assistant release (hass --version):
0.65.5
Python release (python3 --version):
The one supplied with Hassio.
Component/platform:
DuckDNS version 1.2
Description of problem:
DuckDNS Addon fails to recognize that cert for my domain is expiring in less than 30 days, hence it is not refreshing it.
This is log from DuckDNS on restart:
starting version 3.2.4
INFO: Using main config file /data/workdir/config
Account already registered!
Sun Mar 25 21:33:35 CEST 2018: OK
NOCHANGE # INFO: Using main config file /data/workdir/config Unknown hook this_hookscript_is_broken__dehydrated_is_working_fine__please_ignore_unknown_hooks_in_your_script Processing <domain>.duckdns.org Unknown hook this_hookscript_is_broken__dehydrated_is_working_fine__please_ignore_unknown_hooks_in_your_script + Checking domain name(s) of existing cert... unchanged. + Checking expire date of existing cert... + Valid till Jun 22 17:50:27 2018 GMT (Longer than 30 days). Skipping renew!

Config of DuckDNS:
{
"lets_encrypt": {
"accept_terms": true,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem"
},
"token": ,
"domains": [
  <domain>.duckdns.org"
],
"seconds": 60
}

The SSL sensor correctly reports 29 days till expiry:
sensor.ssl_certificate_expiry | 29 | unit_of_measurement: days friendly_name: Dostęp SSL icon: mdi:certificate
-- | -- | --

Chrome (correctly) says that the cert for the UI (opened on the domain specified in the duckdns page) is valid till 2018-04-23.
Expected:
DuckDNS should referesh the cert since there are less than 30 days till expiry.

I don't think this got fixed with the associated PR. I've updated to 1.3 DuckDNS and the addon still refuses to update cert due to incorrect expiry date considered.

@rsokolowski reboot home-assistant to load the new certs

authors: pvizeli rsokolowski

repo: home-assistant/hassio-addons


text:
Move to proper logging library

https://github.com/dmuth/google-go-log4go

Logrus would be a better option for this:
https://github.com/sirupsen/logrus

Closing this one in favor of creating a more extensive one.

repo: home-assistant/hassio-cli


text:
zoneminder fails to init on 0.68

Home Assistant release with the issue:
0.68

Last working Home Assistant release (if known):
0.67
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
zoneminder
Description of problem:
Doesn't startup since upgrade
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
zoneminder:
  host: zoneminderhost
  username: !secret zoneminder_username
  password: !secret zoneminder_password

Traceback (if applicable):
2018-04-28 12:24:51 ERROR (SyncWorker_1) [homeassistant.components.zoneminder] Connection error logging into ZoneMinder
2018-04-28 12:24:51 ERROR (MainThread) [homeassistant.setup] Setup failed for zoneminder: Component failed to initialize.
2018-04-28 12:24:51 ERROR (MainThread) [homeassistant.setup] Unable to setup dependencies of switch.zoneminder. Setup failed for dependencies: zoneminder
2018-04-28 12:24:51 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform switch.zoneminder: Could not setup all dependencies.

Additional information:

I have zoneminder as well.  My install method is a virtual environment.  I am also using the switch component of zoneminder and I do not have this issue when I updated to 0.68
Here is my config.yaml for the switch component which is what this error is about:
 - platform: zoneminder
   command_on: Record
   command_off: None

@nic0dk what about your install method?  is it docker too?
also for the devs my version of ZM is: 1.30.4

mine is s docker version too, from linuxserver.io
https://hub.docker.com/r/linuxserver/zoneminder/
with docker-compose:
https://forums.zoneminder.com/viewtopic.php?t=26596

I've got zoneminder on a VM... haven't updated or otherwise touched it in a few months. I'm pretty confident the change is on the HA side.

FWIW, it's working fine for me still on 0.68 and 0.69 using hass.io.

@mnoorenberghe what version of zm ? Gonna check the api for zm, when I get home

authors: dshokouhi mnoorenberghe nic0dk raccettura

repo: home-assistant/home-assistant


text:
Icon in Picture-Glace that wont be colored

Down on my google drive ive shared my cards that ive setup with Picture-elements and picture-glace
On Picture-Elements my theme works perfekt and colors the icons when aktive blue as they should.
On the other its just white. Ive search around but not seen anyone mentioning a fix for this. But i mean aint this just a theme item to add to the theme? or am i thinking wrong some how?
Picture below.
https://drive.google.com/file/d/1_44la6pkVx8NRn4NXASDB9QcB6XBckZP/view?usp=sharing 51

/move to home-assistant-polymer

authors: askusbloodfist cgarwood


text:
Counter is broken

HA 0.94.1
Component/platform:
Counter
Description of problem:
The defaults (0 & 1) of the initial and step are not observed, and are null.

This breaks the increment service:
unsupported operand type(s) for +: 'NoneType' and 'NoneType'
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/components/websocket_api/commands.py", line 121, in handle_call_service
    connection.context(msg))
  File "/usr/src/app/homeassistant/core.py", line 1150, in async_call
    self._execute_service(handler, service_call))
  File "/usr/src/app/homeassistant/core.py", line 1172, in _execute_service
    await handler.func(service_call)
  File "/usr/src/app/homeassistant/helpers/entity_component.py", line 194, in handle_service
    required_features
  File "/usr/src/app/homeassistant/helpers/service.py", line 316, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/app/homeassistant/helpers/service.py", line 337, in _handle_service_platform_call
    await getattr(entity, func)(**data)
  File "/usr/src/app/homeassistant/components/counter/__init__.py", line 179, in async_increment
    self._state = self.compute_next_state(self._state + self._step)
TypeError: unsupported operand type(s) for +: 'NoneType' and 'NoneType'

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
counter:
  person_counter:

Looks like that we are mixing types.

authors: fabaff robmarkcole


text:
Load as many components in parallel as possible

Description:
Resolve all dependencies of all components when processing a config. That way we can adhere to FIRST_INIT_COMPONENT components. Before this fix, only explicitly mentioned components in the config would be initialized first.
Fix is needed to improve #20799
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

Good improvement

source: gharchive/pull-request

authors: balloob pvizeli


text:
Bug fix for #4903

Description:
Bug fix for #4903
I have not tested this code

@BruurTycho has tested and verified this bug fix

Nice 🐬

authors: Danielhiversen balloob


text:
Cleanup modes & available, bump version requirement

Description:
Bump the version requirement of the backend library, implementing manual mode properly.
This PR also removes UI clutter by not listing the useless modes.
Checklist:
If the code communicates with devices, web services, or third-party tools:

[X] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[X] New dependencies have been added to the REQUIREMENTS variable (example).
[X] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

Hi @rytilahti,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Hi @rytilahti,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

:zap:

authors: homeassistant pvizeli rytilahti


text:
Add HassRespond intent

Adds a new intent named HassRespond that simply returns the response and takes no action.
This intent is meant to hard-code responses to specific questions.
Core support PR: https://github.com/home-assistant/core/pull/129755

Summary by CodeRabbit
Release Notes

New Features

Introduced a new intent, HassRespond, allowing the Home Assistant to return responses without performing actions.
Added predefined responses for the HassRespond intent, enhancing user interaction with greetings and data handling information.
Implemented sentence patterns to recognize various user inquiries related to the assistant's capabilities and origin.

Tests

Added test cases to ensure the HassRespond intent functions correctly, validating responses to user queries.

Dutch translations are pending in #2449. Will keep an eye on this PR for changes to the EN sentences.

Polish translations are also pending https://github.com/home-assistant/intents/pull/2450

Renamed the default response key to hello, and then merge :slightly_smiling_face:

Note: I am doubtful STTs will be able to transcribe "hello home assistant" most languages other than English

authors: TheFes synesthesiam tetele witold-gren

repo: home-assistant/intents


text:
Fix the double program name on the build commands

What does this PR do?
When generating the build commands for "dependency targets", since all was being done by the hooks of the projext CLI, the interface was instantiated, so the command already had the program name (cliName), and because the plugin was adding it, the commands ended with projext projext ....
This PR adds a check that verifies if the CLI is instantiated and if not, then it prepends the program name (obtained from the main CLI service) to the command.
How should it be tested manually?
yarn test
# or
npm test

Pull Request Test Coverage Report for Build 88

8 of 8 (100.0%) changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 84:
0.0%

Covered Lines:
287

Relevant Lines:
287

💛  - Coveralls


text:
Subdivision causes things to peel away from the boundary

Vertices on the boundary should never be allowed to move off the boundary during subdivision.
After Nathan's change 9798fe3, we can observe this in most examples.
We originally noticed this in issue #342: filename_todo.hom.zip

Here by "boundary" you mean the actual bounding box of the entire diagram, right?

Yes. We really need to find a better name for Akvile's "boundary" label.

authors: calintat jamievicary

repo: homotopy-io/homotopy-rs


text:
Vertical Pod Autoscaling for Refinery

So when I set up my Refinery clusters (8 environments, one per), I used the advice in the documentation to size my cache. I haven't re-sized my caches since.
I noticed (albeit much later) that my environment Refineries have drastically different cpu/memory profiles (not entirely unreasonable) but want to free myself from managing the resource requests (as I do of all things). As I have done for many other cases (especially for Go workloads), I looked into vertical pod autoscaling.
If you are unfamiliar with VPA, the premise is that a histogram of utilisation for both cpu/memory (8 days, iirc) is used to calculate recommendations, lower bounds and upper bounds for container resourcing requests; it also tracks for OOM killed events. It's possible to configure it so that the recommendations are applied during pod scheduling, or to automatically evict the workload to make a change (voluntary disruptions). I know that the Refinery docs recommend against downscaling the HPAs due to trace-loss, so that would have to be thought about if one were to use the Auto mode. The other mode is Off which only calculates recommendations which is good for reading from other tools.
It looks like if Refinery were to infer MaxAlloc from the container resource limit, and calculate CacheCapacity from that, when the resource request/limit is changed by e.g. VPA (or even manually), both the MaxAlloc and CacheCapacity would adjust themselves automatically. It's fairly straight forward to take this information from the cgroups, and you may already be doing so for GOMAXPROCS. I accept that it wouldn't be one-size-fits.
automaxprocs is also relevant in that it sets the number of max procs based on the CPU quota (which VPA would adjust).

Hi, @fujin. Apologies for the delay; we had a company offsite last week.
Your proposal is interesting. It's also a little tricky, requiring specific features of k8s (afaict). I gave it about an hour, but wasn't able to find a Go library that I thought would be a relatively easy drop-in. If you know of something, please let me know. It's not a must-have, but would make things easier.
In any case, given the sequence of things we're currently planning, this doesn't really fit in immediately, but I can see us getting to it sometime later in the spring.

authors: fujin kentquirk

repo: honeycombio/refinery


text:
Update deploy_app.sh

실습해보는 작업

문제없음

문제없어요

문제없음

repo: honganja/hashicat-aws


text:
Add unit tests for pkg/agent/openflow

Signed-off-by: Hongliang Liu lhongliang@vmware.com

Codecov Report

Merging #87 (892e1df) into main (8427b4a) will increase coverage by 24.17%.
The diff coverage is 79.72%.

Additional details and impacted files

@@             Coverage Diff             @@
##             main      #87       +/-   ##
===========================================
+ Coverage   34.61%   58.78%   +24.17%
===========================================
  Files         144      376      +232
  Lines       21800    55319    +33519
===========================================
+ Hits         7545    32522    +24977
- Misses      13602    20546     +6944
- Partials      653     2251     +1598

Flag
Coverage Δ

*Carryforward flag

integration-tests
34.61% <50.00%> (ø)

Carriedforward from 8427b4a

unit-tests
54.89% <75.71%> (?)

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files
Coverage Δ

pkg/agent/multicast/mcast_controller.go
46.19% <ø> (+46.19%)
:arrow_up:

pkg/agent/openflow/cookie/allocator.go
73.33% <ø> (+35.55%)
:arrow_up:

pkg/agent/openflow/pipeline.go
81.45% <33.33%> (+23.59%)
:arrow_up:

pkg/agent/openflow/client.go
78.18% <51.85%> (+37.47%)
:arrow_up:

pkg/agent/openflow/multicast.go
79.21% <100.00%> (+79.21%)
:arrow_up:

pkg/agent/openflow/pipeline_other.go
96.49% <100.00%> (+0.33%)
:arrow_up:

pkg/agent/openflow/pod_connectivity.go
96.29% <100.00%> (+1.91%)
:arrow_up:

pkg/ovs/openflow/ofctrl_bridge.go
73.80% <100.00%> (-2.66%)
:arrow_down:

pkg/controller/networkpolicy/mutate.go
0.00% <0.00%> (ø)

... and 339 more

authors: codecov-commenter hongliangl

repo: hongliangl/antrea


text:
删除headerView

建议添加 删除指定position或者view的 api功能，有时候添加多个header，操作时会选择删除部分

同问 。谁来解决下

authors: chenwulue songixan

repo: hongyangAndroid/baseAdapter


text:
上传文件时，文件名中包含有#号，则会报错！

以下是错误日志：
java.lang.StringIndexOutOfBoundsException: length=12; regionStart=9; regionLength=-4
at java.lang.String.startEndAndLength(String.java:588)
at java.lang.String.substring(String.java:1475)
at java.net.DefaultFileNameMap.getContentTypeFor(DefaultFileNameMap.java:38)
at com.zhy.http.okhttp.request.PostFormRequest.guessMimeType(PostFormRequest.java:89)
at com.zhy.http.okhttp.request.PostFormRequest.buildRequestBody(PostFormRequest.java:49)
at com.zhy.http.okhttp.request.OkHttpRequest.generateRequest(OkHttpRequest.java:68)
at com.zhy.http.okhttp.request.RequestCall.generateRequest(RequestCall.java:76)
at com.zhy.http.okhttp.request.RequestCall.buildCall(RequestCall.java:52)
at com.zhy.http.okhttp.request.RequestCall.execute(RequestCall.java:81)
解决办法如下：
private String guessMimeType(String path)
    {
        FileNameMap fileNameMap = URLConnection.getFileNameMap();
        String contentTypeFor = null;
        try {
            // 路径转义
            contentTypeFor = fileNameMap.getContentTypeFor(URLEncoder.encode(path, "UTF-8"));
        } catch (UnsupportedEncodingException e) {
            e.printStackTrace();
        }

        if (contentTypeFor == null)
        {
            contentTypeFor = "application/octet-stream";
        }
        return contentTypeFor;
    }

其他地方也检查下吧。如果问题修复了，请回复一下，想换成jar包。我现在使用你的源码解决问题，项目中不想包含这样的代码（我是临时接手项目修复这个紧急问题，所以浪费了很长时间）。另外把你源码的依赖在README中写一下吧，找依赖是很烦的，谢谢。

thx ~ 抱歉这么久回复，测试虽未发现该问题，不过转义一下可以使程序更加健壮，已经对外文件路径path进行了转义，稍后更新最新版本即可。

authors: hongyangAndroid jacpy

repo: hongyangAndroid/okhttp-utils

license_source: bigquery


text:
分享相关bug

分享文章之后，进行删除操作，然后再次分享相同内容，会提示该文章已经分享过了。{"data":null,"errorCode":-1,"errorMsg":"该文已经被分享过"}

https://www.wanandroid.com/lg/user_article/add/json
这个接口吗？
我试了下，没有复现，删除后可以正常分享。

repo: hongyangAndroid/wanandroid


text:
c.req.json() throwing an error when body is not available instead of null/undefined

What version of Hono are you using?
4.6.4
What runtime/platform is your app running on?
Cloudflare Workers
What steps can reproduce the bug?

Send a request with an empty body
Try to parse the body using c.req.json()

What is the expected behavior?
    const app = new Hono();

    app.post("/generate", async (c) => {
	const payload = await c.req.json(); // if empty return null/undefined

	const prompt = payload.prompt;

	if (!prompt) {
		c.status(400);
		return c.json({ error: "Prompt is required" });
	}

        // additional code
	return c.json({ result });
    });

What do you see instead?
    const app = new Hono();

    app.post("/generate", async (c) => {
	const payload = await c.req.json(); // throws error

	const prompt = payload.prompt;

	if (!prompt) {
		c.status(400);
		return c.json({ error: "Prompt is required" });
	}

        // additional code
	return c.json({ result });
    });

Additional information
First time using hono and I need this to be able to display proper error messages to the client

I followed this issue and it was closed saying this was fixed in v4.5.0 but I am still facing it

Hi @Judge-Paul
It's not Hono-side matter. It will fail to parse empty JSON in a Request even if you don't use Hono. Try to use the following. It will throw an error:
export default {
  fetch: async (req) => {
    const payload = await req.json()
    return new Response('Hi')
  },
} satisfies ExportedHandler

You're right, this code snippet produces the same result
Skill issue I guess, but is there any other way I can parse the body that'd allow me get this result, I am migrating my project from node/express and it works there

If you want to handle JSON parse error, try:
app.get('/generate', async c => {
  const text = await c.req.text()
  let json
  try {
    json = JSON.parse(text)
  } catch {
    return c.json({ error: 'invalid json' }, 400)
  }

  const prompt = payload.prompt
  if (!prompt) {
    return c.json({ error: 'Prompt is required' }, 400)
  }
  // ....

  return c.json({ result })
})

@nakasyou Thanks for this

authors: Judge-Paul nakasyou yusukebe

repo: honojs/hono


text:
docs: change to shell highlight

hightlight for shell code
cd /hono

What about using console.

cd /a
bun install

cd /a
bun install

nice suggestion!

Astro is using ````bash` (as shell).
what do you think? @yusukebe

@EdamAme-x
Ahh, console is not good. Then, I also bash is better.

ok. I ready to be

authors: EdamAme-x yusukebe


text:
Fixed "Missing Buffer type in the parameter of c.body"

Updated the "Date" type definitions in src/context.ts to include Buffer.
This fixes issues such as the following here
The author should do the following, if applicable

[ ] Add tests
[x] Run tests
[x] bun run format:fix && bun run lint:fix to format the code
[ ] Add TSDoc/JSDoc to document the code

Some runtimes appear to fail because there is no built-in type called Buffer.

There may be historical reasons for this, but considering the current Hono, it might be better to simply use BodyInit.
diff --git a/src/context.ts b/src/context.ts
index 86124e00..10dea474 100644
--- a/src/context.ts
+++ b/src/context.ts
@@ -27,9 +27,9 @@ type HeaderRecord =
   | Record<string, string | string[]>

 /**
- * Data type can be a string, ArrayBuffer, or ReadableStream.
+ * Data type can be a string, ArrayBuffer, ReadableStream, or any type accepted by the Response constructor.
  */
-export type Data = string | ArrayBuffer | ReadableStream
+export type Data = BodyInit

 /**
  * Interface for the execution context in a web worker or similar environment.

For reference, the following is the expanded BodyInit type.
https://www.typescriptlang.org/play/?#code/C4TwDgpgBA+gQgewCYgJIDsCWwoF4oBKEAhksQEYA2EAysAE4kC2UAPlAM4OboDmbUOJQTkBcAK4AzSRHo0E4+gGNo7AGIJ6TACLFgxAQFUCAGRollACwAKxesSYcgA

I saw a couple issues in the past on this issue, not that many people use BodyInit and this is more useful for some people.

According to a recent issue about this this has solved it for them.

If you write the test for this PR, the current main should fail. So the following change is needed:
diff --git a/package.json b/package.json
index 669c2027..dc8ac997 100644
--- a/package.json
+++ b/package.json
@@ -630,7 +630,7 @@
     "@hono/node-server": "^1.13.5",
     "@types/glob": "^8.1.0",
     "@types/jsdom": "^21.1.7",
-    "@types/node": "20.11.4",
+    "@types/node": "^22.10.1",
     "@types/supertest": "^2.0.16",
     "@vitest/coverage-v8": "^2.0.5",
     "arg": "^5.0.2",
@@ -644,7 +644,7 @@
     "prettier": "^2.6.2",
     "publint": "^0.1.16",
     "supertest": "^6.3.4",
-    "typescript": "^5.3.3",
+    "typescript": "^5.7.2",
     "vite-plugin-fastly-js-compute": "^0.4.2",
     "vitest": "^2.0.5",
     "wrangler": "3.58.0",
diff --git a/tsconfig.json b/tsconfig.json
index a580d709..ba3eba46 100644
--- a/tsconfig.json
+++ b/tsconfig.json
@@ -1,6 +1,9 @@
 {
   "compilerOptions": {
-    "target": "ES2022",
+    "target": "ES2024",
+    "lib": [
+      "ES2024"
+    ],
     "declaration": true,
     "moduleResolution": "Bundler",
     "outDir": "./dist",
@@ -25,4 +28,4 @@
     "src/**/*.test.ts",
     "src/**/*.test.tsx"
   ],
-}
+}
\ No newline at end of file

With this change, the test actually fails, and it's okay. But to resolve that, we have to fix the many things not only this c.body matter:

So, I think this is not an easy thing.

I ran a test with the newest commit I just pushed, By switching Buffer to Uint8Array it solved all Deno issues and runtime issues in general. It also solves this issue ( tested for myself )

Can this be reviewed? @usualoma @yusukebe

authors: EdamAme-x itztiva usualoma yusukebe


text:
Standardize PouchDB error handling

As discussed in the (hidden) comments of PR #137 we should standardize the way we check for errors thrown by PouchDB.
Sometimes we compare the error.name and sometimes error.status. While comparing against the actual error object thrown by PouchDB might be the most descriptive option, this creates a dependency (on PouchDB) that we don't want to add to this project. It seems comparing by status code is the most robust and feasible (and therefore best!) option.
TODO: refactor error handling to compare against status code when possible (avoiding error.name).

+1 for comparing with Status code. Thanks Cody

This was resolved when #148 was merged.

repo: hoodiehq/hoodie-account-server


text:
docs(LICENSE): unify license accross all active repositories

This PR aims to unify the licenses accross all active repositories
It

adds a License section to the end of the README.md
updates the package.json to include the correct license and author properties
adds a small boilerplate LICENSE file

This PR is based on hoodie-client-store#77.

merged via 059d450, cheers :)

repo: hoodiehq/hoodie-server-task


text:
Upgrade to good@7

The upgrade to good 7 needs changes to the way we use good, see changelogs: https://github.com/hapijs/good/issues/467
I looked into it but couldn’t figure it out myself, would be nice if someone with more experience good have a glance at it. We only use it in one file: plugins/logger.js

for reference: https://github.com/hapijs/good/issues/467

@christophwitzko can you maybe have a look at this? I tried to migrate it but too much stuff changed and we seemed to have used some internal APIs and I have no idea how to migrate it :/

see https://github.com/hapijs/good/issues/500#issuecomment-226604443

closing in favor of https://github.com/hoodiehq/camp/issues/35

repo: hoodiehq/hoodie


text:
🛑 FWAw is down

In 7396eba, FWAw ($FWA_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FWAw is back up in 54a715d after 26 minutes.

repo: hoopybe/uptime


text:
🛑 FWAw is down

In dd497ba, FWAw ($FWA_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FWAw is back up in e4ee9e9 after 12 minutes.


text:
Is this still maintained?

If not ill make a repository and maintain this.

I hate to seen packages as cool as this one not get any attention.

github.com/demency/laravel-friendships for l6

Thanks for picking this project up.

authors: demency omatamix

repo: hootlex/laravel-friendships

license: mit


text:
[TypeError: Cannot read property 'apply' of null]

I get this error, with vscode-ghc-mod 0.2.6 and vscode 1.3.1.
I just open a file in vscode.

Please provide more details.
What were you doing when this happened? Hovering over a symbol to get type information? Trying to go to the symbol definition? What did the code look like? Do you have autosave on?
Also, try setting the log level to "log" (add "haskell.ghcMod.logLevel": "log" to your user or workspace settings in vs code) and open the develop console (ctrl+shift+i or use the command palette) and see if there are relevant logs there when you reproduce the error.

When I open a haskell source file in vs code, I will get outputs from 'ghc-mod server' : [TypeError: Cannot read property 'apply' of null] .  And I set the log level to "log", but got nothing in the develop console. If I open an empty file (such as A.hs) the error is still there.

Was it working for you before and then did it stop working when you upgraded to VS Code 1.3.1?

no, on the vs code 1.1.1, there was the same error.

You have ghc-mod installed and in your path? My version is 5.5.0
And no logs like the ones here? If it isn't triggering any logs, it is happening very early.

My code doesn't ever call "apply" so it is happening in some dependency and without logs I can't figure out where that might be.
If you want, you can clone this repo to debug it yourself and help me track down the issue. It's a fairly easy process:
git clone https://github.com/hoovercj/vscode-ghc-mod.git
cd vscode-ghc-mod
npm install
code client
code server

Then in the client window you press f5 to launch the extension (the launched window will be titled EXTENSION HOST) and in the server window you press f5 to attach to the client process. Then in the extension host you can open a haskell file and see if you get the error. If you do, look back in the debug console of the other windows to see if there is good information.

My ghc-mod's version is 5.5.0.0 and it's compiled with ghc7.10.3 , but the version of ghc in my Mac is 8.0.1. And I uninstalled ghc-7.10.3. I think that may be why it broke down.

I am closing the issue as it seems you have fixed it and/or it is an environment issue, not an issue with the extension.

Added information: the reported error TypeError: Cannot read property 'apply' of null was caused by me passing null as a callback when registering the extension as a hover and definition provider.
I was likely passing null because ghc-mod couldn't be started.
#46 no longer passes null and instead handles the ghc-mod check in the callbacks, so this should not pollute the logs and should make finding the real issue for users much easier.

authors: Qinka hoovercj

repo: hoovercj/vscode-ghc-mod


text:
🛑 De'Longhi PH is down

In b87aab9, De'Longhi PH (https://delonghi.ph/) was down:

HTTP code: 500
Response time: 9761 ms

Resolved: De'Longhi PH is back up in c26b360 after 8 minutes.

repo: hophuochoanggia/upptime


text:
[HOPS-1311]  Adapt service JWT renewer to new protocol

[HOPS-1311]  Make paths configurable
Make sure there is no duplicate PR for this issue

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added and passed (for bug fixes / features)
[ ] HOPS JIRA issue has been opened for this PR
[ ] All commits have been squashed down to a single commit
[ ] The commit message has the following format: [HOPS-XXX] message

Post a link to the associated JIRA issue
https://hopshadoop.atlassian.net/browse/HOPS-1311

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Improvement

What is the new behavior (if this is a feature change)?
Keep compliant with Hopsworks protocol for updating service JWTs

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
When Hops TLS is enabled or when Yarn is configured to manage applications' JWT, Hops won't be compatible with older versions of Hopsworks

Other information:

breaking TestYarnConfigurationFields

Can you also check TestYarnStartupWithCRL

authors: berthoug kouzant

repo: hopshadoop/hops


text:
ENGESC-13270: Fixed sorting of SDX events which was causing some events to not appear when more than default page size.

Jira: https://jira.cloudera.com/browse/ENGESC-13270
To summarize: SDX events are retrieved from both the SDX service and the CB service, with the final events being combined, sorted, and trimmed down to the desired amount.
Customer had more events than the default of 100, causing the incorrect sorting to not show the expected latest events, as well as some events to be completely omitted since the events come from two different services.
By sorting in the right order this is fixed.
Tested this myself locally, verifying that the issue was present originally, but not present after.

Please let me know if any of you think we should shoot for this in 2.54.0. I ask since the customer facing this issue will not see this fix until 2.55.0 hits prod.
I don't know the proper protocol when something like this happens.

repo: hortonworks/cloudbreak


text:
CB-2681-CB-2682 Configure Providers for Schema Registry and SMM

Configure Providers for Schema Registry Server and Streams Messaging Manager.

Configure RDS Providers for Schema Registry Server and SMM.
Configure Local CM Admin and Password for SMM

Closes #CB-2681
Closes #CB-2682

@smaniraju can you please add the necessary changes to SupportedDatabaseProvider.java ?

authors: doktoric smaniraju


text:
CB-4167 Enable Nginx websockets proxying for Knox/Zeppelin

Add config for Nginx to enable websockets when proxying Knox/Zeppelin

Thanks @risdenk !

authors: biharitomi risdenk


text:
Remove checked_value and uncheck_value from input with as: :boolean

J'ai retiré les champs checked_value et uncheck_value des simple_form input qui avait le type as: :boolean, car lorsque le formulaire d'édition est submit, et que la checkbox vaut false, l'information n'est pas envoyé dans les params et du coup le champ n'est pas mis à jour, alors qu'en retirant ces deux élements, le as: :boolean met lui même "0" et "1" comme string, qui eux sont correctement transmis aux params, et correctement auto interprété par Rails comme true/false.
J'en ai profité pour le faire pour le formulaire concernant les checkbox :toc, et :statement.

Je pense que c'est bon pour merger sans attendre la review de @mininao, j'espère que ça vous ira 😄

Pour la quality gate je considère que c'est bon, le code n'ajoute pas de duplication, elle était pré-existante
Pour les tests, les checks ne passent pas sur github mais j'ai lancé les specs chez moi et c'est bon

authors: navidemad rchampourlier

repo: hostolab/covidliste


text:
Support for multiple PO's(#85zrh08cn)

Related Issues

Closes #
Short Description and Why It's Useful

Screenshots of Visual Changes before/after (If There Are Any)

IMPORTANT NOTICE - Remember to add changelog entry
Contribution and Currently Important Rules Acceptance

[ ] I read and followed contribution rules

Verified workflow. Looks good to me.
Please add Screenshot of UI changes happened with this PR & add little description what you did.

repo: hotwax/import


text:
Add pause until morning (squashed commits from add-pause-until-morning branch)

(copy of git diff from https://github.com/hovancik/stretchly/pull/262, which had corrupted commit history)

allow users to pause until specified morningHour
allow to pause until sunrise (morningHour = sunrise and posLatitude and posLongitude have to be specified)

Issue: #243
Requirements

[x]  issue was opened to discuss proposed changes before starting implementation.
[x]  during development, node version specified in package.json was used.
[x]  package versions were not changed.
[x]  app version number was not changed.
[x]  all new code has tests to ensure against regressions. (cannot really test UI stuff)
[x]  npm run lint reports no offenses. (only irrelevant)
[x]  npm run test is error-free. (only irrelevant)
[x]  README and CHANGELOG were updated accordingly.

Changelog updated, not really sure what to put in Readme.
Description of the Change
Allows users to pause until specified morningHour in settings or until 'sunrise' which is calculated based on location provided by user.
Verification Process
Only tested manually that it correctly sets pause time
Other
It depends on #260 for correctness because this pause will be reset upon system suspend with current behavior.

@lundibundi and @hovancik sorry to make a new PR -- history was too corrupt when we tried to hard reset and rebase against the upstream/master. This is now cleaned up and has the most original pause-until-morning functionality.

repo: hovancik/stretchly


text:
Question about intermediate states

Hi,
I was considering cases like upload of large files, that might take some time.
Do you know how cl-fsevent reacts to such cases? Does it trigger the event as soon as the file is created  or only when the file is closed.
The underlying fsevent theoretically allows to specify a delay for receiving the events, but this feature does not seem to be available in cl-fsevent. Is there any reason for that?
Thank you for your nice work anyway.

You should get the event as soon as the file is created. And get WRITE events as the file is modified.
Also, this does not use the fsevents, it uses kqueue. It uses kqueue because it's on FreeBSD.
There is probably some extra functionality the OS has but is not used. This is because when I wrote this i wanted the events to "look the same" regardless of what OS I was running.

authors: aslodzian howeyc

repo: howeyc/cl-fsnotify

license: isc


text:
[Feat/#86] 페이지네이션 구현

💡 개요
closed #42
closed #84
closed #86

무한 스크롤을 구현해보자
컨텐츠 중앙 정렬이 생각보다 간단해서.. 한 커밋으로 처리해부렸어
로딩 스피너도 갑자기 생각나서.. PR 나누기 귀찮아서 여기에 넣어부렸어
무한 스크롤 빼고 다 했다고 한다..

📋 진행상황

[ ] 무한 스크롤
[x] 로딩 스피너 -> 기껏 만들었는데 효과가 없었다고 한다.. 뺐다
[x] 컨텐츠 중앙 정렬
[x] 커뮤니티 페이지 레이아웃 다시
[x] 페이지네이션

🖼 스크린샷
중앙 정렬

커뮤니티 페이지

페이지네이션

뚝딱 하니까 구현 돼버렸네,, 😗

🗨 의견

프로필이랑 영화 페이지 빼고 영화 추천 다 넣어서 통일감이 생겼어 (너비도 오밀조밀해서 이뻐진 것)

이런이런,, 미안합니다
제가 무한 스크롤을 안했다고 3초 전에 말씀 드렸는데 잊어버리셨ㄱ군요

오늘 우리 엄청 열심히 했어 짱짱

repo: hoxies/foxie


text:
Add support for MDB_VL32

If MDB_VL32 is defined, 32bit lmdb lib can handle a db made by 64bit lmdb lib.
In this case, mdb_size_t is not the same as std::size_t.
One possible modification to handle the situation, add lmdb::size_t like as
 namespace lmdb {
   using mode = mdb_mode_t;
   using size_t = mdb_size_t;
 }

then replace std::size_t with lmdb::size_t in places related with
mdb_env_set_mapsize(), mdb_txn_id() and mdb_cursor_count().
This situation may be not so often, however, I think this modification should not be harmful for other situations, mdb_size_t = size_t.
If this modification is acceptable for you, I will make a pull request in that way.
What do you think?

Hi, very sorry I missed this issue, I had some difficult circumstances and wasn't following up on github issues.
Yes, I think this is a good idea to support this, and your proposed change doesn't sound too intrusive.

Thanks. I'll make a pull request.

I recognized MDB_VL32 feature has not been officially released yet.
So, offical releases do not have mdb_size_t.
We can, maybe, employ some metaprogramming technique to detect if the type is defined or not, but using a preprocessor is simple and enough, isn't it?
namespace lmdb {
  using mode = mdb_mode_t;
#ifdef MDB_SIZE_MAX
  using size_t = mdb_size_t;
#else
  using size_t = std::size_t;
#endif
}

Yes I think that seems reasonable, ideally a comment explaining when we'd expect MDB_SIZE_MAX to be set.
BTW: Will you be testing this with the unreleased VL32 feature? Are you using it for anything now, or planning to?

I do use VL32 for enable copying database files created on Win64 PC to 32-bit ARM device. I can participate in testing modifications required, because I do modification of hoytech/lmdbxx myself anyway.

Sorry for the long hiatus.
My use case was solved by another measure, so there is less concern for this issue...
I made some work anyway; I created the PR.
@uaply
Could you check the https://github.com/hoytech/lmdbxx/pull/15 ?

authors: hoytech uaply yak1ex

repo: hoytech/lmdbxx

license: Unlicense


text:
[BUG]: assert grad_chunk.l2_norm is not None

Is there an existing issue for this bug?

[X] I have searched the existing issues

🐛 Describe the bug
Modify the code to adapt to qwen2vl(transformers.Qwen2VLForConditionalGeneration) and find that the loss can be calculated, but partial chunk :  grad_chunk.l2_norm is None.........(LLM is ok)

modified source code to print more information：

result:

Environment
No response

For this kind of issue, it makes more sense to share what modifications you made (since we don't maintain individual modifications).

modified s

I didn't modify the source code originally. The only place I modified was in the second picture, in order to print the error details.

Is there an existing issue for this bug?

[x]  I have searched the existing issues

🐛 Describe the bug
Modify the code to adapt to qwen2vl(transformers.Qwen2VLForConditionalGeneration) and find that the loss can be calculated, but partial chunk : grad_chunk.l2_norm is None.........(LLM is ok)
modified source code to print more information：  result:
Environment
No response

The third picture shows that loss can be printed

Seems that your code is not the newest version. Could you pull the newest main branch and try again?

Seems that your code is not the newest version. Could you pull the newest main branch and try again?

torch 2.4.0 + colossalai 0.4.5 : same error

This is a simple piece of code that will give the same error：
`
import torch
import torch.nn as nn
from transformers import GPT2LMHeadModel,GPT2Config
from transformers import Qwen2VLForConditionalGeneration, AutoTokenizer, AutoProcessor
from colossalai.nn.optimizer import HybridAdam
import colossalai
from colossalai.booster import Booster
from colossalai.lazy import LazyInitContext
from colossalai.booster.plugin import GeminiPlugin
import os
os.environ["RANK"] = "0"
os.environ["LOCAL_RANK"] = "0"
class GPTLMModel(nn.Module):
def init(self,
hidden_size=768,
num_layers=12,
num_attention_heads=12,
max_seq_len=1024,
vocab_size=50257,
checkpoint=False):
super().init()
self.checkpoint = checkpoint
self.model = GPT2LMHeadModel(
GPT2Config(n_embd=hidden_size,
n_layer=num_layers,
n_head=num_attention_heads,
n_positions=max_seq_len,
n_ctx=max_seq_len,
vocab_size=vocab_size))
if checkpoint:
self.model.gradient_checkpointing_enable()
def forward(self, input_ids, attention_mask):
return self.model(input_ids=input_ids, attention_mask=attention_mask, use_cache=not self.checkpoint)[0]
def gpt2_medium(checkpoint=False):
return GPTLMModel(hidden_size=1024, num_layers=24, num_attention_heads=16, checkpoint=checkpoint)
class GPTLMLoss(nn.Module):
def __init__(self):
    super().__init__()
    self.loss_fn = nn.CrossEntropyLoss()

def forward(self, logits, labels):
    shift_logits = logits[..., :-1, :].contiguous()
    shift_labels = labels[..., 1:].contiguous()
    return self.loss_fn(shift_logits.view(-1, shift_logits.size(-1)), shift_labels.view(-1))

def get_data(batch_size, seq_len, vocab_size):
input_ids = torch.randint(0, vocab_size, (batch_size, seq_len), device=torch.cuda.current_device())
attention_mask = torch.ones_like(input_ids)
return input_ids, attention_mask
def main():
# args = parse_args()
BATCH_SIZE = 8
SEQ_LEN = 1024
VOCAB_SIZE = 50257
NUM_STEPS = 10
colossalai.launch_from_torch()
# build GPT model
with LazyInitContext(default_device=torch.device('cuda')):
  # model = gpt2_medium(checkpoint=True)
  model = Qwen2VLForConditionalGeneration.from_pretrained("/data/liuxiaoyu/liuxiaoyu/models/Qwen2-VL-2B-Instruct", device_map="auto"
                                                          )
# build criterion
criterion = GPTLMLoss()
optimizer = HybridAdam(model.parameters(), lr=0.001)

torch.manual_seed(123)

# Gemini + ZeRO DP
plugin = GeminiPlugin(max_norm=1.0, initial_scale=2**5)
booster = Booster(plugin=plugin)
model, optimizer, criterion, _, _ = booster.boost(model, optimizer, criterion)

torch.cuda.synchronize()
model.train()
for n in range(NUM_STEPS):
    print(n)
    # we just use randomly generated data here
    input_ids, attn_mask = get_data(BATCH_SIZE, SEQ_LEN, VOCAB_SIZE)
    optimizer.zero_grad()
    outputs = model(input_ids, attn_mask)
    # print(outputs)
    loss = criterion(outputs.logits, input_ids)
    booster.backward(loss, optimizer)
    optimizer.step()

torch.cuda.synchronize()

if name =='main':
main()
`

This is a simple piece of code that will give the same error：
import torch
import torch.nn as nn
from transformers import GPT2LMHeadModel,GPT2Config
from transformers import Qwen2VLForConditionalGeneration, AutoTokenizer, AutoProcessor
from colossalai.nn.optimizer import HybridAdam
import colossalai
from colossalai.booster import Booster
from colossalai.lazy import LazyInitContext
from colossalai.booster.plugin import GeminiPlugin
class GPTLMLoss(nn.Module):
def __init__(self):
    super().__init__()
    self.loss_fn = nn.CrossEntropyLoss()

def forward(self, logits, labels):
    shift_logits = logits[..., :-1, :].contiguous()
    shift_labels = labels[..., 1:].contiguous()
    return self.loss_fn(shift_logits.view(-1, shift_logits.size(-1)), shift_labels.view(-1))

def get_data(batch_size, seq_len, vocab_size):
input_ids = torch.randint(0, vocab_size, (batch_size, seq_len), device=torch.cuda.current_device())
attention_mask = torch.ones_like(input_ids)
return input_ids, attention_mask
def main():
# args = parse_args()
BATCH_SIZE = 8
SEQ_LEN = 1024
VOCAB_SIZE = 50257
NUM_STEPS = 10
colossalai.launch_from_torch()
# build GPT model
with LazyInitContext(default_device=torch.device('cuda')):
  # model = gpt2_medium(checkpoint=True)
  model = Qwen2VLForConditionalGeneration.from_pretrained("/data/liuxiaoyu/liuxiaoyu/models/Qwen2-VL-2B-Instruct", device_map="auto"
                                                          )
# build criterion
criterion = GPTLMLoss()
optimizer = HybridAdam(model.parameters(), lr=0.001)

torch.manual_seed(123)

# Gemini + ZeRO DP
plugin = GeminiPlugin(max_norm=1.0, initial_scale=2**5)
booster = Booster(plugin=plugin)
model, optimizer, criterion, _, _ = booster.boost(model, optimizer, criterion)

torch.cuda.synchronize()
model.train()
for n in range(NUM_STEPS):
    print(n)
    # we just use randomly generated data here
    input_ids, attn_mask = get_data(BATCH_SIZE, SEQ_LEN, VOCAB_SIZE)
    optimizer.zero_grad()
    outputs = model(input_ids, attn_mask)
    # print(outputs)
    loss = criterion(outputs.logits, input_ids)
    booster.backward(loss, optimizer)
    optimizer.step()

torch.cuda.synchronize()

if name =='main':
main()

This is a simple piece of code that will give the same error：
```
import torch
import torch.nn as nn
from transformers import GPT2LMHeadModel,GPT2Config
from transformers import Qwen2VLForConditionalGeneration, AutoTokenizer, AutoProcessor

from colossalai.nn.optimizer import HybridAdam
import colossalai
from colossalai.booster import Booster
from colossalai.lazy import LazyInitContext
from colossalai.booster.plugin import GeminiPlugin
import os
# os.environ["RANK"] = "0"
# os.environ["LOCAL_RANK"] = "0"

# class GPTLMModel(nn.Module):

#     def __init__(self,
#                  hidden_size=768,
#                  num_layers=12,
#                  num_attention_heads=12,
#                  max_seq_len=1024,
#                  vocab_size=50257,
#                  checkpoint=False):
#         super().__init__()
#         self.checkpoint = checkpoint
#         self.model = GPT2LMHeadModel(
#             GPT2Config(n_embd=hidden_size,
#                        n_layer=num_layers,
#                        n_head=num_attention_heads,
#                        n_positions=max_seq_len,
#                        n_ctx=max_seq_len,
#                        vocab_size=vocab_size))
#         if checkpoint:
#             self.model.gradient_checkpointing_enable()

#     def forward(self, input_ids, attention_mask):
#         return self.model(input_ids=input_ids, attention_mask=attention_mask, use_cache=not self.checkpoint)[0]

# def gpt2_medium(checkpoint=False):
#     return GPTLMModel(hidden_size=1024, num_layers=24, num_attention_heads=16, checkpoint=checkpoint)

class GPTLMLoss(nn.Module):

    def __init__(self):
        super().__init__()
        self.loss_fn = nn.CrossEntropyLoss()

    def forward(self, logits, labels):
        shift_logits = logits[..., :-1, :].contiguous()
        shift_labels = labels[..., 1:].contiguous()
        return self.loss_fn(shift_logits.view(-1, shift_logits.size(-1)), shift_labels.view(-1))

def get_data(batch_size, seq_len, vocab_size):
    input_ids = torch.randint(0, vocab_size, (batch_size, seq_len), device=torch.cuda.current_device())
    attention_mask = torch.ones_like(input_ids)
    return input_ids, attention_mask

def main():
    # args = parse_args()
    BATCH_SIZE = 8
    SEQ_LEN = 1024
    VOCAB_SIZE = 50257
    NUM_STEPS = 10
    colossalai.launch_from_torch()

    # build GPT model
    with LazyInitContext(default_device=torch.device('cuda')):
      # model = gpt2_medium(checkpoint=True)
      model = Qwen2VLForConditionalGeneration.from_pretrained("/data/liuxiaoyu/liuxiaoyu/models/Qwen2-VL-2B-Instruct", device_map="auto"
                                                              )
    # build criterion
    criterion = GPTLMLoss()
    optimizer = HybridAdam(model.parameters(), lr=0.001)

    torch.manual_seed(123)

    # Gemini + ZeRO DP
    plugin = GeminiPlugin(max_norm=1.0, initial_scale=2**5)
    booster = Booster(plugin=plugin)
    model, optimizer, criterion, _, _ = booster.boost(model, optimizer, criterion)

    torch.cuda.synchronize()
    model.train()
    for n in range(NUM_STEPS):
        print(n)
        # we just use randomly generated data here
        input_ids, attn_mask = get_data(BATCH_SIZE, SEQ_LEN, VOCAB_SIZE)
        optimizer.zero_grad()
        outputs = model(input_ids, attn_mask)
        # print(outputs)
        loss = criterion(outputs.logits, input_ids)
        booster.backward(loss, optimizer)
        optimizer.step()

    torch.cuda.synchronize()

if __name__ =='__main__':
    main()
```

@wangbluo @gothicx

@botbw Any insights? Thanks

@botbw Any insights? Thanks
It was my mistake. The “Qwen2VLForConditionalGeneration” model input requires complete input of "input_ids", "attention_mask", "pixel_values", and "image_grid_thw". Although it can run only with "input_ids" and "attention_mask", the above will appear. The error I mentioned

repo: hpcaitech/ColossalAI


text:
Add betas

closes #39
WIP need to check if working

Add specific check for not allowing zero

repo: hpi-epic/manm-cs


text:
folderNameOfTrash should consider hierarchical trash

If the trash folder is placed in a hierachy, the upmost directory will be set as folderNameOfTrash effectively making it the Trash. This is caused in folderFromResponse

In ICEndpoint>>folderFromResponse: the folder name for Trash is always the first member of the folderPath array.
If we have a trash folder below Inbox called Inbox.Trash e.g., currently we only take the first member Inbox.
See this loc:
(responseLine includesSubstring: '\Trash') ifTrue: [self folderNameOfTrash: folderPath first].
The idea of simply using ICEndpointFolder>>folderPath which holds Inbox.Trash in the example did not work, because on many sites we get protocol errors. It seems to be more complicated than that.

authors: Veladus Zumarta

repo: hpi-swa-teaching/IMAPClient


text:
Feature/apmw 196 add coordinates to room

closes #196

Can the Locateable module be applied here, too (https://github.com/hpi-swt2/compass-portal-blue/pull/147) ?
@joh-dah @Max784

Can the Locateable module be applied here, too (#147) ? @joh-dah @Max784

Yes, I think it should be included in the room model. Simply adding include Locatable should do it and fix the currently missing verifications.

authors: Max784 Tratori taminob


text:
plan and discuss asset export capabilities

This issue should be used to gather information on what asset formats will be used and which rendering techniques will be targeted. This work is required to be synced with openll on a regular basis.

For now we should assume the following renderers:

bitmap based font rendering
distance-map based font rendering
vector-map based font rendering

I suggest to start and extend the bitmap font format as presented in the angelcode bmfont project.

check out littera as good reference - please note that this requires a flash player and should be executed only in a save/sandbox environment.

repo: hpicgs/openll-asset-generator


text:
Publish package to GitHub Packages

I'd like to use this package (@hrbrain/eslint-plugin) and private package (@hrbrain/xxx) hosted by GitHub Packages.
As of now, I think we can't fetch packages with the same scope name from different repositories.
So I try to publish this package to GitHub Packages to resolve this issue.

Thank you for your quick review.
Could you merge this PR?
I can't merge this PR.

repo: hrbrain/eslint-plugin


text:
Linear Regression chapter Feedback

Feedback for the Linear Regression chapter

Some planned improvements:

[ ] Add section on interpreting coefficients, especially when multiple features are present.
[ ] Change picture of many dimensions to not be on sidebar since it's weird that it's small
[ ] Add ML pipeline images and highlight them.
[ ] Add code example for multiple/polynomial regression
[ ] Add note about gradient descent to solve versus Ordinary Least Squres

Some planned improvements:

[ ] Add section on interpreting coefficients, especially when multiple features are present.
[ ] Change picture of many dimensions to not be on sidebar since it's weird that it's small
[ ] Add ML pipeline images and highlight them.
[ ] Add code example for multiple/polynomial regression
[ ] Add note about gradient descent to solve versus Ordinary Least Squres

Some planned improvements:

[ ] Add section on interpreting coefficients, especially when multiple features are present.
[ ] Change picture of many dimensions to not be on sidebar since it's weird that it's small
[ ] Add ML pipeline images and highlight them.
[ ] Add code example for multiple/polynomial regression
[ ] Add note about gradient descent to solve versus Ordinary Least Squres

repo: hschafer/Intro-ML


text:
Data restructure: Track groups don't keep counting up from the end of the previous track group

You can see this on the album homepage and in the sidebar on any album or track page (with multiple track groups).
(26 Feb 2022)

Fixed in c5b42b7883025bb3464b52248567133cd0658959! (06 Mar 2022)

repo: hsmusic/hsmusic-wiki


text:
Add missing options

Add missing plugin options to TS declaration file.

Hi @francisdaigle
Thank you for the PR!
I just wonder that why you did some changes in index.test-d.ts?

Hi @hsynlms
The missing options were added were added to the TSD test as well.

I mean lines 32 and 33 change nothing indeed. Also, role, scope, and user properties assignments (lines 17, 18, 19) are useless unless there is no user object within Fastify request.

I mean lines 32 and 33 change nothing indeed.

Just being more explicit.

Also, role, scope, and user properties assignments (lines 17, 18, 19) are useless unless there is no user object within Fastify request.

Hmmm... to my knowledge, this is the standard way of going about things. I believe the point is to register the plugin and test that it compiles. Here's an example.

Thank you @francisdaigle

authors: francisdaigle hsynlms

repo: hsynlms/fastify-guard


text:
NullPointerException

I just opened .gitignore file and this exception was thrown. The file had empty lines and comments.
/storage/*.key
/.idea
/.vagrant
.env
# IDE Helper files
.phpstorm.meta.php

yarn-error.log

Here's a stacktrace
java.lang.NullPointerException
	at mobi.hsz.idea.gitignore.util.MatcherUtil.match(MatcherUtil.java:80)
	at mobi.hsz.idea.gitignore.util.Glob$1.visitFile(Glob.java:126)
	at com.intellij.openapi.vfs.VirtualFileVisitor.visitFileEx(VirtualFileVisitor.java:132)
	at com.intellij.openapi.vfs.VfsUtilCore.visitChildrenRecursively(VfsUtilCore.java:272)
	at com.intellij.openapi.vfs.VfsUtilCore.visitChildrenRecursively(VfsUtilCore.java:304)
	at com.intellij.openapi.vfs.VfsUtilCore.visitChildrenRecursively(VfsUtilCore.java:304)
	at com.intellij.openapi.vfs.VfsUtilCore.visitChildrenRecursively(VfsUtilCore.java:304)
	at com.intellij.openapi.vfs.VfsUtilCore.visitChildrenRecursively(VfsUtilCore.java:304)
	at com.intellij.openapi.vfs.VfsUtilCore.visitChildrenRecursively(VfsUtilCore.java:304)
	at com.intellij.openapi.vfs.VfsUtilCore.visitChildrenRecursively(VfsUtilCore.java:304)
	at mobi.hsz.idea.gitignore.util.Glob.find(Glob.java:140)
	at mobi.hsz.idea.gitignore.util.Glob.findAsPaths(Glob.java:158)
	at mobi.hsz.idea.gitignore.codeInspection.IgnoreCoverEntryInspection.getPathsSet(IgnoreCoverEntryInspection.java:220)
	at mobi.hsz.idea.gitignore.codeInspection.IgnoreCoverEntryInspection.checkFile(IgnoreCoverEntryInspection.java:147)
	at com.intellij.codeInspection.LocalInspectionTool$1.visitFile(LocalInspectionTool.java:156)
	at mobi.hsz.idea.gitignore.psi.IgnoreFile.accept(IgnoreFile.java:115)
	at com.intellij.codeInspection.InspectionEngine.acceptElements(InspectionEngine.java:82)
	at com.intellij.codeInspection.InspectionEngine.createVisitorAndAcceptElements(InspectionEngine.java:70)
	at com.intellij.codeInsight.daemon.impl.LocalInspectionsPass.a(LocalInspectionsPass.java:282)
	at com.intellij.codeInsight.daemon.impl.LocalInspectionsPass.a(LocalInspectionsPass.java:250)
	at com.intellij.concurrency.ApplierCompleter.d(ApplierCompleter.java:133)
	at com.intellij.openapi.application.impl.ApplicationImpl.tryRunReadAction(ApplicationImpl.java:1155)
	at com.intellij.concurrency.ApplierCompleter.a(ApplierCompleter.java:105)
	at com.intellij.openapi.progress.impl.CoreProgressManager.a(CoreProgressManager.java:548)
	at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:493)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:94)
	at com.intellij.concurrency.ApplierCompleter.b(ApplierCompleter.java:116)
	at com.intellij.concurrency.ApplierCompleter.a(ApplierCompleter.java:96)
	at com.intellij.openapi.application.impl.ReadMostlyRWLock.executeByImpatientReader(ReadMostlyRWLock.java:142)
	at com.intellij.openapi.application.impl.ApplicationImpl.executeByImpatientReader(ApplicationImpl.java:250)
	at com.intellij.concurrency.ApplierCompleter.compute(ApplierCompleter.java:96)
	at java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:731)
	at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
	at java.util.concurrent.ForkJoinPool$WorkQueue.pollAndExecCC(ForkJoinPool.java:1190)
	at java.util.concurrent.ForkJoinPool.helpComplete(ForkJoinPool.java:1879)
	at java.util.concurrent.ForkJoinPool.awaitJoin(ForkJoinPool.java:2045)
	at java.util.concurrent.ForkJoinTask.doJoin(ForkJoinTask.java:390)
	at java.util.concurrent.ForkJoinTask.join(ForkJoinTask.java:719)
	at java.util.concurrent.ForkJoinPool.invoke(ForkJoinPool.java:2616)
	at com.intellij.concurrency.JobLauncherImpl.invokeConcurrentlyUnderProgress(JobLauncherImpl.java:63)
	at com.intellij.concurrency.JobLauncher.invokeConcurrentlyUnderProgress(JobLauncher.java:57)
	at com.intellij.codeInsight.daemon.impl.LocalInspectionsPass.a(LocalInspectionsPass.java:253)
	at com.intellij.codeInsight.daemon.impl.LocalInspectionsPass.a(LocalInspectionsPass.java:223)
	at com.intellij.codeInsight.daemon.impl.LocalInspectionsPass.collectInformationWithProgress(LocalInspectionsPass.java:132)
	at com.intellij.codeInsight.daemon.impl.ProgressableTextEditorHighlightingPass.doCollectInformation(ProgressableTextEditorHighlightingPass.java:83)
	at com.intellij.codeHighlighting.TextEditorHighlightingPass.collectInformation(TextEditorHighlightingPass.java:70)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.d(PassExecutorService.java:438)
	at com.intellij.openapi.application.impl.ApplicationImpl.tryRunReadAction(ApplicationImpl.java:1161)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.a(PassExecutorService.java:431)
	at com.intellij.openapi.progress.impl.CoreProgressManager.a(CoreProgressManager.java:548)
	at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:493)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:94)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.b(PassExecutorService.java:430)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.c(PassExecutorService.java:406)
	at com.intellij.openapi.application.impl.ReadMostlyRWLock.executeByImpatientReader(ReadMostlyRWLock.java:142)
	at com.intellij.openapi.application.impl.ApplicationImpl.executeByImpatientReader(ApplicationImpl.java:250)
	at com.intellij.codeInsight.daemon.impl.PassExecutorService$ScheduledPass.run(PassExecutorService.java:404)
	at com.intellij.concurrency.JobLauncherImpl$VoidForkJoinTask$1.exec(JobLauncherImpl.java:165)
	at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
	at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
	at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
	at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)

@Danonk Thanks for the report.
Issue is fixed and will be released with v2.1.2

Thanks :)

@Danonk Please don't close it until it's not released.

Fix is available in v2.2.0-RC1 in EAP channel.

authors: Danonk hsz

repo: hsz/idea-gitignore


text:
Update sbt-scoverage to 1.8.1

Updates org.scoverage:sbt-scoverage from 1.6.1 to 1.8.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scoverage", artifactId = "sbt-scoverage" } ]

labels: sbt-plugin-update, semver-minor

Superseded by #107.


text:
Stackoverflow when implicitly creating an EntityEncoder for an implicit circe Encoder

I brought this up in the gitter channel and received great help from @SystemFw.
I'm adding it as an issue so that other people who might stumble over it are warned and also for tracking a possible fix for it.
If you create an implicit EntityEncoder from an implicit Encoder like so:
implicit def entityEncoder[A: Encoder]: EntityEncoder[F, A] = jsonEncoderOf[F, A]

You will get a StackOverflowError.
The solution (thanks @SystemFw) is to define the implicit like this:
  implicit def entityEncoder[A](implicit enc:  Encoder[A], ev: EntityEncoder[F, String]): EntityEncoder[F, A] = jsonEncoderOf[F, A](ev, implicitly[Applicative[F]], enc)

For the record, this seems to work fine for me but I'm not sure about the correctness:
implicit def jsonEncoder[A <: Product : Encoder, F[_]: Sync]: EntityEncoder[F, A] = jsonEncoderOf[F, A]

@gvolpe Counterexample
object Ex {
  import cats.effect._
  import io.circe._
  import io.circe.generic.auto._
  import org.http4s._
  import org.http4s.circe._

  implicit def jsonEncoder[A <: Product : Encoder, F[_]: Sync]: EntityEncoder[F, A] = jsonEncoderOf[F, A]

   case class Yo()

  class Foo[F[_]: Effect] {
    Encoder[String] // ok
    EntityEncoder[F, String] // ok
    Encoder[Yo] // ok
    EntityEncoder[F, Yo] // ok
    EntityEncoder[F, Int] // doesn't compile
  }
}

Okay so it works fine for any case class and String only... Interesting.

It will also break (I think) for sealed traits that don't extend Product, and objects that aren't case objects

Normally I define my sealed traits that are ADT's by extending Product with Serializable to help the type inference system. Not sure when one would try to get an EntityEncoder for an object though but it's good to keep this in mind.

Do we have plans to do anything about this?  Fix it?  FAQ it?

Could you please explain the reason for the StackoverflowError, @SystemFw, on:
implicit def entityEncoder[A: Encoder]: EntityEncoder[F, A] = jsonEncoderOf[F, A]

?
Thanks!

@kevinmeredith sure. Let's look at the signature of jsonEncoderOf:
 def jsonEncoderOf[F[_]: EntityEncoder[?[_], String]: Applicative, A: Encoder]: EntityEncoder[F, A]
It wants an Encoder for A, and an EntityEncoder[F, String]. So first of all your signature above is making the mistake of not propagating the EntityEncoder[F, String] constraint. Normally forgetting to propagate an implicit will cause a compilation error, since the method call needing it will not find it, however in this specific case, to define entitytEncoder you call jsonEncoder, which looks for an EntityEncoder[F, String] and finds...entityEncoder (by applying A to String), which is in turn defined by calling jsonEncoder, which looks for an EntityEncoder[F, String], which finds...entityEncoder (by applying A to String), which is in turn defined by....
This infinite recursion causes a stack overflow.

Thanks, @SystemFw, for that detailed explanation!
Why must jsonEncoderOf have an EntityEncoder[F, String] in implicit scope?

You know, maybe it shouldn't: maybe we should just refer to it explicitly, with explicit UTF-8 encoding. :thinking:

You have the choice of a different encoding regardless.

I thought I remembered JSON requiring a UTF-8 encoding.  It requires a unicode encoding.
If we provide an implicit string encoder, nothing stops a bizarre encoding. If we provide an implicit charset, nothing stops a bizarre encoding, but we get out of this circle.  If we provide an implicit sealed enum of unicode encodings, we can statically prevent illegal encodings, but, good grief.

jsonEncoderOf no longer takes an EnityEncoder[F, String]. I think this is obsolete now.

authors: SystemFw gvolpe jadlr jmcardon kevinmeredith rossabaker


text:
Restore defaults on MuliptartDecoder.mixedMultipart

Necessary for binary compatibility.

This was overlooked in #4113.  It's troubling that CI didn't catch that.


text:
Update sbt-http4s-org to 0.13.2 in series/0.22

Updates org.http4s:sbt-http4s-org from 0.13.1 to 0.13.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (0.13.1).
You might want to review and update them manually.
docs/changelog.md

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s", artifactId = "sbt-http4s-org" } ]

labels: sbt-plugin-update, early-semver-minor, semver-spec-patch, old-version-remains, commit-count:1

Some of the remaining filters may be due to https://github.com/lampepfl/dotty/issues/10842.
This is the "opposite" of the static-forwarder problem: in Scala 2, when we make an object method package-private, they go away. In Scala 3, they are always there, even if the method was already package-private.

authors: armanbilge scala-steward


text:
Add FormData::Multipart#boundary reader method

I wanted to measure performance of the multipart-parser gem, to compare it to the performance of Rack's multipart parser. I'm using http-form_data to generate test multipart data, and multipart-parser needs me to pass in the boundary. I can call MultipartParser::Reader.extract_boundary_value to extract the boundary from FormData::Multipart#content_type before parsing, but since the FormData::Multipart object already knows the boundary, I thought I could eliminate this extra step.

@ixti Updated 😀

Awesome! Thanks!

authors: ixti janko-m


text:
cannot convert float infinity to integer

This image after after converting it into numpy having some infinite float value resulting in cannot convert float infinity to integer

Hi Sachin. Sorry for the late reply. Next time, you can post or search for topics in our community. There might be mentors/learners there who have the same setup and can help you. If you haven't joined yet, you can find instructions in Week 1 of your classroom. Thanks!

authors: SachinMishra-ux cfav-dev


text:
更新0.42后打开回答和想法会报错

无法复现

已尝试修复

authors: huajiqaq xushet

repo: huajiqaq/Hydrogen


text:
display driver issue

I am using 49 inch dell screen with ubuntu 20,
run for a second and failed after  following message

🚀 Pulling the docker image done.
🚀 Starting DoChat /dɑɑˈtʃæt/ ...
[DoChat] 盒装微信 v0.14.4
Disabling patch for /home/user/.wine/drive_c/users/user/AppData/Roaming/Tencent/WeChat ...
Disabling patch for /home/user/.wine/drive_c/users/user/Application Data/Tencent/WeChat ...
[DoChat] WeChat 3.3.0.115
[DoChat] Starting...
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
Major opcode of failed request:  151 (GLX)
Minor opcode of failed request:  6 (X_GLXIsDirect)
Serial number of failed request:  280
Current serial number in output stream:  279
[DoChat] WeChat.exe exit with code 0
[DoChat] Found new version?
[DoChat] WeChat.exe exited

Link to:

#131

repo: huan/docker-wechat


text:
Feature: Kebab Case

A KebabCase functions. I think it should behave exactly like snakecase accept that _ becomes -.
It's also requested on https://github.com/Masterminds/sprig/issues/113.

Awesome and thanks! That was fast :)

repo: huandu/xstrings


text:
Update to flask v3

Following merged PR #570 for TEST

Replaced by #573

repo: hubmapconsortium/ingest-api


text:
Add annotation to produce RX version of the proxy.

Hi had this discussion over here: https://mail.google.com/mail/u/0/#inbox/1573429ca3bad282

@javadevmtl hey, this link goes to your personal inbox I guess .... can you link to a public archive?

https://groups.google.com/forum/m/#!topic/vertx/UGYtPZDBv1g
Somewhere lost in those threads. But bassically if you include vertx-rx-java plus an extra anotation with your pom, the codegen will also generate rx java interfaces.

See Dan O'Orileys comments.

authors: javadevmtl marcust

repo: hubrick/vertx-kafka-service


text:
🛑 VGMdb API is down

In ecb3f98, VGMdb API (https://vgmdb.info) was down:

HTTP code: 502
Response time: 327 ms

Resolved: VGMdb API is back up in e2ef5a3 after 6 minutes.

repo: hufman/upptime


text:
🛑 Akkoma is down

In 020760e, Akkoma (https://akkoma.chez.chat) was down:

HTTP code: 404
Response time: 492 ms

Resolved: Akkoma is back up in 379feb3 after 6 minutes.


text:
🛑 VGMdb API is down

In ffa5624, VGMdb API (https://vgmdb.info) was down:

HTTP code: 0
Response time: 0 ms

Resolved: VGMdb API is back up in 833bfbc after 5 hours, 37 minutes.


text:
RDF数据入库hugegraph遇到很多困难

您好，我有三个问题没有找到答案，想请教下：
每个实体有1200多个属性，似乎超出了限制，每次都会报错，导致无法入库，怎么增加属性数量上限？报错如下：
ERROR: Failed to load
Exception in thread "main" org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
General error during class generation: 1200
java.lang.ArrayIndexOutOfBoundsException: 1200
还有一个关系入库的bug困扰着我，我用csv方式存储的关系，每行只有两个自定义id用于建立连接，但是vertex中自定义id和name联合做主键，入库关系时报错Invalid id
例如某一行 sx27105,sx10945
写入关系时报错Invalid vertex id '1:null!sx27105'
经检索sx27105实体已经入库.我怀疑是你们仍然用name和id组合去查找实体了，但是我只用id属性做关联，这个问题怎么解决呢？
还有个小问题，默认展示的是主键，我想展示其他字段怎么设置呢？

@boo-boos 分别解答：

请问插入顶点是使用Gremlin进行的吗？建议使用rest api接口。同时，可以给出错误的堆栈信息方便我们分析。
看起来不是bug，如果顶点类型是id+name联合主键，那么导入边时也应该使用id+name，而不是仅仅只有id。如果不是上述意思，建议单独提交一个issue，贴出struct和schema，以供判断错误原因。
hugegraph-hubble可以在【元数据-编辑】里面修改展示列。

@boo-boos 分别解答：

请问插入顶点是使用Gremlin进行的吗？建议使用rest api接口。同时，可以给出错误的堆栈信息方便我们分析。
看起来不是bug，如果顶点类型是id+name联合主键，那么导入边时也应该使用id+name，而不是仅仅只有id。如果不是上述意思，建议单独提交一个issue，贴出struct和schema，以供判断错误原因。
hugegraph-hubble可以在【元数据-编辑】里面修改展示列。

您好，感谢回复，关于问题2和3，我尝试下。至于问题1，我贴出来的就是报错信息，使用hugegraph-loader入库的。仔细尝试之后，似乎属性值上限是256，超过即报错，我有1200个属性，因此报
ERROR: Failed to load
Exception in thread "main" org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
General error during class generation: 1200
java.lang.ArrayIndexOutOfBoundsException: 1200

至于问题1，我贴出来的就是报错信息，使用hugegraph-loader入库的。仔细尝试之后，似乎属性值上限是256，超过即报错，我有1200个属性

可以先使用rest-api将schema创建好，loader创建schema使用的是groovy语法，可能groovy数组有256这个限制，实际上hugegraph没有这个限制的。

@boo-boos 还有其他的问题吗？没问题就关闭issue了。

至于问题1，我贴出来的就是报错信息，使用hugegraph-loader入库的。仔细尝试之后，似乎属性值上限是256，超过即报错，我有1200个属性

可以先使用rest-api将schema创建好，loader创建schema使用的是groovy语法，可能groovy数组有256这个限制，实际上hugegraph没有这个限制的。

您好，那这个问题应该如何解决呢？

至于问题1，我贴出来的就是报错信息，使用hugegraph-loader入库的。仔细尝试之后，似乎属性值上限是256，超过即报错，我有1200个属性

可以先使用rest-api将schema创建好，loader创建schema使用的是groovy语法，可能groovy数组有256这个限制，实际上hugegraph没有这个限制的。

您好，那这个问题应该如何解决呢？

@Linary 看看loader是否能loader不受256这个限制？

@Linary 看看loader是否能loader不受256这个限制？

@Linary 我也遇到了这个问题  有一种实体字段过多 如果采用了api的方式预先定义了schema，那么是不是以后就不能使用loader的方式更新数据了？？？

@Linary 我也遇到了这个问题  有一种实体字段过多 如果采用了api的方式预先定义了schema，那么是不是以后就不能使用loader的方式更新数据了？？？

@Linary 是否有方式更改loader的限制？

@Linary 是否有方式更改loader的限制？

@happy-nlp @zx-6017 可以先定义一个 list，然后调list的toArray()方法传入properties中。举例：
list = ["1","2"..."n"]
schema.vertexLabel("person")
      .properties(list.toArray(new String[0]))
      .primaryKeys("name")
      .nullableKeys("age", "city")
      .ifNotExist()
      .create();

@happy-nlp @zx-6017 可以先定义一个 list，然后调list的toArray()方法传入properties中。举例：
list = ["1","2"..."n"]
schema.vertexLabel("person")
      .properties(list.toArray(new String[0]))
      .primaryKeys("name")
      .nullableKeys("age", "city")
      .ifNotExist()
      .create();

authors: Linary boo-boos javeme zx-6017

repo: hugegraph/hugegraph


text:
Always use SeedableRandomSampler

What does this PR do?
Because at the end of the day the trainer will always use a DispatchDataLoader (even in the case of num_gpus == 1), it needs to be able to set the random seed properly for the sampler. The solution is to just always use the SeedableRandomSampler. While our tests (in accelerate)do not fail, they don't account for if the base case is DispatchDataLoader (Trainer tests).
Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@BenjaminBossan

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

authors: HuggingFaceDocBuilderDev muellerzr

repo: huggingface/accelerate


text:
Disable P2P in just the 4000 series

What does this PR do?
My research was a bit off, the 3090's can still do P2P from what this user reports, so I adjusted the limit to only happen on 40* series.
Fixes https://github.com/huggingface/accelerate/issues/2328
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@SunMarc

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


text:
Add 8 bit support - chapter II

Hi !
Here is a (dirty) attempt of enabling other modules support (other than nn.Parameter) on accelerate
This time I had to slightly modify the script set_tensor_to_device as following:

If is_buffer : assigns the buffer to new_value as usual
assign module._parameters[tensor_name] to the correct new_value ONLY when the device is different to a GPU. The latest case means that the new_value has been already set to the correct device so there is probably no need to put it again on the same device.

I can't see any breaking changes but I suspect the likelihood of this statement being true is quite high. Would love to hear your thoughts @sgugger @muellerzr
Related to the PR: https://github.com/huggingface/transformers/pull/17901

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

authors: HuggingFaceDocBuilderDev younesbelkada


text:
Added new smol 🤏 Multimodal RAG System with ColSmolVLM and SmolVLM recipe 🧑🍳

What does this PR do?

Fixes #243
Who can review?
@merveenoyan and @stevhliu

very cool!

View / edit / reply to this conversation on ReviewNB
andimarafioti commented on 2024-12-05T12:45:51Z ----------------------------------------------------------------
Have you tried to also quantize the docs_retrieval_model?

The library currently doesn't support quantization_config as in transformers:

It could be possible but I think it would add a lot of complexity to the notebook without that native support.

In the actual notebook, it's not shown twice: https://github.com/huggingface/cookbook/blob/12a99a3d8c4f5607bb382e1d8536e60392e653b1/notebooks/en/multimodal_rag_using_document_retrieval_and_smol_vlm.ipynb

View entire conversation on ReviewNB

Added! Comparison of these two systems and the other two multimodal RAG recipes :)

View entire conversation on ReviewNB

Updated 🤗

Thanks for the suggestions @merveenoyan 😄 Applied!

authors: andimarafioti sergiopaniego

repo: huggingface/cookbook


text:
Fixed augmentations no applied to labels during training in fine-tuning semantic segmentation notebook

What does this PR do?

Fixes #248
Who can review?
@merveenoyan and @stevhliu.

Thanks for pointing out! Removed :)

View entire conversation on ReviewNB

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

authors: HuggingFaceDocBuilderDev sergiopaniego


text:
the course is outdated

the topic transformers should be remove imo i dont think all the latest stuff of transformers is covered in this , corrct me if i am wrong

Can you be more specific?

let me just rephrase it, the course should get updated with latest stuff

Can you be more specific?

i feel like the course is outdated it should contain more new stuff ...

Can you be more specific?

i feel like the course is outdated it should contain more new stuff ...

Saying "new stuff" doesn't help much.
It would be better to list specific places where things are wrong or broken.
Not simply "do things better"

Can you be more specific?

i feel like the course is outdated it should contain more new stuff ...

Saying "new stuff" doesn't help much.
It would be better to list specific places where things are wrong or broken.
Not simply "do things better"

OKAY GIVE ME TIME .. I WILL GO THROUGH THE COURSE

Chapter 2 Using Transformers > Models > Saving Methods (Using Pytorch)
Does not save these two files:
ls directory_on_my_computer
config.json pytorch_model.bin
Instead it saves these two files:
ls directory_on_my_computer
config.json model.safetensors

Chapter 2 "End of Chapter Quiz" does not allow you to click the "Complete Chapter" link because it detects that the user hasn't finished the Quiz. If you look at the column on the right hand side of the screen it shows there are two Exercises #10. I'm guessing this must be the problem.

@CodingVoyagerPrincess please make a new pull issue dont trash talk here please i request humbly!

authors: Ayaan-Sharif CodingVoyagerPrincess MichaelrMentele fancellu

repo: huggingface/course


text:
DatasetScriptError should be retried

On dataset mozilla-foundation/common_voice_6_1, we have DatasetScriptError, caused by DatasetGenerationError, caused by a timeout.
In this case, for config de, step config-parquet-and-info:
{
  "error": "An error occurred while generating the dataset",
  "cause_exception": "DatasetGenerationError",
  "cause_message": "An error occurred while generating the dataset",
  "cause_traceback": [
    "Traceback (most recent call last):\n",
    " File \"/src/services/worker/.venv/lib/python3.9/site-packages/fsspec/asyn.py\", line 56, in _runner\n result[0] = await coro\n",
    " File \"/src/services/worker/.venv/lib/python3.9/site-packages/fsspec/implementations/http.py\", line 762, in _read\n out = await self.r.content.read(num)\n",
    " File \"/src/services/worker/.venv/lib/python3.9/site-packages/aiohttp/streams.py\", line 385, in read\n return self._read_nowait(n)\n",
    " File \"/src/services/worker/.venv/lib/python3.9/site-packages/aiohttp/streams.py\", line 492, in _read_nowait\n self._timer.assert_timeout()\n",
    " File \"/src/services/worker/.venv/lib/python3.9/site-packages/aiohttp/helpers.py\", line 709, in assert_timeout\n raise asyncio.TimeoutError from None\n",
    "asyncio.exceptions.TimeoutError\n",
    "\nThe above exception was the direct cause of the following exception:\n\n",
    "Traceback (most recent call last):\n",
    " File \"/src/services/worker/.venv/lib/python3.9/site-packages/datasets/download/streaming_download_manager.py\", line 342, in read_with_retries\n out = read(*args, **kwargs)\n",
    " File \"/src/services/worker/.venv/lib/python3.9/site-packages/fsspec/asyn.py\", line 118, in wrapper\n return sync(self.loop, func, *args, **kwargs)\n",
    " File \"/src/services/worker/.venv/lib/python3.9/site-packages/fsspec/asyn.py\", line 101, in sync\n raise FSTimeoutError from return_result\n",
    "fsspec.exceptions.FSTimeoutError\n",
    "\nThe above exception was the direct cause of the following exception:\n\n",
    "Traceback (most recent call last):\n",
    " File \"/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py\", line 1726, in _prepare_split_single\n for key, record in generator:\n",
    " File \"/src/services/worker/src/worker/job_runners/config/parquet_and_info.py\", line 804, in wrapped\n for item in generator(*args, **kwargs):\n",
    " File \"/tmp/modules-cache/datasets_modules/datasets/mozilla-foundation--common_voice_6_1/d06c81622a9ea58a044f008c934f6c0f864b4051dacba0d920e36160ce362a33/common_voice_6_1.py\", line 256, in _generate_examples\n result[\"audio\"] = {\"path\": path, \"bytes\": f.read()}\n",
    " File \"/usr/local/lib/python3.9/tarfile.py\", line 688, in read\n b = self.fileobj.read(length)\n",
    " File \"/usr/local/lib/python3.9/tarfile.py\", line 525, in read\n buf = self._read(size)\n",
    " File \"/usr/local/lib/python3.9/tarfile.py\", line 543, in _read\n buf = self.fileobj.read(self.bufsize)\n",
    " File \"/src/services/worker/.venv/lib/python3.9/site-packages/datasets/download/streaming_download_manager.py\", line 351, in read_with_retries\n raise ConnectionError(\"Server Disconnected\") from disconnect_err\n",
    "ConnectionError: Server Disconnected\n",
    "\nThe above exception was the direct cause of the following exception:\n\n",
    "Traceback (most recent call last):\n",
    " File \"/src/services/worker/src/worker/job_manager.py\", line 125, in process\n job_result = self.job_runner.compute()\n",
    " File \"/src/services/worker/src/worker/job_runners/config/parquet_and_info.py\", line 1392, in compute\n compute_config_parquet_and_info_response(\n",
    " File \"/src/services/worker/src/worker/job_runners/config/parquet_and_info.py\", line 1300, in compute_config_parquet_and_info_response\n parquet_operations, partial = stream_convert_to_parquet(\n",
    " File \"/src/services/worker/src/worker/job_runners/config/parquet_and_info.py\", line 895, in stream_convert_to_parquet\n builder._prepare_split(\n",
    " File \"/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py\", line 1605, in _prepare_split\n for job_id, done, content in self._prepare_split_single(\n",
    " File \"/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py\", line 1762, in _prepare_split_single\n raise DatasetGenerationError(\"An error occurred while generating the dataset\") from e\n",
    "datasets.exceptions.DatasetGenerationError: An error occurred while generating the dataset\n"
  ]
}

I'm not sure if we should retry all the DatasetScriptError errors, or raise another error when the dataset could not be loaded due to a timeout error.

closing as DatasetScriptError does not exist anymore. And the issue is the same as #3011

repo: huggingface/dataset-viewer