Unable to publish Sass Kumite

Today I just authored a Sass Kumite and clicked on the "Publish" button; however, upon publishing, I realized that my honor did not increase at all.  Upon double-checking, I found out that my Kumite was not visible in the "Kumite" section and that the Kumite was not published at all (it was still in the "Drafts" section).
The screenshots below explain this in more detail:

After publishing the Sass Kumite, it can nowhere be found in the public "Kumite" section:
After navigating to my user profile and selecting "Kumite -> Published", the Sass kumite still cannot be found.
I then selected "Kumite -> Drafts" instead and found my Sass kumite (still) lying there:
When I click on the Kumite title to view the Kumite, it can be seen that the "Fork" button is missing, confirming that the Kumite is not published despite the fact that I clicked on the "Publish" button:

┆Issue is synchronized with this Clickup  by Unito

Thanks for the details. I think I saw the error log for this. The system tried to run Sass in order to save its output, but the runner doesn't support the language.

Thanks for the reply and explanation @jhoffner
I understand that Sass is not supported by Codewars yet but is there any way (workaround) to make it publish successfully without the runner trying to execute the code (and fail)?

@jhoffner  & @DonaldKellett  just following up on since I would like to write a kata  in scss. How could one add support to scss or sass. Thanks.

@dantesolis about the sass support please follow this issue on the codewars runner project

@javatlacati are you referencing the issue-584. And thanks for letting me know. Will try to create/publish one.

Closing because Sass kumite is no longer supported.
Adding support for CSS+HTML is tracked by https://github.com/codewars/runner/issues/21


Considering generate Kotlin data class?

When using Kotlin,there is a new  type(data class) replace java entity class,so is there any plan for support Kotlin data class generating?

+1

yep ,maybe you can make pr


GH-39527: [C++][Parquet] Validate page sizes before truncated to int32

Be defensive instead of writing invalid data.
Rationale for this change
Users can provide this API pages that are large to validly write and we silently truncate lengths before writing.
What changes are included in this PR?
Add validations and throw an exception if sizes are too large (this was previously checked only if page indexes are being build).
Are these changes tested?
Unit tested
Are there any user-facing changes?
This might start raising exceptions instead of writing out invalid parquet files.
Closes #39527
This PR contains a "Critical Fix".

Closes: #39527

@emkornfield Could we move forward? I'll approve if comment fixed

Yes, will try to update this week.

@mapleFU apologies for the delay, I think I've addressed your feedback.

cc @pitrou @wgtmac


Issue with Dependabot and Maui Workloads

I'm trying to set up Dependabot for a Maui app and encountering issues. The extension specifies it "requires macOS or Ubuntu (Windows is not supported)," but the dependabot@1 task tries to build the solution, failing due to missing Maui workloads. When attempting to install them, I receive "Workload ID maui isn't supported on this platform." Why does the task need to build the project to identify package updates? Is there a workaround, or is Maui unsupported with this extension?

That particular logic exists in the core repository. A while back they made the decision to use the NuGet CLI to check for updates which broke a couple of scenarios and they are still fixing them. Two things you can do:

Install the necessary workload in a custom docker image which you can then use to run your updates.
Create an issue in the core repo to seek resolution. https://github.com/dependabot/dependabot-core

https://github.com/dependabot/dependabot-core/issues/10117


Sporza (Belgium) not working

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm reporting a broken site
[X] I've verified that I'm running yt-dlp version 2022.10.04 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
Belgium
Provide a description that is worded well enough to be understood
I wanted to download some videos from sporza.be website, as I used to back in 2021, but this URL fails on me
Unsupported URL: https://sporza.be/nl/matches/voetbal/jupiler-pro-league/2019-2020/regulier/03/kv-oostende-club-brugge~1562000522078/
I only installed yt-dpl on my Win10 machine using the exe, I did not change any configurations.
I use the CMD (Command Line) to run yt-dlp
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', 'https://sporza.be/nl/matches/voetbal/jupiler-pro-league/2019-2020/regulier/03/kv-oostende-club-brugge~1562000522078/']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.10.04 [4e0511f] (win32_exe)
[debug] Python 3.8.10 (CPython 64bit) - Windows-10-10.0.19044-SP0
[debug] Checking exe version: ffmpeg -bsfs
[debug] Checking exe version: ffprobe -bsfs
[debug] exe versions: ffmpeg 2021-02-16-git-8331eb058d-full_build-www.gyan.dev (setts), ffprobe 2021-02-16-git-8331eb058d-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.15.0, brotli-1.0.9, certifi-2022.09.24, mutagen-1.45.1, sqlite3-2.6.0, websockets-10.3
[debug] Proxy map: {}
[debug] Loaded 1690 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2022.10.04, Current version: 2022.10.04
yt-dlp is up to date (2022.10.04)
[debug] [generic] Extracting URL: https://sporza.be/nl/matches/voetbal/jupiler-pro-league/2019-2020/regulier/03/kv-oostende-club-brugge~1562000522078/
[generic] kv-oostende-club-brugge~1562000522078: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
[generic] kv-oostende-club-brugge~1562000522078: Extracting information
[debug] Looking for Brightcove embeds
[debug] Looking for embeds
ERROR: Unsupported URL: https://sporza.be/nl/matches/voetbal/jupiler-pro-league/2019-2020/regulier/03/kv-oostende-club-brugge~1562000522078/
Traceback (most recent call last):
  File "yt_dlp\YoutubeDL.py", line 1477, in wrapper
  File "yt_dlp\YoutubeDL.py", line 1553, in __extract_info
  File "yt_dlp\extractor\common.py", line 672, in extract
  File "yt_dlp\extractor\generic.py", line 3062, in _real_extract
yt_dlp.utils.UnsupportedError: Unsupported URL: https://sporza.be/nl/matches/voetbal/jupiler-pro-league/2019-2020/regulier/03/kv-oostende-club-brugge~1562000522078/

I found this on another video:
An extractor error has occurred. (caused by KeyError('data-video-id'));
When I look in the vrt.py file, I can see this line at 55.
In the source code of the sporza site I can see this as information when starting a video:
data-videoid="vid-99dfb81a-bdb0-4bcf-ab75-2ceed69ef7e1"
I believe changing the line in vrt.py file to 'data-videoid' might solve it...

I found this on another video: An extractor error has occurred. (caused by KeyError('data-video-id'));
When I look in the vrt.py file, I can see this line at 55. In the source code of the sporza site I can see this as information when starting a video: data-videoid="vid-99dfb81a-bdb0-4bcf-ab75-2ceed69ef7e1"
I believe changing the line in vrt.py file to 'data-videoid' might solve it...

Hmm yeah, might've been an oversight in https://github.com/yt-dlp/yt-dlp/commit/4de300768abeddde88c1a23a2fc7f8d308eccee8 (unless they changed the entire site back).
Both versions should be supported imo (along with the other attr variations). Going back through the youtube-dl PRs they seem to switch between the formats.
Also the _VALID_URL will need updating to support this url

Exactly. -id was used until https://github.com/ytdl-org/youtube-dl/commit/82e91d20a0f698b13412dd7b200663c7485791bb, then changed to id, then to -id in https://github.com/yt-dlp/yt-dlp/commit/4de300768abeddde88c1a23a2fc7f8d308eccee8 (but kept in yt-dl), and now id seems to be right. Maybe both types are or have been used depending on the actual site or the time when the page was observed or both.
The yt-dl and yt-dlp VRT extractors are basically identical apart from this and conventions.
The Canvas extractors differ a bit. Both try to use an API URL whose host mediazone.vrt.be (also the host in the URL pattern, but never fetched) no longer resolves, before succeeding with another tactic. The yt-dlp extractor adds a vrtnutoken which is used in this API call, but apparently always crashes the extractor with sporza. The API URL is .../v2 in yt-dlp  is seen in current pages, with no obvious difference in behaviour (but see below).
The problem page is old and its URL has a different pattern. However the page structure is similar to a current page like https://sporza.be/nl/2022/10/16/bekijk-alle-doelpunten-van-de-12e-speeldag-in-de-jupiler-pro-league~1665948601519/; so probably the _VALID_URL is unnecessarily restrictive.
I used this:
    _VALID_URL = r'https?://(?:www\.)?(?P<site>vrt\.be/vrtnws|sporza\.be)/(?:[^/]+/)+(?P<id>[^/?&#]+)'

Additionally, the VRT extractors only get the first matching video in a page whereas the problem page and the above current example have several videos. The extractor should search the whole page:
    def _real_extract(self, url):
        site, display_id = re.match(self._VALID_URL, url).group('site', 'id')
        webpage = self._download_webpage(url, display_id)

        def entries():
            for m in re.finditer(
                    r'(<\w+\b[^>]+\bclass\s*=\s*"(?:[^"]+?\s)?vrtvideo\b[^>]*>)', webpage):
                attrs = extract_attributes(m.group(0))

                asset_id = attrs.get('data-video-id') or attrs['data-videoid']
                publication_id = dict_get(attrs, ('data-publication-id', 'data-publicationid'))
                if publication_id:
                    asset_id = publication_id + '$' + asset_id
                client = attrs.get('data-client') or self._CLIENT_MAP[site]

                entry = self.url_result(
                    'https://mediazone.vrt.be/api/v1/%s/assets/%s' % (client, asset_id),
                    ie='Canvas', video_id=asset_id, video_title=attrs.get('data-title'))
                entry.update({
                    '_type': 'url_transparent',
                    'thumbnail': attrs.get('data-posterimage'),
                    'duration': float_or_none(attrs.get('data-duration'), 1000),
                })
                yield entry

        title = strip_or_none(get_element_by_class(
            'vrt-title', webpage) or self._html_search_meta(
            ['og:title', 'twitter:title', 'name'], webpage))
        description = self._html_search_meta(
            ['og:description', 'twitter:description', 'description'], webpage)
        if description == '…':
            description = None

        result = self.playlist_result(
            entries(), playlist_id=display_id, playlist_title=title,
            playlist_description=description)
        result['timestamp'] = unified_timestamp(self._html_search_meta(
            'article:published_time', webpage))
        return result

With some small (but not required) pulls from the yt-dlp Canvas code and this revised error handler which addresses (a) removing the unwanted bug_reports_message() text from a nested exception message nested in an ExtractorError with expected=True (this should be done globally, though) (b) novel geo-location error codes from the v2 API:
            except ExtractorError as e:
                if isinstance(e.cause, compat_HTTPError) and e.cause.code == 404:
                    args = list(e.args)
                    args[0] = args[0].replace(bug_reports_message(), '')
                    e.args = tuple(args)
                    raise ExtractorError(
                        'Video data not found: no longer available?',
                        cause=e, expected=True)
                raise
            if 'title' not in data:
                code = data.get('code')
                if code == 'AUTHENTICATION_REQUIRED':
                    self.raise_login_required()
                elif code == 'INVALID_LOCATION':
                    self.raise_geo_restricted(countries=['BE'])
                elif code.startswith('CONTENT_AVAILABLE_ONLY_'):
                    self.raise_geo_restricted(
                        msg=' '.join(x.title() if ii == 0
                                     else x.lower() if ii < 4 or len(x) > 2
                                     else x
                                     for ii, x in enumerate(code.split('_'))),
                        countries=code.split('_')[4:5])
                raise ExtractorError(data.get('message') or code, expected=True)

the problem page just gets 404s, presumably because the content has expired
$ python3.9 -m youtube_dl -F 'https://sporza.be/nl/matches/voetbal/jupiler-pro-league/2019-2020/regulier/03/kv-oostende-club-brugge~1562000522078/' --ignore-errors --playlist-end 2
[VRT] kv-oostende-club-brugge~1562000522078: Downloading webpage
[download] Downloading playlist: Invallers Tau en Okereke kruiden Brugse zege aan zee
[VRT] playlist Invallers Tau en Okereke kruiden Brugse zege aan zee: Downloading 2 videos
[download] Downloading video 1 of 2
[Canvas] pbs-pub-6185a3c6-93de-4a4d-80ed-ae02dd0c020a$vid-d2dac3ea-c778-46c1-a03c-d019a6b361a2: Downloading token
[Canvas] pbs-pub-6185a3c6-93de-4a4d-80ed-ae02dd0c020a$vid-d2dac3ea-c778-46c1-a03c-d019a6b361a2: Downloading video JSON
ERROR: Video data not found: no longer available? (caused by ExtractorError("Unable to download JSON metadata: HTTP Error 404: Not Found (caused by <HTTPError 404: 'Not Found'>)"))
[download] Downloading video 2 of 2
[Canvas] pbs-pub-6185a3c6-93de-4a4d-80ed-ae02dd0c020a$vid-0992bab0-cecd-477e-a761-316144e437e4: Downloading token
[Canvas] pbs-pub-6185a3c6-93de-4a4d-80ed-ae02dd0c020a$vid-0992bab0-cecd-477e-a761-316144e437e4: Downloading video JSON
ERROR: Video data not found: no longer available? (caused by ExtractorError("Unable to download JSON metadata: HTTP Error 404: Not Found (caused by <HTTPError 404: 'Not Found'>)"))
[download] Finished downloading playlist: Invallers Tau en Okereke kruiden Brugse zege aan zee
$

but the current page is more successful using API v1
$ python3.9 -m youtube_dl -v -F 'https://sporza.be/nl/2022/10/16/bekijk-alle-doelpunten-van-de-12e-speeldag-in-de-jupiler-pro-league~1665948601519/' --ignore-errors --playlist-items 3-4
[debug] System config: ['--prefer-ffmpeg']
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '-F', 'https://sporza.be/nl/2022/10/16/bekijk-alle-doelpunten-van-de-12e-speeldag-in-de-jupiler-pro-league~1665948601519/', '--ignore-errors', '--playlist-items', '3-4']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Git HEAD: fdb16c0d6
[debug] Python version 3.9.14 (CPython) - Linux-4.4.0-210-generic-i686-with-glibc2.23
[debug] exe versions: avconv 4.3, avprobe 4.3, ffmpeg 4.3, ffprobe 4.3
[debug] Proxy map: {}
[VRT] bekijk-alle-doelpunten-van-de-12e-speeldag-in-de-jupiler-pro-league~1665948601519: Downloading webpage
[download] Downloading playlist: Bekijk alle doelpunten van de 12e speeldag in de Jupiler Pro League
[VRT] playlist Bekijk alle doelpunten van de 12e speeldag in de Jupiler Pro League: Downloading 2 videos
[download] Downloading video 1 of 2
[Canvas] pbs-pub-ce83f448-24d5-460a-b3a2-62a00f6f4ee3$vid-0ddd6273-ca17-4d0b-920b-953a0c4548de: Downloading token
[Canvas] pbs-pub-ce83f448-24d5-460a-b3a2-62a00f6f4ee3$vid-0ddd6273-ca17-4d0b-920b-953a0c4548de: Downloading video JSON
[Canvas] pbs-pub-ce83f448-24d5-460a-b3a2-62a00f6f4ee3$vid-0ddd6273-ca17-4d0b-920b-953a0c4548de: Downloading MPD manifest
[Canvas] pbs-pub-ce83f448-24d5-460a-b3a2-62a00f6f4ee3$vid-0ddd6273-ca17-4d0b-920b-953a0c4548de: Downloading m3u8 information
[info] Available formats for pbs-pub-ce83f448-24d5-460a-b3a2-62a00f6f4ee3$vid-0ddd6273-ca17-4d0b-920b-953a0c4548de:
format code              extension  resolution note
MPEG_DASH-audio_1=64013  m4a        audio only DASH audio   64k , m4a_dash container, mp4a.40.5 (48000Hz)
MPEG_DASH-audio=96012    m4a        audio only DASH audio   96k , m4a_dash container, mp4a.40.2 (48000Hz)
MPEG_DASH-video=551669   mp4        480x270    DASH video  551k , mp4_dash container, avc1.4D401F, 25fps, video only
MPEG_DASH-video=902299   mp4        640x360    DASH video  902k , mp4_dash container, avc1.4D401F, 25fps, video only
MPEG_DASH-video=1303394  mp4        768x432    DASH video 1303k , mp4_dash container, avc1.4D401F, 25fps, video only
MPEG_DASH-video=2205483  mp4        960x540    DASH video 2205k , mp4_dash container, avc1.4D401F, 25fps, video only
HLS-653                  mp4        480x270     653k , avc1.4D401F@ 551k, 25.0fps, mp4a.40.5@ 64k
HLS-1059                 mp4        640x360    1059k , avc1.4D401F@ 902k, 25.0fps, mp4a.40.2@ 96k
HLS-1484                 mp4        768x432    1484k , avc1.4D401F@1303k, 25.0fps, mp4a.40.2@ 96k
HLS-2440                 mp4        960x540    2440k , avc1.4D401F@2205k, 25.0fps, mp4a.40.2@ 96k (best)
[download] Downloading video 2 of 2
[Canvas] pbs-pub-ce83f448-24d5-460a-b3a2-62a00f6f4ee3$vid-8b9a0eb5-0cae-493f-98a3-a30aafb6ce7d: Downloading token
[Canvas] pbs-pub-ce83f448-24d5-460a-b3a2-62a00f6f4ee3$vid-8b9a0eb5-0cae-493f-98a3-a30aafb6ce7d: Downloading video JSON
ERROR: This video is not available from your location due to geo restriction
This video is available in Belgium.
You might want to use a VPN or a proxy server (with --proxy) to workaround.
Traceback (most recent call last):
  File "/home/df/Documents/src/youtube-dl/youtube_dl/YoutubeDL.py", line 816, in wrapper
    return func(self, *args, **kwargs)
  File "/home/df/Documents/src/youtube-dl/youtube_dl/YoutubeDL.py", line 837, in __extract_info
    ie_result = ie.extract(url)
  File "/home/df/Documents/src/youtube-dl/youtube_dl/extractor/common.py", line 534, in extract
    ie_result = self._real_extract(url)
  File "/home/df/Documents/src/youtube-dl/youtube_dl/extractor/canvas.py", line 92, in _real_extract
    self.raise_geo_restricted(countries=['BE'])
  File "/home/df/Documents/src/youtube-dl/youtube_dl/extractor/common.py", line 947, in raise_geo_restricted
    raise GeoRestrictedError(msg, countries=countries)
youtube_dl.utils.GeoRestrictedError: This video is not available from your location due to geo restriction

[download] Finished downloading playlist: Bekijk alle doelpunten van de 12e speeldag in de Jupiler Pro League
$

Moving to v2, all the UK-visible media links that were found with v1 and succeeded with --test are blocked. Presumably an "expat" token is necessary, or v2 is post-Brexit:
$ python3.9 -m youtube_dl -F 'https://sporza.be/nl/2022/10/16/bekijk-alle-doelpunten-van-de-12e-speeldag-in-de-jupiler-pro-league~1665948601519/' --ignore-errors --playlist-items 3-4
[VRT] bekijk-alle-doelpunten-van-de-12e-speeldag-in-de-jupiler-pro-league~1665948601519: Downloading webpage
[download] Downloading playlist: Bekijk alle doelpunten van de 12e speeldag in de Jupiler Pro League
[VRT] playlist Bekijk alle doelpunten van de 12e speeldag in de Jupiler Pro League: Downloading 2 videos
[download] Downloading video 1 of 2
[Canvas] pbs-pub-ce83f448-24d5-460a-b3a2-62a00f6f4ee3$vid-0ddd6273-ca17-4d0b-920b-953a0c4548de: Downloading token
[Canvas] pbs-pub-ce83f448-24d5-460a-b3a2-62a00f6f4ee3$vid-0ddd6273-ca17-4d0b-920b-953a0c4548de: Downloading video JSON
ERROR: Content available only for BE residents and expats
This video is available in Belgium.
You might want to use a VPN or a proxy server (with --proxy) to workaround.
[download] Downloading video 2 of 2
[Canvas] pbs-pub-ce83f448-24d5-460a-b3a2-62a00f6f4ee3$vid-8b9a0eb5-0cae-493f-98a3-a30aafb6ce7d: Downloading token
[Canvas] pbs-pub-ce83f448-24d5-460a-b3a2-62a00f6f4ee3$vid-8b9a0eb5-0cae-493f-98a3-a30aafb6ce7d: Downloading video JSON
ERROR: Content available only in BE
This video is available in Belgium.
You might want to use a VPN or a proxy server (with --proxy) to workaround.
[download] Finished downloading playlist: Bekijk alle doelpunten van de 12e speeldag in de Jupiler Pro League
$

Obviously there are some issues to resolve here, probably easiest for someone in-region. One major thing is to get vrtnutoken working or at least not crashing sporza (etc) extractions; another is to determine if there's a valid current equivalent of media.virtzone.be that should be used in the Canvas extractor's URL pattern. Maybe it should just have (with appropriate changes elsewhere):
    _VALID_URL = r'canvas:(?P<site_id>canvas|een|ketnet|vrt(?:video|nieuws)|sporza|dako):(?P<id>[^/?#&]+)'

Someone able to work on this one please? Would be such a life saver, thanks!


x/net/context: go vet fails because of copied Mutex

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

go version go1.6 linux/amd64

What operating system and processor architecture are you using (go env)?

GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"

What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.

Ran go vet ./... on a project with golang.org/x/net/context/context.go in vendor/.
Also tried running go vet on a fresh clone of https://github.com/golang/net.

What did you expect to see?

go vet to exit with status 0.

What did you see instead?

context.go:218: newCancelCtx returns lock by value: context.cancelCtx contains sync.Mutex
exit status 1

The code is correct, but tricky in its use of values and references to maintain the Mutex. A tentative change like this appears to also be correct, passes the tests, and also passes go vet:
diff --git a/context/context.go b/context/context.go
index 77b64d0..19235cf 100644
--- a/context/context.go
+++ b/context/context.go
@@ -210,13 +210,13 @@ type CancelFunc func()
 // call cancel as soon as the operations running in this Context complete.
 func WithCancel(parent Context) (ctx Context, cancel CancelFunc) {
        c := newCancelCtx(parent)
-       propagateCancel(parent, &c)
-       return &c, func() { c.cancel(true, Canceled) }
+       propagateCancel(parent, c)
+       return c, func() { c.cancel(true, Canceled) }
 }

 // newCancelCtx returns an initialized cancelCtx.
-func newCancelCtx(parent Context) cancelCtx {
-       return cancelCtx{
+func newCancelCtx(parent Context) *cancelCtx {
+       return &cancelCtx{
                Context: parent,
                done:    make(chan struct{}),
        }
@@ -259,7 +259,7 @@ func parentCancelCtx(parent Context) (*cancelCtx, bool) {
                case *cancelCtx:
                        return c, true
                case *timerCtx:
-                       return &c.cancelCtx, true
+                       return c.cancelCtx, true
                case *valueCtx:
                        parent = c.Context
                default:
@@ -377,7 +377,7 @@ func WithDeadline(parent Context, deadline time.Time) (Context, CancelFunc) {
 // implement Done and Err.  It implements cancel by stopping its timer then
 // delegating to cancelCtx.cancel.
 type timerCtx struct {
-       cancelCtx
+       *cancelCtx
        timer *time.Timer // Under cancelCtx.mu.

        deadline time.Time

I'm happy to put this into a CL.

 There's a bunch of things that look like they need fixing here.
newCancelCtx (from x/net/context/context.go:117) should probably also be changed to return *cancelCtx instead of the value type. I can't see a good reason for that to return the value; the rest of that file uses it by pointer.

 It wasn't as of yesterday, and doesn't according to Go 1.6's go vet test. Anyway, just checking to see if this is related.

@mholt I think that is not related, as x/net/context legitimately had a function which returned a lock by value: https://github.com/golang/net/commit/9d8ef8d73b53840886e4a772c72f2b7d396cb37c

@dsymonds Thanks for getting a fix for this! I think https://github.com/golang/net/commit/9d8ef8d73b53840886e4a772c72f2b7d396cb37c resolves the original issue. Should I close this?

@bernerdschaefer Alrighty, I'll open a new issue then.

Is new() really a function call that is copying a lock value?

This looks like a bug in go vet. I'll look into it tomorrow unless somebody fix it today.

@mholt , @bernerdschaefer , I prepared the CL, which should properly handle new(sync.Mutex) case in go vet.

Cool, thanks, does that cover new(sync.Once) too, then? (Issue: #14994)

Cool, thanks, does that cover new(sync.Once) too, then?

Yes

should this add lable go1.7?

@s7v7nislands Done.

@ianlancetaylor maybe Issue: #14994 also need label


AttributeError: 'EmissionsTracker' object has no attribute 'start_task'

CodeCarbon version: 2.3.2
Python version: Python 3.10.9
Operating System: Windows

I try to use codecarbon to measure the training and the inference of ml models with the functions start_task and stop_task.
I get the following error :
tracker.start_task("load dataset")
AttributeError: 'EmissionsTracker' object has no attribute 'start_task'. Did you mean: '_start_time'?
I tried to run this script : https://github.com/mlco2/codecarbon/blob/master/examples/bert_inference.py
to be sure I used the functions well but I get the same error.
Do you know why ?

Hello!
The start_task was added in version 2.3.0, could it be that you are running an older version of the package?
I might suggest to verify that the version of CodeCarbon you are running is the latest. Here you have a small script to check this
import pkg_resources

def get_package_info(package_name):
    try:
        package = pkg_resources.get_distribution(package_name)
        return {
            'version': package.version,
            'location': package.location
        }
    except pkg_resources.DistributionNotFound:
        return f"Package '{package_name}' is not installed"

package_name = 'codecarbon'
package_info = get_package_info(package_name)

if isinstance(package_info, str):
    print(package_info)
else:
    print(f"Package: {package_name}")
    print(f"Version: {package_info['version']}")
    print(f"Location: {package_info['location']}")

If the package version is indeed the latest, and the issue persist, please tell us. We can verify further.

Hello !
Thank you for your answer ! I was using the version 2.3.2 & Python version 3.10.9. I updated my Python version to Pyhton 3.12.1 and I don't have the error anymore.
However, I have a new error :
ZeroDivisionError                         Traceback (most recent call last)
Cell In[34], line 7
5 tracker = EmissionsTracker(project_name="classification-measure")
6 #track the ml model training
----> 7 tracker.start_task("train model")
8 classifier.fit(x_train, y_train)
9 tracker.stop_task()
File ...\Python312\Lib\site-packages\codecarbon\emissions_tracker.py:450, in BaseEmissionsTracker.start_task(self, task_name)
448 for hardware in self._hardware:
449     hardware.start()
--> 450 _ = self._prepare_emissions_data(delta=True)
452 self._tasks.update(
453     {
454         task_name: Task(
(...)
457     }
458 )
459 self._active_task = task_name
File ...\Python312\Lib\site-packages\codecarbon\emissions_tracker.py:582, in BaseEmissionsTracker._prepare_emissions_data(self, delta)
574     cloud_provider = cloud.provider
575     cloud_region = cloud.region
576 total_emissions = EmissionsData(
577     timestamp=datetime.now().strftime("%Y-%m-%dT%H:%M:%S"),
578     project_name=self._project_name,
579     run_id=str(self.run_id),
580     duration=duration.seconds,
581     emissions=emissions,  # kg
--> 582     emissions_rate=emissions / duration.seconds,  # kg/s
583     cpu_power=self._cpu_power.W,
584     gpu_power=self._gpu_power.W,
585     ram_power=self._ram_power.W,
586     cpu_energy=self._total_cpu_energy.kWh,
587     gpu_energy=self._total_gpu_energy.kWh,
588     ram_energy=self._total_ram_energy.kWh,
589     energy_consumed=self._total_energy.kWh,
590     country_name=country_name,
591     country_iso_code=country_iso_code,
592     region=region,
593     on_cloud=on_cloud,
594     cloud_provider=cloud_provider,
595     cloud_region=cloud_region,
596     os=self._conf.get("os"),
597     python_version=self._conf.get("python_version"),
598     codecarbon_version=self._conf.get("codecarbon_version"),
599     gpu_count=self._conf.get("gpu_count"),
600     gpu_model=self._conf.get("gpu_model"),
601     cpu_count=self._conf.get("cpu_count"),
602     cpu_model=self._conf.get("cpu_model"),
603     longitude=self._conf.get("longitude"),
604     latitude=self._conf.get("latitude"),
605     ram_total_size=self._conf.get("ram_total_size"),
606     tracking_mode=self._conf.get("tracking_mode"),
607     pue=self._pue,
608 )
609 if delta:
610     if self._previous_emissions is None:
ZeroDivisionError: float division by zero
Do you know why ?
I have another question, is it different to make the measure with the function 'start_task' like this :
tracker = EmissionsTracker(project_name="classification-measure")
tracker.start_task("train model")
#track the ml model training
tracker.stop_task()
tracker.start_task("model inference")
#track the ml model inference
tracker.stop_task()
emissions = tracker.stop()
And create 2 different trackers like this ?
tracker1 = EmissionsTracker(project_name="train model")
tracker1.start()
#track the ml model training
tracker1.stop()
tracker2 = EmissionsTracker(project_name="model inference")
tracker2.start()
#track the ml model inference
tracker2.stop()
The results are the same, right ?

@Sarah7223 Hi ! This error is related to #549 I made a pull request #570
You can correct on your side by replacing all time.time() by time.perf_counter() in emission_tracker.py
Cheers, Leah

Closing as the answer have been given, please re-open if there is something missing


Accessibility issues with some templates

Hi and congrats for making these beautiful templates.
Some of them though, are not accessible. For example:

https://chakra-templates.dev/templates/navigation/navbar/withSubnavigation

On this one, the Tab key should move from one element to the other, then the Space or Enter keys should open the sub navigation menu, then the arrows keys should allow navigating the menu, the Escape key should allow closing the menu, and the Space or Enter key should allow selecting an item.

https://chakra-templates.dev/templates/navigation/sidebar/simpleSidebar

On this one, no clue is given about which element is selected when using the Tab key.

Hey @Zwyx thank you for your kind words.
Good catch there with the accessibility issues 👌
I am am still planning if and how I can restructure the whole project. The accessibility will be definitely a part of it.
If you want, you can also open a MR to fix these issues.


add description field

What
Update dimensions query to include description field
Trello - https://trello.com/c/LryLDeBf/5940-add-meta-data-to-variable-description
How to review
Confirm changes match requested changes in Trello ticket
Who can review
Anyone

LGTM but is there a unit test we could update to represent the inclusion of this field being expected? Also needs rebase

It looks like there weren't actually any tests for the GetDimensions function, so I've added them in


Tiles not responsive

Window resize, tiles with double to quadro goes beyond the container (span6)

Any news on this ?

Cakn somebody revert back

To foum please

To foum please in topic Metro UI CSS 2x


hgrep on NetBSD

Hi,
I've packaged and merged hgrep into the main pkgsrc branch, https://mail-index.netbsd.org/pkgsrc-changes/2021/10/20/msg242216.html
This means the package is now available from the official repositories for NetBSD.
Thank you for this awesome tool.
/pin

Hi,
I really dislike GitHub, I only have an account to be able to communicate with projects host here, otherwise I keep my own stuff at codeberg.
Hope it's fine I post here in md format.
NetBSD
To install pre-built binaries using the package manager, simply run
pkgin install hgrep
Or, if you prefer to build from source,
cd /usr/pkgsrc/textproc/hgrep
make install

Thank you.

OK, no problem. I'll add it myself. Thank you for telling me the instruction.


DataFrame Viewer with custom objects

Hi, I've been running into the issue where the dataframe viewer wont work more and more.

In general it seems to be because of a custom object in the dataframe.  Is there something I can do to figure out what the 'unknown error' is to try and fix the underlying objects?  Any other suggestions appreciated too!

Hi @mg3146 thank you for the feedback! I would say this is related to https://github.com/spyder-ide/spyder/issues/18821 . Regarding getting more feedback, maybe running Spyder on debug mode could be useful, for that you can go to FIle > Restart in debug mode > Verbose The generated log file should be located at the dir Spyder uses to store preferences (.spyder-py3)  inside your home/user directory in a file named spyder-debug.log.
Let us know if the info above helps!

Basically as the variable explorer currently works, visualizing variables that need specific modules needs for those modules pakcages to be installed over the Spyder installation side. The related issue for that is https://github.com/spyder-ide/spyder/issues/20959. Since you are using the standalone version there is not much you can do (the installer doesn't bundled pip so you can not install packages inside the default Spyder env in a straight forward manner) Not totally sure if using the PYTHONPATH manager could help for Spyder to find the fincad module you are using.
The only workaround to this for the moment is to install Spyder in the same env where you have your custom packages and launch it from there. In that way, Spyder will have access to the packages and there will be no need to use a custom interepreter.
We know this situation is quite convoluted so if you have any other questions or feedback let us know!

Got you.  Is there anyway to tie the variable viewer to the environment that the IPython console uses?
On May 28, 2023 at 3:37 PM -0400, Daniel Althviz Moré @.***>, wrote:

Basically as the variable explorer currently works, visualizing variables that need specific modules needs for those modules pakcages to be installed over the Spyder installation side. The related issue for that is #20959. Since you are using the standalone version there is not much you can do (the installer doesn't bundled pip so you can not install packages inside the default Spyder env in a straight forward manner) Not totally sure if using the PYTHONPATH manager could help for Spyder to find the fincad module you are using.
The only workaround to this for the moment is to install Spyder in the same env where you have your custom packages and launch it from there. In that way, Spyder will have access to the packages and there will be no need to use a custom interepreter.
We know this situation is quite convoluted so if you have any other questions or feedback let us know!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

I think there is no way, sorry :/

This could be solved in Spyder 6 thanks to our conda-based installers. But I don't know how easy it could be without compromising the Spyder installation itself.
@mrclary, what do you think about it?

Got you, it would great if there was a way.  I used to use a conda based install but I had too many environment corruption issues.
On May 28, 2023 at 5:09 PM -0400, Carlos Cordoba @.***>, wrote:

This could be solved in Spyder 6 thanks to our conda-based installers. But I don't know how easy it could be without compromising the Spyder installation itself.
@mrclary, what do you think about it?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Got you, it would great if there was a way.  I used to use a conda based install but I had too many environment corruption issues.

I couldn't have asked for a more succinct expression of the problem. One major advantage of the standalone application is that it protects Spyder from a user unintentionally corrupting the runtime environment.
The conda-based installer for Spyder 6 will make it possible for a user to modify Spyder's runtime environment, but this will likely be highly discouraged by the Spyder development team. However, when our package manager plugin is released, there may be more robust options available in the future. Nevertheless, a solution to #20959, if achievable, would be best as it would remove any need to modify Spyder's runtime environment.

In the event that pickle doesn’t work, could it try to str() whatever is throwing the exception  in the data frame?
On May 28, 2023 at 5:55 PM -0400, Ryan Clary @.***>, wrote:

Got you, it would great if there was a way.  I used to use a conda based install but I had too many environment corruption issues.
I couldn't have asked for a more succinct expression of the problem. One major advantage of the standalone application is that it protects Spyder from a user unintentionally corrupting the runtime environment.
The conda-based installer for Spyder 6 will make it possible for a user to modify Spyder's runtime environment, but this will likely be highly discouraged by the Spyder development team. However, when our package manager plugin is released, there may be more robust options available in the future. Nevertheless, a solution to #20959, if achievable, would be best as it would remove any need to modify Spyder's runtime environment.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

I'm also getting this error on dataframes with simple floats64's too fwiw.


Download links are broken

For example:-
$ curl -I https://s3-us-west-2.amazonaws.com/policy-plus/Policy%20Plus.exe

HTTP/1.1 403 Forbidden
x-amz-request-id: 71110578F6688F35
x-amz-id-2: YWOGb99ik/a9Nhxjv2agTAhKkdKkTuUhMkdvgJfdf2YnYffNjPCeSBcTDhxUjkOjK1yfq2v//Wc=
Content-Type: application/xml
Transfer-Encoding: chunked
Date: Thu, 16 Nov 2017 08:57:19 GMT
Server: AmazonS3

Yep, my bad (cf. https://github.com/Fleex255/PolicyPlus/issues/6). Fixed now, sorry!


Add support for Fluidlogged

This PR adds support for Fluidlogged. This will automatically add milk to the config of Fluidlogged if both mods are installed and also fixes the issue that milk cannot be placed inside any fluidloggable block.

I don't think having this by default is a good idea. If people want it, they can just add it to the fluidlogged config.

The commit f7c3d7a is still quite necessary for it to work properly. As of now, the player won't be able to place the fluid inside a block unless they place the fluid first.


Add support for background processing on iOS

Problem
Should be possible to use the plugin for the type of limited background scanning iOS provides.
Solution
Research settings needed for this and add them to the cordova-xml file.
Some links related to iOS background processing (mostly iBeacon related however):
https://github.com/evothings/phonegap-estimotebeacons/wiki/Background-notification-guide#ios-background-processing
Related Evothings Forum thread:
http://evothings.com/forum/viewtopic.php?f=8&t=1391

Support for background scanning available in this branch: https://github.com/mikaelkindborg/cordova-ble/tree/background
Will be merged to master branch.


Connect with ~fabled-faster on design language

received communication from ~fabled-faster, including preliminary design language. Going to try to hop on a call to see how he envisions building this into the Urbit Foundation figma team.


Tagging Roles

Tagging of roles, which will allow galaxy to publish the same as versions of the roles via galaxy

Could you provide an example or a link @kameshsampath ? Not sure I follow what you are asking

@sherl0cks, i meant [Download Multiple Roles](https://galaxy.ansible.com/intro#Download Multiple Roles), we need to start tagging the commits on our rhtconsulting/jboss_* to make them listed as versions in galaxy roles, right now if you see the Galaxy role info via galaxy.ansible.com you see no version info available, once we start tagging our commits you will see the versions coming/listed there, then the users can choose the role_name, version kind of pattern to get the needed version of the role.
e.g. lets say we tag the current commit as 6.4.7, so the users in the roles.txt can use something like
rhtconsulting.jboss_eap,v6.4.7, and tomorrow we do update our roles for 7.0.0 then we will tag that commit as 7.0.0 and users needed EAP 7 could do rhtconsulting.jboss_eap,v7.0.0
if you already have plans to deal this kind of requirements and triaged for now then we are good.


Revert "Add Nginx cache for Mapit"

Nginx caching was originally added as quick way to cache Mapit, whilst work to fix Mapit caching to memcached was being introduced upstream. This fix has now been adopt and Mapit now caches responses in Memcached. This means the Nginx caches a redundant and can be removed to simply our caching set up. It is also preferable to use Memcached over Ngnix, as it allows us to use shared cache across all instance of Mapit. Reverts alphagov/govuk-puppet#10938

Nice one 👍
I wonder if we can also remove
https://github.com/alphagov/govuk-puppet/blob/8445b2f6c2e4c453cdcd6dd2ea9522a99ad2ee18/modules/govuk/manifests/node/s_mapit.pp#L23-L27
since we won't be using memcache on the machines anymore

Yup - good shout! I'll do that in a separate PR, so this PR is just the revert.


When I modify the value of the data of the custom node, then connect the line, an error will be reported.

Hi! Both my nodes and edges are custom.
When I modify the value of the data of the custom node, then connect the line, an error will be reported.

Any more information so that I can actually look at the issue?
Code examples? Reproduction?
Anything?
This tells me literally nothing except that you can do screenshots.

I didn't describe it clearly enough.
<vue-flow
      ref="vueFlow"
      @dragover="onDragOver"
      class="vue-flow-container"
      v-model="elements"
      :zoom-on-pinch="false"
      :zoom-on-double-click="false"
      @connect="onConnect"
      style="background: #F5F6FA;"
>
    <!--custom node-->
</vue-flow>

Next, I will modify the data of the node.

onConnect

Are you using the latest version or are you on another one?

Also is there any more to the error?
Any message that says more than the one's in the screenshot?
Those just indicate that Vue wasn't able to replace an element, which doesn't really tell me why 😄

Also edgeType is not a valid property for edges.
There is only type for edges and nodes, so you code should be changed to
const newEdge = {
	id: uuidv4(),
	source,
	target,
	type: edgeType,
	markerEnd: MarkerType.ArrowClosed,
}

Are you possibly using the data to render components in your node?
It might be that when you "reset" your data obj to {} you cause those components to crash due to missing properties?
I tried to emulate your case and didn't receive any errors for it; Here's a sandbox
I would assume that nothing is wrong with VueFlow's behavior and the issue is somewhere in your structure instead.
Vue Flow doesn't really care about your data property anyway, it's just passed through to your components and not handled by the flow at all.

Also edgeType is not a valid property for edges. There is only type for edges and nodes, so you code should be changed to
const newEdge = {
	id: uuidv4(),
	source,
	target,
	type: edgeType,
	markerEnd: MarkerType.ArrowClosed,
}

Wrong here, the code is type

Yes. I use data to render the component in my node. But the error content is about flow. I also checked the code, data property are not missing.

Are you possibly using the data to render components in your node? It might be that when you "reset" your data obj to {} you cause those components to crash due to missing properties?
I tried to emulate your case and didn't receive any errors for it; Here's a sandbox
I would assume that nothing is wrong with VueFlow's behavior and the issue is somewhere in your structure instead. Vue Flow doesn't really care about your data property anyway, it's just passed through to your components and not handled by the flow at all.

Yes. I use data to render the component in my node. But the error content is about flow. I also checked the code, data property are not missing.

I mean, in my code, I use type. edgeType here it is written wrong.
I am currently using the latest version. Sorry, here is indeed the vue error.

I will try to reproduce in the sandbox.

Hi, I found the reason for the error. Not related to vue-flow, thank you very much for your reply. I will close this issue.
Thank you also for providing such a useful component.


python312Packages.aioesphomeapi: 25.2.1 -> 25.3.1

Diff: https://github.com/esphome/aioesphomeapi/compare/refs/tags/v25.2.1...v25.3.1
Changelog: https://github.com/esphome/aioesphomeapi/releases/tag/v25.3.1
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

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

2 packages failed to build:

esphome
esphome.dist

49 packages built:

home-assistant-component-tests.airthings_ble
home-assistant-component-tests.aranet
home-assistant-component-tests.bluemaestro
home-assistant-component-tests.bluetooth_adapters
home-assistant-component-tests.bluetooth_le_tracker
home-assistant-component-tests.bthome
home-assistant-component-tests.dormakaba_dkey
home-assistant-component-tests.eq3btsmart
home-assistant-component-tests.esphome
home-assistant-component-tests.eufylife_ble
home-assistant-component-tests.fjaraskupan
home-assistant-component-tests.gardena_bluetooth
home-assistant-component-tests.govee_ble
home-assistant-component-tests.homekit_controller
home-assistant-component-tests.ibeacon
home-assistant-component-tests.idasen_desk
home-assistant-component-tests.inkbird
home-assistant-component-tests.iron_os
home-assistant-component-tests.kegtron
home-assistant-component-tests.keymitt_ble
home-assistant-component-tests.lamarzocco
home-assistant-component-tests.ld2410_ble
home-assistant-component-tests.led_ble
home-assistant-component-tests.moat
home-assistant-component-tests.mopeka
home-assistant-component-tests.motionblinds_ble
home-assistant-component-tests.oralb
home-assistant-component-tests.private_ble_device
home-assistant-component-tests.qingping
home-assistant-component-tests.rapt_ble
home-assistant-component-tests.ruuvitag_ble
home-assistant-component-tests.sensirion_ble
home-assistant-component-tests.sensorpro
home-assistant-component-tests.sensorpush
home-assistant-component-tests.snooz
home-assistant-component-tests.switchbot
home-assistant-component-tests.thermobeacon
home-assistant-component-tests.thermopro
home-assistant-component-tests.tilt_ble
home-assistant-component-tests.xiaomi_ble
home-assistant-component-tests.yalexs_ble
python311Packages.aioesphomeapi
python311Packages.aioesphomeapi.dist
python311Packages.bleak-esphome
python311Packages.bleak-esphome.dist
python312Packages.aioesphomeapi
python312Packages.aioesphomeapi.dist
python312Packages.bleak-esphome
python312Packages.bleak-esphome.dist


Can't find "Edit this page" link

I thought we had a link like this on every page. I can't find it. Where did it go?

Hi, I would love to take a stab at this.

Hi @gaearon the issue is in reactjs.org/src/components/MarkdownPage/MarkdownPage.js line 111 where markdownRemark.fields.path && evaluates to null and so the Edit this page, which is what follows, doesn't get shown.

is there any chance this bug comes from GH-1065 where it changes graphql formats for path?

Yes it probably came from that. I am not sure why that was not a breaking change in Gatsby.

Hi, took a look at this an saw the same issue you have already mentioned. I can see gatsby/onCreateNode.js still assigns path to a string:
createNodeField({
  node,
  name: 'path',
  value: relativePath,
});

And src/types.js still has it defined as a string as well.

Not sure if relevant, but Gatsby never gets to this part for me:
https://github.com/reactjs/reactjs.org/blob/master/gatsby/onCreateNode.js#L31

Anyone figured it out?

@gaearon  would love to pick this one up if it is available?

Feel free to use this as a temp fix if @FadySamirSadek  does not find the root cause of why markdownRemark.fields.path is showing up null. I tested this locally, and it looks like it at-least will get all of the edit buttons back up for now.
https://gist.github.com/DZuz14/808c5af1d9120bf860ae56d4ac676506

@FadySamirSadek You can use my fix here if you'd like: https://github.com/reactjs/reactjs.org/compare/master...mknepprath:fix-edit-this-page-button
It appears to be a Gatsby issue that was fixed in a recent patch. Updating from v1.9.273 to v1.9.277 fixes the links when reverting the addition of the ids.

@mknepprath I was thinking the same thing but it generates an error
`error GraphQL Error Field "path" of type "File" must have a selection of subfields. Did you mean "path {... }"?
file: /Users/fadysadek/Documents/projects/reactjs.org/src/pages/docs/error-decoder.html.js
1 |
2 |   query ErrorPageMarkdown($slug: String!) {
3 |     markdownRemark(fields: {slug: {eq: $slug}}) {
4 |       html
5 |       fields {

6 |         path
|         ^
7 |       }
8 |       frontmatter {
9 |         title
10 |       }
11 |     }
12 |     errorCodesJson {
13 |       internal {
14 |         contentDigest
15 |       }
16 |     }
`

This is really confusing, I've the same problem in the Gatsby 2 PR #1104.
I've no idea why path becomes an object when assigning it to therelativePath.
But it will be a string if we append something on it...
createNodeField({
  node,
  name: 'path',
  value: relativePath + 'whatever',  // can't be an empty string and String(relativePath) does not work either
});

I've also tried replicating this with the gatsby-starter-blog but was unable to, so that probably means that there is something wrong in our code or some plugin we are using.
My best guess is that something is checking if the field is a valid url and then converting it.
@KyleAMathews do you have any ideas?

@FadySamirSadek @alexandernanberg Per this https://github.com/gatsbyjs/gatsby/pull/2255, it seems to convert it to a File node due to it being a relative path, so I'd agree that it has something to do with it checking whether it detects that it's a url.
@FadySamirSadek Did you pull my branch and get that error? Very strange, because that's the error I was getting until I updated the package and removed the id subfield - now it works as expected. I'll try again from scratch...

Well, this is strange - I switched to master, reset everything, and it's still fixed for me... The edit link is showing up and I get the reverse error:
GraphQL Error Field "path" must not have a selection since type "String" has no subfields.

  file: /Users/mknepprath/GitHub/reactjs.org/src/pages/docs/error-decoder.html.js

   1 |
   2 |   query ErrorPageMarkdown($slug: String!) {
   3 |     markdownRemark(fields: {slug: {eq: $slug}}) {
   4 |       html
   5 |       fields {
>  6 |         path {
     |              ^
   7 |           id
   8 |         }
   9 |       }
  10 |       frontmatter {
  11 |         title
  12 |       }
  13 |     }
  14 |     errorCodesJson {
  15 |       internal {
  16 |         contentDigest

...Is it a difference between our environments?

By "reset eveything" does that include removing the .cache folder gatsby creates? I've run into some problems with that being cached very hard.

After further investigation, I realized I still had the version in package.json set to ^1.9.277... if I downgrade it back to ^1.9.273, the edit button goes away. That does seem to be the fix - I'll put in a PR!
@alexandernanberg I meant removing node_modules and the .cache, yeah. That made no difference, but the version bump did.

This has me going in circles! Alright, it's not the version bump of gatsby, it's only fixed after I run yarn upgrade gatsby, so it's likely one of the peer dependencies that gets caught in that net and upgraded. I'll report back once I've dug a bit more.

Still not finding 'edit this page link' on website. Is it in progress ?

Fixed by #1226 🎉


python3Packages.cupy: upgrade and fix build

Description of changes
Fixes #197073. See individual commits for details.
I ran the test suite and the basic tests passed. There were several failures in random parts like filesystem paths, and due to missing features/capabilities in the NVIDIA hardware I have access to at the moment. It doesn't appear the upstream test suite is in perfect shape right now.
We should probably look into adding multiple cutensor versions in nixpkgs (as that being out of date was what originally broke cupy). Additionally, the cusparselt (which is evidently not the same as libcusparse) dependency could be packaged and added enable those features.

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

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

3 packages built:

cudaPackages.cutensor
python310Packages.cupy
python39Packages.cupy

This worked for me, thanks! I'll merge it soon if no complaints.


Add .DEREK.yml to each repo in faas-and-furious

Task
Add .DEREK.yml to each repo in faas-and-furious which contains community functions, some of which are used in the function store.
This will result in us being able to accept PRs with sign-off checking and allowing community to administrate PRs and Issues.
You'll get 18 commits which will bump you up in the leaderboard too 💹 whilst also helping the project a lot.
http://kenfdev.o6s.io/github-stats-page#/

Add .DEREK.yml as per the example in openfaas/faas-cli
Add .github/ISSUE_TEMPLATE.md as per https://raw.githubusercontent.com/faas-and-furious/inception-function/master/.github/ISSUE_TEMPLATE.md

Thanks. Happy for multiple people to work on this and coordinate given how many repos are involved.

ah, i prefer my github alias 😄 , but will do that @alexellis

I've checked and linked the two remaining repos to complete the set.  Once merged this issue can be closed.


Naming conventions to be used across openebs projects

OpenEBS needs to put up a placeholder where various naming conventions are standardised.
e.g. use of the terms:

backend vs. replica
frontend vs. frontend controller
volume vs. persistent volume
storage vs. volume
backing storage vs. persistent location
volume provisioner vs. volume provider

The document should also standardise the use of namespaces for constants & property keys.
In addition, Name, UID, ID etc should be similar in spirit across OpenEBS projects.

The following convetions have evolved organically over the past one year and these needs to be documented under the Concepts/Glossary of docs.openebs.io

"openebs.io" namespace is used for all openebs related parameters and objects.
OpenEBS Volume is mapped to a Persistent Volume
OpenEBS Volume comprises of VolumeController and Volume Replicas. Volume Controller acts as the target to which the Application sends the Data. the Volume controller will then send the data synchronously to Volume Replicas.
OpenEBS Replicas write the data to StoragePools. StoragePools are logical objects created by OpenEBS, that are formed using one more Disks or a hostPath.

Add a terminology section in the contributor docs.


Updated to 1.20.1

onnxruntime 1.20.1
Destination channel: defaults
Links

PKG-4844
Upstream repository
Upstream changelog/diff

Explanation of changes:

Removed extra patches
Allow building and testing with numpy 2

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_b1bggl3col/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:51: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:54: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:26: patch_unnecessary: patch should not be in build when source/patches is not set
===== Final Report: =====
1 Error and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_7esrt7hrg5/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:50: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:51: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:53: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:54: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 9 Warnings were found

Linter check found the following problems:
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
ERROR conda.cli.main_run:execute(125): conda run conda-lint /tmp/abs_043oi8d87c/clone failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:48: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:50: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:51: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 9 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_d88fx5i15_/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:53: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:51: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:50: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:51: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:48: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 12 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_b7fsqvqynp/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:54: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:53: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:51: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:50: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 12 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_e768ndmyfk/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:51: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:53: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:50: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:1: missing_test_requirement_pip: pip is required in the test requirements.
===== Final Report: =====
1 Error and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_87vzetust6/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:50: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:51: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:53: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 9 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_cciy_vnkiq/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:51: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:53: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:50: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 9 Warnings were found


difference between valid "acc" and inference "WER"

Hi, everyone.
Recently I ran the ASR example code. I was wondering why the difference between valid acc on train and WER of inference is so different.
In this case, valid set and test set is perfectly same. and I set the prameter, MAX_TOKEN=5000 N_BEST=1 & BEAM=30 to use infer.py

You can see the valid acc on test set, almost models are above 94% but I got WER is about 17% ~ 27%.
I know that 1-WER and acc are different. But I don't understand the huge difference.
Additonaly, I found the strange decode problem.

Some sections of this sentence seem to have been reversed.
I wonder if others get similar results or if it's an infer code problem.
Thank you for reading this issue.

CC @alexeib

@LeeYongHyeok Hi, I am also bothered for this issue, do you get any explanations? I want to reproduce the result in paper for examples/speech_recognition, however, I only achieve WER for 12.1 with a base transformer structure for Librispeech, and achieve about 11 in Aishell1, it is really wired... since the valid acc in Tensorboard almost get 95.0%...
Thanks a lot for u response ；D

what "asr example code" did you run?

@alexeib Just the demo which provided by fairseq. The path is fairseq/examples/speech_recognition, I have tried both vggtransformer_1 and vggtransformer_base in Librispeech and Aishell, however I cannot never reach a WER as 4.8 or 5.* as original paper said....

@okhonko might be a better person to help with this

@liangzhenlin123 I used to modify the model of the example code. The above problem was caused by my mistake missing the VGGblocks for positional encoding of the vggtransformer model.

@LeeYongHyeok Thanks for your reply! I directly run the demo's command line provided originally in README, so I think I don't face this mistake. So can you get the WER as well as this paper "Transformers with convolutiona lcontext for ASR"? BTW, whats your batchsize, have you used "--update-freq" to expand the max tokens?
Thanks a lot!

@liangzhenlin123 I can't remember the detailed parameters, quite a long time ago, but since I ran it with one GPU, maybe i set the max token to 8000 without fixed batch size. If you want a large batch size, I recommend using the --fp16 option.

@LeeYongHyeok Thanks a lot for your patience :).


Tween set_loops() without arguments is always detected as infinite

Godot version
3.5 beta5
System information
Windows 10
Issue description
Cannot make an infinite loop even when the tween has interval.

Steps to reproduce
Put this into the script.
func _ready():
	var t = create_tween()
	t.set_loops()
	t.tween_interval(0.5)
	t.tween_callback(self,"print_test")

func print_test():
	print(1)

Minimal reproduction project
No response

This is fixed in newest rc, update Godot.


Vscode cannot paste any text from Edge browser

I tried to copy the text content of the edge browser to vscode, but I could not paste it, and the chrome browser can meet this requirement.
VscodeVersion：1.60.0

I'm having this problem in Firefox also. Using Fedora 34, VSCode 1.60.0 and Firefox 91.0.2.

/gifPlease


Inconsistency - Link previews have different border color than quotes

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the app.
Send a quote message in any chat. ex - > hello.
Send a link. ex - google.com and wait for the link preview to appear.
Notice that the left border has a different color in both cases.

Expected Result:
Border color should be consistent for both link previews and quote.
Actual Result:
Border color is different for both link preview and quote.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: 1.3.33-4
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/de42dbc7-a466-45f3-84a1-cf3b68ec1c43
Expensify/Expensify Issue URL:
Issue reported by: @Nikhil-Vats
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1687966486390789
View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
Left border color for link previews is inconsistent with blockquote's left border color.
What is the root cause of that problem?
We are using a different color for link previews left border.
https://github.com/Expensify/App/blob/a23d1614c0e60f99dd51cf6f4fd08f65248203d1/src/styles/styles.js#L3364-L3369
https://github.com/Expensify/App/blob/a23d1614c0e60f99dd51cf6f4fd08f65248203d1/src/styles/styles.js#L2680-L2681
What changes do you think we should make in order to solve the problem?

We should just change the border color used for link previews to be the same as other one - themeColors.border.
Optionally, we can also remove the function getTransparentColor which was added for link previews border color and is only used there.
What alternative solutions did you explore? (Optional)
NA

My proposal above.

@Nikhil-Vats you mean these two are different colors, right?

Yes @mallenexpensify .

@mallenexpensify This was reported by Shawn here and @wojtus7 provided confirmation here.

Thanks @Nikhil-Vats, moving this along

@aimane-chnaif , please review @Nikhil-Vats 's proposal above

Thanks for the review @aimane-chnaif, assigning @Nikhil-Vats 🚀

@aimane-chnaif @mallenexpensify @marcochavezf PR is ready for review.

@thienlnam Melv incorrectly identifies the reporter as it doesn't consider '-' in the GH handle for reporter only (it works well for assignee). Is this a known issue?
@mallenexpensify This issue was actually reported by @shawnborton here. I just created the bug report for it so you can remove me from the issue description as bug reporter.

Thanks @Nikhil-Vats , I opened an internal GH to address the - bug.  Removed  ya from the OP for bug reporter too.

@aimane-chnaif and @Nikhil-Vats paid $1500 each, inc. urgency bonus. Apologies for the delay, I was OOO a couple days.
@aimane-chnaif , please fill out the checklist above.
https://github.com/Expensify/App/issues/21882#issuecomment-1635953496

For auditing, posting the format below
Issue reporter: none
Contributor: @aimane-chnaif $1500 paid via Upwork, inc. urgency bonus
Contributor+: @Nikhil-Vats $1500 paid via Upwork, inc. urgency bonus
@aimane-chnaif can you please fill out the checklist above so we can close this issue? Thx


OSD-23467: Facilitate usage of osdctl dynatrace logs

OSD-23467: Facilitate usage of osdctl dynatrace logs

Add clusterID fetching from current cluster context as default for dynatrace logs command, can still use --cluster-id flag to provide clusterID manually.

Amend --po, --container, --namespace, flags to better align with oc logs command flags.

Add examples to command to help with use.

@devppratik Thank you for the suggestions, all changed accordingly now.

Thanks for the work @MateSaary
This is really awesome

/lgtm
/approve


AGORA-1455 As an OP Delegate, I should be able to vote with partial delegated voting power

When i tested with 0xe538f6f407937ffDEe9B2704F9096c31c64e63A8, which had 10 OP (norm) and 10.9 OP (Adv). It only triggered one trx at a time, so i had to click the button twice

When i tested with 0xe538f6f407937ffDEe9B2704F9096c31c64e63A8, which had 10 OP (norm) and 10.9 OP (Adv). It only triggered one trx at a time, so i had to click the button twice.
I don't think a normal user would know to do this

@yitongzhang  There might've been an query error when pulling votes. It was resolved with merge.
This is my experience: https://www.loom.com/share/016bee4cc2b04a97b0d76deb4f958e32?sid=bfe88328-ccf9-487c-9c39-d02826b845eb
Let me know if you still having issues! A video would be nice


Nosetests opening too many files

Sometimes running the tests seems to run into system resource limits for open files, causing tests to fail.  Here are two sample runs that illustrate this problem, the first using run_tests.py and the second just executing nosetests directly:
https://gist.github.com/dcolligan/a8743d84a302529b161a
https://gist.github.com/dcolligan/bca0d356fb3ad367f235
The default open file limit on OSX Mavericks (my environment) is 256.  You can find out yours by using any of these commands:
launchctl limit maxfiles
python -c "import resource; print(resource.getrlimit(resource.RLIMIT_NOFILE))"
ulimit -n

I got around this by bumping up my resource limits: http://unix.stackexchange.com/questions/108174/how-to-persist-ulimit-settings-in-osx-mavericks
I'm not sure what is causing the open files count to explode.  We seem to close all subprocesses that we launch in the tests.  Maybe we are just opening a large amount of packages / test files.  Or maybe nosetests manages its file handling stupidly.  Not sure.

Interesting... can you try to wrap an strace around it please? I don't see any good reason for opening that many files.

OSX has dtruss, which is similar; here's a run of sudo dtruss nosetests > dtruss.txt 2>&1 https://gist.githubusercontent.com/dcolligan/ccde9e6a0a3a941dca0b/raw/dtruss.txt

Hmmm, looks pretty normal to me  from our side. We seem to hit errors very early on in the process, so I'm guessing it's a problem particular to your setup. Install a Linux VM on your machine?

I'm happy to close this issue if no one else is having it.  I don't think nosetests is going to exceed a two-orders-of-magnitude increase in file limits anytime soon.

Maybe a missing try/finally block with a close?  It seems very
odd that any of the tests I have looked at would open more than
a few files.
Danny Colligan<EMAIL_ADDRESS>writes:

I'm happy to close this issue if no one else is having it. I don't think
nosetests is going to exceed a two-orders-of-magnitude increase in file limits
anytime soon.
—
Reply to this email directly or view it on GitHub.*

Nope, I'm wrong, it is a real problem. On my machine
strace nosetests 2>&1 | grep ^read | tail

shows that the last fd number is > 500, which is definitely wrong. We're missing a close somewhere...

Are you sure that indicates a problem?  Does the OS reuse file descriptors?  That is, if fd 1 is opened and then closed, will the next opened file be fd 1 or 2?  If the later, that would not seem to indicate a problem.  (Not sure of the answer myself, and could be OS-dependent... )
It seems like the errors are happening a lot around wormtable functionality.  Perhaps it's a bug in the library?

Just ran a little experiment which suggests that fds are indeed reused, so the fd number indicates the number of simultaneously open files for that process, which would indicate a problem: https://gist.github.com/dcolligan/15d946087b0c65949be0

Yeah, looks like a wormtable issue. Digging into it now...

It reuses.  The limit is the current number that are actually open.  Worm table
maybe reopening database unnecessarily.  On linux, it's easy to see what is
open by stopping the program and looking in  /proc//fd/
Not sure how on the mac, they have never implemented the /proc
pseudo file system.
Danny Colligan<EMAIL_ADDRESS>writes:

Are you sure that indicates a problem? Does the OS reuse file descriptors? That
is, if fd 1 is opened and then closed, will the next opened file be fd 1 or 2?
If the later, that would not seem to indicate a problem. (Not sure of the
answer myself, and could be OS-dependent... )
It seems like the errors are happening a lot around wormtable functionality.
Perhaps it's a bug in the library?
—
Reply to this email directly or view it on GitHub.*

If it's easy to reproduce, I can help track this down the some day when I don't have
meeting hell..
Danny Colligan<EMAIL_ADDRESS>writes:

Just ran a little experiment which suggests that fds are indeed reused, so the
fd number indicates the number of simultaneously open files for that process,
which would indicate a problem: https://gist.github.com/dcolligan/
15d946087b0c65949be0
—
Reply to this email directly or view it on GitHub.*

OK, I've made a bit of progress on this. Basically we're not cleaning the backend up properly and we're leaking lots of file descriptors when we do the tests. I've added a quick cleanup method which reduced the maximum fd used from ~500 down to ~200. This is still too high, but acceptable. I'll look into it some more and see if I can track the leak down.

I'm running into this problem too. Took an strace and graphed the file numbers as they show up in read(###,...) calls.  Stack trace is here: https://gist.github.com/miketwo/d13bed512ed680913f02#file-nose_output-txt

Hope this helps.

We're ripping out wormtable, and this seems like a wormtable bug, so it's doubtful anyone is going to spend time fixing it.  Closing.

I'm shedding a tear of nostalgia :)


custom registered type name should be used in class templates as well

printing the name of following type:
std::cout << type::get<std::reference_wrapper<std::string>>().get_name() << std::endl;

Results in following output with MSVC 2015:
class std::reference_wrapper<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > >

Desired output:
class std::reference_wrapper< std::string >

Every type with which has the original type name included should be replaced with the custom registered name. That are normally templates, but function ptrs should also be honored...
Coding starting point:
type_register.cpp
std::string type_register_private::derive_name(const type_data& wrapper_type, const type_data& array_raw_type, string_view name)

@rovarma
Can you help me to fix this?
With the new get_template_arguments() is should be not that difficult anymore.


Is Pinceau Supporting >=Vue2.7?

Hello, I'm a new member of the group. Thank you for providing us with a great product.
I have a few questions. I would be a newbie so sorry if I said something out of line.
Also, I'm not good at English, so sorry if it's hard to understand you.
I'm developing UI libraries using @vitejs/plugin-vue2, vue2.7, and @storybook/builder-vite.
In my storybook,  to set <link rel="stylesheet" href="./node_modules/.vite/pinceau/index.css" /> in preview-head.html and config.plugins.push(pinceau()) in viteFinai(config) is work for me.
But the build(vite build) fails.
questions:

Is it possible to use pinceau with vue2?
Are there any better solution to use pinceau in the storybook?

I'm afraid it might be impossible to run it with Vue 2.7, yet I would love to look at your repo to check it out!
Could you provide me with a reproduction?

I'm afraid it might be impossible to run it with Vue 2.7, yet I would love to look at your repo to check it out!
Could you provide me with a reproduction?

Sorry, the project is the library is for internal use only, so it cannot be made public.
For reproduction, I'll prepare a similar environment in another repository, so wait a moment


Keybase Install Error After Updating to macOS High Sierra

Error message:

We were unable to load KBFS (Fuse kext). This may be due to a limitation in MacOS where there aren't any device slots available. Device slots can be taken up by apps such as VMWare, VirtualBox, anti-virus programs, VPN programs and Intel HAXM.
Please run keybase log send to report the error.

my log id: d7f49f1cef6f38ee161a8e1c

thanks.  Did you click "ignore" or "quit"?

@maxtaco I've tried both, clicking "ignore" will allow the UI to load but /keybase is empty.

ok, great.  Well that's working as intended.  Are you indeed running any of those programs listed? VMWare, VirtualBox, etc?

I do have VirtualBox and TunnelBlick installed, but no VMs running or VPN tunnels active.

Yeah it probably doesn't matter, i think they swoop in in front of keybase and grab the KEXT slots.  There's not much more we can do.

cc: @cjb / @chrisnojima, not sure if there is any mitigations we have up our sleeves.

A reboot seems to have cleared it (duh, should have tried that!) - a useful improvement would be to display some kind of info about what other devices are holding the slots, but I guess it's a race for the Kext slots.
Will close for now, thanks!

Ah good to know, thanks!
On Fri, Oct 6, 2017 at 5:41 PM, Craig Watson<EMAIL_ADDRESS>wrote:

Closed #8888 https://github.com/keybase/client/issues/8888.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/8888#event-1282554446, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA05_-rU8N4YpdLrvS-7rJsmK7fMgCdaks5spp6VgaJpZM4PxDdc
.

I am getting that same error message when Keybase starts and I do not run any VM or VPN software. I do have Sophos antivirus so I will try stopping that to see if it makes a difference.
But my real question is that the error message tells me: "Please run keybase log send to report the error." I have no idea where to do that. I can't find that function in any menu and I can't find a Keybase command prompt to type that.

I am also getting this error. I have restarted mult times and every time I restart and keybase starts up, I see this error. I have nothing mounted and have no VMs installed. I believe it's what stopping me from accessing keybase files from finder. Anyone still around on this post to help?

@strib sometimes has a suggestion or two

@danielbressan please do a keybase log send and post the resulting log ID.  I'd prefer a new github issue if you can, this one is closed.


Why assign :filter => :ip_address as default even though :unique option is set to false?

Even though the cache_options[:unique] is false, :filter still gets assigned to :ip_address, which seems kind of weird to me. I assume if we set unique to false that means we don't want any filter but all records.
https://github.com/charlotte-ruby/impressionist/blob/master/lib/impressionist/update_counters.rb#L45-L47
Is it designed to be this way to avoid updating the impressionable class every time, or is it a bug that we should set :filter to :all if unique options is false?
Just want to confirm before sending a pull request. :bow:

I'm not using this gem anymore and has no interest in driving this issue, please allow me to close it 🙇


Add egress ip workload image

eipValidator image is used by kube-burner-ocp egress IP workload. nginxEchoIP image is used in e2e-benchmarking egress IP workload to create custom nginx server in external AWS instance.
This PR is required for
https://github.com/kube-burner/kube-burner-ocp/pull/28
https://github.com/cloud-bulldozer/e2e-benchmarking/pull/699

I also have built quay.io/vkommadi/eip-checker:latest with the latest Containerfile and tested with kube-burner-ocp

Tested this locally ( MAC M1 ) works as expected