Updater service

Add a simple service that takes care to poll the versions.json as the source of truth for the latest version of the services to be "stable".
The service should

expose an endpoint to give the currently running version and the new ones with a newer version for each service.
expose an endpoint to trigger a docker pull (and also restart?) on the latest images.

Optionally we can pass an AUTO_UPDATE=all|patch|minor|major env var to automatically update to the latest version based on SemVer (it can be exported by the installer script of prem-box after asking user)

alternative: https://github.com/premAI-io/prem-app/pull/458


Pretrained diffusion models

Hello,
Thank you for sharing your work!
I wanted to inquire whether you've explored integrating pretrained diffusion models like Stable Diffusion v1.5 or v2.1 into your project. If so, I’d love to hear more about the results and any insights you can share.
Thanks in advance for your time and assistance!

Yes I've tried that, basically using SD as the slot decoder. But I didn't go very far as fine-tuning requires huge memory. If I freeze it, I cannot learn good object-centric representation.
But you can check out the Stable-LSD variant in this work, they have shown some promising results using SD.

Thank you for your response! If possible, could you kindly share the results you have for the COCO and VOC datasets? I’d greatly appreciate it.
Best regards,

I think I don't have them anymore. Well, even in Stable-LSD, the reconstruction results are not very good TBH. Also IIRC, it's not capable of compositional generation at all. So I don't know if this can even work -- the part-whole ambiguity is too complicated in real-world data, unsupervised decomposition is just too hard.

There is another paper you might be interested in: https://arxiv.org/abs/2407.17929
They use more pre-trained knowledge to generate pseudo masks to supervise their slot + SD model. They can get good segmentation results, but still the generation is quite bad I think


eplus: validate "app" JSON, check event status & throw if no playlist

Data analysis
The structure of "data_json" ("app" in the webpage)

JSON object
{
    "app_id": "...",
    "app_name": "...",
    "venue_name": "\uff33\uff54\uff52\uff45\uff41\uff4d\uff49\uff4e\uff47\uff0b", // "Ｓｔｒｅａｍｉｎｇ＋"
    "stream_type": "AWS_SINGLE",
    "embedded_type": "IFRAME",
    "player_mode": null,
    "delivery_status": "...",
    "stream_status": "...",
    "number_of_channel": "1",
    "event_datetime": "...",
    "event_datetime_text": "...",
    "buy_ticket_url": "...",
    "description": null,
    "page_display_period": "...",
    "page_display_period_text": "...",
    "is_live_stream": true,
    "chat_mode": "OFF",
    "drm_mode": null,
    "drm_strict_mode": null,
    "virtual_live_mode": null,
    "chat_type": null,
    "chat_open_mode": "OFF",
    "stream_end_at": null,
    "chat_embed_link": null,
    "archive_mode": "ON",
    "archived_status": "...",
    "image_url": null,
    "end_event_image_url": null,
    "all_in_one_thumbnail": "ON",
    "content": "...",
    "allow_number_of_viewable": "1",
    "event_type": "1",
    "term_event_from": "...",
    "term_event_to": "...",
    "is_pass_ticket": "NO",
    "delete_flag": "0",
    "copyright_code": "...",
    "shooting_angle": "",
    "extra": null,
    "extra_archive": null,
    "is_dvr": "OFF",
    "archive_time": "You can watch this channel until ...",
    "archive_kubun": "1",
    "zoom_date_text": {
        "year": "...",
        "month_day_from": "...",
        "month_day_to": "...",
        "day_of_week_from": "...",
        "day_of_week_to": "...",
        "time": "..."
    },
    // The following 4 fields will disappear if the event becomes inaccessible.
    "emergency_message": null,
    "emergency_mode": "OFF",
    "emergency_image": "https:\/\/d1mc0giw38g3ps.cloudfront.net\/stream_images\/emergency.jpg",
    "origin_chat_embed_link": null,
    // New fields?
    "tvod_mode": "...",
    "tvod_date_text": "...",
}

The lifecycle of an event

What I saw
Timeline ↓
In "data_json" ("app" in the webpage)
In the webpage

Playable on the webpage?
Status of the event
"delivery_status"
"stream_status"
"archived_status"
"is_live_stream"
m3u8 url (listChannels)

no
not started

PREPARING
PREPARING
null
false
[]

T0-900mins
CREATING

T0-900mins
READY
["https://stream.live.eplus.jp/out/v1/{hash0}/index.m3u8"]

T0-240mins
LIVE
true

yes
T0
STARTED

started
T0+60mins

no
ended
T1-10mins
STOPPED

T1
WAIT_CONFIRM_ARCHIVED
READY
SUCCEEDED
false

yes
archive available
T1+90mins
CONFIRMED_ARCHIVE
["https://vod.live.eplus.jp/out/v1/{hash0}/{hash1}/{name0}.m3u8"]

T1+180mins
["https://vod.live.eplus.jp/out/v1/{hash0}/{name1}/{name1}.m3u8"]

T1+980mins
DELETED
true

no
expired

non-existing

The above table is generated by HTML Tables generator – TablesGenerator.com.
Test
Parameters:

--retry-max 1

Before starting:
[...][cli][info] Found matching plugin eplus for URL https://live.eplus.jp/ex/player?ib=...
[...][plugins.eplus][debug] delivery_status = PREPARING, archive_mode = ON
[...][plugins.eplus][error] This event has not started yet
[...][cli][info] Waiting for streams, retrying every 1 second(s)
[...][plugins.eplus][debug] delivery_status = PREPARING, archive_mode = ON
[...][plugins.eplus][error] This event has not started yet
error: No playable streams found on this URL: https://live.eplus.jp/ex/player?ib=...

Started:
[...][cli][info] Found matching plugin eplus for URL https://live.eplus.jp/ex/player?ib=...
[...][plugins.eplus][debug] delivery_status = STARTED, archive_mode = ON
...

Archive deleted:
[...][cli][info] Found matching plugin eplus for URL https://live.eplus.jp/ex/player?ib=...
[...][plugins.eplus][debug] delivery_status = CONFIRMED_ARCHIVE, archive_mode = ON
[...][cli][error] Failed to get list_channels
[...][cli][info] Waiting for streams, retrying every 1 second(s)
[...][plugins.eplus][debug] delivery_status = CONFIRMED_ARCHIVE, archive_mode = ON
[...][cli][error] Failed to get list_channels
error: No playable streams found on this URL: https://live.eplus.jp/ex/player?ib=...

Also see yt-dlp/yt-dlp#5782 .

The difference of the titles is:
>>> validate.Schema(
        validate.parse_html(),
        validate.xml_xpath_string(".//head/title/text()"),
    ).validate(body)

'\n  少女☆歌劇 レヴュースタァライト -The LIVE-#4 Climax 初日夜スイッチング映像視聴チケット | STREAMING PLUS\n'

>>> data_json["app_name"]

'少女☆歌劇 レヴュースタァライト -The LIVE-#4 Climax 初日夜スイッチング映像視聴チケット'

Thus, I prefer "app_name".

The archive_mode check should work. I've seen a live streaming without archives has properties of delivery_status = PREPARING, archive_mode = OFF .

The archive_mode check should work. I've seen a live streaming without archives has properties of delivery_status = PREPARING, archive_mode = OFF .

Interesting, I must have written the wrong code:
[plugins.eplus][debug] delivery_status = WAIT_CONFIRM_ARCHIVED, archive_mode = OFF
[plugins.eplus][error] This event has ended, and the archive will be available shortly

There should not be any archives.


sortOptionSchema doesn't exist

Expected behavior
sortOptionSchema should exist or the import should be removed
Actual behavior
sortOptionSchema is imported in packages/react/src/analytics/integrations/GA4/validation/eventSchemas.js from packages/react/src/analytics/integrations/shared/validation/eventSchemas.js but it doesn't exist anywhere in the codebase
Steps to reproduce

HMR bundler shows warning<EMAIL_ADDRESS>61:66-82 "export 'sortOptionSchema' was not found in '../../shared/validation/eventSchemas'

Context/environment

Additional information

Possible fix
sortOptionSchema should exist or the import should be removed

Hello @AceBunny, this bug was already fixed here and will be released next week.
Thanks for your input anyway 🙂

Yeah, that seems to fix it, sorry for the inconvenience

No inconvenience at all, feel free to open issues whenever you feel its necessary 🙂  cheers!


Sorted bitrates

Hello, first of all, thank you for an awesome package.
Can you enlighten me about the the reasoning behind the sorting of the bitrates? (https://github.com/pascalbaljetmedia/laravel-ffmpeg/blob/master/src/HLSPlaylistExporter.php#L33)
The order they are added to the master playlist actually matters, as the first item on list is the default source that will be used until it has calculated the optimal bitrate.
Say I have the following bitrates [128, 256, 512, 1024, 2048], optimally I'd like to use the 512 bitrate as the default, as the 128 is a very grainy default, only meant for those that really doesn't have a better connection.
Is it possible to turn the sorting off, or is there a thought behind it?

I'll create an option to turn the sorting off, seems like a good feature!


[AutoPR] postgresql/resource-manager

Created to accumulate context: postgresql/resource-manager

(message created by the CI based on PR content)

Deprecated PR


Enable support for rollup v3

Also this PR does:

Drop node v12 and sets minimum to node v14 (and npm 8)
Switch to ESM
Drop the esbuild and just copies the file to the dist folder
Drop support for rollup v1.x.x

@dgrammatiko thanks for opening a pull request, while I agree rollup v3 support needs to be added. I still would like to keep the package supporting a CJS and ESM build. If you want to adjust the PR to keep the builds as is while adding v3 support I can merge the PR.

Sorry to be picky, rather than adding a new build.js script, it would be preferably to keep the existing build pipeline with rollup. The only thing that should need to change for rollup v3 support is just updating dependencies, dropping v1 if there is an api incompatibility, and updating the peerDependencies versions. Is there a reason you want to drop the existing system and just add a script to copy the file over?

it would be preferably to keep the existing build pipeline with rollup.

Then you have to wait till rollup-plugin-esbuild is merged so that the bundling could work. I don't mind closing this PR and let you update the deps when the rollup-plugin-esbuild is v3 compatible

Since the rollup dependencies are devDependencies they are not required for adding v3 support, so the devDependencies can remain the same, and rollup v3 can still be supported. If you want to make the changes you can otherwise I dont mind pushing an update with this. (This is how i added rollup v3 support to rollup-plugin-import-css)

Thanks for taking care of the support for Rollup v3 @dgrammatiko, v1.1.6 is published on npm.


Adding use-intersection-observer

Multiple questions:
1. How this will work

copy and paste?
deploy it to npm until you need something really custom then copy and paste and modify
if we deploy to npm would it be like a set of utils or individually?
import {useIntersectionObserver, useWindowSize} from '@jam3/react-hooks'

2. Do we need code examples?

we can either put a readme with basic behavior and options
or I could create a quick code sandbox with a simple example, I did this one for this hook https://codesandbox.io/s/react-use-intersection-observer-4ojbk for example
we can also link projects but then this cannot be public

What else we need?

no copy and paste
should design the api to allow customization, and later on if that's not enough, whoever is using it and want more should contribute back and release new versions (could happen after the project, but ideally should be before using and install the new version from npm)
I personally would prefer deploy individually, but don't mind having one package
readme for each hook should be enough?
I think we might want learna to do this


[macOS] Install only latest runtime for Xcode - compatibility  bug

Description
On the latest builds of macOS-13 images, strange behaviour is observed in the installed simulators. The behaviour exists only for Xcode 15. If you set more than one runtime, the simulators are duplicated, which leads to errors in the future. As a possible workaround, you can only install the latest available runtime for Xcode 15. Users will need to download/install previous versions at runtime.
UPD: Also possible to install any other of runtimes, for Xcode 15.0 for example.
Related issue:
Check list

[ ] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

This probably isn't the perfect place to report this but on latest builds of macOS-14 images, I am also seeing what I'd call strange behavior with simulators. It seems that xcrun simctl launch <device> <app bundle> hangs with my setup. At this point, I've filed https://github.com/sonos/dinghy/issues/207 (cargo-dinghy can take/build a rust binary for iOS and bundle it up as an iOS app and run it on the simulator) as it's possibly a bug in cargo-dinghy but when using my local m1, things work as expected.
I'm not sure how to debug this behavior. Would it be helpful for me to setup a more refined example (using a simple xcode project, building the app and using xcrun simctl launch?

@simlay sounds as a possible good first issue to be honest. If you are currently not sure that the problem is in the simulators presented in the image, then yes, the best way to check is to build a simple application and run it through the simulator. Even if it freezes, this is an alarm bell. After it you may report it as an issue - we'll investigate it. It would be great if you could provide a sample project and links to successful launches in other environments.


[Doc] Point "Architecture" link to latest doc found in "Adding and Configuring a Service Provider"

In [1] the "Architecture" link directs to a previous doc please fix it to the 5.4.0 docs
[1] https://docs.wso2.com/display/IS540/Adding+and+Configuring+a+Service+Provider

@jsonds Fixed this.
@shavidissa there are a couple of more places in this page that has references to 5.3.0 docs. Can you have a look


will we forward any refs by ourselves?

Radix can be annoying with "ref should be forwarded" errors. My question is if we use this library instead of directly using Radix, will we ever have to forward refs by ourselves or all cases covered already? Even if we create custom components? Thanks

Refs are forwarded where needed. You'll probably only need to if you're wrapping the existing components.

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


[OTBN] Choose a bus

Should OTBN be connected to the main or peri crossbar? Latency doesn't matter for that device.
@eunchan

i feel like this should be the main xbar, since OTBN itself will most
likely be on the main system clock (the peri xbar will be on a slower
clock).
And I'm guessing it would be easier for the design to not have async
boundaries between OTBN configs and the internal logic.
On Tue, Jun 16, 2020 at 8:35 AM Philipp Wagner<EMAIL_ADDRESS>wrote:

Should OTBN be connected to the main or peri crossbar? Latency doesn't
matter for that device.
@eunchan https://github.com/eunchan
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/issues/2518, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSUURM3QRHK5GGFM4PTRW6GMVANCNFSM4N7XR6ZQ
.

Sounds good, thanks @tjaychen! (I thought it would be that way, but I wasn't sure that the exact motivation behind the partitioning was.)

Agree with Tim.
On Tue, Jun 16, 2020 at 08:40:16AM -0700, Philipp Wagner wrote:

Sounds good, thanks @tjaychen! (I thought it would be that way, but I wasn't sure that the exact motivation behind the partitioning was.)
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/lowRISC/opentitan/issues/2518#issuecomment-644844590


Changing "heading" in "local_xy_origins" doesn't make any difference.

Following the explanation in #256, I fixed the origin of the 'map' frame to a geographic coordinate in local_xy_origins.

<rosparam param="local_xy_origins">

  [{ name: swri,
     latitude: 48.891690,
     longitude: 9.172950,
     altitude:<PHONE_NUMBER>86,
     heading: 0.0}]
</rosparam>

I tried changing heading to different values but nothing worked. Running lat_lon_tf_echo node with fixed_frame and target_frame set to map always returns heading to be 90°.

Latitude: 48.891690°, Longitude: 9.172950°, Heading: 90.000000°

However, if I introduce an offset intransform_util.cpp's ToYaw method then I see the corresponding change, but I guess this is not the right way to do it. Any suggestions about that?

In  initialize_origin.py, I found out that _gps_fix.track is fixed to 90°. I changed it to _gps_fix.track = origin["heading"] which seems to fix this issue. This corrects my path messages' transformations ( which contains lat / lon data), but as a result of this my multires_image also gets rotated which is not very convenient.  Could you explain why is this happening? Is there any way to introduce heading only for your path messages transformation, and avoid its affect on tile_map and multires_image? Thanks!
Note: My GPS position gets displayed correctly in every case.

Well, that sort of makes sense.  Changing the heading on the local_xy_origin would effectively be rotating the rest of your tf tree with respect to the wgs84 coordinate frame.  How is it not working properly when the heading is set to 0.0?

Yes, you are right. Instead of changing the heading, I needed to introduce a static transform between map and my path messages frames (). So, I have reverted the changes in  initialize_origin.py  and changed   heading  back to 0.0. It works now. Thanks a lot!


"$default_instance" is an unfortunate choice of a name

Using Amplitude's javascript snippet inside a PHP file with a strict mode ON will complain that default_instance is undefined because in PHP all variables start with $ sign and it thinks it's a variable.
Consider using a string without $ sign.

Unfortunately we aren't likely to change this any time soon. There are integrations out in the wild that depend on that specific name. Will be sure to add a note in the official about this gotcha for PHP devs.


Please add Ports Overlay

See: https://github.com/microsoft/vcpkg/issues/25167?notification_referrer_id=NT_kwDOAIKvvbIzNzgzMjk5MzE2Ojg1NjQ2Njk#issuecomment-1219240007
I test environment VCPKG_OVERLAY_PORTS . but it is invalid here.
Can you add overlay input?

@KangLin I think you could contribute to the documentation by adding instructions on how to set up overlay with the run-vcpkg action.
Either using VCPKG_OVERLAY_PORTS environment variable, or by modifying the default value of the runVcpkgFormatString input you should be able to leverage the "ports overlay" feature.

I am use v7. I don't find runVcpkgFormatString input. it is in v10.
I test environment VCPKG_OVERLAY_PORTS . but it is invalid here.
Please see: https://github.com/KangLin/RabbitRemoteControl/blob/develop/.github/workflows/msvc.yml

@KangLin I looked to the workflow called msvc and could not see what the exact problem is. Looks like the execution with run-vcpkg, along with the environment variable VCPKG_OVERLAY_PORTS set, worked fine.
Could you please elaborate about what's the observed behavior and what is  the expected one?
A link to a relevant error would be helpful, thanks.

vcpkg current openssl version is 3.x.x. but I want to use openssl 1.1.1n. so that I create port folder in my project https://github.com/KangLin/RabbitRemoteControl/tree/develop/vcpkg/ports/openssl .
run the github action. it is use vcpkg openssl 3.x.x .
I think to the environment variable VCPKG_OVERLAY_PORTS isn't used.

I test in locale. it is not work. so that maybe is vcpkg problem.

Use environment variable VCPKG_OVERLAY_PORTS is work. Thanks @lukka response.

@KangLin thanks to let us know! if you'd like to contribute to the documentation with an example leveraging the VCPKG_OVERLAY_PORTS? Or drop in here a link to the workflow which uses overlays and I can figure out how to document this, thanks!

@lukka  I'd be happy to contribute. Please tell me how to do it?
Example: https://github.com/KangLin/RabbitRemoteControl/blob/master/.github/workflows/msvc.yml
openssl 1.1.1n port: https://github.com/KangLin/RabbitRemoteControl/tree/master/vcpkg/ports/
See: https://github.com/microsoft/vcpkg/issues/25167


Duplicate results from racer

Given the code:
pub enum Level {
}

Racer gives:
$ CARGO_HOME=/home/wilfred/.cargo RUST_SRC_PATH=/home/wilfred/src/rustc-1.10.0/src /home/wilfred/.cargo/bin/racer complete-with-snippet 1 14 /home/wilfred/projects/bfc/src/diagnostics.rs
PREFIX 9,14,Level
MATCH Level;Level;1;9;/home/wilfred/projects/bfc/src/diagnostics.rs;Enum;pub enum Level {;""
MATCH Level;Level;1;9;/home/wilfred/projects/bfc/src/diagnostics.rs;Enum;pub enum Level {;""
END

I've seen suggestions appear 5 or 6 times over.

I can not reproduce this fault on the latest commit on master
commit fbfa038
if there is no other exempels when there is duplicated results I think that this can be closed.

I'm still able to reproduce this; I see the same module appearing 3 times in the autocomplete suggestions. Is it possible this is related to using a glob import such as use super::*;?

Thanks @TedDriggs. Are they results you see identical? Maybe we can just hack around this by filtering dupes if they are 100% the same.

Yes, they appear to be identical (all 3 show the exact same path when highlighted)

I found and addressed one source of duplication in #774, so methods should no longer appear multiple times. However, I still see duplicate mod results when completing in the project I repro'd this in back in January, so I'll dig deeper into that.


Exit node relay/direct connection

I find that the exit node I have set up keeps reverting to a Relayed connection.
If I go into Home Assistant stop and start the Tailscale addon it will have a direct connection, but this does not last, so when it changes to a relayed connection the speed drops to under 1Mbps, with a direct connection it is 50-60 Mbps I have to stop and start the addon again.
Is there any way to make it have a direct connection all the time?
Thanks

Closing this. Release is expected soon. New base image and testing is left.
../Frenck

Thank you, I am quite new to this, when it is released will it show as an
update available in Home Assistant?
Regards Dennis
On Thu, 12 Sep 2024, 3:29 pm Franck Nijhof, @.***>
wrote:

Closing this. Release is expected soon. New base image and testing is left.
../Frenck
—
Reply to this email directly, view it on GitHub
https://github.com/hassio-addons/addon-tailscale/issues/403#issuecomment-2346288561,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5AEK7PACCWGC77JCM2FPLTZWGJLRAVCNFSM6AAAAABODA7GRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBWGI4DQNJWGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yes. :)


validation passing when required property is missing.

I'm trying to get validation to fail if property of cancelReason  or code is not provided, which you can see is not in the input. Not sure why validation is passing...
Input:
{
  "cancelPickup" : {
    "pickupNum": "12345"
  }
}

Path:
  /something/cancel2:
    post:
      summary: Dispatch
      description: >-
        Use this endpoint to cancel pickup request to a specified carrier.
      tags:
        - API
      parameters:
        - in: body
          name: body
          description: Cancel Request Payload
          required: true
          schema:
            $ref: "#/components/schemas/CancelRequest"
      responses:
        '200':
          description: Cancel Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CancelResponse'
        '400':
          $ref: '#/components/responses/SyntaxError'
        '401':
          $ref: '#/components/responses/UnauthorizedError'

Components:
components:
  schemas:
    CancelRequest:
      type: object
      properties:
        cancelPickup:
          description: cancel
          type: object
          oneOf:
            - $ref: "#/components/schemas/Cancel"
            - type: object
              required:
                - code
                - cancelReason

    Cancel:
      description: cancel
      type: object
      properties:
        code:
          description: code
          example:
          type: string
          require: true
          nullable: false
        proNum:
          description: pro number
          example:
          type: string
        pickupNum:
          description: pickup number
          example:
          type: string
        cancelReason:
          description: reason why the pickup should be canceled
          example: pickup made for wrong day
          type: string
          require: true
          nullable: false
      required:
        - code
        - cancelReason

Try making the cancelPickup property of the cancel component to define the component as
schema:
  $ref: '#/components/schemas/Cancel'

instead of a oneOf:

thanks for the reply @brhou .


Large-Scale Refactoring

The modules need to be refactored into the following structure

Media

Articles (rename to News)
Wiki

Guild

Chat (forthcoming)
Characters

Sessions

Contracts
Episodes

Configuration

Backgrounds
Professions
Races
Feats
Items
Spells (forthcoming)

The only one I'm not certain about is Guild. I want to also be able to include Shops, and I have no idea where that will go...

Maybe include a 'World' directory, which could contain shops, maps, cities, or something similar?

That's a good idea. I was trying to figure out how best to do that.

Would the World directory also contain NPCs?

Here's a better idea, IMO.
World
├── News
├── Wiki
├── NPCs
├── Cities (includes Maps, possible also includes ability to travel e.g. take an airship to Luïnden)
└── Shops

Guild
├── Characters
├── Episodes
└── Conversations
```

Hm.
I like Media being grouped with World, because then world-specific items all go in one place (unless characters only exist in a world?).  Would make it easier later on for other people if you're planning to release this tool for any DM :)
If it's not typical to include characters as intrinsically linked to a certain 'World', I think structure 1 is fine, because then World-Specifics are all together.
Otherwise, I think option 2 is better because then that illusion isn't being improperly maintained.


[FEATURE] Support routing to/from tagged data

Let's say you have a temperature sensor input in your firmware and want to simulate realistic thermal conditions. To do this, you'd likely have some type of thermal model that outputs a temperature value. We should have integrated support for routing the thermal model output to the temperature sensor's tagged data.
This signal router should be generalized and work for a variety of situations. For example:

Routing to/from a C variable
Routing to multiple tagged data

The routing should happen "on-change". So whenever the route input changes, the route output is updated.

Model Implementation:
Requirements

Since sim is single-threaded, the sim needs to call a function to update model outputs. I.e. model should implement some periodic function that the simulator can call.
Output (and input) data must support the same data types as tagged data
Models can be written in Python (simpler for test devs)
Must be able to route model outputs/inputs to/from tagged firmware data

Implementation

Add sim core feature for registering a model (callback + period). The callback will be called at the set period to update the model outputs. This could also register the model's inputs/outputs with the sim core so it knows the relevant tag names (+ data types)
On each tick, the signal router should update all signals based on defined routes


Feature.2.prototype stage n camera

Added placeholder tileset art for the ground
Added Grid + Tilemap to main scene
Added Cinemachine so it's easy to add a camera that follows the player
Added a virtual camera that will follow a placeholder player circle around at an angle
As mentioned in the task, the target of the camera is easy to change, just update the 'follow' and 'look at' parameters of the virtual camera:

Note:

Eyeballed the camera height + angle, so might need adjusting as we add assets with height. Also pretty chill to change c:

Closes #2

Love if we could use semantic commit titling, It's awesome for history readability. Read more on it here: https://www.conventionalcommits.org/en/v1.0.0/.
I'll also restrict PR's to squash-only so only PR titles matter.
The title for this could be feat: #2 Camera & Stage Prototype

But looks LGTM ^^

Branching conventions + semantic commits sound good to me! c:


unsuccessful "npm install"

Hi,
I’d like to play with mutt-hue-bridge in my setup ( rasbPI 2, esp8266/nodemcu etc. etc. ) but unfortunately I was not able to install it ( maybe my noob level about topic like node.js didn’t help :-( ).
In attach you’ll find the "npm install” result and below a short  description about my environment  :

raspi 2 / jarvis
node.js 4.3.1 / npm 2.14.12
mosquitto 1.4.8

Could you help me?
mqtt_err.txt

Hi iomax,
Awesome that you have a similar setup!
I just tried to do a fresh npm install, which works fine.
Although my node/npm versions on this machine are a bit behind,
I can check on another machine this weekend.
Could you try to set your locale to english for the logs, temporarily?
What operating system are you running?
I'm by no means an expert in node.js, these projects we're my first in Node, but i'd be glad to think with you on this issue.

Wow … thanks for your superfast reply !!! :-)
The RaspPI OS is Raspbian Jessie ( sorry I didn’t know why I named it “jarvis" in my previous msg. :-( ) and here attached the “english” version of the "npm install” outcome.
Thanks for your support
Ciao
max

Il giorno 04/mar/2016, alle ore 17:27, Dennis de Greef<EMAIL_ADDRESS>ha scritto:
Hi iomax,
Awesome that you have a similar setup!
I just tried to do a fresh npm install, which works fine.
Although my node/npm versions on this machine are a bit behind,
I can check on another machine this weekend.
Could you try to set your locale to english for the logs, temporarily?
What operating system are you running?
I'm by no means an expert in node.js, these projects we're my first in Node, but i'd be glad to think with you on this issue.
—
Reply to this email directly or view it on GitHub https://github.com/dennisdegreef/mqtt-hue-bridge/issues/2#issuecomment-192343253.

Sorry, the file … :-)

Il giorno 04/mar/2016, alle ore 18:40, GMail<EMAIL_ADDRESS>ha scritto:
Wow … thanks for your superfast reply !!! :-)
The RaspPI OS is Raspbian Jessie ( sorry I didn’t know why I named it “jarvis" in my previous msg. :-( ) and here attached the “english” version of the "npm install” outcome.
Thanks for your support
Ciao
max

Il giorno 04/mar/2016, alle ore 17:27, Dennis de Greef<EMAIL_ADDRESS><EMAIL_ADDRESS>ha scritto:
Hi iomax,
Awesome that you have a similar setup!
I just tried to do a fresh npm install, which works fine.
Although my node/npm versions on this machine are a bit behind,
I can check on another machine this weekend.
Could you try to set your locale to english for the logs, temporarily?
What operating system are you running?
I'm by no means an expert in node.js, these projects we're my first in Node, but i'd be glad to think with you on this issue.
—
Reply to this email directly or view it on GitHub https://github.com/dennisdegreef/mqtt-hue-bridge/issues/2#issuecomment-192343253.

osmc@c1p8:~$ cd mqtt-hue-bridge/
osmc@c1p8:~/mqtt-hue-bridge$ npm install

<EMAIL_ADDRESS>install /home/osmc/mqtt-hue-bridge/node_modules/mqtt/node_modules/websocket-stream/node_modules/ws/node_modules/bufferutil
node-gyp rebuild

make: ingresso nella directory "/home/osmc/mqtt-hue-bridge/node_modules/mqtt/node_modules/websocket-stream/node_modules/ws/node_modules/bufferutil/build"
CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
In file included from ../src/bufferutil.cc:16:0:
../node_modules/nan/nan.h:261:25: error: redefinition of ‘template v8::Local _NanEnsureLocal(v8::Local)’
NAN_INLINE v8::Local _NanEnsureLocal(v8::Local val) {
^
../node_modules/nan/nan.h:256:25: note: ‘template v8::Local _NanEnsureLocal(v8::Handle)’ previously declared here
NAN_INLINE v8::Local _NanEnsureLocal(v8::Handle val) {
^
../node_modules/nan/nan.h:661:13: error: ‘node::smalloc’ has not been declared
, node::smalloc::FreeCallback callback
^
../node_modules/nan/nan.h:661:35: error: expected ‘,’ or ‘...’ before ‘callback’
, node::smalloc::FreeCallback callback
^
../node_modules/nan/nan.h: In function ‘v8::Localv8::Object NanNewBufferHandle(char*, size_t, int)’:
../node_modules/nan/nan.h:665:50: error: ‘callback’ was not declared in this scope
v8::Isolate::GetCurrent(), data, length, callback, hint);
^
../node_modules/nan/nan.h:665:60: error: ‘hint’ was not declared in this scope
v8::Isolate::GetCurrent(), data, length, callback, hint);
^
../node_modules/nan/nan.h: In function ‘v8::Localv8::Object NanNewBufferHandle(const char*, uint32_t)’:
../node_modules/nan/nan.h:672:67: error: call of overloaded ‘New(v8::Isolate*, const char*&, uint32_t&)’ is ambiguous
return node::Buffer::New(v8::Isolate::GetCurrent(), data, size);
^
../node_modules/nan/nan.h:672:67: note: candidates are:
In file included from ../src/bufferutil.cc:10:0:
/home/osmc/.node-gyp/4.3.1/include/node/node_buffer.h:31:40: note: v8::MaybeLocalv8::Object node::Buffer::New(v8::Isolate*, v8::Localv8::String, node::encoding)
NODE_EXTERN v8::MaybeLocalv8::Object New(v8::Isolate* isolate,
^
/home/osmc/.node-gyp/4.3.1/include/node/node_buffer.h:31:40: note:   no known conversion for argument 3 from ‘uint32_t {aka unsigned int}’ to ‘node::encoding’
/home/osmc/.node-gyp/4.3.1/include/node/node_buffer.h:43:40: note: v8::MaybeLocalv8::Object node::Buffer::New(v8::Isolate*, char*, size_t)
NODE_EXTERN v8::MaybeLocalv8::Object New(v8::Isolate* isolate,
^
/home/osmc/.node-gyp/4.3.1/include/node/node_buffer.h:43:40: note:   no known conversion for argument 2 from ‘const char*’ to ‘char*’
In file included from ../src/bufferutil.cc:16:0:
../node_modules/nan/nan.h: In function ‘v8::Localv8::Object NanNewBufferHandle(uint32_t)’:
../node_modules/nan/nan.h:676:61: error: could not convert ‘node::Buffer::New(v8::Isolate::GetCurrent(), size)’ from ‘v8::MaybeLocalv8::Object’ to ‘v8::Localv8::Object’
return node::Buffer::New(v8::Isolate::GetCurrent(), size);
^
../node_modules/nan/nan.h: In function ‘v8::Localv8::Object NanBufferUse(char*, uint32_t)’:
../node_modules/nan/nan.h:683:12: error: ‘Use’ is not a member of ‘node::Buffer’
return node::Buffer::Use(v8::Isolate::GetCurrent(), data, size);
^
bufferutil.target.mk:90: set di istruzioni per l'obiettivo "Release/obj.target/bufferutil/src/bufferutil.o" non riuscito
make: *** [Release/obj.target/bufferutil/src/bufferutil.o] Errore 1
make: uscita dalla directory "/home/osmc/mqtt-hue-bridge/node_modules/mqtt/node_modules/websocket-stream/node_modules/ws/node_modules/bufferutil/build"
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 4.4.0-1-osmc
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/osmc/mqtt-hue-bridge/node_modules/mqtt/node_modules/websocket-stream/node_modules/ws/node_modules/bufferutil
gyp ERR! node -v v4.3.1
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok

<EMAIL_ADDRESS>install /home/osmc/mqtt-hue-bridge/node_modules/mqtt/node_modules/websocket-stream/node_modules/ws/node_modules/utf-8-validate
node-gyp rebuild

make: ingresso nella directory "/home/osmc/mqtt-hue-bridge/node_modules/mqtt/node_modules/websocket-stream/node_modules/ws/node_modules/utf-8-validate/build"
CXX(target) Release/obj.target/validation/src/validation.o
In file included from ../src/validation.cc:15:0:
../node_modules/nan/nan.h:261:25: error: redefinition of ‘template v8::Local _NanEnsureLocal(v8::Local)’
NAN_INLINE v8::Local _NanEnsureLocal(v8::Local val) {
^
../node_modules/nan/nan.h:256:25: note: ‘template v8::Local _NanEnsureLocal(v8::Handle)’ previously declared here
NAN_INLINE v8::Local _NanEnsureLocal(v8::Handle val) {
^
../node_modules/nan/nan.h:661:13: error: ‘node::smalloc’ has not been declared
, node::smalloc::FreeCallback callback
^
../node_modules/nan/nan.h:661:35: error: expected ‘,’ or ‘...’ before ‘callback’
, node::smalloc::FreeCallback callback
^
../node_modules/nan/nan.h: In function ‘v8::Localv8::Object NanNewBufferHandle(char*, size_t, int)’:
../node_modules/nan/nan.h:665:50: error: ‘callback’ was not declared in this scope
v8::Isolate::GetCurrent(), data, length, callback, hint);
^
../node_modules/nan/nan.h:665:60: error: ‘hint’ was not declared in this scope
v8::Isolate::GetCurrent(), data, length, callback, hint);
^
../node_modules/nan/nan.h: In function ‘v8::Localv8::Object NanNewBufferHandle(const char*, uint32_t)’:
../node_modules/nan/nan.h:672:67: error: call of overloaded ‘New(v8::Isolate*, const char*&, uint32_t&)’ is ambiguous
return node::Buffer::New(v8::Isolate::GetCurrent(), data, size);
^
../node_modules/nan/nan.h:672:67: note: candidates are:
In file included from ../src/validation.cc:10:0:
/home/osmc/.node-gyp/4.3.1/include/node/node_buffer.h:31:40: note: v8::MaybeLocalv8::Object node::Buffer::New(v8::Isolate*, v8::Localv8::String, node::encoding)
NODE_EXTERN v8::MaybeLocalv8::Object New(v8::Isolate* isolate,
^
/home/osmc/.node-gyp/4.3.1/include/node/node_buffer.h:31:40: note:   no known conversion for argument 3 from ‘uint32_t {aka unsigned int}’ to ‘node::encoding’
/home/osmc/.node-gyp/4.3.1/include/node/node_buffer.h:43:40: note: v8::MaybeLocalv8::Object node::Buffer::New(v8::Isolate*, char*, size_t)
NODE_EXTERN v8::MaybeLocalv8::Object New(v8::Isolate* isolate,
^
/home/osmc/.node-gyp/4.3.1/include/node/node_buffer.h:43:40: note:   no known conversion for argument 2 from ‘const char*’ to ‘char*’
In file included from ../src/validation.cc:15:0:
../node_modules/nan/nan.h: In function ‘v8::Localv8::Object NanNewBufferHandle(uint32_t)’:
../node_modules/nan/nan.h:676:61: error: could not convert ‘node::Buffer::New(v8::Isolate::GetCurrent(), size)’ from ‘v8::MaybeLocalv8::Object’ to ‘v8::Localv8::Object’
return node::Buffer::New(v8::Isolate::GetCurrent(), size);
^
../node_modules/nan/nan.h: In function ‘v8::Localv8::Object NanBufferUse(char*, uint32_t)’:
../node_modules/nan/nan.h:683:12: error: ‘Use’ is not a member of ‘node::Buffer’
return node::Buffer::Use(v8::Isolate::GetCurrent(), data, size);
^
validation.target.mk:90: set di istruzioni per l'obiettivo "Release/obj.target/validation/src/validation.o" non riuscito
make: *** [Release/obj.target/validation/src/validation.o] Errore 1
make: uscita dalla directory "/home/osmc/mqtt-hue-bridge/node_modules/mqtt/node_modules/websocket-stream/node_modules/ws/node_modules/utf-8-validate/build"
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR!  It coming from the mqtt version ... Changed the dependency in package.json with mqtt latest version ( from 1.1.3 to 1.7.3 ) and everything went as expected.
Thanks

Hi @iomax
Thanks for letting me know. Would you happen to know the cause of the issue? or what change set between those two versions is related?
I'll take a look at creating a pull request for bumping the version.

@iomax Could you let me know if the latest version is working on your end? I'll re-open the issue if it isn't.

Oh, Yes !!
With the latest mqtt version the installation went ok and now it's working whiteout issues.
Massimo

Il giorno 20 mar 2016, alle ore 14:15, Dennis de Greef<EMAIL_ADDRESS>ha scritto:
@iomax Could you let me know if the latest version is working on your end? I'll re-open the issue if it isn't.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub


What is the difference between the config for training WavTokenizer-small and WavTokenizer-large?

I am curious about what parts of the config need to be modified when WavTokenizer trains the Large version on a larger data set? Could you please give me a reference configuration? In addition, can you give a reference loss value regarding whether the model has converged during training, including the loss of generator and discriminator? I eagerly anticipate your response.

I am curious about what parts of the config need to be modified when WavTokenizer trains the Large version on a larger data set? Could you please give me a reference configuration? In addition, can you give a reference loss value regarding whether the model has converged during training, including the loss of generator and discriminator? I eagerly anticipate your response.

You can directly utilize the configuration of the small version to run the large version, although the increased data volume would typically necessitate a corresponding increase in model parameters. However, the WavTokenizer's parameter configuration already approaches 200M. If you have abundant computational resources, you can attempt to adjust the parameter quantity, and the encoder side can be further expanded. Moreover, it is recommended to evaluate the convergence based on the validation set. In our experiments, the generator's final loss converges to around 38, the discriminator's loss converges to around 10, and the total loss converges to around 25.

I am curious about what parts of the config need to be modified when WavTokenizer trains the Large version on a larger data set? Could you please give me a reference configuration? In addition, can you give a reference loss value regarding whether the model has converged during training, including the loss of generator and discriminator? I eagerly anticipate your response.

You can directly utilize the configuration of the small version to run the large version, although the increased data volume would typically necessitate a corresponding increase in model parameters. However, the WavTokenizer's parameter configuration already approaches 200M. If you have abundant computational resources, you can attempt to adjust the parameter quantity, and the encoder side can be further expanded. Moreover, it is recommended to evaluate the convergence based on the validation set. In our experiments, the generator's final loss converges to around 38, the discriminator's loss converges to around 10, and the total loss converges to around 25.

Thx!


Fix some hack description (Geode version)

Text Length (now it's same as Checkpoint Limit: "Removes the limit that deletes previous checkpoints after the 50th checkpoint")
Disable Camera Zoom (now it's same as Disable Camera Movement: "Disables camera movement via trigger")

thanks, will fix in the next version

fixed


Add formatting

Add Black formatter & CI check

i don't recommend having this big PR without having tests

i don't recommend having this big PR without having extensive tests. But from what i see if it is just quotes and line fitting, we can do it

Yes there is no logic changes. It is format

@dan8f could you please merge the other draft PR (with isort) into this one? Pls check my comments on the other one
We will squash merge and I would prefer to have all reformatting changes in a single commit.


Bug Report:

#Cutscene
pleasseeee fix thattttt aAaAa

Sorry but I'm going to need more information about what's wrong.

Sorry but I'm going to need more information about what's wrong.

i think theyre talking about how cutscenes wont work on desktop

If that's the case, I will not fix this bug, as this bug also occurs in original v0.2.8, and I'm not here to fix bugs that occur in the original game.

Closing due to inactivity.


Invoke 0.13.0 Update

Purpose

Update all task files for 0.13.0 compatibility

Changes

Updated all invoke tasks to take 'ctx' as first argument
In invoke tasks, replaced all mentions of run with ctx.run
Bumped version number of invoke to 0.13.0 in requirements.txt

Side effects

Tasks no longer compatible with earlier versions of invoke

Ticket

https://openscience.atlassian.net/browse/OSF-6492

Please go through the tasks and make sure that you are passing ctx to any task called within another task.

Pass finished.


PyQt5 fix proposal

for #27

if __name__ == '__main__':
    #m = app.launch(Twente, title='Temperature 1951 - 2014', size=(900, 400))
    m = app.launch(Twente, 'pyqt', title='Temperature 1951 - 2014', size=(900, 400))
    m.bgcolor('#eee')  # more desktop-like
    print(m.proxy._runtime)
    app.run()

Serving apps at http://localhost:54307/
<flexx.webruntime.qtwebkit.PyQtRuntime object at 0x00000000075CD588>
get Twente-43649b0/
get Twente-43649b0/flexx-ui.css
get Twente-43649b0/flexx.js
get Twente-43649b0/flexx-ui.js
new ws connection /Twente-43649b0/

the XUL version as not the  update proposal

Except the minor style issues this looks good. Thanks a lot!

The fact that you get Xul when no runtime is specified is intended. Xul is the default backend, because Qt Webkit is slower and does not support webgl.

I hoped there was going to be a modern Chromium motor in PyQt5.5.0/Qt5.5/Windows, so  performant.

Well, maybe it is. I'm not really sure about Qt5. But last time I checked at least webgl was not supported.

Thanks for the fix!


Possible to make it work with just an mp3 or wave file direclty?

Hello
I am just looking for a voice gender recognizer, can this be easily modified to receive just inputs as files audios?

Hello,
Please read the readme section carefully, the system works both with audio files and real-time voice inputs. All the steps required to make it functional WRT the input modes with shell commands, are all mentioned in the readme section.

Thanks for the quick answer @Ashutosh-Ardu , I tried to install it just right now, but I think it only works for windows?
I did the following:
py -m venv venvRGenderV
cd venvRGenderV
cd Scripts
activate
cd..
cd..
pip install -r requirements.txt
And got this error:
Collecting tensorflow (from -r requirements.txt (line 1))
  Obtaining dependency information for tensorflow from https://files.pythonhosted.org/packages/80/6f/57d36f6507e432d7fc1956b2e9e8530c5c2d2bfcd8821bcbfae271cd6688/tensorflow-2.14.0-cp311-cp311-win_amd64.whl.metadata
  Downloading tensorflow-2.14.0-cp311-cp311-win_amd64.whl.metadata (3.3 kB)
Collecting sklearn (from -r requirements.txt (line 2))
  Downloading sklearn-0.0.post10.tar.gz (3.6 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [18 lines of output]
      The 'sklearn' PyPI package is deprecated, use 'scikit-learn'
      rather than 'sklearn' for pip commands.

      Here is how to fix this error in the main use cases:
      - use 'pip install scikit-learn' rather than 'pip install sklearn'
      - replace 'sklearn' by 'scikit-learn' in your pip requirements files
        (requirements.txt, setup.py, setup.cfg, Pipfile, etc ...)
      - if the 'sklearn' package is used by one of your dependencies,
        it would be great if you take some time to track which package uses
        'sklearn' instead of 'scikit-learn' and report it to their issue tracker
      - as a last resort, set the environment variable
        SKLEARN_ALLOW_DEPRECATED_SKLEARN_PACKAGE_INSTALL=True to avoid this error

      More information is available at
      https://github.com/scikit-learn/sklearn-pypi-package

      If the previous advice does not cover your use case, feel free to report it at
      https://github.com/scikit-learn/sklearn-pypi-package/issues/new
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

How to fix this?

@Ashutosh-Ardu  I think because I am not on linux right? Because I saw this .tar.gz + read this (https://sebhastian.com/python-error-subprocess-exited-with-error/)
Could you make it available for windows users please?

@AIhasArrived, Sorry for responding so late. I will look into this issue

Hello @Ashutosh-Ardu , no problem as youmanage to make it work for wondows, I still needit!


Adds missing ":_" from Square.SqlDelight.coroutinesExtensions

Thank you!
FYI, I had noticed it (and worked around with concatenation in the Gradle build file), but didn't get to it because of WIP things (like revamping the Contributing guide, and other non doc related stuff).
I'm merging, hopefully we release it this month in 0.10.0.

I'm doing the same for my project, concatenating in the Gradle build file.
I know maintaining an open-source project is hard, thanks for your time and effort!


TypeScript busy/blocked when typing a new import

open a TypeScript file and JSON file from our workspace
make sure hovers in both work
in the TS file, type an import
😴 TypeScript is dead for ~45seconds, JSON still alive which hints to me there is a problem with tsserver

bump @mjbvz

Closing as duplicate of #20815


feat(clojure): add doctor.el for clj-kondo

I've added a doctor.el to the clojure module with a check for the clj-kondo binary, required by flycheck-clj-kondo.
I end up forgetting to install clj-kondo when setting up a new computer, and doom doctor has always been a friend.
Please let me know if there's anything that needs fixing - the warning text or other things - as this is my first contribution here :eyes:

I saw on discord we should actually target master right? :eyes:
Not sure it will work, let me see if just changing the base works...

Nope, bad idea. Will reopen the PR


[Testing Confirmation] Confirm current testing requirements

As part of the discussion around implementing an organization-wide testing policy, I am visiting each repo to see what tests they currently perform. I am conducting this work on GitHub so that it is easy to reference.
Looking at the k-NN repository, it appears there is

Repository
Unit Tests
Integration Tests
Backwards Compatibility Tests
Additional Tests
Link

k-NN
- [x]
- [x]
- [x]
Certificate of Origin, Link Checker, Documentation Request, Benchmarking Tool
https://github.com/opensearch-project/k-NN/issues/775

I don't see any requirements for code coverage in the testing documentation. If there are any specific requirements could you respond to this issue to let me know?
If there are any tests I missed or anything you think all repositories in OpenSearch should have for testing please respond to this issue with details.

@scrawfor99
Apart from this, we have used OpenSearch Benchmarks to do the benchmarking for this repo for every release. Probably this can be a thing that can be added for all the repos.

Hi @navneet1v, thank you for following up. I did not realize you had your own benchmarking tool. That sounds like a good option for something that could be included elsewhere as well. I will make a note of this.

@scrawfor99 just to clarify, we are using OpenSearch Benchmarking tool and our own created tool to do the benchmarking. Both of them are serving different purpose. Ideally we want to use one which is OpenSearch Benchmarks, but given that OpenSearch Benchmarks doesn't support custom metrics we had to create another tool.

Hi @navneet1v, thank you for the clarification. I will make sure to update the notes to show this distinction. I appreciate your follow-up.


requirement suggestion and more

it would be nice if the bot had a way to calculate [.](the netword and if they could put the gun comados inside the game like other bot can e.g. https://github.com/DuckySoLucky/hypixel-discord-chat-bridge/tree/main/src/minecraft/commands) but I use your bot and I like it a lot and I have it in my guild.

the bot does have some ingame commands just not a lot https://github.com/Altpapier/hypixel-discord-guild-bridge#ingame-commands
I may add networth to it in the future idk yet


Create mono and add SEO starter example

We can update the deployment path after the fact here: https://vercel.com/vercel/next-learn-starter


fix/test/docs: negative interval accumulation with spread rewards

Progress towards #5854
What is the purpose of the change
This PR fixes a negative interval accumulation edge case bug by simply replacing Sub with SafeSub where applicable.
The tests are extended to cover claiming rewards below, inside, and above the position after it is initialized.
Note, that incentive rewards still need to be tested and potentially fixed. This PR only covers spread rewards.
Testing and Verifying
The global invariants are asserted, and the tests ensure that the appropriate amount is claimed from all positions in all cases.
Documentation and Release Note

[ ] Does this pull request introduce a new feature or user-facing behavior changes?
[ ] Changelog entry added to Unreleased section of CHANGELOG.md?

Where is the change documented?

[X] Specification (x/{module}/README.md)
[ ] Osmosis documentation site
[X] Code comments?
[ ] N/A

Lgtm on first pass! Will review test changes in more detail later.

We may have to fix the osmoutils version if E2E fails


Ubuntu 18.04 pip fix

I have removed tensorflow from the setup.py installation procedure as that is causing installation to fail on Ubuntu 18.04 if tensorflow (or it might be because tensorflow-gpu is installed). The error message I kept getting was:

Collecting git+https://github.com/autonomio/talos.git@ubuntu-fix
  Cloning https://github.com/autonomio/talos.git (to revision ubuntu-fix) to /tmp/pip-req-build-ozwxerze
Branch 'ubuntu-fix' set up to track remote branch 'ubuntu-fix' from 'origin'.
Switched to a new branch 'ubuntu-fix'
    Complete output from command python setup.py egg_info:

    ----------------------------------------
Command "python setup.py egg_info" failed with error code -11 in /tmp/pip-req-build-ozwxerze/

Even when using the pip -vvv install  not meaningful came out of the messages.

Hello @C0NTRIBUTE! Thanks for submitting the PR.

There are no PEP8 issues in the file setup.py !

Pull Request Test Coverage Report for Build 266

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

Files with Coverage Reduction
New Missed Lines
%

talos/reducers/reduce_run.py
1
100.0%

talos/reducers/correlation.py
2
84.21%

Totals

Change from base Build 247:
0.0%

Covered Lines:
857

Relevant Lines:
1087

💛  - Coveralls


feat: load sentry DSN from meta tag

Must be merged with https://github.com/lenra-io/client/pull/53 and https://github.com/lenra-io/backoffice/pull/76
Checklist

[x] I didn't over-scope my PR
[x] My PR title matches the commit convention
[x] I did not include breaking changes
[ ] I included unit tests that cover my changes
[ ] I added/updated the documentation about my changes
[x] I made my own code-review before requesting one

Description of the changes

Technical highlight/advice

:tada: This PR is included in version 1.0.0-beta.34 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-beta.34 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


ARROW-9902: [Rust] [DataFusion] Add array() built-in function

This adds array() built-in function to most primitive types. For composite types, this is more challenging and I decided to scope out of this PR.

@jorgecarleitao please rebase

@jorgecarleitao do you already have followup plans for more array functions? some functions like array_first, array_last, array_index_of or array_contains` would be useful for me too.

This is pending #8108, as it requires a bug fix to pass the tests.

@jhorstmann , those are great suggestions!
I am not planning to work on that atm, as I wanted first to have an interface to declare UDFs with the same capabilities as built-in functions (#7967 and #8032).
However, please add them to the issue tracker. You are of course also welcome to take them, if you have the time. They seem to be good entry-level issues, but of course the devil is always in the details ^_^

@jorgecarleitao I plan on reviewing this one tomorrow.

@andygrove , I rebased and added a comment to improve readability of the array_str. Note that this conflicts with the Min/Max of a string, #8215 . Thank you for your patience here 🥇

@andygrove , I rebased and added a comment to improve readability of the array_str. Note that this conflicts with the Min/Max of a string, #8215 . Thank you for your patience here 1st_place_medal

Oh ... no, this is my bad, I was misreading the code. The comment helped though. Thank you!


Feat: Improve card design in either genre or literary realms

Describe the feature
Change UI of literary realms preferably since the genre section and literary realms contents are very very similar which makes the website looks too full of text and having repetitive content.
I wish to chnage the literary realms cards and add suitable animations to make them more attractive. I might add pop up animation or svgs to the cards and reduce text. The final UI is subject to our discussion after assigned
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Describe the feature
Change UI of literary realms preferably since the genre section and literary realms contents are very very similar which makes the website looks too full of text and having repetitive content.
I wish to chnage the literary realms cards and add suitable animations to make them more attractive. I might add pop up animation or svgs to the cards and reduce text. The final UI is subject to our discussion after assigned
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

assigned! tag me when you create a PR!

Somebody has already done this change, so I am adding better backgrounds and making the CSS better to remove wastage of space etc

I am the one who done the changes, and can add the effect on the GENRE cards and make it more efficient with div css and effect elements


SOS username and password missing

Checking https://github.com/geopython/OWSLib/blob/master/owslib/sos.py#L25 I see that username and password are missing while they are assigned in https://github.com/geopython/OWSLib/blob/master/owslib/swe/observation/sos200.py#L50
D

Hi @murdav,
I'm going to work with SOS and before I start I would like to fix some connected issues in OWSLib.
Please, can you give me some specification of this issue? When should username and password be required, some example of code or something? Because this issue doesn't seem so sophisticated to me, but it should be better to know all possibilities, because in other case it can also result in worse...

Hi @pesekon2,
I can certain link WMS username/password implementation:
https://github.com/geopython/OWSLib/blob/master/owslib/wms.py#L50
https://github.com/geopython/OWSLib/blob/master/owslib/map/wms130.py#L59
https://github.com/geopython/OWSLib/blob/master/owslib/map/wms130.py#L385
I simply saw that username and password were missing in the OWSLib SOS implementation. I would say it's an added point to have them when trying to access the getcapabilities if the requested service is using it.
@tomkralidis can give you (and me of course) more information?
D

@murdav / @pesekon2 I see username and password are implemented in owslib.swe.observation.sos100 and owslib.swe.observation.sos200, so it looks like owslib.sos.SensorObservationService needs updating to handle/pass these accordingly.

Hi,
I have created a fork of this repository and update the owslib.sos.SensorObservationService. I will make a pull request tonight after tests. There was just problem that SOS didn't provide username and password to further methods which have it implemented.
In case you have something more to do with SOS, please let me know and I would like to try to solve it.

Great @pesekon2. I would say that was I needed. Thanks again.

@murdav / @tomkralidis
I haven't find any issue with my patch. Pull request done here


Bot Framrwork Composer integration bug

Describe the bug

Version

Browser

[ ] Electron distribution
[ ✅ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[  ✅] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

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

Expected behavior

Screenshots

Additional context

Command failed: npm install --loglevel=error --save<EMAIL_ADDRESS>npm error code ETARGET npm error notarget No matching version found for<EMAIL_ADDRESS>npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete log of this run can be found in: /Users/tashviksrivastava/.npm/_logs/2024-12-09T11_10_51_827Z-debug-0.log

Be aware that the node runtime is still in preview. What version of botbuilder-dialogs-adaptive-runtime-integration-express are you running?


MMCV==1.5.0 is used but incompatible. Please install mmcv>=2.0.0rc4

how to solve this problem:
assert (mmcv_min_version <= mmcv_version < mmcv_max_version),
AssertionError: MMCV==1.5.0 is used but incompatible. Please install mmcv>=2.0.0rc4.

We use mmdet==2.24.0 and mmdet3d==1.0.0rc3 as shown in install-other-mm-packages, please check which package is causing this error and verify if the package version is correct. If you still encounter issues, feel free to contact me.

not solved

maybe it's mmseg's problem, I installed mmseg == 1.0.0, then the problem solved

maybe it's mmseg's problem, I installed mmseg == 0.28.0, then the problem solved

I think it is a common problem, I did not manage to solve it installing mmseg

Hello! I also have this issue and I believe that mmseg is the package that cause this. Could you please tell us the mmseg version you have used in your environment?


Add error check in get_ext(file_name) function in gdc.py

Hi,
The get_ext(filename) functions splits the filename on '.' and checks for extensions supported by a constant called _SUPPORTED_FILE_TYPES.
There is a case in which if the filename doesnt have any supported format available in the _SUPPORTED_FILE_TYPES array, in that case we are returning the format of the file which is not supported by our code. We should add an error check and return NULL or a default extension supported by _SUPPORTED_FILE_TYPES array incase the filename doesnt have a valid ext supported by our code.

@jingchunzhu

Thanks @arp95. I'll look into it and see which one of None and default is better.

Hello, I would like to fix the issue with the function, whats the procedure to push my branch ? Thanks in advance.

Thank you for your interests and PR, @Ayoob7 . This issue is a little bit special. The bottom line is it is not a bug but can use some improvements in coding and documentation.
If I remember it correctly, back in the day, GDC has some files named with only UUID which I found not useful to me and decided to rename them while downloading. So if you check the use of get_ext, you would find that they are used for constructing the new filename. Here is why I have this function and how I'd like it to work:
Say we have a file named "uuid.txt.tar.gz", I want to keep all the "txt.tar.gz" part and replace uuid with some meaningful name, say becoming "patient1_cancer.txt.tar.gz" not "patient1_cancer.gz". So get_ext should return "txt.tar.gz". This is important because if you unzip and extract the file, you can and should still have a "txt" extension. This is why I didn't simply keep the last postfix, "gz", but has get_ext to return that joint string. For what @arp95 has mentioned, say txt, tar and gz are not supported. So the filename doesn't have any supported format available, it will return the last postfix, gz, which is not "supported". Yes indeed but it is what I want. I want to get at least the last part rather than nothing because I want an extension no matter what. In another word, get_ext would check filename from left to right and return as soon as it found a recognized extension type and if none of them is recognized it should return the last one so that I have a relevant extension for file renaming rather than nothing. In this sense, I say it is not a bug because it functions as I want.
That being said, this issue can be improved. Either it should not be called "supported" but something else like "recognized" and documented clearly, or the whole file downloading and renaming part should be rewrite. In my opinion, those are directions this issue should go.
I'll close #7 for now but feel free to comment or submit new PR if you have any suggestions. Again, thank you both for your interests.


Add a basic testing framework to the CLI

Description
It would be nice if there were a command such as typst test that allows to run visual regression tests for a package, similar to cargo test. The main motivation for this is that I saw some packages such as tablex or cetz have their own implementations of regression tests, so I think it would be great if we could unify this in some way so that not every package creator has to roll their own testing system.
I think a good start would be to just include visual regression tests (since this shouldn't be that difficult to implement either), and at a later state we can also think about how Typst code itself could be tested as well.
Use Case
See above.

For reference: Cetz uses a shell-script https://github.com/johannes-wolf/cetz/blob/master/scripts/test which looks for tests (test.typ files), compiles them to PNG and compares them against a reference image (ref.png, next to the test file) using ImageMagick. On failure, a difference image is stored next to the test.

I think we wouldn't even need something like ImageMagick, we can just use Typst's native PNG export. This does mean that SVG and PDF won't be tested, but from the perspective of a package author this is irrelevant, since if there are discrepancies between the output formats it's upon us to fix this, and not the author.

As I understand it, cetz's tests do use PNG export. ImageMagick is only used for the comparison.

Ah, right. But I think we can just use a pixel-comparison based approach, similar to how it's done in svg2pdf, and create diff images in case there are any discrepancies.

So, here are is a first suggestion for how it might look like:
We introduce a new sub command typst test that allows to test a package. It provides the following options:
Running tests
In order to run the tests, you can in principle just run the command above. What will happen is that it will go through all of the test files, generate an image from them and compare them against the reference image. If they match, the test passes, if not it fails. If no corresponding reference image was found, the test will be marked as skipped. If a test fails, a diff image will be generated that can be inspected.
In addition, the following parameters are supported:
--font-path: Provide a path to a directory of fonts that should be included. typst test will by default only use the fonts embedded in the CLI but not system fonts, so as to ensure reproducibility across different platforms, for example in a GitHub CLI.
--exact: Only run the tests whose filename matches the pattern.
--tests-dir: The path to the folder containing the tests. By default 'tests'
Reference images
--update: Updates all currently existing reference images. You can additionally pass a pattern to only match files that match the pattern.
--generate: Generates reference images for all test files that don't have any yet. As above, you can additionally pass a pattern.
Folder structure
This is how the folder structure could look like:
.
└── MyPackage/
    ├── main.typ
    ├── helper.typ
    └── tests/
        ├── assets/
        │   └── some_stuff.json
        ├── ref/
        │   ├── numeric/
        │   │   ├── addition.png
        │   │   └── subtraction.png
        │   └── text/
        │       └── format.png
        ├── src/
        │   ├── numeric/
        │   │   ├── addition.typ
        │   │   └── subtraction.typ
        │   └── text/
        │       └── format.typ
        └── diff/
            └── numeric/
                └── addition.png

Inside of the tests folder, there needs to be another src folder which contains all of the test cases.
The root folder will be wherever typst test was invoked, so the intended usage is that you would invoke typst test inside MyPackage and then can just do #import "/main.typ in each test file to import the actual package. If you want to include assets, you could place them inside of the test folder as well and then include them by something like ../../assets/some_stuff.json.
Discussion points

Something I don't like about the approach mentioned above is that the folder structure is still kind of rigid, i.e. the user has to put their tests inside of the src folder for them to be detected. I guess we could also change it so that any .typ files found in the tests folder will be considered, but then it's a bit hard to figure out where to store the reference images. Should they be stored inside of the same folder as the original .typ file instead of a completely separate ref that mirrors the directory structure?
I think in the ideal case, we could make use of typst.toml in the future to allow configuring such settings inside of that file instead of having to provide them all as arguments in the CLI. However, since Typst doesn't have a notion of a "project" (yet?), we probably can't really make use of that now.

Any ideas? @andreasKroepelin @PgBiel @johannes-wolf  since you all have bigger libraries that probably could profit from such a feature, feel free (but not obliged!) to let me know what you think of that proposal.

I like that proposal a lot! What exactly would a diff image be? I have seen interactive diff viewers for images but how would one show the diff in a static image?

I like that proposal a lot! What exactly would a diff image be? I have seen interactive diff viewers for images but how would one show the diff in a static image?
Basically something like this:

@LaurenzV The only advantage of having Typst becoming a test-runner is that it could use a “warmed up” compiler with memoization shared across tests.
I think running tests can be handled better by external scripts, because implementing all this into Typst + running tests in parallel + image diffing + … might be a bit of a stretch.
Other tools can do this perfectly fine, atm. GNU parallel + ImageMagick, …
Re-Implementing such functionality insides Typst seems less flexible to me. I suggest having an external project that provides some scripts for handling tests instead of having this in the Typst binary.

Fair enough! Although I personally do think that there is a lot of value in having a standardized and streamlined way of testing your packages integrated into Typst. It would be much more convenient if it would just work with the existing binary instead of having to install yet another program. I also don't think it needs to be anything fancy, e.g. image diffing can be implemented pretty easily, similar to how we have it in svg2pdf.
But I do agree that I'm also not sure whether it should really be part of the typst binary, maybe in the long run there should be a separate program similar to cargo that contains additional modules (such as testing, formatting, etc.). Not sure. I guess in the end it's up to @laurmaedje to decide.

Basically something like this:

What am I seeing here? 😅

What am I seeing here? 😅

On the very left you see the reference image, on the very right the actual output, and in the middle the difference between the two.

But I do agree that I'm also not sure whether it should really be part of the typst binary, maybe in the long run there should be a separate program similar to cargo that contains additional modules (such as testing, formatting, etc.).

Just wanted to quickly comment on this: In general, I wouldn't want a second official binary. I don't see the value in splitting things up across two binaries.

Oh, I assume those are red and green areas then? Sorry, those are often difficult to distinguish for me 😅

Oh yeah, sorry, maybe the example was chosen badly. 😅 Basically on the left you can see a green SVG image, on the right you can see the same one but slightly different, and in the middle you see red lines that indicate where the images on the left and right differ.

But I'm also starting to think that maybe for now I will start a separate project (similar to typstfmt) as a kind of playground to see what's possible and what makes sense, and maybe at some point it can then be merged into the official binary.

Will close this, since there is typst-test now and I'm not convinced anymore that this should be part of the CLI.


Add EU support to diagnostics

Please also output region and language in this module for payment and login

Updated to output API region and Magento locale (1.4 branch).


Terminal Key support

Describe the bug
Terminal return key triggers escape extra-key on hardware keyboard
To Reproduce
Steps to reproduce the behavior:

Go to 'terminal'
Click on 'return key (unexpected keyboard2) '
Scroll down to ''
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
complete the following information):
Device
Board: 	NEN
Codename: 	REL
Device Name: 	HUAWEI NEN-LX1
Hardware: 	qcom
ID: 	HUAWEINEN-LX1
Manufacture: 	HUAWEI
Model: 	NEN-LX1
Product: 	NEN-L01CQ
System
API Level: 	29
Android: 	10
Kernel: 	4.19.95+
Preview SDK: 	0
Security Patch Level: 	2020-07-01
VM Version: 	ART 2.1.0
CPU
ABI: 	arm64-v8a
CPU Freq: 	4 x 2016MHz - 300MHz 4 x 1804MHz - 300MHz
CPU cores: 	8
Memory
Low Ram device: 	false
Ram: 	5700 MB
Display
Ratio: 	11:5
Resolution: 	1080 x 2376
xdpi / ydpi: 	398 / 392 dpi
Features
Bluetooth: 	true
GPS: 	true
NFC: 	true
Software
WebView Implementation: 	Huawei WebView <IP_ADDRESS>3

fixed https://github.com/RohitKushvaha01/Xed-Editor/actions/runs/10137404987#artifacts


docs: explain pwa head/manifest icons

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[x] Docs
[ ] Underlying tools
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

Other information:
Closes #5407

I'm not really sure what's causing the AppVeyor failure.

It's removed in 4.4.0? https://github.com/vuejs/vue-cli/commit/6323b73260e461c4aeb866fde4231f15d19f9c4e#diff-122632498f7fe7afa2fc01595a67e13c

/cc @sodatea

That commit was generated by lerna. Really unexpected that it would ever change code other than the version numbers and changelog.

It was removed again ?

Added back. Still confused 😕

🤷🏻 I can redo this PR on a fresh branch if that will help

Seems to be live now (finally 😂) 👍

I am trying to see the new icon for my homescreen app and it does not change unless I reinstall. Am I missing something? Thank you.
This is my vue.config:
pwa: {
name: "MyApp",
themeColor: "#000000",
msTileColor: "#000000",
appleMobileWebAppCapable: "yes",
appleMobileWebAppStatusBarStyle: "black",
assetsVersion: "1.2",
iconPaths: {
favicon32: "img/icons2/favicon-32x32.png",
favicon16: "img/icons2/favicon-16x16.png",
appleTouchIcon: "img/icons2/apple-touch-icon-152x152.png",
maskIcon: "img/icons2/safari-pinned-tab.svg",
msTileImage: "img/icons2/msapplication-icon-144x144.png",
},
manifestOptions: {
icons: [
{
src: "./img/icons2/android-chrome-192x192.png",
sizes: "192x192",
type: "image/png",
},
{
src: "./img/icons2/android-chrome-512x512.png",
sizes: "512x512",
type: "image/png",
},
{
src: "./img/icons2/android-chrome-maskable-192x192.png",
sizes: "192x192",
type: "image/png",
},
{
src: "./img/icons2/android-chrome-maskable-512x512.png",
sizes: "512x512",
type: "image/png",
},
{
src: "./img/icons2/apple-touch-icon-60x60.png",
sizes: "60x60",
type: "image/png",
},
{
src: "./img/icons2/apple-touch-icon-76x76.png",
sizes: "76x76",
type: "image/png",
},
{
src: "./img/icons2/apple-touch-icon-120x120.png",
sizes: "120x120",
type: "image/png",
},
{
src: "./img/icons2/apple-touch-icon-152x152.png",
sizes: "152x152",
type: "image/png",
},
{
src: "./img/icons2/apple-touch-icon-180x180.png",
sizes: "180x180",
type: "image/png",
},
{
src: "./img/icons2/apple-touch-icon.png",
sizes: "180x180",
type: "image/png",
},
{
src: "./img/icons2/msapplication-icon-144x144.png",
sizes: "144x144",
type: "image/png",
},
{
src: "./img/icons2/mstile-150x150.png",
sizes: "150x150",
type: "image/png",
},
],
},


Ensure pthread is linked in when building for ppc64le.

This problem is a variation of #7302.

tested as part of #8053 and its all green


deluge fails to start with python error "pyasn1 0.6.0 ... requirement 'pyasn1<0.6.0,>=0.4.6'"

Describe the bug
deluge builds but fails to run due to a runtime package versioning problem.  I did a git bisect and commit 2544167a82ff99e00a8de68fa529701a30648128 introduced this problem.
Steps To Reproduce
> git checkout 2544167a82ff99e00a8de68fa529701a30648128
> nix-shell -I nixpkgs=. -p deluge --run 'deluge -v'
Traceback (most recent call last):
  File "/nix/store/4kn81r47yfvciivmr5xyyia2ijrm6v4d-python3.11-deluge-gtk-2.1.1/bin/..deluge-wrapped-wrapped", line 9, in <module>
    sys.exit(start_ui())
             ^^^^^^^^^^
  File "/nix/store/4kn81r47yfvciivmr5xyyia2ijrm6v4d-python3.11-deluge-gtk-2.1.1/lib/python3.11/site-packages/deluge/ui/ui_entry.py", line 39, in start_ui
    ui_entrypoints[entrypoint.name] = entrypoint.load()
                                      ^^^^^^^^^^^^^^^^^
  File "/nix/store/07p7lg2s9q9zs4n7lh21p01bwkx99ixj-python3.11-setuptools-69.5.1/lib/python3.11/site-packages/pkg_resources/__init__.py", line 2481, in load
    self.require(*args, **kwargs)
  File "/nix/store/07p7lg2s9q9zs4n7lh21p01bwkx99ixj-python3.11-setuptools-69.5.1/lib/python3.11/site-packages/pkg_resources/__init__.py", line 2504, in require
    items = working_set.resolve(reqs, env, installer, extras=self.extras)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/nix/store/07p7lg2s9q9zs4n7lh21p01bwkx99ixj-python3.11-setuptools-69.5.1/lib/python3.11/site-packages/pkg_resources/__init__.py", line 798, in resolve
    dist = self._resolve_dist(
           ^^^^^^^^^^^^^^^^^^^
  File "/nix/store/07p7lg2s9q9zs4n7lh21p01bwkx99ixj-python3.11-setuptools-69.5.1/lib/python3.11/site-packages/pkg_resources/__init__.py", line 844, in _resolve_dist
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (pyasn1 0.6.0 (/nix/store/ld3ywvbk19575dc04dqlzzb55jyc3gs9-python3.11-pyasn1-0.6.0/lib/python3.11/site-packages), Requirement.parse('pyasn1<0.6.0,>=0.4.6'), {'pyasn1-modules'})

Expected behavior
> git checkout 1aae0909b02ffb4d0d4a45db322df7a8c9fdd34e
> nix-shell -I nixpkgs=. -p deluge --run 'deluge -v'
.deluge-wrapped 2.1.1
libtorrent: <IP_ADDRESS>
Python: 3.11.9
OS: Linux 6.6.29

Notify maintainers

@vcunat, @domenkozar, @ebzzry

The error was surely not introduced by this commit in particular.  I'd guess some a bit earlier commit (probably f9e5f5d9d6e0), but I don't expect it makes that much difference.

Thanks @vcunat, yes f9e5f5d9d6e079b133ba8ae810eeb08438e0e16b looks very suspicious given the error message.  I don't know enough about python packaging to determine what needs to be updated for deluge specifically though; @domenkozar, @ebzzry, could you please take a look?


refactor(services): misc services API refactor

PR Checklist
If you have any questions, you can refer to the Contributing Guide
What is the current behavior?
refactor misc services layer API, next step we need to do more test and refactor current collection & will & subscription model.
Issue Number
None.
What is the new behavior?
None.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Specific Instructions
Are there any specific instructions or things that should be known prior to review?
Other information

CI Failed.

@ysfscream PTAL :)


shared folders between host and container

Can you create a container with shared folders between host and container?
Thank you

Worked for me on Docker Toolbox and Docker for Windows:
...
List binds = new ArrayList<>();
binds.add("//c/Users:/logs");
Map<String, Object> volumes = new HashMap<>();
volumes.put("/logs", null);
HostConfig hostConfig = new HostConfig();
hostConfig.setBinds(binds);
ContainerCreateResponse container = client.container().createNew()
.withImage(imageName)
.withName(containerName)
.withEnv(envVariable)
.withHostConfig(hostConfig)
.withVolumes(volumes)
.withAttachStderr(true)
.withAttachStdout(true)
.done();


Incorrect template-literal parsing when interpolation is followed by element with event handler

The following script, when executed in a document with an element whose ID is app, demonstrates what is probably a bug. It should result in a div element, containing
A
 followed by <button>Button</button>. The button element, when clicked, should log a click event to the console.
Instead, the button element is <button on-click="


Addon uses GridHelper feature that is not compatible with Vaadin 24

See FlowingCode/GridHelpers#36

Upstream issue has been fixed and will be released in grid-helpers 0.3.2


not pulling image from docker hub

I don't think it is correctly pulling the image down and is just running on local system.

My login is not root but is part of the docker group..the image has been pulled down manually.

...but bunny is working if I manually docker exec -it /bin/bash and run the cwl.json inside the container.

This should be fixed with the v0.4.0-alpha release. If you are pulling private docker image you should do a docker login on particular registry before running.


Expand Pull Request Comments Functionality

Nothing crazy here, just expanding Bitbucket\Api\Repositories\Users\PullRequests\Comments to allow for creating, updating, and deleting pull request comments.

Thanks for this. This will be included (in some form) in the v2.0.0 release. :)


Allow specifying user credentials and registry url (ACR scenario)

Checked w/ @mmitche , got OK to merge.


Retile space if non-focused window is minimized

Improve the handling around window not visible event:

If removed window is not the focused window, don't try to change focus to a nearby window
Always, retile the removed window's space. Before we were relying on the change focus event to trigger a space retile.
Don't change focus to a nearby window (in old space) when moving a window to a new space.

Should fix #36


feat(distributor): Automatically determine DISTRIBUTOR_VERSION for uniform registration

This PR

adds automatic detection of DISTRIBUTOR_VERSION for distributor
Removes DISTRIBUTOR_VERSION from helm charts

Notes
Slack discussion: https://keptn.slack.com/archives/CGS63H8G6/p1645091419610049

Closing this as there seems to be no interest of Keptn Core to help me.