[BUG][Server] WARN Plugin 'GriefDefender' is creating timing - this is deprecated behavior, please report it to the authors:

I'm using Grief Defender version 2.3.5
Please tell how to fix these lines in console that I see every time I start my server:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimflagdefinitiongroup' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimflagdefinitionplayer' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: cfg' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: cfp' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: cfr' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimgreeting' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimgroupadmin' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimgroupadmin join' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimgroupadmin unjoin' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimgroupadmin create' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimgroupadmin delete' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gd claimgroup admin claimgroup admin join' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gd claimgroup admin claimgroup admin unjoin' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gd claimgroup admin claimgroup admin create' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gd claimgroup admin claimgroup admin delete' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimgroup' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimgroup join' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimgroup unjoin' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimgroup create' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimgroup delete' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gd claimgroup' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gd claimgroup claimgroup player join' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gd claimgroup claimgroup player unjoin' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gd claimgroup claimgroup player create' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gd claimgroup claimgroup player delete' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimgui' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimid' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimignore' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claiminfo' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claiminherit' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claiminspect' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimlist' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claim' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimnotifications' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: cod' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: cog' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: cop' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: cpg' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: cpp' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimrent' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimreserve' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimschematic' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimsell' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: sellclaim' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimsetspawn' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimsnapshot' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimsnapshot create' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimsnapshot delete' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimsnapshot apply' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gd snapshot' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gd snapshot create' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gd snapshot delete' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gd snapshot apply' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimspawn' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: modesubdivide' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimtax' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimtitle' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimtool' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: modetown' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimtransfer' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: claimunban' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gdwe' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: ct' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gddebug' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gdblocktransfer' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gdconfirm' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gdreload' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gdversion' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: givepet' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gd help' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gd:pagination' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: gdplayerinfo' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: restoreclaim' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: modenature' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: scb' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: townchat' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: towntag' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: transferblocks' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: trapped' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: trustgroup' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: trust' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: trustallgroup' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: trustallgroupadmin' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: trustall' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: unlockdrops' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: untrustgroup' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: untrust' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: untrustallgroup' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: untrustallgroupadmin' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: untrustall' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'Command: trustlist' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] INFO [GriefDefender] Loaded successfully.
09.05 04:10:31 [Server] WARN **** SERVER IS RUNNING IN OFFLINE/INSECURE MODE!
09.05 04:10:31 [Server] WARN The server will make no attempt to authenticate usernames. Beware.
09.05 04:10:31 [Server] WARN While this makes the game possible to play without internet access, it also opens up the ability for hackers to connect with any username they choose.
09.05 04:10:31 [Server] WARN To change this, set "online-mode" to "true" in the server.properties file.
09.05 04:10:31 [Server] INFO Preparing level "world"
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onBlockBreak' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onBlockCollide' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onBlockNotify' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onBlockPlace' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onBlockPost' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onBlockPre' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onEntityExplosionPre' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onEntityExplosionDetonate' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onEntityAttack' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onEntityCollide' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onEntityDamage' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onEntityDamageMonitor' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onEntityDeath' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onEntityDropDeathItem' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onEntityMount' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onEntityMove' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onEntitySpawnPre' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onEntitySpawn' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onEntityTeleport' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onPlayerChangeHeldItem' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onPlayerChat' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onPlayerCommand' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onPlayerDeath' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onPlayerDispenseItem' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onPlayerLogin' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onPlayerHandleShovelAction' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onPlayerInteractBlockPrimary' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onPlayerInteractBlockSecondary' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onPlayerInteractEntityPrimary' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onPlayerInteractEntitySecondary' - this is deprecated behavior, please report it to the authors:
09.05 04:10:31 [Server] WARN Plugin 'GriefDefender' is creating timing 'onPlayerInteractInventoryClick' - this is deprecated behavior, please report it to the authors:
09.05 04:10:32 [Multicraft] Skipped 24 lines due to rate limit (160/s)

timings were removed from GriefDefender 2.3.7 onwards, when paper actually stopped using them.


When I run transcribe_minimal with -fw it gives me an error and doesn't complete

Loaded Faster-Whisper large-v2 model
Traceback (most recent call last):
File "/home/anonymous/anaconda3/envs/stable-ts/bin/stable-ts", line 8, in
sys.exit(cli())
File "/home/anonymous/anaconda3/envs/stable-ts/lib/python3.10/site-packages/stable_whisper/whisper_word_level.py", line 1606, in cli
transcribe_method = getattr(model, transcribe_method)
AttributeError: 'WhisperModel' object has no attribute 'transcribe_minimal'
it works as expected without -fw . is this a bug? is this the expected outcome? is there anything I can do to make these work together?

That is expected. There is only one transcription method supported for faster-whisper models and it is equivalent to transcribe_minimal() on the normal models (i.e. both are wrappers for transcribe_any()).


fix: OpenAPI URL

Added baseUrl to the URL to fetch the OpenAPI YAML correctly.

@lucas-janon @andresaiello can you, please, reivew. I want to be able to fix OpenAPI browser.


Revamping rekor e2e - part 1 of N

Summary
Refactoring e2e tests.
There will be multiple PRs to move the e2e to specific folders. Some code is duplicated up until all the e2e code is refactored.
https://github.com/sigstore/rekor/issues/1075
Release Note
NONE
Documentation
NONE

Does this still generate appropriate code coverage after https://github.com/sigstore/rekor/pull/1071 @cdris ?

Codecov Report

Merging #1089 (9d4b236) into main (4b1fa66) will decrease coverage by 0.88%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1089      +/-   ##
==========================================
- Coverage   63.82%   62.93%   -0.89%
==========================================
  Files          82       82
  Lines        7593     7593
==========================================
- Hits         4846     4779      -67
- Misses       2121     2208      +87
+ Partials      626      606      -20

Flag
Coverage Δ

e2etests
46.31% <ø> (-2.31%)
:arrow_down:

unittests
40.84% <ø> (-0.03%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/types/tuf/tuf.go
37.03% <0.00%> (-29.63%)
:arrow_down:

pkg/types/tuf/v0.0.1/entry.go
41.22% <0.00%> (-20.82%)
:arrow_down:

pkg/pki/factory.go
77.77% <0.00%> (-5.56%)
:arrow_down:

pkg/pki/tuf/tuf.go
51.80% <0.00%> (-3.62%)
:arrow_down:

cmd/rekor-cli/app/search.go
56.42% <0.00%> (-1.43%)
:arrow_down:

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

lgtm

Thanks

@sigstore/rekor-codeowners A friendly reminder!


Profile info shown is out of date

My njump page is showing outdated info including old bio and NIP-05.
<EMAIL_ADDRESS>https://njump.me/npub1aeh2zw4elewy5682lxc6xnlqzjnxksq303gwu2npfaxd49vmde6qcq4nwx
Attaching screenshots from njump and Damus.

I've pushed a fix. Let's wait one week and see if it gets replaced.

@fiatjaf Not seeing any update on my end after about 5 days.


fix: resolve missing get content for testimonials

:tada: This PR is included in version 0.54.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[FEAT] Unable to highlight non-CURD page on menu item

Is your feature request related to a problem? Please describe.
Hi, I'm having a confusing time on how to highlight non-CURD pages to the left menu items and display the breadcrumb navigation properly?
I now have a usage scenario: there is an order placing function in the member module that is not part of the member's CURD, and this order placing function only requires a create page.
Currently my needs are that I want to highlight this page to the Member menu in the left menu item, and I want that new page to be consistent with the breadcrumb navigation like the one that creates the member, and since I need the member's ID, maybe I should just need an edit page?
Is it now possible to fix the issue in the resources config item? I asked Refine Docs AI and didn't find a solution, if there is a solution please let me know, my code is similar to this:
const resources = [
 {
    name: 'vip',
    list: '/vip',
    create: '/vip/create',
    edit: '/vip/edit/:id',
    meta: {
      label: 'Member',
      icon: <CrownOutlined />,
    },
  },
  {
    name: 'vipOrder',
    list: '/vip',
    edit: '/vip/order/:id',
    meta: {
      parent: 'vip',
      hide: true,
    },
  }
]

Thanks, team
Describe alternatives you've considered
No response
Additional context
No response
Describe the thing to improve
Ability to implement non-CURD page highlighting in resources configuration, and to do so in a way that is consistent with the breadcrumb navigation of Create, Edit pages.

Hey @linkscope, thank you for opening an issue here! I think I understand the issue but would love to have some details on what you want this feature to look like.
As a workaround, I think you can define your secondary resource like below:
{
  name: "vip",
  identifier: "vipOrder", // So same resource name is inferred by the data provider
  list: "/vip/order/:id", // To have it listed in the sider menu (I'll explain more on this below)
  meta: { parent: "vip" },
}

This will make this page available in the menu, but :id is required for your page and it will navigate you to a wrong page unfortunately.
We have hideOnMissingParameter in useMenu hook that powers the sider components but looks like we've missed this option to be configurable through props of <ThemedSiderV2 /> components.
If you swizzle the <ThemedSiderV2 /> component and set hideOnMissingParameter to true, it will be only visible when there's an :id value present in the routes or meta.
Let me list what we can do and maybe we can plan this for our next releases:

hideOnMissingParameter should be configurable through props or Refine options but still, the default value should be true anyways, I think we can have this default value issue fixed in the next release
Even if there's no list value of a resource, it should still highlight the parents in the sider if it's the active route.
We're discussing on having the ability to define custom actions for a resource and make it work with menus, breadcrumbs etc. but this is not finalized yet so I cannot give an exact time or how it will work on this one.

For now, about the swizzle workaround, you can swizzle the sider component and use it in your layout, then you can define a custom logic for your highlighted menu items. Or you can use the hideOnMissingParameter prop like I've mentioned above.
Let us know if the features/fixes I've listed above works for you 🚀

@aliemir Thanks for the detailed answer! I'll try to so if the change fixes the issue, in the same time I also hope that this swizzle can be reflected in the documentation, I'm sure most admin have many non-CURD pages.
Also I'd like to be able to do this simply by configuring it entirely in resources, e.g. just like this:
const resources = [
 {
   name: 'member',
   list: '/member',
   edit: '/member/edit/:id',
   create: '/member/create',
   recharge: '/member/recharge/:id' // non-CURD page
 }
]

@linkscope, I just want to have your opinion and feedback on this; what do you expect by defining a custom route in your resource definitions (in this case recharge)? Having it work with menus, breadcrumbs and navigation hooks/buttons maybe? Do you have any other features in mind to work with this?

@aliemir Thanks for your patience in listening! I would expect custom routes (in this case recharge) to work with menus, breadcrumbs and navigation hooks, of course since it's a custom route the default headerButtons can be eliminated, and it would be nice if the useDocumentTitle doesn't need to be set separately, as I did in the previous question, this flow is fully consistent with CURD pages. This process is exactly the same as the CURD page, I hope that the resources configuration should not be limited to CURD, but can be more rich to configure the custom page, this experience is a bit similar to the vue of the vue-router operation process, for example, in this case I only need to add a line of code to achieve the functionality I expect, and at the same time, in the header configuration This painless development process is great, and I hope the team will consider doing this if they can, and thanks for the work!


In the wild inference?

How do you guys handle in the wild inference since you only release models that have been trained on cpn_ft_detections that are already in line with the h36m skeleton?

We use HRNet to get 2D pose inputs and convet them to h36m format.
Visualization and  in-the-wild inference code will be coming soon.

@Vegetebird I see so the detection results you report in the paper are those fine tuned to h36m or did you use hrnet detections?

The performace report in the paper are using cpn_ft_detections following VideoPose.
For in the wild inference, following GAST-Net, the model is trained on cpn_ft_detections and the input 2D poses are predited by HRNet.

@Vegetebird Thanks for the response. One question I had about your Strided transformer paper is what is being interpreted from the compression ratio calculated in the complexity analysis section?

Hi~Sorry for the late reply.
The compression ratio calculated shows our method can reduce the computation cost of Transformers.

Hi~ @alecda573 @akk-123
We have released the demo and in-the-wild inference code. Plaese download the latest repo and refer to demo.


[FIX] lbt/resources/ResourceCollector: Ensure proper matching of indicator files

Indicator files like "Component.js", "manifest.json" or ".library" should only be matched
if the full basename is matched.
Before this fix, files like "MyComponent.js" were matched which resulted in the unexpected
creation of a resources.json file. The file should only be created for components, libraries
and themes.

Coverage remained the same at 94.721% when pulling 9cc67f0e3057b6dd8126fcf159b7fa8edfbe818a on fix-resourcecollector-component-matching into cccb96ab2a2996034ccb007d64995d296560bba1 on master.


densenet updates + pretrained weights

Incorporates changes from https://github.com/titu1994/DenseNet from @titu1994 including imagenet pretrained weights.
Before merging, I also wanted to discuss which of these differences are correct updates, which aspects from the existing code should we keep?

dropout removed from bottleneck (this is still in upstream)
bottleneck lines removed

   if bottleneck:
        nb_layers = [int(layer // 2) for layer in nb_layers]

regularizers changed (add epsilon, remove alpha beta regularizers)
weight decay parameter not passed through in some cases, added in others
initial convolution goes from 3x3 to 7x7
should there be a conv-bn-relu vs bn-relu-conv option? (latter improved resnetv2 results)

@ahundt I already added a PR for this?

In any case, I will answer the points when comparing this model to the PyTorch implementation suggested by the authors :

dropout removed from bottleneck (this is still in upstream)

There is supposed to be only 1 dropout in the dense block, which is at the main conv. The extra dropout at the bottleneck is not present on the PyTorch implementation.

if bottleneck:
nb_layers = [int(layer // 2) for layer in nb_layers]

This accounts for the missing conv layers in a bottleneck model. This was an incorrect assumption on my part, that due to the addition of bottleneck conv, the layer would have 2 convs instead of 1 and therefore half the number of layers to account for that. It was incorrect. The weights ported require this line to be removed.

regularizers changed (add epsilon, remove alpha beta regularizers)

There is no regularizers for BatchNorm. The epsilon change is crucial for the weights loaded to have correct prediction strength. Without it, the correct predictions are made, but the strength of the predictions is on the order of 1-2 % for the strongest class, with it it jumps to the correct 90% + for cheetah image (test it in my repo)

weight decay parameter not passed through in some cases, added in others

Where is the weight decay parameter not passed? I added the weight decay to all 4 block functions.

initial convolution goes from 3x3 to 7x7

This is correct. The Inception mode DenseNet has a 7x7 stride 2 convolution. The CIFAR mode densenet uses a 3x3 stride 1 convolution.

should there be a conv-bn-relu vs bn-relu-conv option? (latter improved resnetv2 results)

There are already too many parameters to modify. I would not add this. If it is really in the interest of someone to do this, they can copy the entire script and modify as needed. The latter may have improved ResNetV2, but it is not guaranteed to improve a DenseNet.
Furthermore, there is no literature saying one is better than the other always, just empirical results from the ResNet paper on a specific model. Whether it transfers to other models has not been studied yet.

All excellent points, thanks! I'll take a look at your PR (I had not seen it) and close this.

@ahundt No problem, and they were important questions. Glad I was able to get it done asap.


Shortcut Arrangement Start Page

Rearrange the short cuts on the start page so it's more according to the general priority.
Note that if there's only 'Personal Information' (for example: normal end user) it's still in the left box/left aligned.

the screenshot above is how I meant it to be arranged.
right now Personal Information is on the far left, but as an admin user (or the like) that's probably not my first concern.
This is how it is right now:


How to call a Generic Functions

What is the game you are using with IL2CPP Resolver?

Details:
Unity.Entities.EntityManager
public readonly bool HasComponent(Entity entity)
Using IL2CPP::Class::Utils::GetMethodPointer(),  I can't get the Pointer, and  how to pass the param T
Screenshots/Video:
No response
Minimal, Complete and Verifiable Example code:
No response

Sorry for very late response.
This is the code if you're trying to get the HasComponent function offset
`Unity::il2cppClass* EntityManagerClass = IL2CPP::Class::Find("UnityEngine.Entities.EntityManager"); // Replace UnityEngine with Unity if it doesn't work
if (EntityManagerClass)
uintptr_t HasComponentOffset = IL2CPP::Class::Utils::GetMethodPointer(EntityManagerClass, "HasComponent");`


Music files with space in their name breaks compiling

Note: for support questions, please use one of the following channels.
Reddit: /r/gbstudio
Discord: Join Chat
This repository's issues are reserved for feature requests and bug reports.

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?
If one of the .mod files has a space in its filename, the project wont build anymore.

- Multiple definition of _music_track_110
- Multiple definition of _music_track_111
- Multiple definition of _music_track_112
- Multiple definition of _music_track_113
-
- make: *** [build/rom/game.gb] Error 1
-
- 2

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Rename sample.mod to have a space in its filename.

What is the expected behavior?
This should "just work"

What is the motivation / use case for changing the behavior?
Users shouldnt't need to consider what their files are named.

Please tell us about your environment:

Version: 1.1.0-rc.2
Platform: all

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Unable to reproduce this on Mac or Windows, both are accepting .mod files with spaces in the filenames for me, could you attach a small project with the issue?

This issue was originally reported by user "Kazy" on Discord. Can send the project privately to you, as I don't know if it's okay to post it publicly.

Just so you know you're looking for a project from "Krazy Productions", I uploaded a bugged project but it was for a different issue.

This was not related to the file name, but a separate issue with mod2gbt, because the tracks didn't get unique ids.


Use ManagedShell.ShellFolders and remove old implementation

Allows browsing into special folders and ZIP files
Improves display of icons
Shell context menu now used in stacks
Removed GetService from CustomCommands
Refactored icon click logic out of icon control
Fixed stacks staying open after icon click
Fixed file rename not selecting last character
TODO: Sorting, take advantage of special folder support

Created draft PR to trigger a build. Not yet ready for merge (see TODO above).


Add apt artifact build scripts

This adds the build scripts to facilitate the
apt artifact building and upload to rpc-repo.
Connects https://github.com/rcbops/u-suk-dev/issues/1143

artifacting-vars.yml is missing.


[UI] Adopt fundamental styles - view Registry

Target

[ ] Adopt the fundamental styles in Registry view

Use https://github.com/dirigiblelabs/ide-next as reference

Issue cloned to https://github.com/eclipse/dirigible/issues/1508


kubernetes_sd_config role for istio virtual services

Proposal
Use case. Why is this important?
We are using Istio and want to monitor endpoints with blackbox exporter.  Currently, we are using static config like this:
- job_name: blackbox-monitor
  metrics_path: /probe
  params:
     module: [http_monitor]
  scrape_timeout: 30s # must be >= timeout settings in blackbox exporter
  static_configs:
  - targets:
     - https://app1.customer1.exmaple.com
     - https://app1.customer2.exmaple.com
     - https://app2.customer2.exmaple.com

As the number of our applications and customers grows, it becomes quite painful to maintain such lists. So, having kubernetes discovery would help a lot. I understand this problem is useful for other kinds of ingresses like Ambassador/Kong and whatever others are out there.
So, I am curious if this is something you are considering to support, perhaps as part of ingress role or separately or it's totally out of scope for Prometheus to support different ingresses discovery?

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


presentFullscreenPlayer doesn't work on Android

I'm trying to use the presentFullscreenPlayer method to play my video. This works perfectly in iOS but it doesn't seem to do anything on the Android side. Here is my basic implementation:
return (
  <View style={{flex: 1}}>
    <TouchableOpacity
      onPress={() => {
        console.log('Open Full Screen Video', this.player)
        this.player.presentFullscreenPlayer()
      }}
      style={{backgroundColor: 'blue', height: 40, width: 60}}/>
    <Video
      rate={0}
      ref={ref => this.player = ref}
      source={{uri: 'https://results.chronotrack.com/mobile/results/video-clip/id/12321/start/1671/duration/20/name/2016JuneJerika.mp4'}}/>
  </View>
)

I can see the console log when running Android but nothing else happens. I can even see in the Video object I'm printing (this.player) has the presentFullscreenPlayer method on the object.

@RyanMitchellWilson  It's discussed in #534

Closed since this is a dupe.


feat: Implement collaboration user & collaborator workflow

Collaborations tab with requests

Collaborations tab with no requests

Collaboration button and form

Design
Figma

If I want to contribute on this should I work on the backend as well or is it implemented?

We can only take contributions from OpenSauced Triage, Committers, and Maintainers for now. We suggest folks not on the team open issues and take a look at the Bugs or Papercuts. If you would like to find good first issues, please check out the companion project to this, open-sauced/hot._

Thank you for the information!


Contourpy pin numpy to < 2.0

Several projects I work on use numpy, scipy and matplotlib extensively. Thus, tests are run against the main and pre-release version of those 3 packages. This has become harder to do because of the pin on numpy introduced in contourpy.

python -m pip install --progress-bar off --upgrade --pre --only-binary :all: -i https://pypi.anaconda.org/scientific-python-nightly-wheels/simple --timeout=180 numpy scipy matplotlib

This line does not install numpy 2.0 as matplotlib depends on contourpy which requires numpy < 2.0.
I don't see a simple way to install simultaneously all 3 pre-releases while contourpy maintain this pin. Any idea would be welcome, else, could you relax the pin on main to both start supporting numpy 2.0 and to allow:

python -m pip install  --progress-bar off --upgrade git+https://github.com/contourpy/contourpy
python -m pip install --progress-bar off --upgrade --pre --only-binary :all: -i https://pypi.anaconda.org/scientific-python-nightly-wheels/simple --timeout=180 numpy scipy matplotlib

You can't do it in a single line, but you can with two lines:
python -m pip install matplotlib scipy
python -m pip install --upgrade --pre --no-deps -i https://pypi.anaconda.org/scientific-python-nightly-wheels/simple numpy matplotlib scipy

The --no-deps is important here otherwise it tries to resolve all the mutually-incompatible dependencies which won't work, as you've seen.
A pip list for this gives me
Package         Version
--------------- -----------
contourpy       1.2.0
cycler          0.12.1
fonttools       4.47.0
kiwisolver      1.4.5
matplotlib      3.9.0.dev0
numpy           2.0.0.dev0
packaging       23.2
pillow          10.2.0
pip             23.2
pyparsing       3.1.1
python-dateutil 2.8.2
SciPy           1.13.0.dev0
setuptools      68.1.2
six             1.16.0

I'll probably remove the numpy < 2.0 pin in contourpy soon anyway, but I would still recommend using the above approach rather than installing contourpy from the github repo as then you will be building contourpy from source which I suspect you will want to avoid.

True, there are different ways to force the install, which is however yielding this error message at import time of matplotlib:

A module that was compiled using NumPy 1.x cannot be run in
NumPy 2.0.0.dev0 as it may crash. To support both 1.x and 2.x
versions of NumPy, modules must be compiled against NumPy 2.0.
If you are a user of the module, the easiest solution will be to
either downgrade NumPy or update the failing module (if available).
NOTE: When testing against pre-release versions of NumPy 2.0
or building nightly wheels for it, it is necessary to ensure
the NumPy pre-release is used at build time.
The main way to ensure this is using no build isolation
and installing dependencies manually with NumPy.
For cibuildwheel for example, this may be achieved by using
the flag to pip:
CIBW_BUILD_FRONTEND: pip; args: --no-build-isolation
installing NumPy with:
pip install --pre --extra-index-url https://pypi.anaconda.org/scientific-python-nightly-wheels/simple
in the CIBW_BEFORE_BUILD step. Please compare with the
solutions e.g. in astropy or matplotlib for how to make this
conditional for nightly wheel builds using expressions.
If you do not worry about using pre-releases of all
dependencies, you can also use --pre --extra-index-url in the
build frontend (instead of build isolation).
This will become unnecessary as soon as NumPy 2.0 is released.
If your dependencies have the issue, check whether they
have nightly wheels build against NumPy 2.0.
pybind11 note: You may see this message if using pybind11,
this is not problematic at pre-release time
it indicates the need for a new pybind11 release.

But it's probably due to matplotlib rather than contourpy (c.f. https://github.com/matplotlib/matplotlib/issues/26847).
It looks like for now the clean solution is to run 2 pre-releases jobs, one with numpy and scipy; and a second with matplotlib.

... 2 jobs actually won't work as it would install matplotlib stable with the same conflict.
But the in 2 lines seems to work without the warning on import for some reason :see_no_evil:
e.g. here https://github.com/vferat/pycrostates/pull/141

@mscheltienne I've dropped the numpy pin on the contourpy main branch so you install from the github repo if you wish.


script regressions

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (cafc260 2024-05-02T00:22:11.188280000Z)
What command(s) is the bug in?
forge script
Operating System
macOS (Apple Silicon)
Describe the bug
There seems to be a few regressions on scripts introduced in the last few weeks.

when running a script it will no longer properly show the number of txns

==========================

Chain 1

Estimated gas price: 28.900907541 gwei

Estimated total gas used for script: 11250722

Estimated amount required: 0.325156076291494602 ETH

==========================
##
Sending transactions [0 - 0]. // in earlier versions this would have shown 0-4 (given there are 5txns in that script)

when running a script with --resume it will no longer show any gas information, but immediately start with:

##
Sending transactions [0 - 0].

omitting info like estimated amount required.

when running a script with --resume after doing some txns the script will fail as the pre-calculated nonce changed.

Context:
- EOA nonce changed unexpectedly while sending transactions. Expected 107 got 108 from provider.

Not sure if that ever was not an issue, but I guess it should be solved anyways as it's quite common (run a script, gas spikes and a txn is not executed, swap some assets, try to resume).
The issue appears to be that the script will try to use the hardcoded nonce from run-latest. I guess the "proper" way would be the recalculate the execution path based on txns that already have a hash.

when running a script it will no longer properly show the number of txns
Are you running the script with --slow flag when this occurs?

@klkvr yes, forge script scripts/Deploy.s.sol:Deploy --rpc-url mainnet --broadcast --ledger --mnemonic-indexes 1 --sender <redacted> --verify -vvvv --slow was the full command

Not sure if that ever was not an issue, but I guess it should be solved anyways as it's quite common (run a script, gas spikes and a txn is not executed, swap some assets, try to resume).

So the issue occurs only when you firstly run scirpt, then do some transactions from script sender which change sender nonce, and then resume script? Or it is the case even when script is just resumed immidiately without sender nonce being changed

@klkvr only when resuming after doing some txns elsewhere(at least didn't face it before).

Marking the ticket as won't fix per the conversation above


add mqtt

it seems MQTT was mixed up with MBEDTLS, this meant the app/mqtt was never made availible.
no code change, just a tweek to the cmake to add mqtt code under pico_lwip_mqtt

Please submit PRs against develop branch - which as you now see already has this fix (#948)

thanks


Notebook review

[x] - Fixes #20

This is still a WIP. More commits will be added. I'm moving manually, chapter by chapter in the notebooks, so feel free to point out if I have missed any code or description in a notebook I have already worked on.

In 04 comment above changes reads

... one of the different glyph functions to see what they do

Maybe should be "one of the different marker types to see..." ?
Otherwise all LGTM so far!

I think I'm done now...

I inadvertently made the environment.yml update commit at #24 instead. Still okay, I guess? @tcmetzger

@Azaya89 are you able to merge PRs in this repo? I'm not sure how the permissions are set up. If not, we should adjust them (self-merge after a review approval is our current preferred process)

Merged both!


Parse other shortcodes before encryption

When this shortcode is wrapped around other shortcode content, those shortcodes don't get parsed by hugo on build.
If this shortcode could be rewritten in such a way that nested shortcodes get parsed while still remaining hidden and being encrypted by the go script, that would make this a lot more useful.

Upon further review, I think this MIGHT be a Hugo bug.

OK, pretty sure this is a hugo bug. Sorry.


Document our stack more comprehensively

Add badges for dependencies (Deno, Zod, lychee) in the readme
We have a more general plan to improve the organization of files in this repo. That will include setting up a docs folder. It will then also make sense to have a doc outlining our tech stack, with a particular focus on external dependencies.

This is something that was specifically asked for, maybe it would be a good idea to finalize at least a draft before we have the presentation here in Hamburg (that is end of the year +-)

That shouldn't be a problem. I can also emphasize in documenting our dependencies that they're all development-related, not necessary at runtime.

I can do some documenting on the leaflet, if you make an Aufschlag for the general layout of the documentation?

I've added a preliminary version of this document, at DOCS/dependencies.md.


[CI] Stops nightly-condabuild from corrupting itself;.

Motivation and Context

Miniconda is installed, unnecessary dependencies are installed and Anaconda are installed through the installer script all corrupting each other.

How Has This Been Tested

Should just work.

Types of changes

[x] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)

As an aside, this logic should be merged in with a parameterized version of test-conda build so that test-conda-build actually contributes to testing the nightly build. The conda nightly build should also be parallelized across circleci.


Improvement in git connect modal message

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The git connect modal shows the following message when a user has 3 repos connected already

The message conveys that a user can only connect 3 repos for free.
It should instead convey that a user can connect unlimited public repos and only 3 private repos for free.
Steps To Reproduce

Create a new app
Connect the app to git and the git connect modal should show the message

Public Sample App
No response
Issue video log
No response
Version
Cloud - 1.8.13

No longer valid, moved to Git Connect v2 in Q3 2023


macOS: Menubar appears at incorrect y on larger secondary display

See screenshot:

Should be fixed in https://github.com/ryanbaer/silencio/commit/ad2db32eb8cd9e8dcba1b96069bdcbb1b3aa3e0a


Fix tests on stable/beta (closes #12)

Apparently, if the macro invocation is the last "expression" in the function block, the parser expects an expression and will not let the macro expand to anything else.  Appending a semicolon will disabuse it of that notion.
The breakage only applies to error_chain! usage inside functions, which is probably not relevant other than in these tests.
Seems to be fixed in nightly 1.12 anyway.

Thanks!


Import favorites items instead of manually define them

For me the whole configuration is not clearly described.
For instance I do not have a password for my account.
When I login with the TGTG iPhone app I use my email address.
Then I get an email with a login button and numeric code to login.
Is this numeric code (one-time-password?) the password that I should use?

Update:
I tried to use that numeric code with the "get items" script but it doesn't work, that gives an authentication failure.
But I got an email that I tried to logon from different device and that email also contained a link to reset password. After resetting and using that password it worked.

I also do not understand why my favourites are not used by default.
The upstream component seems to support that.
Instead I need to use a python script to get these. That is not user friendly at all (it only works for developers that are familiair with running python scripts). I would expect that I can just pick the items when I setup the configuration preferably in the Home Assistant UI.
How to get the api secrets as alternative for username and password is not well documented.
I am in the Netherlands BTW

Hi,
Thanks for your comment 😊
Regarding the login using username/password,
The current setup isn't interactive (= everything is fixed in configuration.yaml), so I don't see how and where we could ask the user to input the receive PIN code.
Good to hear that you find a way to reset your password, I updated the Readme to hint that.
Regarding tokens,
I would love to set up an interactive setup using the Home Assistant UI.
Sadly I lack the skills and time to do that ... I would be very happy if somebody take that up 😕
I'll track this in a separate issue.
Regarding why I didn't choose to setup favorites by default,
I didn't used like this, but it should be possible to do it. I don't promise anything, but I'll look at it!
In the meantime this issue will be used to discuss this if that's ok for you.

Thank you, I have got it working now with username and password.
Great way to be notified and be the first to make a reservation for the TGTG package.
Still struggling to get API credentials in my own script, but must be because it is my first python code.

@groenmarsmannetje could you try this script? it should tell you all the 3 tokens you need :)
https://github.com/Chouffy/home_assistant_tgtg/blob/main/tgtg_get_tokens.py

Hey there,
I had some free time: now favorites are fetch if you don't define item: 😊
Related release: https://github.com/Chouffy/home_assistant_tgtg/releases/tag/3.0.0
Check the Readme on the home page!
I'll close this issue now, but feel free to comment here

Thank you very much. I can confirm that the script works.


AUTO-112: Set up Verify MSA on PaaS

This pull requests contains multiple commits required for setting up Verify MSA on PaaS. Please see commits' messages for further details.

Can't review Andy's first change but this looks good otherwise


Data processing: Image normalization

Hello,
I'm working with this code and have a question concerning data processing involved. In the following line for TrainData loader, what are these mean and std values? Where are they calculated from? I was wondering if I can use some normalization functions from OpenCV or Numpy for this purpose.
https://github.com/JirongZhang/DeepHomography/blob/fab5701bc4680b83821c83d4a06992fe1bddf609/Oneline-DLTv1/dataset.py#L26
Thank you
Warm regards,
Dharm

Just do it ~


proposal: cmd/vet: add new flag to support stdmethod checks for specific methods

What version of Go are you using (go version)?

$ go version
go version go1.18.1 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/fishy/.cache/go-build"
GOENV="/home/fishy/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/fishy/.gopath/pkg/mod"
GONOPROXY="redacted"
GONOSUMDB="redacted"
GOOS="linux"
GOPATH="/home/fishy/.gopath"
GOPRIVATE="redacted"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go-1.18"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.18/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18.1"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/fishy/work/thrift/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2627081732=/tmp/go-build -gno-record-gcc-switches"

What did you do?
In Apache Thrift go library, the interface TProtocol has
ReadByte and WriteByte that's different from the expectation of stdmethods:
type TProtocol interface {
  ...
  WriteByte(ctx context.Context, value int8) error
  ...
  ReadByte(ctx context.Context) (value int8, err error)
  ...
}

This causes go vet to complain about the implementations, and we have to do extra work to disable stdmethods check for packages containing the implementation, for example: https://github.com/reddit/baseplate.go/blob/205ac6852ad82ad5508106a6cb7156e2e73d3b3a/scripts/linters.sh#L19-L31
IMHO the stdmethods check should auto skip "violations" that explicitly implement a different interface (e.g. this line of var _ thrift.TProtocol = (*tDuplicateToProtocol)(nil) should be enough to silent stdmethods on (*tDuplicateToProtocol).ReadByte and (*tDuplicateToProtocol).WriteByte), as an explicit interface with different function signature should be enough signal that the difference is intentional, otherwise the interface should embed io.ByteReader/io.ByteWriter instead.
What did you expect to see?
What did you see instead?
$ go vet .
# github.com/apache/thrift/lib/go/thrift
./binary_protocol.go:215:27: method WriteByte(ctx context.Context, value int8) error should have signature WriteByte(byte) error
./binary_protocol.go:423:27: method ReadByte(ctx context.Context) (int8, error) should have signature ReadByte() (byte, error)
...

See also https://github.com/golang/go/issues/36970. This is roughly the same but a different function.
An alternative is to rename the methods. This is not ideal, but it does work.

IMHO the stdmethods check should auto skip "violations" that explicitly implement a different interface (e.g. this line of var _ thrift.TProtocol = (*tDuplicateToProtocol)(nil) should be enough to silent stdmethods on (*tDuplicateToProtocol).ReadByte and (*tDuplicateToProtocol).WriteByte), as an explicit interface with different function signature should be enough signal that the difference is intentional

This is a reasonable mechanism for suppression. There would be a requirement that the assignment appears in the declaring package. There would also need to be a suppression mechanism for the warning on the interface definition. A possible mechanism could again be an assignment:
var _ interface{WriteByte(ctx context.Context, value int8) error} = TProtocol(nil)

IMO changing the interface of stdmethods to allow for suppression [mechanism aside] goes against my intuition of 'if it passes cmd/vet [stdmethods], then if I see name a method named M, M has signature S [and implements standard interface I]'. I think this is a sufficiently large interface change to cmd/vet to require a proposal. Instructions on the proposal process: https://github.com/golang/proposal#the-proposal-process.

otherwise the interface should embed io.ByteReader/io.ByteWriter instead.

Would this effectively require that interfaces embed standard interfaces for interface definitions to be checked by stdmethods? That would be turning off checking for pre-existing interfaces if they contain the same function but do not embed the interface. This would also be true going forward. (Is this different than just type-checking at this point?)

An alternative is to rename the methods. This is not ideal, but it does work.

thrift.TProtocol dated back to 0.7.0/2011 (the ctx args were added in 0.14.0/2021).  Also all other thrift language libraries call the methods readByte/writeByte (see: java, c++, py, etc.), so renaming is really infeasible in this case.

Would this effectively require that interfaces embed standard interfaces for interface definitions to be checked by stdmethods?

No. What I'm suggesting is by default it still checks everything (the current behavior), just allow explicit suppression.

Thank you for the clarification. If I now understand correctly, this can be read as 'If not suppressed, keep the pre-existing check'?

Thank you for the clarification. If I now understand correctly, this can be read as 'If not suppressed, keep the pre-existing check'?

correct

Thinking out loud about yet more options:

An option is to post-process the vet output. (Probably as annoying as excluding the package in the shell script.)
An option is to add a flag that allows for suppression. Some precedent for this, but precedent is not flexible enough to turn this off for some packages or some types.
An option is to remove these from stdmethods. (IMO this would also need a proposal).

You can run vet by hand with -stdmethods=false. Run go tool vet help for more information.

I have partially reverted the title.
If none of the suggested paths forward is appealing, I think the next step is to put forward a proposal for a suppression mechanism for this checker. A community contribution would be welcomed here.

As @timothy-king mentioned, the suggested mechanism may be insufficient since the interface declaration alone
type TProtocol interface {
	WriteByte(ctx context.Context, value int8) error
	ReadByte(ctx context.Context) (value int8, err error)
}

will trigger the warnings:
./t1.go:11:2: method WriteByte(ctx context.Context, value int8) error should have signature WriteByte(byte) error
./t1.go:12:2: method ReadByte(ctx context.Context) (value int8, err error) should have signature ReadByte() (byte, error)

Basically checker stdmethods disallows  reusing these method names with different signatures. On one hand, it is too strong since it uses only the method names to do matching. On the other hand, it is guessing that people are using these methods in a standard manner, and it is right in most cases.
Instead of introducing a complicated suppression mechanism, I would suggest a simple one that allows people to define the subset of method names that should be checked or skipped checking, as checker printf does.

I think the anonymous interface way as proposed by @timothy-king should work? e.g.
var _ interface{WriteByte(ctx context.Context, value int8) error} = TProtocol(nil)

but adding a flag to stdmethods as similar to the printf one allowing removing some of the names from the check would also be good enough for our case. I do prefer it to be a denylist rather than allowlist (as the printf case) though, as this way if we have other names added to stdmethods in the future we don't need to add that to the overridden list.

I think the anonymous interface way as proposed by @timothy-king should work? e.g.
var _ interface{WriteByte(ctx context.Context, value int8) error} = TProtocol(nil)

I guess @guodongli-google point is that the current implementation of the checker would still complain as there is a definition of interface TProtocol and the checker analyzes such definitions too.

but adding a flag to stdmethods as similar to the printf one allowing removing some of the names from the check would also be good enough for our case. I do prefer it to be a denylist rather than allowlist (as the printf case) though, as this way if we have other names added to stdmethods in the future we don't need to add that to the overridden list.

I agree a deny list seems a better fit here as the checker already has a predefined set of methods+signatures it looks at. Either way, this will likely require a proposal IMO.

yea I will write a proposal when I get time :sweat_smile:

Following the guidance of https://go.dev/s/proposal-process, I'm adding proposal label to this issue to turn it into a proposal.
From the discussions above, the proposal is to:
Add a command line flag to go vet with stdmethods check, let's call it stdmethods.suppress for now (open to better names, obviously), which should work as a denylist for stdmethods to ignore.
As a concrete example, for Apache Thrift go library, we should be able to run go vet -stdmethods.suppress="ReadByte,WriteByte" ./... to still do all other stdmethods checks except ReadByte and WriteByte.
A few (half) open questions/rationales:

denylist vs. allowlist

I think a denylist works much better here, as it allows users to suppress certain functions they know stdmethods will complain about otherwise (e.g. they know they are implementing some other interfaces with different expectations). If we use an allowlist instead, users are subject to add new methods to the allowlist when future version of go vet adds checks for more methods.

command line flag vs. suppression from the code

I initially tried to write this proposal with suppression from the code approach, as suggested in https://github.com/golang/go/issues/52445#issuecomment-1103208727, but as I wrote that proposal I realized that there are too many corner cases and potential breaking changes in that approach to make it far less feasible than the flag approach. For example, currently stdmethods will also complain unexpected function signatures in anonymous interfaces, so this needs to be changed (at least we need to make stdmethods to stop complaining on anonymous interfaces when the anonymous interface is used in a blank variable declaration case).

oh wait actually I don't have the permissions to add proposal label 🤦

I turned this issue into a proposal.  Thanks.

In the case of vet's printf checker we have been able to avoid the need for external configuration files by using Go declarations themselves to enable or disable the checker (with a comment to make the intent clear). This has several advantages:

it keeps the actual logic and the checker configuration in the same place;
it causes the checker configuration to be subject to type-checking by the compiler;
it localizes the effect of changes on the dependency graph (by contrast, using an external configuration file would demand a complete "vet rebuild" after any change to it). This is important for performance of 'go vet' and gopls, which are both structured as incremental build systems.

I wonder whether a similar approach could be made to work here. In other words, is there some Go syntax we could add to the declaration of TProtocol that would have no effect at runtime but would indicate to the stdmethods analyzer (suitably modified) that TProtocol is exempt from the check. Here's a (very weak) starting point for illustration:
// This declaration tells vet's stdmethods checker to disable
// its usual checks for each of the parameter types.
func stdmethodsSuppress(TProtocol, SomeOtherType) {}

I imagine a number of other vet checks might want similar ways of expressing a set of types, or functions, or whatever, so we should examine them holistically before committing to any particular syntax.


Custom Blocked Words skips first word in CSV

Hello,
we are us a custom block list. Recently, we discovered, that the first word in the CSV is skipped.
Maybe this is an issue on our side, but we reproduced the error with multiple lists.
Kind Regards
Theo

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

ID: aa84f24e-7d01-85fa-4927-d38fea6c49f8
Version Independent ID: 3a79d18a-54b0-4c9a-a2cf-a01eae627b9f
Content: Group naming policy quickstart - Microsoft Entra
Content Source: articles/active-directory/enterprise-users/groups-quickstart-naming-policy.md
Service: active-directory
Sub-service: enterprise-users
GitHub Login: @barclayn
Microsoft Alias: barclayn

@tfo-inc
Thanks for your feedback! We will investigate and update as appropriate.

@tfo-inc
I'm going to assign this to the document author so they can take a look at it accordingly
@barclayn
Can you please check and add your comments on this doc update request as applicable.

What is the current status with this issue?

@tfo-inc thank you for reaching out.  #please-close


internal/trace/v2: OOMs in TestGCStress on 386 platforms

#!watchflakes
post <- pkg == "internal/trace/v2" && `out of memory` && goarch == "386"

Example failure: https://logs.chromium.org/logs/golang/buildbucket/cr-buildbucket/8752088278110881105/+/u/step/11/log/2.
I suspect this is just bad luck, and the uptick in failures might be correlated with an uptick in noise on our builders. The heap for this test isn't that big, but it does allocate extremely rapidly. It's within the realm of possibility that the GC is transiently failing to keep up, leading to enough memory use that we see failures on 386. I think we can avoid this by setting a memory limit because the actual live heap should be relatively small (last I checked, 50-60 MiB max).

So the above CL didn't fix the issue. However, after trying this out on a gomote, I can get much more predictable behavior from the GC by not allocating a random size slice (surprise, surprise).
It appears that we can perhaps fall into some unlucky combination of:

The GC is struggling to finish in time because the test is only allocating and the pacer hasn't caught on to the absolutely crazy high allocation rate quite yet.
All the memory allocated black while the GC is active inflates the next cycle's live heap size.
This happens for more than one cycle.
The random sizes allocated end up on the bigger side.

I can definitely reproduce big heap inflation early on in the run (not quite 2 GiB, but 100s of MiB) and it always levels out. If I use a consistent slice size, I don't see the same overruns anymore.
I do not understand yet why the flakes here only started to kick up on March 25th. There was only one flake before that in a CL I had been trying out. The only tracing-related CL that could possibly be the culprit is https://go.dev/cl/565937, but that CL shouldn't really affect the code executing in this test much, if at all.

Confirmed that this issue is fixed. There have been no new failures on any builders, except for one in a CL which was based on a commit that didn't include the fix.


Can't add new component and configure new rout (React)

Hey everybody.
I'm using React megaboiler plate (with Redux).
I added a Component name CoursePage.js into Components folder. This component is quite simple, its only render() a .
And at routes.js, I also imported new component and added new route:

But after run server, request to http://localhost:3000/courses, web's always display 404 - Not Found.
What's wrong with my approach?

Could you put in a code snippet?

I have the same issue. I also see this in the console.
Warning: React attempted to reuse markup in a container but the checksum was invalid. This generally means that you are using server rendering and the markup generated on the server was not what the client was expecting. React injected new markup to compensate which works but you have lost many of the benefits of server rendering. Instead, figure out why the markup being generated is different on the client or server:
 (client) " data-reactid="1"><div data-reactid="2"
 (server) " data-reactid="1"><nav class="navbar na


Support Flatpak installations of native Linux games

What's your idea?
Split off from #142. Some Linux games are available via Flatpak, without any other store/launcher. This would require mapping each game to its Flatpak ID, which isn't currently listed on PCGW.

I will defiantly try to get ths ids to PCGW.
But I think for the forseable futere the api route would be more sucessful: https://github.com/mtkennerly/ludusavi/issues/142#issuecomment-1285260054

Re: https://github.com/mtkennerly/ludusavi/issues/142#issuecomment-1288228001 (@LeSnake04)

Maybe it makes sense to implement the system for getting flatpaks defined by the manifest and just manually define the heroic and steam id for now.

Yeah, I can do that. If there are some specific games that are relevant for you, we could add them first to get some sample data and do some testing. Then when we have a good way to bulk add the remaining IDs and tie them to specific PCGW game names, it'll "just work".

For that it makes sense to add a root for the flatpak var. (its possible to use a .var at a different location, so users should be able to set it manually).

Good point. I'm curious, would the "home folder" root cover this? For example, let's say you set up a home root to "/tmp/home", which then implied that Ludusavi should check "/tmp/home/.var/app/{id}". That might not be intuitive, so I'm not opposed to adding a separate config, but I'm just wondering how much freedom you have to move .var around.

The home path way would work. Flatpak only supports portable repositories for now and no portable data/config
I will search some games and their corusponding ids.
For steam and heroic we should set the id to * to indicate search for all
I think a good way to help users manually bridging is to add a new type of custom entries for flatpaks where to user provides a flatpak id and a list of PCGW ids (or click an toggle to enable scanning for all games.)

Bad news

Now we eighter have to push changes to each flatpak repo, which will take ages, or make a own system.
I can make a simple gui for adding entries

I think a good way to help users manually bridging the gap is to add a new type of custom entries for flatpaks where the user provides a flatpak id and a list of PCGW ids (or click an toggle to enable scanning for all games.)
I had some situations in the past where I missed this feature.

Can you explain how you'd expect an "all games" option to work? Would you want a single "custom game" that actually backs up the data for every Flatpak game you have installed at once? If so, that doesn't really fit how Ludusavi organizes saves by game, but you could make a custom entry using globs to back up ~/.var/app/*/data and ~/.var/app/*/config.

Bad news

Hmm, I'm not sure why they seem opposed to providing context. Oh well.
I managed to find a discussion on their server from 2021 where someone asked about adding the Snap store, starting here: https://discord.com/channels/165183350913499136/327384491343478784/828417676484935700.
It sounds like the main concern was that uploads aren't guaranteed to be official:
https://discord.com/channels/165183350913499136/327384491343478784/828450116980572171

Aemony — 04/05/2021

This snap is maintained by the Snapcrafters community, and is not necessarily endorsed or officially maintained by the upstream developers.

I hate "stores" or platforms that actually allows random strangers online from publishing an application or game on it

https://discord.com/channels/165183350913499136/327384491343478784/828452599128129566

Aemony — 04/05/2021
Mhm, I don't doubt there's official ones -- I did see that they had "verified account" tags, but random end users would not really care about that sort of thing when adding these sorts of stuff to PCGW, and eventually I fully expect that most of the listed snaps we'd list as if they were official releases would in fact be unaffiliated unofficial repackages which neither has official support nor endorsement from the actual devs or pubs
Btw, sorry if I sound frustrated -- I've had a frustrating last few hours and these sorts of random platforms that allows third-party re-releases where end-users must put their trust into a random stranger online unaffiliated with the original product is one of my pet peeves, so my frustration from earlier (and entirely different unrelated things) sorta comes across here

I think the concern itself is valid, anyway. Does Flathub have some way of filtering/valiating official releases? I wouldn't want to include unofficial ones in the manifest either, to avoid supporting anything illegal (or at least seeming to, even if it weren't intentional).

You could only ever have Ludusavi do that for one game, though, or else you'd get duplicate backups. For example:

Manifest contains three Flatpak IDs: com.game1, com.game2, com.game3
Ludusavi checks for any saves of Game 1. It backs up all known Flatpak IDs (game1, game2, game3)
Ludusavi checks for any saves of Game 2. It backs up all known Flatpak IDs (game1, game2, game3)
Ludusavi checks for any saves of Game 3. It backs up all known Flatpak IDs (game1, game2, game3)

You would then have 3 copies of each game's Flatpak save data.

each game has it own home dir, so the game save from widelands will not be found in the supertux flatpak home dir

The situation regarding official downloads has changed!
Flatpaks can be verifed by the developer now. (@mtkennerly you might want to log into flathub with your github account to verify the ludusavi flatpak)
the verification status can be seen in the API output. To list the data of all flatpaks read the data from https://flathub.org/api/v2/search/: . Then we can just filter out all games and check their verified status.

@LeSnake04 Thanks for the heads-up! I logged in and it says verified in the developer settings, so I assume the badge will show up soon.
As a stopgap (until the data is automatically included), I can at least add support for a new field in the manifest, which could then be populated by a custom game entry or by a secondary manifest (https://github.com/mtkennerly/ludusavi/issues/95 , once it's implemented). I'll try to look into that for the next release.

I've added the support for this in Ludusavi and in the manifest schema.
The missing piece is a way to automatically add Flatpak IDs to the manifest. https://flathub.org/api/v2/search/: is very promising, but we'd need an approach that can avoid false positives like linking https://flathub.org/apps/com.hunterwittenborn.Celeste with https://www.pcgamingwiki.com/wiki/Celeste . In that specific case, we could ignore it because it's not verified or because it's not in the game category, but it's just an example of how names can be misleading.
@LeSnake04 For now, if there are some specific games you'd like to see added, you could submit a PR that modifies manifest-override.yaml. If the game is already in the manifest and just missing the Flatpak ID, you could add an entry like this:
Example Game:
  id:
    flatpak: com.example.Game

If it's not in the manifest at all, then ideally we would create a PCGW article and then add the Flatpak ID as above. You can also add a whole game entry from scratch in manifest-override.yaml, but PCGW is better if at all possible.


Delete behavior_tree_action_builder

PR was merged.
https://github.com/OUXT-Polaris/ouxt_automation/pull/141


Replace status.json with content items in Kontent Project

Motivation
When keeping the state of the migrations not in the status.json file, it would be easier to implement migrations in a CICD pipeline. My suggestion would be to keep this state as close as possible to the project / environment and store it as separate content-type(s).
Proposed solution
If the CLI could figure out based on projected & environment what the current state of the migrations is it would be really easy to run the migrations in an automatic stateless deployment process without telling the CLI exactly what to migrate.
With the current implementation we need to keep the status.json in sync between different deployment-agents in our CICD pipeline which makes it really hard to implement
Additional context
The proposed solution is heavily inspired by the EF Core Code first migration

Hi,
have you considered to commit your status.json using your deployment agent?
I think this would be more realiable then store status.json into Kontent.
If this solution does not fit to you, please let me know.


Add step to fetch configlet to PR template

Summary
Program configlet mentioned in the Checklist of PR template is not contained in this repo. This PR adds the step to fetch the latest configlet.
I noticed this repo also contains a fetch-configlet.ps1 for Windows PowerShell users. Is it recommended to also add a variant for Windows users?
TODO: Sync the change to https://github.com/exercism/common-lisp, from where the .github/pull_request_template.md is copied. See https://github.com/exercism/jq/issues/106.
Checklist

[ ] If docs where changed, run ./bin/configlet generate to ensure all documents are properly generated.
[ ] CI is green

The fetch* scripts are managed centrally and pushed out to all track repos.
I think windows users can probably figure it out.

The fetch* scripts are managed centrally and pushed out to all track repos.

True for fetch* scripts (found it in https://github.com/exercism/org-wide-files/tree/main/tracks-files/bin), but I meant to refer to the PR template, which is not managed centrally and is only contained in a few tracks (currently only 4), with different contents.
https://github.com/search?q=org%3Aexercism+path%3A".github%2Fpull_request_template.md"&type=code
Do you suggest adding a similar ./bin/fetch-configlet to the PR template in common-lisp track?


Issue with cut/paste to an empty group

Hey there, thank you for your app !
I just had an issue today with cut-pasting, here's the initial flow:

Create a group and leave it empty
In another group (or in the "home page"), cut an entry
Go to the empty group you just created

Expected: I should be able to paste the entry
Actual: the Paste/Cancel ribbon is not present. I have to create a fake entry, then the ribbon appears, then I can paste my initial entry

Thanks <3

Thanks <3

Thank you for reporting this issue.


add option to ignore conflicts

add option to ignore conflicts

I'll fix it up for you in a bit, today or tomorrow. Thanks for the contrib

It works now, you can do nothing on conflict like this:
using DapperBulkQueries.Common;
using DapperBulkQueries.Npgsql;

connection.ExecuteBulkInsertAsync(... , OnConflict.DoNothing);

Make sure to update nuget package to the new version before trying it.


[wip] use action-ros-ci, add codecoverage

pardon the sparse commit messages, i couldn't figure out a way to test github actions locally
General changes:

change workflow to use github actions action-ros-ci, which is used by other packages in the ROS community
introduces the rmf.repos file, allowing you to pull in other external repositories for testing
testing/coverage on a per-package basis
codecov bot now reports coverage

Waiting for PR fix for mixins:

https://github.com/ros-tooling/action-ros-ci/pull/526

todo: fixing every uncrustify issue that each package's tests will trigger when built. will wait for more PRs to go in
references:
https://github.com/ros-controls/ros2_controllers/blob/master/.github/workflows/ci.yml#L44
https://github.com/ros-tooling/action-ros-ci
https://github.com/colcon/colcon-lcov-result

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@28542c3). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master    #285   +/-   ##
========================================
  Coverage          ?   5.65%
========================================
  Files             ?    1369
  Lines             ?   92091
  Branches          ?   10565
========================================
  Hits              ?    5207
  Misses            ?   78008
  Partials          ?    8876

Flag
Coverage Δ

tests
5.65% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@28542c3). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #285   +/-   ##
=========================================
  Coverage          ?   32.13%
=========================================
  Files             ?      300
  Lines             ?    29559
  Branches          ?    19632
=========================================
  Hits              ?     9500
  Misses            ?     3415
  Partials          ?    16644

Flag
Coverage Δ

tests
32.13% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@28542c3). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #285   +/-   ##
=========================================
  Coverage          ?   32.22%
=========================================
  Files             ?      147
  Lines             ?    14738
  Branches          ?     9816
=========================================
  Hits              ?     4750
  Misses            ?     1666
  Partials          ?     8322

Flag
Coverage Δ

tests
32.22% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@28542c3). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #285   +/-   ##
=========================================
  Coverage          ?   32.41%
=========================================
  Files             ?      644
  Lines             ?    59880
  Branches          ?    39792
=========================================
  Hits              ?    19412
  Misses            ?     6648
  Partials          ?    33820

Flag
Coverage Δ

tests
32.41% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Gaffer.FileSequence.fileSequence() errors on sequences with multiple ranges.

I found this in an op when trying to specify a complex multi-range file sequence.
In the FileSystemPathPlugValueWidget the _setPlugFromPath runs path.fileSequence on the changed value.
If, however, the path contains a complex range, such as:

FileSystemPath( '/tmp/colorWheel.#.exr 1001-1018,1020-1025,1028' )

the path.fileSequence() will error with the following error:

IndexError: basic_string::substr

The internal value to the op does not change, so to the user the previous value is used in the op, but displays the user-entered value.

OK, so I've taken a bit of a look at this. The exception might come from here in Gaffer :
https://github.com/ImageEngine/gaffer/blob/master/src/Gaffer/FileSystemPath.cpp#L148
but it actually originates from here in Cortex :
https://github.com/ImageEngine/cortex/blob/master/src/IECore/FileSequenceFunctions.cpp#L245
I think there's a definite bug on that last line (it should be std::max() rather than std::min()), but I don't think that's the whole solution. It looks to me that IECore::ls() is not designed to accept sequences with the frame range already specified, so with the fix you just end up with an empty sequence anyway.
So, should FileSystemPath::fileSequence() avoid doing the ls() when the frame range is specified already? Or should ls() be made to support explicit frame ranges? In the latter case what would it do - return the same exact sequence provided those files existed, and NULL otherwise? And, a related question, do we even intend to support explicit frame ranges in FileSystemPath, since from the code it looks very much like we don't try to currently? @andrewkaufman, what do you reckon?

From what I remember FileSystemPath was considering the frame range as a property of the Path and not part of the string itself. So I wonder how we got into this situation? Maybe its a bug that comes up with FileSequenceParameterValueWidget because that one is trying to take that property and make it part of the string value?

Yeah, that sounds plausible, and "property of the path and not part of the string" sounds good to me. Is this something you'll get a chance to look at, or do you want me to take it, and if so, with what sort of priority?

I definitely won't get to it before my holidays. I'm not sure of priority because I don't know how often this comes up / impacts actual production work. Maybe @mikepkes  can comment on that?


sqlite.py file error - development branch

While building and running containers using docker-compose.yaml I got an error like below (from container logs)
Traceback (most recent call last):
  File "./app.py", line 24, in <module>
    import data.sqlite as sqlite
ModuleNotFoundError: No module named 'data.sqlite'

(...)

--- no python application found, check your startup logs for errors ---
[pid: 13|app: -1|req: -1/2] <IP_ADDRESS> () {32 vars in 346 bytes} [Tue May 19 10:35:44 2020] GET /nfvo => generated 21 bytes in 0 msecs (HTTP/1.1 500) 2 headers in 83 bytes (0 switches on core 0)

I checked container and it didn't contain sqlite.py in /usr/src/app/data directory. In my opinion is caused by volume mounted in that path (docker-compose.yaml file)
I fixed this error locally, so that's not very urgent :)

I changed something in the database handling to support the site-inventory.  I'll check that.

It builds fine for me. I'm on commit d29273e66313cc67c3f0a18133c3f51e6a6e9729.
Can you check your local gitignore file in the data folder? I changed that.

Containers were built successfully for me, but error was raised after containers were started. While running, 500 error was returned for each http message.
I used the same commit like you - d29273e
.gitignore file content below
ubuntu@msolo--server:~/mso-lo/adaptation_layer/data$ cat .gitignore
/*.db
!.gitignore
ubuntu@msolo--server:~/mso-lo/adaptation_layer/data$ ls
__init__.py  sqlite.py

but file sqlite.py is missing in containers data directory. btw, it's not caused by .dockerignore

I attached a content of data directory inside container below
root@msolo--server:~/mso-lo# docker exec -it mso-lo bash
root@f46ee3694c06:/usr/src/app# cd data
root@f46ee3694c06:/usr/src/app/data# ls
mso-lo.db

Ok I know what happened. I should have not put code in the data folder. Let me fix this in a PR I'm working on otherwise I get a lot of conflicts. Gonna merge soon.
Ps. In the meantime, I think that if you remove the volume and rebuild without using cache it should work.

I fixed this error locally, maybe not in the most sophisticated way, but it's enough for robot tests. :)
So it's not very urgent for me.
Thanks

This should be now fixed in development branch.
Please check README, installation guide has changed a bit.

I tested it and works perfectly. (ver with disable site-inventory )

Ok, closing :)


flutter test --platform chrome should not be available on stable channel yet

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.7.8+hotfix.3, on Mac OS X 10.14.5 18F132, locale en-VN)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 10.2.1)
[✓] iOS tools - develop for iOS devices
[✓] Android Studio (version 3.4)
[✓] VS Code (version 1.36.0)
[!] Connected device
    ! No devices available

! Doctor found issues in 1 category.

Steps:

go to any package with test (in this case, I will use https://github.com/zino-app/graphql-flutter/tree/master/packages/graphql as an example)
flutter test --platform chrome

Observed behavior:

test running with weird results

Expected behavior:
"chrome" is not an allowed value for option "platform".

Run 'flutter -h' (or 'flutter <command> -h') for available flutter commands and options.

==========
Steps:

flutter test -h

Observed behavior:
# abridged
    --[no-]test-assets          Whether to build the assets bundle for testing.
                                Consider using --no-test-assets if assets are not required.
                                (defaults to on)

    --platform                  The platform to run the unit tests on. Defaults to "tester".
                                [tester (default), chrome]

Expected behavior:
Platform "chrome" should not be a valid choice and should not be displayed.
Note
flutter test --platform chrome should come together with flutter for web (they both should be available, or both unavailable)

cc @Hixie

@truongsinh As after flutter 1.9 web support is already available in tech preview, I think it's safe to close the issue. If you disagree, please comment and I will re-open it right away.


Option to offset tooltip without setting it to a fixed position

Is your feature request related to a problem? Please describe.
When tooltips contain relatively long content, they may block out a significant part of the chart:

Describe the solution you'd like
I would like to be able to render the tooltip below the chart, in a floating panel to avoid breaking up the layout
Describe alternatives you've considered
Considered using the legend, but this would take up a significant amount of space in the layout. Tried using CSS and a margin but the position is calculated so it's unreliable to set a static value.
Additional context
Please excuse my poor editing skills, but this is more or less what I'd like to get to:

I'm having a similar issue. I use a custom tooltip and I'd like to position it always above the cursor. It would be great if the position of the tooltip was customizable via a callback function.
I'm thinking of something like this:
{
  tooltip: {
    /**
     * @param {Number} mouseX - mouse x position
     * @param {Number} mouseY - mouse y position
     * @param {Number} tooltipX - the default tooltip x position
     * @param {Number} tooltipY - the default tooltip y position
     */
    position(mouseX, mouseY, tooltipX, tooltipY) {
      const calculatedX = () => {
        /* do sth */
      };
      const calculatedY = () => {
        /* do sth */
      };

      return {
        x: calculatedX,
        y: calculatedY,
      };
    },
  },
};


fix: fix start index with page size for list rows

Codecov Report

Merging #1 into master will decrease coverage by 0.06%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master       #1      +/-   ##
============================================
- Coverage     80.41%   80.35%   -0.07%
- Complexity     1265     1266       +1
============================================
  Files            79       79
  Lines          6530     6525       -5
  Branches        743      735       -8
============================================
- Hits           5251     5243       -8
+ Misses          889      886       -3
- Partials        390      396       +6

Impacted Files
Coverage Δ
Complexity Δ

...n/java/com/google/cloud/bigquery/BigQueryImpl.java
82.91% <100.00%> (+0.07%)
85.00 <0.00> (+1.00)

...a/com/google/cloud/bigquery/BigQueryException.java
70.27% <0.00%> (-4.02%)
14.00% <0.00%> (ø%)

...ogle/cloud/bigquery/WriteChannelConfiguration.java
86.23% <0.00%> (-0.58%)
46.00% <0.00%> (ø%)

...om/google/cloud/bigquery/LoadJobConfiguration.java
92.77% <0.00%> (-0.44%)
56.00% <0.00%> (ø%)

...a/com/google/cloud/bigquery/InsertAllResponse.java
88.88% <0.00%> (-0.31%)
15.00% <0.00%> (ø%)

...m/google/cloud/bigquery/QueryJobConfiguration.java
90.08% <0.00%> (-0.27%)
68.00% <0.00%> (ø%)

...google/cloud/bigquery/StandardTableDefinition.java
93.15% <0.00%> (-0.19%)
16.00% <0.00%> (ø%)

...src/main/java/com/google/cloud/bigquery/Field.java
83.33% <0.00%> (-0.17%)
27.00% <0.00%> (ø%)

.../google/cloud/bigquery/spi/v2/HttpBigQueryRpc.java
4.42% <0.00%> (+0.02%)
2.00% <0.00%> (ø%)

Continue to review full report at Codecov.

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

@dmitry-fa ,PTAL


bitvis_vip_gpio   C_VVC_CMD_DATA_MAX_LENGTH   limit

Hello,
we are working with bitvis_vip_gpio in our verification flow a lot! We use it mostly when verifying our units to configure the unit using "vector" configuration or readout specific status information.
Often is the configuration a records with a lot of logic vector parameters. In this case, because of the limited C_VVC_CMD_DATA_MAX_LENGTH we are forced to instantiate a lot of GPIO VVC instances in our harness, regardless of the need of a single point configuration.
We are able to branch our own bitvis_vip_gpio with a modified C_VVC_CMD_DATA_MAX_LENGTH, but I would like to ask a general question: Is it possible to increase this value in your master releases to something more significant (e.g. 512 or 1024).
I believe, there is no issue, if this parameter is adapted, and the backward compatibility should work without any problems.
Thank you!

Hi,
I see your point. Let us check if this has other consequences. If not - it should be possible to implement this in a release very soon.
-- Espen

We will check closer. Our worry is that this might affect other VVCs / VVC-fetches, but we haven't tried it out yet. Hopefully we will have time to consider this in our next meeting on Monday.

Espen

Fixed in release v2023.03.10