Make this flexible to let someone list multiple evaluations

https://github.com/LemmaLegalConsulting/docassemble-StudentEvaluations/blob/9124749346a007273b266ff5f0498ae969774ecd/docassemble/StudentEvaluations/data/questions/prs_complaint_interview.yml#L272-L302

Already complete. Remove TODO line 272


[Bug Report] Table components: When all checkbox is disable, table-header's checkbox can still click

Element UI version
2.2.0
OS/Browsers version
chrome 62
Vue version
2.5.13
Reproduction Link
https://jsfiddle.net/samuel666/mmx38qxw/361/
Steps to reproduce
Create a table.
Bind a attribute that name is 'selectable' and value is 'selectableFun'.
The function that name is selectableFun is 'return false';
What is Expected?
table-header's checkbox cann't click
What is actually happening?
table-header's checkbox can still click

This is a tradeoff against having to call selectable functions multiple times, which can be a performance issue.
Since the current behavior doesn't break anything, and clicking the header's checkbox doesn't trigger selection-change, we may keep it as is.


HTML.tmLanguage file needs to be updated

See http://www.sublimetext.com/forum/viewtopic.php?f=2&t=18613&start=30#p68931
Also: http://www.sublimetext.com/forum/viewtopic.php?f=2&t=18634

Thanks for this! I will need to double check but it may be unnecessary to include both syntax files anymore. Which would help relieve this issue further. Added this to the June Sprint.

Instead of forking and injecting a fixed syntax, you could also fork the official package and patch that.
https://github.com/sublimehq/Packages


chore(nuxt.new): Typo in assets screenshot

I'm a bit lost. Is there anything else on my part to be done? 🔥💚


Added Prometheus IMetricResponseWriter for ascii and protobuf

removed net452 target because it wasn't compiling with AppMetrics.Extensions.Middleware package
Also why do we need App.Metrics.Extensions.Reporting.Prometheus project?

That's fine re the net452 target, I've removed support on middleware for now, if there are requests for support I'll revisit, not worth the effort at the moment.
App.Metrics.Extensions.Reporting.Prometheus would be to push metrics to prometheus, I understand you'll be configuring prometheus to pull from an API. I can revisit the push at a later date if you're not interested in that.

Pushing metrics to prometheus is quite an edge case. First of all you can't even do it directly, you have to run https://github.com/prometheus/pushgateway as standalone app and configure prometheus to scrape from it. The idea is that you will use it only for short lived jobs. But the thing is that the project is almost unmaintained.
I am pretty sure that no one will even ask for it

Oh right, in that case, won't bother ;)
What's their visualization like? Or do ppl use grafana mostly?

grafana 100%

OK cool, I'm adding a sanbox project to your branch, any chance you could add a grafana dashbboard demo to the repo using some metrics recorded by that project and some setup instructions to the readme re prometheus?

I can't promise anything but I'll try to find some time

Never mind, for the grafana demo I guess it makes sense to use the "generic" dasboard I've used for other reporters


feature: kubean helm need add a logo

as title described, a logo is needed

/kind feature

https://github.com/kubean-io/kubean-helm-chart/blob/main/charts/kubean/Chart.yaml#L22
Logo added.


npm update?

Hey Osei,
Would you mind pushing an update to npm? I'd love to use the unzipWithProgress feature since the other one doesn't return a promise when done (I need to know when unzipping is done..).
Thanks!

Sure :)

Done 1.2.1

Lovely, thanks!

Just to add: works perfectly! (only tested iOS)


⚠ ClamAV has degraded performance

In 449165a, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 419 ms

Resolved: ClamAV performance has improved in 34618aa.


Is there any way I can use Swashbuckle to generate Swagger UI/Doc for already deployed app?

We have a already deployed web api application. Is there any way we can use Swashbuckle to generate Swagger UI/Doc for already deployed app. Consider we do not have option to again build thoes application.

It's not really an intended use-case and so you would have to jump through a lot of hoops to get it working. Generating the corresponding docs in a separate process - so, long as you have access to the DLL's, it's essentially not very different from what the SB tests do - https://github.com/domaindrivendev/Swashbuckle/tree/master/Swashbuckle.Tests.
Have you considered not using SB and manually creating a static swagger.json file for your API. You could then host this, along with the swagger-ui (https://github.com/swagger-api/swagger-ui) in a separate static website.

I am new to SB and swagger. So, kindly suggest ho do I do it i.e. generate swagger.json without SB from my API?


Git ignore package-lock.json

We already use npm-shrinkwrap, so it will be ignored anyway.

I love you


[deps] fix: update deps

Update the following deps:

rocksdb to 7.7.3
benchmark to 1.7.1
mongo-c-driver to 1.22.2
mongo-cxx-driver to 3.7.0
cppzmq to 4.9.0

Added zlib dependency to mongo-c-driver test due to the openssl update to 3.0.7 remove it.

can you check if we can replace any of these with public packages as part of this update?

can you check if we can replace any of these with public packages as part of this update?

OK. I will switch them to the public packages but the main lost would be rpath support. There are also some Windows specific changes. The other downside is that the public version are not the latest release.

if our changes are needed (for win or mac or nix) we should keep using custom packages, but if they have been incorporated into main packages (as some have been in the past ) we should prefer those.


Fix: proper HTTP codes for REST API endpoint to retrieve cluster report

Description
Fix: proper HTTP codes for REST API endpoint to retrieve cluster report
Fixes https://issues.redhat.com/browse/CCXDEV-11519
Type of change

Bug fix (non-breaking change which fixes an issue)

Testing steps
Can be tested locally by providing unknown cluster, cluster name with improper format, organization with improper format etc.
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report
Patch coverage has no change and project coverage change: -0.02% :warning:

Comparison is base (6971163) 4.38% compared to head (4d25706) 4.36%.

Additional details and impacted files
@@            Coverage Diff            @@
##           master    #406      +/-   ##
=========================================
- Coverage    4.38%   4.36%   -0.02%
=========================================
  Files          15      15
  Lines        1118    1123       +5
=========================================
  Hits           49      49
- Misses       1069    1074       +5

Files Changed
Coverage Δ

server/handlers.go
0.00% <0.00%> (ø)

storage/storage.go
1.04% <0.00%> (-0.02%)
:arrow_down:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Text corrections in toast-ux-guidance.md

@mijacobs  : PR passed acceptance checklist. Please evaluate further and approve/merge if appropriate. Thanks!


Print testfile content for debugggin

i'm not really in favour of this as it will spam the logs with a huge amount of data that we could get by looking at the template file itself.

This change helped me in really making sure that I got the scenario input correct. This change adds 3912 lines to the output and makes is 6.4% larger. That's not too bad 😉
wc -l main.output debug_testfile.output
   61367 main.output
   65279 debug_testfile.output
  126646 total

another option would be to add a new envvar similar to TESTS_LOG_LEVEL_DEBUG so that this can be enabled optionally.

Yes, that would work as well. Let me work on this.

Looks good. Commit msg could do with a tidy up and maybe also a comment about the new env var.

Done.


Added test for UpdateTaskList

What changed?
Added Unit tests

Why?
Code coverage

How did you test it?

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 018fa4b2-cf81-4f7c-8c44-a00664671260
Details

0 of 0   changed or added relevant lines in 0 files are covered.
61 unchanged lines in 16 files lost coverage.
Overall coverage decreased (-0.02%) to 69.284%

Files with Coverage Reduction
New Missed Lines
%

common/task/weighted_round_robin_task_scheduler.go
2
89.05%

common/task/parallel_task_processor.go
2
93.06%

service/matching/tasklist/db.go
2
73.23%

common/persistence/execution_manager.go
2
86.43%

service/matching/tasklist/task_list_manager.go
2
76.09%

common/task/fifo_task_scheduler.go
2
85.57%

common/persistence/sql/sqlplugin/mysql/task.go
2
73.68%

service/history/task/transfer_active_task_executor.go
2
72.72%

common/persistence/sql/sqlplugin/mysql/db.go
2
79.49%

common/log/tag/tags.go
3
50.46%

Totals

Change from base Build 018fa464-40c9-4742-b88d-967555b43b81:
-0.02%

Covered Lines:
102080

Relevant Lines:
147336

💛  - Coveralls


fix(#654): --prebuild-tag-prefix option cannot be empty

Any ideas why it failed only on Windows ? because it looks like a CI issue to me..
Maybe someone can just rerun the test ?
Thanks

@MarshallOfSound, I can see that you closed this PR because you renamed master branch to main, so do I need to resubmit it ? And would you accept it this time ? since you gave no answers to that for about 2 years...
Thanks


another update

(also a lot of commits from master, only this one has my changes: https://github.com/chrisbarnettster/training-material/commit/aff4012f9a90399b08b615d84b97543f096fc670)

ping @chrisbarnettster, @tsenapathi


Recursive children

cc @jojolepro @Moxinilian
This adds a helper function to get all the children of an entity recursively.

This change is

@Rhuagh can you elaborate on how the vec is sorted?  I'm not super clear on that.

For example let's say I have
Parent <- Child
e1 <- e2
e3 <- e4
So then would the vec be sorted [e1, e2, e3, e4]?  If so what signals to me that I need to stop at e2?

r? @Rhuagh

r? @jojolepro

@Rhuagh please do a cargo publish post merge.

Bors r+


Update Barcode Scanner Compatibility

Updated document structure to capture a single list of compatible devices and provide a consolidated support summary

@TerryWarwick,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


docs: Add tutorial with program derived address.

Signing with a program is pretty confusing for people using solana for the first time. Not really specific to Anchor but a useful example nonetheless.

This should be extended into an entire tutorial providing intuition + design patterns for using program controlled accounts + seeds + associated accounts.

I found this guide that briefly goes of PDAs: https://paulx.dev/blog/2021/01/14/programming-on-solana-an-introduction/
Still would like something more clear.

theres a chapter in the anchor book about it now so Im closing this issue


Flutter 1.22, FlutterFire, and Xcode 14 complains about IPHONEOS_DEPLOYMENT_TARGET

I'm in the process of building out a codelab for FlutterFire https://github.com/flutter/codelabs/pull/20
With Xcode 14, I'm seeing a new error:
warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target
    'Firebase' from project 'Pods')

We have set the minimum iOS version to 9.0 in a variety of places, but the generated ./ios/Pods/Pods.xcodeproj/project.pbxproj has a bunch of lines that match IPHONEOS_DEPLOYMENT_TARGET = 8.0;
Any chance of updating the template ios/Podfile that we generate to set iOS 9? The following line is at the top of file, but it is currently commented out.
platform :ios, '9.0'

This is actually a pretty old problem (that's why the comment you uncommented was originally added https://github.com/flutter/flutter/pull/4893/files#diff-3484408d815583a1721faee188827c45R5), and is a duplicate of https://github.com/flutter/flutter/issues/40109 and I guess I shouldn't have closed that one.  I'll reopen it and duplicate this over there since it already has history.
CocoaPods discussion: https://github.com/CocoaPods/CocoaPods/issues/7314
Please see previous attempts to do this and discussion around it:
https://github.com/flutter/flutter/pull/36117
https://github.com/flutter/flutter/issues/40109#issuecomment-529691520

Duplicate of #40109

I had the same problem, but a simple flutter clean fixed it for me. In my case, I think it occurred because I updated XCode and Flutter.

@jmagman, so what was being done really?

The fix explanation is in https://github.com/flutter/flutter/pull/66590.  It is available in the master channel.


react-native-lottie package always throw error when updated macos operation system to Catalina 10.15.4

Description
i'm using long time react-native-lottie package in my project. But yesterday, i'm updated my macos operation system to Catalina 10.15.4 version and always throw below error when run react-native run-ios command.
Steps to Reproduce

Open the iTerm app.
runned react-native run-ios  command in iTerm from react-native project directory.

Expected behavior: Running my react-native application in simulator or device.
Actual behavior:
CompileSwift normal x86_64 /Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/node_modules/lottie-react-native/src/ios/LottieReactNative/ContainerView.swift
    cd /Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift -frontend -c "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/node_modules/lottie-react-native/src/ios/LottieReactNative/AnimationViewManagerModule.swift" -primary-file "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/node_modules/lottie-react-native/src/ios/LottieReactNative/ContainerView.swift" -emit-module-path "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/Objects-normal/x86_64/ContainerView~partial.swiftmodule" -emit-module-doc-path "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/Objects-normal/x86_64/ContainerView~partial.swiftdoc" -emit-module-source-info-path "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/Objects-normal/x86_64/ContainerView~partial.swiftsourceinfo" -serialize-diagnostics-path "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/Objects-normal/x86_64/ContainerView.dia" -emit-dependencies-path "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/Objects-normal/x86_64/ContainerView.d" -emit-reference-dependencies-path "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/Objects-normal/x86_64/ContainerView.swiftdeps" -target x86_64-apple-ios9.0-simulator -enable-objc-interop -sdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator13.4.sdk -I "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Products/Debug-iphonesimulator/lottie-react-native" -I "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Products/Debug-iphonesimulator/lottie-ios" -F "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Products/Debug-iphonesimulator/lottie-react-native" -enable-testing -g -import-underlying-module -module-cache-path "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/ModuleCache.noindex" -swift-version 4.2 -enforce-exclusivity=checked -Onone -D DEBUG -D COCOAPODS -serialize-debugging-options -Xcc -working-directory -Xcc "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods" -enable-anonymous-context-mangled-names -Xcc "-fmodule-map-file=/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Products/Debug-iphonesimulator/lottie-ios/Lottie.modulemap" -Xcc "-fmodule-map-file=/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods/Headers/Public/lottie_react_native/lottie-react-native.modulemap" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/swift-overrides.hmap" -Xcc -iquote -Xcc "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/lottie-react-native-generated-files.hmap" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/lottie-react-native-own-target-headers.hmap" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/lottie-react-native-all-non-framework-target-headers.hmap" -Xcc -ivfsoverlay -Xcc "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/all-product-headers.yaml" -Xcc -iquote -Xcc "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/lottie-react-native-project-headers.hmap" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Products/Debug-iphonesimulator/lottie-react-native/include" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods/Headers/Private" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods/Headers/Private/lottie-react-native" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods/Headers/Public" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods/Headers/Public/DoubleConversion" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods/Headers/Public/React-Core" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods/Headers/Public/React-RCTBlob" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods/Headers/Public/React-RCTText" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods/Headers/Public/React-cxxreact" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods/Headers/Public/React-jsi" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods/Headers/Public/React-jsiexecutor" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods/Headers/Public/React-jsinspector" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods/Headers/Public/Yoga" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/Pods/Headers/Public/glog" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/DerivedSources-normal/x86_64" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/DerivedSources/x86_64" -Xcc "-I/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/DerivedSources" -Xcc -DPOD_CONFIGURATION_DEBUG=1 -Xcc -DDEBUG=1 -Xcc -DCOCOAPODS=1 -module-name lottie_react_native -o "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/Objects-normal/x86_64/ContainerView.o" -index-store-path "/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Index/DataStore" -index-system-modules
/Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/node_modules/lottie-react-native/src/ios/LottieReactNative/AnimationViewManagerModule.swift:5:8: error: module compiled with Swift 5.1.3 cannot be imported by the Swift 5.2 compiler: /Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/ios/build/Perfx/Build/Products/Debug-iphonesimulator/lottie-ios/Lottie.swiftmodule/x86_64-apple-ios-simulator.swiftmodule
import Lottie
       ^

** BUILD FAILED **

The following build commands failed:
	CompileSwift normal x86_64 /Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/node_modules/lottie-react-native/src/ios/LottieReactNative/AnimationViewManagerModule.swift
	CompileSwift normal x86_64 /Users/muratoner/Desktop/Sabancı Projects/Mobile/HRNext/node_modules/lottie-react-native/src/ios/LottieReactNative/ContainerView.swift
	CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler
(3 failures)

Versions
npm: 6.14.2
macOS: Catalina 10.15.4
react-native: 0.61.3
react-native-cli: 2.0.1
lottie-ios: 3.1.3
lottie-react-native: 3.3.2

Same issue.

tried change Build System to Use Shared Setting

@muratoner did you solve the problem? if yes how?

@ibrahimyolbir i couldn't remember how i solved it because tried different methods.

Try this one to clear cached data.
rm -rf ~/Library/Developer/Xcode/DerivedData


Apply Isolation Tabs accross list views

Before we only had this applied to the list view, but as this is desired across the site, I have removed the prop and made it the default.
The functionality was already present. We just need to ensure the setting is set in the corresponding environments.

misunderstood ticket


Iterate a range of numbers defined by a variable

Hello,
First of all thanks for this nice repo :+1:
In the "do not use seq" part you recommend to use the bash built-in range expression which is not straightforward compatible with variables since it works with literals.
Then, is there a best option ? || which of those two options is the best:

use the external seq such as: for i in seq 1 ${END}; do;
use bash built-ins eval and echo such as: for i in $(eval echo "{1..$END}"); do but requires a fork() for substitution.

Hi @denaitre,
Thanks for your feedback.
As far as I understand it's possible to use brace expansion for these: http://wiki.bash-hackers.org/syntax/expansion/brace
I'm currently very busy. Would you mind opening a pull request with your suggested changes?

any update?


V1.4 features checking

Changes Unknown when pulling 8906d0b03110a7059e50ec39b5c076c61a2266b0 on v1.4Features into ** on master**.

Changes Unknown when pulling<PHONE_NUMBER>c984ad0ed88d1c4f483b69eaa5751f on v1.4Features into ** on master**.

Changes Unknown when pulling 83cbd25db6e71e865f1fa0532ecbc03d8c880920 on v1.4Features into ** on master**.

Changes Unknown when pulling e4ea8cb3865594e65e18f9e53e7d20d21dc36da0 on v1.4Features into ** on master**.

Changes Unknown when pulling 60f400f120125bbfc97ccb9bdbf94f9d408ee75b on v1.4Features into ** on master**.

Changes Unknown when pulling 39c0808110e044a80d61aa4a81985516f68b1206 on v1.4Features into ** on master**.

Changes Unknown when pulling 39c0808110e044a80d61aa4a81985516f68b1206 on v1.4Features into ** on master**.

Coverage decreased (-1.3%) to 91.497% when pulling c2af231aaaec627f6e18249828737e806482e153 on v1.4Features into a6b4f07e78bf5099c22a8ea4ec20ce36998cf7e6 on master.

Coverage decreased (-1.3%) to 91.497% when pulling 9a3a963d8ab5dfce3b36986d581f815f5aeb0db4 on v1.4Features into a6b4f07e78bf5099c22a8ea4ec20ce36998cf7e6 on master.

Coverage decreased (-1.3%) to 91.497% when pulling 09e38a9dd3ffde9b22c24faecad93bc659e017a9 on v1.4Features into a6b4f07e78bf5099c22a8ea4ec20ce36998cf7e6 on master.

Coverage decreased (-0.7%) to 92.064% when pulling 54dde5cf317da647aaa2388bc70975f57e13f39a on v1.4Features into a6b4f07e78bf5099c22a8ea4ec20ce36998cf7e6 on master.

Coverage decreased (-0.6%) to 92.123% when pulling 6c7d9e80322e8d5cb299f266a05272dcd2a5ce10 on v1.4Features into a6b4f07e78bf5099c22a8ea4ec20ce36998cf7e6 on master.


damask: init at 0.1.3

Description of changes
Adds Damask, a GNOME app to change your wallpaper to the wallpaper of the day from Bing or various other online sources.
Things done

Built on platform(s)

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

[ ] Tested, as applicable:

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

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Please add damask to all-packages.nix


Add generator of solid images and save on the server

I found it interesting to create a method that creates a fake image directly on the server, this facilitates the manipulation of images of records in the database. The lorempixel.com site is a bit slow to download and create the images, large volumes of data becomes impractical to use the download feature.

Can you post examples of the generated images?

createImage($dir = 'storage/app', $width = 200, $height = 380, $fullPath = false, $word = "image generated with Faker")
createImage($dir = 'storage/app', $width = 640, $height = 480, $fullPath = false, $word = "image generated with Faker")
createImage($dir = 'storage/app', $width = 640, $height = 480, $fullPath = false, $word = null)
createImage($dir = 'storage/app', $width = 100, $height = 100, $fullPath = false, $word = null)

You can add other font colors and background, but to simplify for now the colors are fixed.

Thanks for your PR, but I'll pass on this one - I don't think it's a good idea to make Faker larger and less compatible just for an image generator, especially considering that there is already one available.
That being said, I recommend you to publish it as a standalone generator, that I could link to in Faker's README.


RedisTimeSeries :: Release new version with Align and GroupBy support

Please :)

https://github.com/dengliming/redis-modules-java/releases/tag/1.0.3


⚠ MBKM has degraded performance

In 61ed768, MBKM (https://mbkm.unmer.ac.id/) experienced degraded performance:

HTTP code: 200
Response time: 21383 ms

Resolved: MBKM performance has improved in f6838a4 after 4 minutes.


Define min/max values for input fields

Feature Description
Currently, users can enter huge numbers in editor fields (e.g., font size of 10,000). We should define sensible min/max values for each editor field and enforce them in the UI, including helpful text in case of invalid input.
Min/Max Values

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria
QA Instructions

For now, from a UX perspective let's just go with preventing users from entering values outside the defined min/max values. If a user enters/tries to enter a smaller/larger value, reset the field to the min or max allowed (e.g., I enter 150% in transparency then the editor auto resets it to 100%)

@o-fernandez, added some more fields to the spreadsheet, FYI.

Thanks @barklund and @o-fernandez for recent updates on the spreadsheet. I'm starting the technical stuff related, as soon as I have some stable proposal, I will sync up again here to check the final thoughts related to the values ranges.

@o-fernandez could you please confirm if the current values in the spreadsheet will be the final expected ranges? Also, I a few changes requests that need review cuz some of them are not reflecting correctly the current editor UI (e.g. text line height and letter spacing).

Updated, let's go with what's in the spreadsheet for now since we don't have any better guidance. @samitron7 @pbakaus @barklund for review if they'd like to make changes before this is wrapped up.

@o-fernandez mostly seems good, but I would not limit width/height to 10. Otherwise you can't create thin rectangle lines, something we found today is needed as workaround until we have lines / borders.

QA Instructions missing

@merapi Could you please add some thorough testing instructions here? I know you added some at #2255, but that covers only 1 element, and not everything from the linked spreadsheet.
By doing that you can also verify one last time that the implementation in #2255 matches the spreadsheet.

@csossi Last connected PR is now fixed, PTAL. Additionally, you can test other fields as listed here if they respect min/max values.

Note: you can now test this on master as I merged the PR prematurely. Didn't realize it had so many connected issues...

Tested on Master

am able to set font size less than 8
able to set line height less than .5
able to set letter space greater than 300%
able to set padding greater than 300

@csossi check now, master on QA was stale, I refreshed it (you need to change it back and forth to get the latest version of a given branch).

Verified in QA (Tested in Master)

1 Issue: I  can still add text and then shrink it in the canvas to be smaller than the min specified.
Will file a new issue for this - not a Beta blocker


redraw/redrawstatus does not flush window.

redraw or redrawstatus does not flush window in MacVim so users cannot recognize the current status by indicators like "Downloading [2/5]..." or whatever. Try https://gist.github.com/lambdalisue/94d14ff706a5627d64f5
So I add gui_macvim_flush() after ex_redraw and ex_redrawstatus in this commit.
It seems that the issue no longer exists with that commit but I am not familiar with Vim/MacVim source code so could anyone check the side-effect and fix this problem?
Thanks :-)

Could you test https://github.com/macvim-dev/macvim/pull/175?

Perfect. Thanks. I'm looking forward it to be merged ;-)

:confetti_ball:

Shouldn't this have been solved by using :redraw! instead of :redraw, rather than chaning MacVim source?
Plain Vim doesn't behave in the way that this commit (and #182) make MacVim behave.

Shouldn't this have been solved by using :redraw! instead of :redraw, rather than chaning MacVim source?

I don't think so. I tried redraw! but using redraw! in for loop makes screen blinking.
Vim help said.
							*:redr* *:redraw*
:redr[aw][!]		Redraw the screen right now.  When ! is included it is
			cleared first.
			Useful to update the screen halfway executing a script
			or function.  Also when halfway a mapping and
			'lazyredraw' is set.

So redraw and redraw! is a bit different.
I tinkg calling gui_macvim_flush_force after redraw or redrawstatus is a correct behavior.

but using redraw! in for loop makes screen blinking

But that's how plain Vim works.
Also, the flush_force version of this repair makes for a blinking cursor upon :redraw, when it didn't previously blink.

The docs show that :redraw isn't supposed to completely clear and then redraw the screen.  That's what :redraw! is for.

But that's how plain Vim works.

No. At least in Vim on Ubuntu, GVim on Ubuntu, or Vim on Mac, the screen does not blink when I call :redraw but redraw!. So you cannot use redraw! instead of redraw. It's different.
https://gist.github.com/lambdalisue/94d14ff706a5627d64f5

The docs show that :redraw isn't supposed to completely clear and then redraw the screen. That's what :redraw! is for.

No. :redraw! stands for to clear first. redraw should also redraw the screen whenever called as well but without clearing (thus the screen won't blink).
I'm not sure if calling gui_macvim_flush_force is a correct way but I'm sure that the previous behavior is way different from other Vim.

And actually I noticed that redraw! did not work as well in revision ddc5c14 the one before the fix.

No. :redraw! stands for to clear first. redraw should also redraw the screen whenever called as well but without clearing (thus the screen won't blink).

That's what I said.  :redraw is not for clearing first, :redraw! is for clearing first.

@chdiza your comment "Plain Vim doesn't behave in the way that this commit (and #182) make MacVim behave. " is useless. Please provide a concrete reproduction scenario like https://gist.github.com/lambdalisue/94d14ff706a5627d64f5.

At the very least, if I take that gist and :source it and run Test2, the behavor is different in MacVim and plain Vim.  In plain Vim (i.e., from github.com/vim/vim, /usr/local/bin -u NONE -N), I see the countdown from 99 echoed by single digits.  In MacVim (mvim -u NONE -U NONE -N) I see nothing at all echoed.  It should work in both MacVim and plain Vim.  If I run MacVim in the console, it behaves like plain Vim.

Now I got. Yes it seems an issue on redraw! but redraw.

It didn't do that prior to the flush tweaks.  I don't have time right now to see whether it was introduced in the flush or the force_flush change.

Expected behavior
Of https://gist.github.com/lambdalisue/94d14ff706a5627d64f5
Indicator is increasing 1 by 1 (E.g. Test: 1 -> Test: 2 -> ...) without blinking screen when Test 1 (redraw) is called.
Indicator is increasing 1 by 1 (E.g. Test: 1 -> Test: 2 -> ...) with blinking screen** when Test 2 (redraw!) is called.
Actual behavior
Just before the redraw fix
revision: ddc5c148e848ca3b6113af0f994678caeb3da0dd
Both Test1 and Test2 hung a bit and Test 99 is suddenly shown.
After the 1st redraw fix
revision: 2d3163f649caec70afcea3df950ba40eb40af568
Indicator is increasing 2 by 2 (Test: 1 -> Test: 3 -> ...) without blinking screen when Test 1 is called (almost correct behavior).
Nothing is shown when Test 2 is called.
After the 2nd redraw fix
revision: 05e488d36905b719a9f24a3047e511fec13b658e
Indicator is increasing 1 by 1 (Test: 1 -> Test: 2 -> ...) without blinking screen when Test 1 is called (correct behavior).
Nothing is shown when Test 2 is called.
My conclusion
Both redraw and redraw! were broken and only redraw was fixed with recent commits. So reverting the commits won't fix the problem and further workarounds are required I guess. But I'm not really familiar with the code of Vim nor MacVim so I have no idea how :-p
How did I change the revision (in case)
I add :revision => "xxx" to brew edit macvim and re-installed.
head "https://github.com/macvim-dev/macvim.git", :revision => "ddc5c14"

with blinking screen (because of screen flush) when Test 2 (redraw!) is called.

Why is a blinking screen expected in this case?  It doesn't blink in plain Vim when I call Test2.

because it clear the screen. try with fullscreen mode and/or a slow machine. prob your GPU is too fast to recognise i guess.


Failed setup, will retry - Coway API error

Hello,
I've just added two devices to the integration. The first one added fine with no trouble. However, the second one fails to connect to Home Assistant "failed setup, will retry".
Looking at the logs, I'm getting this message: "Error fetching coway data: Coway API error: Coway server failed to return purifier quality status."
Any suggestions to get this working? I wondered if the issue was because I had two devices on one account, so I added the second device to a new IOCare account and added it to HA as a new "hub". The issue still happens.
Thanks!

There will be a release here shortly. The issue stems from some purifiers that were recently purchased not working with the old API (at least only for the quality endpoint).
If you have a purifier on your account that does work with the older API and then add a purifier that doesn't, the integration fails. So, the issue isn't with having multiple purifiers on a single account as this is completely fine. Feel free to add all of your purifiers to a single account. Once I release version 0.4.0 (it'll be within the next ~30min - 1 hour), install it and then try again.

Please download & install 0.4.0. This should solve your issue.

Thank you. Yes, I'm no longer getting that error message (instead I'm now getting issue #39 ), so looks like this particular issue resolved. Thanks!

Thank you. Yes, I'm no longer getting that error message (instead I'm now getting issue #39 ), so looks like this particular issue resolved. Thanks!

0.4.1 resolves the new issue.


Add Elastic metricbeat to examples of DaemonSets and rename logstash

The URL points to the docs related to how to configure metricbeat on k8s. Besides, rename logstash reference to filebeat.
cc @axw , @exekias, @jamiesmith

/assign @kbhawkey

Page preview:
https://deploy-preview-19024--kubernetes-io-master-staging.netlify.com/docs/concepts/workloads/controllers/daemonset/

/approve


Add function that parses JSONPath

Add state_input parameter to StateMachine.simulate() for passing data to the starting state. Currently doesn't do anything
Add StateMachine._apply_json_path() for validating, parsing, then applying JSONPath to some data (see: https://docs.aws.amazon.com/step-functions/latest/dg/amazon-states-language-paths.html). Currently not used

Codecov Report

Merging #6 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines           86       101   +15
  Branches        10        15    +5
=========================================
+ Hits            86       101   +15

Impacted Files
Coverage Δ

src/awsstepfuncs/state_machine.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Interest in Pydantic 2.0

With the latest update to FastAPI, there is now support for Pydantic 2.0. Is there interest for an update of this stack to support it?

The next update to this stack will go to inboard 0.51 which is one step before fastapi 0.100 and pydantic 2.0. Lots of updates.
My assumption is that, since this is a starter stack, backwards compatibility is not required.
You can review the pull request https://github.com/whythawk/full-stack-fastapi-postgresql/pull/35 to see the changes before they're completed.

Can this be closed?

@hrehfeld Hi, yes, will do ...


Customizing default template

Hey guys!
We would like to use all the power provided by create-react-app every time we start with a new project. As we always add few extra libraries after the app is created like react-router, redux, classnames and use a slightly different project structure to the provided by the default template, I was wondering if there is a recommended way of doing this repetitive work.
Here is what I tried so far:

Fork of react-scripts and modify the default template
With this solution is possible to modify the generated app structure. However, adding new dependencies is not quite simple. It takes adding a .template.dependencies.json and modifying the scripts/init.js so it installs the additional dependencies if present even when a custom template is not provided via --internal-testing-template and avoid installing react and react-dom when previously installed. I'm wondering if this could be a feature request itself.
A downside I see with this approach is it takes maintaining your own version of react-scripts even when you don't need to modify the react-scripts dependencies itself but the template's dependencies.

CRAFT. React Create App From Template
This is a very interesting concept. This command line utility allows you to use your own template when creating a new app. The problem is it doesn't really create a new app but basically copies a repository with a previously created react app then applies some changes to the output, as far as I could see. This is far from being ideal since when I'm creating a new app, I would prefer using the most recent version of react-scripts as possible rather on rely on the one installed in the template, which may be outdated.

This may be an advanced use case and not sure if it is out of the core ideas for this awesome project but it seems create-react-app already contains most of the things needed to support something like this:
create-react-app MyApp --template <url-to-template>
Does anyone know what is the general recommendation from the community to deal with this case?
Thanks!

Here's a third alternative that does all that you want without too much extra work: Write a script that works on top of create-react-app.
#!/usr/bin/env bash

create-react-app $1
cd $1
yarn add react-router redux classnames
# use mv and mkdir commands to get desired project structure

You can use it like this:
./create-custom-react-app.sh my-new-app

@fcaldera I create a  create-react-app wrapper . May be satisfied with what you say. you can see create-custom-react-app

Thanks @GAumala. It looks like a good approach. Our needs however demanded a more flexible and maintainable solution since we wanted to share this across teams and every team may have different needs on dependencies and project structure. In simpler scenarios it can definitely work.

@likun7981 it seems we ended up like building the same thing. You can see ours here: https://github.com/cebroker/craft. This is pretty much a WIP so please disregard our lack of documentation.
I like several things you did down there, specially the support for local templates and the use of the hidden option of create-react-app which simplifies everything. Not sure how much we should rely on that hidden feature but it was definitely a smart move. Thanks for sharing!

I think this is an excellent idea, and should be added as a built-in option to the CRA CLI tool.
This would possibly help address complaints that CRA doesn't deal with app setup at all.  This way, the Redux docs could tell people to use --template react-app-template-simple-redux-starter, the MobX docs could point to --template react-app-template-mobx-setup, and someone else could point to --template my-awesome-kitchen-sink-template.
I'm going to cheat a bit and tag @gaearon and @Timer to see if I can bring this to their attention.

I'd be willing to implement this if it's something the CRA team would like to include. I personally think it would be useful.
I just looked at the code and it seems like everything is in place for this already. There's even a super secret option that will let you use it:
.option(
    '--internal-testing-template <path-to-template>',
    '(internal usage only, DO NOT RELY ON THIS) ' +
      'use a non-standard application template'
  )

It would be very easy to make this an officially supported option so I'm guessing there's a reason it's not exposed. I'd love to know what that is though.

Having this option officially supported would be useful for people who want to extend CRA (something like this.
Just having a repository to be used as a initial app template is not as useful as having a package that extends CRA as a dependency of your project.
Having a package allow us to update script and push this updates via package update, allowing the user to get the new code just by updating the version of the package. Doing this with a template repository is not as practical.

https://github.com/facebook/create-react-app/issues/2960#issuecomment-356108258
This logic can be applied to CRA itself, right?
Lots of boilerplate generating CLI's have a --template flag.
They make the mistake of making those templates 3rd party, but if CRA team would maintain a few variants then --template could be handy.
Very specifically: I hate having to delete all the junk in a CRA app (yes I fire up a lot of CRA apps just to test misc stacks) and would love a --template=bare or just --bare flag. I really don't care about the rest.

Hello everyone, I was digging the same issue as I'm creating a small fork (as suggested into the official docs) to support some webpack extensions (like in react-app-rewired) and adding some custom templates.
I found out that --internal-testing-template is currently supported and will try to fetch a template folder from the cwd.
It works decently enough for me, but I've tweaked a little bit the init.js so to be able to host more basic templates in my own version of react-scripts.
I hope this flag that seems so experimental will one day become just --template as you all suggest!

Can this be closed now the --template flag has been added? https://create-react-app.dev/docs/custom-templates/

Whoa I need to read release blog posts. :O Nice! Thank you CRA Team! <3


failed

using your plugin get fail

How can i fix it?

Seems identical to #7.
Are you running the latest version of the plugin? I cannot reproduce with plugin version 1.3.1


[Feature] Installation script for various libraries and software

Currently, to install and setup the raspberry pi with the needed software and libraries is a lengthy project. This could be made much quicker with an installation script.

@all-contributors please add @kadensu for code, doc and bug

This is implemented with the pip file. Unused dependencies have been removed as of #75


Audio: Consider api_version, organization params (Bug #509)

Thanks for this!
We've since rewritten the library entirely, so this change is no longer relevant. I'm sorry we didn't get to it sooner.


[Bug Report] Input type textarea append slot bug

Element UI version
1.4.6
OS/Browsers version
all
Vue version
2.4.4
Reproduction Link
https://jsfiddle.net/bgn34nL0/
Steps to reproduce
Add slot="append" to input type textarea
What is Expected?
Append slot content
What is actually happening?
Nothing

The append slot is only meant for inputs, not textareas.

But why?


Use Caching in Github Actions Workflow

Description
This PR sets up the caching action in the Github workflow so that installing Python dependencies is faster.
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have run changie new to create a changelog entry

My delays in merging approved PRs have come to bite me.

FYI - this reduces the Python test action from 90-120s -> 30-40s.


Can't scroll down left side sometimes

File: index.md
sometimes I can not scroll down the left

Likely to do with the JavaScript necessary to resize left side nav

.sidebar's position: fixed rule is causing #navbar to take up 100% of the browser's height (which is being controlled by JS); similar to what's going on with the right sidebar too.
I'll call dibs on this one 👍  any pointers on where you guys have the code for this?

@allejo this might be fixed. If not, can you work with @jsouth on this ?
cc: @johndmulhausen

Sure! I'm aware that @jsouth fixed the right sidebar width in #2804. Not sure if he's working on fixing the overlapping of both sidebars by the footer as seen here:

PR #2860 has this behavior instead (still a WIP):

@allejo You are right! Go for it.

Points to @allejo for #2860


Link to docs for configuring an iop deployment

Linking to information we were missing while working on #38.

@michielbdejong CI is failing since it thinks it's a chart update, if you can include [skip ci] on the commit message like in https://github.com/cs3org/charts/commit/23425adfff483fe5252f564189cac695da45dd3e - thanks!


Sarama has stuck on the batch with zero records length.

Versions
Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.

Sarama
Kafka
Go

Version 1.29.1
AWS Managed Kafka
1.17

Configuration
What configuration values are you using for Sarama and Kafka?
                 cfg.Net.MaxOpenRequests = 1
		// consume all messages
		cfg.Consumer.IsolationLevel = sarama.ReadUncommitted
		// require producer idempotency
		cfg.Producer.Idempotent = true
		// require consistency on Kafka side before considering the message produced
		cfg.Producer.RequiredAcks = sarama.WaitForAll
		// specify network keep-alive to reduce 'broken pipe' errors on non-KMS environments
		cfg.Net.KeepAlive = time.Second * 30
		// increase processing time from 1s (default) to 5s
		cfg.Consumer.MaxProcessingTime = time.Second * 5

Logs
When filing an issue please provide logs from Sarama and Kafka if at all
possible. You can set sarama.Logger to a log.Logger to capture Sarama debug
output.
logs: CLICK ME

2021/10/22 10:38:26.384689 lvl=INF component=kafka records batch &{5805968 49 2 snappy 0 false false 0 2021-09-30 11:45:34.617 +0200 CEST 2021-09-30 11:45:34.617 +0200 CEST 82609 0 1563 [0xc00030e150] false false [] 1326}
2021/10/22 10:38:26.384705 lvl=INF component=kafka records batch &{5806083 49 2 snappy 0 false false 0 2021-09-30 12:00:01.188 +0200 CEST 2021-09-30 12:00:01.188 +0200 CEST 82609 0 1678 [0xc00030e1c0] false false [] 733}
2021/10/22 10:38:26.384728 lvl=INF component=kafka records batch &{5806313 49 2 snappy 0 false false 0 2021-09-30 12:29:55.542 +0200 CEST 2021-09-30 12:29:55.542 +0200 CEST 82609 0 1908 [0xc00030e230] false false [] 10546}
2021/10/22 10:38:26.384751 lvl=INF component=kafka records batch &{5806399 49 2 snappy 0 false false 0 2021-09-30 12:42:07.755 +0200 CEST 2021-09-30 12:42:07.755 +0200 CEST 82609 0 1994 [0xc00030e2a0] false false [] 1130}
2021/10/22 10:38:26.384772 lvl=INF component=kafka records batch &{5806689 49 2 snappy 0 false false 0 2021-09-30 13:25:25.119 +0200 CEST 2021-09-30 13:25:25.119 +0200 CEST 82609 0 2284 [0xc00030e380] false false [] 2934}
2021/10/22 10:38:26.384790 lvl=INF component=kafka records batch &{5807057 49 2 snappy 0 false false 0 2021-09-30 14:24:12.229 +0200 CEST 2021-09-30 14:24:12.229 +0200 CEST 82609 0 2652 [0xc00030e3f0] false false [] 3124}
2021/10/22 10:38:26.384807 lvl=INF component=kafka records batch &{5807106 49 2 snappy 0 false false 0 2021-09-30 14:31:33.337 +0200 CEST 2021-09-30 14:31:33.337 +0200 CEST 82609 0 2701 [0xc00030e460] false false [] 2335}
2021/10/22 10:38:26.384824 lvl=INF component=kafka records batch &{5807150 49 2 snappy 0 false false 0 2021-09-30 14:38:49.18 +0200 CEST 2021-09-30 14:38:49.18 +0200 CEST 82609 0 2745 [0xc00030e4d0] false false [] 2917}
2021/10/22 10:38:26.384858 lvl=INF component=kafka records batch &{5807374 49 2 snappy 0 false false 0 2021-09-30 15:12:07.587 +0200 CEST 2021-09-30 15:12:07.587 +0200 CEST 82609 0 2969 [0xc00030e540] false false [] 5744}
2021/10/22 10:38:26.384933 lvl=INF component=kafka records batch &{5807388 49 2 snappy 0 false false 0 2021-09-30 15:14:10.358 +0200 CEST 2021-09-30 15:14:10.358 +0200 CEST 82609 0 2983 [0xc00030e5b0] false false [] 31539}
2021/10/22 10:38:26.384958 lvl=INF component=kafka records batch &{5807391 49 2 snappy 0 false false 0 2021-09-30 15:14:44.664 +0200 CEST 2021-09-30 15:14:44.664 +0200 CEST 82609 0 2986 [0xc00030e620] false false [] 2135}
2021/10/22 10:38:26.385027 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.418552 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.450115 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.481958 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.522805 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.557499 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.593690 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.625917 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.657295 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.775601 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.806612 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.840360 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.871158 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}

Problem Description
I'm using Goka (Sarama based library) and have some problems with reading from the one partition of 4. The consumer has stuck on the one particular batch and rereads it again and again.
Here is some info:
This is batch struct:
type RecordBatch struct {
	FirstOffset           int64
	PartitionLeaderEpoch  int32
	Version               int8
	Codec                 CompressionCodec
	CompressionLevel      int
	Control               bool
	LogAppendTime         bool
	LastOffsetDelta       int32
	FirstTimestamp        time.Time
	MaxTimestamp          time.Time
	ProducerID            int64
	ProducerEpoch         int16
	FirstSequence         int32
	Records               []*Record
	PartialTrailingRecord bool
	IsTransactional       bool

	compressedRecords []byte
	recordsLen        int // uncompressed records size
}

I added some logs for all decoded batches and firstly I see this:
2021/10/22 10:38:26.384671 lvl=INF component=kafka records batch &{5805856 49 2 snappy 0 false false 0 2021-09-30 11:29:46.662 +0200 CEST 2021-09-30 11:29:46.662 +0200 CEST 82609 0 1451 [0xc00030e0e0] false false [] 1735}
2021/10/22 10:38:26.384689 lvl=INF component=kafka records batch &{5805968 49 2 snappy 0 false false 0 2021-09-30 11:45:34.617 +0200 CEST 2021-09-30 11:45:34.617 +0200 CEST 82609 0 1563 [0xc00030e150] false false [] 1326}
2021/10/22 10:38:26.384705 lvl=INF component=kafka records batch &{5806083 49 2 snappy 0 false false 0 2021-09-30 12:00:01.188 +0200 CEST 2021-09-30 12:00:01.188 +0200 CEST 82609 0 1678 [0xc00030e1c0] false false [] 733}
2021/10/22 10:38:26.384728 lvl=INF component=kafka records batch &{5806313 49 2 snappy 0 false false 0 2021-09-30 12:29:55.542 +0200 CEST 2021-09-30 12:29:55.542 +0200 CEST 82609 0 1908 [0xc00030e230] false false [] 10546}
2021/10/22 10:38:26.384751 lvl=INF component=kafka records batch &{5806399 49 2 snappy 0 false false 0 2021-09-30 12:42:07.755 +0200 CEST 2021-09-30 12:42:07.755 +0200 CEST 82609 0 1994 [0xc00030e2a0] false false [] 1130}
2021/10/22 10:38:26.384772 lvl=INF component=kafka records batch &{5806689 49 2 snappy 0 false false 0 2021-09-30 13:25:25.119 +0200 CEST 2021-09-30 13:25:25.119 +0200 CEST 82609 0 2284 [0xc00030e380] false false [] 2934}
2021/10/22 10:38:26.384790 lvl=INF component=kafka records batch &{5807057 49 2 snappy 0 false false 0 2021-09-30 14:24:12.229 +0200 CEST 2021-09-30 14:24:12.229 +0200 CEST 82609 0 2652 [0xc00030e3f0] false false [] 3124}
2021/10/22 10:38:26.384807 lvl=INF component=kafka records batch &{5807106 49 2 snappy 0 false false 0 2021-09-30 14:31:33.337 +0200 CEST 2021-09-30 14:31:33.337 +0200 CEST 82609 0 2701 [0xc00030e460] false false [] 2335}
2021/10/22 10:38:26.384824 lvl=INF component=kafka records batch &{5807150 49 2 snappy 0 false false 0 2021-09-30 14:38:49.18 +0200 CEST 2021-09-30 14:38:49.18 +0200 CEST 82609 0 2745 [0xc00030e4d0] false false [] 2917}
2021/10/22 10:38:26.384858 lvl=INF component=kafka records batch &{5807374 49 2 snappy 0 false false 0 2021-09-30 15:12:07.587 +0200 CEST 2021-09-30 15:12:07.587 +0200 CEST 82609 0 2969 [0xc00030e540] false false [] 5744}
2021/10/22 10:38:26.384933 lvl=INF component=kafka records batch &{5807388 49 2 snappy 0 false false 0 2021-09-30 15:14:10.358 +0200 CEST 2021-09-30 15:14:10.358 +0200 CEST 82609 0 2983 [0xc00030e5b0] false false [] 31539}
2021/10/22 10:38:26.384958 lvl=INF component=kafka records batch &{5807391 49 2 snappy 0 false false 0 2021-09-30 15:14:44.664 +0200 CEST 2021-09-30 15:14:44.664 +0200 CEST 82609 0 2986 [0xc00030e620] false false [] 2135}

Looks ok. But then I see:
2021/10/22 10:38:26.385027 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.418552 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.450115 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.481958 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.522805 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.557499 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.593690 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.625917 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.657295 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.775601 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.806612 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.840360 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.871158 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.901792 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}
2021/10/22 10:38:26.934249 lvl=INF component=kafka records batch &{5807565 49 2 none 0 false false 0 0001-01-01 00:00:00 +0000 UTC 2021-09-30 15:43:16.281 +0200 CEST 82609 0 3160 [] false false [] 0}

and it keeps going indefinitely.
I dug into the code and figured out that there is no exit from such situation when the records len is 0. Sarama just reads this batch again and again. A high watermark was not reached.
We use AWS Managed Kafka in this case.
Please help. We are firing.

Hello! I just hit the same error as you, but your solution doesn't seem to work as the app is stuck in a loop and the offset isn't changing... Any idea how to fix this? :)
2021-12-31T10:32:39.030 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.031 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.031 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.032 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.033 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.034 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.035 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.036 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.037 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.038 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.039 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.040 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.041 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.042 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.042 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.043 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.044 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.045 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.046 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.046 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.047 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.048 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.049 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.050 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.051 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.051 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.052 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.053 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.054 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.055 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.055 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.056 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.057 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.058 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.059 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.060 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.061 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.062 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.062 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.063 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.064 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.065 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131
2021-12-31T10:32:39.066 consumer/broker/1004 received batch with zero records but high watermark was not reached, topic ***, partition 34, offset 15138131

I experienced the same issue with latest Sarama. Apparently we had some issues with one of our Kafka nodes in the clusters that triggered this behaviour in our Sarama consumers. We have Kafka consumers in both Scala and Go, and only the Sarama client got into this endless loop, the Scala client handled the issue just fine. We are not sure what the issue with Kafka itself was yet, but apparently there is an edge case here with Sarama that make it enter into an endless loop with the error above and stops consuming messages.


mopidy-iris: 3.14.0 -> 3.14.2

Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 3.14.2 with grep in /nix/store/anzim7y47xa3m530qzq91n9wl8ys1kk2-Mopidy-Iris-3.14.2
directory tree listing: https://gist.github.com/96a0fc1d9812e5c4e6659fd37c7b21c6

cc @rvolosatovs for review

Failure on x86_64-darwin (full log)
Attempted: mopidy-iris
Partial log (click to expand)
cannot build derivation '/nix/store/j1d5z8bk053vqd3sls0wbs8n15p3r7bz-gst-plugins-good-1.12.3.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/xz4lrlhr5sswxvq6nbcwf45d7jhr4203-gtk+3-3.22.29.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/02nrmp7qm6503l0ia9yrnw8mcyrd7ilg-libgsf-1.14.42.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/g5727ibzk572xkxxal9xmxlanbm8djpv-librsvg-2.42.2.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/236g4q7l15n579ppllbi281w66qa4s96-gst-plugins-bad-1.12.3.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/6yr6askhm4ah4h32ra1fmbkzyyia28k5-hook.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/iszv6s17mvpl5zin0fxs5hvz9vvq42j1-mopidy-2.1.0.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/z9dyk0m200152bz75kzzlbxpi2ddpsa4-mopidy-local-images-1.0.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/59kd0rnq93r4x1jailax9m12afar3klv-Mopidy-Iris-3.14.2.drv': 2 dependencies couldn't be built
error: build of '/nix/store/59kd0rnq93r4x1jailax9m12afar3klv-Mopidy-Iris-3.14.2.drv' failed

Failure on x86_64-linux (full log)
Attempted: mopidy-iris
Partial log (click to expand)
    mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/1rz4g4znpzjwh1xymhjpm42vipw92pr73vdgl6xs1hycac8kf2n9'
FAILED: meson-install
/nix/store/b8gd0cbvkm59x8flbc53bvsvmskyig5a-python3-3.6.4/bin/python3.6m /nix/store/n0m1fh2cfp751ifdakwxgl3ngf4cxamm-meson-0.44.0/bin/meson --internal install /tmp/nix-build-glib-networking-2.56.0.drv-0/glib-networking-2.56.0/build/meson-private/install.dat
ninja: build stopped: subcommand failed.
builder for ‘/nix/store/az4mcgkvgj04aj2kyclkki9iq5spl54s-glib-networking-2.56.0.drv’ failed with exit code 1
cannot build derivation ‘/nix/store/1hdpf4m8xk3lcpwb2whazgdvfwv9zbmp-mopidy-2.1.0.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/943lzr97q971yx3n5yrqy50yaw8b5iql-mopidy-local-images-1.0.0.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/bqp2pibpr2fmyn7ri77l7q9yg9x2nv3d-Mopidy-Iris-3.14.2.drv’: 2 dependencies couldn't be built
error: build of ‘/nix/store/bqp2pibpr2fmyn7ri77l7q9yg9x2nv3d-Mopidy-Iris-3.14.2.drv’ failed

Failure on aarch64-linux (full log)
Attempted: mopidy-iris
Partial log (click to expand)
shrinking /nix/store/ywycbpvknlb925isf5dk8r4dzji4jsg1-glib-networking-2.56.0/lib/gio/modules/libgiolibproxy.so
strip is /nix/store/3zq400fri5dv7d30lpxlqm2v9y1iis6j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/ywycbpvknlb925isf5dk8r4dzji4jsg1-glib-networking-2.56.0/lib  /nix/store/ywycbpvknlb925isf5dk8r4dzji4jsg1-glib-networking-2.56.0/libexec
patching script interpreter paths in /nix/store/ywycbpvknlb925isf5dk8r4dzji4jsg1-glib-networking-2.56.0
checking for references to /build in /nix/store/ywycbpvknlb925isf5dk8r4dzji4jsg1-glib-networking-2.56.0...
strip is /nix/store/3zq400fri5dv7d30lpxlqm2v9y1iis6j-binutils-2.28.1/bin/strip
cannot build derivation '/nix/store/x5ma7c2mjcrdx8hiliki06cclsjbz2yk-mopidy-2.1.0.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/6bidwxglr7sq9g2r4k9nvw2iqm97qy2l-mopidy-local-images-1.0.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/y306llmskk6zyi4yjdfh04l8qaxy5csh-Mopidy-Iris-3.14.2.drv': 2 dependencies couldn't be built
error: build of '/nix/store/y306llmskk6zyi4yjdfh04l8qaxy5csh-Mopidy-Iris-3.14.2.drv' failed


[SDK] Transaction History

This adds GetTransactionHistory API to the Client SDK.
This closes #263
@tiero @altafan @bordalix @louisinger please review.

@sekulicd still no timestamp on Transaction.
You can use (ExpiresAt - timeout) to figure it out when the VTXO/Tx was created.

@altafan please verify PR now, for gosec thing i excluded 'G115 (CWE-190): integer overflow conversion uint64 -> int64' completely and few other errors i add ignore comment in code that i find its safe to ignore.


[Doc Improvement][Update the docs set with consistent app manifest terminology][3124756]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/resources/schema/manifest-schema.md
92
28
link
:white_check_mark:

msteams-platform/samples/deploy-collaboration-control-in-teams.md
92
6
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-manifest.md
93
3
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-register-aad.md
91
25
link
:white_check_mark:

msteams-platform/tabs/how-to/using-teams-client-library.md
88
21
link
:white_check_mark:

msteams-platform/tabs/send-activity-feed-notification.md
95
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/resources/dev-preview/developer-preview-intro.md
92
6
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
90
33
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
92
27
link
:white_check_mark:

msteams-platform/samples/deploy-collaboration-control-in-teams.md
92
6
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-manifest.md
93
3
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-register-aad.md
91
25
link
:white_check_mark:

msteams-platform/tabs/how-to/using-teams-client-library.md
88
21
link
:white_check_mark:

msteams-platform/tabs/send-activity-feed-notification.md
95
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/resources/dev-preview/developer-preview-intro.md
92
6
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
90
33
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
92
27
link
:white_check_mark:

msteams-platform/samples/deploy-collaboration-control-in-teams.md
92
6
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-manifest.md
93
3
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-register-aad.md
91
25
link
:white_check_mark:

msteams-platform/tabs/how-to/using-teams-client-library.md
88
21
link
:white_check_mark:

msteams-platform/tabs/send-activity-feed-notification.md
95
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/resources/dev-preview/developer-preview-intro.md
92
6
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
90
33
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
92
27
link
:white_check_mark:

msteams-platform/samples/deploy-collaboration-control-in-teams.md
92
6
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-manifest.md
93
3
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-register-aad.md
91
25
link
:white_check_mark:

msteams-platform/tabs/how-to/using-teams-client-library.md
88
21
link
:white_check_mark:

msteams-platform/tabs/send-activity-feed-notification.md
95
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/TOC.yml
99
6
link
:white_check_mark:

msteams-platform/resources/dev-preview/developer-preview-intro.md
92
6
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
90
33
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
92
27
link
:white_check_mark:

msteams-platform/samples/deploy-collaboration-control-in-teams.md
92
6
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-manifest.md
93
3
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-register-aad.md
91
25
link
:white_check_mark:

msteams-platform/tabs/how-to/using-teams-client-library.md
88
21
link
:white_check_mark:

msteams-platform/tabs/send-activity-feed-notification.md
95
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/TOC.yml
99
6
link
:white_check_mark:

msteams-platform/resources/dev-preview/developer-preview-intro.md
92
6
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
90
33
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
92
26
link
:white_check_mark:

msteams-platform/samples/deploy-collaboration-control-in-teams.md
92
6
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-manifest.md
93
3
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-register-aad.md
91
25
link
:white_check_mark:

msteams-platform/tabs/how-to/using-teams-client-library.md
88
21
link
:white_check_mark:

msteams-platform/tabs/send-activity-feed-notification.md
95
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/TOC.yml
99
6
link
:white_check_mark:

msteams-platform/resources/dev-preview/developer-preview-intro.md
92
6
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
89
37
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
91
34
link
:white_check_mark:

msteams-platform/samples/deploy-collaboration-control-in-teams.md
92
6
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-manifest.md
93
3
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-register-aad.md
91
25
link
:white_check_mark:

msteams-platform/tabs/how-to/using-teams-client-library.md
88
21
link
:white_check_mark:

msteams-platform/tabs/send-activity-feed-notification.md
95
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/TOC.yml
99
6
link
:white_check_mark:

msteams-platform/resources/dev-preview/developer-preview-intro.md
90
7
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
89
37
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
91
34
link
:white_check_mark:

msteams-platform/samples/deploy-collaboration-control-in-teams.md
92
6
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-manifest.md
93
3
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-register-aad.md
91
25
link
:white_check_mark:

msteams-platform/tabs/how-to/using-teams-client-library.md
88
21
link
:white_check_mark:

msteams-platform/tabs/send-activity-feed-notification.md
95
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/TOC.yml
99
10
link
:white_check_mark:

msteams-platform/resources/dev-preview/developer-preview-intro.md
90
7
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
89
42
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
91
38
link
:white_check_mark:

msteams-platform/samples/deploy-collaboration-control-in-teams.md
92
8
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-manifest.md
93
12
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-register-aad.md
91
58
link
:white_check_mark:

msteams-platform/tabs/how-to/using-teams-client-library.md
88
21
link
:white_check_mark:

msteams-platform/tabs/send-activity-feed-notification.md
95
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.


Week 28 Review Ticket - Shreya Sapkal

MCQ Test #4

[x] Score: 45/50
[x] Link to blog of missed/confusing questions

Group Project/Lesson Planning

[x] Link to Lesson Plan Pull Request
[x] Date of Lesson on Lesson Plan Meta Data and scheduled with Teacher:

Individual Work

[x] My favorite Taylor Swift song is Paper Rings. I like it because it is catchy and cute. However, to sing, I like Style, You Belong With Me, and Trouble. To listen to in the car, I like Lavender Haze, because it has nice vocals and a cool beat.

2.7/3 this is well done.
Despite the issue Shreya had with her kernel, she completed all the work that she could do without it. Nice pros and cons chart, and she helped us all with the pull request.


Async/await

This is a must need as a ton of code I write now is using async/await.

Esprima stable currently not supporting this..

You can ask them to release beta version here
https://github.com/jquery/esprima/issues

https://github.com/jquery/esprima/issues/1749

finally
https://github.com/jquery/esprima/commit/d95fac62108c4a45139c4fe60c6c3155f585342a

Hi! Please try new<EMAIL_ADDRESS>it support async functions now.

Closed. Beta version supports async functions.


Including rules tcp and upd where are the same

Reviewers
@jframos @jesuspg
Description
https://jirapdi.tid.es/browse/CLAUDIA-4851
Test
tested locally

Coverage remained the same at 43.66% when pulling f46d8d0225e236decec6261ee70bbf926cdc75a8 on hmunfru:bug/CLAUDIA-4851-tcp-and-upd-ports into ce73ea62e5183efebd1a9b1a4694177dd27cc9f9 on telefonicaid:develop.

LGTM

Please take care about the update of the Rule.java class...

now this PR does no make sense. I will close it.

but, what about unit test!

Yes, @jesuspg is correct, I assume that you create a new PR with this two unit test changed files.


smartctl_exporter ignores nvme devices by default

Describe the bug
smartctl_exporter is completely silent in its metrics about NVMe devices:
$ curl -s http://<IP_ADDRESS>:9633/metrics | grep nvme
$ curl -s http://<IP_ADDRESS>:9633/metrics | grep sda | head -1
smartctl_device{ata_additional_product_id="unknown",ata_version="ACS-4 (minor revision not indicated)",device="sda",firmware_version="SN03",form_factor="3.5 inches",interface="sat",model_family="Seagate Exos X16",model_name="ST16000NM001G-2KK103",protocol="ATA",sata_version="SATA 3.3",serial_number="ZL2PVCR3"} 1
$ ls -l /dev/sda /dev/nvme0*
crw------- 1 root root 249, 0 Jan 10 00:35 /dev/nvme0
brw-rw---- 1 root disk 259, 0 Jan 10 00:35 /dev/nvme0n1
brw-rw---- 1 root disk 259, 1 Jan 10 00:35 /dev/nvme0n1p1
brw-rw---- 1 root disk 259, 2 Jan 10 00:35 /dev/nvme0n1p2
brw-rw---- 1 root disk   8, 0 Jan 10 00:35 /dev/sda

When you look at its log, you can see that it complains about being unable to open the device:
# journalctl -u prometheus-smartctl-exporter.service | tail
Jan 10 13:59:05 howl smartctl_exporter[3692782]: ts=2023-01-10T12:59:05.238Z caller=readjson.go:155 level=error msg="Smartctl open device: /dev/nvme0 failed: Permission denied"
Jan 10 13:59:28 howl smartctl_exporter[3692782]: ts=2023-01-10T12:59:28.883Z caller=readjson.go:69 level=warn msg="S.M.A.R.T. output reading" err="exit status 2"
Jan 10 13:59:28 howl smartctl_exporter[3692782]: ts=2023-01-10T12:59:28.883Z caller=readjson.go:123 level=error msg="Device open failed, device did not return an IDENTIFY DEVICE structure, or device is in a low-power mode"
Jan 10 13:59:28 howl smartctl_exporter[3692782]: ts=2023-01-10T12:59:28.883Z caller=readjson.go:155 level=error msg="Smartctl open device: /dev/nvme0 failed: Permission denied"
Jan 10 13:59:54 howl smartctl_exporter[3692782]: ts=2023-01-10T12:59:54.804Z caller=readjson.go:69 level=warn msg="S.M.A.R.T. output reading" err="exit status 2"
Jan 10 13:59:54 howl smartctl_exporter[3692782]: ts=2023-01-10T12:59:54.804Z caller=readjson.go:123 level=error msg="Device open failed, device did not return an IDENTIFY DEVICE structure, or device is in a low-power mode"
Jan 10 13:59:54 howl smartctl_exporter[3692782]: ts=2023-01-10T12:59:54.804Z caller=readjson.go:155 level=error msg="Smartctl open device: /dev/nvme0 failed: Permission denied"
Jan 10 14:00:54 howl smartctl_exporter[3692782]: ts=2023-01-10T13:00:54.801Z caller=readjson.go:69 level=warn msg="S.M.A.R.T. output reading" err="exit status 2"
Jan 10 14:00:54 howl smartctl_exporter[3692782]: ts=2023-01-10T13:00:54.801Z caller=readjson.go:123 level=error msg="Device open failed, device did not return an IDENTIFY DEVICE structure, or device is in a low-power mode"
Jan 10 14:00:54 howl smartctl_exporter[3692782]: ts=2023-01-10T13:00:54.801Z caller=readjson.go:155 level=error msg="Smartctl open device: /dev/nvme0 failed: Permission denied"

Steps To Reproduce
Steps to reproduce the behavior:

Have an nvme device
Set prometheus.exporters.smartctl.enable = true;
Notice nothing about the NVMe device present in http://<IP_ADDRESS>:9633/metrics
Notice errors in journalctl -u prometheus-smartctl-exporter.service

Expected behavior
I would expect the NVMe device to have its smart data collected. I don't have an opinion on whether they should be collected from the top-level device (e.g. /dev/nvme0) or at the namespace level (e.g. /dev/nvme0n1).
Additional context
smartctl_exporter gets started as a user that doesn't have read access to top-level nvme devices, which causes it to completely ignore them (i.e. behave as if they didn't exist; see #91 on smartctl_exporter for the bug about it being silent). It does have access to devices at namespace level, but its device auto-detection detects the top-level one.
It seems that smartctl claims that the "correct" level to query is /dev/nvme0 (see smartctl --scan, even when smartctl -a /dev/nvme0n1 also works.
The reason the exporter can query all the other devices is because it runs with disk in supplementary groups:
# systemctl cat prometheus-smartctl-exporter.service
(...)
[Service]
(...)
SupplementaryGroups=disk

As shown above, top-level NVMe devices are owned by root:root. I guess this might be caused by them being char (as opposed to block) devices.
Notify maintainers
@mweinelt @Frostman
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.80, NixOS, 23.05 (Stoat), 23.05.git.d8b095dabd9`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.12.0`
 - channels(root): `""`
 - channels(robryk): `""`
 - nixpkgs: `/etc/nixpkgs`

My nixpkgs version is c4e1db0e2571a5f134471e6aa7b7fce129c7d822 with own patches on top.

https://github.com/NixOS/nixpkgs/pull/205165

Hi @robryk, the latest version of smartctl_exporter identifies NVMe drives.
$ xh --body :19633/metrics | rg nvme
smartctl_device{ata_additional_product_id="unknown",ata_version="",device="nvme0",firmware_version="001C",form_factor="",interface="nvme",model_family="unknown",model_name="INTEL SSDPEKKW512G8",protocol="NVMe",sata_version="",serial_number="BTHH807006AA512D"} 1
smartctl_device_available_spare{device="nvme0"} 100
smartctl_device_available_spare_threshold{device="nvme0"} 10
smartctl_device_block_size{blocks_type="logical",device="nvme0"} 512
smartctl_device_block_size{blocks_type="physical",device="nvme0"} 0
smartctl_device_bytes_read{device="nvme0"} 6.1971011072e+13
smartctl_device_bytes_written{device="nvme0"} 2.9831524352e+13
smartctl_device_capacity_blocks{device="nvme0"} 1.000215216e+09
smartctl_device_capacity_bytes{device="nvme0"} 5.12110190592e+11
smartctl_device_critical_warning{device="nvme0"} 0
smartctl_device_interface_speed{device="nvme0",speed_type="current"} 0
smartctl_device_interface_speed{device="nvme0",speed_type="max"} 0
smartctl_device_media_errors{device="nvme0"} 0
smartctl_device_num_err_log_entries{device="nvme0"} 0
smartctl_device_percentage_used{device="nvme0"} 9
smartctl_device_power_cycle_count{device="nvme0"} 53
smartctl_device_power_on_seconds{device="nvme0"} 1.572588e+08
smartctl_device_smart_status{device="nvme0"} 1
smartctl_device_smartctl_exit_status{device="nvme0"} 0
smartctl_device_temperature{device="nvme0",temperature_type="current"} 41
# HELP smartctl_device_total_capacity_bytes NVMe device capacity bytes (only for devices with multiple NVMe namespaces)
smartctl_device_total_capacity_bytes{device="nvme0"} 0

However, it does need to be run by root. A little Googling lead me to Why smartctl could not be run without root. They concluded root was required and they went so far as to open an issue with smartmontools. After digging through the smartmontools tickets, I found the ticket the blogger opened.
RFE: add O_RDRW mode for sat/scsi/ata devices

According to function blk_verify_command() from current kernel sources (see block/scsi_ioctl.c), O_RDONLY or O_RDWR make no difference if device was opened as root (or with CAP_SYS_RAWIO).
The SCSI commands listed in function blk_set_cmd_filter_defaults() show that some of the smartctl -d scsi functionality might work with O_RDONLY for non-root users. Some more might work with O_RDWR.
But smartctl -d sat (to access SATA devices) won't work at all because the SCSI commands ATA_12 and ATA_16 (see scsi_proto.h) are always blocked for non-root users.

Please note that we have smartctl running as non-root and collecting information from SATA devices. I don't know why your link claims it doesn't work (maybe it used not to?), but it does work now, so I won't try to investigate whether it used not to.
The issue here is that smartctl while running as non-root and without access to open top-level NVMe devices won't collect from NVMe. The reason it doesn't have access to top-level NVMe devices is because they are not group-owned by disk in the default setup created by built-in udev rules.

Let's add a group named rawio that udev assigns permissions to, as was proposed in the upstream systemd issue.
I'm opposed to making the exporter run as root, if we don't have to, sorry.


Ignore all streaming errors on crash test

See Paulo's comment on 12494.
@mambocab to review

Could you note the JIRA ticket in a comment or the commit message? Then I'll be +1.


Loading of output C file FAILED on Mac

I tried to build and run the plugin on my Mac. Plugin load seems okay but when I tried to ^D on a function, I still get the error as #29 :

The out from IDA's console is

from the #29 I can't find any solution。
By the way, I used the latest code to build。
I use this file to test .

Sorry, I forgot to explain my system information , it is ：
OS version：macOS Catalina 10.15.3
IDA SDK version：7.0
IDA version：7.0

Issue is no longer valid. v1.0 does not use Python and works only in IDA 7.5 with SDK 7.5.

Issue is no longer valid. v1.0 does not use Python and works only in IDA 7.5 with SDK 7.5.