fix: fix config file not working

The break is not needed and it lead to config files not work.

Codecov Report

Merging #13 into master will increase coverage by 2.55%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #13      +/-   ##
=========================================
+ Coverage   88.14%   90.7%   +2.55%
=========================================
  Files          20      20
  Lines         270     269       -1
=========================================
+ Hits          238     244       +6
+ Misses         32      25       -7

Impacted Files
Coverage Δ

commitizen/cli.py
88.23% <ø> (+13.23%)
:arrow_up:

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 e4840a0...f2264c3. Read the comment docs.

Thanks.
Just for future cases, the commit message could be fix: config file not working without the redundancy of 2 fix


AZ interactive fail

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az interactive
Errors:
The command failed with an unexpected error. Here is the traceback:
No module named 'prompt_toolkit.interface'
Traceback (most recent call last):
  File "/usr/local/Cellar/azure-cli/2.41.0/libexec/lib/python3.10/site-packages/knack/cli.py", line 233, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/local/Cellar/azure-cli/2.41.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 663, in execute
    raise ex
  File "/usr/local/Cellar/azure-cli/2.41.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/local/Cellar/azure-cli/2.41.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
    result = cmd_copy(params)
  File "/usr/local/Cellar/azure-cli/2.41.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/local/Cellar/azure-cli/2.41.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/usr/local/Cellar/azure-cli/2.41.0/libexec/lib/python3.10/site-packages/azure/cli/command_modules/interactive/custom.py", line 41, in start_shell
    azext_interactive.start_shell(cmd, style=style)
  File "/Users/dpulloquinga/.azure/cliextensions/interactive/azext_interactive/__init__.py", line 10, in start_shell
    from .azclishell.app import AzInteractiveShell
  File "/Users/dpulloquinga/.azure/cliextensions/interactive/azext_interactive/azclishell/app.py", line 33, in <module>
    from prompt_toolkit.interface import Application, CommandLineInterface
ModuleNotFoundError: No module named 'prompt_toolkit.interface'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az interactive

Expected Behavior
Environment Summary
macOS-13.0-x86_64-i386-64bit, Darwin 22.1.0
Python 3.10.8
Installer: HOMEBREW

azure-cli 2.41.0

Extensions:
interactive 0.4.5
enterprise-edge 0.1.1

Dependencies:
msal 1.20.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

Duplicate of https://github.com/Azure/azure-cli/issues/24213


Adding the ability to pass the providerName arg for default schemaFilePath construction

Without being able to pass a providerName, the user must specify the schemaFile
but 99% of our schemaFiles are in a standard location therefore we can make
this optional.
I thought about trying to pull the provider name out of the repoSlug but there
are no guarantees that the repo name relates to the providerName
So the user can now pass schemaFile or pass providerName and we can find the
correct schemaFile

Makes sense ... would consider making the behaviour explicit that only one of the arguments is set:

Raise error if both are set.
Indicate behaviour in flag docs.

I like this - I am going to add a wee bit more validation here

New functionality:
./dist/registrygen_darwin_amd64/registrygen metadata --repoSlug pulumi/pulumi-aws --schemaFile=""  --version v4.36.0 --publisher Pulumi
Error: `providerName` is required when `schemaFile` is not specified

This means we now need to do as follows:
/dist/registrygen_darwin_amd64/registrygen metadata --repoSlug pulumi/pulumi-aws --schemaFile=""  --version v4.36.0 --publisher Pulumi --providerName aws


db: _init: don't forget leading zeros

Leftover from #147

Codecov Report
Base: 69.02% // Head: 67.84% // Decreases project coverage by -1.17% :warning:

Coverage data is based on head (d6161c2) compared to base (bb3df65).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #148      +/-   ##
==========================================
- Coverage   69.02%   67.84%   -1.18%
==========================================
  Files          25       25
  Lines        1556     1552       -4
  Branches      219      158      -61
==========================================
- Hits         1074     1053      -21
- Misses        452      471      +19
+ Partials       30       28       -2

Impacted Files
Coverage Δ

src/dvc_objects/db.py
97.74% <100.00%> (ø)

src/dvc_objects/fs/system.py
63.23% <0.00%> (-20.59%)
:arrow_down:

tests/test_reflink.py
87.50% <0.00%> (-12.50%)
:arrow_down:

src/dvc_objects/fs/path.py
47.87% <0.00%> (-1.09%)
:arrow_down:

src/dvc_objects/fs/utils.py
36.97% <0.00%> (-0.53%)
:arrow_down:

src/dvc_objects/executors.py
31.11% <0.00%> (+0.67%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


removed the not numpy 1.15.2 pin

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Removed 'not numpy 1.15.2' pin as issues with numpy 1.15.2 build have now been fixed (see https://github.com/conda-forge/iris-feedstock/pull/41#discussion_r224928363).

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you, but it looks like there was nothing to do.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@dkillick

@corinnebosley nice!


💡 [REQUEST] - <deepseek-coder-1.3b-instruct>

Model introduction
Can you please test the 1.3B version of deepseek-coder-instruct? I think this would be good to know if one can run this on their phone or their 4GB video-card and still have room for a large context. On the benchmark site https://huggingface.co/spaces/mike-ravkine/can-ai-code-results, it competes very well with larger models. I would like a second opinion.
Model URL
https://huggingface.co/deepseek-ai/deepseek-coder-1.3b-instruct
Data type
float16
Additional instructions (Optional)
It should be like the other 6.7B and 34B deepseek-coder models you've tested so far.
Author
No
Security

[X] I confirm that the model is safe to run which does not contain any malicious code or content.

Integrity

[X] I confirm that the model comes from unique and original work and does not contain any plagiarism.

Thanks!

Thank you for testing @ganler. 7th place! It's quite good for a 1.3B model!  I wonder if the WizardLM team will further fine tune it. Thank you for putting it on the board! The DeepSeek team definitely know how to train a coding model!


Revert "Add explicit dependency to validatePom and generatePom tasks (#12807)"

This reverts commit c04dad58bbc941b8d5f18326d5c5cfb7ac312239.

Description
Revert "Add explicit dependency to validatePom and generatePom tasks (#12807)
Related Issues
See please https://github.com/opensearch-project/OpenSearch/pull/12807#issuecomment-2015266673

Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[x] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

❌ Gradle check result for c30d5d9: FAILURE

https://github.com/opensearch-project/OpenSearch/issues/12595
https://github.com/opensearch-project/OpenSearch/issues/12306
https://github.com/opensearch-project/OpenSearch/issues/12239

TY for the help here @reta! I will review the initial PR to see if I can provide any insight on how to prevent it from being a breaking change to the plugins.

❌ Gradle check result for c30d5d9: FAILURE

Caused by: java.lang.OutOfMemoryError: Java heap space

Would changing back ConfigureEach to all possibly resolve the incompatible issue with security plugin?

Would changing back ConfigureEach to all possibly resolve the incompatible issue with security plugin?

We need to test that and other plugins

❌ Gradle check result for c30d5d9: FAILURE

> Task :qa:wildfly:composeUp FAILED
Get "https://quay.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

❌ Gradle check result for c30d5d9: FAILURE

https://github.com/opensearch-project/OpenSearch/issues/10006
java.lang.Exception: Test abandoned because suite timeout was reached.
	at __randomizedtesting.SeedInfo.seed([81B30C60E4925A1F]:0)

Would changing back ConfigureEach to all possibly resolve the incompatible issue with security plugin?

We need to test that and other plugins

I just tested that changing back to all can run assemble on security plugin successfully.
☁  ~/workplace/security[main] ./gradlew assemble
=======================================
OpenSearch Build Hamster says Hello!
  Gradle Version        : 8.5
  OS Info               : Mac OS X 14.3 (x86_64)
  JDK Version           : 21 (Oracle JDK)
  JAVA_HOME             : /Library/Java/JavaVirtualMachines/jdk-21.jdk/Contents/Home
  Random Testing Seed   : C82B0FF391C689CE
  In FIPS 140 mode      : false
=======================================

> Task :compileJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.5/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD SUCCESSFUL in 44s
11 actionable tasks: 11 executed

This might be the issue that the previous compatibility tests failed on security plugin. https://github.com/opensearch-project/OpenSearch/pull/12807#issuecomment-2010933074

@reta I raised a PR to fix the incompatibility for security plugin. You can take a look there. https://github.com/opensearch-project/OpenSearch/pull/12876

Closing in favor of https://github.com/opensearch-project/OpenSearch/pull/12876


Support conversion of Java type variable declaration

String foo = "bar"

becomes
val foo: String = "bar"

Thanks!

You once helped me. I refactored the project into this website: https://gradle-kotlin-converter.vercel.app/


Updating the version to 2021.5.24 and corresponding SHA256 checksum.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] N/A Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] N/A Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Updating to the latest version on PyPi.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Update index.json file at stage level for each distribution

Description
Call UploadIndexFile.groovy to update latest build number after sucessfully building each distribution
Issues Resolved
Resolves https://github.com/opensearch-project/opensearch-build/issues/4167
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@Divyaasm please fix the conflict jenkins/opensearch-dashboards/distribution-build.jenkinsfile.

Made a comment in the related PR in the ci repo.


improve performance of ensureCanMutateNextListeners

Small improvements for preventing unnecesary calls of ensureCanMutateNextListeners

CI failing is not my fault 👀

Fixed the formatting issue on master.
How exactly does the change here improve performance?  What benchmarks have you run to see if there's an improvement?

Currently currentListeners.slice() calls at each dispatch, but it is unnecesary if it dispatch is not nesting. It is correct?

@markerikson I writing some simple benchmarks. It checks exactly the case solved by this PR - subscribe / unsubscribe after each dispatch.

Finally sat down to look through this. I don't think it really warrants the complexity increase for a 0.3 millisecond speed boost. I'd rather make things easier to read in this case. Thanks anyways for looking at it!


String literals for description

Seems like it's not possible to use """ or " to make some description in graphql schema. It returns an error:
panic: graphql: syntax error: unexpected "\"\"", expecting Ident

It is possible. However, this feature was introduced later and this is why it is opt-in in this library to avoid breaking changes. In order to use it you have to use a special schema option:
opts := []graphql.SchemaOpt{graphql.UseStringDescriptions()}
schema := graphql.MustParseSchema(s, &query{}, opts...)


README: that time of the year! 🎄

That time of the year :christmas_tree: - let's merge this without tests?
Screenshots (if appropriate):

To all of the CloudStack contributors - Happy Christmas and holidays!
/cc alphabetically-ish @alexandremattioli @andrijapanicsb @borisstoyanov @bwsw @chiradeep @DaanHoogland @davidjumani @GabrielBrascher @gsirett @harikrishna-patnala @K0zka @kiwiflyer @PaulAngus @mlsorensen @mike-tutkowski @milamberspace @msinhore @nathanejohnson @NuxRo @nvazquez @Pearl1594 @pdion891 @ravening @shwstppr @Spaceman1984 @steveroles @sureshanaparti @svenvogel @swill @syed @vladimirpetrov @weizhouapache @wido and so many others! (sorry guys in case I missed any of your handles - you're in thoughts as well)

LGTM

LGTM @rhtyd :)

Thanks @rhtyd Merry Christmas an happy holidays to you too.

+1
Happy holidays all! Here’s to a better 2021
Best regards,
From: Rohit Yadav<EMAIL_ADDRESS>Sent: 21 December 2020 11:47
To: apache/cloudstack<EMAIL_ADDRESS>Cc: Steve Roles<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [apache/cloudstack] README: that time of the year! 🎄 (#4554)
To all of the CloudStack contributors - Happy Christmas and holidays!
/cc alphabetically-ish @alexandremattiolihttps://github.com/alexandremattioli @andrijapanicsbhttps://github.com/andrijapanicsb @borisstoyanovhttps://github.com/borisstoyanov @bwswhttps://github.com/bwsw @chiradeephttps://github.com/chiradeep @DaanHooglandhttps://github.com/DaanHoogland @davidjumanihttps://github.com/davidjumani @GabrielBrascherhttps://github.com/GabrielBrascher @gsiretthttps://github.com/gsirett @harikrishna-patnalahttps://github.com/harikrishna-patnala @K0zkahttps://github.com/K0zka @kiwiflyerhttps://github.com/kiwiflyer @PaulAngushttps://github.com/PaulAngus @mlsorensenhttps://github.com/mlsorensen @mike-tutkowskihttps://github.com/mike-tutkowski @milamberspacehttps://github.com/milamberspace @msinhorehttps://github.com/msinhore @nathanejohnsonhttps://github.com/nathanejohnson @NuxRohttps://github.com/NuxRo @nvazquezhttps://github.com/nvazquez @Pearl1594https://github.com/Pearl1594 @pdion891https://github.com/pdion891 @raveninghttps://github.com/ravening @shwstpprhttps://github.com/shwstppr @Spaceman1984https://github.com/Spaceman1984 @steveroleshttps://github.com/steveroles @sureshanapartihttps://github.com/sureshanaparti @svenvogelhttps://github.com/svenvogel @swillhttps://github.com/swill @syedhttps://github.com/syed @vladimirpetrovhttps://github.com/vladimirpetrov @weizhouapachehttps://github.com/weizhouapache @widohttps://github.com/wido and so many others! (sorry guys in case I missed any of your handles - you're in thoughts as well)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/apache/cloudstack/pull/4554#issuecomment-748932616, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKRF7KSLNAKZLZSACWE4OD3SV4YR5ANCNFSM4VEDIP2A.
Steve Roles
VP Service Delivery
s: +44 20 3603 0540  |   m: +44<PHONE_NUMBER>  |   d:
e<EMAIL_ADDRESS>|  w: www.shapeblue.com  |  t:  @shapeblue
a: 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error.
Find out more about ShapeBlue and our range of CloudStack related services:
IaaS Cloud Design & Build    |    CSForge - rapid IaaS deployment framework
CloudStack Consulting    |    CloudStack Software Engineering
CloudStack Infrastructure Support    |    CloudStack Bootcamp Training Courses

Happy Christmas & New Year everybody. Its been great collaborating with everybody in this crazy year.
Please merge the 2021 PR as quickly as possible :-)

grinch this :( 👎 unless we want of course rc3 and or 4.15 tinted...

Thanks, @rhtyd, Merry Christmas and happy holidays to all! :)

Merry Christmas and happy holidays to everyone!
On Mon., Dec. 21, 2020, 7:16 a.m. Pearl Dsilva<EMAIL_ADDRESS>wrote:

@Pearl1594 approved this pull request.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/cloudstack/pull/4554#pullrequestreview-556337088,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAANULURGIC7WUO6GPVTCJ3SV44ALANCNFSM4VEDIP2A
.

+1
All the best everyone.

Happy holidays, I'll ACK this once the Travis CI errors have been addressed. :rofl:

+1
Christmas than the other years but I which all you guys very Christmas !!!

Once again - happy Christmas, holidays, and new year! Let's merge this.

I retract my minus grinch ;)


Fails to match certain characters when extending InlineSyntax

Looks like there are a few characters I've found where the regex matcher never seems to trigger onMatch when extending inline syntax. These characters are matched correctly using
Specifically, when trying to match single quotes ' and square brackets [ and ] in strings.
Here's a reduced example of my implementation.
class CustomSyntax extends InlineSyntax {
  CustomSyntax() : super(r"'");
  bool onMatch(InlineParser parser, Match match) {
      // ... never called
  }
}

This regex does match correctly when using the regular RegExp matcher.
void main () {
  var test = "'";
  var match = RegExp(r"'").stringMatch(test);
  print(match); // output: '
}

Hi @nishtahir
Couldn't find InlineSyntax with latest version of the package
Can you please provide your flutter doctor -v, a complete reproducible minimal code sample, and complete flutter run --verbose logs running the minimal code sample?
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


LTO doesn't work with rust nightlies after 2020-04-29

As reported in #7 building the rusty-demo with LTO doesn't work with rust nightlies newer than 2020-04-29. If this doesn't resolve by itself we should investigate what changed and if this requires any changes on our end in order to reenable LTO.
The error that gets printed when linking is the following:
error: failed to get bitcode from object file for LTO (Bitcode section not found in object file)
As a temporary workaround LTO was disabled in the release profile in #14

This is likely related to Don't force rustc to do codegen for LTO builds, which makes cargo more lto-aware to speed up builds. But I am not sure where the problem lies exactly.

This was merged only 3 days ago, so it probably isn't that specific PR (I'm assuming rust nightlies are built from master). However there seem to be a lot of related PRs concerning LTO and changing how it works in the past weeks.

The problem is solved. At least it works on my test system.

It's still broken for me.
Tested on windows with rustc 1.45.0-nightly (ad4bc3323 2020-06-01) and commit c68ef8ed2e72a988d27a286c1cc23f52db1533d6.
Both rusty_demo and netbench fail to compile in release mode with lto enabled with the error: error: failed to get bitcode from object file for LTO (Bitcode section not found in object file)

I fixed it, but we have still an issue by building application with LTO support. The linker encodes the wrong OS ABI. See also rust-lang/rust#73606

Looking at the PR, this only works for thin LTO, right? Commit https://github.com/hermitcore/rusty-hermit/pull/44/commits/66325e69fa026b03b943db6b26f2560187effe7d suggests that using full lto lto = true would still broken, correct?

Yes, but this is also a bug in the Linker Plugin. I am able to link and to run with lto = true,  but the optimization is too aggressive. I was able to see, that the linker assumes that global data is partly constant, which isn't the case. I have to look in the details...

The -C linker-plugin-lto (or somethin simmilar) has to be set. e.g. int the .cargo/config

Hm, can you set -C linker-plugin-lto only for x86_64-unknown-hermit and releaseversion?

I close this issue. The readme describes, how LTO can be activated.


Create LICENSE

This license will not hold us liable for the use of Baileys by anyone. This is likely the root cause why Baileys got targeted, there is no license.

Why AGPL and not GPL?

Why not use the MIT license, which adiwajshing used back then https://github.com/WhiskeySockets/Baileys/blob/add-license-1/LICENSE.md
It also ensures that all contributors can't be held liable


Preserve task domains for tasks inside do_while loop

On every iteration, apply task domains as set in the workflow execution.
This feature was missing and made do wile behave incorrectly when using
task domains (since the domains were reset for tasks inside the loop).
Signed-off-by: Maros Marsalek<EMAIL_ADDRESS>

Hey @apanicker-nflx , this is a small improvement (single line changed) to the do while task, including unit tests.


Get ownership or clone the custom google search engine

Hi @thindil,
I'm taking care of your archived project thindil/adasearch. You can see my update on this page. I appreciate any feedback about it, if you have any.
This issue is mainly for properly taking a fork, not only of the HTML, but also of the custom Google engine. Is this something that can be transferred or exported to be cloned, so it is now under my control?

Hello.
Thank you for taking care of it. If you want, I can transfer the old project to you, so no fork would be needed. 😄
About custom search engine. I'm not sure. I see I can add a new owner to it, perhaps then you will be able to manage it. For this, I will need any of your emails. When this won't work, I will give you all needed information about the search engine configuration.

Hello.
Thank you for taking care of it. If you want, I can transfer the old project to you, so no fork would be needed. 😄

I don't mind it saying it's a fork, it's like a homage to you :smile:, and in any case, that could be removed, as I did for https://github.com/mgrojo/ASFML because the previous author was disappeared. That can be asked to GitHub, but now that I've learned more about Git I guess you can also do it, by just cloning from the original and then creating a new project from scratch and populating it with that cloned repository. I guess the transfer would do the same? Or would it still be under your path? In that case, I prefer to keep it as a fork, which can later be converted into a main repository.

About custom search engine. I'm not sure. I see I can add a new owner to it, perhaps then you will be able to manage it. For this, I will need any of your emails. When this won't work, I will give you all needed information about the search engine configuration.

Let's try then with the new owner. You can use mgrojo at gmail.com.

About fork, no problem here for me. 😄
About ownership: I added the email, you have now to verify your account there. The full address to the settings is: https://programmablesearchengine.google.com/controlpanel/overview?cx=009829025445605706198%3A-dt42nxzgi8
If everything will be good there, I will remove myself from the list of owners (I hope it is possible). If you have any questions, feel free to ask. I hope I remember how to set things there. 😉

About fork, no problem here for me. 😄

I've been reading about the transfer of ownership, and it seems the better way to go, because it will leave a redirection behind, so any link that might there be out there, would redirect to the new location. There's no redirection for the github page, though, so I guess it will simply disappear.
I've renamed this repository so we can try the transfer and leave it in "mgrojo/adasearch".

About ownership: I added the email, you have now to verify your account there. The full address to the settings is: https://programmablesearchengine.google.com/controlpanel/overview?cx=009829025445605706198%3A-dt42nxzgi8

Perfect, thanks. I'm now in.

If everything will be good there, I will remove myself from the list of owners (I hope it is possible). If you have any questions, feel free to ask. I hope I remember how to set things there. 😉

For the moment, the configuration seems straightforward. I have a doubt already, did you try with the included and excluded pages to improve results? It seems as best as it could be, nevertheless, so maybe not useful.

Transferring ownership, I was trying to do it, and I got error:
mgrojo already has a repository in the thindil/adasearch network
My guess, you have to delete this fork if we want to transfer it to you.  That can make following this issue a bit harder, unless you reopen it on the original repo.  I just "unarchived" it for a moment.😉
Including/excluding, no, I didn't play with it. I never felt like I need it. But last time I was setting it a few years ago, before AI bonanza. Today, it can be a good idea to remove some fake pages, if they appear somewhere in results.


added a QUASR-downloader

It would be amazing to have all of the QUASR configurations accessible with just one command.
I implemented a simple interface using the 'requests' library, that downloads any QUASR field.
I tried to make it so that it picks a random configuration, but apparently not all integers between 0 and 300,000 correspond to an entry in the database.
@andrewgiuliani is there a list of which entries exist, so that a robust random picker can be returned?
Or even better, the user could directly query the database for a list of constraints (NFP, A, iota, coil length, etc) and get a random config that fits their needs.
Something like this must be already implemented on the website, one would only have to adapt this to python. I am happy to do this but would need more info on the database itself. Would this be of interest @andrewgiuliani?

Sorry to leave this hanging so long, but I think this would be a great addition, and am wanting to use this as I am looking at more QUASRs with pyoculus, and it would be great to directly grab them from a script.
@jsoules, has the content of the json changed with newer entries to the database? For example https://quasr.flatironinstitute.org/model/1258083 only returns surfaces and coils
@andrewgiuliani, lets divide the work, it should be pretty minimal, hard-code a few numbers into the tests and adapt to the new format of QUASR (no magnetic axis anymore :'( )

@jsoules, has the content of the json changed with newer entries to the database? For example https://quasr.flatironinstitute.org/model/1258083 only returns surfaces and coils

Hi,
Not sure what you mean--I'm looking at that link and I see it populating with surfaces, coils, modB, and currents, as well as populating the Poincare plots. (All those assets are present on the site back-end.)
The data in the individual-record JSON is an extract of the relevant row for the whole-database JSON; this is what populates the "Device Metadata" block on the right-hand side in the web UI.
The set of fields included in the JSON (i.e. the quantities of interest) have changed in different releases, but without knowing the time point you're comparing to, I'm hesitant to give a definitive answer. But any changes would affect all devices, as the same format is used for the entire database.

When we wrote the scripts in June, the database would return a json file containing surfaces, magnetic_axis, coils, which allowed us to mirror the return style of other configurations in the simsopt zoo such as simsopt.configs.get_w7x_data().
This would allow a user to more easily swap out a quasr configuration in an existing script.
Is it also possible for the user to request the entire row from the database? These quantities could be useful in scripts that further deal with this data.

Hi Chris, you're right! I have those json files too, we will swap them out so the axis is returned as well. As for the row of the data frame, that should be doable as well. Let me discuss with Jeff


Store multiple game logs with time stamp

Fixes #777
Stores up to 10 game logs in the log folder with the time stamp

sry maybe nitpicking, but could java.time API be used?
On Sun, 30 Aug 2020, 14:14 Sheikah45<EMAIL_ADDRESS>wrote:

@Sheikah45 commented on this pull request.
In src/main/java/com/faforever/client/preferences/PreferencesService.java
https://github.com/FAForever/downlords-faf-client/pull/1870#discussion_r479762402
:

@@ -346,6 +355,22 @@ public Path getThemesDirectory() {
return getFafDataDirectory().resolve("themes");
}

public Path getNewGameLogFile() {
try (Stream listOfLogFiles = Files.list(getFafLogDirectory())) {

 listOfLogFiles

     .filter(p -> GAME_LOG_PATTERN.matcher(p.getFileName().toString()).matches())

     .sorted(Comparator.comparingLong(p -> p.toFile().lastModified()))

     .sorted(Collections.reverseOrder())

     .skip(NUMBER_GAME_LOGS_STORED - 1)

     .forEach(p -> noCatch(() -> Files.delete(p)));

} catch (IOException e) {

 logger.error("Could not list log directory.", e);

} catch (NoCatchException e) {

 logger.error("Could not delete game log file");

}
return getFafLogDirectory().resolve(new SimpleDateFormat("'game_'yyyy-MM-dd_HHmmss'.log'").format(new Date()));

Yeah personally I think the time might be more intuitive for the user than
game uid and I can add a dash separator for the time
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/FAForever/downlords-faf-client/pull/1870#discussion_r479762402,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBYJJOJTIOCIW2Z5YMJIL3SDI7A7ANCNFSM4QO766RQ
.


@simplewebauthn/browser doesn't respect excludeCredentials

I'm pretty new to WebAuthn, so I may have got this wrong but to my understanding, by providing the populated excludeCredentials object, the client would not issue a new credential if one already exists on the same authenticator. My application returns a registration options object which contains excludeCredentials:
// ...
"excludeCredentials": [
        {
            "type": "public-key",
            "id": "rMyK_5Nroqc25QB4piUgIRKG4v4"
        }
    ],
// ...

however, startRegistration() still produces another credential. When storing the credential in my database, I base64url.encode its ID and then return that string when producing registrationOptions.
Am I doing something wrong, or could this be an issue with the library— any help would be appreciated 😅

Which authenticator are you working with? If you can, can you set a breakpoint on your front end code and make sure the credentials are present when SimpleWebAuthn calls navigator.credentials.create()? startRegistration() doesn't omit excludeCredentials for any reason so I'm thinking this is going to be an authenticator quirk you're up against.

I'll be honest, I'm not sure on which script to set a breakpoint— I've had a look around devtools/sources/scripts, but can't find much. I'm using TouchID on macOS in Safari. I've just tried with Safari on iOS but that doesn't even seem to bring up the prompt.

I'm using TouchID on macOS in Safari.

I just tested this out myself and Safari seems to simply ignore entries in excludeCredentials; I was able to successfully register Touch ID twice in a row despite the first registration's credential ID appearing in excludeCredentials in the second registration.
Your code is probably fine. In this case it's just a reality of WebAuthn: there are many active players to be mindful of, including authenticator and browser vendors, and "quirks" like this are things to be aware of as you decide to move forward with this technology 😅

@chrisyalamov I'm going to close out this issue. If in the future you believe this is still legitimate then please feel free to reopen with code samples demonstrating the issue.

Please see this thread on the apple developer forums


[Feature Request] Rename Properties Auto Rewriter

This issue is a "fix suggestion" for #891
How I describe in issue #891 I have bug with exported/imported data/modules (objects/classes etc) what have any props (keys) .
My suggestion is something like:
Original code
const object = require("class.js") // return class with {active: true} prop.
object.active // true

Obfuscated code
const object = require("class.js") // return class with {active: true} prop.
// This, how I write, should execute in runtime, maybe we can run this in handlerFunction or on pre/post obfuscation start?
for (const key of object) {
 const value = object[key];
 object.0xfff = value; // set new keyname for value
 delete object[key];   // delete old key
}
object.0xfff // true

Actualy, this is only prototype. I think we can fail with private properties, methods and etc.

https://github.com/javascript-obfuscator/javascript-obfuscator/issues/629


Cannot set field if class doesn't contain same fields

Describe the bug
When setting a field sometimes it fails.
It seems that if the class generated that will be replaced contains fields that the other class doesn't contain it fails.
Your environment
Java 17 - FixtureMonkey - 0.4.9
Steps to reproduce
Run abstractTest() multiple times until it fails
https://github.com/esfomeado/fixture-monkey-bug/blob/master/src/test/java/com/example/bug/FixtureMonkeyTest.java
Expected behaviour
Should work all the times and set the field correctly.
Actual behaviour
The field is not set sometimes.
Can not set java.lang.String field com.example.bug.Peter.age to com.example.bug.John
java.lang.IllegalArgumentException: Can not set java.lang.String field com.example.bug.Peter.age to com.example.bug.John
	at java.base/jdk.internal.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:167)
	at java.base/jdk.internal.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:171)
	at java.base/jdk.internal.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:58)
	at java.base/jdk.internal.reflect.UnsafeObjectFieldAccessorImpl.get(UnsafeObjectFieldAccessorImpl.java:36)

@esfomeado
It is fixed since 0.4.10.
Thank you for your help!!


Add the build configuration

Review this

 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.:x: JohandeVries86 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


attack against user session with omniauth.origin

Please complete all sections.
Configuration

Provider Gem: omniauth-auth0
Ruby Version: 2.4.2
Framework: rails-5.1.4
Platform: OS X, Linux

Expected Behavior
Omniauth shouldn't allow untrusted parties to populate the user session with arbitrary data by blindly trusting the contents of the origin query parameter in a GET to /auth/<provider>.
Actual Behavior
Omniauth puts the contents of the origin query parameter into the user's session.
If the application is using cookies for session storage, it is trivially easy to overflow a user's session cookie by redirecting them to /auth/<provider>?origin=<string longer than 4k>. (Or, use a value that gets the session cookie close to, but not over, the 4k limit, so that auth succeeds, but any attempt to put anything into the user's session after that causes it to overflow.)
If the application is using different session storage, it opens a possible DOS attack against the storage layer.
Steps to Reproduce
Navigate to /auth/<provider>?origin=<long string>.
--
Maybe I've missed some important aspect of how this feature works, but it seems to me that saving the user's location is much easier to do securely in the application layer, rather than the middleware layer.

Unless there's something that I'm missing, this check is typically handled through Rack::Session::Cookie or, in your case, ActionDispatch::Cookies::CookieJar.
Rack::Session::Cookie:

https://github.com/rack/rack/blob/master/lib/rack/session/cookie.rb#L156-L170

ActionDispatch::Cookies::CookieJar

https://github.com/rails/rails/blob/1fa268bfa5667a0e9ddbfda243b5282c023ab9ad/actionpack/lib/action_dispatch/middleware/cookies.rb#L589-L593
https://github.com/rails/rails/blob/1fa268bfa5667a0e9ddbfda243b5282c023ab9ad/actionpack/lib/action_dispatch/middleware/cookies.rb#L632-L636

@tmilewski I'm not quite sure what you mean. If you're saying that the Cookie(Jar) code notices that the cookie is > 4k and raises an exception, then yes, it does. What I'm saying is that OmniAuth makes it easy for other parties (other than the application itself, I mean) to cause this exception by sending the user to /auth/<provider>?origin=<large string>.
This, by itself, is not a huge deal; it's just annoying. But:
Let's say you're using the ActiveRecord session store, and someone repeatedly initiates a new session and goes to /auth/<provider>?origin=<large string> and never completes authentication (so the callback phase is never run, and the session data is never removed). It seems like it would be easy to eat up a massive amount of database storage in a short time.
Also, the purpose of origin (I think, based on Saving User Location) is to be able to redirect the user to the page they had originally requested upon successful authentication. Of, you don't want to do this blindly; if someone sends your user to /auth/<provider>?origin=<fake bank site>, you don't want to redirect the user there upon successful authentication. And it's much easier to ensure that the redirect URL is a safe one if the only party that can put the redirect URL in the session is your application (assuming that your session is tamper-proof, of course).
So OmniAuth actually makes it more difficult to (safely) save the user's location than it would be if it did not store omniauth.origin. OmniAuth basically gives you these choices:
- inspect omniauth.origin in the callback and redirect if you determine it's safe; or
- put your own return URL in the session, under a different key, and ignore omniauth.origin altogether, in which case you already know it's safe, because you chose it (again, assuming your session is tamper-proof).
But if you choose the second option and you're using a cookie store for your sessions, you need to worry about the fact that you're now trying to put two, potentially large URLs in the session, even though you only care about one of them. In which case you could add a setup phase proc that does something like this:
      setup: -> (env) {
        request = Rack::Request.new(env)
        request.update_param("origin", "X")
      }

Because if you put the empty string in origin, then OmniAuth will put the HTTP_REFERER in the session, so your best bet (as far as I can tell) is to put the shortest, non-falsey value you can there.
This isn't just a theoretical scenario. We experienced a cookie overflow for precisely this reason. At the time, we didn't know that OmniAuth was already storing the HTTP_REFERER value, and we thought, at first, that it would be a good idea to use the omniauth.origin mechanism to store the return URL. But it appears to be considerably more work to use omniauth.origin safely than it is to work around it.
That said, it's entirely possible that I'm missing something important here, and that there's a very simple way to use omniauth.origin safely.

@97jaz Let me know what you think per #912, specifically https://github.com/omniauth/omniauth/pull/912/commits/867165ab231355ebce10f003b2a15f6b2a0b783f

@tmilewski Yes, that's much more convenient -- thank you!
(I'd argue that the default behavior should be that there is no origin param, but I understand that that wouldn't be backwards-compatible.)

@97jaz I agree with you that the default shouldn't include origin. I'd prefer to make this backward compatible move and talk through changing defaults with everyone later.

Pushed as 1.7.0: https://rubygems.org/gems/omniauth/versions/1.7.0
Thanks!

Thank you, @tmilewski!


Persist user sessions over multiple binder links for the same repo

(I may have posted this before so feel free to link+close if it's already an issue, but I couldn't find it)
Right now, if somebody clicks two binder links in succession, then two different binder pods will be created for them. As more resources like https://www.inferentialthinking.com/ and the sphinx-gallery plugin start popping up, this is going to result in a lot of inefficient use of pods.
We should make BinderHub behave kind of like jupyterhub on the short-term. If someone clicks a bunch of links that point to the same repository, it should find a pre-existing pod linked to their IP (maybe with a cookie?) and just direct them there, rather than rebuilding a pod.
I feel like this may be blocked until #323 is merged? Curious what people think
User behavior

A user clicks a binder link
User clicks another link relatively quickly (within 10 minutes)
A. link that points to same repository, different path
B. link that points to different repository

What happens now
A. A new Binder pod is created, local token updated, user directed there
B. A new Binder pod is created, local token updated, user directed there
What we would like to happen
A. BinderHub detects this is the same repository as a pre-existing user pod, redirects the user to a new path on that pod, does not create a new pod.
B. A new Binder pod is created, local token updated, user directed there

Unpicking scenarios a bit more, I can think of several:

S/one clicks a link on Github repo and then clicks on it again; this might mean they didn't finish the session or it might mean they want a clean session; eg in first case, they maybe tried one notebook in the repo, then realise they want to try another and might sensibly return to the first session; eg in second case, someone doing demos to different people might want a clean start each time. I could imagine a flag in button link URL specifying which behaviour is desired, perhaps with the default of reusing an already running pod associated with that browser cookie/repo if possible.
Sphinx docs - people trying multiple examples: someone clicks a link from one page, then clicks another link from another example in the same page or a different page; the same session may or may not suffice depending on assumptions made in the example statement about prior state. Which is to say, it's not clear if multiple examples in same page are stateless or not. eg two examples may be independent or first example may be dependent on previous example having been run; (there is a complementary issue in some sphinx docs eg where a preamble %matplotlib cell needs to be run to display graphical output but a novice user might only try to run the example cell (%matplotlib inline should be  autorunnable dependent cell?)
Thebelab style interaction, eg embedded runnable examples in Sphinx generated docs: in this case, there may be multiple examples in one page, or examples spread across several pages; again, in case of multiple-examples in one page, the desired behaviour might be stateful or stateless based on prior cell execution. It may also be the case in long running examples in documentation spread over several HTML pages that an example on one page may be dependent on the prior running of an example on a previous page; cf. the SageMath cell server, which can be used to embed a runnable cell in a VLE/LMS, (example: Moodle plugin for SageMath cell server) which is a stateless, single cell execution service.

I think 3. is taken care of by the various JS extensions that exist:

https://spacy.io/usage/spacy-101#annotations (based on https://github.com/ines/juniper)
http://play.nteract.io/ via nteract components, can't find the link right now
thebelab

Sharing or not of a binder instance is something that can be configured in each of these. I think as binderhub operator we should not try and force someone using them into a particular behaviour.
For 1. and 2. I think we can try and reuse an existing binder instance for the same user. My guess would be that for most uses that want a "clean slate" all they need is to start a new kernel. Then those who really want a clean clean slate we should offer an obvious button to shutdown the existing binder instance. It will add a few extra clicks for the demo use case you describe but would help save a lot of resources for the (I think) more frequent use case where a user visits several binder links in short succession.

(I may have posted this before so feel free to link+close if it's already an issue, but I couldn't find it)

It was this one :smile: https://github.com/jupyterhub/binderhub/issues/327
I'll keep this one open instead since it's got more discussion.


Footer Responsiveness Issue

Describe the bug
The footer section of the website is not responsive and does not align properly across different screen layouts and device sizes. On smaller screen sizes, particularly smartphones, the social media icons move out of the screen, causing a poor user experience.
To Reproduce
Steps to reproduce the behavior:

Open the website.
Resize the browser window to different sizes or view it on various devices.
Scroll down to the footer section.
Observe the misalignment and social media icons moving out of the screen on smaller screen sizes.

Expected behavior
The footer section should be responsive and adapt seamlessly to different screen sizes and device layouts. The content, including the social media icons, should remain within the visible area and align properly without any overlapping or overflowing elements.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser Chrome, Edge

Smartphone (please complete the following information):

Device: Realme GT 6T
OS: Android 12
Browser:  Chrome

Additional context
The issue appears to be related to the responsive CSS styling of the footer section, which is not adequately handling different screen sizes and device layouts. This can negatively impact the user experience, especially on mobile devices, where the social media icons become inaccessible or partially visible.

@Priyaaa1 Please assign this issue to me and also add the gssoc and appropriate level label to this issue. I would love to contribute.


Let debugged Go tests find their runfiles

Checklist

[x] I have filed an issue about this change and discussed potential changes with the maintainers.
[ ] I have received the approval from the maintainers to make this change.
[x] This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.
Discussion thread for this change
Issue number: #2313
Description of this change
Go runfiles discovery requires at least one of the runfiles variables
RUNFILES_DIR or RUNFILES_MANIFEST to be set. With the script path
experiment, which is enabled by default, only TEST_SRCDIR is currently
extracted from the script and passed to the test binary. As a result,
runfiles discovery fails on Windows (where a manifest is required) as
well as when following the official runfiles discovery process, which
does not include TEST_SRCDIR.
This is fixed by including all RUNFILES_* variables in the environment
used to start the test binary.

Looks like this issue got fixed in another PR?
https://github.com/bazelbuild/rules_go/pull/3029
@fmeum Can you confirm?

Looks like this issue got fixed in another PR?
https://github.com/bazelbuild/rules_go/pull/3029
@fmeum Can you confirm?

No, this PR resolves a different issue: Tests run with debug symbols thanks to https://github.com/bazelbuild/rules_go/pull/3029, but they will still fail to find their runfiles. The latter is fixed by setting the runfiles environment variables.

@vsiva @alice-ks Friendly ping. This PR should be quick to review and is quite important for rules_go users.

Overall, this change looks good. I'll start the import of it.
Please note that without a test, this functionality might easily break in the future again. Hence, consider to add tests with future PRs.


Point README Slack badge URL to #redux channel

The problem is that the new users will see a login page with "you need an invite from administrator".

Closing for the reason above.

Ah, I see. Sorry for the confusion!


Source distribution is not provided

For some reason, we need to install all python packages from source distribution (pip install with option --no-binary)
It doesn't work for ecmwflibs because you only provide wheels.
Is it in your roadmap to also provide source distribution ?

If you don't want to change it in your repository, maybe it's something you could change "on the fly" in the GitHub Action used to publish the package. That's what we are doing for some of our packages, see for example the workflow for mflog

It is not currently possible to create a source distribution that is compiled on the user's computer, as there are too many external dependencies required. But contributions are welcome. I will close the PR for now.


Design Plan Alert Mail Template at Sendgrid

We will start using SendGrid for templating our emails,
Need to have a template for the following case:

[ ] Weekly plan digest. Recieves  a list of new plans, including the following fields:

plan name,
plan description,
plan location,
plan status

Resolved


I receive notification in android only when app is killed or in the background

Hi
When the app is open and running, I do not receive notifications, only if I close or kill the app.
Any idea why?
Thanks
rubenc

How are you sending the payload?

I'm testing with notifications in firebase website:
https://console.firebase.google.com/

Never mind, I understand better how it works, excellent job by the way
When the app is running i need to handle the UI, now I'm receiving them
Thanks


Rework Frequency section

Redesign the frequency section for event creation/editing.
Test functionality on mobile devices.

So far just did some renaming, and added an example.


Can't find remove_lower_dimensional_cells in recent versions of meshio

Hi @nschloe
I have inherited some code that calls remove_lower_dimensional_cells pretty much every time it loads a mesh.
Looks like that method is not on the mesh class anymore. I can't find when the change happened though.
I only had a quick look through the code but it is still needed?
R

Yeah, I took all mesh-manipulating routines out of meshio a while ago. Will publish a separate package with that soon.


[Bug]: Regex validation for env variables in spawner page.

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When adding an environment variable with only digits in the name, the build status freezes, and the notebook controller outputs this error:
1.663845121362662e+09 DEBUG events Warning {"object": {"kind":"Notebook","namespace":"opendatahub","name":"jupyter-nb-lferrnan","uid":"49ea52f2-fabd-457c-94bd-988549fe3817","apiVersion":"kubeflow.org/v1beta1","resourceVersion":"618045"}, "reason": "FailedCreate", "message": "Reissued from statefulset/jupyter-nb-lferrnan: create Pod jupyter-nb-lferrnan-0 in StatefulSet jupyter-nb-lferrnan failed error: Pod \"jupyter-nb-lferrnan-0\" is invalid: spec.containers[0].env[2].name: Invalid value: \"1341\": a valid environment variable name must consist of alphabetic characters, digits, '_', '-', or '.', and must not start with a digit (e.g. 'my.env-name', or 'MY_ENV.NAME', or 'MyEnvName1', regex used for validation is '[-._a-zA-Z][-._a-zA-Z0-9]*')"}
We should have validation in the frontend to comply with this value.
Expected Behavior
When writing an env variable that starts with a number, have form validation.
Steps To Reproduce

Go to the spawner page
Create a new env variable
Fill it with digits, i.e. 1234
Start the notebook, it will freeze and it won't output any error.

Workaround (if any)
Not using env variables that start with digits.
OpenShift Infrastructure Version
No response
Openshift Version
No response
What browsers are you seeing the problem on?
No response
Open Data Hub Version
No response
Relevant log output
No response

Ah yeah, field validations are lacking in our space -- good issue to log, not sure if QE has a test case for this in their automation -- I'll reach out and let them know.


Deduplicate fuzzy finder keybindings

This will require a docs update, but opening for discussion as this came up in chat with @bolinfest.
Good keybindings are precious and rare, and we don't have to hew perfectly to sublime for new users. I understand that users can rebind commands as necessary, but as most users will likely stick to the defaults, I think we should pick one binding for the fuzzy finder and stick with it. I personally remapped cmd-p to the command palette literally the first day I started using Atom so I prefer to keep cmd-t but I know that's totally subjective and could be argued into doing this the other way.
cc: @bolinfest , @atom/core

I am extremely biased here, but I came to Atom directly from Sublime, so I favor the cmd-p shortcut (although I came to Sublime from TextMate, so I was used to cmd-t before... shrugs).

One other data point is that the GitHub website uses the t shortcut to go to the file picker. Consistency with other GitHub products should count for something too.

Ping? Let's move this forward one way or the other to free up a keybinding!

I'm honestly reluctant to remove either binding, but cmd-t should probably be the one to die if we really need to do it.

:+1: :100:
The ctrl- and cmd- keybindings are a precious resource. Having two for the same package is :panda_face:.
However I agree that we'd need to remove cmd-t / ctrl-t

We have ctrl-shift-p for the command panel
We could have ctrl-alt-p for a project switcher (the spec runner doesn't need a keyboard shortcut as the average user doesn't care)
It mimics sublime in a very obvious way


windows builld

make it work ond windows fully

this stuff is pretty much all sorted, there was some real nightmares in there like the fact windows doesn't signal processes with pipes


Add per call options to ygnmi

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

85 of 89 (95.51%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 88.51%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ygnmi/gnmi.go
54
58
93.1%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
1533

Relevant Lines:
1732

💛  - Coveralls

fixes in https://github.com/openconfig/ygnmi/pull/58


[Request] Anti OBS/Anti Screenshots?

an anti obs/screenshots for esps would be nice.

anti screenshot i could do but i wont, anti obs i dont think so


Exception when try create a Postgres connection

Describe the bug
When I try to create a Postgres connection, is happing an exception.
To Reproduce
Steps to reproduce the behavior:

Go to 'Data'
Click on 'Add Data Source...'
Click on 'New connection...'
Select the Postgres connection  option
Click on 'Test connection'
See error

Expected behavior
To connect on database
Stacktrace
Could not load file or assembly 'System.Threading.Tasks.Extensions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Screenshots

Device (please complete the following information):

OS: Wiin 11

I have the same problem

Hello!
Reproduced your issue, created a task and passed it to the development department, expect a fix in the next version of FastReport Community Edition
Best regards,
Bogdan

I have the same problem too.

@RieMomo Im using this as paliative
https://github.com/rftd/FastReport.Design.Avalonia
Its a custom designer with plugin manager, using the demo version of FastReport.Avalonia.

Hello!
The problem has been solved in the new version

Hello!
Reproduced this issue, passed your feedback to the development department, expect changes in the next versions of FastReport Community Edition
Best regards,
Bogdan


Add flags to PowerShell 4 install for no UI and no restart

Hello @zl4bv , we have removed /norestart as we need to reboot PC after powershell installation. However /quiet was removed by mistake, which will be added soon once PR https://github.com/chef-windows/powershell/pull/32 gets merged

Hi @NimishaS , so if we rely on Windows Update Standalone Installer to perform its own reboot does that mean it is no longer necessary to include the reboot handler on line 40?
include_recipe 'powershell::windows_reboot' if node['powershell']['installation_reboot_mode'] == 'immediate_reboot' && powershell_version < 4

@zl4bv , we are not relying on Windows Update Standalone Installer to perform reboot. What I experienced was that Windows Update Standalone Installer didn't prompt for reboot also because of /quiet.
Reboot happens because of line #40 only. i.e.
include_recipe 'powershell::windows_reboot' if node['powershell']['installation_reboot_mode'] == 'immediate_reboot' && powershell_version < 4

@zl4bv , Reboot fixes have been merged in the master branch. You can use it now.
We can close this PR if your requirements are fulfilled.

Thanks for your help @NimishaS - yes my requirements are fulfilled.


Invoke Terraform Workflow on push to Cryptolake

When there is a push to the cryptolake branch, the nessie workflow invokes the deploy-lakefs-on-ecs.yaml workflow in the terraform repository, which creates/updates a long lived lakeFS environment for Cryptolake using the image generated in the nessie workflow. The name of the environment is cryptolake-prod and it can be accessed from https://cryptolake-prod.lakefs.dev/
This workflow is run here within nessie so the deployed image is certain to have passed all the tests before being deployed.
When the deployed version of lakeFS should be upgraded is still an open question. It can be updated on release, on a schedule, or manually by pushing to this branch.

@arielshaqed I wanted some way to ensure that the version of lakeFS merged to the cryptolake branch and deployed was a valid version that passed all the system tests. The way I decided on was to make the deployment dependent on if the system tests were passed. Is there a better way of ensuring the validity of a lakeFS version?

@arielshaqed I wanted some way to ensure that the version of lakeFS merged to the cryptolake branch and deployed was a valid version that passed all the system tests. The way I decided on was to make the deployment dependent on if the system tests were passed. Is there a better way of ensuring the validity of a lakeFS version?

OK, I see! The usual tool that CI /CD systems provide for something like this is the confusingly named "dependency". It's called that because it is named for some old concept in Makefile, regardless of the way it's been used for the past 20 years.
Consider a separate workflow that depends on Nessie succeeding. https://docs.github.com/en/actions/reference/events-that-trigger-workflows#workflow_run might be your friend here.

@arielshaqed I wanted some way to ensure that the version of lakeFS merged to the cryptolake branch and deployed was a valid version that passed all the system tests. The way I decided on was to make the deployment dependent on if the system tests were passed. Is there a better way of ensuring the validity of a lakeFS version?

OK, I see! The usual tool that CI /CD systems provide for something like this is the confusingly named "dependency". It's called that because it is named for some old concept in Makefile, regardless of the way it's been used for the past 20 years.
Consider a separate workflow that depends on Nessie succeeding. https://docs.github.com/en/actions/reference/events-that-trigger-workflows#workflow_run might be your friend here.

@arielshaqed I took a look at the event trigger! If I used this method, I would have to find some way of sending the sha-tag of the docker image built in nessie to this new workflow within lakeFS, or build a second image from within that workflow, and run this curl command using that sha-tag.
This event trigger doesn't support passing in inputs (possibly because this is triggering on the completion of an outside workflow and it's probably not the best idea to make the internals of the nessie workflow open to external workflows). I can do this by using the same curl method used here to pass the sha-tag to a new workflow within the lakeFS repo using a workflow_dispatch trigger, which would then just run the same curl command to run the workflow in Terraform repo – that seems redundant!
One way I could do it using the workflow_run trigger is by saving the sha as an artifact and retrieving it in a different workflow, and then using the curl command (which can be done using this user made action but is not supported by any github provided action: https://github.com/dawidd6/action-download-artifact)
Another way using this trigger would be to build the image again, push it to ECR, and then send that tag all from within a new workflow, which seems a little wasteful.
I think the way it is currently makes sense, but I do see the benefits of separation. I'm not sure about the impacts of either of these trade-offs, though intuition tells me I should be careful of the user action breaking, and that the added cost of building the image again is not very large.

Aha, talking with Itai made me understand that the sha-tag can be obtained by running git rev-parse --short HEAD and doesn't need to be passed as an input, so this separation using a workflow_run trigger is possible! I'll try this out

Cool, this looks like a really neat and useful automation! I like how it's gitops (or maybe GitHubops) from the user perspective: I trigger a deploy by merging to cryptolake and do nothing else. So as I user when I asked myself "but how do I roll back a deploy?", I realized git branch cryptolake; git revert; git push origin is a nice answer!
One last request (_NOT on this PR..._): @itaiad200 do you think it would make sense to add a badge to our README about what version was deployed to our cryptolake, and whether that deployment succeeded?

There's a small problem at the moment with the roll back functionality, being the migration of the postgres database. At the moment since I am getting the image using the sha-tag, there's not a way of knowing whether a migrate up or migrate down is needed, so if you're migrating down, you need to do that manually. I can check to see if it's possible!

One last request (_NOT on this PR..._): @itaiad200 do you think it would make sense to add a badge to our README about what version was deployed to our cryptolake, and whether that deployment succeeded?

Agree that a badge is a nice add-on. But not part of this PR though ;)


Add ItemMatch + ItemNoMatch Descriptors

Implement ItemMatch, ItemNoMatch, descriptor + feature and associated unit tests.
Resolves issue #1311
Resolves issue #1310

Hi @jon-bown ,
Thanks for the contribution! It looks great, and I believe might need a small adjustment.
I ran an example based on your pytest for ItemMatch descriptor and it failed with TypeError, could you please take a look?
Here is an example:
import pandas as pd
from evidently.report import Report
from evidently.metric_preset import TextEvals
from evidently.descriptors import ItemMatch, ItemNoMatch

data = {
        "generated": [
            "You should consider purchasing Nike or Adidas shoes.",
            "I eat apples, grapes, and oranges",
            "grapes, oranges, apples.",
            "Oranges are more sour than grapes.",
            "This test doesn't have the words.",
        ],
        "forbidden": [
            ["nike", "adidas", "puma"],
            ["grapes", "apples", "oranges"],
            ["Apples", "Oranges", "Grapes"],
            ["orange", "sweet", "grape"],
            ["none", "of", "these"],
        ],
    }

df = pd.DataFrame(data)

report = Report(metrics=[
    TextEvals(column_name="generated", descriptors=[
        ItemMatch(with_column="forbidden", case_sensitive=False)
            ]
        )
])

report.run(reference_data=None, current_data=df)
report

Hi @jon-bown , Thanks for the contribution! It looks great, and I believe might need a small adjustment.
I ran an example based on your pytest for ItemMatch descriptor and it failed with TypeError, could you please take a look?
Here is an example:
import pandas as pd
from evidently.report import Report
from evidently.metric_preset import TextEvals
from evidently.descriptors import ItemMatch, ItemNoMatch

data = {
        "generated": [
            "You should consider purchasing Nike or Adidas shoes.",
            "I eat apples, grapes, and oranges",
            "grapes, oranges, apples.",
            "Oranges are more sour than grapes.",
            "This test doesn't have the words.",
        ],
        "forbidden": [
            ["nike", "adidas", "puma"],
            ["grapes", "apples", "oranges"],
            ["Apples", "Oranges", "Grapes"],
            ["orange", "sweet", "grape"],
            ["none", "of", "these"],
        ],
    }

df = pd.DataFrame(data)

report = Report(metrics=[
    TextEvals(column_name="generated", descriptors=[
        ItemMatch(with_column="forbidden", case_sensitive=False)
            ]
        )
])

report.run(reference_data=None, current_data=df)
report

Hi @emeli-dral, this actually came up in the unit tests as well. I solved it this way before attempting the feature calculation:
df["forbidden"].apply(tuple)
I'm now thinking this should be handled inside the generate_feature function, thoughts?

Hi @jon-bown , Thanks for the contribution! It looks great, and I believe might need a small adjustment.
I ran an example based on your pytest for ItemMatch descriptor and it failed with TypeError, could you please take a look?
Here is an example:
import pandas as pd
from evidently.report import Report
from evidently.metric_preset import TextEvals
from evidently.descriptors import ItemMatch, ItemNoMatch

data = {
        "generated": [
            "You should consider purchasing Nike or Adidas shoes.",
            "I eat apples, grapes, and oranges",
            "grapes, oranges, apples.",
            "Oranges are more sour than grapes.",
            "This test doesn't have the words.",
        ],
        "forbidden": [
            ["nike", "adidas", "puma"],
            ["grapes", "apples", "oranges"],
            ["Apples", "Oranges", "Grapes"],
            ["orange", "sweet", "grape"],
            ["none", "of", "these"],
        ],
    }

df = pd.DataFrame(data)

report = Report(metrics=[
    TextEvals(column_name="generated", descriptors=[
        ItemMatch(with_column="forbidden", case_sensitive=False)
            ]
        )
])

report.run(reference_data=None, current_data=df)
report

Hi @emeli-dral, I was also seeing this in my unit tests but didn't realize it was related to the data definition not handling list types in the input data. I've added some type handling to the data_processing.py file, let me know what you think?

First of all, I apologise for the delay.
You’ve correctly identified the issue: the improper handling of the list type in the current implementation. After reviewing this, we’ve decided that full support for the list type in the data definition will be handled separately, so there’s no need for you to implement that in this PR.
To resolve this, I suggest the following changes:
1/ Change from List to Tuple:
Please modify the items from being a list to a tuple. Since tuple is immutable, this will help ensure stability when dealing with feature data types.
2/ Revert Changes in data_preprocessing.py:
Revert any changes made to data_preprocessing.py related to list handling, as they will no longer be necessary after switching to tuples.
Thus we will expect users to explicitly create an item as a tuple rather than a list, which is a reasonable requirement. I'll make sure that this expectation is clearly documented for users.
Many thanks for your work on this!

First of all, I apologise for the delay. You’ve correctly identified the issue: the improper handling of the list type in the current implementation. After reviewing this, we’ve decided that full support for the list type in the data definition will be handled separately, so there’s no need for you to implement that in this PR.
To resolve this, I suggest the following changes:
1/ Change from List to Tuple: Please modify the items from being a list to a tuple. Since tuple is immutable, this will help ensure stability when dealing with feature data types.
2/ Revert Changes in data_preprocessing.py: Revert any changes made to data_preprocessing.py related to list handling, as they will no longer be necessary after switching to tuples.
Thus we will expect users to explicitly create an item as a tuple rather than a list, which is a reasonable requirement. I'll make sure that this expectation is clearly documented for users.
Many thanks for your work on this!

I've reverted the data_preprocessing.py file. As far as the changing from list to tuple, do you want me to modify anything in my feature implementation for this? The error previously was being thrown before the feature was called, so even if I did modify something that error would still be thrown unless they do what I'm doing in the unit tests.

Hi @jon-bown,
I took a look at the error, and luckily it’s a very minor issue!
The error occurs during the generation of the display_name in the following section of the code:
def _as_column(self) -> ColumnName:
    160     return self._create_column(
    161         self._feature_column_name(),
--> 162         default_display_name=f"Text Contains of {self.mode} [{', '.join(self.items)}] for {self.column_name}",
    163     )

To resolve this, I recommend simplifying the default_display_name to something like "Text contains defined items"  and "Text does not contain defined items".
Additionally, I think the same fix could work for the other issue. How about using "Text contains defined words" and "Text does not contain defined words"?
Once these changes are made, we should be good to merge your PRs. Feel free to also add the new descriptors to the list of descriptors under the Text Evals heading on the documentation page.
Thanks again for your contributions!

Hi @emeli-dral
Thanks for catching that, I've updated the default_display_name in the _as_column function. Is there anything you think I should change for the _feature_column_name function? I went off of the other two features for the style, but let me know if what I have is ok!

Hi @jon-bown,
Thanks a ton for all your hard work on this PR! You've done an awesome job, and your efforts have really paid off. I appreciate the attention to detail and how smoothly you handled everything.
Excited to merge this in!

Thanks for the contribution @jon-bown ! 🚀


rpc: decide on versioning

We need to make a decision on how we want to version our RPC. In the future we could provide multiple versions at multiple endpoints. At the very least, it will be a failsafe for someone accidentally trying to use an old version of our api
We can then provide the first RPC at /v1 for example
Also: return it as part of node.Info

We can add standard versioning to the gateway starting at v1 but for json rpc, I propose just versioning it via an endpoint that can be provided on the NodeModule since that's where all admin-related info lives. In Lotus, they just have an endpoint on the common API that returns the version as an encoded uint32. I feel like it's overkill and we can just return a string :)

Alternatively, we could explore something related to the discussion here. But IMO this is a later consideration and something we should think about from a devX perspective (probably loop in @YazzyYaz)

As another alternative, we could think about versioning the namespaces under which our modules are registered, but I think that's hairy.

As another alternative, we could think about versioning the namespaces under which our modules are registered, but I think that's hairy.

This is the correct approach IMO. Wouldn't say it's hairy but it adds some overhead for sure.

🤷🏻


Relational layer version 2

Fixes for the config.relational feature.
Remaining:

[ ] Verify implementation
[ ] Run comparison on G, D

Too many open questions on this right now.


Cannot log trace id

We are using the OpenTelemetry tracer, which auto injects Traceparent and Tracestate headers which is awesome. However, we also want Envoy to log the trace id.
Today, our logs use %REQ(X-REQUEST-ID)% as the trace id, but this is not helpful because request id and trace id seem to be distinct concepts in Envoy.
I tried adding a Lua script that could do this for us, but it seems that the Traceparent header is not yet available.
Logging %REQ(TRACEPARENT)% works but is not desirable because we don't need the other data in our logs.
Any thoughts on how else we could accomplish getting the trace id into our logs?
P.S: https://github.com/envoyproxy/envoy/issues/30052 would also potentially work for us

Adding various tracer owners for comment: @mattklein123 @wbpcode @alexanderellis @basvanbeek

trace-id is the substring of traceparent.
you can use %REQ(X?Y):Z% notation, where Z means max number of chars.
so %REQ(TRACEPARENT):35% will give you string with 00-<trace-id> value.
unfortunately, there is no parameter to omit first 3 chars - should be something like ):3:32%


Read table entries from a particular role only

Right now, reads return all table entries. It's very common that a controller only wants to read the table entries associated with its own role. So it would be great if the Read request could filter all table entries that don't match the specified role.
message ReadRequest {
uint64 device_id = 1;
// if specified, only table entries programmed by this role will be returned.
string role_name = 3;
repeated Entity entities = 2;
}

@konne88 Did you mean to assign this to me?  I suppose I can look into what P4Runtime API spec changes would be required here and try to write them up.  Just didn't expect it :-)

Sorry, wasn't so much meant as you need to review this, but more as a "this is what's going on, just in case you want to know".

FYI, you can ping someone in a Github comment by putting an @ before their Github user id, too.

@antoninbas @stefanheule
What do you think about this idea? If this seems reasonable, I'm happy to send out the PR to change the spec.

I fully support this, reading entries not for your own role is pretty annoying and does not seem like it would ever be beneficial.


Auto update model

Make model auto update every x months

every 3 months

added as part of https://github.com/suchak1/hyperdrive/pull/221
Check back in a few months.


⚠ Bofrost.be has degraded performance

In 1e129e2, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2103 ms

Resolved: Bofrost.be performance has improved in 249d5b1.


Unsupported Positional Parameters

Hey guys,
I'm getting the following error when trying to query something with positional parameters:
error: unsuppoted positional parameter. This driver does not accept positional parameters with indexes (like ?<number>)"

With the (libsql-cgo)[https://github.com/libsql/go-libsql] client the query works without any problems (but the client has other problems lol)
Example query:
SELECT * FROM example
WHERE example_id = coalesce(?1,  example_id) or swag_id = coalesce(?2, swag_id)

Note that normal positional parameters are supported. Only the ones with indexes are not supported. See https://github.com/tursodatabase/libsql-client-go/blob/main/examples/sql/counter/main.go#L80

I opened a PR to add support for it.


Server report displays time since epoch when node not active

In case a node is not active the report shows humanizes the result of time.Since(time.Unix(0,0)) so gets displayed in years:
+---------------------------------------------------------+
|               RAFT Meta Group Information               |
+------+--------+---------+--------+----------------+-----+
| Name | Leader | Current | Online | Active         | Lag |
+------+--------+---------+--------+----------------+-----+
| A    |        | true    | true   | 0.36s          | 0   |
| B    | yes    | true    | true   | 0.00s          | 0   |
| C    |        | false   | false  | 51y83d6h10m28s | 14  |
| D    |        | false   | false  | 7m23s          | 14  |
| E    |        | true    | true   | 0.36s          | 0   |
+------+--------+---------+--------+----------------+-----+

maybe could display unknown or -?
+---------------------------------------------------------+
|               RAFT Meta Group Information               |
+------+--------+---------+--------+----------------+-----+
| Name | Leader | Current | Online | Active         | Lag |
+------+--------+---------+--------+----------------+-----+
| A    |        | true    | true   | 0.36s          | 0   |
| B    | yes    | true    | true   | 0.00s          | 0   |
| C    |        | false   | false  | -              | 14  |
| D    |        | false   | false  | 7m23s          | 14  |
| E    |        | true    | true   | 0.36s          | 0   |
+------+--------+---------+--------+----------------+-----+

nats -s nats://sys:sys@<IP_ADDRESS>:4222 server report jetstream 5 --trace
22:10:28 >>> $SYS.REQ.SERVER.PING.JSZ: {}
22:10:28 <<< {"data":{"server_id":"NDNJ4EA6VJOU3AX3QBTCGGBNAPZAXGM6ON2UZP73BE7YZCMV64BETW5I","now":"2021-03-12T06:10:28.823705Z","config":{"max_memory":6442450944,"max_storage":456062287872,"store_dir":"nodes/A/jetstream"},"memory":0,"storage":0,"api":{"total":176,"errors":32},"current_api_calls":0,"meta_cluster":{"name":"ABC","leader":"B","replicas":[{"name":"D","current":false,"offline":true,"active":337619352000,"lag":1},{"name":"B","current":true,"active":359040000,"lag":1},{"name":"E","current":false,"active":240190733000,"lag":14},{"name":"C","current":false,"offline":true,"active":778235578000,"lag":14}]}},"server":{"name":"A","host":"<IP_ADDRESS>","id":"NDNJ4EA6VJOU3AX3QBTCGGBNAPZAXGM6ON2UZP73BE7YZCMV64BETW5I","cluster":"ABC","ver":"2.2.0-RC.8","seq":25904,"jetstream":true,"time":"2021-03-12T06:10:28.823775Z"}}
22:10:28 <<< {"data":{"server_id":"NCUWG26LWK4OVMW6FURORX4C3HS5IFQJWLDDWXYL6XUEC2FCKZGNPPRX","now":"2021-03-12T06:10:28.823826Z","config":{"max_memory":-1,"max_storage":-1,"store_dir":"./nodes/E"},"memory":0,"storage":0,"api":{"total":4,"errors":4},"current_api_calls":0,"meta_cluster":{"name":"ABC","leader":"B","replicas":[{"name":"B","current":true,"active":359162000,"lag":14},{"name":"A","current":false,"active":240190701000,"lag":14},{"name":"C","current":false,"offline":true,"active":1615529428823841000,"lag":14},{"name":"D","current":false,"offline":true,"active":1615529428823841000,"lag":14}]}},"server":{"name":"E","host":"<IP_ADDRESS>","id":"NCUWG26LWK4OVMW6FURORX4C3HS5IFQJWLDDWXYL6XUEC2FCKZGNPPRX","cluster":"ABC","ver":"2.2.0-RC.8","seq":2046,"jetstream":true,"time":"2021-03-12T06:10:28.823856Z"}}
22:10:28 <<< {"data":{"server_id":"ND2GVEEXLVAQMWBXQM6FZRBFLPFELETDHC75JYFNM7255EGW5NTHFN5M","now":"2021-03-12T06:10:28.823901Z","config":{"max_memory":-1,"max_storage":-1,"store_dir":"./nodes/B"},"memory":0,"storage":479165,"api":{"total":368,"errors":138},"current_api_calls":0,"total_streams":1,"total_messages":10195,"total_message_bytes":479165,"meta_cluster":{"name":"ABC","leader":"B","replicas":[{"name":"A","current":true,"active":359185000},{"name":"C","current":false,"offline":true,"active":1615529428823921000,"lag":14},{"name":"D","current":false,"offline":true,"active":443238313000,"lag":14},{"name":"E","current":true,"active":359168000}]}},"server":{"name":"B","host":"<IP_ADDRESS>","id":"ND2GVEEXLVAQMWBXQM6FZRBFLPFELETDHC75JYFNM7255EGW5NTHFN5M","cluster":"ABC","ver":"2.2.0-RC.8","seq":2109,"jetstream":true,"time":"2021-03-12T06:10:28.823937Z"}}

problem is, as you can see with D some offline ones do have a legit active time and it's useful.  So probably I should add some kind of threshold since obviously 51 years is too long - but whats a sane threshold.


MySQL HA environment trips the NoProgressException and kill hive-sre

The initial connection take more than a few seconds and kills the program.

We'll increase the number of cycles from 5 to 20 to increase the time threshold for this check (from 2.5 secs to 10 secs).
If that still isn't enough, you can change the 'reportingInterval' from 500 (ms) to 1 sec in the config, which will increase the time to 20 secs.
In the config yaml, add 'reportingInterval: 1000' to above or below the 'parallelism' config and at the same indent level.


Laravel v5.6.*

Problem 1
- Installation request for encore/redis-manager ^0.1.1 -> satisfiable by encore/redis-manager[v0.1.1].
- Conclusion: remove laravel/framework v5.6.12
- Conclusion: don't install laravel/framework v5.6.12
- encore/redis-manager v0.1.1 requires illuminate/contracts 5.5.* -> satisfiable by illuminate/contracts[v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40].
- don't install illuminate/contracts v5.5.0|don't install laravel/framework v5.6.12
- don't install illuminate/contracts v5.5.16|don't install laravel/framework v5.6.12
- don't install illuminate/contracts v5.5.17|don't install laravel/framework v5.6.12
- don't install illuminate/contracts v5.5.2|don't install laravel/framework v5.6.12
- don't install illuminate/contracts v5.5.28|don't install laravel/framework v5.6.12
- don't install illuminate/contracts v5.5.33|don't install laravel/framework v5.6.12
- don't install illuminate/contracts v5.5.34|don't install laravel/framework v5.6.12
- don't install illuminate/contracts v5.5.35|don't install laravel/framework v5.6.12
- don't install illuminate/contracts v5.5.36|don't install laravel/framework v5.6.12
- don't install illuminate/contracts v5.5.37|don't install laravel/framework v5.6.12
- don't install illuminate/contracts v5.5.39|don't install laravel/framework v5.6.12
- don't install illuminate/contracts v5.5.40|don't install laravel/framework v5.6.12
- Installation request for laravel/framework (locked at v5.6.12, required as 5.6.*) -> satisfiable by laravel/framework[v5.6.12].

Fixed, please try again


(linux) Can't find electron

Every time I run NPM Start or NPM Build, shows this:

What do I do?

npm install

npm install
Thank you very much!


add 2 CMake options to easily build example and test program

readme.md file have been updated to explain how to use them :-)

Thanks!


fix: spaming endpoint/service not found errors

Type of change:
Bugfix
What this PR does / why we need it:
Solves #1625

Thanks! Please fix the CI jobs

Codecov Report

Merging #1626 (253b0d3) into master (9476e13) will increase coverage by 0.36%.
The diff coverage is 20.00%.

@@            Coverage Diff             @@
##           master    #1626      +/-   ##
==========================================
+ Coverage   41.30%   41.66%   +0.36%
==========================================
  Files          87       87
  Lines        7460     7467       +7
==========================================
+ Hits         3081     3111      +30
+ Misses       4026     3994      -32
- Partials      353      362       +9

Impacted Files
Coverage Δ

pkg/providers/ingress/ingress.go
4.09% <0.00%> (ø)

pkg/providers/translation/service.go
32.89% <15.38%> (+18.51%)
:arrow_up:

pkg/providers/apisix/translation/apisix_route.go
31.30% <100.00%> (+0.09%)
:arrow_up:

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

Sorry for the delay, could you please check the CI errors? @goblain

Sorry for the delay. Could you please merge the master branch first (the latest code)
We have made some fixes to test cases and others.
Thanks!


Document config for connecting to Windows domain server with integrated authentication

I have a microsoft sql server I need to connect to using Windows authentication.
With the MS sql server plugin in VSCode, this works by specifying ServerName\DBinstance and specifying "integrated" for the authentication type.
The mssql go driver explicitly supports using windows authentication
However, I cannot tell how to configure sqls to take advantage of that. Using the above as the dataSourceName results in a call to localhost for the server, which is incorrect.
It would be great to get more clarity on how to do this please.

I found the answer on StackOverflow by @akvalley
copying directly from SO:
The connection string for Windows Authentication looks like this:

"server=localhost;user id=;"

The value for "user id" parameter is blank and the "password" parameter is not used in the connection string.

and his answer also links to the issue denisenkom/go-mssqldb#475


IssuTest.testIssue221 and SocketInterceptorTest.interceptSSLBasic sometimes fails on windows

Removed possible illegal memory access during cluster listener thread termination. Possible scenario: shutdown is called from within cluster listener thread, before shutdown completes, HazelcastClient goes out of scope, client destructor is called, it waits on client shutdown latch, the shutdown completes and the client destruction is completed and cluster thread is also destructed hence accessing a startLatch at this point will cause illegal memory access.

Test PASSed.


add examples of model change pull requests

In https://github.com/openmicroscopy/ome-documentation/pull/1537#issuecomment-249163837 @sbesson suggests a seealso note referencing past model changes. Staged at http://www.openmicroscopy.org/site/support/contributing-staging/data-model-schema.html#major-or-minor-release.

@sbesson: Help! CI is breaking the pull request links by setting SOURCE_USER. Suggestions?

I can see 2 solutions: either we define an extlink which does not inherit the configurable omero_github_root (e.g. see omero_scc_branch which points at an explicit fork) and always points at origin or we actively move away from the SOURCE_USER strategy across the board. The latter would be equivalent to treating GitHub source code links in the same way we treat e.g. API links where documentation needs to be updated after publication/tagging.

The staged links are working correctly and linking to the PR's fine, formatting on the page also looks well. The merge docs build is now green again so should be good to merge.


rebase and reword docstrings

Hi @glevv
I rebased another PR that merged references to the classes you were working on, and since I was doing that, I reworded the docs a bit.
Would you mind merging :)
Thanks a lot!


Pytest deprecated support for nose - Removed in version 8

Will affect us if we update to pytest 8.
More details: https://docs.pytest.org/en/stable/deprecations.html#support-for-tests-written-for-nose

would love to work on this.

@Adamantios Can I take this up?

Hello @hamzzy and @prateekj117. Thank you for your interest in contributing to our project! You are welcome to contribute, and we appreciate your effort in helping us improve.
To ensure that your PR is accepted, please follow our Contributing Guidelines. These guidelines will provide you with the necessary steps and standards for contributing to the project.


Blank screen on boot

Hi there, I've tried to use this layer using these settings:
MACHINE=raspberrypi-4
DISTRO_FEATURES_remove ?= "alsa ext2 api-documentation bluetooth ipv6 opengl pcmcia ppp ptest wayland wifi x11 vulkan"
IMAGE_FEATURES += "ssh-server-dropbear"
IMAGE_FEATURES += "debug-tweaks"
IMAGE_INSTALL_append += " nodejs nodejs-npm node-red bash"
DISTRO_FEATURES += "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = ""
ENABLE_UART = "0"
RPI_USE_U_BOOT = "1"
PREFERRED_PROVIDER_virtual/bootloader = "u-boot"
IMAGE_INSTALL_append += " rauc"
DISTRO_FEATURES += "rauc"
SDIMG_ROOTFS_TYPE = "ext4"
WKS_FILE = "sdimage-dual-raspberrypi.wks.in"

I have ENABLE_UART to 0 (tried also without setting it) because I don't have a seria lcable.
Basically the raspberry only shows a blank page, no output or anything. Before adding this layer and using only uboot everything was working, do you have any advice on what to try?

Hi @alex88,
I recommend you to enable ENABLE_UART and to check the output on the serial console using UART to USB debug cable in order to get better understanding what is going on. Probably the logs from the serial console will indicate the cause of the issue you are having.
Best regards,
Leon

Thanks for such a quick response, I'll buy the cable and see what's going on! In the meantime I'll try also other bootloaders

@alex88 the RAUC integration having depends on u-boot.
Btw details how to use the layer are available here: https://www.konsulko.com/getting-started-with-rauc-on-raspberry-pi-2/#comment-334 with a minor that it should be WKS_FILE = "sdimage-dual-raspberrypi.wks.in".

Yeah that's the one I've followed, the only difference is that the machine was set to 64 bit. Thanks!

this might be related to the issue you are experience. If you ask me, you better make sure you have it working as per tutorial before proceeding with any changes.
Best regards,
Leon

It looked simple enough at first, but it seems none of this is simple at least at first

The 32 bit version works just fine, must be an issue with the 64 one, I'll use 32 until the uart cable gets delivered and then maybe spend some time with the 64 one. I saw there are some issues for the 64bit version on the meta-raspberry layer too so I think I can close this issue as it's not related to this layer. Thank you for helping!


Nerf the xp/hr in Guardians of the Rift

Currently the xp/hr obtained through guardians of the rift is assuming an alt is being used.
This is inconsistent with the xp/hr elsewhere in the bot.

@Lajnux Can you look at this?


Current gitlab-ci.yml example caching leads to failing tests

First off, thanks for this package, it's been a great help :-) However I did run into an issue that I expect others will experience too. Caching of resources is causing the Dusk tests to fail after a blade update.
Steps to recreate:

Clean Laravel install
Install Dusk
Add https://github.com/chilio/laravel-dusk-ci/blob/master/examples/.gitlab-ci.yml
Commit to new Gitlab repo

Tests should now be Green

Change the Laravel title in welcome.blade.php to Laravel 5
Edit Tests\Browser\ExampleTest->testBasicExample() to $browser->visit('/')->assertSee('Laravel 5');
Commit and push

The test will now fail, saying they're not seeing "Laravel 5", even though it's definitely there.
When you check the tests/Browser/screenshots image you'll see that it's still showing the old blade version. After a lot of trial and erroring, the issue was because of the job caching.
Pretty simple fix though, just remove these lines from the gitlab-ci.yml example and all is well again :)
        - resources
        - public

I removed the public folder as well as something's bound to end up in there that will cause a similar issue.

You are absolutely true. Thanks for pointing that out.
I've already updated this example.
I will include some more examples in the future, cause caching and artifacts mechanisms need much more explanations while using gitlab runners in different environments.


Download models

Updating a flow chart on fetch and downloading model from Hugging Face

After downloading model, should we automatically check for engine and init engine (if neccessary)?


prevent broken data api call from taxonomy ID selector

Taxonomy ID selector triggers broken query, for example, Annotation or Comprehensive Genome Analysis app,

click drop down button,

this is part of #1806

i believe i have fixed it, PR submitted.

confirmed on alpha.


Receipts can be invalid if isssuing profile does not set their address

Who is your user?
A financial contributor
What are they trying to achieve?
They need a valid receipt for accounting purposes.
How are they currently doing this?
They get a receipt via email or download it from transaction details, but if the issuing profile (host or independent collective) has not set their address, that area is blank on the receipt. So right now people are making do with such invalid receipts.
I have seen multiple examples of this recently, such as the below:

P4 - not super frequent or blocking essential functions, but we should try to guide people to set their address more clearly.

@Betree is this query correct if I want to email host admins without addresses set which have had at least one order (i.e. needed to generate a receipt) https://opencollective-metabase.herokuapp.com/question/617-hosts-without-address

@alanna Sorry for the late reply. It's not:

We're only looking at orders made directly to the fiscal host. We should also look at hosted collectives
Some accounts have their addresses set in data.location.structured (we're planning on unifying everything with #3494

@alanna let me know if I should go ahead and write a query for this


Mumble never initializes

When I join a server, I get this message at the bottom right:
[Mumble] initializing
[Warning] Not connected to mumble

It happens to me on all servers that use Mumble.

It was a firewall-like problem... I guess.
I was getting wifi through my phone; yesterday i bought a network card and now everything works fine.


Fix Correct the alignment process when the existing rows with same key has marked delete sign

Proposed changes
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall


Update fs2-core, fs2-io, ... to 2.5.5

Updates

co.fs2:fs2-core
co.fs2:fs2-io
co.fs2:fs2-reactive-streams

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "co.fs2" } ]

labels: library-update, semver-patch

Superseded by #180.