Failed build notifications aren't being sent

We are using Ivy for dependency management. This results in there being module builds for each jenkins project. For some reason build failures aren't going to slack. Only "back to normal" messages are being sent there.

When a build fails does Jenkins report it as failed?  If so then go into the job configuration and confirm failed build is checked one slack notifications.

Yep. The email notification goes out saying the build has failed but the slack notification doesn't. Other slack notifications also work. It is just the failed build slack notification that isn't working.

Please provide slack plugin version and Jenkins version.  Also, any potentially related stack traces from logs.

Slack plugin is 1.7. Jenkins version 1.606.
Jenkins log contains only one stack trace. Not sure it is relevant:
java.io.IOException: Unable to read /percentile/apps/jenkins/jobs/help/config.xml
at hudson.XmlFile.read(XmlFile.java:144)
at hudson.model.Items.load(Items.java:280)
at jenkins.model.Jenkins$17.run(Jenkins.java:2673)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
at jenkins.model.Jenkins$7.runTask(Jenkins.java:903)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.thoughtworks.xstream.io.StreamException:  : input contained no data
at com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:126)
at com.thoughtworks.xstream.io.xml.AbstractPullReader.readRealEvent(AbstractPullReader.java:148)
at com.thoughtworks.xstream.io.xml.AbstractPullReader.readEvent(AbstractPullReader.java:141)
at com.thoughtworks.xstream.io.xml.AbstractPullReader.move(AbstractPullReader.java:118)
at com.thoughtworks.xstream.io.xml.AbstractPullReader.moveDown(AbstractPullReader.java:103)
at com.thoughtworks.xstream.io.xml.XppReader.(XppReader.java:63)
at com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:54)
at com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:65)
at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1053)
at hudson.XmlFile.read(XmlFile.java:142)
... 10 more
Caused by: java.io.EOFException: input contained no data
at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3003)
at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
at com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:109)
... 19 more

/percentile/apps/jenkins/jobs/help/config.xml was an empty file so I moved it out of the way and the exception no longer shows up in the logs.

Here is the relevant bit from the log file:
Apr 01, 2015 3:34:25 PM INFO hudson.model.Run execute
testtwo/percentile:testtwo #48 main build action completed: FAILURE
Apr 01, 2015 3:34:26 PM WARNING jenkins.plugins.slack.ActiveNotifier completed
Project percentile:testtwo has no Slack configuration.
Apr 01, 2015 3:34:26 PM INFO hudson.model.Run execute
testtwo/percentile:testtwo-megabank #48 main build action completed: SUCCESS
Apr 01, 2015 3:34:26 PM WARNING jenkins.plugins.slack.ActiveNotifier completed
Project percentile:testtwo-megabank has no Slack configuration.

Ok I see what has happened now. There seems to be separate configuration for modules and projects in Jenkins as far as slack is concerned. This doesn't seem to be the case for email notifications. It means that we have to go and configure each module separately if we want to use slack. We don't need to do that for email notifications.

It would be good if someone would contribute combining them.  So there's only the post build step and when you add that step you have to configure it as well.

I don't actively develop this project.  I only maintain pull requests and releases.  It would be great of someone could merge the UI so there's not so many moving parts.  That is the post-build step has configuration.

I am running into issue where failed builds are not being notified as well.

This happened to me as well. I initiated a job failure on purpose since I created the job.  I finally set to notify on success AND failure, changed the job to finally succeed, I then made the job fail and it started working. Odd....

In your case it doesn't notify repeated failures.  If you want that then you'll need to enable that option.

I also observed the same issue but after selecting "Notify Repeated Failure" it worked fine.. I see failure build notifications are triggering back to slack.

should be fixed by moving to post build actions


Missing Market Bug

My Market shows up in the Sort Categories, but doesnt show when I click on that category ( I can scroll on the markets pg and see the market- just doesnt filter in when sorting categories)

working - closing


[Doc-Enhancement] Bot content cannot be changed based on user selected Teams theme

Hi Team,
The current user interface (UI) theme such as default, dark, or contrast can be identified using Teams sdk in tab with following reference: https://learn.microsoft.com/en-us/javascript/api/@microsoft/teams-js/app.appinfo?view=msteams-client-js-latest#@microsoft-teams-js-app-appinfo-theme
Based on theme, images or content styles can be changed in tab application. But the same thing cannot be done in Bots. Content styles/images posted using adaptive cards in bots cannot be changed based on theme. So, same thing needs to be considered during the design. Please mention the note related to the same.

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

ID: 3af8496d-46be-a691-11e1-16734f71f891
Version Independent ID: be0ff3e1-8bef-5ca7-8d9c-566e89e3fd41
Content: Bots in Microsoft Teams - Teams
Content Source: msteams-platform/bots/what-are-bots.md
Service: msteams
GitHub Login: @surbhigupta
Microsoft Alias: anclear

@surbhigupta12 - Could you please help to add the above note in the doc - https://learn.microsoft.com/en-us/microsoftteams/platform/bots/what-are-bots
Note : Bot content cannot be changed based on user selected Teams theme.


WIP: Wrap PCA shape signed distance function

itkPCAShapeSignedDistanceFunction was not wrapped. Wrap it for double
CoordRep (only type supported since OptimizerParameters is hardcoded as
templated over double)  and for the space dimensions that have been
selected by the user. It is only wrapped for the default image type which
is itk::Image<double, VSpaceDimension>.

CMake Error at Wrapping/TypedefMacros.cmake:220 (message):
  Module
  /Users/vsts/agent/2.146.0/work/1/s/Modules/Segmentation/SignedDistanceFunction/wrapping/itkShapeSignedDistanceFunction.wrap
  or
  /Users/vsts/agent/2.146.0/work/1/s/Modules/Segmentation/SignedDistanceFunction/wrapping/wrap_itkShapeSignedDistanceFunction.cmake
  not found.
Call Stack (most recent call first):
  Wrapping/TypedefMacros.cmake:168 (itk_load_submodule)
  Modules/Segmentation/SignedDistanceFunction/wrapping/CMakeLists.txt:8 (itk_auto_load_submodules)

@thewtex : Missing file. Should work now.

PR on master created #492

This is great, thanks @fbudin69500  and @thewtex


[DEV-2564] Feature: Pagination

Added functionality for both classic Pagination and Infinite Loading, as discussed on the call yesterday.
Classic Pagination is used by default, guides on how to enable Infinite Loading are provided in the code and in README.
Any opinions and concerns are welcome! :)

@oleg-semyonov please always indicate that you're responsible for delivering the PR :)

@digitalbase @yuriyyakym would like to get your opinions here before merging :)

Now shouldn't infinate loading not automatically load content when you get to the bottom of the page (like without a button) ?

This makes it very hard to read the footer of the page (should it be there), so I'd refrain from implementing it.

Now shouldn't infinate loading not automatically load content when you get to the bottom of the page (like without a button) ?

In addition to Kamil's note, I don't think it's a scope of the starter. We already expose all needed methods to handle infinite loading, so if someone would like to have it load on scroll, they can easily do so in a way they like it.


zsh-autopair: init at 1.0

Motivation for this change
A plugin that auto-closes, deletes and skips over matching delimiters in zsh intelligently
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 112661 at cfb6e6a9 run on x86_64-linux 1

1 package built:

zsh-autopair

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/shells/zsh/zsh-autopair/default.nix:14:3:
   |
14 |   installPhase = ''
   |   ^


Better debugging/trace story for on-chain code

Currently, debugging Validator code running on-chain is painful since there is no equivalent of Show which compiles to plutus core.
For me, the debugging story has been:

Use traceIfFalse with a descriptive error on all boolean conditions of the Validator.

Look at the trace output given by failing tests to get a view of the TxInfo for the ScriptContext.

The above are good sometimes but when the time comes to properly trace execution, the picture is a lot worse. We end up having to insert conditional traceErrors and manually binary search to find out values...
In #3142, @ak3n mentioned Data may be a builtin in future, which might enable some better options.
Meanwhile: what are our best options for debugging on-chain code currently? Would it be viable (if a bit painful) to use the CEK machine API?

@bezirg are you the best person to answer this question:

Meanwhile: what are our best options for debugging on-chain code currently? Would it be viable (if a bit painful) to use the CEK machine API?

? This issue is old, but that doesn't make the question any less important.

... meanwhile, we do now have a debugger and working on a better debugging experience is one of our objective and is something that we already do, hence I'm marking this issue with status: objective.


check if the db file path dir exists before setting up schema

What changed?
This PR checks if the parent directories exist for the given database file path and returns a more descriptive error to the user.

Why?
The current error output is confusing. Fixes the issue mentioned in https://github.com/temporalio/temporalite/issues/55

How did you test it?
Yes. Tested it locally.

Potential risks
Users are confused by a new error?

Is hotfix candidate?
No.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

LGTM, please just sign the CLA and we should be good to go. Thanks!

I agreed to the CLA a couple times but I'm not sure why it's not showing

Might be because your commits are signed off as @zillow-jeff, not @theverything.


x/tools/go/analysis/analysistest: Run will pass generated test files to analyzer

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

$ go version
go version go1.15 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="auto"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/simon.sawert/Library/Caches/go-build"
GOENV="/Users/simon.sawert/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/simon.sawert/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/simon.sawert/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/simon.sawert/git/analyzer-mre/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/dy/tkxx13zx3n1d_m28k_3lh6w00000gr/T/go-build111181793=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
I created testdata including a test file (a file suffixed _test.go) and then I created a test and used analysistest.Run to test this code.
What did you expect to see?
Only my files from the testdata to be passed to the analyzer run function.
What did you see instead?
The generated test file(s) in the build cache gets passed.

The problem for me is that the analyzer I've created adds a diagnostics report on the test code generated in cache and thus I cannot get my test to pass. I guess this might be related to #40574.
Here's an minimal reproducible example:
% tree
.
├── amre.go
├── amre_test.go
└── testdata
    └── src
        └── mypackage
            ├── mypackage.go
            └── mypackage_test.go

3 directories, 6 files

package amre

import (
    "fmt"

    "golang.org/x/tools/go/analysis"
)

var Analyzer = &analysis.Analyzer{
    Name: "amre",
    Run:  run,
}

func run(pass *analysis.Pass) (interface{}, error) {
    for _, file := range pass.Files {
        filename := pass.Fset.Position(file.Pos()).Filename
        fmt.Println("testing", filename)
    }

    return nil, nil
}

package amre

import (
    "testing"

    "golang.org/x/tools/go/analysis/analysistest"
)

func TestA(t *testing.T) {
    testdata := analysistest.TestData()

    analysistest.Run(t, testdata, Analyzer, "mypackage")
}

% go test ./... -v
go test ./... -v
=== RUN   TestA
testing /Users/simon.sawert/Library/Caches/go-build/00/0090ea545eb3074c3efc79841f1af52ecd6009c127392415405c05125895f58a-d
testing /Users/simon.sawert/git/analyzer-mre/testdata/src/mypackage/mypackage.go
testing /Users/simon.sawert/git/analyzer-mre/testdata/src/mypackage/mypackage.go
testing /Users/simon.sawert/git/analyzer-mre/testdata/src/mypackage/mypackage_test.go
--- PASS: TestA (0.96s)
PASS
ok      analyzer-mre    1.258s

Oh, this isn't related to the analysistest in any way, it's the analyser itself! Running the same code on a package containing tests will have the same result. Closing this and will try to figure out how I can avoid these getting passed to the analyser completely.


Adding implicit conversion from ArraySegment and TryCopyTo APIs.

Note: This PR will only pass CI after https://github.com/dotnet/corefxlab/pull/1602 is merged.
cc @KrzysztofCwalina, @shiftylogic

@dotnet-bot test this please

@dotnet-bot test Innerloop Ubuntu16.04 Debug Build and Test

Looks good


Add Ethernet-bridge support for QoS-OLSR

I have done some changes based on the comments. This PR is focused on QoS-OLSR Ethernet bridging without NATS for 1.5 and 1.0 MS versions. Others changes have be done and I will make the PR of them.
The changes can be summarized as follows:

created a config file for QoS-OLSR
added another if condition in case of some typos while writing a routing protocol
fixed some typos for the mesh.conf

Duplicate of #310
Let's review this as is - focusing on the integration with 1.0/1.5 (not NATS) at this point.

@joenpera quick sanity check - there's nothing in the new NATS configuration that uses bridge_settings.sh is there? I don't believe so but before I go ahead and approve a merge...
My thinking is as follows. These changes support eth bridge in 1.5 and 1.0, without impacting NATS + 2.0. We should therefore merge this PR without too much complaint as long as @francislin12 confirms he has tested on 1.5 (he has, and it works) so that at least there is some form of QoS-OLSR in develop (even if it is for 1.5/1.0). I know there's some IPv6 stuff randomly in there, plus the configuration probably isn't done in the nicest manner but at lease the feature is then merged.
The next task would then be of course moving QoS-OLSR to 2.0 in a clean and proper way.
Thoughts?

@joenpera quick sanity check - there's nothing in the new NATS configuration that uses bridge_settings.sh is there? I don't believe so but before I go ahead and approve a merge...
My thinking is as follows. These changes support QoS-OLSR eth bridge in 1.5 and 1.0, without impacting NATS + 2.0. We should therefore merge this PR without too much complaint as long as @francislin12 confirms he has tested on 1.5 (he has, and it works) so that at least there is some form of QoS-OLSR in develop (even if it is for 1.5/1.0). I know there's some IPv6 stuff randomly in there, plus the configuration probably isn't done in the nicest manner but at lease the feature is then merged.
The next task would then be of course moving QoS-OLSR to 2.0 in a clean and proper way.
Thoughts?

Current develop comms controller (NATS) is not using bridge_settings.sh.    Later MS2.0 should implement bridge and routing and those will be removed from comms controller.  From that point comms controller just controls radio resource and starts 11s.


Integration test files naming requirement breaks VSCode test sidebar

Steps to reproduce

Create a patrol integration test
Open VSCode test sidebar
Click the "Run Tests" button

Actual results
When using the VSCode test sidebar, the "Dart Code" plugin will search for all occurrences of files ending with _test.dart, and will present them in a list, making it easy to see at a glance which are passing and which are failing, and overall improving the DX when iterating over tests.
The dart extension assumes that all files ending with _test.dart can be run with the standard dart and Flutter test runners, so when it encounters a Patrol integration test, it tries to run it but just hangs indefinitely.
This makes it impossible to use the very useful "Run Tests" button in that panel:

Could the requirement for the tests to end with _test.dart be removed? That way, teams using VSCode could freely rename their patrol test to another suffix, allowing them to use VSCode test panel
Logs

Logs
<!-- Replace this line with your logs. Do not remove the backticks! -->

Patrol version
patrol: ^2.3.1
Patrol Doctor output

Patrol Doctor output
Program adb found in /Users/vincenthoodoo/Library/Android/sdk/platform-tools/adb
Env var $ANDROID_HOME set to /Users/vincenthoodoo/Library/Android/sdk
Program xcodebuild found in /usr/bin/xcodebuild
Program ideviceinstaller found in /usr/local/bin/ideviceinstaller

Flutter Doctor output

Flutter Doctor output
[!] Flutter (Channel [user-branch], 3.13.9, on macOS 14.1.2 23B92 darwin-x64, locale en-NZ)
    ! Flutter version 3.13.9 on channel [user-branch] at /Users/vincenthoodoo/Dev/flutter
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/docs/get-started/install.
    ! Upstream repository unknown source is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to unknown source to dismiss this error.
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] VS Code (version 1.84.2)
[✓] Connected device (3 available)
[✓] Network resources

Thanks for bringing this issue to our attention @vincent-hoodoo! We'll release a fix soon, likely as patrol_cli v2.4.1.
In the meantime I recommend you to upgrade to latest Flutter v3.16.x, and to latest Patrol v3.2.x.

Thank you @piotruela and @bartekpacia , I just implemented test_file_suffix in my patrol configuration and it's working well, I can now run my test suite from VSCode.
I noticed that https://github.com/leancodepl/patrol/pull/2009 didn't include any documentation update, was there a reason for it? I'm probably not the only one with this issue, someone else might be wondering how to address it.


Undocumented behavior

Passing in a 0 for usagePage or usageId acts as a "wildcard" and will return any matching controls; passing in 0 for both parameters returns all controls.
Aside from being an obtuse design, which should instead be exposed through a separate API, this behavior isn't documented but yet is critical for most implementations.

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

ID: 69ae80d3-bd52-a6bb-90b7-b51c0e8b63f7
Version Independent ID: 38fe55f5-f4e9-4044-cf09-cbb6206c8edc
Content: HidDevice.GetNumericControlDescriptions(HidReportType, UInt16, UInt16) Method (Windows.Devices.HumanInterfaceDevice) - UWP app developer
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.devices.humaninterfacedevice.hiddevice.yml&version=GBlive&_a=contents
Service: windows
GitHub Login: @wdg-dev-content
Microsoft Alias: wdg-dev-content

Thanks for the feedback! While I can't do anything about the API design, I have updated the relevant docs for the GetNumeric and GetBooleanControlDescriptions methods.


feat: Add standard attribute/property definitions

Component name
Components updated

[x] pfe-accordion
[x] pfe-autocomplete
[x] pfe-avatar
[x] pfe-badge
[x] pfe-band
[x] pfe-button
[x] pfe-card
[x] pfe-content-set
[x] pfe-navigation
[x] pfe-number
[x] pfe-tabs

Related issue

#933 Update attribute prefixing

TODO

[x] add support for static get properties() on the base class (note to self: use Object.getPrototypeOf(this.constructor).properties)

Preview
Link(s) to demo page(s) where this element can be viewed:

Preview

What has changed and why
Property definitions provide a standard, streamlined way to declare the properties and attributes your component needs.  Property definitions provide the following features:

Two-way binding between property and attribute values.
Default value initialization.
Data types (for properties).
Observer function to be run when a value changes.
Optional namespacing prefix for attribute names.
Aliasing properties to one another, for phased deprecation.
And more!

More information
Testing instructions

Regression testing, no visible changes to components

Browser requirements
Your component should work in all of the following environments:

[ ] Latest 2 versions of Edge
[x] Internet Explorer 11 (should be useable, not pixel perfect)
[x] Latest 2 versions of Firefox (one on Mac OS, one of Windows OS)
[ ] Firefox 68 (or latest version for Red Hat Enterprise Linux distribution)
[x] Latest 2 versions of Chrome (one on Mac OS, one of Windows OS)
[x] Latest 2 versions of Safari
[ ] Android mobile device (such as the Galaxy S9)
[ ] Apple mobile device (such as the iPhone X)
[ ] Apple tablet device (such as the iPhone Pro)

Ready-for-merge Checklist
Check off items as they are completed.  Feel free to delete items if they are not applicable.

[x] Expected files: all files in this pull request are related to one request or issue (no stragglers or scope-creep).
[x] Tests have been updated to cover these changes.
[ ] Browser testing passed.
[x] Repository compiles and tests pass.
[ ] Changelog updated (not needed for documentation updates).
[x] Documentation (README.md, WHY.md, etc.) updated or added.
[ ] Link to the demo recording:

Merging
Please squash when merging and ensure your commit message uses conventional commit formatting.
Be sure to share your updates with the<EMAIL_ADDRESS>mailing list!

I did some testing in the latest release of Edge (Edgium 85) on Windows 10.  I checked...

pfe-accordion
pfe-autocomplete
pfe-avatar
pfe-badge
pfe-band
pfe-button
pfe-card
pfe-collapse

...before running out of time.  I did not find any Edge-specific problems, but I did find a pfe-avatar issue and two potential pfe-band issues (but I could be just misunderstanding pfe-band).
pfe-avatar
The pfe-avatar demo page isn't working right now, in any browser.
When pfe-avatar--width isn't defined, the following line errors because .replace can't be called on undefined.
const size = this.cssVariable("pfe-avatar--width").replace(/px$/, "") || PfeAvatar.defaultSize;

pfe-band
On the demo page, the "Complement band, layout classes" section has a card titled "Aside: right body bottom", but it's displayed on the left.

In the "Short content band" section, a card titled "Aside: left body top" appears on the right.  The CTA is also large, but that seems to be inentional since its text reads "This CTA has overrides".

(Note: it looks like this in


Publish test artifacts for all projects.

Some of the code we have under tests is or will be reused in other
projects. Mainly our test fixtures will be reused but creating
individual projects which just test utilities for each already existing
project seem overkill.

Thanks for this

I missed that. For now the 4MB will not hurt us much. But i will take a look and try to get rid of those jars.

looks like release runtimes haven't changed
https://github.com/joernio/joern/actions/workflows/release.yml


Regression: "a match type could not be fully reduced" when flattening a list of tuples

Compiler version
Affected: 3.5.0 and newer (tested on Scastie up to 3.6.1)
Latest working version: 3.4.3
Minimized code

case class MyNum(i: Int)

val l = List((MyNum(1), MyNum(1)))

l.flatMap(_.toList)

https://scastie.scala-lang.org/ZXMSKeMdT9SdHzvHdxVaQw
Output
Does not compile on 3.5.0 and newer:
    Found:    List[Tuple.Union[(_$1 : (Playground.MyNum, Playground.MyNum))]]
    Required: IterableOnce[Playground.MyNum]

    Note: a match type could not be fully reduced:

      trying to reduce  Tuple.Union[(_$1 : (Playground.MyNum, Playground.MyNum))]
      trying to reduce  Tuple.Fold[(_$1 : (Playground.MyNum, Playground.MyNum)), Nothing,
      [x, y] =>> x | y]
      failed since selector (_$1 : (Playground.MyNum, Playground.MyNum))
      does not uniquely determine parameters h, t in
        case h *: t => h | Tuple.Fold[t, Nothing, [x, y] =>> x | y]
      The computed bounds for the parameters are:
        h <: Playground.MyNum
        t <: Playground.MyNum *: EmptyTuple.type

Expectation
Should compile (as it does on 3.4.3) and give a flat list of MyNums.

Last good release: 3.5.0-RC1-bin-20240403-ece87c3-NIGHTLY
First bad release: 3.5.0-RC1-bin-20240404-a7f00e2-NIGHTLY
Bisect points at 0bf43b2fbb1ad0faa64cd1da97a9682b02724c49
cc @sjrd

Given the bisect commit, I suspect that the new error is legitimate. It fixed an unsoundness issue (https://github.com/scala/scala3/issues/19746), so it may very well prevent compilation of code that worked more-or-less by chance before.

Not sure if it get this right.
Is my usage of Tuple's toList function unsound?  Or does the current implementation of toList just incorrectly rely on unsound behavior that has been fixed in 3.5.0?
The signature of toList is
inline def toList: List[Union[this.type]]

In its current state toList is quite limited.  Any chance to get that improved?

@hegetim I think @sjrd  meant that https://github.com/scala/scala3/issues/19746 was an unsoundness issue (check the soundess label), and the fix for that caused this regression (that's where the bisect script points). We need to fix it separately.

@Gedochao thanks for the explanation.  So I guess this is not exactly a regression.  The error is valid because in the declared return type, this.type is too narrow to be used in Tuple.Union.  In order to improve the usability of Tuple's toList function, we probably have to make the widening of the tuple type explicit?
For example, changing toList into an extension method like this
extension [T <: Tuple](t: T)
  inline def toList: List[Tuple.Union[T]] = t.productIterator.toList.asInstanceOf[List[Tuple.Union[T]]]

would solve the issue (see https://scastie.scala-lang.org/42ADHhqzSEaaAmirzwxqyg)
I'm not sure if this can be done in a binary compatible way.


Remove version: WHONET.2023 version 23.15.1

Microsoft Reviewers: Open in CodeFlow

URL: https://whonet.org/WHONET2023-Setup-x86.exe
Status Code: 200
(Automated message - build 870)


The correct way to set openthread-specific configuration variables (IDFGH-11141)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Some of openthread-specific options are set through Kconfig menu. For example, the OPENTHREAD_CONFIG_DUA_ENABLE thread option is set using the OPENTHREAD_DUA_ENABLE Kconfig option. The build system includes a corresponding header file (components/openthread/private_include/openthread-core-esp32x-ftd-config.h for example) which translates Kconfig's CONFIG_OPENTHREAD_DUA_ENABLE into a thread's OPENTHREAD_CONFIG_DUA_ENABLE. This header file is included by the openthread library through the OPENTHREAD_CONFIG_FILE definition.
But what if the required option is not in the Kconfig menu and corresponding components/openthread/private_include/openthread-core-esp32x-***-config.h header file? How to define a option in this case?
For example, I want to set the openthread option OPENTHREAD_CONFIG_RADIO_STATS_ENABLE, which enables the radio stats openthread cli command (examples/openthread/ot_cli project). But neither in the Kconfig menu nor in the settings translation header file is there any mention of radio statistics. What is the correct way to enable this option without changing the SDK source code?

Hi vke, Sorry for the delay, you can just add the config in the file components/openthread/private_include/openthread-core-esp32x-***-config.h manually.
For example: add this line in the file components/openthread/private_include/openthread-core-esp32x-radio-config.h
#define OPENTHREAD_CONFIG_RADIO_STATS_ENABLE 1

Thanks for your reply! Yes it is possible and I will do as you said, thanks! But in this case, I will change the SDK files (not my own project files) and I will have to merge this changes with each SDK update.

Ok, right, I will create a MR in our internal branch add this config to the IDF and make it as a menuconfig, but it need to wait for one or two weeks for getting the changes on the github.

Just for OPENTHREAD_CONFIG_RADIO_STATS_ENABLE, or something general that allows to change any option, such as including a user config to override any openthread config defines not included in menuconfig?

Also I can add a menuconfig for enable custom openthread config, if you enable this feature, you can use your own config.

Ok, right, I will create a MR in our internal branch add this config to the IDF and make it as a menuconfig, but it need to wait for one or two weeks for getting the changes on the github.

Just for OPENTHREAD_CONFIG_RADIO_STATS_ENABLE, or something general that allows to change any option, such as including a user config to override any openthread config defines not included in menuconfig?

Yah, the same as your thought.

Sorry, I read your commit again, and. I think I can add a config for eanbling the custom openthread config feature, and if the user enable this config, they can use there own config(the file name can be configured still via menuconfig), how about this way?

In my opinion, this would be the ideal solution, and also the simplest. Just an option to include a user's openthread config. The user will be able to independently set any definitions, even new ones that will appear in future versions of openthread.
Thank you!


Proper Replacement of external CSS

Category

[x] Question
[ ] Typo
[ ] Bug
[ ] Additional article idea

Expected or Desired Behavior
If you are reporting a bug, please describe the expected behavior. If you are suggesting an enhancement please describe thoroughly the enhancement, how it can be achieved, and expected benefit.
Observed Behavior
I'm using Asciidoctor.js to render text content in a SPFx webpart since we use this a lot in our documentation.
In order to narrow the impact of the asciidoctor.css I've included it in the webpart.module.scss and thus it will rewrite the css attributes to be unique.
The problem aries where Asciidoctor.js renders the orginal class names and I need to substitute them as follows.
  private regexp = new RegExp('class=\"(' + Object.keys(styles).join("|") + ')\"', "g");
  private asciidoctor = Asciidoctor();

private renderDocument(text: string): void {
    var c = this.asciidoctor.convert(text);
    var str = c.replace(this.regexp, (full, token) => {
      return 'class="' + styles[token] + '"';
    });

    return str;
  }

Is there a preferred of doing such task or is this a good way of doing this to be a good SPFx citizen?
Cheers,
Mario

Hi @mariotoffia, the approach you are following could have some perf issues. How big are these documents? Do you notice perf issues with this approach?

Wouldn't it be sufficient to keep the original class names but to wrap them in the web part class name, like:
In the .scss file:
.myWebPartClass {
  :global {
    .originalClass1 {
    }
    .originalClass2 {
    }
  }
}

In your web part you would then use:

Using this approach you wouldn't need to postprocess the document. The only unique class you'd have would be the root web part CSS class which you can easily reference from the styles variable.

Hi @waldekmastykarz, that would work. But that would not make the class names unique. i.e. there will still be chances of class name collisions with other web parts. If that is not a concern, then this should work fine.

While the classes wouldn't be unique, they wouldn't collide with other web parts because they are nested in the .myWebPartClass which would get appended a unique hash when transpiled from .scss to .css. So the only risk is if there were other elements on the page targeting nothing but the global class name. In such case you'd need to override the specific properties.

@waldekmastykarz  I like your approach since as someone stated above - my solution is not really a solution since the performance hit. However as a noop in html/css world... can I use the @import in the scss file to accomplish this since asciidoctor do have lots of css specified?
like:
.asciidocviewerwebpart {
  :global {
    @import "asciidoctor.js"
  }
}

today I'm using this import as follows:
.asciidocviewerwebpart {
  @import "asciidoctor.module";
}

Cheers,
Mario

According to the documentation you should be able to do it.

We closed this issue as it had not activity within last 180 days. This is a generic process we have decided to perform for issues, which have not been explicitly marked still to be "work in progress" based on tags. We are performing this cleaning to make sure that old issues that have already been solved (but not closed) or are no longer relevant are cleaned out and make the issues more manageable. If this issue still valid, we would ask you to open a new issue and follow the guidance in the issue template related on the recommended location. We do apologize any inconveniences this might cause. Please do remember that issues in the issue lists are also messages for others in the community, so you can also check if you can assist on any of them. “Sharing is caring!”


Fix: Update .gitignore

Fixes #251
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with gradlew app:connectedGmsDebugAndroidTest to make sure you didn't break anything (with an emulator running or phone connected)

[x] If you have multiple commits please combine them into one commit by squashing them.

I had updated .gitignore and ran  $ git rm --cached .idea/gradle.xml

Thanks!


squoosh-cli bus-errors on mac M1 mac book pro

running squoosh-cli on M1 (Apple Silicon) bus errors when trying to compress any jpeg file (I haven't tried it on other formats)
To Reproduce
Steps to reproduce the behavior:

npm i -g @squoosh/cli
squoosh-cli --mozjpeg auto 1.jpg
After a few seconds....
zsh: bus error  squoosh-cli --mozjpeg auto 1.jp

Expected behavior
Not to crash
Version:

OS w/ version: macOS Big Sur 11.3.1
Node version: v16.0.0
npm version: 7.10.0

Is your issue related to the quality of image compression?
Please attach original and output images (you can drag & drop to attach).

Perhaps this issue has the same underlying problem as this issue opened on the next.js repository.
Running next.js with arm native Node Version 16 causes segmentation faults when trying to compress images using the squoosh library.

I just published @squoosh/lib v0.3.0 which has a rebuild of all our codecs. I just tested it on my M1 with Node 16 and it worked. Can you give it another try?
I’ll close this bug, but please re-open if it’s still breaking for you!

I just published @squoosh/lib v0.3.0 which has a rebuild of all our codecs. I just tested it on my M1 with Node 16 and it worked. Can you give it another try?
I’ll close this bug, but please re-open if it’s still breaking for you!

I seem to be having a bus error on M1 still


Translation fix for fill-in-the-blank-with-placeholder-text.russian.md

Translated headers;
Fixed translation mistakes.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


Create dupage.txt

@vkoprivica Pull request merged. Please notice that free educational license for JetBrains tools is for high and higher schools students, i.e. those who are over 13 of age. Thank you!


Workaround for IE8 bug on related link bullet points

Fixes an issue where pseudo elements on an anchor tag receive the same
text decoration as the anchor tag.
IE 8 (before)

IE 8 (after)

Chrome (no change)

Did you try using the ie(8) mixin and setting text-decoration: none on the pseudo element?

Not convinced adding more markup is the solution here, but don't have the context – is there a reason the bullets being added to the links and not the list items, where you'd usually expect to find them?

Another issue with the current implementation – Voiceover (and possibly other assistive tech) will read the bullet as part of the link. So when tabbing through the links on the page it'll read 'Bullet. National curriculum in England: primary curriculum'.
Using a pseudo element on the list item would prevent that but might still cause similar problems. Ideally though you would just use a normal bulleted list, and no pseudo elements at all?

@36degrees

is there a reason the bullets being added to the links and not the list items, where you'd usually expect to find them?

Explained here: https://github.com/alphagov/static/pull/941/files#diff-b2af3eb92cd75ba5d8c0d1ab14ce7424R25. I'm not aware of a way to achieve the same effect with bullets on the list item.
@alextea
Unfortunately that won't work in this instance. The problem is that IE8 fumbles the CSS spec and ignores text-decoration rules on the pseudo element.

@36degrees given these pages are in beta, I'd suggest we proceed with the current implementation. I've made a note of the issue here https://trello.com/c/37jp8eJQ/514-taxonomy-sidebar-related-links-bullet-points-can-we-make-these-better-for-screenreaders. Alex'll take another look at this once he's back from leave the week after next.

It'd be good to document the reason behind '[making] the bullets clickable and [highlighting] them on link hover' because that seems like an odd thing to do… was this something that came out of user research?

I agree with @36degrees – making bullet points clickable seems like unnecessary complexity and web inconsistent behaviour.

We have anchors in lists all over GOV.UK and we don't reimplement bullets.

These are all fair points and none of these decisions are final. We have enabled the A/B test today and are keen to keep running experiments on it to see how it can be improved.
We have a trello card to revisit this, and if people think this isn't a good way forward we can remove it before the A/B test ends.
Please note that this is only shown inside the new navigation pages to a small percentage of users. The sidebar is a bit different already in terms of its layout, so there are quite a few things to consider before we enable it to 100% of users:
Related Links

Taxonomy sidebar

Please do keep giving your feedback on these PRs, because I think that's important and will help shape things as we go along.


read_callback parameters not used if given initial_input

https://github.com/carlmontanari/scrapli/blob/d0eb38b56320acd054c5efc0455d3dde8e4011c5/scrapli/driver/generic/sync_driver.py#L534C32-L534C32
If read_callback is given an initial_input, then read_callback does a write and recursively calls itself. Only the callback parameter is passed to that recursive call, preventing any other parameter from having an effect.

hmm yeah you just mean the delay/timeout args? or am I missing something else too :D
pr would be most welcome if you're up for it! (just plz do sync and async)

hmm yeah you just mean the delay/timeout args? or am I missing something else too :D
pr would be most welcome if you're up for it! (just plz do sync and async)

Yeah read_output, read_delay and read_timeout.
I can make a PR. I assume something simple like below would work for both (I haven't looked at async) ?
        if initial_input is not None:
            self.channel.write(channel_input=f"{initial_input}{self.comms_return_char}")
            return self.read_callback(callbacks=callbacks, read_output=read_output, read_delay=read_delay, read_timeout=read_timeout, initial_input=None)

yep, that looks good to me! much appreciated! if ya dont wanna/dont get to it I can sort it out this weekend prolly too!
thanks for raising it @MattCatz 🥳

sorted thanks to @MattCatz !


[TRAH] Sergei / TRAH 3108 / Add redirect route for signup

Changes:

Create Redirect component
Create routes object

Video:
https://github.com/deriv-com/traders-hub/assets/120570511/ae2d8c87-7225-48ac-bded-00b3333c04f0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
446

Relevant Lines:
784

💛  - Coveralls


Implement flake8-raise

GitHub, PyPI.

[x] R100: raise in except handler without from

Already implemented via B904 from flake8-bugbear
Already implemented via TRY200 from tryceratops

This is buggy and only triggers with raise Exception() and not raise Exception (no parentheses)

Maybe implementation for one of these should be scrapped with the error code aliased to the other? :thinking:

[x] R101: use bare raise in except handler

Already implemented via TRY201 from tryceratops

[ ] R102: unnecessary parentheses on raised exception

So this plugin is mostly implemented. R102 looks like it should be a relatively easy rule to define.

Just confirming that in addition to adding R102, we should:

Remove B904, and mark it as an alias of TRY200.
Fix TRY200 to flag raise Exception (without parentheses).

Yeah, sounds good. I guess it makes sense to keep TRY200 over B904 as tryceratops is exception-focused and flake8-bugbear is a random collection of stuff.


⚠ Jenkins Plugins Artifactory has degraded performance

In b9ca832, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1258 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 82e5887 after 12 minutes.


Table Resource Schema not valid. Spec reference unclear

Current Behaviour (for problems)

When reporting a problem, describe what happens that isn't expected behaviour?

If load an invalid json file from File > Import Column Properties > json from file... the error message "The Table Resource Schema, at {path} data curator/tabular-data-resource.json, is not valid. Please refer to https://frictionlessdata.io/specs/ for more information." is shown. The error refers to Table Resource Schema; I assume this is intended to match "Tabular Data Resource" at https://frictionlessdata.io/specs/tabular-data-resource/ but given there are other specs including "Table Schema", "Tabular Data Package" etc. it would be good to have a more specific label and/or URL.
Expected Behaviour

When reporting a problem, describe what should happen

I am referred to the precise specification so I can diagnose the issue.
Steps to Reproduce

When reporting a problem, provide a set of steps so others can reproduce the problem.

Open Data Curator using the icon

Your Environment

Include details about the environment you experienced the problem - this will help us fix the bug quicker.

Data Curator version: 1.1.0
Operating System and version: e.g. macOS High Sierra 10.13.6

Hi @kayakr
I guess at the time we wanted to protect against very specific web-links changing over time - but I guess we should rely on frictionless to to support this if it happens. At least the main page points the user in the right direction.
I'll have a look at this and see if there is something more specific we can do here.


Expected inference time on the object detection model - >4s?

I did some tests and it take a little over 4 seconds to process a single frame with the built in object detection model. I realize it is not completely the same, but I was hoping to get performance somewhat like what Intel published for their Movidius Neural Compute stick using MobileNets here: https://software.intel.com/en-us/articles/mobilenets-on-intel-movidius-neural-compute-stick-and-raspberry-pi-3 .
Is this expected behavior? Is there a way to speed up inference with this build-in model?
Also, what does the duration_ms time represent in the inference.run response?
For reference, I used the face_camera_trigger.py demo app to generate an image and the following code to see how quickly I could repeatedly process that image.  Here is the main module:
def main():
    parser = argparse.ArgumentParser()
    parser.add_argument('--input', '-i', dest='input', required=True)
    parser.add_argument('--output', '-o', dest='output')
    args = parser.parse_args()

    image = Image.open(args.input)
    image_center, offset = _crop_center(image)
    draw = ImageDraw.Draw(image)

    with ImageInference(object_detection.model()) as inference:
        print("Object detection model loaded")

        while True:
            try:
                start = time()
                result = inference.run(image_center)
                print("Total time %s seconds. Frame time %s ms" % (time() - start, result.duration_ms))

            except KeyboardInterrupt:
                break

if __name__ == '__main__':
    main()

This was after I tried a similar procedure with 'CameraInference(object_detection.model())`, which is my real goal.

Chad, Thanks for bringing this to our attention. We improved our python side post processing to reduce latency to 155 ms per inference. This also reduces CPU usages. We are working on an improved protocol to reduce latency, it will be available at later release.

@weiranzhao - thanks for the update. I just loaded your recent commit. Using my code above, I can confirm I see a faster inference inline with your measurement:
kind=PERSON(1), score=0.503174, bbox=(0, 133, 444, 781)
Total process time: 0.14915060997009277 seconds. Bonnet inference time: 36 ms
kind=PERSON(1), score=0.700792, bbox=(156, 132, 707, 774)
Total process time: 0.1789381504058838 seconds. Bonnet inference time: 36 ms
kind=PERSON(1), score=0.623835, bbox=(166, 120, 695, 787)
Total process time: 0.14641261100769043 seconds. Bonnet inference time: 36 ms
kind=PERSON(1), score=0.618723, bbox=(166, 119, 697, 789)
Total process time: 0.15200567245483398 seconds. Bonnet inference time: 36 ms


DNS over HTTPS support and encrypted SNI?

Firefox supports them also on Android and currently using DNS over HTTPS or DNS over TLS requires installing Intra or similar app acting to be a VPN (unless using Android 9 where enabling a VPN disables DoT).
I think DoH should be opt-in and the server configurable even if you ran your own resolver.

If it's based on Chromium, DDG Browser could use Bromite's patches for DoH! :)

Agree
I also hope so but because DuckDuckGo uses the webview and not bundled chromium in itself so I don't know if they could use that or not

Any updates on this? It's a major security feature and a must-have for the a security focused browser.

I found this article on how to connect android phones to a dns server of your choice. Hope it helps!

Better Encrypted SNI: Encrypted Client Hello
Good-bye ESNI, hello ECH: https://blog.cloudflare.com/encrypted-client-hello/
More information: https://tools.ietf.org/id/draft-ietf-tls-esni-08.html


[BUG] Android Provisioning Error using BLE

Reproduction steps

Launch Android App
Launch Lighting App Linux (Enable BLE and wpa_supplicant)
Select "PROVISION CHIP DEVICE WIFI"
Scan QR
Input WiFi Credentials
Connecting to Lighting App in Linux
Connection Failed because of BLE Connection Error

BLE Error Log is below in Android
04-14 14:25:17.192 D 2057     2278     BtGatt.GattService: onConnected() - clientIf=5, connId=0, status=133, address=001A7D_5
04-14 14:25:17.193 D 5353     5537     BluetoothGatt: onClientConnectionState() - status=133 clientIf=5 device=001A7D_5
04-14 14:25:17.200 I 5353     5537     chip.BluetoothManager: MATTER-3840.onConnectionStateChange status = 133, newState=0

v1.0.2 is well BLE provisioned, but the recent master code is not working well due to the above error code.
In my experience, if you try 10 times, it's about 2-3 times for success. I'm creating a ticket because I think I need to check it.
Log is attatched
LogFilter_20230414_141853-BLEProvisioning-Error.zip
Bug prevalence
2~3 / 10
GitHub hash of the SDK that was being used
62974a091b0366a18a8e88222121bbeea936dc9c
Platform
android
Platform Version(s)
No response
Anything else?
No response

I am facing the same Issue，Do you have a reliable solution？ @jeonghwan7

@nicelyjust Hi, Sorry for late reply!.
In my experience status=133 error is unstable network connection.
It seems that the success rate of commissioning increases if the commissioner and the commissioner are placed very close together.

Thank for your suggestion！ @jeonghwan7

it seems it has been rooted caused with close distance.


Jakarta EE 8 TCK job

To test Jakarta EE 8 compatibility we need to create a Jenkins job on project's Cloud Jenkins instance formally testing the API against the relevant TCK and as needed, relevant CTS subset tests.
For projects that do not already have automated testing, there is provided parameterized Jenkins job that can be invoked to perform these tests. User provides a link to an Eclipse GlassFish test build and sets the test sub-set parameters:

For CTS -- https://ci.eclipse.org/jakartaee-tck/job/jakartaeetck-certification/
For Stand-alone TCKs -- https://ci.eclipse.org/jakartaee-tck/job/standalonetck-certification/

Additional instructions and guidance for using and directly running TCKs is available on this wiki. Also in the jakartaee-tck project repository.

I'm not commiter in jakartaee-tck project and my account does nit have right to edit jobs on https://ci.eclipse.org/jakartaee-tck/
I can setup JAXB/Metro related jobs in jaxb or metro projects (https://ci.eclipse.org/jaxb or https://ci.eclipse.org/metro)

Currently whole jakartaee-tck project in master branch is not buildable because of javax -> jakarta changes being in progress.
I fixed SAAJ and added https://ci.eclipse.org/metro/job/saaj-tck-build/ job to have access to the binaries.

@Tomas-Kraus from when is jaxb-tck part of jakartaee tck? I thought it's standalone TCK living in its own repository. Who did set up this job? Isn't it what was required to be done?

Well, I misunderstand this task a bit. JAXB TCK job for Jakarta EE 8 compatibility exists since June 2019 and works fine.
https://ci.eclipse.org/jaxb-impl/job/jaxb-ri-tck/


[vite] Internal server error: Failed to resolve entry for package "promjs". The package may have incorrect main/module/exports specified in its package.json.

In vite environment ，prom-react plugin does not work.
Node： 16.17.0
React：18.0.0

Hi, sorry for taking so much time to respond.
Can you provide further information? Is there any trace or output we can use to figure out what's going on?


chore(react): update links rel and as unions to LiteralUnion for better IntelliSense

x-ref https://github.com/remix-run/remix/pull/1102#issuecomment-996850247

Suggest changing the title to "chore(react): update links rel and as unions to LiteralUnion for better IntelliSense" because as we still allow string, it has nothing to do with type safety.

instead of another dependency, can we just do whatever type trick LiteralUnion does?

instead of another dependency, can we just do whatever type trick LiteralUnion does?

done :)


Update MADEWITHVRTK.md

Added my own product, ArcaidVR

There were the following issues with your Pull Request

Commit: 249c00e8caebbb9e70b11c01ca46e24e9459e8b3
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/thestonefox/SteamVR_Unity_Toolkit

This message was auto-generated by https://gitcop.com

https://github.com/thestonefox/VRTK/commit/37ff81fd6824eed55c084fdfc4555667baaf2d2c


Turkish encoding is not importing properly

Yes, Tkinter Designer struggles with other languages than english. Try to add dummy text and then manually update the text after it's converted.

Yes, I have solved this issue.
If you have any erase turkish character, while converting to tkinter encoding will be cannot be decided properly.


Index of ActiveLabel Pattern pressed.

Is there any way I get index of which exactly Label is pressed.
I'm using mention tap I.e username and when user click on it I need userID of that user and not username. So in this case if I get the index of which username is pressed then I could fetch the userID easily.

I am looking for something similar! Have you achieved same @nitesh-ios ?

Any update on this?

Sorry there is no such thing as returning index. In this case every fucntion returns the value of the label which there you should either look into your data to find more info or use and API to query something.
I suggest using the same array which you load your TabeView with to find out other details about what just being pressed.


Missing LICENSE file

At the readme there is:

But the actual license file is missing.

I don't think the file is actually necessary; https://github.com/chrisdickinson/raf/blob/master/package.json#L22 declares explicitly a license that comes with its own license text already.

It is for automatic libraries that verify license as part of the build process.
Such as:
https://github.com/ryanuber/go-license
https://github.com/aviadl/thirdPartyLicenseCollector

For npm packages, those libraries should primarily be checking the SPDX-compliant "license" field of package.json; if they're not doing that, then they're broken.

That's right - the license file, with proper copyright, must be present on the repository and npm package (https://tldrlegal.com/license/mit-license). @ljharb

@ljharb you are probably right. But yet, many companies (like mine) want to play safe so don't allow us to use any code without proper licenses. Would be a shame to have to drop your lib just because of a missing license file. I hope you understand.

It’s not my lib :-)


Broken link on Deployment Overview Docs page

https://docs.flagsmith.com/deployment/overview
Link on "Deploy on Railway" button brings up a 404 page
Creating this issue here because the docs repository is archived and read only

OK I've made a new style Railway template but for some reason it's not building the Dockerfile. Have asked in the Railway Discord.

This seems to be working for me now.


Keybase on Windows is installed for current user only

Hi,
just like Linux, Windows is a multi user system, too. Please let the installer install Keybase for all users, so that an admin can install it once.

Right now, on every platform including Linux, Keybase only works for a single user at a time.  We haven't built multi-user support yet.

Multi-user support should work if KBFS is disabled, no?

How would one do that (on all platforms)?
BTW: Wouldn't it help to simply mount the top level directory into the user's home (/home/user/keybase) instead of the filesystem root (/keybase)?

@zanderz we install stuff silently on Windows all the time, using either Puppet or Salt w/o any changes in UAC. And in case the installation is managed by an admin, there shouldn't be silent updates anyway, since it's the responsibility of said admin to do this.

@heini I realize many admins in enterprise environments prefer to carefully control updates to installed software themselves, but Keybase clients don't yet offer this flexibility.

Yep, that's what this issue is all about ;-)


Behaviour of Y is affected

After enabling this plugin, Y yanks the complete line. However, after disabling this plugin Y yanks only the text after the cursor, which is the expected behaviour.
Neovim version: 0.10.1
luminate.nvim: d347e3997022ce96c695b919e3d0171e1ccea3d2

In my settings, regardless of whether my plugin is enabled or disabled, the Y behavior is the same as y$.
local illuminate = {
   "mei28/luminate.nvim",
  event = "VeryLazy",
  config = function()
    require 'luminate'.setup({
    })
  end,
}

local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not (vim.uv or vim.loop).fs_stat(lazypath) then
  local lazyrepo = "https://github.com/folke/lazy.nvim.git"
  local out = vim.fn.system {
    "git",
    "clone",
    "--filter=blob:none",
    "--branch=stable", -- latest stable release
    lazyrepo,
    lazypath,
  }
  if vim.v.shell_error ~= 0 then
    vim.api.nvim_echo({
      { "Failed to clone lazy.nvim:\n", "ErrorMsg" },
      { out,                            "WarningMsg" },
      { "\nPress any key to exit..." },
    }, true, {})
    vim.fn.getchar()
    os.exit(1)
  end
end
vim.opt.rtp:prepend(lazypath)

-- Lazy plugin spec: https://github.com/folke/lazy.nvim#-plugin-spec
local lazy = require("lazy")
lazy.setup({ illuminate, }, {})

I caught the issue with the following config in lazy.nvim-
{
  "mei28/luminate.nvim",
  keys = { "Y" },
  config = function()
    require("luminate").setup({ })
  end,
}

I used your settings and reproduced the problem. However, the issue is related to the lazy.nvim function. Therefore, even if you use keys = {'Y'} in another plugin, the problem may still occur

Is the issue related to the "Y" key specifically?
Is there another way to lazy load the plugin using key presses?

I used setting like follow, it works for me
  {
    'mei28/luminate.nvim',
    -- branch = 'fix#15',
    keys = { { 'u' }, { 'U' }, { '<C-r>' }, { 'p' }, { 'y' }, },
    config = function()
      require 'luminate'.setup({

      })
    end
  },

or it may works well as you want.
  keys = { { 'Y', function() vim.cmd('normal! y$') end } },

Thank you that works!!!


changing the consul_definition tags to an array

I have realised that the tags that I had written in the consul_defition are supposed to be an array so the example was partially wrong. Here is an update to fix it.

Current coverage is 49.34%

Merging #286 into master will increase coverage by +0.13% as of 829110f

@@            master    #286   diff @@
======================================
  Files            7       7
  Stmts          380     381     +1
  Branches         0       0
  Methods          0       0
======================================
+ Hit            187     188     +1
  Partial          0       0
  Missed         193     193

Review entire Coverage Diff as of 829110f

Powered by Codecov. Updated on successful CI builds.


Investigate Missing Grants in Nihms-Loader/Grant-Loader

Context from Slack channel:
https://eclipse-pass.slack.com/archives/C14JBAT8C/p1698843563652299
I checked the logs for the grant and nihms loader.
For the grant loader, no updates pulled.  Nothing has changed in coeus since 10-20-2023.  I don't know if this normal update frequency, or they are not updating coeus any longer since the launch of fibi (even though they said they would...).
For the nihms loader, here are the last couple of lines from the log:
INFO 12:17:58.982 (NihmsCsvProcessor) 8111 records were processed with 119 failures.
INFO 12:17:58.990 (NihmsTransformLoadService) Transform and load complete. Processed 3 files
8 replies

Tim
  [8 minutes ago](https://eclipse-pass.slack.com/archives/C14JBAT8C/p1698843718665879?thread_ts=1698843563.652299&cid=C14JBAT8C)
For some more context about that summary:
119 records with failures. From my analysis of the logs, it's likely only a handful of grants that are causing this.
Here is the list of grants that I identified that do not exist in pass_grants and are likely the cause of these errors:
https://eclipse-pass.slack.com/archives/C14JBAT8C/p1698758280894039?thread_ts=1698754903.720519&cid=C14JBAT8C

Tim
Of these 149 error records, 147 of them were missing grants. The unique missing grants are:
R01 DA011796
R55 AR050026
N01 HC095162
K24 AG056578
R01 HL049762
N01 HG065403
U01 AI068613
N01 AR092240
P01 CA093900
N01 AI040085
R37 GM028962
R21 MH122936
R21 NS127076
U01 AI069518
I know N01 HC095162 and K24 AG056578 were the grants that were missing from Fibi. Likely they are all missing from Fibi as well.
[@Russ Poetker](https://eclipse-pass.slack.com/team/U0562HERGHY)
 Do we have access to the fibi front end, or access to the DB to query for them?

I took a look through COEUS and found something interesting. While none of these were in teh system, a search for LIKE against the suffix found grants with a different prefix, matching the first letter of the desired prefix:
R01 DA011796 -> R37
R55 AR050026 -> R01
N01 HC095162
K24 AG056578
R01 HL049762
N01 HG065403 -> N01
U01 AI068613 -> UM1
N01 AR092240
P01 CA093900
N01 AI040085
R37 GM028962 -> R01
R21 MH122936 -> RF1
R21 NS127076
U01 AI069518 -> UM1

@jrmartino Thanks Jim! That is interesting that only the activity codes were different. Once this goes into ready for dev, I think I will talk to the owners of Fibi about this and see what their thoughts are. Perhaps they were entered incorrectly on the Fibi side of things.


Feature request to add custom data labels to bar chart bars

There are plugins to add labels to charts but what if custom hard coded data labels need to be added? These will be labels above each bar in the chart that are not the actual values. For example of value is below 20, have a label "Poor". if value is between 20 and 50 add data label "good" and above 50 add data label "great".

There is the official plugin chartjs-plugin-datalabels that provides a formatter option that allows to do exactly what you need. Labels don't even need to be hard-coded but can be calculated instead (see this jsfiddle). If you still have issues with data labels, please report your bugs/requests to the chartjs-plugin-datalabels repository instead.

Thank you. I updated the fiddle to include a line chart as well and want to suppress the labels for line only.
https://jsfiddle.net/vpyuydo1/2/
I will ask at the chartjs-plugin if this is not the right place.

Have a look at chartjs/chartjs-plugin-datalabels#20

Please check with this
https://emn178.github.io/chartjs-plugin-labels/samples/demo/


Logs aggregator dies/is stopped

What's your CLI version?
0.85.29
Description & steps to reproduce
I tried a kurtosis run today, and got this:
INFO[2023-11-19T13:17:16-03:00] No Kurtosis engine was found; attempting to start one...
INFO[2023-11-19T13:17:16-03:00] Starting the centralized logs components...
INFO[2023-11-19T13:17:16-03:00] Centralized logs components started.
INFO[2023-11-19T13:17:17-03:00] Successfully started Kurtosis engine
INFO[2023-11-19T13:17:17-03:00] Creating a new enclave for Starlark to run inside...
Error:  An error occurred running command 'run'
  Caused by: An error occurred calling the run function for command 'run'
  Caused by: An error occurred getting the enclave context for enclave ''
  Caused by: Unable to create new enclave with name ''
  Caused by: An error occurred creating an enclave with name ''
  Caused by: rpc error: code = Internal desc = stream terminated by RST_STREAM with error code: INTERNAL_ERROR

I dumped the engine logs, and found:
2023-11-19 13:17:17 WARN[2023-11-19T16:17:17Z][docker_kurtosis_backend.go:CreateLogsCollectorForEnclave] Logs aggregator exists but is not running. Instead container status is 'STOPPED'. This is unexpected as docker should have restarted the container automatically.
2023-11-19 13:17:17 WARN[2023-11-19T16:17:17Z][docker_kurtosis_backend.go:CreateLogsCollectorForEnclave] This can be fixed by restarting the engine using `kurtosis engine restart` and attempting to create the enclave again.
2023-11-19 13:17:17 2023/11/19 16:17:17 http2: panic serving <IP_ADDRESS>:36748: Propagate must be provided with a cause
2023-11-19 13:17:17 goroutine 24 [running]:
2023-11-19 13:17:17 golang.org/x/net/http2.(*serverConn).runHandler.func1()
2023-11-19 13:17:17     /home/circleci/go/pkg/mod/golang.org/x/net@v0.17.0/http2/server.go:2361 +0x140
2023-11-19 13:17:17 panic({0x135bb60, 0x1a0e0c0})
2023-11-19 13:17:17     /usr/local/go/src/runtime/panic.go:884 +0x20c
2023-11-19 13:17:17 github.com/kurtosis-tech/stacktrace.Propagate(...)
2023-11-19 13:17:17     /home/circleci/go/pkg/mod/github.com/kurtosis-tech/stacktrace@v0.0.0-20211028211901-1c67a77b5409/stacktrace.go:85
2023-11-19 13:17:17 github.com/kurtosis-tech/kurtosis/container-engine-lib/lib/backend_impls/docker/docker_kurtosis_backend.(*DockerKurtosisBackend).CreateLogsCollectorForEnclave(0x4000098d80, {0x1a30d50, 0x4000556100}, {0x40004950e0, 0x20}, 0x2?, 0x0?)
2023-11-19 13:17:17     /home/circleci/project/container-engine-lib/lib/backend_impls/docker/docker_kurtosis_backend/docker_kurtosis_backend.go:424 +0x238
2023-11-19 13:17:17 github.com/kurtosis-tech/kurtosis/container-engine-lib/lib/backend_impls/docker/docker_kurtosis_backend.(*DockerKurtosisBackend).CreateEnclave(0x4000098d80, {0x1a30d50, 0x4000556100}, {0x40004950e0, 0x20}, {0x40001455b0, 0xe})
2023-11-19 13:17:17     /home/circleci/project/container-engine-lib/lib/backend_impls/docker/docker_kurtosis_backend/docker_kurtosis_backend_enclave_functions.go:152 +0xc4c
2023-11-19 13:17:17 github.com/kurtosis-tech/kurtosis/container-engine-lib/lib/backend_impls/metrics_reporting.(*MetricsReportingKurtosisBackend).CreateEnclave(0x0?, {0x1a30d50?, 0x4000556100?}, {0x40004950e0, 0x20}, {0x40001455b0?, 0x40004bac60?})
2023-11-19 13:17:17     /home/circleci/project/container-engine-lib/lib/backend_impls/metrics_reporting/metrics_reporting_kurtosis_backend.go:114 +0x3c
2023-11-19 13:17:17 github.com/kurtosis-tech/kurtosis/engine/server/engine/enclave_manager.(*EnclaveCreator).CreateEnclave(0x40001c2800, {0x1a30d50, 0x4000556100}, {0x0, 0x0}, 0x0?, {0x40001455b0, 0xe}, {0x4000331096, 0x2}, ...)
2023-11-19 13:17:17     /home/circleci/project/engine/server/engine/enclave_manager/enclave_creator.go:57 +0xc4
2023-11-19 13:17:17 github.com/kurtosis-tech/kurtosis/engine/server/engine/enclave_manager.(*EnclaveManager).CreateEnclave(0x4000149900, {0x1a30d50, 0x4000556100}, {0x4000331089, 0x7}, {0x0, 0x0}, 0x0?, {0x0, 0x0}, ...)
2023-11-19 13:17:17     /home/circleci/project/engine/server/engine/enclave_manager/enclave_manager.go:180 +0x380
2023-11-19 13:17:17 github.com/kurtosis-tech/kurtosis/engine/server/engine/server.(*EngineConnectServerService).CreateEnclave(0x4000132620, {0x1a30d50, 0x4000556100}, 0x22ef8?)
2023-11-19 13:17:17     /home/circleci/project/engine/server/engine/server/engine_connect_server_service.go:103 +0x1c0
2023-11-19 13:17:17 connectrpc.com/connect.NewUnaryHandler[...].func1({0x1a35830, 0x4000132e70})
2023-11-19 13:17:17     /home/circleci/go/pkg/mod/connectrpc.com/connect@v1.11.1/handler.go:52 +0x14c
2023-11-19 13:17:17 connectrpc.com/connect.NewUnaryHandler[...].func2({0xffff831585f8, 0x400054a040})
2023-11-19 13:17:17     /home/circleci/go/pkg/mod/connectrpc.com/connect@v1.11.1/handler.go:81 +0x294
2023-11-19 13:17:17 connectrpc.com/connect.(*Handler).ServeHTTP(0x40001c1080, {0x1a24040, 0x4000550018}, 0x400055a200)
2023-11-19 13:17:17     /home/circleci/go/pkg/mod/connectrpc.com/connect@v1.11.1/handler.go:239 +0x628
2023-11-19 13:17:17 github.com/kurtosis-tech/kurtosis/api/golang/engine/kurtosis_engine_rpc_api_bindings/kurtosis_engine_rpc_api_bindingsconnect.NewEngineServiceHandler.func1({0x1a24040, 0x4000550018}, 0x400055a200)
2023-11-19 13:17:17     /home/circleci/project/api/golang/engine/kurtosis_engine_rpc_api_bindings/kurtosis_engine_rpc_api_bindingsconnect/engine_service.connect.go:269 +0x220
2023-11-19 13:17:17 net/http.HandlerFunc.ServeHTTP(0x4000501860?, {0x1a24040?, 0x4000550018?}, 0x0?)
2023-11-19 13:17:17     /usr/local/go/src/net/http/server.go:2109 +0x38
2023-11-19 13:17:17 net/http.(*ServeMux).ServeHTTP(0x40005019a8?, {0x1a24040, 0x4000550018}, 0x400055a200)
2023-11-19 13:17:17     /usr/local/go/src/net/http/server.go:2487 +0x140
2023-11-19 13:17:17 golang.org/x/net/http2.(*serverConn).runHandler(0x40001f00a0?, 0x1a30df8?, 0x40004a4150?, 0x18694a0?)
2023-11-19 13:17:17     /home/circleci/go/pkg/mod/golang.org/x/net@v0.17.0/http2/server.go:2368 +0xc4
2023-11-19 13:17:17 created by golang.org/x/net/http2.(*serverConn).scheduleHandler
2023-11-19 13:17:17     /home/circleci/go/pkg/mod/golang.org/x/net@v0.17.0/http2/server.go:2303 +0x22c

I checked, and my logs aggregator was indeed stopped, though I'm not sure why:

I also have a logs-collector somehow hanging around, even though I don't have any enclaves running:
$ kurtosis enclave ls
UUID   Name   Status   Creation Time

This is the output of docker container inspect kurtosis-logs-aggregator:
[
    {
        "Id": "ebaa0ce2ae972c613cfe03403cae2040ef4f317968ca5b2faacd3c3ff23f961a",
        "Created": "2023-11-17T08:54:59.858197634Z",
        "Path": "/bin/sh",
        "Args": [
            "-c",
            "printf '\n[sources.\"fluent_bit\"]\ntype = \"fluent\"\naddress = \"<IP_ADDRESS>:9714\"\n\n[sinks.uuid_file]\ntype = \"file\"\ninputs = [\"fluent_bit\"]\npath = \"/var/log/kurtosis/%%Y/%%V/{{ enclave_uuid }}/{{ service_uuid }}.json\"\t\nencoding.codec = \"json\"\nbuffer.when_full = \"block\"\n' \u003e /etc/vector/vector.toml \u0026\u0026 /usr/bin/vector -c=/etc/vector/vector.toml"
        ],
        "State": {
            "Status": "exited",
            "Running": false,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 0,
            "ExitCode": 137,
            "Error": "",
            "StartedAt": "2023-11-17T08:55:00.116585384Z",
            "FinishedAt": "2023-11-18T15:36:40.796399588Z"
        },
        "Image": "sha256:ec83552fc89eacc0af3a4d1576523a74f8b31b5931aa560b90423dcd3c6e1355",
        "ResolvConfPath": "/var/lib/docker/containers/ebaa0ce2ae972c613cfe03403cae2040ef4f317968ca5b2faacd3c3ff23f961a/resolv.conf",
        "HostnamePath": "/var/lib/docker/containers/ebaa0ce2ae972c613cfe03403cae2040ef4f317968ca5b2faacd3c3ff23f961a/hostname",
        "HostsPath": "/var/lib/docker/containers/ebaa0ce2ae972c613cfe03403cae2040ef4f317968ca5b2faacd3c3ff23f961a/hosts",
        "LogPath": "/var/lib/docker/containers/ebaa0ce2ae972c613cfe03403cae2040ef4f317968ca5b2faacd3c3ff23f961a/ebaa0ce2ae972c613cfe03403cae2040ef4f317968ca5b2faacd3c3ff23f961a-json.log",
        "Name": "/kurtosis-logs-aggregator",
        "RestartCount": 0,
        "Driver": "overlay2",
        "Platform": "linux",
        "MountLabel": "",
        "ProcessLabel": "",
        "AppArmorProfile": "",
        "ExecIDs": null,
        "HostConfig": {
            "Binds": [
                "kurtosis-logs-storage:/var/log/kurtosis/"
            ],
            "ContainerIDFile": "",
            "LogConfig": {
                "Type": "json-file",
                "Config": {}
            },
            "NetworkMode": "default",
            "PortBindings": {},
            "RestartPolicy": {
                "Name": "on-failure",
                "MaximumRetryCount": 0
            },
            "AutoRemove": false,
            "VolumeDriver": "",
            "VolumesFrom": null,
            "ConsoleSize": [
                0,
                0
            ],
            "CapAdd": [],
            "CapDrop": null,
            "CgroupnsMode": "private",
            "Dns": null,
            "DnsOptions": null,
            "DnsSearch": null,
            "ExtraHosts": [],
            "GroupAdd": null,
            "IpcMode": "private",
            "Cgroup": "",
            "Links": null,
            "OomScoreAdj": 0,
            "PidMode": "",
            "Privileged": false,
            "PublishAllPorts": false,
            "ReadonlyRootfs": false,
            "SecurityOpt": null,
            "UTSMode": "",
            "UsernsMode": "",
            "ShmSize": 67108864,
            "Runtime": "runc",
            "Isolation": "",
            "CpuShares": 0,
            "Memory": 0,
            "NanoCpus": 0,
            "CgroupParent": "",
            "BlkioWeight": 0,
            "BlkioWeightDevice": null,
            "BlkioDeviceReadBps": null,
            "BlkioDeviceWriteBps": null,
            "BlkioDeviceReadIOps": null,
            "BlkioDeviceWriteIOps": null,
            "CpuPeriod": 0,
            "CpuQuota": 0,
            "CpuRealtimePeriod": 0,
            "CpuRealtimeRuntime": 0,
            "CpusetCpus": "",
            "CpusetMems": "",
            "Devices": null,
            "DeviceCgroupRules": null,
            "DeviceRequests": null,
            "MemoryReservation": 0,
            "MemorySwap": 0,
            "MemorySwappiness": null,
            "OomKillDisable": null,
            "PidsLimit": null,
            "Ulimits": null,
            "CpuCount": 0,
            "CpuPercent": 0,
            "IOMaximumIOps": 0,
            "IOMaximumBandwidth": 0,
            "MaskedPaths": [
                "/proc/asound",
                "/proc/acpi",
                "/proc/kcore",
                "/proc/keys",
                "/proc/latency_stats",
                "/proc/timer_list",
                "/proc/timer_stats",
                "/proc/sched_debug",
                "/proc/scsi",
                "/sys/firmware"
            ],
            "ReadonlyPaths": [
                "/proc/bus",
                "/proc/fs",
                "/proc/irq",
                "/proc/sys",
                "/proc/sysrq-trigger"
            ],
            "Init": false
        },
        "GraphDriver": {
            "Data": {
                "LowerDir": "/var/lib/docker/overlay2/eeaa3853b171c6f86b7b1fa3c1893bb5d21e9ca5ee72fc9dd4d6bf7ab9a1f84a-init/diff:/var/lib/docker/overlay2/73a73c54f4733e3093b694a5477e7d1cc8ec08b38ec33ffc6cadaff24554b3f4/diff:/var/lib/docker/overlay2/0649dd28395f8fcd43911f7fe784e1424786f892c5d3ec21cd33d75b51b491e5/diff:/var/lib/docker/overlay2/c1f399053d8ca7a31e3b1156ab6b8115ded5d353a375c601927295de44fe64ae/diff:/var/lib/docker/overlay2/bcb7c67adf3f86995fddd2b45f36b34a2bc43595fe3bb7e48c34f96c4d4bd077/diff:/var/lib/docker/overlay2/fcd0f8d8397e8d2d3653911c289eda57bee2a2bd7222539e2da5a76a06a4a808/diff:/var/lib/docker/overlay2/9c880fe16116762d9d91885e8c6490bb21f350849b88079a22e2f587108762b5/diff:/var/lib/docker/overlay2/04b6c1d99cf7535684fc7333499d7adbc5e8d72401086835fc1c6715f0cc013d/diff",
                "MergedDir": "/var/lib/docker/overlay2/eeaa3853b171c6f86b7b1fa3c1893bb5d21e9ca5ee72fc9dd4d6bf7ab9a1f84a/merged",
                "UpperDir": "/var/lib/docker/overlay2/eeaa3853b171c6f86b7b1fa3c1893bb5d21e9ca5ee72fc9dd4d6bf7ab9a1f84a/diff",
                "WorkDir": "/var/lib/docker/overlay2/eeaa3853b171c6f86b7b1fa3c1893bb5d21e9ca5ee72fc9dd4d6bf7ab9a1f84a/work"
            },
            "Name": "overlay2"
        },
        "Mounts": [
            {
                "Type": "volume",
                "Name": "kurtosis-logs-storage",
                "Source": "/var/lib/docker/volumes/kurtosis-logs-storage/_data",
                "Destination": "/var/log/kurtosis",
                "Driver": "local",
                "Mode": "z",
                "RW": true,
                "Propagation": ""
            }
        ],
        "Config": {
            "Hostname": "ebaa0ce2ae97",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": false,
            "OpenStdin": true,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],
            "Cmd": [
                "-c",
                "printf '\n[sources.\"fluent_bit\"]\ntype = \"fluent\"\naddress = \"<IP_ADDRESS>:9714\"\n\n[sinks.uuid_file]\ntype = \"file\"\ninputs = [\"fluent_bit\"]\npath = \"/var/log/kurtosis/%%Y/%%V/{{ enclave_uuid }}/{{ service_uuid }}.json\"\t\nencoding.codec = \"json\"\nbuffer.when_full = \"block\"\n' \u003e /etc/vector/vector.toml \u0026\u0026 /usr/bin/vector -c=/etc/vector/vector.toml"
            ],
            "Image": "timberio/vector:0.31.0-debian",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": [
                "/bin/sh"
            ],
            "OnBuild": null,
            "Labels": {
                "com.kurtosistech.app-id": "kurtosis",
                "com.kurtosistech.container-type": "kurtosis-logs-aggregator"
            }
        },
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "90b24aa1e00d5a26d6cf689794d149f8732b2ae474a7382f496eb65a8f79283d",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {},
            "SandboxKey": "/var/run/docker/netns/90b24aa1e00d",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "",
            "Gateway": "",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "",
            "IPPrefixLen": 0,
            "IPv6Gateway": "",
            "MacAddress": "",
            "Networks": {
                "bridge": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": null,
                    "NetworkID": "8662e507c238504d517d3e5496325a3bdaea893a404df2b8d29602fdf219eea8",
                    "EndpointID": "",
                    "Gateway": "",
                    "IPAddress": "",
                    "IPPrefixLen": 0,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "",
                    "DriverOpts": null
                }
            }
        }
    }
]

And the container logs:
2023-11-17 05:55:00 2023-11-17T08:55:00.121833Z  INFO vector::app: Log level is enabled. level="vector=info,codec=info,vrl=info,file_source=info,tower_limit=info,rdkafka=info,buffers=info,lapin=info,kube=info"
2023-11-17 05:55:00 2023-11-17T08:55:00.123136Z  INFO vector::app: Loading configs. paths=["/etc/vector/vector.toml"]
2023-11-17 05:55:00 2023-11-17T08:55:00.125273Z  INFO vector::topology::running: Running healthchecks.
2023-11-17 05:55:00 2023-11-17T08:55:00.125364Z  INFO vector: Vector has started. debug="false" version="0.31.0" arch="aarch64" revision="0f13b22 2023-07-06 13:52:34.591204470"
2023-11-17 05:55:00 2023-11-17T08:55:00.125370Z  INFO vector::app: API is disabled, enable by setting `api.enabled` to `true` and use commands like `vector top`.
2023-11-17 05:55:00 2023-11-17T08:55:00.125380Z  INFO vector::topology::builder: Healthcheck passed.
2023-11-17 05:55:00 2023-11-17T08:55:00.125612Z  INFO source{component_kind="source" component_id=fluent_bit component_type=fluent component_name=fluent_bit}: vector::sources::util::net::tcp: Listening. addr=<IP_ADDRESS>:9714

Desired behavior
I never get this error; Kurtosis correctly manages the logs-aggregator
What is the severity of this bug?
Critical; I am blocked and Kurtosis is unusable for me because of this bug.
What area of the product does this pertain to?
CLI: the Command Line Interface

Confirmed that it's not a problem of switching contexts; I just switched to my cloud context and back again and the logs-aggregator was started along with the engine

(though these silly logs-collectors are still hanging around..)

An interesting observation is that the status codes of the exited containers are 137. According to chat gpt:
An exit status of 137 typically indicates that a process was terminated by a signal. In the context of Docker, specifically, this often happens when a container is killed due to exceeding its allocated memory limit.
This could further support that something is being resource leaked.

Update - this likely wasn't being caused by the log collector memory leak. Going to look deeper into memory limits on the logs aggregator.


[QUERY] - VirtualMachines.GetByIdAsync() equivalent for Arc VMs?

Query/Question
Hi!
Using the newest releases of Azure Fluent and Azure Resource management SDKs.  Is there an equivalent of the VM.GetByIdAsync() endpoint that works with ARC VMs?  When I try with either a Windows or a Linux ARC VM, I get null or resource not found errors.
Thanks!
Environment:

Name and version of the Library package used: [e.g. Azure.Storage.Blobs 12.2.0]
Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): [e.g. Azure AppService or Windows 10 .NET Framework 4.8]
IDE and version : [e.g. Visual Studio 16.3]

Found the answer, these can be retrieved with the Microsoft.Azure.Management.HybridCompute.Machines() operator from that namespace.  It can also be retrieved with ResourceManager using Resources.GetById() as well;


KDC_ERR_KEY_EXPIRED

This page says KDC_ERR_KEY_EXPIRED cannot occur in event 4768 - this is wrong. If you logon to a terminal server, diconnect you session and change you password you will find Events with Event-ID 4768 and Result Code 0x17 after a while in security eventlog.

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

ID: 94cebf1d-b16d-4ddc-b532-be829b858938
Version Independent ID: 3707f457-98d5-e5b3-c749-99afe0d6d495
Content: 4768(S, F) A Kerberos authentication ticket (TGT) was requested. (Windows 10) - Windows security
Content Source: windows/security/threat-protection/auditing/event-4768.md
Product: w10
Technology: windows
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@cscherb Could you share such an event? It's strange that looking at the article about event 4768 it's clearly stated that
This event doesn't generate for Result Codes: 0x10, 0x17 and 0x18. Event “4771: Kerberos pre-authentication failed.” generates instead.


Haltere nerve and dorsal metathoracic nerve are synonyms for each other

There are two terms for what appear to be exact synonyms of the other for haltere nerve and dorsal metathoracic nerve.

I completely support this proposal, and note that "haltere nerve' is already already a synonym for dorsal metahoracic nerve.


fix(di): Remove try catch on importFiles

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

v6.58.1
GitHub release

Your semantic-release bot :package::rocket:


Disambiguate To Dos from todos

todo is a Portuguese word. The reference to the To Do items should be differentiated in some way, I suggest through capitalization.
This only changes the translation file, no other changes required.

Changes on the translations should only be created over https://i18n.meetfranz.com/. See #1141, https://github.com/meetfranz/franz/pull/1203#issuecomment-457246994 and https://github.com/meetfranz/franz/issues/39


Migrate from rocket.rs to axum

What/Why
Kellnr was started more than three years ago. Rocket.rs was one of the most promising web frameworks at that time. Unfortunatly the development stopped. Axum emerged as a new popular framework with it's roots in the tokio ecosystem, which makes it a perfect fit for Kellnr, as tokio is already heavily used.
To Do
Kellnr uses rocket.rs for routing, authentication and serving static files. All of this has to be migrated. The list below gives an overview of what has to be done.
The behavior should not change to make the migration as smooth as possible. For nearly all APIs multiple corresponding tests exist.
Contribute
The branch migrate-to-axum is used. If you intend to help with the migration, fork the project and use this branch as the base for your work. Please check the migrated APIs below, such that it is clear what is still missing and work is not done multiple times.
Root - UI
The root serves mostly UI related APIs.
API

[x] ui::kellnr_version
[x] ui::crates
[x] registry::kellnr_api::me
[x] ui::search
[x] ui::statistic
[x] web_ui::settings::settings
[x] ui::crates_data
[x] ui::cratesio_data
[x] ui::delete
[x] ui::build_rustdoc

Tests

[x] ui::kellnr_version
[x] ui::crates
[x] registry::kellnr_api::me
[x] ui::search
[x] ui::statistic
[x] web_ui::settings::settings
[x] ui::crates_data
[x] ui::cratesio_data
[x] ui::delete
[x] ui::build_rustdoc

Static File Server
This route serve static file content, e.g. the user interface for Kellnr.
API

[x] "/" -> serves "./static"

User
The user API manages all things related to Kellnr users, for example creating a user or adding a authentication token.
API

[x] user::login
[x] user::logout
[x] user::change_pwd
[x] user::add
[x] user::delete
[ ] user::delete_forbidden (still needed?)
[x] user::reset_pwd
[x] user::add_token
[x] user::delete_token
[x] user::list_token
[x] user::list_users
[x] user::login_state

Tests

[x] user::login
[x] user::logout
[x] user::change_pwd
[x] user::add
[x] user::delete
[ ] user::delete_forbidden (still needed?)
[x] user::reset_pwd
[x] user::add_token
[x] user::delete_token
[x] user::list_token
[x] user::list_users
[x] user::login_state

Crates
The API for the crates are implemted under /api/v1/crates. This is the heart of Kellnr and allows cargo to push and pull crates.
API

[x] index::kellnr_prefetch_api::prefetch_kellnr
[x] index::kellnr_prefetch_api::prefetch_len2_kellnr
[x] index::kellnr_prefetch_api::config_kellnr
[x] registry::kellnr_api::download
[x] registry::kellnr_api::publish
[x] registry::kellnr_api::yank
[x] registry::kellnr_api::unyank
[x] registry::kellnr_api::search
[x] registry::kellnr_api::list_owners
[x] registry::kellnr_api::add_owner
[x] registry::kellnr_api::remove_owner

Tests

[x] index::kellnr_prefetch_api::prefetch_kellnr
[x] index::kellnr_prefetch_api::prefetch_len2_kellnr
[x] index::kellnr_prefetch_api::config_kellnr
[x] registry::kellnr_api::download
[x] registry::kellnr_api::publish
[x] registry::kellnr_api::yank
[x] registry::kellnr_api::unyank
[x] registry::kellnr_api::search
[x] registry::kellnr_api::list_owners
[x] registry::kellnr_api::add_owner
[x] registry::kellnr_api::remove_owner

Crates.io
Kellnr can proxy and cache crates.io, as such it dublicates the crates API from above for crates.io
API

[x] index::cratesio_prefetch_api::prefetch_cratesio
[x] index::cratesio_prefetch_api::prefetch_len2_cratesio
[x] index::cratesio_prefetch_api::config_cratesio
[x] registry::cratesio_api::download
[x] registry::cratesio_api::search
[x] ui::delete_cratesio_index

Tests

[x] index::cratesio_prefetch_api::prefetch_cratesio
[x] index::cratesio_prefetch_api::prefetch_len2_cratesio
[x] index::cratesio_prefetch_api::config_cratesio
[x] registry::cratesio_api::download
[x] registry::cratesio_api::search
[x] ui::delete_cratesio_index

Not Found
Forward all not found pages to the vue.js router.

[x] "not found" -> "/static/index.html" -> The vue.js router will take over from here

In case it's not known already, ServeDir from tower-http is the most common solution for serving static files from disk.
There is a known issue for automatic redirects (/static/foo to /static/foo/ if foo is a directory in the ServeDir disk directory), if enabled and ServeDir is nested using nest_service.
It sounds like you want anything that's not a (known?) API route to go to static file serving though? In that case the ServeDir should be added as a .fallback_service() on the router, and the issue linked above is irrelevant. There's just one extra thing to note: you need to set an explicit fallback on the api router if you don't want unknown /api routes to go to ServeDir (since by default fallbacks are inherited by nested routers).

All APIs are ported and all test work with axum.
Next:

[ ] Remove all rocket references
[ ] Test all functionality manually for cases that miss a test

All test run successfully. Port to axum finished.


Export "Review endpoint utterances" and align to intend

Is it possible to export the utterances under "review endpoint utterances" in luis portal? If not, that would be a nice one as of the following user stories:

As an Analyst, I want to export endpoint utterances LUIS is not sure about, so I can dispatch it in external tools like excel

As an Analyst, I want to align intends for reviewed endpoint utterances luis wasn't sure about, so I can improve the model in my day to day workflow using my own tool stack, like excel.

If I missed this possibility, please guide me towards the right commands.
Thanks

Yes. This is possible today using the LUIS CLI.
You can use the >luis suggest command to get the list of utterances listed under "review endpoint utterances" section.

You can use luis list intents command to get the list of intents in your app and the associated intentId.
You can use the intentId to get endpoint utterances per intentId

> luis list intents -h
LUIS Command Line Interface - © 2018 Microsoft Corporation

Gets information about the intent models.

Usage:
luis list intents --skip <integer> --take <integer>

Command arguments are:
 --appId <string> (required)             The application ID.
 --versionId <string> (required)         The version ID.
 --skip <integer>                        The number of entries to skip. Default value is 0.
 --take <integer>                        The number of entries to return. Maximum page size is 500.
                                         Default is 100.

Configuration and Overrides:
 --appId                                 Specifies the public LUIS application id. Overrides the
                                         .luisrc value and the LUIS_APP_ID environment variable.
 --authoringKey                          Specifies the LUIS authoring  key (from luis.ai portal user
                                         settings page). Overrides the .luisrc value and the
                                         LUIS_AUTHORING_KEY environment variable.
 --versionId                             Specifies the version id. Overrides the .luisrc value and
                                         the LUIS_VERSION_ID environment variable.
 --endpointBasePath                      Specifies the base URI for all requests. Overrides the
                                         .luisrc value and the LUIS_ENDPOINT_BASE_PATH environment
                                         variable.

Global Arguments:
 --help,    -h                           Prints this help file.
 --version, -v                           Prints the version of this cli tool
 --!                                     Dumps all documented commands to the console with
                                         descriptions

>luis suggest intents -h
LUIS Command Line Interface - © 2018 Microsoft Corporation

Suggests examples that would improve the accuracy of the intent model.

Usage:
luis suggest intents --intentId <string> --take <integer>

Command arguments are:
 --appId <string> (required)             The application ID.
 --versionId <string> (required)         The version ID.
 --intentId <string> (required)          The intent classifier ID.
 --take <integer>                        The number of entries to return. Maximum page size is 500.
                                         Default is 100.

Configuration and Overrides:
 --appId                                 Specifies the public LUIS application id. Overrides the
                                         .luisrc value and the LUIS_APP_ID environment variable.
 --authoringKey                          Specifies the LUIS authoring  key (from luis.ai portal user
                                         settings page). Overrides the .luisrc value and the
                                         LUIS_AUTHORING_KEY environment variable.
 --versionId                             Specifies the version id. Overrides the .luisrc value and
                                         the LUIS_VERSION_ID environment variable.
 --endpointBasePath                      Specifies the base URI for all requests. Overrides the
                                         .luisrc value and the LUIS_ENDPOINT_BASE_PATH environment
                                         variable.

Global Arguments:
 --help,    -h                           Prints this help file.
 --version, -v                           Prints the version of this cli tool
 --!                                     Dumps all documented commands to the console with
                                         descriptions


Update rules-bad.yml for following error in CI

https://github.com/prometheus/prometheus/actions/runs/6376911164/job/17304643297#step:4:1059
(Please mention this under hacktoberfest)
Which says
 FAILED: ./testdata/rules-bad.yml: group "alerts", rule 1, "InstanceDown": annotation "summary": template: __alert_InstanceDown:1: undefined variable "$label"

Thanks for looking, but this is a test to check that a bad rule results in a fail.
The tests now fail with:
  --- FAIL: TestCheckRulesWithRuleFiles/rules-bad (0.00s)
        main_test.go:543:
            	Error Trace:	/__w/prometheus/prometheus/cmd/promtool/main_test.go:543
            	Error:      	Not equal:
            	            	expected: 1
            	            	actual  : 0
            	Test:       	TestCheckRulesWithRuleFiles/rules-bad

The diagnostic output you see would help someone if this was a real failure, but we expect this to fail and are testing for that.

@dgl
Thanks for update
I'm looking forward to contribute is there any test which is not added yet so I can help to add it
Let me know if you have anything for me to work on


Update dynamodb to 2.16.52

Updates software.amazon.awssdk:dynamodb from 2.16.17 to 2.16.52.
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 = "software.amazon.awssdk", artifactId = "dynamodb" } ]

labels: library-update, semver-patch

Superseded by #1080.


Invalid pending activity retrieval issue for a given device id in EMM 2.1.0

This is regarding the support-1.1.2-XXX-Phase1 branch.
Even if a record already exists in the DM_ENROLMENT_OP_MAPPING for the same enrollment_id with pending status for a given device, a record is inserted to the DM_OPERATION table but not to the DM_ENROLMENT_OP_MAPPING once the /admin/devices/applications API is invoked. This is causing the "No activity can be found upon the provided activity id <ACTIVITY_ID>" error when invoking the <ACTIVITY_ID>/applications.

This is fixed in the latest version of the IoT server.