dbots.js icon indicating copy to clipboard operation
dbots.js copied to clipboard

Published 20 hours ago • verified publisher icon dbots-pkg

chore(deps-dev): bump @discordjs/collection from 1.5.3 to 2.1.0

Open dependabot[bot] opened this issue 1 year ago • 7 comments
trafficstars

Bumps @discordjs/collection from 1.5.3 to 2.1.0.

Release notes

Sourced from @​discordjs/collection's releases.

@​discordjs/collection@​2.1.0

Bug Fixes

Documentation

  • Split docs.api.json into multiple json files (597340f)

Features

  • Local and preview detection (79fbda3)

Refactor

@​discordjs/collection@​2.0.0

Documentation

Features

  • Return entries instead of values in toJSON method (#9345) (defeee5)
  • Align some methods with the Change By Copy proposal (#9207) (65966ae)
    • BREAKING CHANGE: The sorted method has been renamed to toSorted
  • Align some methods with the Set Methods proposal (#8890) (3b8df63)
    • BREAKING CHANGE: The intersect method has been renamed to intersection
    • BREAKING CHANGE: The difference method has been renamed to symmetricDifference
    • BREAKING CHANGE: The subtract method has been renamed to difference
  • Support findLast and reduceRight methods (#9573) (ac64508)
Changelog

Sourced from @​discordjs/collection's changelog.

@​discordjs/collection@​2.1.0 - (2024-05-04)

Bug Fixes

Documentation

  • Split docs.api.json into multiple json files (597340f)

Features

  • Local and preview detection (79fbda3)

Refactor

@​discordjs/collection@​2.0.0 - (2023-11-12)

Documentation

Features

  • Return entries instead of values in toJSON method (#9345) (defeee5)
  • Align some methods with the Change By Copy proposal (#9207) (65966ae)
    • BREAKING CHANGE: The sorted method has been renamed to toSorted
  • Align some methods with the Set Methods proposal (#8890) (3b8df63)
    • BREAKING CHANGE: The intersect method has been renamed to intersection
    • BREAKING CHANGE: The difference method has been renamed to symmetricDifference
    • BREAKING CHANGE: The subtract method has been renamed to difference
  • Support findLast and reduceRight methods (#9573) (ac64508)
Commits

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

dependabot[bot] avatar Jun 01 '24 02:06 dependabot[bot]

So this falls under a wider topic we have about custom session_ids. It was also identified in our #3094 MLOps research.

We have a weird constraint that session_id/versioning needs to be sortable but I still think a composite key of label_{timestamp} would be helpful here.

datajoely avatar Jul 26 '24 12:07 datajoely

Giving some human label would be great. That way we can do things like "look at the pubmedbert-v3 run" instead of having to juggle date strings.

I'd prefix the date to make the sort easier though

pascalwhoop avatar Jul 26 '24 17:07 pascalwhoop

As stated, we need to ensure a date_prefix so the order is maintained, adding a suffix should be fine. I am pro for this as I have need for this many years ago, can we link this to the versioning research at least?

https://github.com/kedro-org/kedro/issues/3997 @iamelijahko

noklam avatar Aug 27 '24 13:08 noklam

just for your UX research transparency, we now completely moved away from versioning and instead have a RUN_ID env variable that we pick up in globals.yaml and prefix all pipeline paths with that. we found this approach (all data of a version bundled under one path) to be preferable.

Pascal

On Tue, Aug 27, 2024 at 3:53 PM Nok Lam Chan @.***> wrote:

As stated, we need to ensure a date_prefix so the order is maintained, adding a suffix should be fine. I am pro for this as I have need for this many years ago, can we link this to the versioning research at least?

#3997 https://github.com/kedro-org/kedro/issues/3997 @iamelijahko https://github.com/iamelijahko

— Reply to this email directly, view it on GitHub https://github.com/kedro-org/kedro/issues/4028#issuecomment-2312629986, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARN3F3DRA6TFFHCGHWM6Y3ZTSAG5AVCNFSM6AAAAABLMKSRO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJSGYZDSOJYGY . You are receiving this because you authored the thread.Message ID: @.***>

--

The contents of this email are confidential and intended only for the intended recipient. If you are not the intended recipient or responsible for delivery of the message to such person, you may not use, copy, distribute or deliver this message or any part of its contents to anyone, or take any action in reliance on it. If you have received this email in error, please immediately notify the sender and then permanently delete this message. The views, opinions, conclusions and other information provided herein are not intended to be and should not be interpreted as medical advice. Please consult your physician for all medical advice.

pascalwhoop avatar Aug 28 '24 13:08 pascalwhoop

@pascalwhoop It's unlikely that we add this feature for now (especially since there's a reasonable workaround) so @ankatiyar will check to what extent something like this is possible with DVC and we'll turn this into a Discussion.

astrojuanlu avatar Feb 03 '25 16:02 astrojuanlu

I looked into it with DVC, and you can indeed tag versions (but with git). The docs for "Kedro + DVC" integration are under construction 🚧 but and should be out soon but you can refer to this comment or this coffee chat

The versioning in DVC is tied to git commits but you can tag the commits with a label eg.

git add data.dvc model.weights.h5.dvc metrics.csv .gitignore
git commit -m "First model, trained with 1000 images"
git tag -a "v1.0" -m "model v1.0, 1000 images"

And then train a second version and commit this too

git add data.dvc model.weights.h5.dvc metrics.csv
git commit -m "Second model, trained with 2000 images"
git tag -a "v2.0" -m "model v2.0, 2000 images"

And go back to a previous version like this

git checkout v1.0
dvc checkout

ETA: Example above from this DVC tutorial: http://dvc.org/doc/use-cases/versioning-data-and-models/tutorial#tutorial-data-and-model-versioning

ankatiyar avatar Feb 05 '25 16:02 ankatiyar

Giving some human label would be great. That way we can do things like "look at the pubmedbert-v3 run" instead of having to juggle date strings.

I'd prefix the date to make the sort easier though

Datetimes are appealing. They can readily be considered within ppl's emails and calendars, or the dates of reports and other artifacts. Also, datetimes can be loaded into Python and used for other purposes.

galenseilisnh avatar Apr 04 '25 23:04 galenseilisnh