temporarily suspend all mergify rules

What does this PR do?
most of the actions are not valid anymore, so we will re-enable them one by one in the upcoming week :]
Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
[x] Did you make sure to update the documentation with your changes?
[x] Did you write any new necessary tests?
[x] Did you verify new and existing tests pass locally with your changes?
[x] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified; Bugfixes should be including in bug-fix release milestones (m.f.X) and features should be included in (m.X.b) releases.

Did you have fun?
Make sure you had fun coding 🙃

@williamFalcon can you pls review this suspension?


Basic Deployment: Admin Password

Description
The basic deployment doesn't have an admin password field. and it is auto generated and currently only available in the JSON Deployment details.

so the admin password should either be a field in the basic deployment or the superuser email and password should be added in the deployment details tab.

it's already exists but there was an issue in production that blocking some fields from showing up

Verified on https://getmastodon.threefold.io/
All admin credentials are now displayed in the deployment details.


Make trace lookup faster by using a hash

Backport from #86.
RSpec::Buildkite::Analytics.uploader.traces was an array and we would loop through this many times to find our matching trace. On larger test suites with 1000s of tests, it would cause 100s of 1000s of loops. We can instead lookup the value directly with a hash.

thanks @blaknite for getting this in 👍


Whats Happen With This Basic Example

Just want to show here, LOL.... Coz I really don't know how to fix this error in basic code.
Here my screen shoot : http://imgur.com/a/1I9jg

Something else is being hosted on your localhost:3000 port.

I receive the same error when I start the server by using npm start.

This is fixed in the branch I'm working on, the example has been greatly reduced in complexity for hosting.


Retrieve target branch from PR label(s)

There are use cases where the target branch is not always fixed, instead it is dynamically computed from the original PR label(s).
That is why we created this additional workflow step [1] to properly parse labels with a prefixed pattern and extracting the target branch from them, this could be hard to maintain and error-prone.
Proposal: integrate this step in the tool itself, in this way target-branch will become optional and you can provide the regex/pattern to use in order to extract the target branch from the original PR labels, if any.
[1] https://github.com/kiegroup/droolsjbpm-build-bootstrap/blob/main/.github/workflows/pr-backporting.yml#L12-L25
### Tasks
- [ ] https://github.com/kiegroup/git-backporting/issues/77

here is a snippet for inspiration, from a similar action:

const getBaseBranches = ({
  labelRegExp,
  payload,
}: Readonly<{
  labelRegExp: RegExp;
  payload: PullRequestClosedEvent | PullRequestLabeledEvent;
}>): string[] => {
  if ("label" in payload) {
    const base = getBaseBranchFromLabel(payload.label.name, labelRegExp);
    return base ? [base] : [];
  }

  return compact(
    payload.pull_request.labels.map((label) =>
      getBaseBranchFromLabel(label.name, labelRegExp),
    ),
  );
};

That's a good hint, thanks @earl-warren for the reference!


chore: add spell checker

Add a spell checker

with eslint plugin (for ts/js files)
with cli for md files not supported by eslint

Fix spelling issues, add custom words dict
Fix prettier-eslint recommended config, apply fixes to files

TODO

[ ] Fix/handle 615 spelling warnings (with dupes) from eslint as it can drown out any other eslint issues.

https://coveord.atlassian.net/browse/KIT-2515

@btaillon Yes I had added the corresponding VSCode extension to the recommended list sometime back.
@aprudhomme-coveo This PR doesn't contain all the spelling fixes yet (as denoted by the TODO). I will get them fixed today and if its still not addressed we can look into it.


tests to verify fix for DRILL-4862

Hello Abhishek,
I have added tests to verify fix for DRILL-4862
You should look at framework/resources/Functional/convert/drill_4862*.q tests
Please review and merge, I have a clean run where my new test have passed, there are other unrelated failures in that run. I will share the link to that pre-commit run.
Thanks,
Khurram

HEy Khurram,
Looks like there are over 10 commits in here. Can you please do the following:

add mapr/master as a remote, if you haven't done so already
git remote add mapr git@github.com:mapr/drill-test-framework.git
create a new branch
`git checkout -b BRANCH_NAME
rebase it over mapr/master
git rebase mapr/master
add files part of this check-in
git add FILE_NAME
commit them
git commit -m "MESSAGE"
push them to a new branch
git push origin BRANCH_NAME
create a PR from this branch via Github

Those others commits that are showing up were the ones we already merged in an earlier PR. Those were tests for null equality join support.
I think the HEAD got changed/messed up somehow on my machine, while I was trying to build different versions of Drill.
Is it not possible that we can fix the HEAD on my current repo on my machine ?
I have never had this kind of issue before, only after the HEAD was changed I have started to see these issues.
 Retain 'pick' on the earliest and most relevant commit. Change 'pick' to 's' on each line for a related commit. Save it. Then once rebase starts, edit the commit message to remove all messages above the instructions, except for the most relevant message.
force push this to your new branch
git push -f origin BRANCH_NAME

However, we see this message when I did a compare of the two branches, " Able to merge. These branches can be automatically merged."
So I would assume that it is safe to merge, given that there are no conflicts & we have a clean pre-commit run.
Thanks,
Khurram


fix(policies): skip policy enforcement only for Istio-init container

current annotation that is set by istio mutation will prevent complete pod to be checked on the
provided policies (allowedusers,capabilities and containerlimits). With this change it will only
skip validation for istio-init container
BREAKING CHANGE: This will cause the policies allowedusers/capabilities/containerlimits to work on
all pods that are injected by istio. This might prevent users for instance to update pods that are
running as root already.
Checklist

[x] Architecture Design Records have been added as adr/*.md and appended to list in adr/_index.md.
[x] The values-schema.yaml file and test/** fixtures have been updated to reflect code changes.
[x] The OpenApi Schema from redkubes/otomi-api project is compatible with definitions from values-schema.yaml file.

I consider this BREAKING CHANGE as a low risk, because policies enforcement was already performed for Deployments and Stateful Sets, Daemon Sets (so for those manifests before istio mutation web hook)

Where is the previous PR from @bartusz01 where I elaborated on this issue?

Where is the previous PR from @bartusz01 where I elaborated on this issue?

there was no PR opened before

indeed, didnt create a PR yet, because I wanted to look into the Rego code. However, it can be merged already to fix the issue. I just now removed also the container-limits exception, since istio-init container is deployed with allowed resources.

Ok. Can we also take istio-proxy into account please? And not merge unfinished reviews @j-zimnowoda ?

So may I ask why istio-proxy is not caught by gatekeeper now @bartusz01 ? Or is it and should it be added similarly?

Check the comments above! istio-proxy is validated and allowed, there is nothing in its securityContext that will force gatekeeper to deny the request, see here the istio-proxy security context:
securityContext:
      allowPrivilegeEscalation: false
      capabilities:
        drop:
        - ALL
      privileged: false
      readOnlyRootFilesystem: true
      runAsGroup: 1337
      runAsNonRoot: true
      runAsUser: 1337

aha, it is made very strict since some versions ago then. I remember we had issues with it back when the exclusion mechanism was made. non-issue then. Awesome


Monte Carlo methods for scipy.integrate

Problem description
I was wondering why there are no Monte Carlo integration methods (uniform sampling, importance sampling, MISER, VEGAS) in scipy.integrate? Especially for high dimensional integrals MC methods provide good efficiency and they are applicable to a wide range of fields in science and engineering.
The solution I'd like
One could implement a set of Monte Carlo methods that are applicable to n-dimensional integrals. E.g. something like this (adapted from here):
from scipy import integrate
N = 5
def f(t, x):
return np.exp(-x*t) / t**N
integrate.mcuniform(f, [[1, np.inf],[0, np.inf]])
integrate.mcmiser(f, [[1, np.inf],[0, np.inf]])
integrate.mcvegas(f, [[1, np.inf],[0, np.inf]])
Alternatives I've considered
I am aware of the vegas and scikit-monaco projects but there can be issues with the installation on Windows (requires C compiler) and I would think that such important methods should be easily available independent of the platform. Including MC methods into scipy.integrate would also ensure an uniform documentation and syntax.

Hi @EdKaHe, this is the kind of feature that could very well make sense to have as part of scipy.integrate, but would be fairly technical code to get right. If there was a proposal to, e.g., integrate vegas into SciPy by its maintainer (who would keep maintaining it for the foreseeable future), we would certainly consider that. We've done that kind of integration of fairly mature code in other places, and it's a good way to make algorithms that are best-in-class - or at least better than what we already have - available to users.

qmc_quad will be part of 1.11.0. It's essentially the simplest possible QMC integration method, but in higher dimensions it's more effective than nquad, so I think it satisfies the enhancement request. If not, please feel free to reopen.


[WIP] assert_referential_integrity raise unless production

When it silently does not save records, it's hard to debug...
(Well it logs a warning, but who checks log when debugging? ;-)
First you check you really produce the InventoryObjects,
then you scratch your head and scatter breakpoints in saving machinery,
until you find the if assert_referential_integrity — doh!
I fell on this at least twice...
This mirrors the approach in assert_distinct_relation of logging in
prod and exploding in console / tests.
@Ladas @agrare please what do you think?
@miq-bot add-label enhancement, developer, test

failed tests, I should have seen this coming :-)

@cben yes, we do this in the other assert, it definitely make sense.
@miq-bot assign @agrare

Fixed test (see 2nd commit description).
Don't merge yet, I want to test it doesn't break provider repos.

Added simple assert_referential_integrity spec, PTAL.
All provider repos were green against this (yesterday), except unrelated failure in https://travis-ci.org/cben/manageiq-providers-ansible_tower/jobs/260174147
(wrote POC script https://github.com/cben/miq-workenv/blob/master/test-with to push commits overriding manageiq repo & branch, and had my forks' Travis check.  Caveat emptor.  I'm hatcing a friendlier approach...)


Treat empty collection and null the same option

It would be nice to be able to configure this.

@strohhut sounds good.  Please implement and I will be happy to merge in the pull request.

I have to extend CollectionComparer.IsTypeMatch so it allows one side to be null (just like StringComparer.IsTypeMatch). If I do this then CollectionComparer.Compare now also executes when one side is null. This is problematic for ExcludeLogic.ShouldExcludeClass because this method expects the types of both sides. But I only get the type when the value is not null.

Thanks for the update.  It looks like you will need to modify in other areas then.

I saw that there are many classes that I would need to touch like ByteArrayComparer, HashSetComparer, etc. Unfortunately this is too complex for me to do right now.
Feel free to close this featue request.
Thank you!

No problem.  Best of luck with your projects.


Support H5182 Meat Thermometer with dual probes

Bluetooth data decoded and logged. SVG not specifically created, but may get done in the future.


fix: add new deployment scripts and CI workflows

adds new deployment scripts
adds deployment flows for mintable tunnels
bump .nvmrc
bump node version in workflows
add slither, lint and test workflows

narrator: in this PR review, the reviewer will display his inability to differentiate between testnet and mainnet


isBatteryOptimizationEnabled returns true

isBatteryOptimizationEnabled return true on Pixel 7 with Android 15 while background usage is enabled.

Not fixed yet.

Same issue on google pixel 8 with android 14

Not fixed yet.

Not fixed yet.

Unfortunately there are quite a few things much higher on the priority list and there are no more available magical fix gnomes wandering about looking for tasks
Suggest you instrument the native APIs here if possible via patch-package to log as much information as possible about the native API call before it is made, and all information about the result after it returns, to get more insight into why it is failing

I would say that the REQUEST_IGNORE_BATTERY_OPTIMIZATIONS permission is missing.

No permission is required to request the status.
That permission is only required to display an in-app dialog for users that allows direct disable of optimizations so not having that permission should have no relation to requesting the current optimization status. That action is strongly discouraged by Google in fact and can get your app banned. We don't use it, instead we use the gentler / does-not-get-app-banned ACTION_IGNORE_BATTERY_OPTIMIZATION_SETTINGS - and only if you want to try to alter the setting, not to request status
For status request we simply delegate to the power manager for this:
https://github.com/search?q=repo%3Ainvertase%2Fnotifee+isBatteryOptimizationEnabled+language%3AJava&type=code&l=Java
It is a very simple API - a one-liner except the platform version check, no permission required
There have been (and according to comments on the closed issue) still are reports of this status not being maintained correctly in the operating system on multiple devices, so it seems to be an upstream issue:
https://issuetracker.google.com/issues/37067894#comment14
Reports are that an app uninstall/reinstall will reset the status (not the most useful, but at least an indication that some change is detectable), does that happen in this case? https://stackoverflow.com/questions/50231908/powermanager-isignoringbatteryoptimizations-always-returns-true-even-if-is-remov
I don't think we're going to be able to fix this here unfortunately, though gathering information may result in a documentation update about why the status is potentially incorrect / not up to date


Registry changes

Description
Describe the purpose of and changes within this Pull Request.
Testing
Do any existing tests cover this change? Are new tests needed?
Documentation
Is there any documentation impact for this change?

Codecov Report

Merging #47 (fa6ecbf) into master (25abe8f) will increase coverage by 61.24%.
The diff coverage is 78.31%.

@@             Coverage Diff             @@
##           master      #47       +/-   ##
===========================================
+ Coverage   26.50%   87.75%   +61.24%
===========================================
  Files          40      100       +60
  Lines        6839    17738    +10899
===========================================
+ Hits         1813    15566    +13753
+ Misses       5026     2172     -2854

Impacted Files
Coverage Δ

ebpfapi/dllmain.cpp
70.00% <ø> (ø)

libs/api_common/api_common.hpp
82.85% <ø> (+57.14%)
:arrow_up:

libs/api_common/device_helper.cpp
83.14% <ø> (+62.92%)
:arrow_up:

libs/platform/ebpf_program_types.c
0.00% <ø> (-46.81%)
:arrow_down:

libs/platform/unit/platform_unit_test.cpp
99.26% <ø> (ø)

tests/libs/common/common_tests.cpp
92.92% <ø> (ø)

libs/service/verifier_service.cpp
79.41% <28.57%> (ø)

libs/execution_context/ebpf_maps.c
89.66% <50.00%> (ø)

libs/execution_context/ebpf_core.c
91.88% <66.66%> (ø)

libs/api_common/registry_helper.cpp
69.56% <69.56%> (ø)

... and 105 more

Continue to review full report at Codecov.

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


Shortcuts

Add shortcuts for some of the functions of the tab manager:

[x] Open the tab manager extension
[x] Undo
[x] Toggle the settings bar #100
[x] Arrange tabs #100
[x] Navigate to a window
[x] Toggle 'all windows' mode

@BorFour There is currently a shortcut for Undo, Ctrl + Z for windows and linux or Command + Z for Mac. A section listing the shortcuts should be added with these new shortcuts.

#125 adds some functionality, but to add more than 4 hotkeys, a different implementation will be needed. This can be done in the next release.


MSBuild v15 folder only contains a typescript folder and not a javascript folder also

I have upgraded from VS2015 to VS2017 and have an issue building Cordova apps for Windows.
I get the following error:
`C:\code\presales\PresalesApp\PresalesApp\platforms\windows\CordovaApp.Windows10.jsproj(61,3): error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v15.0\JavaScript\Microsoft.VisualStudio.WJProject.Default.props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.`

But when I check the msbuild folder there is no JavaScript folder, only a TypeScript folder.
I have installed all the available components under Build Tools with the Installer. What do I need to do to get the build tools to install the Javascript folder I need?

@ajberry I'm closing this as it doesn't seem related to any of the code in this repository. This repo only contains code for a few command line tools used with ASP.NET Core apps, not Cordova apps. Try opening an issue on https://developercommunity.visualstudio.com instead. Your issue looks similar to this one: https://developercommunity.visualstudio.com/content/problem/30384/msb4019-the-imported-project-cprogram-files-x86msb.html


The current .NET SDK does not support targeting .NET Core 3.1.  Either target .NET Core 2.2 or lower, or use a version of the .NET SDK that supports .NET Core 3.1

Problem encountered on https://dotnet.microsoft.com/learn/aspnet/microservice-tutorial/docker-image
Operating System: windows
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

Please check your myMicroservice.csproj file, it seems using .net core 3.1 as target which causes the problem .
Changing target to 2.2 may help solve this issue.

Yes, actually I want to use net core 3.1
Is it possible ?

In your Dockerfile, replace mcr.microsoft.com/dotnet/core/sdk:2.2
with mcr.microsoft.com/dotnet/core/sdk:3.1 may help. @eripin91


Update sparse parent folder mtimes to trigger Explorer refresh

Resolves #1532
If a File Explorer window is open to a directory in VFS4G, changes
to the files being projected are not enough to trigger a refresh.
This is especially noticeable when using the 'gvfs sparse' verb.
To force Explorer to refresh when 'gvfs sparse' triggers a projecion
changes, VFS4G will now update the last write time for every folder
placeholder that had children added or removed from the sparse set.

@kewillford you can hold off on reviewing my changes to RefreshSparseFolder I realized the approach I'm using now won't work in all scenarios, and I'm working on an update.

@kewillford you can hold off on reviewing my changes to RefreshSparseFolder I realized the approach I'm using now won't work in all scenarios, and I'm working on an update.

@kewillford okay this is ready for another look.  Please let me know if you can think of a better way of determining the list of directories to refresh.  With the most recent commit I took a simple approach:

For any path that was added or removed from the set, refresh its ancestors (if they are on disk)

This could result in over-refreshing (i.e. there are scenarios where not all ancestors would need to be refreshed) but assuming there are not thousands of deeply nested folders being changed in each call to gvfs sparse  I'm not sure we need the extra complexity of a fancier algorithm.
cc: @derrickstolee for his thoughts as well


fixed braces

Looks good. BTW you don't need to open a new pull request for each change (the old PR gets updated with the new commit).


incorrect  Signal

Hi,
trying to get the right signal from the Sensor but i got follow Singal, How to Fix it ?:

Any update?

That does look rather odd. Did you make any changes to the code in any way?
There does seem to be some connection between the computer and arduino.
Let us know what hardware you are using, and give us more details about your system setup to help troubleshoot.

@biomurph  No I used:
1- Arduino UNO
2- Linux OS
3- PulseSensorAmped_Arduino for get data from Arduino
4- PulseSensor_Amped_Processing_Visualizer for Show Data
I downloaded exact the same code in the github and run.
The Another odd things is my sensor wire color is different than Other Pulse sensor :

Thanks for the info.  That is not our tech, and there are many imitators of our open source hardware. Please tell us where you got it from, so other folks will know not to purchase from them.
Unfortunately, we cannot help you with the problem, as we have no idea what is going on with the hardware you have.

Thanks @biomurph I buy it from a electric local shop and it's looks like your sensor.

What shop? Where are you?

I Live in Iran and need your sensor for a research program, I can't buy your sensor from your official website Directly so after looking around about your sensor one local shop in my city (Mashhad) give to me a very similar, after trying very hard for fix the problem I decided send an issue about sensor and until that I i thought my sensor is original!
Please posting a warning in your website about the Fake pulse sensor for other Person.
Thanks.

Well, that is something... We have alot of copiers in China, which is the likely source of your counterfeit part. I have tried to purchase some of the copies, but that one does not look familiar. It may be possible to try and make it work, but we are very far away. I'd like to figure out if there is a way we can help you. If you email me joelatpulsesensordotcom we can pick up the conversation there.

@biomurph Thank I'll send you email.


[FEATURE] highway car race

Description
Divided into levels like hard and medium and easy..
Car race having red car have to compete with other cars and win the race.
Screenshots
No response
Additional information
No response

Hi @SimranLahrani842 , I have assigned this issue to you. Kindly complete within 10 august. Good luck.

Hi @SimranLahrani842 , I have assigned this issue to you. Kindly complete within 10 august. Good luck.

Yes mam
Thankyou for immediate response .👍❤


macOS

negrep build for macOS?

You can build for MacOS by installing dotnet core and then:
chmod a+x ./Deployment/publish_osx_local.sh
./Deployment/publish_osx_local.sh

The workflow has been changed to build Negrep for macOS. The negrep for macOS is already available in Release artefacts. The https://nevod.io site was updated to provides downloading link to negrep for macOS.


"minecraft: falling_block" does not recognize Tags.

:tada: This issue has been resolved in version 1.9.4 :tada:
The release is available on:

npm package (@latest dist-tag)
Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:


Value error when passing clang-tidy config file in --run-clang-tidy-options (RDT-287)

Runner raises a value error when passing "-config-file .clang-tidy" in --run-clang-tidy-options.
Looks like https://github.com/espressif/clang-tidy-runner/blob/master/pyclang/runner.py#L305 is checking for "Enabled checks" in the warning.txt file, but in this case the file is empty.
Here's the shell command and output (I excluded the unrelated build and reconfigure output).
$ idf.py clang-check --run-clang-tidy-py tools/clang-tidy/run-clang-tidy.py --run-clang-tidy-options "-config-file .clang-tidy"
...
run command: /Users/jonathan/.espressif/python_env/idf4.4_py3.10_env/bin/python /Users/jonathan/src/revlytics-firmware/tools/clang-tidy/run-clang-tidy.py .* -config-file .clang-tidy || true
Traceback (most recent call last):
  File "/Users/jonathan/.esp/esp-idf/tools/idf.py", line 816, in <module>
    main()
  File "/Users/jonathan/.esp/esp-idf/tools/idf.py", line 734, in main
    cli(sys.argv[1:], prog_name=PROG, complete_var='_IDF.PY_COMPLETE')
  File "/Users/jonathan/.espressif/python_env/idf4.4_py3.10_env/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/Users/jonathan/.espressif/python_env/idf4.4_py3.10_env/lib/python3.10/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/Users/jonathan/.espressif/python_env/idf4.4_py3.10_env/lib/python3.10/site-packages/click/core.py", line 1689, in invoke
    return _process_result(rv)
  File "/Users/jonathan/.espressif/python_env/idf4.4_py3.10_env/lib/python3.10/site-packages/click/core.py", line 1626, in _process_result
    value = ctx.invoke(self._result_callback, value, **ctx.params)
  File "/Users/jonathan/.espressif/python_env/idf4.4_py3.10_env/lib/python3.10/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/Users/jonathan/.esp/esp-idf/tools/idf.py", line 636, in execute_tasks
    task(ctx, global_args, task.action_args)
  File "/Users/jonathan/.esp/esp-idf/tools/idf.py", line 217, in __call__
    self.callback(self.name, context, global_args, **action_args)
  File "/Users/jonathan/.espressif/python_env/idf4.4_py3.10_env/lib/python3.10/site-packages/pyclang/idf_extension.py", line 25, in call_runner
    runner()
  File "/Users/jonathan/.espressif/python_env/idf4.4_py3.10_env/lib/python3.10/site-packages/pyclang/runner.py", line 169, in __call__
    self._run(folder, log_fs, output_dir)
  File "/Users/jonathan/.espressif/python_env/idf4.4_py3.10_env/lib/python3.10/site-packages/pyclang/runner.py", line 140, in _run
    func(folder, log_fs, output_dir)
  File "/Users/jonathan/.espressif/python_env/idf4.4_py3.10_env/lib/python3.10/site-packages/pyclang/runner.py", line 183, in _f
    return func(self, *args, **kwargs)
  File "/Users/jonathan/.espressif/python_env/idf4.4_py3.10_env/lib/python3.10/site-packages/pyclang/runner.py", line 306, in run_clang_tidy
    raise ValueError(first_line)
ValueError

I looked into this further and turns out run-clang-tidy.py is run from the build directory, not the project root directory. https://github.com/espressif/clang-tidy-runner/blob/07ce251b3e1ca506f6a68d41c5f528399200fe14/pyclang/runner.py#L300
My clang-tidy config file is the root directory so the file wasn't found. I was able to get this working by passing in a path relative to the build directory (e.g., ../.clang-tidy).
idf.py clang-check --run-clang-tidy-py tools/clang-tidy/run-clang-tidy.py --run-clang-tidy-options "-config-file ../.clang-tidy"

It would be more intuitive to pass the build directory using the -p option instead of running from the build directory.

Thanks for reporting!


FASTP error: input files don't contain identical amount of reads

Description of the bug
fastp seems to have issues handling uneven pair read data:
ERROR ~ Error executing process > 'PATHOGENSURVEILLANCE:GENOME_ASSEMBLY:FASTP (GCA_001063175_1_ASM106317v1_genomic)'

Caused by:
  Process `PATHOGENSURVEILLANCE:GENOME_ASSEMBLY:FASTP (GCA_001063175_1_ASM106317v1_genomic)` terminated with an error exit status (255)

Command executed:

  [ ! -f  GCA_001063175_1_ASM106317v1_genomic_1.fastq.gz ] && ln -sf SRR1655712.fastq.gz GCA_001063175_1_ASM106317v1_genomic_1.fastq.gz
  [ ! -f  GCA_001063175_1_ASM106317v1_genomic_2.fastq.gz ] && ln -sf SRR1655712_1.fastq.gz GCA_001063175_1_ASM106317v1_genomic_2.fastq.gz
  fastp \
      --in1 GCA_001063175_1_ASM106317v1_genomic_1.fastq.gz \
      --in2 GCA_001063175_1_ASM106317v1_genomic_2.fastq.gz \
      --out1 GCA_001063175_1_ASM106317v1_genomic_1.fastp.fastq.gz \
      --out2 GCA_001063175_1_ASM106317v1_genomic_2.fastp.fastq.gz \
      --json GCA_001063175_1_ASM106317v1_genomic.fastp.json \
      --html GCA_001063175_1_ASM106317v1_genomic.fastp.html \
       \
       \
       \
      --thread 4 \
      --detect_adapter_for_pe \
       \
      2> >(tee GCA_001063175_1_ASM106317v1_genomic.fastp.log >&2)

  cat <<-END_VERSIONS > versions.yml
  "PATHOGENSURVEILLANCE:GENOME_ASSEMBLY:FASTP":
      fastp: $(fastp --version 2>&1 | sed -e "s/fastp //g")
  END_VERSIONS

Command exit status:
  255

Command output:
  (empty)

Command error:
  Detecting adapter sequence for read1...
  No adapter detected for read1

  Detecting adapter sequence for read2...
  No adapter detected for read2

  WARNNIG: different read numbers of the 206 pack
  Read1 pack size: 218
  Read2 pack size: 1000

  ERROR: input files don't contain identical amount of reads

Work dir:
  /nfs7/BPP/Chang_Lab/paradarc/ps_pipeline_validation/scripts/pathogensurveillance/work/7f/07a5910f230b21e809665e7b2033a4

Tip: view the complete command output by changing to the process work dir and entering the command `cat .command.out`

Is this a sample error? Do we want to troubleshoot that or should the user drop that sample?
Command used and terminal output
No response
Relevant files
No response
System information
No response

Are we sure that these are in fact paired reads? Could we somehow be getting two single-end runs or something? I dont think it is normal to have unpaired reads so an error might be appropriate. Can you take a look at the sample and see if anything obviously off, like very different file sizes?

I investigate more today. It looks like that biosample had 3 SRAs:
> ls -ltr /nfs7/BPP/Chang_Lab/paradarc/ps_pipeline_validation/scripts/pathogensurveillance/path_surveil_data/reads/SRR1655712*
-rw-r--r-- 1 paradarc bpp 16896478 Nov  1 15:03 /nfs7/BPP/Chang_Lab/paradarc/ps_pipeline_validation/scripts/pathogensurveillance/path_surveil_data/reads/SRR1655712.fastq.gz
-rw-r--r-- 1 paradarc bpp 78616787 Nov  1 15:03 /nfs7/BPP/Chang_Lab/paradarc/ps_pipeline_validation/scripts/pathogensurveillance/path_surveil_data/reads/SRR1655712_2.fastq.gz
-rw-r--r-- 1 paradarc bpp 76902111 Nov  1 15:03 /nfs7/BPP/Chang_Lab/paradarc/ps_pipeline_validation/scripts/pathogensurveillance/path_surveil_data/reads/SRR1655712_1.fastq.gz

and you can see in the FASTP command it took the single end read file with one of the paired end read files...we may need to purge or throw errors if more than 2 SRAs were downloaded.


Fix grammar on mapper lottery page

I noticed some of the sentences were a bit hard to grasp or were similar to Dutch grammar. I asked ChatGPT to fix the grammar and applied it where I thought it would be an improvement.

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


java.io.FileNotFoundException: /var/run/${{app_name}}.pid (Permission denied)

kafka-manager -Dconfig.file=/usr/local/kafka-manager/conf/application.conf -Dhttp.port=9001
Oops, cannot start the server.
java.io.FileNotFoundException: /var/run/${{app_name}}.pid (Permission denied)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.(FileOutputStream.java:213)
at java.io.FileOutputStream.(FileOutputStream.java:162)
at play.core.server.ProdServerStart$.createPidFile(ProdServerStart.scala:131)
at play.core.server.ProdServerStart$.start(ProdServerStart.scala:45)
at play.core.server.ProdServerStart$.main(ProdServerStart.scala:27)
at play.core.server.ProdServerStart.main(ProdServerStart.scala)

@awaemmanuel
You can edit file /etc/kafka-manager/application.ini and replace path /var/run/${{app_name}}.pid.
And you can put -Dconfig.file=/usr/local/kafka-manager/conf/application.conf -Dhttp.port=9001 into this file.

Hello @alexshadow007,
Thanks for your response.
What should I replace -Dpidfile.path=/var/run/{{app_name}}.pid with please?

@awaemmanuel
You don't have permissions to write into /var/run/.
You must use folder which you have write permissions.
For example: -Dpidfile.path=/tmp/kafka-manager.pid.

Thanks that works, just have another error that seems related to RequireJS
Please file a bug at: http://github.com/webjars/json/issues/new
[warn] o.w.RequireJS - Could not read WebJar RequireJS config for: dustjs-linkedin 2.6.1
Please file a bug at: http://github.com/webjars/dustjs-linkedin/issues/new

@awaemmanuel https://github.com/yahoo/kafka-manager/pull/185

@alexshadow007 :I've changed the dependencies of dustjs and json. Recompiled. The warning disappears, but nothing shows on the UI. Blank page. All my brokers are all up and running.

@alexshadow007 - I get the following error when starting kafka-manager...
my application.ini as follows,
-Dpidfile.path=kafka-manager.pid
-Dconfig.file=application.conf
-Dhttp.port=9077
$ ./kafka-manager
21:58:32,654 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]
21:58:32,654 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
21:58:32,655 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/C:/GIT-workspace/kafka/kafka-manager/target/universal/kafka-manager-<IP_ADDRESS>/conf/logback.xml]
21:58:32,859 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
21:58:32,861 |-INFO in ch.qos.logback.core.joran.action.ConversionRuleAction - registering conversion word coloredLevel with class [play.api.Logger$ColoredLevel]
21:58:32,861 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
21:58:32,871 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE]
21:58:32,924 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
21:58:33,011 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No compression will be used
21:58:33,013 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern application.%d{yyyy-MM-dd}.log for the active file
21:58:33,020 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - The date pattern is 'yyyy-MM-dd' from file name pattern 'application.%d{yyyy-MM-dd}.log'.
21:58:33,020 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Roll-over at midnight.
21:58:33,025 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Setting initial period to Tue Feb 02 21:58:33 MST 2016
21:58:33,031 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file name: application.home_IS_UNDEFINED/logs/application.log
21:58:33,032 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is set to [application.home_IS_UNDEFINED/logs/application.log]
21:58:33,039 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Failed to create parent directories for [C:\GIT-workspace\kafka\kafka-manager\target\universal\kafka-manager-<IP_ADDRESS>\application.home_IS_UNDEFINED\logs\application.log]
21:58:33,040 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - openFile(application.home_IS_UNDEFINED/logs/application.log,true) call failed. java.io.FileNotFoundException: application.home_IS_UNDEFINED\logs\application.log (The system cannot find the path specified)
at java.io.FileNotFoundException: application.home_IS_UNDEFINED\logs\application.log (The system cannot find the path specified)
at      at java.io.FileOutputStream.open0(Native Method)
at      at java.io.FileOutputStream.open(FileOutputStream.java:270)
at      at java.io.FileOutputStream.(FileOutputStream.java:213)
at      at ch.qos.logback.core.recovery.ResilientFileOutputStream.(ResilientFileOutputStream.java:28)
at      at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:148)
at      at ch.qos.logback.core.FileAppender.start(FileAppender.java:108)
at      at ch.qos.logback.core.rolling.RollingFileAppender.start(RollingFileAppender.java:86)
at      at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
at      at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:317)
at      at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:196)
at      at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:182)
at      at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:62)
at      at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:149)
at      at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:135)
at      at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:99)
at      at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:49)
at      at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
at      at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:152)
at      at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
at      at org.slf4j.impl.StaticLoggerBinder.(StaticLoggerBinder.java:55)
at      at org.slf4j.LoggerFactory.bind(LoggerFactory.java:141)
at      at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:120)
at      at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:331)
at      at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:283)
at      at play.api.Logger$.(Logger.scala:177)
at      at play.api.Logger$.(Logger.scala)
at      at play.api.inject.guice.GuiceApplicationBuilder.applicationModule(GuiceApplicationBuilder.scala:73)
at      at play.api.inject.guice.GuiceBuilder.injector(GuiceInjectorBuilder.scala:126)
at      at play.api.inject.guice.GuiceApplicationBuilder.build(GuiceApplicationBuilder.scala:93)
at      at play.api.inject.guice.GuiceApplicationLoader.load(GuiceApplicationLoader.scala:21)
at      at play.core.server.ProdServerStart$.start(ProdServerStart.scala:52)
at      at play.core.server.ProdServerStart$.main(ProdServerStart.scala:27)
at      at play.core.server.ProdServerStart.main(ProdServerStart.scala)
21:58:33,041 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
21:58:33,044 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
21:58:33,048 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
21:58:33,051 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.AsyncAppender]
21:58:33,056 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [ASYNCFILE]
21:58:33,056 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to ch.qos.logback.classic.AsyncAppender[ASYNCFILE]
21:58:33,056 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNCFILE] - Attaching appender named [FILE] to AsyncAppender.
21:58:33,058 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNCFILE] - Setting discardingThreshold to 51
21:58:33,059 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.AsyncAppender]
21:58:33,059 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [ASYNCSTDOUT]
21:58:33,059 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to ch.qos.logback.classic.AsyncAppender[ASYNCSTDOUT]
21:58:33,059 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNCSTDOUT] - Attaching appender named [STDOUT] to AsyncAppender.
21:58:33,060 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNCSTDOUT] - Setting discardingThreshold to 51
21:58:33,061 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [play] to INFO
21:58:33,061 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [application] to INFO
21:58:33,061 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.avaje.ebean.config.PropertyMapLoader] to OFF
21:58:33,061 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.avaje.ebeaninternal.server.core.XmlConfigLoader] to OFF
21:58:33,061 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.avaje.ebeaninternal.server.lib.BackgroundThread] to OFF
21:58:33,061 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.gargoylesoftware.htmlunit.javascript] to OFF
21:58:33,061 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache.zookeeper] to INFO
21:58:33,062 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to WARN
21:58:33,062 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [ASYNCFILE] to Logger[ROOT]
21:58:33,062 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [ASYNCSTDOUT] to Logger[ROOT]
21:58:33,062 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
21:58:33,063 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@3af9c5b7 - Registering current configuration as safe fallback point
21:58:32,654 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]
21:58:32,654 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
21:58:32,655 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/C:/GIT-workspace/kafka/kafka-manager/target/universal/kafka-manager-<IP_ADDRESS>/conf/logback.xml]
21:58:32,859 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
21:58:32,861 |-INFO in ch.qos.logback.core.joran.action.ConversionRuleAction - registering conversion word coloredLevel with class [play.api.Logger$ColoredLevel]
21:58:32,861 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
21:58:32,871 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE]
21:58:32,924 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
21:58:33,011 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No compression will be used
21:58:33,013 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern application.%d{yyyy-MM-dd}.log for the active file
21:58:33,020 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - The date pattern is 'yyyy-MM-dd' from file name pattern 'application.%d{yyyy-MM-dd}.log'.
21:58:33,020 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Roll-over at midnight.
21:58:33,025 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Setting initial period to Tue Feb 02 21:58:33 MST 2016
21:58:33,031 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file name: application.home_IS_UNDEFINED/logs/application.log
21:58:33,032 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is set to [application.home_IS_UNDEFINED/logs/application.log]
21:58:33,039 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Failed to create parent directories for [C:\GIT-workspace\kafka\kafka-manager\target\universal\kafka-manager-<IP_ADDRESS>\application.home_IS_UNDEFINED\logs\application.log]
21:58:33,040 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - openFile(application.home_IS_UNDEFINED/logs/application.log,true) call failed. java.io.FileNotFoundException: application.home_IS_UNDEFINED\logs\application.log (The system cannot find the path specified)
at java.io.FileNotFoundException: application.home_IS_UNDEFINED\logs\application.log (The system cannot find the path specified)
at      at java.io.FileOutputStream.open0(Native Method)
at      at java.io.FileOutputStream.open(FileOutputStream.java:270)
at      at java.io.FileOutputStream.(FileOutputStream.java:213)
at      at ch.qos.logback.core.recovery.ResilientFileOutputStream.(ResilientFileOutputStream.java:28)
at      at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:148)
at      at ch.qos.logback.core.FileAppender.start(FileAppender.java:108)
at      at ch.qos.logback.core.rolling.RollingFileAppender.start(RollingFileAppender.java:86)
at      at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
at      at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:317)
at      at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:196)
at      at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:182)
at      at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:62)
at      at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:149)
at      at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:135)
at      at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:99)
at      at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:49)
at      at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
at      at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:152)
at      at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
at      at org.slf4j.impl.StaticLoggerBinder.(StaticLoggerBinder.java:55)
at      at org.slf4j.LoggerFactory.bind(LoggerFactory.java:141)
at      at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:120)
at      at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:331)
at      at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:283)
at      at play.api.Logger$.(Logger.scala:177)
at      at play.api.Logger$.(Logger.scala)
at      at play.api.inject.guice.GuiceApplicationBuilder.applicationModule(GuiceApplicationBuilder.scala:73)
at      at play.api.inject.guice.GuiceBuilder.injector(GuiceInjectorBuilder.scala:126)
at      at play.api.inject.guice.GuiceApplicationBuilder.build(GuiceApplicationBuilder.scala:93)
at      at play.api.inject.guice.GuiceApplicationLoader.load(GuiceApplicationLoader.scala:21)
at      at play.core.server.ProdServerStart$.start(ProdServerStart.scala:52)
at      at play.core.server.ProdServerStart$.main(ProdServerStart.scala:27)
at      at play.core.server.ProdServerStart.main(ProdServerStart.scala)
21:58:33,041 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
21:58:33,044 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
21:58:33,048 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
21:58:33,051 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.AsyncAppender]
21:58:33,056 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [ASYNCFILE]
21:58:33,056 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to ch.qos.logback.classic.AsyncAppender[ASYNCFILE]
21:58:33,056 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNCFILE] - Attaching appender named [FILE] to AsyncAppender.
21:58:33,058 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNCFILE] - Setting discardingThreshold to 51
21:58:33,059 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.AsyncAppender]
21:58:33,059 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [ASYNCSTDOUT]
21:58:33,059 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to ch.qos.logback.classic.AsyncAppender[ASYNCSTDOUT]
21:58:33,059 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNCSTDOUT] - Attaching appender named [STDOUT] to AsyncAppender.
21:58:33,060 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNCSTDOUT] - Setting discardingThreshold to 51
21:58:33,061 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [play] to INFO
21:58:33,061 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [application] to INFO
21:58:33,061 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.avaje.ebean.config.PropertyMapLoader] to OFF
21:58:33,061 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.avaje.ebeaninternal.server.core.XmlConfigLoader] to OFF
21:58:33,061 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.avaje.ebeaninternal.server.lib.BackgroundThread] to OFF
21:58:33,061 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.gargoylesoftware.htmlunit.javascript] to OFF
21:58:33,061 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache.zookeeper] to INFO
21:58:33,062 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to WARN
21:58:33,062 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [ASYNCFILE] to Logger[ROOT]
21:58:33,062 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [ASYNCSTDOUT] to Logger[ROOT]
21:58:33,062 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
21:58:33,063 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@3af9c5b7 - Registering current configuration as safe fallback point
21:58:33,115 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNCFILE] - Worker thread will flush remaining events before exiting.
21:58:33,116 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNCFILE] - Queue flush finished successfully within timeout.
21:58:33,116 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNCSTDOUT] - Worker thread will flush remaining events before exiting.
21:58:33,116 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNCSTDOUT] - Queue flush finished successfully within timeout.
21:58:33,122 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
21:58:33,123 |-INFO in ch.qos.logback.core.joran.action.ConversionRuleAction - registering conversion word coloredLevel with class [play.api.Logger$ColoredLevel]
21:58:33,123 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
21:58:33,123 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE]
21:58:33,124 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
21:58:33,125 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No compression will be used
21:58:33,125 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern application.%d{yyyy-MM-dd}.log for the active file
21:58:33,126 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - The date pattern is 'yyyy-MM-dd' from file name pattern 'application.%d{yyyy-MM-dd}.log'.
21:58:33,126 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Roll-over at midnight.
21:58:33,126 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Setting initial period to Tue Feb 02 21:58:33 MST 2016
21:58:33,126 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file name: C:\GIT-workspace\kafka\kafka-manager\target\universal\kafka-manager-<IP_ADDRESS>/logs/application.log
21:58:33,126 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is set to [C:\GIT-workspace\kafka\kafka-manager\target\universal\kafka-manager-<IP_ADDRESS>/logs/application.log]
21:58:33,128 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [play] to INFO
21:58:33,128 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [application] to DEBUG
21:58:33,129 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.avaje.ebean.config.PropertyMapLoader] to OFF
21:58:33,129 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.avaje.ebeaninternal.server.core.XmlConfigLoader] to OFF
21:58:33,129 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.avaje.ebeaninternal.server.lib.BackgroundThread] to OFF
21:58:33,129 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.gargoylesoftware.htmlunit.javascript] to OFF
21:58:33,129 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache.zookeeper] to INFO
21:58:33,129 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [akka] to INFO
21:58:33,129 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [kafka] to INFO
21:58:33,129 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO
21:58:33,129 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to Logger[ROOT]
21:58:33,129 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
21:58:33,129 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@6f27a732 - Registering current configuration as safe fallback point
Oops, cannot start the server.
com.google.inject.ProvisionException: Unable to provision, see the following errors:

Could not find a suitable constructor in controllers.Application. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private.
at controllers.Application.class(Application.scala:16)
while locating controllers.Application
for parameter 1 at router.Routes.(Routes.scala:63)
while locating router.Routes
while locating play.api.inject.RoutesProvider
while locating play.api.routing.Router

Could not find a suitable constructor in controllers.Cluster. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private.
at controllers.Cluster.class(Cluster.scala:28)
while locating controllers.Cluster
for parameter 2 at router.Routes.(Routes.scala:63)
while locating router.Routes
while locating play.api.inject.RoutesProvider
while locating play.api.routing.Router

Could not find a suitable constructor in controllers.Consumer. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private.
at controllers.Consumer.class(Consumer.scala:16)
while locating controllers.Consumer
for parameter 5 at router.Routes.(Routes.scala:63)
while locating router.Routes
while locating play.api.inject.RoutesProvider
while locating play.api.routing.Router

Could not find a suitable constructor in controllers.Logkafka. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private.
at controllers.Logkafka.class(Logkafka.scala:33)
while locating controllers.Logkafka
for parameter 4 at router.Routes.(Routes.scala:63)
while locating router.Routes
while locating play.api.inject.RoutesProvider
while locating play.api.routing.Router

Could not find a suitable constructor in controllers.PreferredReplicaElection. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private.
at controllers.PreferredReplicaElection.class(PreferredReplicaElection.scala:26)
while locating controllers.PreferredReplicaElection
for parameter 6 at router.Routes.(Routes.scala:63)
while locating router.Routes
while locating play.api.inject.RoutesProvider
while locating play.api.routing.Router

Could not find a suitable constructor in controllers.ReassignPartitions. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private.
at controllers.ReassignPartitions.class(ReassignPartitions.scala:27)
while locating controllers.ReassignPartitions
for parameter 7 at router.Routes.(Routes.scala:63)
while locating router.Routes
while locating play.api.inject.RoutesProvider
while locating play.api.routing.Router

Could not find a suitable constructor in controllers.Topic. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private.
at controllers.Topic.class(Topic.scala:33)
while locating controllers.Topic
for parameter 3 at router.Routes.(Routes.scala:63)
while locating router.Routes
while locating play.api.inject.RoutesProvider
while locating play.api.routing.Router

Could not find a suitable constructor in controllers.api.KafkaStateCheck. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private.
at controllers.api.KafkaStateCheck.class(KafkaStateCheck.scala:19)
while locating controllers.api.KafkaStateCheck
for parameter 8 at router.Routes.(Routes.scala:63)
while locating router.Routes
while locating play.api.inject.RoutesProvider
while locating play.api.routing.Router

8 errors
at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1025)
at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1051)
at play.api.inject.guice.GuiceInjector.instanceOf(GuiceInjectorBuilder.scala:321)
at play.api.inject.guice.GuiceInjector.instanceOf(GuiceInjectorBuilder.scala:316)
at play.api.Application$class.routes(Application.scala:112)
at play.api.DefaultApplication.routes(Application.scala:241)
at play.api.Play$$anonfun$start$1.apply$mcV$sp(Play.scala:90)
at play.api.Play$$anonfun$start$1.apply(Play.scala:87)
at play.api.Play$$anonfun$start$1.apply(Play.scala:87)
at play.utils.Threads$.withContextClassLoader(Threads.scala:21)
at play.api.Play$.start(Play.scala:87)
at play.core.server.ProdServerStart$.start(ProdServerStart.scala:54)
at play.core.server.ProdServerStart$.main(ProdServerStart.scala:27)
at play.core.server.ProdServerStart.main(ProdServerStart.scala)

You can try setting it to put it under the /var/log/kafka-manager directory. I build an RPM from the project and part of that it created a system user kafka-manager which when I tried to start the service it created /var/log/kafka-manager
My application.ini
-Dconfig.file=/usr/share/kafka-manager/conf/application.conf
-Dpidfile.path=/var/run/kafka-manager/kafka-manager.pid
-Dhttp.host=<IP_ADDRESS>
-Dhttp.port=9001

Is this still an open issue?  The pid file path can be controlled by the application.ini file as haydenk noted about.

@venkates77  I've got the same error, have you got any solutions for this?

If you are making a rpm package you must edit src/templates/etc-default and change the JAVA_OPTS (and probably PIDFILE even though it doesn't appear to get read):
-/var/run/${{app_name}}/.pid
+/var/run/${{app_name}}/running.pid
Before making the package.  If you already made the package.  You can just edit /etc/default/kafka-manager and change the pid on the JAVA_OPTS line.
At least that is what worked for me.

Did anyone resolve this problem - https://github.com/yahoo/kafka-manager/issues/192#issuecomment-179010987

I have a pull request to resolve this issue, see: https://github.com/yahoo/kafka-manager/pull/321


Theme colors are not applied correctly

When I override my selected themes (light / dark) from daisyui and set my CI primary color and inspecting the result in the browser (for example, the daisyui primary button) the color is not the same.
See sample:

How do I manage to see the same HEX color in the UI as defined in my theme?
The color difference can be verified using color picker and also using the Chrome dev tools.

Turns out that the color my stakeholder provided was not converting from hex to hsl and back consistently. I think it is an color issue and have nothing to do with daisyui, since I found other colors online and with them everything worked as expected.

It should work correctly 🤔
daisyUI is using this library to change color formats and in my experience, it's accurate:
https://www.npmjs.com/package/color
Can you give me your color palette so I can test?

I just dived into it and saw that daisyui is converting to HSL. After that I tested my HEX '#314EF3' by putting it into an HSL converter, than took the HSL and converted it back to HEX using the same tool. The HEX at the end was different from my original. So there is nothing wrong with daisy, but with the color of my stakeholder.
I think there is no need for further investigation.

The reason that you're seeing a different Hex code is because the decimals in hex values are being rounded.
Here are the exact numbers:
#314EF3 => hsl(231,89%,57.3%)
#2F4DF3 => hsl(230.8,89.1%,56.9%)

As you can see, the difference is so low and in my opinion, it's safe to say they are the same colors. It's impossible to distinguish them from each other.


Checksum Change

Just to check - I get a different checksum for collectionandqueries.tar.gz but end up with the same baseline results.

Woah. This is odd. I just redownloaded the tarball and confirm @edwardhdlu 's checksum.
I also have my tarball from previous, which confirms the checksum in the doc.
So the tarball's changed recently?!
@Victor0118 @rodrigonogueira4 do you know anything about this?

I think @rodrigonogueira4 downloaded the MSMARCO corpus quite long ago. I guess they have added some other files to the tarball since then but do not change collection.tsv.

MS Marco organizers added some files to the collection tar file:
https://github.com/dfcf93/MSMARCO/issues/29

Okay, great! Thanks @edwardhdlu


Relax rules for decoding JSON for asides with custom styles

Bug/issue #, if applicable:
rdar://117158675
Summary
Today DocC normally encodes aside block content as JSON like this:
 {
  "type": "aside",
  "content": [

  ],
  "style": "important"
}

...for a set of standard styles ("tip", "important", "experiment", etc.). These styles are defined in the Swift Markdown package.
Aside blocks can also use a custom style that is not defined in Swift Markdown, in which case DocC will encode the aside as JSON by setting style="note" and then appending an optional name attribute:
 {
  "type": "aside",
  "content": [

  ],
  "style": "note",
  "name": "Some Custom Title"
}

When decoding asides, DocC uses the opposite logic: If both style="note" and a name attribute is present, then set the style to the given name. Otherwise, directly save the style.
However, this makes it impossible to parse JSON containing asides that might be generated by other tools which do not follow the rule about style="note". The code change in this PR allows RenderBlockContent#init(from decoder:) to be a bit more flexible when decoding JSON. After merging this change, DocC will always save the value of the name attribute as the style if it is present, regardless of what style is set to.
For example, while parsing this JSON:
 {
  "type": "aside",
  "content": [

  ],
  "style": "important",
  "name": "Some Custom Title"
}

... DocC will discard "important" and instead set style="Some Custom Title".
Dependencies
None.
Testing
Create an aside in some documentation with a custom style, for example like this:
## Overview

> Custom Title: this is an important note.

Then compile the content, find the Render JSON file representing this page, and find the encoded version of this aside. For example:
jq < .docc-build/data/documentation/testasides.json '.primaryContentSections[0].content[1]'
{
  "name": "Custom Title",
  "style": "note",
  "type": "aside",
  "content": [
    {
      "type": "paragraph",
      "inlineContent": [
        {
          "type": "text",
          "text": "this is an important note."
        }
      ]
    }
  ]
}

Manually edit the JSON and set the style attribute to some other value, such as "important:"
jq < .docc-build/data/documentation/testasides.json '.primaryContentSections[0].content[1]'
{
  "name": "Custom Title",
  "style": "important",
  "type": "aside",
  "content": [
    {
      "type": "paragraph",
      "inlineContent": [
        {
          "type": "text",
          "text": "this is an important note."
        }
      ]
    }
  ]
}

Now write a small Swift program that parses this modified JSON file and displays the custom title of this aside:
let path = "file:///path/to/testasides.json"
if let url = URL(string: path) {
    let data = try Data(contentsOf: url)
    let renderNode = try JSONDecoder().decode(RenderNode.self, from: data)
    let sec = renderNode.primaryContentSections[0] as! ContentRenderSection
    if case let .aside(aside) = sec.content[1] {
        print("Custom Aside Title: \(aside.style.displayName)")
    }
}

It should display the custom title, and not "important:"
Custom Aside Title: Custom Title

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x ] Ran the ./bin/test script and it succeeded
~~- [ ] Updated documentation if necessary``

@swift-ci please test

@swift-ci please test


feat: add tsconfig.json to basic example

Description
Resolves #3402. Added tconfig.json and src directory to the basic example to show possible configuration while keeping the example simple.
Included a few basic compiler options in the tsconfig (module, target, moduleResolution, strict)  -as well as the include and exclude fields - to reflect configuration that one might commonly see. Added an example of a function export to src to provide an example of testing a module.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
[ ] Ideally, include a test that fails without this PR but passes with it.
[x] Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

[x] Run the tests with pnpm test:ci.

Documentation

[ ] If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

[x] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

thanks!


Since a couple of months EV3s (only EV3devs) cannot always connect to the server

mainly during peaks, e.g. 10 to 12 in the morning. Seems that EV3Dev is trying to connect to the lab first with https and second with http. Our server has an proxy rule to redirect all incoming traffic to https unless it is a robot (identified by a specific string in the header) with old firmware (versions which haven't supported https on the robot). The last documented flag in the header was "... 2.7 ...", but it seems that EV3Dev is having "... 3.4 ...".
To Reproduce
Steps to reproduce the behavior:
difficult, maybe change the code to connect only with html to reproduce the error
Expected behavior
EV3Dev tries several times to connect and succeed finally.
This might work much more reliable if EV3dev tries to connect again with https instead of http. We could also change the rule in the apache for older versions.

A few details:

only very old installations should use "ulrlib .. 2.7" as a user-agent string, newer ones should use "urllib 3.x". Ideally we don't hard-code the version to '3.4'
the beahaviour switched from trying http first and then https to now try https first and only fallback to http
I need to keep http support for developers testing to localhost and to users that use a raspberry pi
CHanging the setting to include http or https would be nice but needs also ev3dev UI updates and that will take time to get released :/

The code in question is here:
https://github.com/OpenRoberta/robertalab-ev3dev/blob/develop/roberta/lab.py#L310
An alternative to trying the protocol could be to pattern-match the url and use https: for *.openroberta.org and http for anything else unless there already is a protocol prefix. This way people can put https://myserver.org into the UI and it will work.
Sounds like a plan?

In /etc/apache2/sites-available resp sites-enabled the file lab.open-roberta.org.80.conf was changed to filter a bit more general: RewriteCond %{HTTP_USER_AGENT} !^Python-urllib/*. The configuration was reloaded (thanx to Beate).
Thus, the problem should be fixed. @ensonic: pls inform us, if the problem remains.
Avoiding http in general would be a better solution. We should work on that in the future. If we disable ev3lejosv0 (which needs http always) somewhere down the line, this would be a good moment to close http access at all.


Put back C++ JWTCredentials code and add a test case in interop test.

Somehow the code was dropped somewhere along the road...

LGTM but looks like python is broken. I'm sure why though. Maybe @nathanielmanistaatgoogle could have a look: https://travis-ci.org/grpc/grpc/jobs/54016096

The python build seems fine to me?

Python build is now fine. It was broken when I made the comment.

Done.


[FIX] sap.m.OverflowToolbar: Fix @extends information

Thanks, this is merged to master (for 1.40) now. A downport to 1.38 may happen; in this case you'll see this here.


Hive Metadata import problem

hive metadata is stored in mysql. Import the metadata as follows：
./metadata-extract.sh -p "{"jdbcDriver": "com.mysql.jdbc.Driver", "jdbcUrl": "jdbc:mysql://<IP_ADDRESS>:3306/metastore", "jdbcUser": "test","jdbcPassword": "test","dbName": "test"}" -d "hive" -r  "student_ext"
The import process can be successful, but quicksql treats the hive database as mysql, and the tables querying the hive database are looked up as mysql

This problem has been fixed. Refer to #220


Revise sample to use msal-react instead of msal-browser

The sample was previously using msal-browser within a HOC (authProvider.js) to enable authentication. This PR replaces it with msal-react. As msal-react brings its own HOC, authProvider.js was no longer required.

Decided to keep this sample as it is to accommodate older React APIs and patterns . Closing.


DNM - Introduce x_DISABLE_SIGN option

-- RFC --
Introduce the T_COSE_DISABLE_SIGN option and replace T_COSE_DISABLE_SIGN1 with it.
The tests that use multiple signatures can also be disabled with this option.
COSE_Sign1 structure support is always enabled.
Related issue: #111
Note:
The tests are currently failing, but it is expected since this PR and #211 are connected and
this one is still in progress.

Is DNM De novo mutation? :-)

Is DNM De novo mutation? :-)

"WIP" might have been better. :)
Thank you for the feedback, I've updated the PR accordingly.


syntax error near unexpected token `('

I've pulled from docker but I'm not sure whether I'm running it correctly.  This is what I'm trying...
'C:\Users\me> docker run kfei/slack-cleaner slack-cleaner --token "xoxp-#####" --message --channel general --user "*"`
And this is the error I get:
import: unable to open X server `' @ error/import.c/ImportImageCommand/364.
import: unable to open X server `' @ error/import.c/ImportImageCommand/364.
/usr/local/bin/slack-cleaner: line 7: from: command not found
/usr/local/bin/slack-cleaner: slack-cleaner: line 10: syntax error near unexpected token `('
/usr/local/bin/slack-cleaner: slack-cleaner: line 10: `    sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0])'

Any guidance would be greatly appreciated.  I generated the token from https://api.slack.com/docs/oauth-test-tokens

running docker run -it --rm kfei/slack-cleaner and inside of the docker container slack-cleaner --token "xoxp-#####" --message --channel general --user "*" works just fine. not sure why it's not working from a single run command.

That worked -- thank you!

How can I create a script that does this?


[feat][zk] Enable certificate refresh for Quorum and Netty Servers

Fixes https://github.com/apache/pulsar-helm-chart/issues/285
Motivation
The current Pulsar SSL Server Contexts always reload certificates from the file system. Zookeeper supports such options, but we do not enable them by default. I propose we do that.
Apache Zookeeper documentation:

sslQuorumReloadCertFiles : (No Java system property) New in 3.5.5, 3.6.0: Allows Quorum SSL keyStore and trustStore reloading when the certificates on the filesystem change without having to restart the ZK process. Default: false

client.certReload : (Java system property: zookeeper.client.certReload) New in 3.7.2, 3.8.1, 3.9.0: Allows client SSL keyStore and trustStore reloading when the certificates on the filesystem change without having to restart the ZK process. Default: false

Modifications

Enable the Quorum server to update its context (already available)
Enable the Netty Server to update its context (not available until ZK 3.8.1 or 3.9.0 https://issues.apache.org/jira/browse/ZOOKEEPER-3806, but won't hurt anything to get for free when we upgrade)

Verifying this change
This is a trivial configuration change.
Does this pull request potentially affect one of the following parts:

[x] The default values of configurations

I do not believe this needs a PIP because our standard default is already to refresh certificates in the broker, function worker, the proxy, and the websocket proxy.
Documentation

[x] doc-not-needed

Matching PR in forked repository
PR in forked repository: https://github.com/michaeljmarshall/pulsar/pull/5

sslQuorumReloadCertFiles : (No Java system property) New in 3.5.5, 3.6.0: Allows Quorum SSL keyStore and trustStore reloading when the certificates on the filesystem change without having to restart the ZK process. Default: false

client.certReload : (Java system property: zookeeper.client.certReload) New in 3.7.2, 3.8.1, 3.9.0: Allows client SSL keyStore and trustStore reloading when the certificates on the filesystem change without having to restart the ZK process. Default: false

LGTM

Good idea to reference the ZK documentation @nodece. I updated my PR's description with it. Thanks!

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@69deb1f). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #18097   +/-   ##
=========================================
  Coverage          ?   27.05%
  Complexity        ?     3540
=========================================
  Files             ?      393
  Lines             ?    43424
  Branches          ?     4464
=========================================
  Hits              ?    11748
  Misses            ?    29826
  Partials          ?     1850

Flag
Coverage Δ

unittests
27.05% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.


dictionary format when no cell type labels in adata

Could you please provide an example of gene_set dictionary for cases where 'use_cell_types = False'? I can't seem to find the right format.
Thanks

Hi,
Thank you for using Spectra.
Indeed, there was a bug when setting use_celltypes = False we have fixed this now and we have added an example in the tutorial (see cell number 12)
https://github.com/dpeerlab/spectra/blob/main/notebooks/example_notebook.ipynb
let me know if that helps.
Thank you,
Thomas

I can confirm that use_celltypes=False works fine with a dictionary with everything under a global heading
gene_set_annotations = {
    "global": {"G2M phase": g2m_genes,
               "S phase": s_genes,
               "Hallmark_Hypoxia": hypoxia_genes,
               "Hallmark_Inflammation": inflammatory_genes,
               "Hallmark_Il2_Stat5": il2_genes,
               "Hallmark_Il6_JAK_Stat3": il6_genes,
               "Hallmark_IFNg_response": ifng_genes,
               "Hallmark_TGFb_activity": tgfb_genes,
               "Hallmark_Apoptosis": apoptosis_genes,
               "Elyada_myCAF": myCAF,
               "Elyada_iCAF": iCAF
}

Though I'm trying to load a saved model with spc.load_from_pickle and it's not liking any option for the cell_type_key parameter. I'm not 100% positive they're related, but not sure what else it may be.
adata has spectra output:

Got an error 1) omitting the parameter, 2) trying to set to None, 3) assigning an arbitrary cell type key not used in the spectra run, and 4) setting a column in obs to 'global' (below)
---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
Cell In [99], line 1
----> 1 model = spc.load_from_pickle('../output/iflc_disease_spectra', adata,
      2                             gene_set_annotations, cell_type_key='celltype_level2')

File ~/mambaforge/envs/scvi-env/lib/python3.9/site-packages/spectra/spectra.py:1240, in load_from_pickle(fp, adata, gs_dict, cell_type_key)
   1239 def load_from_pickle(fp, adata, gs_dict, cell_type_key):
-> 1240     model = SPECTRA_Model(X = adata[:,adata.var["spectra_vocab"]].X, labels = np.array(adata.obs[cell_type_key]),  L = adata.uns["SPECTRA_L"],
   1241                           vocab = adata.var_names[adata.var["spectra_vocab"]], gs_dict = gs_dict)
   1242     model.load(fp, labels = np.array(adata.obs[cell_type_key]))
   1243     return(model)

File ~/mambaforge/envs/scvi-env/lib/python3.9/site-packages/spectra/spectra.py:541, in SPECTRA_Model.__init__(self, X, labels, L, vocab, gs_dict, use_weights, adj_matrix, weights, lam, delta, kappa, rho, use_cell_types)
    537     else:
    538         adj_matrix, weights = spectra_util.process_gene_sets_no_celltypes(gs_dict = gs_dict, gene2id = gene2id, weighted = use_weights)
--> 541 self.internal_model = SPECTRA(X = X, labels = labels, adj_matrix = adj_matrix, L = L, weights = weights, lam = lam, delta=delta,kappa = kappa, rho = rho, use_cell_types = use_cell_types)
    543 self.cell_scores = None
    544 self.factors = None

File ~/mambaforge/envs/scvi-env/lib/python3.9/site-packages/spectra/spectra.py:210, in SPECTRA.__init__(self, X, labels, adj_matrix, L, weights, lam, delta, kappa, rho, use_cell_types)
    208     self.rho = nn.ParameterDict()
    209 #initialize global params
--> 210 self.theta["global"] = nn.Parameter(Normal(0.,1.).sample([self.p, self.L["global"]]))
    211 self.eta["global"] = nn.Parameter(Normal(0.,1.).sample([self.L["global"], self.L["global"]]))
    212 self.gene_scaling["global"] = nn.Parameter(Normal(0.,1.).sample([self.p]))

IndexError: invalid index to scalar variable.

The only thing I can think of is that spectra was run on a cluster and I'm now looking at the results locally. adata and model were saved in the run, but the `gs_dict' was remade locally and might be differing in some way. Not sure that could explain it but will explore

Thank you Thomas for the fix,  It now works very well for me now and thank you for the great tool!
Adrien

Hi dpcook,
sorry for the late reply. Yes, the spc.load_from_pickle function requires an identical gene set dictionary.
It is easier to just use pickle to save the model instead of the Spectra method.
We have corrected this in the tutorial which we now provide on Colab.
https://github.com/dpeerlab/spectra/blob/main/notebooks/Spectra_Colaboratory_tutorial.ipynb
Please let me know if that helps.
Thanks,
Thomas

This is great--thanks Thomas! Feel free to close the issue.

Thank you :)


fix: led strip

@jhanca-robotecai
Previously leds were not working correctly.
You are right, the current version depends on ASR, HMI and TTS being synchronized. It was tested on the robot extensively and works stable.


[Bug]: cannot type the passphrase for the ssh key when i git push

Opencommit Version
3.0.16
Node Version
20.15.1
NPM Version
10.7.0
What OS are you seeing the problem on?
Other Linux Distro
What happened?
after generating the commit  message and accepting it. it asks for pushing but i am using ssh key so i should type the passphrase but i can't

Expected Behavior
hwn i choose to push the cli asks for the passphrase and i can type it
Current Behavior
it shows the msg to type the passphrase but nothing is typed
Possible Solution
No response
Steps to Reproduce
No response
Relevant log output
No response

@banoni-dev
Hi,
Maybe this isn't the answer you expected, but you can skip the git-push step by using the OCO_GITPUSH environment variable.
If you set OCO_GITPUSH to false, the oco CLI will not automatically push your branch after generating the commit.
# ~/.opencommit

OCO_GITPUSH=false

@matscube hi, thank you for the help. I think what we need is to pipe stdout into the cli logs somehow, if you have any ideas — please share in this thread <3

@di-sukharev Hi,
By using the stdin option of execa, it might be possible to input the SSH key password during the git push process of oco and pipe it to the git command.
However, if users cache the password with ssh-agent, they won't be prompted for a password during git push.
This issue could be addressed by caching the password in advance using ssh-add.
The use case for piping password input via stdin might be limited, but if there's demand, I can look into implementing this feature. What do you think?

https://github.com/sindresorhus/execa/tree/v7.0.0?tab=readme-ov-file#stdio
https://nodejs.org/api/child_process.html#child_process_options_stdio

Takanori, please do, it would be a great improvement. Lets pipe all the
stdout, it is good to also see husky and other pre-commit/push pipeline
logs

@banoni-dev please refer to this comment https://github.com/di-sukharev/opencommit/issues/369#issuecomment-2246805940 as a workaround


change in NLB / TLS Access Logs

Some fields will be added to NLB, but the regular expressions are too strict and cause errors. Since we don't know the details of the added field, we will modify the regular expression so that it will not cause an error even if it is added.

https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-access-logs.html#access-log-entry-format


Quickswap sources using the Input menu options

@Master92 did quite a lot of coding already, I took inspiration from his work which allows cycling through the source options.
On top of that I've added the option to choose to cycle only between HDZero and the expansion module, which is most useful on races where people use both systems, and for people flying lots of whoops with both systems.

I've added Toggle Mode to the Auto Scan screen, because this seemed the most logical to me. Open to suggestions!
The Cycle setting does cycle through all source options, the Race setting switches between the expansion module and HDZero. In case Race is selected, and anything other than the expansion module or HDZero is active, it will switch to HDZero when the button is pressed to switch sources.

The dropdown menu on the Input screen now has the option Toggle source added to the list, in this case I've set it on the Right long: button (not as default).
The code also takes into account that the expansion module can be switched off automatically, which is taken care of in the quickswap too.

#411 was already closed, but not implemented yet. This PR takes care of issue #411.

Would've been nice if you left me as the author of the code I wrote by cherry picking from my branch properly.
The changes, however look nice, good job. A little fronted documentation of what race mode means would be appreciated by many users, I think.
Also, squashing equally named commits would serve comprehensibility for the future imho 😉

Nice, thanks, how can I test it?

Would've been nice if you left me as the author of the code I wrote by cherry picking from my branch properly.
The changes, however look nice, good job. A little fronted documentation of what race mode means would be appreciated by many users, I think.
Also, squashing equally named commits would serve comprehensibility for the future imho 😉

Thanks for the tip, still new to using GitHub, will keep them in mind! Frontend documentation in the goggles GUI you mean? Other option would be to drop the config in the Auto Scan and add 2 options in the drop-down Input, one for Cycle sources and one for Toggle HD - Analog.

Nice, thanks, how can I test it?

GitHub does an automatic build to check the code. I think you could use that build to test, can be found under the Checks tab: https://github.com/hd-zero/hdzero-goggle/actions/runs/9419103738/artifacts/1579597591

Nice, thanks, how can I test it?

@DarthCedius I've made a few more changes, settings weren't stored properly when changing the setting from Cycle to Race. Did you try to update using the link I provided? There's a new build made by Github based on the latest fixes: https://github.com/hd-zero/hdzero-goggle/actions/runs/9428376367/artifacts/1581709527

Pilots may not associate the terminology Toggle Mode with Toggle Source function. wondering if they should be the same naming scheme. :man_shrugging:

Toggle sources and Toggle source?
or  maybe Inputs menu should have 2 options Toggle sources (all) Toggle sources (race)`? I'm unsure.

@nerdCopter Agreed, naming scheme should be in line.
Regarding the two options for implementation, I'm fine with either. Adding it to the inputs menu keeps everything in one page, which would keep things clean IMO. Cycle sources and Toggle sources could be the two added options.

Cycle will use all sources
Toggle will use HDZero - Expansion module

Since the Inputs menu is new, we can add a description for each option, including these two.
Who can be the deciding factor in choosing which path to follow for implementation?

[...] Cycle sources and Toggle sources could be the two added options.

i like that, albeit i'm "nobody" to decide.

Who can be the deciding factor in choosing which path to follow for implementation?

other interested community members or @ligenxxxx (or yourself :wink:) .

Nice, thanks, how can I test it?

@DarthCedius I've made a few more changes, settings weren't stored properly when changing the setting from Cycle to Race. Did you try to update using the link I provided? There's a new build made by Github based on the latest fixes: https://github.com/hd-zero/hdzero-goggle/actions/runs/9428376367/artifacts/1581709527

it's working great thanks, maybe you should add a temporary OSD info to state which input you are on.

Nice, thanks, how can I test it?

@DarthCedius I've made a few more changes, settings weren't stored properly when changing the setting from Cycle to Race. Did you try to update using the link I provided? There's a new build made by Github based on the latest fixes: https://github.com/hd-zero/hdzero-goggle/actions/runs/9428376367/artifacts/1581709527

it's working great thanks, maybe you should add a temporary OSD info to state which input you are on.

@DarthCedius
Thank you for your constructive feedback!
Temporary OSD info would be a nice to have when the cycle option is selected, I agree.
I'm not sure if I can implement that myself though, I'll have a look.

[...] Cycle sources and Toggle sources could be the two added options.

i like that, albeit i'm "nobody" to decide.

Who can be the deciding factor in choosing which path to follow for implementation?

other interested community members or @ligenxxxx (or yourself 😉) .

The more I think of it, the more I like that option too. Keeps the OSD menu cleaner and both options are integrated on one page. @ligenxxxx do you agree? If yes, I'll rework the code to remove the config in the Auto Scan page and add two options to the dropdown list on the Inputs page, Cycle sources and Toggle sources.

@sanderpuh , happy to test after commit/push on weekends. i dont have any hdmi to test that part though.

@sanderpuh , i'm happy to test after commit/push on weekends. i don't have any hdmi to test that part though.

Current commit seems to be working well, been using it for a while now on my own goggles without any issues. I've also implemented a beep on my end when sources are swapped as an audible indicator.
That being said, I'll rework the code to have 2 more options on the inputs page, one will be 'cycle sources' and the other will be 'toggle sources'. The Toggle mode menu item is no longer necessary, and can be dropped. The function to swap sources will stay the same. I'll have to timeblock some time next week, after next week it's time for some holidays :)
After implementation of these two items, we could further enhance by implementing #395 from @qvasic - Add a beep option to the OSD menu with setting Off, Boot and Source - which will enable the end user to not use the beep at all, use it to indicate booting has finished, or use it to indicate the source is switched and booting has finished.

This PR can be closed when PR #433 is merged.


Email Login Error Authorization Failed

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I set up Teslamate for the first time (USA user), chose to login Tesla via email/password instead of using existing API tokens. The error given was:

Error: :authorization_failed

In the SSH console, I see the following log:

teslamate_1  | 2021-11-17 16:40:27.614 [info] GET /sign_in
teslamate_1  | 2021-11-17 16:40:27.619 [info] Sent 200 in 5ms
teslamate_1  | 2021-11-17 16:41:47.463 [info] GET https://auth.tesla.com/oauth2/v3/authorize -> 200 (415.139 ms)
teslamate_1  | 2021-11-17 16:41:47.607 [error] POST https://auth.tesla.com/oauth2/v3/authorize -> 403 (138.538 ms)

If I go to the link https://auth.tesla.com/oauth2/v3/authorize given in the log via Chrome, it shows that the website reported an error:

Error has occurred
Bad Request

Expected Behavior
Expected to successfully log into my Tesla account via email/password to begin capturing data from my Tesla vehicle.
Steps To Reproduce

Go to public FQDN address.
Once at Teslamate log in screen, instead of using Access Token & Refresh Token, click "Use email and password" link at the bottom.
Once at the email and password screen log in, enter in credentials as the same as Tesla.com.
Click Sign in button.
Get a red banner displaying "Error: :authorization_failed".

Relevant log output
teslamate_1  | 2021-11-17 16:40:27.614 [info] GET /sign_in
teslamate_1  | 2021-11-17 16:40:27.619 [info] Sent 200 in 5ms
teslamate_1  | 2021-11-17 16:41:47.463 [info] GET https://auth.tesla.com/oauth2/v3/authorize -> 200 (415.139 ms)
teslamate_1  | 2021-11-17 16:41:47.607 [error] POST https://auth.tesla.com/oauth2/v3/authorize -> 403 (138.538 ms)

Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
1.25.0

Tesla now returns a page saying

Access Denied
You don't have permission to access "http://auth.tesla.com/oauth2/v3/authorize" on this server.

Until a few days ago you would have received an error message "Recaptcha is required" because Tesla require a Google reCAPTCHA to generate API tokens. See https://github.com/adriankumpf/teslamate/issues/1945#issuecomment-913684723.
The bottom line is that currently logging in is only possible with manually generated tokens.

Thanks for reviewing issue and providing greater clarity on the login issue. I was reluctant to use a Tesla token generating app, but since this leaves me no other choice, I've gone ahead and downloaded Tesla Tokens app for Android. I successfully logged in with the tokens generated and data are starting to be logged to Teslamate. Thanks for everything. :)

The docker image that is currently available is still giving this error when logging in with email/password, please disable logging in with email/password completely or warn that it is currently not possible to do so.

^Agreed plz note that email/password login is currently unavailable

Ok great, so now we can't login to Teslamate without generating tokens on the install and email login isn't supported? Get rid of the login for email then please.

Just to let others know - yesterday a big number (probably tens of thousands globally) of old tokens have been revoked by Tesla. There seems to be a security issue ongoing. Thus, a lot of Teslamate users will need to relogin/authenticate again and they might be confused by not functioning login with e-mail/password in Teslamate.
https://twitter.com/tezlabapp/status/1481180064926547969?s=21


feature request: ptpython extra

I would love to see an integration for ptpython.  Other people are interested too.

I looked into the code in ptpython that prints evaluated values in the REPL. It's not very feasible to inject prettyprinter there right now. I left a comment about that in the issue you linked to (https://github.com/prompt-toolkit/ptpython/issues/153#issuecomment-465896922).
If you or someone else were to create a PR to ptpython to make the integration feasible, it shouldn't be too hard to provide the integration on the prettyprinter side. A minimum would be to have a single method on the ptpython.repl.PythonRepl class that handles printing the evaluated value, so that prettyprinter could monkeypatch that method with its own. A nicer integration would be through a configurable hook as a part of the ptpython public API.


Env updates

Golden runs from this branch:

AutoRIFT: https://github.com/ASFHyP3/hyp3-testing/actions/runs/6029521709

Failed when attempting to download a FAILED job, which is a bug unrelated to this PR that I'll tackle separately.

InSAR: https://github.com/ASFHyP3/hyp3-testing/actions/runs/6029530520

Failed but produced good comparisons, so it's not an issue for this PR.

RTC: https://github.com/ASFHyP3/hyp3-testing/actions/runs/6029534173

Passed!

This PR unblocks #64


Wait for Tasks in _emit Before Moving On

Proposed changes

Add an option to wait for all tasks to complete before moving on. The recommendation is to ALWAYS take the event and use each on_ callback function to add the event to your own queue.
This work is meant to be done in this issue https://github.com/deepgram/deepgram-python-sdk/issues/264, but this issue will explicitly help with the thread management.
Context

Possible Implementation

Other information

This is available in the latest release:
https://github.com/deepgram/deepgram-python-sdk/releases/tag/v3.3.0


src: now using ubi8/nodejs-10

Pull Request Test Coverage Report for Build 270

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

Totals

Change from base Build 268:
0.0%

Covered Lines:
21

Relevant Lines:
22

💛  - Coveralls


_posts/0000-01-02-cneuhofer.md

Getting more confused.
How do you add a title?

AAAAGGGGHHHH!!!!!


Add Forwarded Header

Feature request
Add Forwarded Header
Feature description

https://www.nginx.com/resources/wiki/start/topics/examples/forwarded/
Perhaps with user-selected option on how to handle coexistence with X-Forwarded-*?
How the feature is useful
Adds the currently NGINX recommended, partial implementation of RFC 7239 standardized Forwarded header
Understandable if not wanting to implement partial solution... also, I don't mind taking a stab at it with PR.

👍 Always open to adding more options as long as they have sensible default values and easy to understand/configurable options for the user. You're most welcome to create a PR if you want!