Use date format expected by Rave

This PR updates the date formatter to use the proper format expected by Rave. I tested a submission and verified that it worked correctly.
Currently the ORKDateQuestionResult results also use the same date time formatter - if a consumer wants a different format they will have to alter our ORKQuestionResult (MORK) category. I think we should eventually either 1. decide on a separate format and add it ourselves or 2. add an interface for specifying custom date formatters.
I've also updated the example to use the authenticationJSON method.
Executed 4 tests, with 0 failures (0 unexpected) in 0.026 (0.030) seconds

This guy is having trouble at the end of ViewController.m:
ORKScaleAnswerFormat *scaleFormat = [[ORKScaleAnswerFormat alloc] initWithMaximumValue:10 minimumValue:1 step:1 defaultValue:5];

as the method signature in ResearchKit is different.  It is now:
- (instancetype)initWithMaximumValue:(NSInteger)maximumValue
                        minimumValue:(NSInteger)minimumValue
                        defaultValue:(NSInteger)defaultValue
                                step:(NSInteger)step;

(I believe I have this fixed in one of my other PRs)

Huh, I may be running an older version of ResearchKit - will investigate and update.

LGTM!


Simple typos

The words with accents already were in the pt-br file before.
I removed all the accents, can you verify now?
Thanks

Many languages uses different kind of accents, thats why some help us to ~remove~ replace accents form incoming input in validation


MM-29954 Disable sticky sidebar headings on Firefox and Safari and fix position of NEW badge

Turns out both of these were broken by different PRs
Ticket Link
https://mattermost.atlassian.net/browse/MM-29954

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

Trying to auto merge this PR.

Pull Request successfully merged
SHA: 4c8d23ccf9d3e11348777863c2d7ec90b780e280

Cherry pick is scheduled.


Ability to see debug logs of force:package:version:create

Is your feature request related to a problem? Please describe.
I have run into an obscure bug in SFDX Package Creation where a particular test is failing only on package version create, but building the package without --codecoverage works fine and then on deploying to a test scratch org, all tests pass. Unfortunately, a package without --codecoverage cannot be promoted. This test works fine in scratch orgs with multiple configurations (Person accounts on/off, multicurrency on/off). Unfortunately, I cannot see the debug logs of a package creation process so I don't know what is triggering the error. Weirdly enough, another test which does the same thing passes the test on package create.
What are you trying to do
Package version create failing tests, same tests pass in all other circumstances.
Describe the solution you'd like
The ability to see a full debug log of force:package:verison:create to better understand why the process is failing.
Describe alternatives you've considered
Removing the test solves the problem but leaves us with uncovered code. Adding --loglevel=TRACE does not show debug logs.
Additional context
Add any other context or screenshots about the feature request here.

I like this idea, but without changing tooling API by salesforce it cannot be added to the sfdx cli. sfdx just create Package2VersionCreateRequest and then polling to check status. If status equals Error then it returns data from the Package2VersionCreateRequestError object

@rnavroze - What you're experiencing might be something that the "Unpackaged Metadata" pilot could help with.
https://releasenotes.docs.salesforce.com/en-us/winter21/release-notes/rn_sfdx_packaging_path_unpackaged_md.htm
As for the feature request for log visibility on package:version:create, I'd recommend reposting your suggestion in one of the packaging-related community groups for better visibility to the packaging team.

Managed Packaging (Partner Community)
Unlocked Packaging (Trailblazer Community)

I'll mention this to the PM as well.

@VivekMChawla Thank you for the suggestion. I eventually figured out through a lot of trial and error that it was a race condition where a record being created by a trigger was being deleted by the test, which worked fine in all environments but somehow not the package build environment.
I will post the suggestions there as well as this is certainly a useful feature for situations like this.

I worked around this by creating a new scratch org, not change any setting in the org and run tests against this org

We've run into numerous examples of this behaviour (tests only fail when creating a new package version).
Typically the failures seem to be a result of a test running in a package that is not aware of content from a package it depends on.
For example, let's say you have Packages A and B, with B depending on A. In Package A you have defined some additional Task status values, some of which indicate the task is closed. If you have a test in Package B that sets the status of a Task to one of these additional closed values and then query based on IsClosed, you will not get a result because in the context of the test in Package B the additional status values do not exist. A similar behaviour happens with custom permissions.
We have even developed an isRunningCodeCoverageTest static method that we use to ensure certain asserts pass (or to bypass certain asserts). The method checks if the email of the current user is<EMAIL_ADDRESS>


Possible to improve English and German pronunciation?

NVIDIA NeMo (ByT5 G2P and G2P-Conformer):

NVIDIA NeMo provides grapheme-to-phoneme models for various languages, including German.

The ByT5 G2P model is based on a neural network and can handle out-of-vocabulary words (OOV) and heteronyms (words with the same spelling but different pronunciations).

The G2P-Conformer model is a non-autoregressive CTC model that is faster during inference.

These models allow you to enforce desired pronunciations by providing a phonetic transcript of the input.
You can train and evaluate these models using manifest files containing grapheme and phoneme pairs

Is it possible to do this using NeMoOnnxSharp?

It supports both German TTS/ASR. See this
https://github.com/kaiidams/NeMoOnnxSharp/blob/ad2ffe375e525bb63c59c9b1cd5154afe70351a0/NeMoOnnxSharp.Example/Program.cs#L39

I have use the code for German
Here is the feedback

The volume of TTS for German is softer than when using Microsoft Speech.

Second,
I have seen Mel and MFCC code. I wonder if these codes can be repurposed for German audio and eventually to extract German phonemes from German Audio
In the entiere internet, hardly anything like this.  Even Wav2ToVec2 is not often shown how to work with the German langauge.
Can you do something about this?

It supports both German TTS/ASR. See this

I have tried TTS/ASR for German: My interest is extraction of German Phonemes from German Audio

In case of German, their pronunciation is not ambiguous. Why do you need a phonemizer?
In case of English, NeMo FastPitch was trained with a phonemizer which translates all but ambiguous words, and FastPitch can handle ambiguous words in many cases.

FastPitch is a text-to-speech (TTS) model developed by NVIDIA. It's a fully-parallel transformer architecture with prosody control over pitch and individual phoneme duration¹. Here are some key features:

Fully-Parallel Architecture: Unlike traditional TTS models that generate speech sequentially, FastPitch generates speech in parallel, which makes it much faster¹.
Prosody Control: FastPitch allows for control over the pitch and duration of individual phonemes, which can make the generated speech more expressive and engaging¹.
Transformer-Based: FastPitch is based on the Transformer architecture, which is known for its efficiency and scalability¹.
Integration with NeMo: FastPitch can be trained or fine-tuned using NVIDIA's NeMo framework, a generative AI framework built for working on large language models (LLMs), multimodal models (MM), automatic speech recognition (ASR), and text-to-speech synthesis (TTS)².

FastPitch is used for generating mel spectrograms from text, which can then be converted to audio using a vocoder¹. It's trained on the LJSpeech dataset sampled at 22050Hz and has been tested on generating female English voices with an American accent¹. Please note that this model works well with vocoders that were trained on 22050Hz data¹.
Source: Conversation with Bing, 3/30/2024
(1) TTS En FastPitch | NVIDIA NGC. https://catalog.ngc.nvidia.com/orgs/nvidia/teams/nemo/models/tts_en_fastpitch.
(2) GitHub - NVIDIA/NeMo: NeMo: a framework for generative AI. https://github.com/NVIDIA/NeMo.
(3) Google Colab. https://colab.research.google.com/github/NVIDIA/NeMo/blob/stable/tutorials/tts/FastPitch_MixerTTS_Training.ipynb.
(4) undefined. https://arxiv.org/abs/2006.06873.

Is there GermanG2P.cs in NeMoOnnxSharp?
FastPitch of NeMo uses a phonemizer for English but doesn't use for German. NeMoOnnxSharp doesn't contain German phonemizer.


Support progress bars for read_opus()

2b78e6c bases {progressr}, which almost universally works for all iterators in R.

WIP; does not yet work how I intend it to do.

I need to implement the progress feature for the inner read sequence (within read_opus_lapply())

The parallel chunking arg would be best set using options().

feature progress bar for parallel reads


Add pkgchk tool and integrate into CI

pkgchk will verify the following things:

package and directory names match
all lower-case characters in package path
directory for ARM packages are well-formed

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] The PR targets the latest branch.
[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] Apache v2 license headers are included in each file.

Can one of the admins verify this patch?

Note this will fail until I finish cleaning up the repo (can't happen until https://github.com/Azure/azure-rest-api-specs/pull/4089 is merged).

Fixes most of https://github.com/Azure/azure-sdk-for-go/issues/2907

autorest.go 2.1.115 has dropped so we can move ahead with this PR.


[Back-End] Create the logic for generating the Hacktoberfest reports

Summary
Add description here...

We are going to provide a snapshot. This is scoped in the backend repo.


Missleading indentation in ecal_mon_plugin_wrapper

The line of code is here:
https://github.com/continental/ecal/blob/fe7ba1c266cdfb23b5d28c6c02ac123a0f96e5d2/app/mon/mon_gui/src/plugin/plugin_wrapper.cpp#L124
I guess it is missing curly braces, but I am not sure enough to change it myself

Yes, it's missing the curly braces. I think I added the line a few weeks ago (Yep, git blame says so).
Programming to much Python.
This is why we should always have curly braces is else statements.


Feat: Adding a Newsletter System

What feature?
Preface
By newsletter system, I mean a bi-weekly or monthly email to our users telling them about the blogs (or anything we made)
How to do it?

We can start of by First Implementing an input for it under each blog
Those Inputes will be stored somewhere (TO be decided, like sanity, supabase, Google Sheets)
In the given time duration a corn job of sorts should trigger the email
Or we don't want to do a corn job and do something custom that also will work
For emails we can use resend for now, as we grow bigger we can use mailgun and their student benefit perks
react-email can be used for styling the email but we are open to suggestions

These are all suggestions not hard and fast rules, feel free to raise concerns/suggestions.
Add screenshots
No response
Record

[x] I agree to follow this project's Code of Conduct
[ ] I want to work on this issue

I'm ready to work upon it

I was thinking of implementing this by first taking the input email into sanity, and monthly we manually run a script that fetches blogs from a given period from sanity itself. The way email is to be made is something we have to do rnd. React Email can be a good choice for it.
So all we have to do is make a script that makes email by taking content fetched from sanity, putting it in a pre-designed template, and sending it by resend API.
I am open to suggestions.

yeah, seems like a good enough plan


Efficient python tf buffer

Summary

Instead of having a custom tf listener this PR replaces the whole buffer. Python code is only involved if we actually do a transform.
Proposed changes

Related issues

Checklist

[ ] Run colcon build
[ ] Write documentation
[ ] Test on your machine
[ ] Test on the robot
[ ] Create issues for future work
[ ] Triage this PR and label it

This needs some cleanup and better handling of tf exceptions, but it generally works!

Any comments @timonegk ?


Slider manipulation results in crashes for react-native-windows when no step is specified

Environment

Building on a PC with visual studio 2019
Using<EMAIL_ADDRESS>Using<EMAIL_ADDRESS>
Description
If you don't specify a step value, no default is set. This then causes xaml range value component to generate errors
Reproducible Demo

Setup a react-native-windows project
Add<EMAIL_ADDRESS>as a dependency and register the package in your project's app.cpp file
Add a slider to your app, avoid specifying a step value
Manipulate the slider

Observed behavior
The application crashes because no step value is set
Expected behavior
The application falls back to using a default step value

fyi @BartoszKlonowski I already have a fix

fyi @BartoszKlonowski I already have a fix

@rectified95 I didn't notice your comment, but why have you been working on an issue which has already a developer assigned to it?

@rectified95 I didn't notice your comment, but why have you been working on an issue which has already a developer assigned to it?

@BartoszKlonowski The issue was spotted by a consumer from Hololens. along with the autolinking problem. He first reached out to me and only created these issues for tracking/visibility. I don't have the privileges to assign issues in this repo, so couldn't self-assign, and later on didn't check that you had it on you. We wanted to fix it sooner than later so I went ahead and did it.

@BartoszKlonowski The issue was spotted by a consumer from Hololens. along with the autolinking problem. He first reached out to me and only created these issues for tracking/visibility. I don't have the privileges to assign issues in this repo, so couldn't self-assign, and later on didn't check that you had it on you. We wanted to fix it sooner than later so I went ahead and did it.


[Fastlane.Swift] FastlaneSwiftRunner fails to build

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
Since the update from 2.183.2 to 2.184.0 the FastlaneSwiftRunner fails to build.
the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions on several occasions in Fastlane.swift
Fastlane.Swift was intialized from a clean state and nothing custom was added to make sure no code was affecting it.
Command executed

bundle exec fastlane init swift
bundle exec fastlane custom

Complete output when running fastlane, including the stack trace and command used

[✔] 🚀
[18:39:15]: loading manifest: /Users/david/.gem/ruby/2.7.0/gems/fastlane-2.184.0/fastlane/swift/upgrade_manifest.json
[18:39:15]: FastlaneSwiftRunner project is up-to-date
[18:39:15]: Resolving Swift Package Manager dependencies...
[18:39:15]: $ xcodebuild -resolvePackageDependencies -scheme FastlaneRunner -project ./fastlane/swift/FastlaneSwiftRunner/FastlaneSwiftRunner.xcodeproj
[18:39:16]: ▸ Command line invocation:
[18:39:16]: ▸     /Applications/Xcode-12.5.0.app/Contents/Developer/usr/bin/xcodebuild -resolvePackageDependencies -scheme FastlaneRunner -project ./fastlane/swift/FastlaneSwiftRunner/FastlaneSwiftRunner.xcodeproj
[18:39:16]: ▸ User defaults from command line:
[18:39:16]: ▸     IDEPackageSupportUseBuiltinSCM = YES
[18:39:16]: ▸ resolved source packages:
[18:39:16]: $ xcodebuild -showBuildSettings -scheme FastlaneRunner -project ./fastlane/swift/FastlaneSwiftRunner/FastlaneSwiftRunner.xcodeproj
[18:39:17]: $ set -o pipefail && xcodebuild -scheme FastlaneRunner -project ./fastlane/swift/FastlaneSwiftRunner/FastlaneSwiftRunner.xcodeproj -destination 'generic/platform=macOS' build | tee /Users/david/Library/Logs/gym/App-FastlaneRunner.log | xcpretty
▸ Compiling RubyCommand.swift
▸ Compiling RubyCommandable.swift
▸ Compiling Gymfile.swift
▸ Compiling MatchfileProtocol.swift
▸ Compiling SocketClientDelegateProtocol.swift
▸ Compiling LaneFileProtocol.swift
▸ Compiling Precheckfile.swift
▸ Compiling ScanfileProtocol.swift
▸ Compiling Matchfile.swift
▸ Compiling ScreengrabfileProtocol.swift
▸ Compiling ArgumentProcessor.swift
▸ Compiling GymfileProtocol.swift
▸ Compiling SnapshotfileProtocol.swift
▸ Compiling Deliverfile.swift
▸ Compiling Fastfile.swift
▸ Compiling Actions.swift
▸ Compiling Appfile.swift
▸ Compiling SocketClient.swift
▸ Compiling DeliverfileProtocol.swift
▸ Compiling Runner.swift
▸ Compiling RunnerArgument.swift
▸ Compiling ControlCommand.swift
▸ Compiling main.swift
▸ Compiling PrecheckfileProtocol.swift
▸ Compiling SocketResponse.swift
▸ Compiling Scanfile.swift
▸ Compiling Plugins.swift
▸ Compiling Snapshotfile.swift
▸ Compiling Fastlane.swift
▸ Compiling Screengrabfile.swift
▸ Compiling OptionalConfigValue.swift
▸ Compiling RubyCommand.swift
▸ Compiling RubyCommandable.swift
▸ Compiling Gymfile.swift
▸ Compiling MatchfileProtocol.swift
▸ Compiling SocketClientDelegateProtocol.swift
▸ Compiling LaneFileProtocol.swift
▸ Compiling Precheckfile.swift
▸ Compiling ScanfileProtocol.swift
▸ Compiling Matchfile.swift
▸ Compiling ScreengrabfileProtocol.swift
▸ Compiling ArgumentProcessor.swift
▸ Compiling GymfileProtocol.swift
▸ Compiling SnapshotfileProtocol.swift
▸ Compiling Deliverfile.swift
▸ Compiling Fastfile.swift
▸ Compiling Actions.swift
▸ Compiling Appfile.swift
▸ Compiling SocketClient.swift
▸ Compiling DeliverfileProtocol.swift
▸ Compiling Runner.swift
** BUILD FAILED **

The following build commands failed:
	CompileSwift normal x86_64 /Users/.../fastlane/swift/Plugins.swift
	CompileSwift normal x86_64 /Users/.../fastlane/swift/Snapshotfile.swift
	CompileSwift normal x86_64 /Users/.../fastlane/swift/Fastlane.swift
	CompileSwift normal x86_64 /Users/.../fastlane/swift/Screengrabfile.swift
	CompileSwift normal x86_64 /Users/.../fastlane/swift/OptionalConfigValue.swift
	CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler
	CompileSwift normal arm64 /Users/.../fastlane/swift/Fastlane.swift
(7 failures)
▸ Compiling RunnerArgument.swift
▸ Compiling ControlCommand.swift
▸ Compiling main.swift
▸ Compiling PrecheckfileProtocol.swift
▸ Compiling SocketResponse.swift
▸ Compiling Scanfile.swift
▸ Compiling Plugins.swift
▸ Compiling Snapshotfile.swift
▸ Compiling Fastlane.swift

❌  /Users/.../fastlane/swift/Fastlane.swift:625:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:892:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:1453:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:1645:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:1841:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:2229:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:2433:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:2537:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:3835:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:5561:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:5834:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:6612:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:6806:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:7458:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:8600:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:8680:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:8998:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:9869:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:10073:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:10154:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:10222:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:10566:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:10824:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:11071:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:11999:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:12157:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:12372:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

❌  /Users/.../fastlane/swift/Fastlane.swift:12800:10: the compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

        .compactMap { $0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~

▸ Compiling Screengrabfile.swift
▸ Compiling OptionalConfigValue.swift
[18:43:59]: Exit status: 65
+-----------+--------+
|    Lane Context    |
+-----------+--------+
| LANE_NAME | custom |
+-----------+--------+
[18:43:59]: Exit status: 65
[18:43:59]: fastlane finished with errors

[!] Exit status: 65

Environment
✅ fastlane environment ✅
Stack

Key
Value

OS
11.2.3

Ruby
2.7.3

Bundler?
true

Git
git version 2.31.1

Installation Source
~/.gem/ruby/2.7.0/bin/fastlane

Host
macOS 11.2.3 (20D91)

Ruby Lib Dir
<EMAIL_ADDRESS>

OpenSSL Version
OpenSSL 1.1.1k  25 Mar 2021

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode-12.5.0.app/Contents/Developer/

Xcode Version
12.5

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile.swift`
// This file contains the fastlane.tools configuration
// You can find the documentation at https://docs.fastlane.tools
//
// For a list of all available actions, check out
//
//     https://docs.fastlane.tools/actions
//

import Foundation

class Fastfile: LaneFile {
	func customLane() {
	desc("Description of what the lane does")
		// add actions here: https://docs.fastlane.tools/actions
	}
}

No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.184.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.4.0

bundler
2.2.15

uri
0.10.0

rake
13.0.3

CFPropertyList
3.0.3

public_suffix
4.0.6

addressable
2.7.0

artifactory
3.0.15

atomos
0.1.3

aws-eventstream
1.1.1

aws-partitions
1.461.0

aws-sigv4
1.2.3

jmespath
1.4.0

aws-sdk-core
3.114.0

aws-sdk-kms
1.43.0

aws-sdk-s3
1.95.0

babosa
1.0.4

claide
1.0.3

colored
1.2

colored2
3.1.2

highline
2.0.3

commander
4.6.0

declarative
0.0.20

digest-crc
0.6.3

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.7.6

emoji_regex
3.2.2

excon
0.81.0

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-net_http
1.0.1

faraday-net_http_persistent
1.1.0

multipart-post
2.0.0

ruby2_keywords
0.0.4

faraday
1.4.2

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

fastimage
2.2.3

gh_inspector
1.1.3

jwt
2.2.3

memoist
0.16.2

multi_json
1.15.0

os
1.1.1

signet
0.15.0

googleauth
0.16.2

httpclient
2.8.3

mini_mime
1.1.0

trailblazer-option
0.1.1

uber
0.1.0

representable
3.1.1

retriable
3.1.2

rexml
3.2.5

webrick
1.7.0

google-apis-core
0.3.0

google-apis-androidpublisher_v3
0.3.0

google-apis-playcustomapp_v1
0.2.0

google-apis-iamcredentials_v1
0.3.0

google-apis-storage_v1
0.3.0

google-cloud-env
1.5.0

google-cloud-errors
1.1.0

google-cloud-core
1.6.0

google-cloud-storage
1.31.1

json
2.5.1

mini_magick
4.11.0

naturally
2.2.1

plist
3.6.0

rubyzip
2.3.0

security
0.1.3

simctl
1.6.8

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

nanaimo
0.3.0

xcodeproj
1.19.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

generated on: 2021-05-22

Can you add which Xcode + Swift version are you using?

I get the same error, using Xcode 12.5 and Swift 5.4.

I'll check asap. It doesn't happen with older Swift versions nor with the CI system.

Same issue here, Xcode 12.5 and Swift 5.4. Are there any fixes on the way @minuscorp ?

I'm trying to launch a fix soon, this week at most.

You can checkout the PR proposed to see if it fixes your issues @divadretlaw

Tested using this command bundle exec fastlane generate_swift_api on PR and master.
FastlaneSwiftRunner builds successfully on the PR branch but fails on master using Xcode 12.5 and Swift 5.4
But executing the command using the PR fastlane:

bundle exec fastlane init swift
bundle exec fastlane custom

still gives the same error, possibly because the checked in files in fastlane/swift are not updated to reflect the changes.

That's probably it. I check the ability to generate the build files but maybe the checkout has the old ones until the release is done


A translation imporvement suggestion

The translation located in line 10 has a tiny imporvement could be done. The phrase 'a useful skill by itself' should be considered as a whole meaning 「自身就是一项有用的技能」rather than split it up, take the 'by itself' part sticking it to 'learning to program'. That would be a diffrent meaning. Beside, it makes more sense translating this way considering the sentence right after it. The author made a comparision about programming serves as an useful skill itself alone and in the situations it serves as way to solve other problems.
Other modifications are trival and could be ignored since in most case they are just a matter of taste resulting in no misunderstandings.

The end line spaces are automatically deleted by my text editor(atom). I'm not a syntax lunatic.😂


Add support for tvOS and watchOS

Describe the feature
Currently tvOS and watchOS fail because the package files (here and in smithy-swift) don't specify min versions.
Update the package manifest to match the min version defined in crt.
Additionally, verify all services build successfully and all tests pass
Use Case
N/A
Proposed Solution
No response
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

Not a requirement for GA, but might be low-hanging fruit and with enough requests we will reconsider priority.

Closing as this is done already


cmd/pull: add retry to curl bottle download

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

Adds retry logic to the "download bottle file with curl" step in the bottle verification method.
Works around issue with GET and HEAD apparently acting differently, and bottle downloads failing even after successful polling completion. This is something @UniqMartin has been seeing.
I went with this implementation because it sticks with doing the main polling (which is expected to happen several times in the normal caes) using the lightweight HEAD and reused server connection, which is polite to Bintray's server, and produces concise "Waiting on Bintray....." progress output.
Uses exponential backoff instead of constant backoff for this step because it's using curl so it gets a new connection every time.
I also tried switching the polling to use a GET with byte ranges instead of HEAD, but it appears that Bintray's web server does not support them.

Re 745a1312dce936ddd519c2e151e889459243c543: I'm pretty sure this line can be just dropped (and should be to avoid future confusion). It is probably unlikely to ever matter, but I'd use the same opportunity to bump max_curl_retries to 2 or 3.
I guess the morale of the story could be to run brew readall --syntax (and tests!) locally if the bot is particularly busy and you're inclined to pull before the test-bot run finishes successfully.

Yeah, it was a dumb bug on my part after I moved the retry_count += 1 down into the rescue block. Removed in 2044294a865a85c4c3144a3000bd9a48427e12c6. Sorry about that.
I had run brew tests locally, but I never do brew readall --syntax. Maybe brew tests should incorporate brew readall --syntax as a test, for convenience, and so our PR template steps include it?

I had run brew tests locally, but I never do brew readall --syntax. Maybe brew tests should incorporate brew readall --syntax as a test, for convenience, and so our PR template steps include it?

If you want to poke this code a bit, I think nowadays (after the split) readall is making even less sense than it did a while ago, because it performs two completely orthogonal tasks:

Check the Ruby syntax of Homebrew (the package manager) files.
Validate aliases and try to load all formula files, either from a specified tap or all installed taps.

The former only makes sense for the Homebrew/brew repository and the latter only makes sense in the various Homebrew/homebrew-* repositories, thus some rearrangement would make sense. I don't think tests is the right place for it, but maybe it would be convenient to have a developer command that can be run locally without too much thought and does something similar to test-bot for Homebrew/brew.
That said, if you really wanted to dive into the code, I think test-bot could benefit from some refactoring around readall and tests. Not all of it makes sense in both the Homebrew/brew repository and the Homebrew/homebrew-* repositories now that we have separated them.

The former only makes sense for the Homebrew/brew repository and the latter only makes sense in the various Homebrew/homebrew-* repositories, thus some rearrangement would make sense.

👍

Was some discussion on this line from https://github.com/Homebrew/homebrew-core/pull/999#issuecomment-218608832 and below, if anyone wonders historically why my hack seemingly came out of the blue 😄.
Agree with @UniqMartin's comment above here.


h apply date 21

@nvmbrasserie This seems to have a different solution for id_dttot than what is now merged. Can you have a look and pick what's better?


Missing location.

https://github.com/marklister
I move between various locations: Harare, various places in DRC, Ivory coast etc.

So if you could add "Africa" as an African city that would probably work.


support kafka header

Support Kafka header passthrough, which can be used to transmit trace ID.

Hi @xiangzi1113 @fishery86 please take a look while you're free

Suggestion: Discard BatchProduceWithJson(), and instead extend BatchProduce(), transmitting trace information through the header


Eventing TLS: Pass CA certs to the data plane

Problem
After https://github.com/knative-sandbox/eventing-kafka-broker/issues/3109, we're now resolving destinations to full addressables which contains URL and CA certs that we need to pass to the data plane through the "contract".
Our contract (which is a protobuf message) contains a few URLs:
destination: https://github.com/knative-sandbox/eventing-kafka-broker/blob/06e73351124a536eeb208f223e2b654b9a044dfa/proto/contract.proto#L111-L112
deadLetter: https://github.com/knative-sandbox/eventing-kafka-broker/blob/06e73351124a536eeb208f223e2b654b9a044dfa/proto/contract.proto#L75-L76
replyUrl: https://github.com/knative-sandbox/eventing-kafka-broker/blob/06e73351124a536eeb208f223e2b654b9a044dfa/proto/contract.proto#L115-L116
All of them are HTTP URLs that might be TLS endpoints and our data plane needs to trust a specific CA for each of them.
In this issue, we need to:

add CA certs fields to our contract, for example: destinationCACerts, replyUrlCACerts, and deadLetterCACerts as strings (each living alongside the URL counterpart)
generate the code that is generated out of the protobuf definition with hack/update-codegen.sh
Pass CA Certs to the data plane [1]

[1] for example, in the trigger destination case, we, currently, have this:
https://github.com/knative-sandbox/eventing-kafka-broker/blob/06e73351124a536eeb208f223e2b654b9a044dfa/control-plane/pkg/reconciler/trigger/trigger.go#L308-L327
we would need to additionally do something like this:
if destination.CACerts != nil {
  egress.DestinationCACerts = *destination.CACerts
}

For other fields, the logic is the same, names might vary.
To find the places, we need such logic, use the URIResolver usages as in https://github.com/knative-sandbox/eventing-kafka-broker/issues/3109
Exit Criteria

Pass CA certs to the data plane
Unit tests that verify that the contract contains CA certs

Time Estimate (optional):
How many developer-days do you think this may take to resolve?
2
Additional context (optional)
/help

/assign


How to import to a subcollection

I am trying to export a top-level collection foo which exports just fine.
Next, I want to import this exported json into a second level collection, which is foo/baz.
I am getting the below error
Error: Value for argument "documentPath" must point to a document, but was "foo/baz/bar/bat/23/taz/1wda". Your path does not contain an even number of components.
Below is the command I am using to export
backfire export ./testdata  --config config --paths foo --debug
And to import
backfire import ./testdata.ndjson --config config --gcpProject project  --debug
FYI, in the json I am editing all the paths that begin with foo with foo/baz

Hi @gtlsgamr, the error should be fairly self explanatory, and it comes from the Firebase SDK. Please take a look at the Cloud Firestore Data model to understand how documents and collections work.
By changing foo to foo/baz, you've turned your paths, which would have been originally pointing to documents, to be pointing to a collection.
For example, users/john would have pointed to a document with the ID john in the collection users. You've now changed the path to users/baz/john, which is now pointing to a subcollection called john under the document baz. You cannot import a document to to a collection path.
If you want to change the nesting level of your documents, you'll need to add an even number of segments.
Closing this as it's not an issue with the package, but feel free to reply if you need further assistance!


quay.io/jetstack/cert-manager not public

Hi community, I'm trying to install cert-manager from a Helm chart but looks like the image quay.io/jetstack/cert-manager is not public so the image pull failed.
Is this intentional? To reproduce, simply run docker pull quay.io/jetstack/cert-manager:v1.6.1

looks like the image quay.io/jetstack/cert-manager is not public

There isn't a quay.io/jetstack/cert-manager image I think. For the controller (main cert-manager component) it should be quay.io/jetstack/cert-manager-controller
docker pull quay.io/jetstack/cert-manager-controller:v1.6.1 works for me.

Ah I see, thank you for explaining :)
So it seems that quay.io would return the code of 403 for inexistent repos, and the Helm chart I used misconfigured the image name :(


Handle IOException when opening InputStream to download GitHub project

Before, the input stream was opened in the downloadAndSaveProject method, which did not catch IOExceptions. These however were thrown if an input stream could not be opened.
Now, the input stream is opened directly inside the getInputStream function, previously the getConnection function, which to me makes more sense.
From what I've read online, it seems that closing this input stream is sufficient for releasing the underlying resources of the connection, meaning that is not necessary to also close the connection itself.

(looks good except for these two comments)

Codecov Report

Merging #306 into master will increase coverage by 0.23%.
The diff coverage is 26.66%.

@@             Coverage Diff             @@
##             master    #306      +/-   ##
===========================================
+ Coverage     80.47%   80.7%   +0.23%
- Complexity      536     630      +94
===========================================
  Files            69      82      +13
  Lines          1603    1954     +351
  Branches        254     312      +58
===========================================
+ Hits           1290    1577     +287
- Misses          213     258      +45
- Partials        100     119      +19

Impacted Files
Coverage Δ
Complexity Δ

...ngpipeline/miner/github/GitHubProjectDownloader.kt
60.31% <26.66%> (-2.37%)
11 <1> (-1)

...ithubtestreporter/webhookevents/CheckSuiteEvent.kt
100% <0%> (ø)
6% <0%> (?)

...eline/githubtestreporter/CIJobCompletedListener.kt
89.28% <0%> (ø)
5% <0%> (?)

...ipeline/githubtestreporter/webhookevents/Shared.kt
100% <0%> (ø)
0% <0%> (?)

...tionpipeline/githubtestreporter/AppKeyGenerator.kt
93.75% <0%> (ø)
3% <0%> (?)

...e/githubtestreporter/githubapi/CustomHttpClient.kt
18% <0%> (ø)
3% <0%> (?)

...tionpipeline/githubtestreporter/WebHookReceiver.kt
86.66% <0%> (ø)
9% <0%> (?)

...alidationpipeline/githubtestreporter/Properties.kt
62.5% <0%> (ø)
5% <0%> (?)

.../githubtestreporter/githubapi/JsonObjectBuilder.kt
100% <0%> (ø)
3% <0%> (?)

... and 10 more

Continue to review full report at Codecov.

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


documentation Best Practices

http://www.quartz-scheduler.org/documentation/best-practices.html
Trigger Tips
it should be TriggerBuilder，not  TriggerUtils ？？

Fixed by PR #371


File watcher crashing when passing a class name to view command

I mistakenly passed a class name to view command and since the file watcher is not able to find the file, it crashed.
twd view MainViewModel
09:38:25.723 [main] INFO  i.r.tumbleweed.web.TumbleweedServer - Watching for changes: MainViewModel
java.lang.NullPointerException: Cannot invoke "java.nio.file.Path.register(java.nio.file.WatchService, java.nio.file.WatchEvent$Kind[], java.nio.file.WatchEvent$Modifier[])" because the return value of "java.nio.file.Path.getParent()" is null
	at io.redgreen.tumbleweed.filesystem.FileWatcher.startWatching(FileWatcher.kt:18)
	at io.redgreen.tumbleweed.web.TumbleweedServer.startWatchingFileForChanges(TumbleweedServer.kt:103)
	at io.redgreen.tumbleweed.web.TumbleweedServer.start(TumbleweedServer.kt:46)
	at io.redgreen.tumbleweed.cli.dev.view.ViewCommand.run(ViewCommand.kt:32)
	at picocli.CommandLine.executeUserObject(CommandLine.java:1939)
	at picocli.CommandLine.access$1300(CommandLine.java:145)
	at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2358)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2352)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2314)
	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2179)
	at picocli.CommandLine$RunLast.execute(CommandLine.java:2316)
	at picocli.CommandLine.execute(CommandLine.java:2078)
	at io.redgreen.tumbleweed.cli.MainKt.main(Main.kt:46)

This is happening because view command is expecting a valid file path and doesn't verify the path before starting the watch service.
We can follow the similar approach we have in WatchCommand and throw an IllegalArgumentException with proper error message like so
if (!jsonFile.toPath().exists()) {
  throw IllegalArgumentException("JSON file not found at given path: $jsonFile, please provide a valid file path")
}

or handle it in the TumbleweedServer. Currently we are doing this check when file changes happen. But we can do another check before starting it and just show an error message using logger.
I personally prefer the first approach as it's consistent with how we are handling CLI params for watch command as well. WDYT @ragunathjawahar ?

I agree, none of the commands validate inputs at the moment. This is what I have in mind.

For files, we could check the file path. That's a good start.
For the file format, it would help to validate if the user is passing in the desired format itself (e.g. CSV, JSON).

Instead of throwing an exception, we could just print an error message to the user.

Instead of throwing an exception, we could just print an error message to the user.

Yeah, I was initially thinking of using logger to print the logs. But wasn't sure if I should introduce that dependency in the command yet or not.


Sanity query: consider conflicts between k8s and calico policies

Should also report conflicts between K8s policies and Calico policies with order==1000

Moved to NP-Guard repo. See here


build: add test/... to the bazel_build job

update the bazel_build job (the job that tests that everything
builds with Bazel) to also include test/...

Blocked by PR #20221

@wagnermaciel looks like the job fails for some reason. Can you look into it? Happy to help if needed. I wonder how this runs in g3 right now?

@wagnermaciel looks like the job fails for some reason. Can you look into it? Happy to help if needed. I wonder how this runs in g3 right now?

@devversion I could actually use some help here. When I build //test/... locally everything passes, but on CI the test is failing saying it
could not resolve //src/material-experimental/mdc-theming/prebuilt/indigo-pink.css

I remember Jeremy was surprised that we are able to reference indigo-pink.css in the benchmark components like this
styleUrls: ['//src/material-experimental/mdc-theming/prebuilt/indigo-pink.css'],
so I am pretty sure referencing indigo-pink like this is what's causing the failures but I don't know why.

@wagnermaciel yeah, that was actually something I was not sure either. I looked into it.. and it seemed that this purely worked by accident in ngtsc. See explanation of why this works. As a side note: It would be good to consider moving away from this unconventional pattern at some point.
Can you try adding the prebuilt theme to ng_assets of the component benchmark rule? I see it is only added to styles, but we load the prebuilt theme as part of the component, so it needs to be part of the dependencies when the ng_module is built. This might also explain why it surfaces only on CI where we build in remote build containers (with full sandboxed environments).

I tried locally but was not able to reproduce it there. I'm pretty confident it's due to the issue I mentioned before w/ RBE. We can remove the prebuilt theme from the styles too because they are inlined directly into the component definition when the ng_module target is built.

@devversion I tried using ng_assets to provide the styles but the tests still failed to build on ci
I think we'll have to solve the larger problem and revisit this. Even though the current component_benchmark implementation is nice and simple, I agree that this not a good pattern and a more complex solution is clearly needed
I'm not sure if or when asset injection will be implemented given how many other higher priority tasks we've got lined up but how would you feel about discussing it again in next weeks team meeting?

@wagnermaciel Yeah. I'm not sure why it works locally but not on CI. The only difference is really the remote container sandboxing as far as I remember. Agreed, that we should not bother with this as obviously this is working by accident/is somewhat hacky.


dnd terminal editor in editor area disposes of it

this is responsible for that
https://github.com/microsoft/vscode/blob/a9e2bd1495325c5b35f6539beaffda710e92a2e5/src/vs/workbench/contrib/terminal/browser/terminalEditorService.ts#L68-L72

and that's because the editor group gets closed when the editor is moved


Youtube Subtitle - can't download auto-generated in French when EN manual-subtiles exists

[ ] I'm reporting a broken site support issue
[ ] I've verified that I'm running youtube-dl version 2<IP_ADDRESS>
[ ] I've checked that all provided URLs are alive and playable in a browser
[ ] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[ ] I've searched the bugtracker for similar bug reports including closed ones
[ ] I've read bugs section in FAQ

Verbose log
youtube-dl --id xgy0rW0oaFI --sub-lang fr --write-auto-sub --sub-format vtt --skip-download
[youtube] xgy0rW0oaFI: Downloading webpage
[youtube] xgy0rW0oaFI: Looking for automatic captions
[info] Writing video subtitles to: xgy0rW0oaFI.fr.vtt
Description
This vidéo  https://www.youtube.com/watch?v=xgy0rW0oaFI

is in french
has only English manual-subtile

When downloading french auto-generated sub, I do not get auto-generated (from voice) but get the transated version of the english subtitles.
Other "tools" get the right ones :
https://savesubs.com/process?url=https://www.youtube.com/watch?v=xgy0rW0oaFI&feature=youtu.be&t=5129
To check, at 00:01:11  you should read "entrée" and not "apéritif"
"entrée" is the right word said in the vidéo
"apéritif" is the translation from the english subtitle version
Thanks,

It happened to me too, but with this video: https://www.youtube.com/watch?v=cSMNUxmNA8A
Not to mention I'm not trying to download the French subtitles, I'm trying to get the auto English ones. I need the automatic ones specifically for https://github.com/antiboredom/videogrep
Hopefully this is fixed soon.


exporter/stats/prometheus: support interval windows

This is a tracking bug for the interval window support for the Prometheus exporter.

I think this issue is blocked on https://github.com/census-instrumentation/opencensus-go/issues/185 or at least the research related to it for example https://github.com/census-instrumentation/opencensus-go/issues/185#issuecomment-348342508


added resiliency to changelog helper.py

Added retries to stix downloads in changelog_helpers.py

Thanks for the pull request, but ultimately I decided to go with a similar approach found in https://stackoverflow.com/questions/15431044/can-i-set-max-retries-for-requests-request - but only after you suggested this approach.


Add option to configure the default show context (number of context lines) in search editor

I keep opening the search editor and clicking the show context button every single time - the show context to me is one of the stronger features of the search editor.
It would be nice to be able to configure it permanently. I know reusePriorSearchConfiguration exists but that would affect all the other settings.
My proposal is to add search.searchEditor.defaultShowContextValue property (number | null) which when defined would override the default value for the number of context lines.
reusePriorSearchConfiguration would take precedence if both are used.

Thanks for this and the PR! I unfortunately wasn't able to get around to it in the May iteration but I've scheduled it for June.

Closed with #97920.

A description would be helpful. Right now this is probably not apparent to a normal user

This doesn't appear to work for me. I set it to the suggested value of 2 but context was not shown

Version: 1.46.0-insider (user setup)
Commit: 1bfa086adb9271ff56be11821da686e4cfffb672
Date: 2020-06-02T06:55:33.079Z
Electron: 7.3.0
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

Description was already added in master, will look into rest

The description is:
The default number of surrounding context lines to show in Search Editor results. If defined, this overrides #search.searchEditor.reusePriorSearchConfiguration# for context line configuration in new Search Editors.
Testing, this does seem to work: if I set the value, then open a new search editor, and run a query, it will have context. It doesn't update live, but I think based on the description that wouldn't be expected.

That doesn't work for me. Here's a recording, maybe I'm missing something: https://memes.peet.io/img/20-06-28fc1d00-d10d-4ea3-8563-cf0a1058e6d3.webm

Ah... hm. This was meant for the command Search Editor: open new Search Editor, not Search Editor: Open Results in Editor. Open in editor doesn't run a new search, so it can't get the context lines. Agreed that it's confusing...

I've updated the name of the setting to defaultNumberOfContextLines and updated the description text to be more specific about where it applies. Also updated so the number isn't displayed when it is not actually used (open results in editor case).
Please verify:

search.searchEditor.defaultNumberOfContextLines name and description make sense.
When the setting is set to some value, running "Search Editor: Open new Search Editor" will pre-fill that value correctly, and searches will have that number of context lines
when creating a search editor from existing results ("Open Results in Editor"), the context lines box does not incorrectly show that context lines are enabled.

Please consider giving it a numeric default instead of null, so we can use the settings GUI for it too

We actually can render number | null in the settings editor. Empty input is mapped to null. (That was one of my intern projects lol)

Oh yeah I forgot we can for number. Not string.

This doesn't seem to work if I type a search term and press Ctrl Enter: no context lines are added to the view.


Configure Renovate

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.
🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

go.mod (gomod)

What to Expect
With your current configuration, Renovate will create 1 Pull Request:

Update dadosjusbr/coletores commit hash to 58ae69e

Schedule: ["at any time"]
Branch name: renovate/dadosjusbr-coletores-digest
Merge into: main
Upgrade dadosjusbr/coletores to 58ae69ee7ffe954905b9da97453cba519ad11e56

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

This PR has been generated by Renovate Bot.

Desculpa gente, estava testando uma GitHub app com a minha conta pessoal e ela acabou criando esses PRs na maior parte das orgs que faço parte.


Add priority queue

Add priority queue example with proper comments.

@dubesar may i work on this?


Can't find modules defined in typings directory

Using lodash and having the typings installed I can compile.
Using typedoc with the same typescript version I get:
Cannot find name '_'.

+1 I also get this.

I was able to fix this by adding ./typings/index.d.ts to source-files. Maybe this can help you also ...

I was originally running:
$ typedoc --out docs  --module "commonjs" src

Using TypeScript 1.8.10 from /Users/glavin/Documents/Project Dev/unibeautify/node_modules/typescript/lib
Error: /Users/glavin/Documents/Project Dev/unibeautify/src/beautifier.d.ts(0)
 Cannot find module 'bluebird'.
Error: /Users/glavin/Documents/Project Dev/unibeautify/src/beautifier.ts(2)
 Cannot find module 'bluebird'.

Then I added --includeDeclarations typings/ and it works:
$ typedoc --out docs --includeDeclarations typings/ --module commonjs src

Using TypeScript 1.8.10 from /Users/glavin/Documents/Project Dev/unibeautify/node_modules/typescript/lib
Rendering [========================================] 100%

Documentation generated at /Users/glavin/Documents/Project Dev/unibeautify/docs

I've ended with:
typedoc --out docs --exclude \"**/*.spec.ts\" --excludeExternals --excludePrivate --readme README.md  node_modules/@types src


Unable to create a mirror for GarageBand loops

Describe the bug
Receive the error shown below trying to mirror GarageBand Mandatory/Optional loops:
loopdown: error: --discover-plists-range not allowed without argument: --discovery-plists
The arguments I'm passing to the binary are:
./loopdown -a garageband -m -o --create-mirror /Users/TestCapture/Desktop/GB_Downloads
Which macOS Version?
Output of sw_vers:
(Apple M1 iMac)
ProductName:		macOS
ProductVersion:		13.4.1
BuildVersion:		22F82
Additional context
/usr/local/bin/python3 --version
Python 3.11.4

Please check v1.0.20230706 and see if this is resolved.

Was seeing same issue, does seem resolved in v1.0.20230706


Fix diagnostics issue #2477

Summary
Update the container tooling docs now that we support direct download
Fixes https://github.com/dotnet/diagnostics/issues/2477

@gewarren do you have any idea why the checks are failing? I can't seem to figure it out.

@gewarren do you have any idea why the checks are failing? I can't seem to figure it out.

That is usually a transient error. I'll close and reopen to trigger a new build.


Update datascience-python to 5.0.0 and civis-jupyter-notebook to 0.4.5

@salilgupta1 Can you review this please?


fix(deps): :arrow_up: update angular monorepo to v17.0.1

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

@angular/animations
17.0.0 -> 17.0.1

@angular/common
^17.0.0 -> ^17.0.1

@angular/common
17.0.0 -> 17.0.1

@angular/compiler
17.0.0 -> 17.0.1

@angular/compiler-cli (source)
17.0.0 -> 17.0.1

@angular/elements
17.0.0 -> 17.0.1

@angular/forms
17.0.0 -> 17.0.1

@angular/language-service
17.0.0 -> 17.0.1

@angular/platform-browser
^17.0.0 -> ^17.0.1

@angular/platform-browser
17.0.0 -> 17.0.1

@angular/platform-browser-dynamic
^17.0.0 -> ^17.0.1

@angular/platform-browser-dynamic
17.0.0 -> 17.0.1

@angular/router (source)
^17.0.0 -> ^17.0.1

@angular/router (source)
17.0.0 -> 17.0.1

@angular/service-worker
17.0.0 -> 17.0.1

Release Notes

angular/angular (@angular/animations)
v17.0.1
Compare Source
http

Commit
Type
Description

5c6f3f8ec0
fix
Don't override the backend when using the InMemoryWebAPI (#52425)

migrations

Commit
Type
Description

70d30c28e0
fix
Add support for ng-templates with i18n attributes (#52597)

4f125c5f9a
fix
Switches to multiple passes to fix several reported bugs (#52592)

Web Frameworks: the internet frontier.
These are the voyages of the framework Angular.
Its continuing mission:
To explore strange, new technologies.
To seek out new users and new applications.
To boldly go where no web framework has gone before.
In honor of v17.0.1
                                                  ______
                                     ___.--------'------`---------.____
                               _.---'----------------------------------`---.__
                             .'___=]===========================================
,-----------------------..__/.'         >--.______        _______.---'
]====================<==||(__)        .'          `------'
`-----------------------`' ----.___--/
     /       /---'                 `/
    /_______(______________________/
    `-------------.--------------.'
                   \________|_.-'

Live long and prosper 🖖🏻

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
npm WARN cli npm v10.2.3 does not support Node.js v20.2.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-11-12T17_51_21_871Z-eresolve-report.txt

npm ERR!


Documenting install via Docker

Hi, could instructions please be posted on how to install / configure Elastix via the Docker image on Dockerhub? I looked in the Getting Started portion of the docs (https://simpleelastix.readthedocs.io/GettingStarted.html) and saw great instructions for setting up Elastix via CMake etc but not for Docker. I would like to install / configure Elastix via Docker and import it into a Jupyter notebook. Documentation on setup much appreciated.
Thank you!

Hi, on the elastix repository on DockerHub you can find a detailed readme on how to use and pull the docker image to use on you local machine via the command line.
If you want to use elastix in a jupyter notebook I would suggest having a look at the ITKElastix package, rather than the docker image. ITKElastix is available on Pypi and can easily be installed with pip install itk-elastix. See the example notebooks for using itk-elastix in a jupyter notebook.


Multi Sort uses the wrong priority sequence

Current:
Clicking one column header and then another column header marks the last clicked column header with a 1, and gives it the highest sorting priority.
Expected:
The first clicked column has the highest priority.

Not sure how much work it will be to change this. Needs to be checked.

Is is doable by overriding _onSorterChanged (on sort-mixing of vaadin-grid) to use push, not unshift. But this would be overriding private method, that is ugly. Other option would be to catch the sorter event, and redirect it to our own handler, but again same issue.
So to fix this we need to modify private behavior of vaadin-grid, which can easily break at any point when vaadin-grid dependency is updated.

Trying to see if I can get this resolved while I implement px-data-grid-sorter.html

No resolved to 5A, maybe will be to 5B. Way to fix this is little ugly (replacement of event handling in vaadin-grid when header clicked).


specify how this works in readme.md

Hi all
Checking this library out - trying to figure out how it works - it looks like it doesn't use NODE_PATH (that wouldn't really be possible given the nature of this), so how does it work?
I probably won't use it unless I know how it works, will try to poke around some more to figure it out

This module works by monkey-patching the internal require('module').Module._nodeModulePaths method to prepend additional directories: https://github.com/patrick-steele-idem/app-module-path-node/blob/97fc60947bcca6e194f549d0d374ef34a5eb49df/lib/index.js#L7-L17
You may want to consider using the more recent require-self-ref module as an alternative. Both app-module-path and require-self-ref work, but I find require-self-ref to be cleaner. require-self-ref monkey patches the internal require('module').Module. _resolveFilename method.
I don't have time to update the README at the moment, but hopefully that helps clarify.

thanks that helps! you probably could just copy and paste this answer to the top of the readme

it's up to you if you want to merge it
https://github.com/patrick-steele-idem/app-module-path-node/pull/24
thanks


Support ruby 2.2 for developer

Add 2.2 to travis CI
Add unittest dependencies to ruby 2.2 and up ruby 2

I don't think I change any logic, so stick to current release version should be fine.

Thanks!


Local Jenkins needs updated to v2.181

Please update the helm chart and then update the cluster.

Helm chart updated


feat(css): support resolving stylesheets from exports map

Description

This allows stylesheets to import styles that should resolve to a style condition in an export map. Resolves #7809.
Additional context

I would have preferred to implement the value of the of unsafe condition to be true only when either the importer isn't an ES module or when there is an import assertion/query param indicating that the requested module isn't JavaScript (for the case where the importer is index.html). However this approach felt a bit too involved, so this new isUnsafeExport resolver option feels like the best solution for now.

What is the purpose of this pull request?

[ ] Bug fix
[x] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

Thanks for creating a PR for this. I've placed this in the to-discuss list for the coming team meetings, as supporting webpack's special conditions is a new feature. Will give an update when we come around to it!

How is it looking for getting this feature into Vite 3?

This is currently still in the team discussion board. We haven't got a chance to visit yet, but will make an update when we do!

Has this feature been discussed yet? Would also love to see this generally available

@bluwy any updates here?

@bluwy What discussion does this feature still need? I would really like to move some projects over to Vite but this feature is important given how all of our existing code imports stylesheets w/ webpack.

One of the things I'm concerned of that I want to discuss with the team is whether Vite should follow this convention. It seems to only be implemented by Webpack and so a package that takes advantage of this condition currently works with Webpack only.
This can be workaround by splitting the modules as separate entrypoints too, and I think that's the better/safer way instead of mixing styles and JS. Others may have different opinion which I'd be interested to hear.
I'm trying to push into reviewing more topics in the meetings but we constantly have higher priority topics that pushes back many outstanding backlog. I'm not a fan of this PR being stalled for too long too but we're trying our best to fit in time to discuss things.

This can be workaround by splitting the modules as separate entrypoints too, and I think that's the better/safer way instead of mixing styles and JS. Others may have different opinion which I'd be interested to hear.

I think keeping styles and js in the same module has huge value for component libraries

@bluwy, You should conside this feature becuase most of libraries build with webpack using this configuration and If developer tries to use these libs and build it using vite then build will always fail.
Is there any workaround can be used in vite configuration to fix this issue? Because we can not remove sass module exports from third party libraries.

Yes, given https://github.com/vitejs/vite/issues/11947 I'm thinking this make sense now. I'll bring this to discussion async this week.

After last week's meeting, we decided to go forward with the new conditions, because we also have the same ones for mainFields. We should not use the isUnsafeExport though, I think it should work without as a general fallback, and it could be a breaking change too if that's used.
I'll make some changes in this PR and it should be good for Vite 4.2

I believe isUnsafeExport can be dropped as long as style and others appear before import and require in export maps.
However, given the current support for export maps with styles (i.e. none), I don't see this as potentially breaking. I would still encourage its use here since it guards stylesheet imports from doing something invalid like attempting to load a JS file as a stylesheet.

That makes sense, thanks for considering it. I'll let you sort out the DX!
I agree that resolution failures tend to be really opaque. But it would be great if something like this were possible!
./my-styles.scss: failed to resolve conditions "style", "sass", or "default" in ./node_modules/my-component/package.json:

@use 'my-component';
^^^^^^^^^^^^^^^^^^^^

We've discussed this and decided to keep import/require/browser/node conditions for CSS for now to be safe. If it turns out to negatively affect things, we could tighten it up in Vite 5 again.


Initial variant not applied when same as breakpoint variant

Bug report
Describe the bug
Context: Responsive Styles
When setting the @initial variant to the same variant as the breakpoint, the initial variant gets not applied.
    <Container colorMode={{ "@initial": "light", "@bp1": "light" }}>

Expected background-color: rgb(255 250 126)

    </Container>

To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Go to CodeSandbox

Expected behavior
The initial variant should be applied, even it is the same for all breakpoints variants.

@hadihallak Toggling between variants all seems to not be applied correctly. I believe this is due to duplicate class names being removed.
Eg:
  <Container colorMode={{ "@initial": "light", "@bp1": "dark", "@bp2": "light" }}>

Expected Background color: rgb(255 250 126)

  </Container>

@DevinEdwards  Not sure I fully understand this, would you be able to share a new codesandbox

Sure thing @hadihallak. I forked the above and added extra breakpoints to illustrate the issue.
Codesandbox
Repeating responsive variants at different breakpoints doesn't work. From my perspective, Stitches relies on the ordering of class names for the specificity of responsive variants, and the duplicate class names are being stripped out.
For the record Stitches is amazing, and really appreciate all the time and effort that has been put into it. 🙏🏼

Hi @hadihallak, this is the message I sent you in Discord - I think you were able to pinpoint the issue then as you pointed me to this thread!
Message link reference: https://discord.com/channels/752614004387610674/752795957674115092/989805725205291068
Message Content:
For example: <Grid columns={{ "@initial": 2, "@bp1": 1, "@bp2": 2 }}>
✅ @bp1  - children items are laid out as 1 column
✅ @bp2  - children items are laid out as 2 columns. This also validates that 2 columns works.
❌ @intial - the code of the variant is simply not applied. Columns are not applied as indicated.
Here is a codesandbox to easily see the issue. @bp1 starts at 100px, @bp2 starts at 200px. https://codesandbox.io/s/stitches-forked-tbwxcx?file=/src/App.js:929-992

@DevinEdwards Thanks! really appreciate the support 🙏
Looks like you ended up linking the same codesandbox of the original issue by a mistake in your comment so would be helpful if you fix that

@DevinEdwards Thanks a lot for the updated link — it adds so much more context to this bug 🙏
I'm rewriting the internal sheet implementation of stitches and there is a very high chance this bug will automatically be fixed and be a s part of the 2.0 release.
Will keep you all updated in this issue once the fix is confirmed

Hi @hadihallak, any news?


Is this project still maintained?

This project still has activity.  I see @matthew-andrews commenting as recently as 8 days ago.  However, the master branch has not been touched in nearly a year.
The releases page shows the most recent release, v2.1.1, was published nearly 2 years ago.  npmjs.com shows the most recent release of 2.2.1 a year ago.
Additionally, there are 8 open pull requests, and many have been opened for a year or almost 2.
I'm not trying to beat up @matthew-andrews and appreciate the work that has gone into this project.  I just am wary about including something in my projects without understanding the current state of the project.
I suggest at the very least cleaning up the PRs.  Close out old ones that will never be merged, and deal with the ones that are left either with discussion or merging them in.

@matthew-andrews do you need help maintaining this project? Is there any way we can help?
Thanks,
@fesebuv

Hi folks … sorry for the slow reply.
The project was always maintained to the point of being usable for the projects of which I was responsible.
There was a time when all the issues on this project seemed to be “fix this in order to allow react native to work”. I thought and still think react native is not a good direction for the web and didn't want to proactively support it. This was my small protest.
I was kindly prompted to have a look at this project again by someone emailing me about a minor security issue in a dependency it was bringing in yesterday. Now since I have a bit more time, I have been tidying it up a little.
I would encourage people to test their projects against the master branch of this repo to make sure nothing has broken. I will release it as a major version soon.


Fix node breaking changes in proto

In this PR I propose a fix to the breaking changes brought by the changes to the node proto in this commit: https://github.com/0xPolygonMiden/miden-node/commit/db51f392257abcf2fd5a703a15b830e4d8a5f7ab

Failing clippy check but other than that, LGTM.

I am not sure what should be modified for this clippy warning to be removed. It's the code that you had previously.
It is linked to your clippy config in CI

Thank you! Looks good!
To fix the clippy error, let's bump up the min Rust version for all crates to 1.75. The new nightly version of clippy is now making these checks (when previously it wouldn't).
We may also want to specify this in relevant docs (e.g., in the readme file we list min supported Rust version).

Bumped. When you say "all crates" do you mean all Miden crates ( Base, Node, etc...) ?

Bumped. When you say "all crates" do you mean all Miden crates ( Base, Node, etc...) ?

Ah - there is only a single crate here. No - just miden-client crate is fine (in other repos, these are being bumped up already).


coredumping

On some OS's the C/C++ assert based images coredump when assert fails.
This can easily take longer than 10 seconds causing the [test] to time-out.
Hence you get a grey timed-out traffic-light and not a red traffic-light.

Fixed with [--ulimit core=0:0] in docker-run command.


CtsStatusCodeException: HTTP Error: 405 Method Not Allowed

Raygun report https://app.raygun.com/crashreporting/258s6a2/errors/77623468638 has more details about the error

HTTP Error: 405 Method Not Allowed is returned (and logged) upon every HTTP HEAD request. Our app is not configured to respond to HEAD requests; doing so would require adding an [HttpHead] attribute to controllers in addition to [HttpGet].
I've identified three sources for HEAD requests (so far):

Links (e.g., password reset, account confirmation) embedded in emails are scanned by Outlook. (See Safe Links - Office 365 | Microsoft Docs.)
Links embedded in an Excel spreadsheet are checked to confirm they exist before opening a browser ("User-Agent": "Microsoft Office Excel 2014").
An unknown bot identifying itself as "Firefox/3.6.28"!?

The bot can be ignored.
Links in emails and in Excel trigger crash reports in Raygun but still work. It's probably a good thing that emailed links fail, since processing them would invalidate embedded tokens. (See Magic links don't work when Outlook "safe links" are enabled · Issue #629 · FusionAuth/fusionauth-issues.) But if this starts to cause Microsoft to block those links, the code can be rewritten to allow HEAD requests, but not process the tokens. (Just return the correct status code.)


ENH: Audit EXISTS Docs

#826
CC @lucifercr07
Let me know if i missed anything. Happy to contribute.

@apoorvyadav1111 can you check now once


Use PHPUnit\Framework\TestCase instead of PHPUnit_Framework_TestCase

I use the PHPUnit\Framework\TestCase notation instead of PHPUnit_Framework_TestCase while extending our TestCases. This will help us migrate to PHPUnit 6, that no longer support snake case class names.
Just need to bump PHPUnit version to ^5.7 for compatibility.

Thanks!


#2: move verification integration repository to core repository

name: Pull request
about: Contribute your changes to the project
title: '[pull-request]'
labels: ''
assignees: ''
Description
Short description or comments
Reference
Issues #XXX
Checklist

[ ] Acceptance criteria are met
[ ] Pipeline has been run successfully
[ ] JUnit tests have been run successfully
[ ] Changelog is adjusted
[ ] Documentations are completed
[ ] Frontend is tested
[ ] Created sub-branches are deleted
[ ] Boards are updated ( Digitalisierung , Support , Zenhub )
[ ] feature process is created or extended
[ ] git-ops is customized
[ ] Openshift environments are prepared (Secrets, etc.)

CHANGELOG entry is missing


[Terminal v0.11.1121.0] "defaultProfile" section under 'globals' setting isn't working

Environment
Windows build number: Microsoft Windows NT 10.0.19041.0
Windows Terminal version: 0.11.1121.0

Steps to reproduce

Open settings.json file ad go to "defaultProfile" section present under "globals".
set "defaultProfile": "{c6eaf9f4-32a7-5fdc-b5cf-066e8a4b1e40}" . c6eaf9f4-32a7-5fdc-b5cf-066e8a4b1e40 is the guid of wsl ubuntu 18.04 present under profiles section.
Now close and open the terminal and still it is opening powershell terminal instead of ubuntu 18.04.
Windows got updated to KB4558244 and Terminal to 0.11.1121.0. Everything was fine before these updates.

Expected behavior
If deafultProfile is set to wsl Ubuntu 18.04 guid then it should open the ubuntu 18.04 distro(I'm using Ubuntu 18 only) not Powershell eveytime.
Actual behavior
defaultProfile is set to wsl ubuntu 18.04 guid and it is opening powershell.
PFA the screenshots.

The Globals section was removed, and the settings format has changed

Thanks for the report! 0.11 introduced some breaking settings changes which is probably causing this issue for you. This is tracked by another issue on our repo - please refer to #5458 for more discussion.
/dup #5458


Can't get WebhookPublisher to successfully send JSON payload to AWS API Gateway

Describe the bug
I wanted to inspect the payloads of events that would be sent out to an outbound webhook. I created a simple AWS API gateway that accepts a POST with a json payload, logs it, and returns it as well in the response.
This works great with curl.
curl -X POST -H "Content-Type: application/json" -d '{"foo": "bar"}' https://nix213jk8a.execute-api.us-east-2.amazonaws.com
{"foo": "bar"}

But when I try to use it with the notification configuration it just fails when trying to send notifications through the API server.
2023-06-20 15:35:10,766 ERROR [WebhookPublisher] An error was encountered publishing notification to Outbound Webhookwith HTTP Status : 403 Forbidden Destination: https://nix213jk8a.execute-api.us-east-2.amazonaws.com Response: {"message":"Forbidden"}

Version of dependency-check used
The problem occurs using version 4.8.0 of the api server.
Log file
Recent logs: https://gist.github.com/jesseadams/62889214435dd8c10c4880af91c1cb97
To Reproduce
Steps to reproduce the behavior:

Configure an outbound webhook alert using org.dependencytrack.notification.publisher.WebhookPublisher with the correct API gateway URL
Submit an SBOM to process and wait for it to completely process, thus generating notifications.
See lambda executions with the payload in the AWS CloudWatch log console

Expected behavior
I would expect to see the payloads showing up in the CloudWatch logs of the lambda, just like when I send manual tests via curl requests.
Additional context
I feel like I am just missing something really simple, but the documentation is pretty basic.
https://docs.dependencytrack.org/integrations/notifications/#outbound-webhooks

@jesseadams You're in the wrong github. DependencyTrack is at https://github.com/DependencyTrack/dependency-track


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/290 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit 8685dbf:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-01-14-01-42-13 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-01-14-01-42-13

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[ pthreads:x64-windows] build failure

Host Environment

OS: WIN 10
Compiler: Vcpkg version: 2021-09-10-2059ef11aa6067e6f59b0d939c5d17e3c5c47d3e

To Reproduce
Steps to reproduce the behavior:
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:127 (message):     Command failed: "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/nmake.exe" -f Makefile all install DESTROOT="C:\\Users\\DUMA\\darknet\\vcpkg\\packages\\pthreads_x64-windows"
Failure logs
`Detecting compiler hash for triplet x64-windows...
The following packages will be built and installed:

bzip2[core]:x64-windows -> 1.0.8#2
cuda[core]:x64-windows -> 10.1#8
cudnn[core]:x64-windows -> 7.6.5#4
ffmpeg[avcodec,avdevice,avfilter,avformat,core,swresample,swscale]:x64-windows -> 4.4#14
giflib[core]:x64-windows -> 5.2.1
hdf5[core,szip,zlib]:x64-windows -> 1.12.0#4
leptonica[core]:x64-windows -> 1.81.1
libarchive[bzip2,core,libxml2,lz4,lzma,openssl,zstd]:x64-windows -> 3.5.2#1
libiconv[core]:x64-windows -> 1.16#11
libjpeg-turbo[core]:x64-windows -> 2.0.6#2
liblzma[core]:x64-windows -> 5.2.5#3
libpng[core]:x64-windows -> 1.6.37#15
libwebp[core,nearlossless,simd,unicode]:x64-windows -> 1.1.0#4
libxml2[core]:x64-windows -> 2.9.12#4
lz4[core]:x64-windows -> 1.9.3#3
opencv[contrib,core,dnn,ffmpeg,jpeg,png,quirc,tiff,webp]:x64-windows -> 4.5.3
opencv4[contrib,core,dnn,ffmpeg,jpeg,png,quirc,tiff,webp]:x64-windows -> 4.5.3#2
openjpeg[core]:x64-windows -> 2.3.1#4
openssl[core]:x64-windows -> 1.1.1l#1
protobuf[core]:x64-windows -> 3.18.0
pthreads[core]:x64-windows -> 3.0.0#10
quirc[core]:x64-windows -> 1.1#2
stb[core]:x64-windows -> 2020-09-14#1
szip[core]:x64-windows -> 2.1.1#7
tesseract[core]:x64-windows -> 4.1.1#8
tiff[core,jpeg,lzma,zip]:x64-windows -> 4.3.0#1
vcpkg-cmake[core]:x64-windows -> 2021-09-13
vcpkg-cmake-config[core]:x64-windows -> 2021-05-22#1
vcpkg-pkgconfig-get-modules[core]:x64-windows -> 2021-04-02#1
zlib[core]:x64-windows -> 1.2.11#12
zstd[core]:x64-windows -> 1.5.0
Additional packages (*) will be modified to complete this operation.
Restored 0 packages from C:\Users\DUMA\AppData\Local\vcpkg\archives in 741.3 us. Use --debug to see more details.
Starting package 1/31: pthreads:x64-windows
Building package pthreads[core]:x64-windows...
-- Downloading https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=cfhcable;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=pilotfiber;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=gigenet;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=versaweb;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=ayera;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=netactuate;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=phoenixnap;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=astuteinternet;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=freefr;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=netcologne;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=deac-riga;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=excellmedia;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=iweb;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=jaist;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=jztkft;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=managedway;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=nchc;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=netix;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=ufpr;https://sourceforge.net/projects/pthreads4w//files/pthreads4w-code-v3.0.0.zip/download?use_mirror=tenet -> pthreads4w-code-v3.0.0.zip...
-- Cleaning sources at C:/Users/DUMA/darknet/vcpkg/buildtrees/pthreads/src/49e541b66c-53502e357c.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Users/DUMA/darknet/vcpkg/downloads/pthreads4w-code-v3.0.0.zip
-- Applying patch fix-arm-macro.patch
-- Applying patch use-md.patch
-- Using source at C:/Users/DUMA/darknet/vcpkg/buildtrees/pthreads/src/49e541b66c-53502e357c.clean
-- Building x64-windows-rel
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:127 (message):
Command failed: "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/nmake.exe" -f Makefile all install DESTROOT="C:\Users\DUMA\darknet\vcpkg\packages\pthreads_x64-windows"
Working Directory: C:/Users/DUMA/darknet/vcpkg/buildtrees/pthreads/src/49e541b66c-53502e357c.clean
Error code: 2
See logs for more information:
C:\Users\DUMA\darknet\vcpkg\buildtrees\pthreads\nmake-build-x64-windows-release-out.log
C:\Users\DUMA\darknet\vcpkg\buildtrees\pthreads\nmake-build-x64-windows-release-err.log

Call Stack (most recent call first):
ports/pthreads/portfile.cmake:38 (vcpkg_execute_required_process)
scripts/ports.cmake:140 (include)
Error: Building package pthreads:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: pthreads:x64-windows
Vcpkg version: 2021-09-10-2059ef11aa6067e6f59b0d939c5d17e3c5c47d3e
Additionally, attach any relevant sections from the log files above.`
Additional context
i am trying build the darknet library https://github.com/AlexeyAB/darknet
Here are their compile  instruction
Set-ExecutionPolicy unrestricted -Scope CurrentUser -Force
git clone https://github.com/AlexeyAB/darknet
cd darknet
.\build.ps1 -UseVCPKG -EnableOPENCV -EnableCUDA -EnableCUDNN

@nhanminhnhat1998, could you attach the failure logs?
C:\Users\DUMA\darknet\vcpkg\buildtrees\pthreads\nmake-build-x64-windows-release-out.log
C:\Users\DUMA\darknet\vcpkg\buildtrees\pthreads\nmake-build-x64-windows-release-err.log

my bad .

nmake-build-x64-windows-release-out.log:
nmake-build-x64-windows-release-out.log

nmake-build-x64-windows-release-err.log
nmake-build-x64-windows-release-err.log

vcpkg-manifest-install.log

@nhanminhnhat1998, do you install windows sdk? if not, could you install it via VS installer and try again?
For me the errno.h file locates in C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\ucrt.
.\_ptw32.h(143): fatal error C1083: Cannot open include file: 'errno.h': No such file or directory

Hi PheobeHui,
I works thanks a lot. but i have another error, in term of downloading. I tried to turn of my firewall and anti virus. but it did not help. Not sure if I should create new issue.
Thank you for your help.
here are the files it tried to download
Error: Failed to download from mirror set:
https://www.nasm.us/pub/nasm/releasebuilds/2.15.05/win32/nasm-2.15.05-win32.zip: WinHttpSendRequest() failed: 12007
https://fossies.org/windows/misc/nasm-2.15.05-win32.zip: WinHttpSendRequest() failed: 12007
[DEBUG] D:\a_work\1\s\src\vcpkg\base\downloads.cpp(626)
[DEBUG] Exiting after 84.51 ms us (84439 us)


Display HORUS staked tokens (if HORUS is a tracked token)

Create a mechanism that can retrieve the staked HORUS balance from the specific table on the horustokenio contract. This staked balance should show alongside the HORUS liquid balance (like EOS) does.
Most likely we'll need our custom wallet contract activated before this is feasible.

This should get you the balance of 'total_staked_horus', which can be subtracted from the /get_currency_balance total HORUS to determine the liquid balance:
Note: 'scope' is the account name & 'code' is the contract name
POST /v1/chain/get_table_rows HTTP/1.1
Host: eos.greymass.com:443
Cache-Control: no-cache
Postman-Token: c509ca96-a1cd-4bfb-90d7-fcbcaf5a83b0
{
"scope": "horustokenio",
"code": "horustokenio",
"table": "userres",
"json": "true"
}
{
"rows": [
{
"owner": "horustokenio",
"total_staked_horus": "304000000.0000 HORUS"
}
],
"more": false
}


Microsoft.MachineLearningServices/workspaces/data/versions@2023-04-01-preview&2023-06-01-preview two variants have same x-ms-discriminator-value

API paths:
https://github.com/Azure/azure-rest-api-specs/blob/4cd95123fb961c68740565a1efcaa5e43bd35802/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-06-01-preview/mfe.json#L1623
https://github.com/Azure/azure-rest-api-specs/blob/4cd95123fb961c68740565a1efcaa5e43bd35802/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-06-01-preview/mfe.json#L5643
API version:

2023-04-01-preview
2023-06-01-preview

Two variants have same x-ms-discriminator-value= uri_folder:
https://github.com/Azure/azure-rest-api-specs/blob/4cd95123fb961c68740565a1efcaa5e43bd35802/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-06-01-preview/mfe.json#L14503-L14524
https://github.com/Azure/azure-rest-api-specs/blob/4cd95123fb961c68740565a1efcaa5e43bd35802/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-06-01-preview/mfe.json#L26073-L26083

@azure/aml-compute-instance take a look on this, thanks


URGENT - robyn_recreate() with JSON produces different model

Hi everyone, I have quite an urgent issue I would like your help with. I exported a JSON of a model I selected with a client. The JSON itself is fine, as you can see below (I included the first 5 variables for illustration).

When running robyn_recreate(), I produce a completely different model (see below). I would really appreciate your help on this!

I tested robyn_recreate() for another client. Results are again different, but this time not by much. Here is the original model's ROI:

Here is the recreated model's ROI:

sorry for the late reply. There's another thread/issue looking into this too, where we've fixed couple of bugs to close this gap. I just tested it and it looks good. Can you pls update to the latest github version and rebuild/retry?

I'm using the latest version and the issue still persists unfortunately, shall I send you the JSON + data for debugging?

Yes please<EMAIL_ADDRESS>

UPDATE: I found the cause of the biggest discrepancy (I forgot that I hard-coded the covid variable within InputCollect$dt_mod before running the model). The results are looking better now, but there is still a discrepancy (the output of robyn_recreate still differs from the original). Here are the ROI figures side by side:
ORIGINAL

RECREATED

Dear @gufengzhou, have you managed to find a cause of the issue? I appreciate the effort!

Hey sorry it's been quite busy. I found out that the recreated model has hyperparameters rounded to 4 digits, while the initial one doesn't. But still need to figure out where the rounding is from. will update here once we made progress. @laresbernardo FYI


[RFC] Fix update guid

I tried creating tests for the update paths but it seems that all InitialCreateScript versions were to same up until this release.
Yet the upgrade fails when going from 1.2.0 to the latest version. I must be missing something.
I used following script to get all the release InitialCreateScript versions that were released:
#!/usr/bin/env bash

set -e
set -u

while IFS= read -r info; do
	sha=${info%% *}
	tag=${info##*/}
	echo "sha ${sha:0:6} tag $tag"
	while IFS= read -r script; do
		if ! [[ $script =~ "SqlServer" ]]; then
			echo "i $script"
			git checkout -f $sha
			filename=$(basename $script)
			ext=${filename##*.}
			mv $script "./${filename%.*}_${tag}_${sha:0:6}.$ext"
		fi
	done < <(git ls-tree -r --name-only $sha | grep -i InitialCreateScript.cs)
done < <(git show-ref --tags)

Awesome, that fixes the issue. I couldn't spot the trailing comma :)

@willdean  Can you have a look why this is failing? It's in the push to create test. Completely unrelated to my changes. Probably some odd timing thing again...

I'll take a look - this has been failing intermittently for ever.  I thought I might have fixed it by waiting for completion on the options post, but it appears that isn't enough.

@willdean @jakubgarfield I reordered the update scripts with this patch to keep update working from older versions.
Now it will only insert the inital data after all updates have been done.
Please have a look and commit if you think it is ok.

@RedX2501  - The add-administrator stuff was broken for SqlServer.
Can you think of any reason why the code to add an administrator has to be hand-coded Sql?  Could we not just add it using the membership service, which could then be common to Sqlite/sqlserver and would be far cleaner code?

I guess that before our Introduction of DoAction all update scripts had were strings.
I think we could change it now. I think that's stuff for a new PR for 6.1?

@willdean Can we merge this?

@RedX2501  - I think so.


Fix Known Test Failures 🐞 🔧 🚶

Bug fix
Details

Version
Severity

v0.0.1
3 Incorrect Behavior

Description
7 unit tests are marked as known failures. The should be fixed
Steps to Reproduce

Run: npm test

Defective Behavior
Out put shows 7 known failures
Desired Behavior
All tests pass as designed.

Completed by #104


documentation - broken link to the protocol page

see https://github.com/memcached/memcached/wiki/Commands , there's a broken link to "Protocol Documentation". it points at "NewProtocols", should probably be "Protocols" instead

Fixed, thanks!


[UI/UX] Title Enhancing the footer of the webpage

The current footer design could benefit from enhanced responsiveness and modern styling. This issue aims to implement a grid-based, responsive layout, ensuring optimal display on various screen sizes. Additionally, improved styling and hover effects are requested for better user interaction.

kindly assign me under hacktoberfest 2024

Hi @devlohani99  this is just a template repo to fork and raise a PR
Checkout repos here to contribute that counts towards hacktoberfest  and join discord for more discussions


dimension names with .'s

question from @coccyx:
I thought we removed all .'s from dimension names? I still see http.target was that an omission?

I see http.status and http.target still with .'s in the dimension name.

@jrcheli is this the only place where these fields are set:

@ledbit, @coccyx Yeah.  This looks straightforward.
My testing for this to see if I'm missing others:
find . -type f | xargs egrep "(NUMFIELD)|(STRFIELD)" | cut -d\: -f2 | cut -d\" -f2 | sort | uniq | grep "\."

The only two hits for this are "http.status_code" and "http.target", both in src/httpagg.c.  My other worry about needing to untangle metrics and events was not well founded.  This .c file only sends metrics.  There should be no risk of modifying event output with this change.


replace exp list --all with --all-commits

dvc exp list --all has been replaced by dvc exp list --all-commits (the former still works but is an undocumented alias).

🚩 Your build failed. See the build logs here

Updating this branch with the latest version of master should fix the build!


Action to close the popup

Currently I must click Esc to exit the dialog popup. This is kind of out of the way, and I would prefer if we could map this to a different key.
Either an extra Action that I can bind in my .ideavimrc, a setting I can change in the the HarpoonIJ settings. Or most preferably just bind exit to q while I'm inside of the popup (how it works in the original harpoon).
Love the plugin, use it daily.

Unfortantly I don't have much time to work on this right now but i would be open to a PR if someone wants to add this feature


⚠ Processors has degraded performance

In 3decbd5, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 103 ms

Resolved: Processors performance has improved in 93e074f.