Problem with empty io.kubernetes.container.terminationMessagePath tag when using OpenTSDB sink

Heapster outputs metrics with an empty io.kubernetes.container.terminationMessagePath tag, which makes OpenTSDB unable to accept those. Heapster should report the default path (/dev/termination-log) or there should be a way to omit empty tags completely. Or am I missing something?

we should probably skip empty metric labels in the OpenTSDB sink, then.  Assigning to the OpenTSDB maintainer.

cc @bluebreezecf

As per https://github.com/OpenTSDB/opentsdb/issues/412 and current OpenTSDB logic it looks that empty tags are not allowed. I would mark tag where value is empty with defaultTagValue or delete this tag at all. What do you think? I will be glad to send quick PR if needed.

@jakon89
In my preview tries, the OpenTSDB does not allow empty tags. So i prefer to send defaultTagValue if the value if empty.

mark tag where value is empty with defaultTagValue

Would defaultTagValue be something like ____empty_tag_value ?


1023 error boundary

Closes #1023
Summary
We were previously not exporting Carbon's ErrorBoundary and ErrorBoundaryContext component. This PR exports and adds the stories to our storybook

Added ErrorBoundary  folder that holds story
updated index.js to include export for ErrorBoundary and ErrorBoundaryContext

Acceptance Test (how to verify the PR)

Go to ErrorBoundary story and make sure they work. Open up the welcome story dropdown and see that these two components are on the list of Exports.

Code looks good, will check the story when the deployment is ready

:tada: This PR is included in version 2.128.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Consider support/handling of System.IO

http://forums.bridge.net/forum/general/open-discussions/1320

The System.IO namespace appears to be unimplemented. At least some basic support should be available as an extension package. Especially the exceptions like System.IO.TimeoutException should be available. While they are in the System.IO namespace they get used elsewhere.
In terms of the System.IO namespace, I think supporting Stream, Reader, Writer, and MemoryStream along with the readers/writers such as BinaryReader, BinaryWriter, TextReader, TextWriter etc would be sufficient. It would at least allow existing code that accepts a stream/reader/writer parameter. It occurs to me supporting the encoding classes would probably be necessary to help with the IO routines as well.

Hi, is there any movement on this? I am really hoping to get access to the following:
System.IO.Stream
System.IOBinaryWriter
System.IO.BinaryReader
Together these 3 classes would support almost any case for reading and writing data efficiently from a HTML5 Typed Array.
My case is a complete 3D engine platform and editor where all resource data is abstracted to a byte[]. If correctly implemented, the data should be read as a stream, along with pointer offsets, as this is highly optimized and required for the WebGL buffer channels.
Link to reference and notable nod to WebGL. http://www.html5rocks.com/en/tutorials/webgl/typed_arrays/

Hello. Unfortunately we have not been able to make any progress with this functionality.

@PluginIO, I have made a pull request: #2789. It has MemoryStream, BinaryWriter, BinaryReader and Stream. BinaryWriter and BinaryReader do not have Write(string) and ReadString since there are no Encodings.

This is really great news. I will take a look ASAP and thanks for the heads up.


Add defer close to open files

Related to #162
Windows is a bit picky on opened files.

hey @odacremolbap, could you also take this change in the file you updated? Have no idea how it got it. Thanks.


Error: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130...

Describe the bug
To Reproduce
Expected behavior
Screenshots
Applicable Versions:

Netlify CMS version<EMAIL_ADDRESS>Git provider: git-gateway
Browser version: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.122 Safari/537.36

CMS configuration
local_backend: true
public_folder: /img
media_folder: static/img
slug:
  encoding: unicode
  clean_accents: false
  sanitize_replacement: "-"
display_url: https://bigduckmusic.com
publish_mode: simple
backend:
  name: git-gateway
  branch: master
  commit_messages:
    create: Create {{collection}} “{{slug}}”
    update: Update {{collection}} “{{slug}}”
    delete: Delete {{collection}} “{{slug}}”
    uploadMedia: "[skip ci] Upload “{{path}}”"
    deleteMedia: "[skip ci] Delete “{{path}}”"
collections:
  - name: blog
    label: Features
    folder: src/pages/features
    create: true
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}"
    fields:
      - label: Template Key
        name: templateKey
        widget: hidden
        default: blog-post
      - label: Title
        name: title
        widget: string
      - label: Publish Date
        name: date
        widget: datetime
      - label: Description
        name: description
        widget: text
      - label: Review
        name: isReview
        widget: boolean
        default: false
      - label: Spotify link
        name: spotify
        widget: string
      - label: Spotify link
        name: spotifyL
        widget: spotify
      - label: Featured Post
        name: featuredpost
        widget: boolean
        default: false
      - label: Featured Image
        name: featuredimage
        widget: image
      - label: Body
        name: body
        widget: body
      - label: Tags
        name: tags
        widget: list
    publish: true
    sortableFields:
      - commit_date
      - title
      - date
      - commit_author
      - description
  - name: gigs
    label: Gigs
    folder: src/pages/gigs
    create: true
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}"
    fields:
      - label: Template Key
        name: templateKey
        widget: hidden
        default: gig-post
      - label: Title
        name: title
        widget: string
      - label: Spotify link
        name: spotify
        widget: string
      - label: Publish Date
        name: date
        widget: datetime
      - label: Description
        name: description
        widget: text
      - label: Featured Post
        name: featuredpost
        widget: boolean
      - label: Featured Image
        name: featuredimage
        widget: image
      - label: Body
        name: body
        widget: markdown
      - label: Tags
        name: tags
        widget: list
      - label: Carousel
        name: Carousel
        widget: list
        fields:
          - label: image
            name: image
            widget: image
    publish: true
    sortableFields:
      - commit_date
      - title
      - date
      - commit_author
      - description
  - name: picks
    label: picks
    folder: src/pages/picks
    create: true
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}"
    fields:
      - label: Template Key
        name: templateKey
        widget: hidden
        default: picks-page
      - label: Publish Date
        name: date
        widget: datetime
      - label: Title
        name: title
        widget: string
      - label: Featured Images
        name: featuredimages
        widget: list
        fields:
          - label: image
            name: image
            widget: image
          - label: link
            name: link
            widget: string
    publish: true
    sortableFields:
      - commit_date
      - title
      - date
      - commit_author
  - name: pages
    label: Pages
    files:
      - file: src/pages/index.md
        label: Landing Page
        name: index
        fields:
          - label: Template Key
            name: templ
...

create: Create {{collection}} “{{slug}}”
update: Update {{collection}} “{{slug}}”
delete: Delete {{collection}} “{{slug}}”
uploadMedia: "[skip ci] Upload “{{path}}”"
deleteMedia: "[skip ci] Delete “{{path}}”"

Are those “ and ” quotes actually in your config file? If so, you may want to replace them with regular " quotes and see if you still get that error.

Hi @rickithadi, can you share the full error and config.yml? The error usually comes from a custom preview template

Closing per lack of response


Development version 0.15.0.dev0

Description:
Development version 0.15.0.dev0
Issue Reference URL
https://github.com/awslabs/aws-eks-data-maker/issues/

Do not change content below. Mark applicable check boxes only.
Thank you for submitting a contribution to AWS Orbit Workbench.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a ISSUE associated with this PR?
[ ] Does your PR title start with ISSUE-XXXX where XXXX is the issue number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[ ] Has your PR been rebased against the latest commit within the target branch (typically 'main')?
[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under Apache License 2.0?

Already pushed this , we can close this PR


new question added and new style and assets added

Please check if this PR fulfills these

[x] The commit message is descriptive of changes
[x] You have tried at least one local test (this includes viewing the changes on your local fork)
[x] Docs have been added / updated as needed (for bug fixes / features)

What kind of change does this PR introduce?

[x] Typo / Doc Update
[x] Bug Fix
[ ] Feature / New Item

What is the new behavior (if this is a feature change)?

[ ] Added Interview Technical Question
[x] Added Interview Whiteboard Question
[ ] Corrected existing items
[ ] Other

Adding new question ? Please check if this PR fulfills these

[x] <title> tag has been updated
[x] <h1> tag has been updated
[x] new file is kabob-case-like-this.html
[x] link to question has been added in technical.html or whiteboard.html

Other information:

Thanks, for your feedback. I will make the changes as soon as possible.
On Thu, Oct 3, 2019, 8:50 PM Luke Schlangen<EMAIL_ADDRESS>wrote:

@LukeSchlangen requested changes on this pull request.
This should probably be split into two separate PRs:

Breadth-first search

Fix a few typos (breadth-first instead of breath-first)
Add link to whiteboard questions html
This part is really close!

Style changes

There are a lot of style changes here. Especially as minimized,
it is difficult to understand the impact of these changes, and it makes
this project less approachable (if someone wanted to update the styles in a
small way, it would be hard to do so). We likely won't accept this part of
this Pull Request.

This is exciting! I'm looking forward to your updates and getting this
merged!
In views/questions/whiteboard/breath-first-search.html
https://github.com/approachable-io/software-interview-prep/pull/137#discussion_r331097250
:

@@ -0,0 +1,75 @@
+
+

+

Breath First Search | Software Interview Whiteboard Questions

Small typo: Breadth First
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/approachable-io/software-interview-prep/pull/137?email_source=notifications&email_token=AGH256HERKRSTP5527SKVFLQMYETBA5CNFSM4I5CO2NKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCGZQ5NI#pullrequestreview-296947381,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGH256GYWUFNGHLDXQGK2LTQMYETBANCNFSM4I5CO2NA
.

Great work! Thank you so much for your contribution!

Great to hear from you .
On Fri, Oct 4, 2019, 6:14 PM Luke Schlangen<EMAIL_ADDRESS>wrote:

Merged #137
https://github.com/approachable-io/software-interview-prep/pull/137
into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/approachable-io/software-interview-prep/pull/137?email_source=notifications&email_token=AGH256AJTUHKPJ6UEFYDW3LQM43C5A5CNFSM4I5CO2NKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUAWKKOI#event-2687280441,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGH256EF7MOK22IPNLJ7MDTQM43C5ANCNFSM4I5CO2NA
.


Bump multiple dependencies

Bump github.com/operator-framework/api from 0.19.0 to 0.20.0
Bump k8s/io group from 0.28.4 to 0.29.1
Bump github.com/onsi/ginkgo/v2 from 2.13.1 to 2.15.0
Bump github.com/onsi/gomega from 1.30.0 to 1.31.0

/lgtm


Version 2.0.7 on npm missing extension fix

Version 2.0.7 on npm is missing the extension fix
Version 2.0.5 on npm has the fix, on version 2.0.6 on npm I haven't tested it

I can't reproduce it: I've downloaded the latest npm package and inspected it
and the extension fix is still in it:


Column name has changed

The column name in the dataset is no longer called Company response, but rather Company response to consumer.
This must be changed in the script, or a null reference exception is encountered with the merge statement.

Thank you.


Documentation for compaction

Probably best to put in the advanced section on the site

Topic compaction documentation is available in https://pulsar.incubator.apache.org/docs/latest/cookbooks/compaction/


.Net: Bug: Unable to use Semantic Kernel on .Net Framework 4.8

Describe the bug
It is not possible to use the SK on .NET framework.
To Reproduce
Steps to reproduce the behavior:

Create a console application for .NET FW 4.8
Install the Microsoft.SemanticKernel nuget package. Version 1.32 is selected.
This will fail with this message
Unable to find a version of 'Azure.AI.OpenAI' that is compatible with 'Microsoft.SemanticKernel.Connectors.AzureOpenAI 1.32.0 constraint: Azure.AI.OpenAI (= 2.1.0-beta.2)'.

Expected behavior
This should work, so that I can build semantic kernel applications on the .NET FW. You are shipping the code as .NET standard 2.0, so this should work?
Platform

OS: Windows
IDE: Visual Studio
Language: C#
Source: Nuget version 1.32 of MicrosoftSemanticKernel

Additional context
Normally I would build with .NET, not the FW, but there are important constraints that force me to use FW (must run inside Visual Studio).

Installing the Azure.AI.OpenAI nuget prior to the semantic kernel does not fix the issue.

@pvillads , have a look on this issue.

https://github.com/microsoft/semantic-kernel/issues/9755

Installing previously the Azure.AI.OpenAI should fix the problem, but make sure you are installing the pre-release (2.1.0-beta), not the GA (2.0.0).
You may also receive similar notification for other packages like in the issue above.

Thank you. I will give it a spin.
However, I would not like to ship anything with preview or beta versions for customers. I am hoping these issues go away as the preview and beta items transform into GA versions.
BR PV
From: Mark Wallace @.>
Sent: Monday, December 16, 2024 4:15 AM
To: microsoft/semantic-kernel @.>
Cc: Mention @.>; Author @.>; Comment @.***>
Subject: Re: [microsoft/semantic-kernel] .Net: Bug: Unable to use Semantic Kernel on .Net Framework 4.8 (Issue #9966)
@pvilladshttps://github.com/pvillads I installed the following (in order) to get this to work:

Microsoft.Extensions.AI.Abstractions.9.0.1-preview.1.24570.5
Microsoft.Extensions.VectorData.Abstractions.9.0.0-preview.1.24523.1
Azure.AI.OpenAI.2.1.0-beta.2
Microsoft.SemanticKernel.1.32.0

Reply to this email directly, view it on GitHubhttps://github.com/microsoft/semantic-kernel/issues/9966#issuecomment-2545471767 or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACYNH7LQJEIMPOSPH4D2IZD2F275PBFKMF2HI4TJMJ2XIZLTSWBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVI2TEMBVGAYTIMJVHCSG4YLNMWUWQYLTL5WGCYTFNSBKK5TBNR2WLKRVGIZTIMJWGI2DOONENZQW2ZNJNBQXGX3MMFRGK3FMON2WE2TFMN2F65DZOBS2YSLTON2WKQ3PNVWWK3TUUZ2G64DJMNZZJAVEOR4XAZNKOJSXA33TNF2G64TZUV3GC3DVMWUTMMBXGI4DSMJYGWBKI5DZOBS2K2LTON2WLJLWMFWHKZNKGI3TGNZSGE3TONRVQKSHI6LQMWSWYYLCMVWKK5TBNR2WLKRVGIYDKMBRGQYTKOECUR2HS4DFUVWGCYTFNSSXMYLMOVS2UNJSGM2DCNRSGQ3TTJ3UOJUWOZ3FOKTGG4TFMF2GK.
You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Remove dead code and duplicate codes

Codecov Report

Merging #264 (aaa75bb) into master (4b7ef39) will decrease coverage by 0.57%.
The diff coverage is 91.30%.

@@             Coverage Diff              @@
##             master     #264      +/-   ##
============================================
- Coverage     70.36%   69.78%   -0.58%
+ Complexity      650      646       -4
============================================
  Files            94       94
  Lines          2038     1986      -52
  Branches        277      274       -3
============================================
- Hits           1434     1386      -48
+ Misses          494      490       -4
  Partials        110      110

Impacted Files
Coverage Δ

...a/seedu/masslinkers/logic/commands/ModCommand.java
100.00% <ø> (ø)

...ava/seedu/masslinkers/logic/parser/ParserUtil.java
92.22% <ø> (ø)

...main/java/seedu/masslinkers/model/student/Mod.java
92.10% <ø> (ø)

...va/seedu/masslinkers/model/util/ModComparator.java
100.00% <ø> (ø)

...edu/masslinkers/logic/parser/ModCommandParser.java
86.90% <90.90%> (+0.87%)
:arrow_up:

...eedu/masslinkers/logic/commands/ModAddCommand.java
70.00% <100.00%> (ø)

...inkers/logic/parser/exceptions/ParseException.java
50.00% <0.00%> (-50.00%)
:arrow_down:

...kers/commons/exceptions/IllegalValueException.java
50.00% <0.00%> (-50.00%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Cleanup: Remove Setup and Keccak (Setup) example

It doesn't make much sense to do trusted setup in a mobile app, so we can remove this.
We also want to remove this API usage in other parts of the code.

A bunch of this was removed from recent PR #75 by @vivianjeng
Maybe some left-overs for Setup, not sure?

They are all replaced by proving with arkzkey and wasm
The issue can be closed. 🙏🏻

This is a separate issue from O now I realize, but we probably want to make this cleaner: https://github.com/oskarth/mopro/blob/main/mopro-ffi/src/lib.rs right now two generate_proof functions and it is a bit confusing which to use.
https://github.com/oskarth/mopro/blob/main/mopro-ffi/src/lib.rshttps://github.com/oskarth/mopro/blob/main/mopro-ffi/src/lib.rs 3 initialize functions, two generate proof, two verify proof and two interfaces :D
We'd want to simplify this a bit, and if there are options (like dylib, arkzkey, path etc) it should be clear. I believe this is also what @Meyanis95 referred to earlier in chat.

On OP issue we still have https://github.com/oskarth/mopro/blob/main/mopro-ios/MoproKit/Example/MoproKit/KeccakSetupViewController.swift with Setup in it. I think we should make this part more explicit, and maybe even remove some examples (?)


SimpleBlobDetector

Can I use SimpleBlobDetector to calculate speed of vehicle?
Plz give me some hint to do this?

Car Speed Detector


Domain activation is Failed - One or more of the CNAMEs you provided are already associated with a different resource.

App Id: d9kq0ggl8z9ty
Region: eu-central-1
Step: Domain activation
Status: Failed
Error message
Error message: One or more of the CNAMEs you provided are already associated with a different resource.
Notes
We used the domain before for a CloudFront distribution but we deleted everything.

@marcschroeter I have checked the records. Looks like the domain status is available now. Free free to contact us if you still have problems.


sudo docker-compose up   error

mysql_1  | Version: '5.7.16'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)

This is actually not an error report. Please post in details.


Is the YAML in the democode valid YAML?

Hi,
Very many thanks for all your work on this excellent codebase. It is a great job.
A question/issue re YAML please.
On editing some of the sidebar YAML files in the _data/ folder, am getting a build error on github pages.
So to troubleshoot the YAML syntax was trying to use a YAML validator such as http://beautifytools.com/yaml-validator.php
However if I put this yaml from your working demo code;
https://github.com/tomjohnson1492/documentation-theme-jekyll/blob/gh-pages/_data/sidebars/home_sidebar.yml
into that tool, am getting an error.
"Error : Unable to parse.
Line : 6    - title: Products"
So am struggling to work from a basic yaml syntax that is known to be valid YAML
Am assuming this is not completely unknown to you/others?
many thanks in advance
Tony

I think the issue may be that line breaks (spaces) are not liked in the YAML validators
so instead of ;
entries:

title: Sidebar
levels: one
folders:

title: Products
output: web
folderitems:

title: News
url: /news.html
output: web
title: Theme instructions
url: /mydoc_introduction.html
output: web
title: Product 1
url: /p1_landing_page.html
output: web
title: Product 2
url: /p2_landing_page.html
output: web

which fails the YAML validator..
this seems to pass;
entries:

title: Sidebar
levels: one
folders:

title: Products
output: web
folderitems:

title: News
url: /news.html
output: web
title: Theme instructions
url: /mydoc_introduction.html
output: web
title: Product 1
url: /p1_landing_page.html
output: web
title: Product 2
url: /p2_landing_page.html
output: web

Now I can the YAML validator ok.
thanks


unik build "compile: signal: killed"

I'm still getting a signal killed message during the build process of a fairly complex go code base (as mentioned in #27).
Is there anyway to debug the problem further. I've checked for obvious things:

no longer importing runtime packages
no _linux (etc) source files
no os specific build flags

Tried building inside the container as suggested in #13 - but still only see the signal: killed message. The package it fails in is fairly large, could it be running out of memory in the image?

i think you are correct that this is probably a memory issue.

Anyway of extending the images to fix this or am I out of luck in this case?

unfortunately, I can't reproduce this error on my side to know whether or not this will fix it. however, I would like you to modify the UniK source in the following file: https://github.com/emc-advanced-dev/unik/blob/master/pkg/compilers/rump/generic.go#L123
I want to see if adding the flag --memory=inf to the docker run command fixes this issue.
so, take the function
func execContainer(imageName string, cmds, binds []string, privileged bool, env map[string]string) error {
	dockerArgs := []string{"run", "--rm"}
	if privileged {
		dockerArgs = append(dockerArgs, "--privileged")
	}
	for _, bind := range binds {
		dockerArgs = append(dockerArgs, "-v", bind)
	}
	for key, val := range env {
		dockerArgs = append(dockerArgs, "-e", fmt.Sprintf("%s=%s", key, val))
	}
	dockerArgs = append(dockerArgs, imageName)
	dockerArgs = append(dockerArgs, cmds...)
	cmd := exec.Command("docker", dockerArgs...)
	unikutil.LogCommand(cmd, true)
	if err := cmd.Run(); err != nil {
		return errors.New("running container "+imageName, err)
	}
	return nil
}

and replace it with
func execContainer(imageName string, cmds, binds []string, privileged bool, env map[string]string) error {
	dockerArgs := []string{"run", "--rm", "--memory=inf"}
	if privileged {
		dockerArgs = append(dockerArgs, "--privileged")
	}
	for _, bind := range binds {
		dockerArgs = append(dockerArgs, "-v", bind)
	}
	for key, val := range env {
		dockerArgs = append(dockerArgs, "-e", fmt.Sprintf("%s=%s", key, val))
	}
	dockerArgs = append(dockerArgs, imageName)
	dockerArgs = append(dockerArgs, cmds...)
	cmd := exec.Command("docker", dockerArgs...)
	unikutil.LogCommand(cmd, true)
	if err := cmd.Run(); err != nil {
		return errors.New("running container "+imageName, err)
	}
	return nil
}

then recompile UniK (either with go build, assuming you've got UniK in your GOPTAH, or using docker with make binary)

also, maybe you need to increase the amount of memory allocated to the docker host if you are using docker-machine?

ok let me try and see if that helps

thank you

i'm sorry; this is invalid syntax. apparenlty there is no default memory limit for containers; which means the host itself is running out of memory.you can try running with memory swap. to use memory-swap instead, use the following:
func execContainer(imageName string, cmds, binds []string, privileged bool, env map[string]string) error {
	dockerArgs := []string{"run", "--rm", "--memory-swap=-1"}
	if privileged {
		dockerArgs = append(dockerArgs, "--privileged")
	}
	for _, bind := range binds {
		dockerArgs = append(dockerArgs, "-v", bind)
	}
	for key, val := range env {
		dockerArgs = append(dockerArgs, "-e", fmt.Sprintf("%s=%s", key, val))
	}
	dockerArgs = append(dockerArgs, imageName)
	dockerArgs = append(dockerArgs, cmds...)
	cmd := exec.Command("docker", dockerArgs...)
	unikutil.LogCommand(cmd, true)
	if err := cmd.Run(); err != nil {
		return errors.New("running container "+imageName, err)
	}
	return nil
}

my docker-machine only had the default 1GB and so was killing the process. I've upped it to 8GB which built the unikernel 👍
Next quest - how to get a file into the image.

working on that... right now only Go sources will be compiled into the image. We're working on baking static assets into images (#18)
hopefully this isn't a big blocker for you; I'll make sure to fast-track this feature

go ahead and close this issue... I've managed to pull in what I need datawise, by using go-bindata and statically writing it into a .go file (yuk I know, but also kinda cool)!

sadly I see the image spin up I see it "calling program.bin main()", but I then see nothing until the container is destroyed - I'm expecting a whole bunch on the output.
on the daemon I see the following:
WARN[4857] retrying... 4                                 error=[common/get_instance_ip.go:21] instance 08:00:27:a8:e0:5f not found in map: map[]
DEBU[4859] getting instance ip
WARN[4859] retrying... 3                                 error=[common/get_instance_ip.go:21] instance 08:00:27:a8:e0:5f not found in map: map[]
DEBU[4861] getting instance ip
WARN[4861] retrying... 2                                 error=[common/get_instance_ip.go:21] instance 08:00:27:a8:e0:5f not found in map: map[]
DEBU[4863] getting instance ip
WARN[4863] retrying... 1                                 error=[common/get_instance_ip.go:21] instance 08:00:27:a8:e0:5f not found in map: map[]
DEBU[4865] getting instance ip
WARN[4865] retrying... 0                                 error=[common/get_instance_ip.go:21] instance 08:00:27:a8:e0:5f not found in map: map[]
ERRO[4865] error encountered, ensuring vm and disks are destroyed  error=[virtualbox/run_instance.go:129] failed to retrieve instance ip: {[common/get_instance_ip.go:21] instance 08:00:27:a8:e0:5f not found in map: map[]}
DEBU[4865] running VBoxManage command                    command=[VBoxManage controlvm myInstance poweroff]
DEBU[4865] running VBoxManage command                    command=[VBoxManage unregistervm myInstance --delete]
ERRO[4870] error handling request                        error=[virtualbox/run_instance.go:129] failed to retrieve instance ip: {[common/get_instance_ip.go:21] instance 08:00:27:a8:e0:5f not found in map: map[]}

A "feature" of unik is that it kills unikernels that are taking too long to boot. We've disabled this on the python-support branch, so you might want to try checking that out and running on that branch to see if your unikernel is taking longer than 30 seconds to boot. Other than that I'm unsure why your unikernel would not quickly enter the bootstrap phase (where it registers with the listener).

did it work on the python branch?

I tried that this afternoon and it failed with an opcode error which is
really odd. I'll grab and attach the log at some point.
On Thursday, 19 May 2016, Scott Weiss<EMAIL_ADDRESS>wrote:

did it work on the python branch?
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/emc-advanced-dev/unik/issues/29#issuecomment-220347862

any update on this?


Not working at all

Extension says connected but nothing happens to my discord presence.
Tried reinstalling and restarting Discord and VS-Code
Any help will be appreciated.

create a new terminal and then go to the output tab. click the dropdown and click RPC. what does it say?

I got nothing however when I ran "Discord Rich Presence: Reconnect Discord Presence to Discord Gateway" i got this

happening to me also, the extension is useless now

The rpc.enable: command not found error happens when you have installed the extension and have not properly restarted vscode. Try reinstalling the extension, then close vscode and kill all its processes. Open vscode and make sure discord is running before you do so.

This doesnt work ^

Im now getting this.

This ID is not my discord id, and it isnt the default id.

No, it's your discord client id (the is separate from your user id)

Im on windows. Not Linux

No more errors however discord still is not showing anything.

OK its working now, for some reason my discord settings were not allowing it to show.


No executable code of the debugger’s target code type is associated with this line.

 Just started today.
Breakpoint warning: No executable code of the debugger’s target code type is associated with this line.
Possible causes include: conditional compilation, compiler optimizations, or the target architecture of this line is not supported by the current debugger code type. - /home/rich/git/sudoku/HiddenSinglesCandidate.cs:187
Breakpoint warning: No executable code of the debugger’s target code type is associated with this line.
Possible causes include: conditional compilation, compiler optimizations, or the target architecture of this line is not supported by the current debugger code type. - /home/rich/git/sudoku/HiddenSinglesCandidate.cs:230

It isn't consistent.
My system:
rich@mazama:~$ uname -a
Linux mazama 6.5.0-17-generic #17-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 11 14:01:59 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
rich@mazama:~$ cat /etc/os-release | head -n 1
PRETTY_NAME="Ubuntu 23.10"
rich@mazama:~$  dotnet --version
8.0.101

Code:
Version: 1.87.0-insider
Commit: 8fa84589eef3538dbc763ff98dc7d5a8a0c56374
Date: 2024-02-09T05:46:41.377Z
Electron: 27.3.1
ElectronBuildId: 26731440
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.5.0-17-generic

DevKit: v1.4.2 (pre-release)

What that message means is that the debugger could find a PDB file that has information for the source file, but the source file didn't have a record for the line of the breakpoint.
Once you hit the problem, does it consistently reproduce if you relaunch without recompiling the project? You can use a launch.json without a preLaunchTask to ensure that there is no build, or just check the build log to see if msbuild decided to run the compiler or not.

That makes sense. This didn't come up again. It was a problem for about 20mins.
I was also running the project from terminal. It's a short-running console app, so DevKit and Terminal were never running the app at the same time. Perhaps they had a symbolic battle?
If it doesn't repro later today, I'll close this.

My understanding is that Dev Kit and terminal should, normally at least, use the same .NET SDK to build the project. So, I don't know of a reason why they would "fight".

The last week or so, DevKit is working much better for me (all pre-rel versions).


Order form breaks if user enters an order, puts in an order expiration and then tries to edit the limit price

See in the screenshot below my max cost is still at $3 and the buy button is deactivated

@matt-bullock  what are the steps to reproduce?
I can put in
quantity 10
price 0.8
set an expiration date of 1 day
then change total order value to 3
I get the correct behavior

tried to reproduce the steps but it looks fixed now. closing


update customization information for shell app

OOD_DEFAULT_SSHHOST and OOD_SSHHOST_ALLOWLIST specified in env and how they work
Also details changes from future PRs https://github.com/OSC/ondemand/pull/601 and https://github.com/OSC/ondemand/pull/570

This is out of date - Jeff's merge actually updated both Set Default SSH Host and Set SSH Allowlist sections appropriately.


Test adding output directory to flutter drive.

Test adding output directory to flutter drive.
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] I followed the breaking change policy and added Data Driven Fixes where supported.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Hey @godofredoc, this is a big change, and will break our customers. In addition, since the relevant test infrastructure is so complicated (one of the meta problems I know we're trying to solve), it is not clear to me why we need to pass these directories via CLI flags rather than using scoped environment variables. Could you write up a one pager doc explaining the high level problem you're trying to solve, and then the relevant technical details for why it would be worth making a breaking change to solve this problem?


qpwgraph: 0.5.2 -> 0.5.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/qpwgraph/versions.
meta.description for qpwgraph is: Qt graph manager for PipeWire, similar to QjackCtl.
meta.homepage for qpwgraph is: https://gitlab.freedesktop.org/rncbc/qpwgraph
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.5.3 with grep in /nix/store/5pz199pfgyhf1gf0w3xmkz6bvqsp2hyg-qpwgraph-0.5.3
found 0.5.3 in filename of file in /nix/store/5pz199pfgyhf1gf0w3xmkz6bvqsp2hyg-qpwgraph-0.5.3

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
qpwgraph

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5pz199pfgyhf1gf0w3xmkz6bvqsp2hyg-qpwgraph-0.5.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A qpwgraph https://github.com/r-ryantm/nixpkgs/archive/38c5c8055741294ce33b3ddeeec204ffa02dff3f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/38c5c8055741294ce33b3ddeeec204ffa02dff3f#qpwgraph

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5pz199pfgyhf1gf0w3xmkz6bvqsp2hyg-qpwgraph-0.5.3
ls -la /nix/store/5pz199pfgyhf1gf0w3xmkz6bvqsp2hyg-qpwgraph-0.5.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

qpwgraph

Maintainer pings
cc @kanashimia @exi @Scrumplex for testing.

https://gitlab.freedesktop.org/rncbc/qpwgraph/-/compare/v0.5.2...v0.5.3


Replace cpp-unicodelib with uni-algo dependency

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 99.419%

Totals

Change from base Build<PHONE_NUMBER>5:
0.09%

Covered Lines:
1027

Relevant Lines:
1033

💛  - Coveralls


Move _Print into separate module

Move and add unittests.

To much TCLI context needed. Better where it currently is.


Linked Data Signatures context

Sorry I didn't bring this up earlier, I didn't realize I needed it: https://w3id.org/identity/v1
Used by https://w3c-dvcg.github.io/ld-signatures/
Apparently I need to include that context in my hash before giving it to rdf-normalize, otherwise the output of normalize is an empty string.

Released in 2.2.2.

Thank you.


ComputerCraft 1.7 not found when launching Minecraft

I just installed the most recent OpenModsLib, OpenPeripheral, and ComputerCraft but only version 1.70 and OpenPeripheral is not finding ComputerCraft. When I launch Minecraft, it says this exactly as I see it:
Forge Mod Loader has found a problem with your minecraft installation
The mods and versions listed below could not be found
ComputerCraft : [1.70,]
The file 'ForgeModLoader-client-0.log' contains more information
So I checked and saw CC 1.7 in my mods folder. Then, disabling OpenPeripheral I looked through mods loaded and ComputerCraft was there with its logo and its pack.info contents there. I can't find the log file because it's my own unlisted FTB modpack(now I forgot my password for it, great) which is stored differently than normal FTB modpacks.

It's not ComputerCraft 1.70, it's 1.7. And 1.6 < 1.7 < 1.64 < 1.71. OP is deliberately requiring non-existing version 1.70 to make sure we aren't loading with 1.6X.


Placeholder for Ruby Tracker doco updates

This is confusing language: ":buffer_size is the number of events which will be queued before they are all sent, a process called "flushing". When using GET, it defaults to 0 because each event has its own request. When using POST, it defaults to 10, and the buffered events are all sent together in a single request."
Is it Snowplow:: or SnowplowTracker:: ?

moved to docs, closing


SpectrumDataset: is a IterableDataset,How to use shuffle in Dataloader?

When i run these codes
import torch
import pandas as pd
import polars as pl
import depthcharge as dc
import natsort
import re
import numpy as np
import pyarrow as pa
from pyarrow import int32
from depthcharge.data import SpectrumDataset
from torch.utils.data import DataLoader
from depthcharge.transformers import SpectrumTransformerEncoder
from depthcharge.encoders import FloatEncoder
from depthcharge.data import CustomField

mzml_file = ["20190118_Q2_MD_ColQ2-51_AlexanderBull_P15_Fluide_4microscans.mgf"]

parse_kwargs = {
    "progress": False,
    "preprocessing_fn": [
        dc.data.preprocessing.set_mz_range(min_mz=0),
        dc.data.preprocessing.filter_intensity(max_num_peaks=200),
        dc.data.preprocessing.scale_intensity(scaling="root"),
        dc.data.preprocessing.scale_to_unit_norm,
    ],
    "custom_fields": [
      # CustomField("Seq", lambda x: x["params"]["seq"], pa.string()),
        CustomField("RT", lambda x: x["params"]["rtinseconds"], pa.float64()),
        CustomField("charge", lambda x: x['params']['charge'], pa.list_(int32())),
    ]
}

dataset = SpectrumDataset(mzml_file, batch_size=8, parse_kwargs=parse_kwargs)

from torch.utils.data import DataLoader

loader = DataLoader(dataset, batch_size=None,sampler=True)

for batch in loader:
    print(batch)

I get a error.
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
Cell In[26], line 38
     33 dataset = SpectrumDataset(mzml_file, batch_size=8, parse_kwargs=parse_kwargs)
     36 from torch.utils.data import DataLoader
---> 38 loader = DataLoader(dataset, batch_size=None,shuffle=True)
     40 for batch in loader:
     41     print(batch)

File ~/miniconda3/envs/ttt/lib/python3.11/site-packages/torch/utils/data/dataloader.py:313, in DataLoader.__init__(self, dataset, batch_size, shuffle, sampler, batch_sampler, num_workers, collate_fn, pin_memory, drop_last, timeout, worker_init_fn, multiprocessing_context, generator, prefetch_factor, persistent_workers, pin_memory_device)
--> 308     raise ValueError(
    309         f"DataLoader with IterableDataset: expected unspecified shuffle option, but got shuffle={shuffle}")
    311 if sampler is not None:
    312     # See NOTE [ Custom Samplers and IterableDataset ]
    313     raise ValueError(
    314         f"DataLoader with IterableDataset: expected unspecified sampler option, but got sampler={sampler}")
    315 elif batch_sampler is not None:
    316     # See NOTE [ Custom Samplers and IterableDataset ]
    317     raise ValueError(
    318         "DataLoader with IterableDataset: expected unspecified "
    319         f"batch_sampler option, but got batch_sampler={batch_sampler}")

ValueError: DataLoader with IterableDataset: expected unspecified sampler option, but got shuffle=True

How to use shuffle in Dataloader?

Hi @cliang-huanglab 👋
Alas, it is a bit tricky to shuffle data from an IterableDataset. However, you can invoke the samples argument as part of the **kwargs to shuffle data as it is a LanceDataset. This shuffles the data using a reservoir sampling approach.
However, we're in the process of updating Lance under the hood, which should make a few things better!


[Feature Request] Sorting ticks in barchart

Hi
I'd like to see in a future version this kind of option: If my x-axis comes from a factor variable (e.g. good quality and bad quality in the x-axis and the observed frequency of each type in the y-axis) then I'd like to:

Sort to x-axis ticks in the same order as in the data
Sort the x-axis ticks alphabetically or according to the y-value so that the chart describes a half U shape

I believe you can already do this, by setting the sorted values as the domain of an ordinal scale.

Thanks !!!
I didn't find that in Google
On Jul 1, 2016 5:09 AM, "Curran Kelleher"<EMAIL_ADDRESS>wrote:

I believe you can already do this, by setting the sorted values as the
domain of an ordinal scale.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alexandersimoes/d3plus/issues/505#issuecomment-229897347,
or mute the thread
https://github.com/notifications/unsubscribe/AJn6OVE6pl5h_GfIThGEcsYT0SOJVpB7ks5qRNkygaJpZM4JC1Ls
.

There was a reply here that now is missing

Curran Kelleher<EMAIL_ADDRESS>6:09 (hace 7 horas)
para alexandersimoe., mí, Author
I believe you can already do this, by setting the sorted values as the domain of an ordinal scale.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

In other words, how do I pass
var x = d3.scale.ordinal()
    .domain(["A","B","C"])
    .rangePoints([0, width]);

to d3plus?

Yes, sorry about that. I mistakenly thought this was an issue on the D3 project itself when I posted that, and when I realized it was an issue in d3plus, I deleted the reply.
In raw D3, the ordinal scale domain will dictate the ordering that appears on the axis.
However, I'm not so familiar with D3Plus actually, and I'm not sure how to expose this functionality within the abstraction that D3Plus provides, so I deleted the comment. I'm not sure how it can be done in D3Plus. Good luck though!

no worries, I still don't figure out a solution
—————
Mauricio Vargas Sepúlveda 帕夏
2016-07-01 15:02 GMT-03:00 Curran Kelleher<EMAIL_ADDRESS>
Yes, sorry about that. I mistakenly thought this was an issue on the D3
project itself when I posted that, and when I realized it was an issue in
d3plus, I deleted the reply.
In raw D3, the ordinal scale domain will dictate the ordering that appears
on the axis.
However, I'm not so familiar with D3Plus actually, and I'm not sure how to
expose this functionality within the abstraction that D3Plus provides, so I
deleted the comment. I'm not sure how it can be done in D3Plus. Good luck
though!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/alexandersimoes/d3plus/issues/505#issuecomment-230011206,
or mute the thread
https://github.com/notifications/unsubscribe/AJn6OUacLwvzA-t5fSyLMIoC7xlmqzVbks5qRVYzgaJpZM4JC1Ls
.

You can manually set a scale's range using:
.x({"range": [0, 1, 2, 3]})

You can override the sorting algorithm by using the .order( ) and either passing a separate key with each data point that corresponds to it's sort order (then saying .order("your-key-name")) or by passing a custom function to the method.


Add support for traits.

Hey. Hey.
Traits aren't supported yet?

Trait is an usefull and powerfull feature, though it's only compatible with 5.4 and latter, it mays be used.
And we cant just merge trait method in the class that use it at the compilation because we wont be able to use the trait from the php code.

I tend to agree with what fezfez said. We might want to stabilize zephir before adding new features. With php parser and abstract syntax tree, we will always be able to merge the code in trait into individual classes.

By only merging traits into classes, you wlil break the API. Traits are not used only inside the library, they are also usable outside a library. Better no implement them rather than merge methods.

How about giving up PHP5.3 support?

Trait are definitively not supported in php 5.3, right ?

I mean Zephir giving up support for PHP 5.3.
There are problems when running Zephir extensions on PHP 5.3, which I can hardly trace.
By giving up support for PHP 5.3, Traits are reasonable feature for Zephir.

In my tool PHP-To-C-Ext, it now allows using trait to build zephir based php extensions. Under the hood it just merge all functions in the trait into individual classes.
https://github.com/jimthunderbird/php-to-c-extension#example-07

Traits are not aimed to be merged into class.
If you want zephir to support this feature , just create another type specific to zephir, and call it mixin for instance.
A php class that uses a trait is NOT compatible with php 5.3 and so should go for zephir.
You should see traits as a part of the public API, not as something used internaly in the library.
Sometimes traits are even not used internaly in the library, they are just utilities available for everyone that use the library.
Believe me or not, but merging traits into classes and throwing them away from the final extension will bring a lot of confusions.

+1

Judging by this infographic http://php.net/supported-versions.php Soon we will lose the support of 5.4. Maybe it's time to use Traits? :)

It would be nice if zephir support trait as a built-in structure, if not, right now I am still going the method merging ways, developers have options not to use trait.
https://github.com/jimthunderbird/php-to-c-extension

Any update on this?

+1

Should be possible now that support for php 5.3 is dropped.

Hope implement traits soon +1

@Green-Cat +1

I figure there are three ways to use traits within Zephir:

As Zephir traits to add functionality for Zephir classes
As PHP traits to add functionality for PHP classes
As a combination of both

I think no.3 is powerful, but confusing. I think no.1 is nice, but I think most useful would be no.2? Best would be both no.1 and no.2, where 1 trait is not both for Zephir and PHP.
Like suggested it would be good to make them distinct: mixin for Zephir (no.1), trait for PHP (no.2). No.3 would be implicit be no.1 and no.2. That is confusing. I think if functionality is shared, a no.2 that implements no.1 for example would be better maintainable.

@aschwin zephir is like a layer on top of C with zend Api. Imo it would be best to make it as transparent as possible so that a class in zephir is a class in php and a trait in zephir a trait in php. If you want to hide stuff from php it would be best to use a technique like optimizers. This technique could probably be extended with more funtionality (on the part of the zephir programmer), but implementing this can be much harder. For example if you want to hide a zephir class from php, because all the classes are registered with the zend api, it would require custom logic so that they can not be used in php.

@flip111 is problably one of the few to understand what a is a trait: a trait is a trait.

+1

+1

+1

+1

I will try to add trait support for PHP only, support for zephir itself will be too hard for me i guess.

But the problem with traits is that internal traits started working just from latest php 7.0.12 for php 7, didn't check php 5 yet.

2018 Calling

More likely we will see php 8 rather than traits

I feel like this language lacks... everything

Because it was mainly done for writing phalcon and its features were driven by phalcon development.

It would be really amazing to have Traits for the Phalcon 4 era.  Not having them is really affecting the design of my extension.

i hope phalcon need trait, so we can use trait on zephir haha


Add the self-study guide to the list

Hey,
I just published the self-study guide to prepare the certification and I was wondering if it could be added to this repository. If you let me know the section that fits best, I can open a PR.
Thanks!

@raulfraile there is a Book Section https://github.com/jmolivas/symfony-certification-guide#books
I think that will be the best place to add.
Feel free to send the PR


vrc-get repo packages description might be wrong in program

https://github.com/anatawa12/vrc-get/blob/e21699a5d6628e4209ba3fc3bfb9c201c7d10791/src/commands.rs#L593-L602

That's incorrect. Can you fix this?

Ah… Does your "doc" mean command description? Or README.md?
If "doc" is command description, the answer is YES.
If not, please tell me the true behavior of RepoPackages.

I mean doc comment, same as command description in --help command.

OK. (maybe it was lack of my knowledge)
I'll do that.


[test-triage] chip_csr_aliasing

Hierarchy of regression failure
Chip Level
Failure Description
Offending '(pwr_ast_i.io_clk_val || (!por_d0_ni))' has 1 failures:

Test chip_csr_aliasing has 1 failures.
1.chip_csr_aliasing.2680549163
Line 303, in log /container/opentitan-public/scratch/os_regression/chip_earlgrey_asic-sim-vcs/1.chip_csr_aliasing/latest/run.log

      Offending '(pwr_ast_i.io_clk_val || (!por_d0_ni))'
  UVM_ERROR @ 43636.757000 us: (pwrmgr_ast_sva_if.sv:67) [ASSERT FAILED] IoClkHandshakeOn_A
  UVM_INFO @ 43636.757000 us: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
  --- UVM Report catcher Summary ---

Steps to Reproduce

GitHub Revision: 81bde034a
dvsim invocation command to reproduce the failure, inclusive of build and run seeds:
./util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i chip_csr_aliasing --build-seed<PHONE_NUMBER> --fixed-seed<PHONE_NUMBER> --waves fsdb

Tests with similar or related failures

[ ] csr_aliasing
[ ] regwen_csr_and_corresponding_lockable_csr
[ ] tl_d_outstanding_access
[ ] tl_d_partial_access

@sriyerg there are some intermittent issues with this but last night's report seemed to show it was ok.

Tests
2022-11-10 08:10:06
2022-11-09 08:04:06
2022-11-08 08:03:42
2022-11-07 08:08:10
2022-11-06 07:11:02
2022-11-05 07:11:23
2022-11-04 07:12:05
2022-11-03 07:11:23
2022-11-02 07:03:26
2022-11-01 07:10:18
Suite

1
chip_csr_aliasing
100
80
100
100
100
100
100
60
80
60
csr_aliasing, regwen_csr_and_corresponding_lockable_csr, tl_d_outstanding_access, tl_d_partial_access

Previous report - https://reports.opentitan.org/hw/top_earlgrey/dv/2022.11.09_17.04.47/report.html highlighted failure as
Offending '(pwr_ast_i.io_clk_val || (!por_d0_ni))' has 1 failures:

Test chip_csr_aliasing has 1 failures.
1.chip_csr_aliasing.2680549163
Line 303, in log /container/opentitan-public/scratch/os_regression/chip_earlgrey_asic-sim-vcs/1.chip_csr_aliasing/latest/run.log

      Offending '(pwr_ast_i.io_clk_val || (!por_d0_ni))'
  UVM_ERROR @ 43636.757000 us: (pwrmgr_ast_sva_if.sv:67) [ASSERT FAILED] IoClkHandshakeOn_A
  UVM_INFO @ 43636.757000 us: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
  --- UVM Report catcher Summary ---

The failure needs to be debugged. The tests run with different randomization seeds each night. Depending on the seed value, they may occasionally hit a corner failure case. Lets keep the bug open.

@ballifatih this seems like the same failure as the one you've encountered in #16154 right?

@tjaychen Yes I think the failure is similar (both coming from pwrmgr_ast_sva_if). However, I think this test started failing earlier than the one in #16154. Unfortunately, I haven't been able to identify the root cause for the other one yet.

I wasn't able to actually reproduce the same failure at 81bde034a, but the error that I got is slightly different:
 "../src/lowrisc_tlul_common_0.1/rtl/tlul_assert.sv", 296: tb.dut.top_earlgrey.u_xbar_main.tlul_assert_host_rv_core_ibex__cored.gen_assert_final[2].noOutstandingReqsAtEndOfSim_A: started at<PHONE_NUMBER>6ps failed at<PHONE_NUMBER>6ps
266   Offending '((pend_req[2].pend == 1'b0) || $test$plusargs("disable_assert_final_checks"))'
267 UVM_ERROR @ 45520.370276 us: (tlul_assert.sv:296) [ASSERT FAILED] noOutstandingReqsAtEndOfSim_A
268 UVM_INFO @ 45520.370276 us: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]

The seed I used was<PHONE_NUMBER>.

I wasn't able to actually reproduce the same failure at 81bde034a, but the error that I got is slightly different:
 "../src/lowrisc_tlul_common_0.1/rtl/tlul_assert.sv", 296: tb.dut.top_earlgrey.u_xbar_main.tlul_assert_host_rv_core_ibex__cored.gen_assert_final[2].noOutstandingReqsAtEndOfSim_A: started at<PHONE_NUMBER>6ps failed at<PHONE_NUMBER>6ps
266   Offending '((pend_req[2].pend == 1'b0) || $test$plusargs("disable_assert_final_checks"))'
267 UVM_ERROR @ 45520.370276 us: (tlul_assert.sv:296) [ASSERT FAILED] noOutstandingReqsAtEndOfSim_A
268 UVM_INFO @ 45520.370276 us: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]

The seed I used was<PHONE_NUMBER>.

Is this the first error in the simulation? If not, we can ignore it and only deal with the first error.
If it's the 1st error, please let me know how to reproduce it.

Yes in run.log, I only see this assertion failure. What I did was following (which is the seed from this issue):

Also, I couldn't find the log of the failed run in the nightly regression (looking at build nr 407 on 9th of Nov.). Are there multiple runs happening in the regression since the test passes %80?

Thanks @ballifatih. Let me have a try.

Thanks @weicaiyang. I also started running another one just to make sure I didn't use wrong params. Last time it took around 2 hours though (current run is at 43 min now).

@weicaiyang I actually got the expected result this time, I must have done something wrong the first time.

Could this be about the test writing EXT_CLOCK_EN of lc_ctrl.TRANSITION_CTRL (which I assume happens randomly)?
The main reason for pwr_ast_i.io_clk_val = clk_src_io_val_o to be pulled down by ast seems like ast received io_clk_byp_req = On from LC (see below). That is the only input change to ast before clk_src_io_val_o goes down. (I removed a bunch of ast input/outputs that are stable in the vicinity of this change.)

Within LC, I can see that a memory write comes to TRANSITION_CTRL by TL-UL (tl_i.a_address offset matches offset of this register). We cannot see in this waveform, but pwr_ast_i.io_clk_val signal goes down around 5 aon_clk cycles after LC propages byp_req.

If overwriting TRANSITION_CTRL is the issue (or rather the violation of IoClkHandshakeOn_A from the mentioned commit), then I think this signal trigger should not violate the updated version of the same SVA since #16454. @matutem
The old SVA from the commit 81bde034a
https://github.com/lowRISC/opentitan/blob/81bde034a7b21e3444342c96555fc63595a03c65/hw/ip/pwrmgr/dv/sva/pwrmgr_ast_sva_if.sv#L67-L69
And the new SVA that is trigger sensitive:
https://github.com/lowRISC/opentitan/blob/08827b56858186f9a6c43ed29ace95188e2d7984/hw/ip/pwrmgr/dv/sva/pwrmgr_ast_sva_if.sv#L69-L71
And here is the original violation waveform:

Again, IF this was the cause.

Thanks @ballifatih for looking into this.
Seems like @matutem already fixed this. Let me run a test with 100 seeds. If no more failure, let's close this.

Forgot to update this issue. I ran 100 seeds, and this error no longer occurred.
But I saw some other failures. Will look into it. If needed, will file another issue.


crictl/kubernetes fails to pull images from insecure-registry.

I added a comment to https://github.com/containerd/containerd/issues/2758 but no one answered.
Description
I've set inscecure registry in /etc/containerd/config.toml like below:
Output of cat /etc/containerd/config.toml:
root = "/var/lib/containerd"
state = "/run/containerd"
oom_score = 0

[grpc]
  address = "/run/containerd/containerd.sock"
  uid = 0
  gid = 0
  max_recv_message_size = 16777216
  max_send_message_size = 16777216

[debug]
  address = "/run/containerd/debug.sock"
  uid = 0
  gid = 0
  level = "debug"
[metrics]
  address = ""
  grpc_histogram = false
[cgroup]
  path = ""
[plugins]
  [plugins.cgroups]
    no_prometheus = false
  [plugins.cri]
    stream_server_address = "<IP_ADDRESS>"
    stream_server_port = "0"
    enable_selinux = false
    sandbox_image = "k8s.gcr.io/pause:3.1"
    stats_collect_period = 10
    systemd_cgroup = false
    enable_tls_streaming = false
    max_container_log_line_size = 16384
    [plugins.cri.containerd]
      snapshotter = "overlayfs"
      no_pivot = false
      [plugins.cri.containerd.default_runtime]
        runtime_type = "io.containerd.runtime.v1.linux"
        runtime_engine = "/usr/local/bin/runc"
        runtime_root = "/var/lib/containerd"
      [plugins.cri.containerd.untrusted_workload_runtime]
        runtime_type = ""
        runtime_engine = ""
        runtime_root = ""
    [plugins.cri.cni]
      bin_dir = "/opt/cni/bin"
      conf_dir = "/etc/cni/net.d"
      conf_template = ""
    [plugins.cri.registry]
      [plugins.cri.registry.mirrors]
        [plugins.cri.registry.mirrors."registry.bc.**.**"]
          endpoint = ["http://registry.bc.**.**"]
        [plugins.cri.registry.mirrors."docker.io"]
          endpoint = ["https://registry-1.docker.io"]
    [plugins.cri.x509_key_pair_streaming]
      tls_cert_file = ""
      tls_key_file = ""
  [plugins.diff-service]
    default = ["walking"]
  [plugins.linux]
    shim = "/usr/local/bin/containerd-shim"
    runtime = "/usr/local/bin/runc"
    runtime_root = "/var/lib/containerd"
    no_shim = false
    shim_debug = true
  [plugins.opt]
    path = "/opt/containerd"
  [plugins.restart]
    interval = "10s"
  [plugins.scheduler]
    pause_threshold = 0.02
    deletion_threshold = 0
    mutation_threshold = 100
    schedule_delay = "0s"
    startup_delay = "100ms"

Output of crictl info:
{
  "status": {
    "conditions": [
      {
        "type": "RuntimeReady",
        "status": true,
        "reason": "",
        "message": ""
      },
      {
        "type": "NetworkReady",
        "status": true,
        "reason": "",
        "message": ""
      }
    ]
  },
  "config": {
    "containerd": {
      "snapshotter": "overlayfs",
      "defaultRuntime": {
        "runtimeType": "io.containerd.runtime.v1.linux",
        "runtimeEngine": "/usr/local/bin/runc",
        "runtimeRoot": "/var/lib/containerd",
        "options": null
      },
      "untrustedWorkloadRuntime": {
        "runtimeType": "",
        "runtimeEngine": "",
        "runtimeRoot": "",
        "options": null
      },
      "runtimes": null,
      "noPivot": false
    },
    "cni": {
      "binDir": "/opt/cni/bin",
      "confDir": "/etc/cni/net.d",
      "confTemplate": ""
    },
    "registry": {
      "mirrors": {
        "docker.io": {
          "endpoint": [
            "https://registry-1.docker.io"
          ]
        },
        "registry.bc.**.**": {
          "endpoint": [
            "http://registry.bc.**.**"
          ]
        }
      },
      "auths": null
    },
    "streamServerAddress": "<IP_ADDRESS>",
    "streamServerPort": "0",
    "enableSelinux": false,
    "sandboxImage": "k8s.gcr.io/pause:3.1",
    "statsCollectPeriod": 10,
    "systemdCgroup": false,
    "enableTLSStreaming": false,
    "x509KeyPairStreaming": {
      "tlsCertFile": "",
      "tlsKeyFile": ""
    },
    "maxContainerLogSize": 16384,
    "containerdRootDir": "/var/lib/containerd",
    "containerdEndpoint": "/run/containerd/containerd.sock",
    "rootDir": "/var/lib/containerd/io.containerd.grpc.v1.cri",
    "stateDir": "/run/containerd/io.containerd.grpc.v1.cri"
  },
  "golang": "go1.10.7"
}

Steps to reproduce the issue:

insecure-registry
restart containerd
pull image via crictl

Describe the results you received:
Output of crictl -D pull registry.bc.**.**/master/ui-incident:latest:
DEBU[0000] PullImageRequest: &PullImageRequest{Image:&ImageSpec{Image:registry.bc.**.**/master/ui-incident:latest,},Auth:nil,SandboxConfig:nil,}
DEBU[0000] PullImageResponse: nil
FATA[0000] pulling image failed: rpc error: code = Unknown desc = failed to resolve image "registry.bc.**.**/master/ui-incident:latest": no available registry endpoint: failed to do request: Head https://registry.bc.**.**/v2/master/ui-incident/manifests/latest: dial tcp <IP_ADDRESS>:443: connect: no route to host

Describe the results you expected:
crictl can pull images from insecure-registry.
Output of containerd --version:
containerd github.com/containerd/containerd v1.2.2<PHONE_NUMBER>f7fe2f4e74d43e2fc7ccd237edcbce
and
containerd github.com/containerd/containerd v1.2.3 7f5f1176dd9fb3cc8d3ce5de91759ed3dc969fa2
Output of crictl --version:
crictl version v1.13.0

"Head https://registry.bc../v2/master/ui-incident/manifests/latest: dial tcp <IP_ADDRESS>:443: connect: no route to host"
This is the issue. Is <IP_ADDRESS>:443 the correct server? Why your node can't reach it?

Hi, yes, all nodes reach it.
crictl info
        "registry.bc.**.**": {
          "endpoint": [
            "http://registry.bc.**.**"
          ]
        }

curl -I registry.bc..****
HTTP/1.1 400 Not a Docker request
Server: nginx/1.14.1
Date: Fri, 08 Feb 2019 18:08:54 GMT
Content-Type: text/html;charset=iso-8859-1
Content-Length: 338
Connection: keep-alive
Cache-Control: must-revalidate,no-cache,no-store

I tried with containerd 1.2.2.
My containerd config:
...
[plugins.cri.registry.mirrors."test.io"]
  endpoint = ["http://test.io"]
...

The containerd log for crictl pull test.io/busybox:
DEBU[2019-02-25T17:18:09.396085697-08:00] resolving
DEBU[2019-02-25T17:18:09.396134148-08:00] do request                                    request.headers=map[Accept:[application/vnd.docker.distribution.manifest.v2+json, application/vnd.docker.distribution.manifest.list.v2+json, application/vnd.oci.image.manifest.v1+json, application/vnd.oci.image.index.v1+json, *]] request.method=HEAD url="http://test.io/v2/busybox/manifests/latest"
DEBU[2019-02-25T17:18:09.549029268-08:00] fetch response received                       response.headers=map[Connection:[keep-alive] Vary:[Accept-Encoding] Wpe-Backend:[apache] Content-Type:[text/html; charset=UTF-8] Expires:[Wed, 11 Jan 1984 05:00:00 GMT] X-Cacheable:[non200] X-Cache:[HIT: 3] Cf-Ray:[4aee937d0d9a22ca-LAX] Set-Cookie:[__cfduid=d35a435c2a71e78d3bfedee37c507582b1551143889; expires=Wed, 26-Feb-20 01:18:09 GMT; path=/; domain=.test.io; HttpOnly] Link:[<https://test.io/wp-json/>; rel="https://api.w.org/"] Cache-Control:[max-age=600, must-revalidate] Server:[cloudflare] Date:[Tue, 26 Feb 2019 01:18:09 GMT] X-Pass-Why:[] X-Cache-Group:[normal]] status="404 Not Found" url="http://test.io/v2/busybox/manifests/latest"
DEBU[2019-02-25T17:18:09.549203643-08:00] resolving
DEBU[2019-02-25T17:18:09.549260849-08:00] do request                                    request.headers=map[Accept:[application/vnd.docker.distribution.manifest.v2+json, application/vnd.docker.distribution.manifest.list.v2+json, application/vnd.oci.image.manifest.v1+json, application/vnd.oci.image.index.v1+json, *]] request.method=HEAD url="https://test.io/v2/busybox/manifests/latest"
DEBU[2019-02-25T17:18:10.587115970-08:00] fetch response received                       response.headers=map[Wpe-Backend:[apache] X-Cache-Group:[normal] Content-Type:[text/html; charset=UTF-8] Vary:[Accept-Encoding] Link:[<https://test.io/wp-json/>; rel="https://api.w.org/"] X-Pass-Why:[] X-Cacheable:[non200] Expect-Ct:[max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"] Server:[cloudflare] Set-Cookie:[__cfduid=dff703a774f1a4a9ffef9d604e3793c971551143889; expires=Wed, 26-Feb-20 01:18:09 GMT; path=/; domain=.test.io; HttpOnly] Expires:[Wed, 11 Jan 1984 05:00:00 GMT] X-Cache:[MISS] Cf-Ray:[4aee937eadee9318-SJC] Date:[Tue, 26 Feb 2019 01:18:10 GMT] Cache-Control:[max-age=600, must-revalidate]] status="404 Not Found" url="https://test.io/v2/busybox/manifests/latest"
ERRO[2019-02-25T17:18:10.587265765-08:00] PullImage "test.io/busybox" failed            error="failed to resolve image "test.io/busybox:latest": no available registry endpoint: test.io/busybox:latest not found"

From the log we can tell that containerd does try pulling from http://test.io/v2/busybox/manifests/latest first. Because the image doesn't exist, it tries the default endpoint https://test.io/v2/busybox/manifests/latest with best effort here.
Can you run containerd with --log-level debug to see whether your containerd has tried http://registry.bc.**.**/v2/master/ui-incident/manifests/latest?

reslove?

This should be resolved.  If it is not, please let us know so we can re-open the issue.

same issue with containerd 1.5.2 and insecure registry.
podman and docker can pull without issues from it (after creating proper config).
k8s+containerd and crictl+containerd throw:
FATA[0000] pulling image failed: rpc error: code = Unknown desc = failed to pull and unpack image "registry.xxx.xxx:5000/image": failed to resolve reference "registry.xxx.xxx:5000/verify:v1": failed to do request: Head http://registry.xxx.xxx:5000/v2/verify/manifests/v1: net/http: HTTP/1.x transport connection broken: malformed HTTP response "\x15\x03\x01\x00\x02\x02"

command:
crictl pull registry.xxx.xxx:5000/image-v1

but it seems to work if I run the registry without any certificates, like this:

Why does it fail when we add a certificate to the registry container ?
podman run -d \
  -p 5000:5000 \
  --restart=always \
  --name kind-registry \
  -v $(pwd)/auth:/auth \
  -v $(pwd)/certs/localhost:/certs \
  -e REGISTRY_AUTH=htpasswd \
  -e REGISTRY_AUTH_HTPASSWD_REALM="Registry Realm" \
  -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \
  -e REGISTRY_HTTP_TLS_CERTIFICATE=/certs/localhost.crt \
  -e REGISTRY_HTTP_TLS_KEY=/certs/localhost.key \
  registry:2

Log of the registry reports such an error
2021/09/28 08:22:05 http: TLS handshake error from <IP_ADDRESS>:52546: tls: first record does not look like a TLS handshake

crictl pull generates the same error as mentioned within your comment
root@kind-control-plane:/# crictl pull localhost:5000/hello-app
FATA[0000] pulling image: rpc error: code = Unknown desc = failed to pull and unpack image "localhost:5000/hello-app:latest": failed to resolve reference "localhost:5000/hello-app:latest": failed to do request: Head "http://kind-registry:5000/v2/hello-app/manifests/latest?ns=localhost%3A5000": net/http: HTTP/1.x transport connection broken: malformed HTTP response "\x15\x03\x01\x00\x02\x02"

We can of course do a curl
curl -vk -u admin:snowdrop https://kind-registry:5000/v2/hello-app/manifests/latest?ns=localhost%3A5000
*   Trying fc00:f853:ccd:e793::3:5000...
* Connected to kind-registry (fc00:f853:ccd:e793::3) port 5000 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=BE; ST=Namur; L=Florennes; O=Red Hat; OU=Snowdrop; CN=localhost
*  start date: Sep 28 07:01:23 2021 GMT
*  expire date: Sep 28 07:01:23 2022 GMT
*  issuer: C=BE; ST=Namur; L=Florennes; O=Red Hat; OU=Snowdrop; CN=localhost
*  SSL certificate verify result: self signed certificate (18), continuing anyway.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Server auth using Basic with user 'admin'
* Using Stream ID: 1 (easy handle 0x55f8e6e0b890)
> GET /v2/hello-app/manifests/latest?ns=localhost%3A5000 HTTP/2
> Host: kind-registry:5000
> authorization: Basic YWRtaW46c25vd2Ryb3A=
> user-agent: curl/7.74.0
> accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS == 250)!
< HTTP/2 404
< content-type: application/json; charset=utf-8
< docker-distribution-api-version: registry/2.0
< x-content-type-options: nosniff
< content-length: 96
< date: Tue, 28 Sep 2021 07:27:25 GMT
<
{"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"latest"}}]}
* Connection #0 to host kind-registry left intact


How OSRM Process Restrictions

RT

Summary on current status:

For OSM data, OSRM could handle following two cases

from_way, via_node, to_way
from_way, via_way, to_way

For professional data, we have following cases didn't be supported by OSRM

from_way, via_way, via_way, ..., to_way

Which means complex restriction is not handled by OSRM.  Here is one case

No-Left-turn, from red-edge via several blue edge to green edge.  OSRM generate following error information:
205904 205894 [debug] Restriction references unconnected way: xxxxx

After adjust OSRM code in my local, I could handle complex restriction.  Need more case to verify.

You'll include  #91 Complex Restriction in this research, right?
Will you consider on #90 Time/Conditional Restriction or not? It's just a question.


feat: adding fcc news author practice project API

This PR adds the code for the fcc news API I created for the fcc new fetch project as part of the curriculum here
https://github.com/freeCodeCamp/CurriculumExpansion/pull/331
Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

closing this PR and adding the authors object to the cdn repo.


Broken Search values

Here you can append searches that resulted in some unexpected behavior.

https://www.etracking.io/number/6b88cc25f076fd52943129a45e453d2e3eca5394 will be searched and not treated as a url


Transform user rewrites to avoid rewrite stacking

Currently, Netlify rewrites that point at a Next page fail, because rewrites can't be "stacked". To handle this we should parse user rewrites onPreBuild, find the ones that eventually point at functions, and change them to point at the functions directly, with the full path appended to the function.
e.g. change this:
[[redirects]]
from = "/oldblog/*"
to  = "/newblog/:splat"
status = 200

to this:
[[redirects]]
from = "/oldblog/*"
to  = "/.netlify/functions/___netlify-handler/newblog/:splat"
status = 200

And then in the handler, read the target path and pass it to next/server. This depends on updates to proxy to pass the target URL through to the function in the event.

Probably makes sense to wait for Edge Router https://github.com/netlify/pod-ecosystem-frameworks/issues/62 before tackling this

Closing this as it works in the v5 runtime.


set env for ekuiper source yaml,  can not get the expect result by manager ui

Environment:  docker

eKuiper version (e.g. 1.3.0): 1.4.2
Hardware configuration (e.g. lscpu):
OS (e.g. cat /etc/os-release): linux
Others:

What happened and what you expected to happen:
set env for ekuiper source yaml,  can not get the expect result by manager ui, should be able to get the expect result by manager ui
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:

Same to me.
I set env MQTT_SOURCE__DEFAULT__SERVER=tcp://admin:pass@my.mqtt.server:22334
But when I go to the ekuiper-manager web page. I see the tcp://<IP_ADDRESS>:1883 in the mqtt default setting.
It should be what I set in the environment variable list.

Already resolved, so close


Programming language name conflict

It looks like "The Nova Programming Language" is used by a pre-existing project[1] that has been in development since at least 2003 (date of the 0.1.0 public release). I don't know how I missed this when choosing a name, but to be nice we should consider changing our project name from Nova to something else.
[1]: http://www.navgen.com/nova/index.html

Potential Name List

Beau
Blast
Cinder
Elysium
Ent
Fen
Princess
Rhin
Sunder
Vile

The language name was changed from Nova to Sunder in fa9324c08c2ec7fb1e69d42fd318daa0ba76b9d8.


[Question]: How to find highlight group after _get_hl_from_capture was removed?

Does this repo require the upstream builtin treesitter support to finish their implementation before highlight groups can be correctly displayed like they were before?
I see a similar issue was opened #89 that only showed that there was an error that occurred due to what I am asking about here.
For example, before this was removed from this repository, this is what was shown:
I can go into my configuration and specify that I want to change luaTSFunction and the color of the item that I am currently hovering above will change to that color.
# Treesitter
* @variable -> luaTSVariable -> TSVariable
* @field -> luaTSField -> TSField
* @function -> luaTSFunction -> TSFunction

# Syntax
* luaFunc -> Identifier
* luaFuncSig -> luaFuncSig
* luaFuncId -> Function
* luaFuncName -> Function

After this function was removed, this is what is shown:
The highlight groups are still the same name as above, but now luafunction provides no meaning to me as someone who wants to create or alter a theme.
# Treesitter
* @variable -> luavariable -> variable
* @field -> luafield -> field
* @function -> luafunction -> function
# Syntax
* luaFunc -> luaFunc
* luaFuncSig -> luaFuncSig
* luaFuncId -> Function
* luaFuncName -> Function

Also, this might not be the exact place to ask this question, but are filetype specific highlight groups being erased? That is, luaTSField vs TSField. (I hope that they aren't.)

Neovim now supports mapping captures directly (so you can do hi link @variable Identifier -- or, indeed, hi link @variable.lua Function). This makes the highlight group functionality no longer needed (for its intended purpose: knowing what to hi link).
There may be new convenience functions (either in Neovim or this plugin) at a later point if these are deemed useful enough(!).

What was displayed was just plainly wrong. The copy of the internal implementation of Neovim was just not update. We should probably try to get the extmarks from the tree-sitter namespace or just try to get an API for extmark based highlights.

Thank you, I understand it now.
I'll also go ahead and ask this while I am here because it seems silly to create an issue upstream to ask but, what's the best way to check if the user has this functionality? I tried vim.fn.has('patch-8.2.0674') but it shows 0 on my end. I'd like to check whether the user's version allows for this because otherwise the error W18: Invalid character in group name is shown. I chose this patch because it was the next one I saw after the commit 030b422d1.

The old TS* mapping will still exist for now. You could use the same check as we do in highlight.lua in this repo (does hl_map exist)

I'll also go ahead and ask this while I am here because it seems silly to create an issue upstream to ask but, what's the best way to check if the user has this functionality?

You don't -- Neovim doesn't do patch/commit levels. You need to check for a specific version (has('nvim-0.8)` in this case), where nightly/master reports as the next (unreleased) version.
You cannot and should not support users running anything but the very latest master (or a recent release) -- if they report an error, tell them to git pull and rebuild.


I cannot find the program

Hello, I have downloaded ACSE and cannot find the program in the files.

Please download from the Releases tab. What you downloaded was the source code.


POST_URL environment variable

ReferenceError: Missing required environment variable(s): POST_URL!
Is this variable still being used ? If so, what should be the value ?

It is not needed any more.


Feat: host availability event

Send a event type Realtime.REALTIME_NO_HOST_AVAILABLE when have no one host candidate inside a meeting.
if another host joins within the 1min time frame, the event Realtime.REALTIME_HOST_AVAILABLE has fired when user know about the host availability inside the room

:tada: This PR is included in version 4.12.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Unfortunate: the the un4chan userscript toolkit

i.e., the non-ui parts of c4, so others can userscript without being tied to either 4chan's UI choices or c4's UI choices (as much as possible, anyway). unf for short.
I aiming for this library to be usable with polymer, so one could make a Material Design(tm) userscript on top. So far so good, though polymer itself might take some convincing to work within greasemonkey though (haven't tried it yet).
Still TODO is extracting the fancy new SharedWorker-based updater into something usable. I basically want to have an API like:
unf.data.subscribe board, tno, (thread) ->
  ui.rerender-with-new-data thread

which should plug in to most MVWhatever libraries (polymer, react, mithril, etc) nicely. Then, just wrap this up in a separate buildscript/repository, add npm + publishing for greasemonkey @require, and it's ready for use, albeit probably buggy (like c4).
There are some other parts of c4 that might be worth extracting as well, such as the relative dates, lightbox/tooltips, the youtube api queue, and the posting logic. Once that's extracted, c4 is a pretty tiny codebase: some html templates, styles, and a bundle of hideous dom-mangling.
@saxamaphone69 , 4u.

Just noticed the PR title has "the" twice in it.

:+1:

i thought something was actually happening x(


Missing the code of scale-aware and task-aware block?

Thank you for sharing the code! I'm seeking for details about scale-aware, spatial-aware and task-aware blocks in the source code. However, as i can see in the source code "dyhead/dyhead.py", there only exists the implementation of spatial-aware block.
Is this a mistake or my misunderstanding?

i also find the scale-aware,can you tell me where is it? thank you.

@kriskrisliu In dyhead.py from line 79-82, you can observe all three attentions being used. I think the difference is that they are first applying spatial attention using deformable convolutions and then level attention using hard sigmoid followed by task attention through DyReLU. But it is confusing to understand because they are doing this for each level in the pyramid (in for loop).

I can not find it too！

尺度的实现能找到，空间的实现 就是用了可变形卷积得到offset，但是 任务级别的实现没找到代码啊！


Update cats-effect to 3.2.4

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

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

labels: library-update, semver-patch

Codecov Report

Merging #173 (55bf17e) into main (7fb2378) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #173   +/-   ##
=======================================
  Coverage   89.49%   89.49%
=======================================
  Files          88       88
  Lines        2561     2561
  Branches       72       72
=======================================
  Hits         2292     2292
  Misses        269      269

Continue to review full report at Codecov.

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


Session 704 is replicated in session 705

Session 705 has the transcript for Session 704

Came here to file this issue, but looks like someone already filed it. I've verified that 705 does actually have subtitles.


DRAFT: try to remove code duplication for different datatypes using macro

Didn't want to open macro pandora box but this makes code much shorter. IDE support in vscode still works.
If we like the approach, I can add missing datatypes

It does make the code shorter, but actually, I find the tdigest_cast version more elegant. We have to cast anyways, so we can also do that beforehand. There's no performance impact from that. What do you think?

It does make the code shorter, but actually, I find the tdigest_cast version more elegant. We have to cast anyways, so we can also do that beforehand. There's no performance impact from that. What do you think?

Agree, tdigest_cast should be better. Didn't notice this function and it was not used

ok, then we should make that one the default and actually remove the other one. But for that we also have to bring in the changes that you already did for the current function. Will you take this over or shall I do it sometime?

See https://github.com/appian/polars-tdigest/pull/13


moon -v test oddity

Note below that the output of moon -v test first shows that a test passes:
...::new_transition invalid commands ok
and then later reports that the same test fails:
...::new_transition invalid commands failed: FAILED: ...
This seems rather odd and confusing.
$ moon version
moon 0.1.20240709 (6f94653 2024-07-09)

$ moon -v test
test .../sunburst-chart/parse-data.mbt::chars_to_string ok
test .../sunburst-chart/string.mbt::split_string ok
test .../sunburst-chart/string.mbt::compare_topic_values ok
test .../tests/plugin-functions_test.mbt::new_transition invalid commands ok
test .../tests/plugin-functions_test.mbt::new_transition valid commands ok
test .../tests/plugin-functions_test.mbt::new_transition invalid commands failed: FAILED: /Users/.../tests/plugin-functions_test.mbt:10:14-10:55 `"new_transition(some-unknown-long-command-name:yo) passed when it should have failed" == "unknown transition command"`
test .../tests/plugin-functions_test.mbt::new_transition valid commands failed: unknown transition command
Total tests: 7, passed: 5, failed: 2.

Here is the code for these tests:
test "new_transition invalid commands" {
  let expected_fails = ["", ":", "some-unknown-long-command-name:yo"]
  each_exn(
    expected_fails,
    fn(cmd) {
      try {
        @sunburst.new_transition(cmd)!
        raise "new_transition(\(cmd)) passed when it should have failed"
      } catch {
        e => @test.eq(e, "unknown transition command")!
      }
    },
  )!
}

test "new_transition valid commands" {
  let expected_success = [
    "ChangeTopicList:Age,Mortality,Medication", "FocusTo:", "FocusTo:51-60,True,Kinase Inhibitor",
  ]
  each_exn(expected_success, fn(cmd) { @sunburst.new_transition(cmd)! })!
}

fn each_exn[T, Err](arr : Array[T], func : (T) -> Unit!Err) -> Unit!Err {
  for i = 0; i < arr.length(); i = i + 1 {
    func(arr[i])!
  }
}

moon test had been refactored recently, could you help verify again with the lastest moon?

Unfortunately, there appears to have been a regression in moon test with today's latest compiler.
It is not showing any error messages for failures.  See screenshot:

Update: if I run rm -rf target, then the problem goes away.
I think I might have a clue on the failure mechanism now... Here are the steps:

Start with a repo with no errors on a previous version of the compiler
Get the latest compiler using: curl -fsSL https://cli.moonbitlang.com/install/unix.sh | bash
Run: moon update && moon install
Run: moon test
RESULT: no output except that the number of failed results is now non-zero
Run: rm -rf target
Run: moon test
RESULT: now all the failures are shown

NOTE that in all of the above, there were ZERO changes to the code itself.
So I'm thinking that whatever mechanism is cacheing test results also needs to cache the VERSION of the compiler that generated those results so that if the compiler changes, all cached test results are discarded and it starts over with a clean slate.
Maybe you could create a CI/CD pipeline that tests this scenario by using an old compiler to test old code that used to pass all tests, but then your pipeline updates the compiler to the latest and you run tests again and ensure that it generates some output?

As for the original reported problem, I haven't seen that in a long time, and that seems to be fixed.
Thank you!


12.1.0

12.1.0 - 05 August 2016
Backwards compatible changes

#612 - Upgrade request dependency, fixes #608 by @bengourley
Added managedconfigurationsfordevice.delete to androidenterprise v1 API
Added managedconfigurationsfordevice.get to androidenterprise v1 API
Added managedconfigurationsfordevice.list to androidenterprise v1 API
Added managedconfigurationsfordevice.patch to androidenterprise v1 API
Added managedconfigurationsfordevice.update to androidenterprise v1 API
Added managedconfigurationsforuser.delete to androidenterprise v1 API
Added managedconfigurationsforuser.get to androidenterprise v1 API
Added managedconfigurationsforuser.list to androidenterprise v1 API
Added managedconfigurationsforuser.patch to androidenterprise v1 API
Added managedconfigurationsforuser.update to androidenterprise v1 API
Added appengine v1 API
Added clientSslPolicies.testIamPermissions to compute alpha API
Added instanceGroupManagers.patch to compute alpha API
Added instanceGroupManagers.update to compute alpha API
Added projects.disableXpnHost to compute alpha API
Added projects.disableXpnResource to compute alpha API
Added projects.enableXpnHost to compute alpha API
Added projects.enableXpnResource to compute alpha API
Added projects.getXpnHost to compute alpha API
Added projects.getXpnResources to compute alpha API
Added projects.listXpnHosts to compute alpha API
Added regionDiskTypes.get to compute alpha API
Added regionDiskTypes.list to compute alpha API
Added regionDisks.createSnapshot to compute alpha API
Added regionDisks.deletes to compute alpha API
Added regionDisks.get to compute alpha API
Added regionDisks.insert to compute alpha API
Added regionDisks.list to compute alpha API
Added regionDisks.setLabels to compute alpha API
Added regionDisks.testIamPermissions to compute alpha API
Added regionAutoscalers.delete to compute beta API
Added regionAutoscalers.get to compute beta API
Added regionAutoscalers.insert to compute beta API
Added regionAutoscalers.list to compute beta API
Added regionAutoscalers.patch to compute beta API
Added regionAutoscalers.testIamPermissions to compute beta API
Added regionAutoscalers.update to compute beta API
Added regionInstanceGroupManagers.abandonInstances to compute beta API
Added regionInstanceGroupManagers.delete to compute beta API
Added regionInstanceGroupManagers.deleteInstances to compute beta API
Added regionInstanceGroupManagers.get to compute beta API
Added regionInstanceGroupManagers.insert to compute beta API
Added regionInstanceGroupManagers.list to compute beta API
Added regionInstanceGroupManagers.listManagedInstances to compute beta API
Added regionInstanceGroupManagers.recreateInstances to compute beta API
Added regionInstanceGroupManagers.resize to compute beta API
Added regionInstanceGroupManagers.setAutoHealingPolicies to compute beta API
Added regionInstanceGroupManagers.setInstanceTemplate to compute beta API
Added regionInstanceGroupManagers.setTargetPools to compute beta API
Added regionInstanceGroupManagers.testIamPermissions to compute beta API
Added regionInstanceGroups.get to compute beta API
Added regionInstanceGroups.list to compute beta API
Added regionInstanceGroups.listInstances to compute beta API
Added regionInstanceGroups.setNamedPorts to compute beta API
Added regionInstanceGroups.testIamPermissions to compute beta API
Added projects.jobs.debug.getConfig to dataflow v1b3 API
Added projects.jobs.debug.sendCapture to dataflow v1b3 API
Added projects.templates.create to dataflow v1b3 API
Added dfareporting v2.6 API
Added servicecontrol v1 API
Added servicemanagement v1 API
Added servicemanagement v1 API
Added spreadsheets.values.append to sheets v4 API

Current coverage is 88.56% (diff: 100%)

Merging #613 into master will not change coverage

@@             master       #613   diff @@
==========================================
  Files             8          8
  Lines           271        271
  Methods          41         41
  Messages          0          0
  Branches         59         59
==========================================
  Hits            240        240
  Misses           31         31
  Partials          0          0

Powered by Codecov.


If someone else has access to your Wallet

Hey @jorge-campo, sending this for your review!
This article breaks the rule of no links in procedures when talking about switching between accounts. Otherwise, I'd have to either to list the same steps as Chen does in her article several times, or risk confusing the user by leaving this step out of the procedure - you'll skip admonitions when you're in rush.

Thanks @jorge-campo, I revised the article using your suggestions - all of them 🙂


[BUG] OSB hangs when runs carried out with large number of clients and target-throughput enabled

Describe the bug
For tests where the target throughput is > 4000 ops/s and search_clients > 4000, OSB stalls and does not report results. This only happens if target throughput is set.  Based on the OSB logs, some workers never meet at the joinpoint and this is preventing OSB from reporting results.
On the target cluster, the run appears to have completed in the expected time and the target throughput is achieved.
The cause is not clear but it seems to be related to the target-throughput pathway and also in how Thespianpy workers are missing (the suspicion is that they exit prematurely and cause OSB to stall.)
This may be related to the issue reported in #318.

@IanHoang @gkamat Are you planning to resolve this in the current sprint? Thanks

@IanHoang @gkamat Are you planning to resolve this in the current sprint? Thanks

Most likely not. We'll be focusing on other areas that might relate to this though.


Error message change with release v2.1.6

Noticed that with the latest version v2.1.6 the error message format has been changed (https://github.com/pelotom/runtypes/pull/61/files#diff-92c6b06e4d1db78667de9db352d5cc7bL30) and doesn't contain key in the error message. It would be still really useful to have the key name also in error message.

Closing as it's stale. key in result objects is superseded by details property in v6.


fs: Make fs API callback runt-time check optional

The commit changes run-time checks of file system driver's callbacks
pointers, against null, optional by replacing if with CHECKIF macro,
which means that they can be removed from compilation with Kconfig option
CONFIG_NO_RUNTIME_CHECKS.
Additionally the commit allows the same checks to fail hard, with
assertion, when CONFIG_ASSERT_ON_ERRORS option is selected.
Signed-off-by: Dominik Ermel<EMAIL_ADDRESS>The review has been spun off from the https://github.com/zephyrproject-rtos/zephyr/pull/29396.

@de-nordic please rebase


GUACAMOLE-131: Migrate to Webjars for JavaScript library dependencies.

This change migrates to Webjars (http://www.webjars.org/) for the JavaScript library dependencies, and upgrades messageformat.js to 1.0.2, which is now MIT-licensed. Serving the static files provided by each Webjar requires using the WebjarServlet, in our case mapped by Guice. Lacking this, the static files are unreachable.
I needed to exclude two dependencies:

angular, which was being pulled in at version 1.3.0-beta9 due to angular-module-shim.
messageformat, which was being pulled in at version 0.1.7 due to angular-translate-interpolation-messageformat.

What do you mean by exclude dependencies? I see the dependencies declared in the POM.

There are <exclusions>...</exclusions> sections for two of the declared dependencies, preventing older versions of transitive dependencies from overriding the explicitly-declared versions we want.

Ah yes, there it is. I totally missed that. 😞


Query by first and last name

Add query partameters for first and last name

MosaicGateway and usecase tests completed. E2E tests pending


Compile and report errors

In file included from ./cpp-ethereum/libethereum/CommonNet.h:28:0,
from ./cpp-ethereum/libethereum/ClientBase.h:30,
from ./cpp-ethereum/libethereum/Client.h:27,
from ./cpp-ethereum/libethashseal/Ethash.h:25,
from ./validation.h:44,
from checkpoints.cpp:10:
./cpp-ethereum/libp2p/Common.h: In member function ‘dev::p2p::Node::operator bool() const’:
./cpp-ethereum/libp2p/Common.h:259:52: error: cannot convert ‘const NodeID {aka const dev::FixedHash<64u>}’ to ‘bool’ in initialization
explicit operator bool() const { return bool{id}; }
^
In file included from ./cpp-ethereum/libethereum/CommonNet.h:28:0,
from ./cpp-ethereum/libethereum/ClientBase.h:30,
from ./cpp-ethereum/libethereum/Client.h:27,
from ./cpp-ethereum/libethashseal/Ethash.h:25,
from ./validation.h:44,
from blockencodings.cpp:14:
./cpp-ethereum/libp2p/Common.h: In member function ‘dev::p2p::Node::operator bool() const’:
./cpp-ethereum/libp2p/Common.h:259:52: error: cannot convert ‘const NodeID {aka const dev::FixedHash<64u>}’ to ‘bool’ in initialization
explicit operator bool() const { return bool{id}; }
^
Makefile:11943: recipe for target 'libbitcoin_server_a-checkpoints.o' failed
make[2]: *** [libbitcoin_server_a-checkpoints.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from ./cpp-ethereum/libethereum/CommonNet.h:28:0,
from ./cpp-ethereum/libethereum/ClientBase.h:30,
from ./cpp-ethereum/libethereum/Client.h:27,
from ./cpp-ethereum/libethashseal/Ethash.h:25,
from ./validation.h:44,
from ./txdb.h:20,
from ./index/txindex.h:10,
from init.cpp:24:
./cpp-ethereum/libp2p/Common.h: In member function ‘dev::p2p::Node::operator bool() const’:
./cpp-ethereum/libp2p/Common.h:259:52: error: cannot convert ‘const NodeID {aka const dev::FixedHash<64u>}’ to ‘bool’ in initialization
explicit operator bool() const { return bool{id}; }
^
Makefile:11901: recipe for target 'libbitcoin_server_a-blockencodings.o' failed
make[2]: *** [libbitcoin_server_a-blockencodings.o] Error 1
Makefile:12069: recipe for target 'libbitcoin_server_a-init.o' failed
make[2]: *** [libbitcoin_server_a-init.o] Error 1
make[2]: Leaving directory '/root/qtum/src'
Makefile:18637: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/root/qtum/src'
Makefile:786: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

How did you fix this?


Handle cases of reset_index level being None or an empty list

Closes #863
As I was writing the test for None, I thought about the case of an empty list.
I wasn't sure how it should be handled, but thankfully I don't have to break my head over it. I simply asked: wwpd? (what would pandas do?)

 I'm not sure what version the CI is using, so I'm not sure how to match.

Quite a few CIs failing. I'm comparing to the output from https://github.com/pandera-dev/pandera/pull/862 which was just a doc fix: I see that black isn't happy.
I have 21.12b0 and 22.3.0.
22.3.0 makes no changes to either file.
21.12b0 changes both files.
I'm not sure what version is running in CI.

CI uses 22.3.0 https://github.com/pandera-dev/pandera/blob/master/.pre-commit-config.yaml#L37-L41, I'd recommend using pre-commit hooks locally so that it aligns with CI
also, breaks in the unit tests are due to protobuf==4.21.0 which has been yanked but somehow still being install by CI.
Will perhaps have to pin it to <4.21.0 as a quickfix.

Black is now happy. Thanks for pointing me to the pre-commit config. It was the custom line-length that was creating the difference. :)
For the issue with protobuf, I'll wait on you for next steps.


Replace CMake deps on gtest_main with iree::testing::gtest_main

The build only fails because it's based on the current master. Test locally against the changes introduced within #371 with which the build is passing.

Rebased on latest master.