Sources reachable by build tools, IDEs, etc.?

After adding the compile 'com.google.cloud.bigtable:bigtable-hbase-1.2' dependency, IntelliJ, Gradle, etc. cannot find sources JAR.
I'm hoping this is enough information, please let me know if I should try to better illustrate the problem /dig into the issue.

% curl -sf 'http://repo1.maven.org/maven2/com/google/cloud/bigtable/bigtable-hbase-1.2/0.9.3/bigtable-hbase-1.2-0.9.3-sources.jar'|bsdtar tf -
META-INF/MANIFEST.MF
META-INF/
com/
com/google/
com/google/cloud/
com/google/cloud/bigtable/
com/google/cloud/bigtable/hbase1_2/
com/google/cloud/bigtable/hbase/
META-INF/maven/
META-INF/maven/com.google.cloud.bigtable/
META-INF/maven/com.google.cloud.bigtable/bigtable-hbase-1.2/
com/google/cloud/bigtable/hbase1_2/BigtableConnection.java
com/google/cloud/bigtable/hbase/bigtable-hbase.properties
META-INF/maven/com.google.cloud.bigtable/bigtable-hbase-1.2/pom.xml
META-INF/maven/com.google.cloud.bigtable/bigtable-hbase-1.2/pom.properties

We do some wild renaming of packages with the shade plugin so that we can work both in the hadoop/hbase ecosystem and the Dataflow.
In maven, I have to do a "mvn install" to get everything to work properly.

Is it not a goal to provide a good developer experience or is fixing this problem too unrealistic to be tracked as a Github issue?

It's a great goal.  It unfortunately lower than making things work.  We need the package renaming logic to work in both hadoop/hbase environments and Dataflow environments.    I'll reopen this to see if there's a way improve the experience.

try: curl -sf 'http://repo1.maven.org/maven2/com/google/cloud/bigtable/bigtable-hbase/0.9.3/bigtable-hbase-0.9.3-sources.jar'|bsdtar tf -

We've introduced bigtable-hbase-1.x, which no longer requires shading and should avoid the missing source issues

I'm not sure to understand how the last comment solve this ticket: from the beginning this ticket is about "bigtable-hbase-1.2"

bigtable-hbase-1.2 is being deprecated in favor of bigtable-hbase-1.x.  The approach taken for -1.0, -1.1, -1.2 and -1.3 jars had a fundamental flaw that boils down to package renaming due to versioning issues relating to "dll hell" or more precisely "transitive dependency hell".  We had to do quite a bit of changes in our dependencies to fix that deep rooted problem. We were concerned about backwards compatibility with the 1.[0-3], so we wanted to keep them as is.  We opted to solve the spirit of this request by creating a new single artifact that is a drop in replacement for the 1.[0-3] set of artifacts that did not require us to perform package renaming in our artifacts.

My apologies, I should've been more clear.  We are introducing 3 new artifacts that are replacing the old bigtable-hbase-{shaded,1.0,1.1,1.2,1.3}.
The new artifacts are:

bigtable-hbase-1.x: depends on hbase-shaded-client and exposes grpc and modern version of protobuf. This artifact is meant for standalone usage in webapps, beam, and other environments where the user is in control of their dependencies. This contains the actual connection implementation for hbase 1. It doesn't require any shading and allows for source navigation in ides. This should be the default choice for most users.

bigtable-hbase-1.x-shaded: this artifact doesn't contain any java source files, but uses the maven shade plugin to relocate all internal dependencies. This is meant for environments where the user is not in control of their dependencies and is mostly an implementation detail for dataflow 1.x that will eventually be deprecated in favor of beam.  Source navigation will be partially broken for this artifact: you will be able to navigate to the hbase connector code, but navigation to the underlying core client will be broken. However this is just a stopgap measure until we transition to beam.

bigtable-hbase-1.x-hadoop: this is similar the -shaded variant but exposes Hadoop compatible dependencies. This is meant to be used in mapreduce jobs where the mapreduce framework injects jars into the user'a classpath. This will have similar limitations as the -shaded variant: you will be able to navigate to hbase compatibility code, but not the underlying core client. Unfortunately I don't think this is something we can do anything about. I would appreciate any suggestions.

Which of these environments are you concerned about?

Thank you for the details. I'm concerned about a webapp context.
So bigtable-hbase-1.x (with an actual x letter in the name?) is a new artifact that will arrive soon on maven central?
Is their a documentation where all the publish artifacts (currently 12) are listed and their usage is documented?

Yes, literally bigtable-hbase-1.x, it will be available in maven central once we finish polishing the release. Once its released, you will be able to switch to it and never have to be concerned about shading issues.
Documentation is one of the things that needs to be updated for the upcoming release. And you are right we do have too many artifacts, here is a summary of them:
The 3 artifacts I mentioned above and bigtable-hbase-dataflow are the main artifacts that are intended for public consumption.
List of other artifacts:

bigtable-hbase-dataflow: bigtable connector for dataflow 1.x using the hbase api
bigtable-dataflow-import: is meant to be a cli utility to enable importing & exporting hbase sequence files to/from bigtable using dataflow
bigtable-hbase-mapreduce: is meant to be a cli utility to enable importing & exporting hbase sequence files to/from bigtable using hadoop/mapreduce
bigtable-hbase: is an internal artifact not meant for public consumption it contains/will contain common code for hbase 1 & 2 apis
bigtable-hbase-shaded, bigtable-hbase-1.0, bigtable-hbase-1.1, bigtable-hbase-1.2, bigtable-hbase-1.3: Will be deprecated as of the next release and will be deleted in the following release.
bigtable-client-core is the low level client that exposes its own undocumented api that hasn't stabilized yet and thus we discourage direct usage of it.
bigtable-protos: auto generated protobufs and grpc wrappers


live: add "tail" vertical_overflow method

Type of changes

[ ] Bug fix
[x] New feature
[x] Documentation / docstrings
[x] Tests
[ ] Other

Checklist

[x] I've run the latest black with default args on new code.
[ ] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[x] I've added tests for new code.
[x] I accept that @willmcgugan may be pedantic in the code review.

Description
This implements an alternative vertical_overflow="tail" mode for Live, behaving somehow like "crop" but only showing the trailing lines that fit the terminal height, adding an ellipsis at the top
Here is an example:

Here's the code used to generate the above asciicast:
from time import sleep
from rich.live import Live
from rich.console import Console

console = Console(
    height=5,
    force_terminal=True,
    legacy_windows=False,
    color_system=None,
    _environ={},
)
console.print("This is a console with height=5")

with Live(
    console=console,
    auto_refresh=False,
    vertical_overflow="tail",
) as live:
    display = ""
    for step in range(10):
        display += f"Step {step}\n"
        sleep(1)
        live.update(display, refresh=True)

Im afraid I don't think this is a good idea. Consider Textual for such functionality.
https://textual.textualize.io/blog/2023/07/29/pull-requests-are-cake-or-puppies/


Steps differ from option listed on Configuration

[Enter feedback here]
When checking on example to configure B2B direct connect the example recommend:
"Allow all Contoso users and groups to have outbound access to Fabrikam using B2B direct connect."
But this option is not present on portal configuration:

This could eventually create confusing to customer when using example as a guide...
https://docs.microsoft.com/en-us/azure/active-directory/external-identities/b2b-direct-connect-overview#example-1-allow-b2b-direct-connect-with-fabrikam-and-block-all-others

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

ID: 0a16a239-3c26-c839-6b40-a12afe1d5fba
Version Independent ID: b86ecce0-b57d-8d53-f3ae-cbd0f0fcbbba
Content: B2B direct connect overview - Azure AD - Microsoft Entra
Content Source: articles/active-directory/external-identities/b2b-direct-connect-overview.md
Service: active-directory
Sub-service: b2b
GitHub Login: @msmimart
Microsoft Alias: mimart

@Wibusts
Thanks for your feedback! We will investigate and update as appropriate.

#reassign:@csmulligan

@Wibusts thanks so much for this suggestion. I've moved this issue to an internal work item for tracking. I'll update this thread once I have any news on this item.

Hi @Wibusts  thank you so much for pointing this out. We've updated the article and changes should publish shortly. This issue will close automatically once the changes are merged. Thanks again!

#please-close


Velocity with Scrollmagic

I'm trying to get velocity's Sequenced Animations to run with scrollmagic.
This is the code taken from ScrollMagic's docs on Velocity.

This is the sequence animation snippet taken from Velocity docs

How can I add the sequence into scrollmagics?
var scene = new ScrollMagic.Scene({triggerElement: "#trigger"})
.setVelocity <-- sequence here
.addTo(controller);
Please help.
Thank you!

You'd need to take it up with ScrollMagic as we have nothing to do with it (unlike the other way around where they support us) - however logically I'd be looking to see if they support Velocity Sequences at all.

I see!
Thank you.


Add --features option to generate binaries

The binary will not be generated unless the --features option is given, so the option description has been added.

Oops, duplicate #172

#172 is a more broad one and I have change requests there, so merging this for now


Exr fix

Replaced exrTools with Imagemagic Convert.
Fixed a bug where textures were converted multiple times.

@benjamin-heasly
can you review this PR and let me know if it needs any more changes?

Hi @hblasins,
Sorry for the delay on my part.  Yes, this looks good to me.
I made a few changes:

add recursive search for local files that are referenced form the scene
tests for this search
a few tests for recoding images
minor code cleanup

So I will go ahead and merge.  Thanks for the imagemagic.
If we need to make more changes to support what you're working on, I suggest we make a fresh issue, branch, PR.


Safeguarding against usage of uninitialized DistributedManager

Modulus Pull Request
Description

closes #474
Should be merged in after #469
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[x] The CHANGELOG.md is up to date with these changes.
[x] An issue is linked to this pull request.

Dependencies

None

/blossom-ci

/blossom-ci

/blossom-ci

/blossom-ci

What it does makes sense. Is this fix supposed to safeguard against initialized DM but requesting an uninitialized distributed group?

@azrael417 Not quite. This PR is safeguarding against using the manager before calling DistributedManager.initialize() first. There was a bug in CorrDiff where this was silently happening causing a multi GPU job to behave like independent single GPU jobs since that's the default.

/blossom-ci

/blossom-ci


Cannot suppress import warnings inside script tags.

Whenever importing components into other components, I am unable to disable these warning dots in all of my components. See screenshot below. You can see I am using the Homepage component inside my route.

The following settings did not work:

"javascript.validate.enable": false
"html.validate.scripts": false,

You need to set the extensions options to false, not vscode default ones:
i.e
"svelte.plugin.css.diagnostics.enable": false,
"svelte.plugin.typescript.diagnostics.enable": false,

Changing "svelte.plugin.typescript.diagnostics.enable": true and completely restarting VS Code fixed this. Do you think enabling typescript diagnostics by default is a good idea? I would think most people would probably be using Svelte with vanilla JS first, before adding in Typescript.

Great to know!
About enabling typescript diagnostics: it's nice to have at least inferred types, even if you're using js 😁


How Does this Library Handle dtstart?

It isn't stated clearly in the docs anywhere, and it seems like there are conflicting opinions in both how this library handles dtstart. In the docstrings for base.py and Recurrence it does seem to indicate that dtstart is handled the according the RFC 2445, which uses it as both the starting point for recurrences and as the first recurrence returned.
This is in contrast to how dateutil.rrule handles it, which just uses dtstart as the starting point for recurrences and does not automatically add it as the first occurrence.
It looks like this can be a bit of a pain point for users. #50 #36
Should this be better documented somewhere, to explicitly state that it doesn't follow the way dateutil.rrule handles dtstart and follows more closely to the spec. Or should changing the behavior be considered since it appears to cause issues? I recognize that this would be a big change.

Didn't recognize that the inclusion of dtstart is indeed according to RFC 2445. Thanks @jpulec.
Then I would suggest to 1) document it and 2) maybe add an optional parameter dtstart_include to the between method that has False as default. This way it is clear how django-recurrence works for this case, it stays backwards compatible and users who are bothered by the default behavior can change it.
Any thoughts on that? If someone is interested I can make a pull request.

@denisiko I'm biased, but I would really prefer a solution that supports some way following dateutil.rrule and not the spec, similar to what you described in 2).
Should this be something done as a between() parameter? Or does it make more sense to just add a setting for the entire library to support one behavior over the other? Or perhaps both?

@jpulec I could think of a global settings constant in combination with a between param that overwrites the settings value if set. So it would be like:

dtstart is included if nothing is specified (according to spec)
dtstart inclusion is handled by user's global settings (if set properly)
dtstart is handled by optional between param if set explicitly

@denisiko Is it just me, or would it seem to make more sense for the between() parameter to be the first place to check? That way a user could override it on a call by call basis. So we could do something like add a global setting called RECURRENCE_DTSTART_INCLUDE or whatever, and that value would default to True. Then the function signature for between() could specify dtstart_include=settings.RECURRENCE_DTSTART_INCLUDE as a default. That way you could override it easily on a call by call basis, or you could just flip the setting to have the default changed everywhere.
Does that make sense?

@jpulec That's exactly what I meant :-) Think I wasn't clear on describing the order.
I already started working on this. I even named the global settings param exactly like you suggested :-) But after some thinking I came to the conclusion that it would be better to move my planned between() param dtstart_inc to the initialisation of the recurrence object and the definition of the recurrence field (like a max_length on a CharField). Then the global variable would be overwritten there.
I think it is easier this way because then you can e.g. define two different RecurrenceFields in a model where one includes dtstart and the other doesn't, without redefining dtstart for every single between(). Besides dtstart isn't only relevant for between(), but also for after() and some other functions as far as I can see from the code base.
Makes sense? I will have a PR ready by the end of the week.

Thanks @jpulec and @denisiko for all your work here - sorry I'm a bit late to the party.
I'm open to being convinced otherwise, but I'm -1 on doing this with a setting - I think a parameter is much clearer. My concern with a setting is this: say you have two reusable apps installed which both depend on django-recurrence, and one wants the setting set, and one doesn't - how will that be resolved? If they both just use a parameter that works fine, but with a setting it's all or nothing for every consumer of settings.py.
Thoughts?

@dominicrodger I understand your concern. The way I would approach this is as following:
You have a variable in base.py which is reserved for the user's setting (for now I have placed it under the DAILY, WEEKLY etc. constants). It tries to get the user's RECURRENCE_DTSTART_INCLUDE setting and if it doesn't get a valid bool it defaults to False.
If another app wants a specific value for RECURRENCE_DTSTART_INCLUDE it just has to overwrite the variable in base.py (a setter function would make sense), so there's no need to access django.conf.settings. This should be made clear e.g. as a comment.
When I have the PR ready it's going to be clear I think.

On the other hand it is not very elegant that you would have to explicitly overwrite the value on module level ever time you import the module and before you do anything with it. Maybe @dominicrodger is right and a parameter for the field and the object would be sufficient.

I still think the whole pull request #36 should be merged, maybe after some cleaning up. The current code is just wrong, my tests prove that. Also some weird tests with comments are resolved.
Maybe bump to a new major version without backwards compatibility, so people know their own code/fix to fix this is broken. In other words, people that had this problem and fixed it locally, know it's not ideal and can just drop the local fix.
Having a parameter to let people decide to fix this issue is not ideal, that's a fix for a fix. Please just fix the core.
Furthermore I found some more issues with weekly patterns and excluding dates, didn't fix that one yet.

@douwevandermeij The code is not wrong or broken at this part, it follows a clear specification. Right at the beginning of the docs it says that Recurrence/Rule objects use a subset of RFC 2445. You can't just cherrypick from the spec because that would break consistency, so you also have to treat dtstart according to RFC 2445:

The "DTSTART" property value, if specified, counts as the first occurrence.

Therefore your test function test_occurrences_with_start_and_end_weekly_tuesdays() doesn't prove anything in this direction and is wrong in the current state, because it is missing a crucial assertion.
I admit that the current dtstart practice might not be ideal (I was also in favor of merging your pull request because I didn't know the relevant part of the spec back then), but again I think it would be better to let the user decide if he wants to alter the default behavior. This would not be a fix for a fix, it would be the best compromise in my opinion.
Anyway: I created my own pull request #93 that enables the user to decide for himself how dtstart should be handled. Also tried to document it as clear as possible.

Ah, I didn't know that relevant spec either. Sounds like a weird spec, but it should be obeyed, fair enough. Your suggestion sounds plausible then; best of both worlds.

Think so too, pretty weird idea. Just would be nice if this dtstart chapter closes.

I think this issue can be closed now with #93.

@denisiko I believe you're right. Glad to see this all get resolved. Great work and thanks!

No problem and thanks!


Extract local dish name from dish description

To be able to display the local dish name in a better fashion than in the dish description, we need to extract it from the data directly.
To do so, we will:

[x] Create a new field localName in resources/data/dishes
[x] Supply a local name for dishes from countries that don't use the Latin alphabet (and leave others empty)

This will affect all the dishes from countries that don't use the Latin alphabet (China, Japan, Korea, Taiwan, Thailand).
Related Issue: https://github.com/localonomy/app/issues/2

Closed by: https://github.com/localonomy/api/commit/f262c56336c88bff2f54dbd33146c2300eb94572


[issue67] self.latest_action_name = None

Proposed changes:
Minor bug fix. See https://github.com/RasaHQ/rasa_core/issues/67
Status (please check what you already did):

[x] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog

 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.fakesecret seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Good catch :+1: thanks


Update cadence client to up to date version

What changed?
Updated Cadence client to a recent version

Why?
To make sure that Cadence client used for Cadence internal automation is in sync with recent version.

How did you test it?
integration tests

Potential risks
Should be none, we haven't introduced any breaking changes in the client so far.

Release notes
Updated Cadence Go client

Documentation Changes

It does not work since ringpop requires an ancient version for thrift:
`../../.gvm/pkgsets/go1.20/global/pkg/mod/github.com/uber-go/tally@v3.5.10+incompatible/prometheus/reporter.go:166:19: undefined: prom.Observer
../../.gvm/pkgsets/go1.20/global/pkg/mod/github.com/uber-go/tally@v3.5.10+incompatible/prometheus/reporter.go:167:19: undefined: prom.Observer
github.com/uber/ringpop-go
../../.gvm/pkgsets/go1.20/global/pkg/mod/github.com/uber/ringpop-go@v0.8.5/ringpop.go:817:20: not enough arguments in call to s.Write
have ("github.com/apache/thrift/lib/go/thrift".TBinaryProtocol)
want ("context".Context, "github.com/apache/thrift/lib/go/thrift".TProtocol)
../../.gvm/pkgsets/go1.20/global/pkg/mod/github.com/uber/ringpop-go@v0.8.5/ringpop.go:821:12: not enough arguments in call to transport.Flush
have ()
want ("context".Context)
../../.gvm/pkgsets/go1.20/global/pkg/mod/github.com/uber/ringpop-go@v0.8.5/ringpop.go:834:16: not enough arguments in call to s.Read
have ("github.com/apache/thrift/lib/go/thrift".TBinaryProtocol)
want ("context".Context, "github.com/apache/thrift/lib/go/thrift".TProtocol)
FAIL	github.com/uber/cadence/cmd/server/cadence [build failed]`


App crashes during the launch on android 4.1.2

Steps to Reproduce

Run "flutter build apk"
Install on android emulator 4.1.2 with adb install build/app/outputs/apk/release/app-release.apk
Launch app

Logs

E/AndroidRuntime: FATAL EXCEPTION: main
    java.lang.UnsatisfiedLinkError: Couldn't load flutter: findLibrary returned null
        at java.lang.Runtime.loadLibrary(Runtime.java:365)
        at java.lang.System.loadLibrary(System.java:535)
        at io.flutter.view.FlutterMain.startInitialization(FlutterMain.java:172)
        at io.flutter.view.FlutterMain.startInitialization(FlutterMain.java:149)
        at io.flutter.app.FlutterApplication.onCreate(FlutterApplication.java:22)
        at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:999)
        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4151)
        at android.app.ActivityThread.access$1300(ActivityThread.java:130)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1255)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at android.os.Looper.loop(Looper.java:137)
        at android.app.ActivityThread.main(ActivityThread.java:4745)
        at java.lang.reflect.Method.invokeNative(Native Method)
        at java.lang.reflect.Method.invoke(Method.java:511)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
        at dalvik.system.NativeStart.main(Native Method)

Analyzing mobile...

   info • Name non-constant identifiers using lowerCamelCase • lib/model/model.dart:2:16
   info • Name non-constant identifiers using lowerCamelCase • lib/model/model.dart:3:16
   info • Name non-constant identifiers using lowerCamelCase • lib/tests/test_page.dart:39:8
   info • Name non-constant identifiers using lowerCamelCase • lib/tests/test_page.dart:44:8
   info • Use `;` instead of `{}` for empty constructor bodies • lib/tests/test_page.dart:53:24
warning • The asset icons/ does not exist • pubspec.yaml:44:6

6 issues found. (ran in 3.3s)

[✓] Flutter (Channel beta, v0.5.1, on Mac OS X 10.13.5 17F77, locale en-US)
    • Flutter version 0.5.1 at /Users/yevgeniishein/Library/flutter
    • Framework revision c7ea3ca377 (5 weeks ago), 2018-05-29 21:07:33 +0200
    • Engine revision 1ed25ca7b7
    • Dart version 2.0.0-dev.58.0.flutter-f981f09760

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /Users/yevgeniishein/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • ANDROID_HOME = /Users/yevgeniishein/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.4.1, Build version 9F2000
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.0

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 26.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[!] IntelliJ IDEA Community Edition (version 2017.2.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.io/intellij-setup/#installing-the-plugins

[✓] VS Code (version 1.24.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.13.2

[✓] Connected devices (1 available)
    • emulator-5554 • emulator-5554 • android-x86 • Android 4.1.2 (API 16) (emulator)

! Doctor found issues in 1 category.

Sorry for the late response.
Is this still an issue with recent Flutter versions?

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.

Yep, it's still an issue

@rostopira can you please provide more information about how to reproduce?
Please add the output of flutter doctor -v.

Just install Jelly Bean emulator via AVD, 4.1.2 with Google APIs, try to launch anything
Gonna test with 4.2 now
But to be honest, I think it's emulator bug, not flutter
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v1.2.2-pre.21, on Mac OS X 10.14.1 18B75, locale
    en-BY)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
[✓] Android Studio (version 3.3)
[✓] IntelliJ IDEA Ultimate Edition (version 2018.3.4)
[!] VS Code (version 1.31.0)
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (3 available)

! Doctor found issues in 1 category.

Got a response from tester
App works just fine on a real device running Andoid 4.1.1

Is this also with flutter run or only with flutter build ... and flutter install?

@zoechi with both and --debug param, I've even tried with --target-platform=android-x86 and --target-platform=android-x64

Is this also with flutter run or only with flutter build ... and flutter install?

Sorry, I meant  flutter build ... and adb install

2. Install on android emulator 4.1.2 with adb install build/app/outputs/apk/release/app-release.apk


RIUI-755: Add back error anchor post being deleted by merge

https://tools.hmcts.net/jira/browse/RIUI-755

This will break server-side. Needs refactoring to consider no-javascript


com.shine.app loads infinitely after logging in ( Firebase related?)

Hello,
As stated in the issue up above, the application com.shine.app infinitely loads, while Firebase issues pop up in logcat. Here is the most prominent one:
03-22 08:47:04.112  1401  1554 I com.shine.app: Rejecting re-init on previously-failed class java.lang.Class<com.appsflyer.FirebaseInstanceIdListener>: java.lang.NoClassDefFoundError: Failed resolution of: Lcom/google/firebase/iid/FirebaseInstanceIdService;
03-22 08:47:04.112  1401  1554 I com.shine.app:   at com.appsflyer.internal.k$d com.appsflyer.internal.k.ˏ(android.content.Context) (:105)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at void com.appsflyer.AppsFlyerLibCore.ॱ(android.content.Context, java.util.Map) (:2210)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at java.util.Map com.appsflyer.AppsFlyerLibCore.ˏ(com.appsflyer.internal.j) (:1973)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at void com.appsflyer.AppsFlyerLibCore.ॱ(com.appsflyer.AppsFlyerLibCore, com.appsflyer.internal.j) (:51010)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at void com.appsflyer.AppsFlyerLibCore$a.run() (:3298)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at java.lang.Object java.util.concurrent.Executors$RunnableAdapter.call() (Executors.java:458)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at void java.util.concurrent.FutureTask.run() (FutureTask.java:266)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at void java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run() (ScheduledThreadPoolExecutor.java:301)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at void java.util.concurrent.ThreadPoolExecutor.runWorker(java.util.concurrent.ThreadPoolExecutor$Worker) (ThreadPoolExecutor.java:1167)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at void java.util.concurrent.ThreadPoolExecutor$Worker.run() (ThreadPoolExecutor.java:641)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at void com.appsflyer.AFExecutor$3$2.run() (:33)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at void java.lang.Thread.run() (Thread.java:764)
03-22 08:47:04.112  1401  1554 I com.shine.app: Caused by: java.lang.ClassNotFoundException: Didn't find class "com.google.firebase.iid.FirebaseInstanceIdService" on path: DexPathList[[zip file "/system/framework/android.test.mock.jar", zip file "/system/framework/android.test.runner.jar", zip file "/data/app/com.shine.app-JdmskfYsTyt3c2bBhjjDuQ==/base.apk", zip file "/data/app/com.shine.app-JdmskfYsTyt3c2bBhjjDuQ==/split_config.arm64_v8a.apk", zip file "/data/app/com.shine.app-JdmskfYsTyt3c2bBhjjDuQ==/split_config.en.apk", zip file "/data/app/com.shine.app-JdmskfYsTyt3c2bBhjjDuQ==/split_config.xxhdpi.apk"],nativeLibraryDirectories=[/data/app/com.shine.app-JdmskfYsTyt3c2bBhjjDuQ==/lib/arm64, /data/app/com.shine.app-JdmskfYsTyt3c2bBhjjDuQ==/base.apk!/lib/arm64-v8a, /data/app/com.shine.app-JdmskfYsTyt3c2bBhjjDuQ==/split_config.arm64_v8a.apk!/lib/arm64-v8a, /data/app/com.shine.app-JdmskfYsTyt3c2bBhjjDuQ==/split_config.en.apk!/lib/arm64-v8a, /data/app/com.shine.app-JdmskfYsTyt3c2bBhjjDuQ==/split_config.xxhdpi.apk!/lib/arm64-v8a, /system/lib64, /system/vendor/
03-22 08:47:04.112  1401  1554 I com.shine.app:   at java.lang.Class dalvik.system.BaseDexClassLoader.findClass(java.lang.String) (BaseDexClassLoader.java:134)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at java.lang.Class java.lang.ClassLoader.loadClass(java.lang.String, boolean) (ClassLoader.java:379)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at java.lang.Class java.lang.ClassLoader.loadClass(java.lang.String) (ClassLoader.java:312)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at com.appsflyer.internal.k$d com.appsflyer.internal.k.ˏ(android.content.Context) (:105)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at void com.appsflyer.AppsFlyerLibCore.ॱ(android.content.Context, java.util.Map) (:2210)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at java.util.Map com.appsflyer.AppsFlyerLibCore.ˏ(com.appsflyer.internal.j) (:1973)
03-22 08:47:04.112  1401  1554 I com.shine.app:   at void com.appsflyer.AppsFlyerLibCore.ॱ(com.appsflyer.AppsFlyerLibCore, com.appsflyer.internal.j) (:51010)
03-22 08:47:04.113  1401  1554 I com.shine.app:   at void com.appsflyer.AppsFlyerLibCore$a.run() (:3298)
03-22 08:47:04.113  1401  1554 I com.shine.app:   at java.lang.Object java.util.concurrent.Executors$RunnableAdapter.call() (Executors.java:458)
03-22 08:47:04.113  1401  1554 I com.shine.app:   at void java.util.concurrent.FutureTask.run() (FutureTask.java:266)
03-22 08:47:04.113  1401  1554 I com.shine.app:   at void java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run() (ScheduledThreadPoolExecutor.java:301)
03-22 08:47:04.113  1401  1554 I com.shine.app:   at void java.util.concurrent.ThreadPoolExecutor.runWorker(java.util.concurrent.ThreadPoolExecutor$Worker) (ThreadPoolExecutor.java:1167)
03-22 08:47:04.113  1401  1554 I com.shine.app:   at void java.util.concurrent.ThreadPoolExecutor$Worker.run() (ThreadPoolExecutor.java:641)
03-22 08:47:04.113  1401  1554 I com.shine.app:   at void com.appsflyer.AFExecutor$3$2.run() (:33)
03-22 08:47:04.113  1401  1554 I com.shine.app:   at void java.lang.Thread.run() (Thread.java:764)

Every warning and/or error I've seen seems to be related to Firebase in some way. If you need any more logs or if I can help with this issue in any way feel free to ping!

Pinging this issue since it seems nobody even looked at it yet.
It seems appsflyer, a library used by Shine, is trying to load Lcom/google/firebase/iid/FirebaseInstanceIdService which doesn't have an implementation in microG as of yet.
As such the application fails and you're prompted to an infinite loading screen upon trying to log in.
I reiterate, I'm willing to develop reproducible PoCs, help debug this issue and whatnot but without any thoughts on this I won't be able to do much, as I'm fairly ignorant when it comes to microG's codebase and if this issue is even linked to what I believe it is.

@mar-v-in would need to take a look at that. I am not sure if he is developing on microg right now.

The issue might not be Firebase related after all, but I do not see any issue in a verbose logcat whatsoever, so we're back to square one.
Here is my log included where I try to log in, wait a few seconds and then stop logging
logs-2020-04-25-19-01-56.zip

Related to #971 ; uses the same library and encounters the same kind of deadlock


BUG: weird dot at the end of Folder Name

I tried to add a bunch of test folders to the Silverstripe demo site and they got a "dot" added to the end of their name. I added a folder "test" ten or so times.

Reproduced outside of demo.silverstripe.org (SS 3.6.0)


Generate unique instance ID for each cloud..

Generate unique ID UUID for each cloud.

Resolves issues with #36
Closes #46
Closes https://issues.jenkins-ci.org/browse/JENKINS-56201

@rachely3n getInstanceUniqueId() returned the hashcode of the cloud's name, which would result in a collision if two clouds shared the same name. This PR generates a unique UUID for each cloud and incorporates it into the cloud label, which removes potential collisions.

@craigatgoogle Yep, I understood that portion, but just wanted to verify, is the problem with two different masters only defined by different clouds or do we also want to distinguish instances under different instance configurations.

@rachely3n the referenced issue is #46 which is two masters using the same cloud configuration. This PR would solve that problem.

Small comment; everything else looks good. However, I'm not sure I see how this change will close out those issues. Instead of getInstanceUniqueId, we're replacing it with UUID. Wouldn't instances under different configurations but with the same cloud instance id still be identified as the same by CleanLostNodes?

No..
That never happened...
Both issues (#36 and #46) was about same names (ids) of different clouds.

@rachely3n Maybe in some ways..
Only think that might be wort adding at instance configuration level is max number of instances..
But if really needed it can be now easily done by creating 2 or more clouds..

Just ran the integration tests. One test is failing:
INFO: Provisioning node from config com.google.jenkins.plugins.computeengine.InstanceConfiguration@475e0463 for excess workload of 1 units of label 'integration'
Mar 22, 2019 10:58:19 AM com.google.jenkins.plugins.computeengine.ComputeEngineCloud availableNodeCapacity
INFO: Found capacity for 10 nodes in cloud integration
Mar 22, 2019 10:58:21 AM com.google.jenkins.plugins.computeengine.ComputeEngineCloud lambda$provision$0
INFO: Waiting 300000ms for node integration-qn1zfz to connect
Mar 22, 2019 10:58:22 AM com.google.jenkins.plugins.computeengine.ComputeEngineCloud provision
INFO: Provisioning node from config com.google.jenkins.plugins.computeengine.InstanceConfiguration@485cb497 for excess workload of 1 units of label 'integration'
Mar 22, 2019 10:58:23 AM com.google.jenkins.plugins.computeengine.ComputeEngineCloud availableNodeCapacity
INFO: Found capacity for 9 nodes in cloud integration
Mar 22, 2019 10:58:25 AM com.google.jenkins.plugins.computeengine.ComputeEngineCloud lambda$provision$0
INFO: Waiting 300000ms for node integration-pmrzns to connect
Mar 22, 2019 10:59:55 AM com.google.jenkins.plugins.computeengine.ComputeEngineCloud lambda$provision$0
INFO: 90796ms elapsed waiting for node integration-pmrzns to connect
 expected:<[954519824]> but was:<[81926d94-678f-4607-a49c-d519f87b5faf]>
[INFO]
[ERROR] Tests run: 12, Failures: 1, Errors: 0, Skipped: 0

@rachely3n Which test is failing?
I cannot see 954519824 as static anywhere..

@rachely3n Ok found it :)

Is there a way we could run integration tests in CI?
Maybe only from inside local (from inside repo itself) PRs but still would be great..

@ingwarsw we're currently trying to improve that part, but we haven't been able to devote much resources to it. Sorry about that! I know it can be frustrating.

Thanks again for contributing this, super useful!


Implement with selenium

Hi is there a way to implement 2 captcha with selenium thanks.

Hi is there a way to implement 2 captcha with selenium thanks.

Hi!
You can use selenium or any other browser automation framework for your task and at the same time use our package to interact with 2captcha API.
Use 2captcha to get an answer for your captcha, then use selenium to submit the answer.


Can't find proof of the yeti

I didn't expect to find it but I expected you to at least try. :wink:
> GET /api/evidence/proof-of-the-yeti HTTP/1.1
> User-Agent: curl/7.40.0
> Host: next.belframework.org
> Accept: */*
>
< HTTP/1.1 500 Internal Server Error
< Server: nginx/1.4.6 (Ubuntu)
< Date: Fri, 27 Feb 2015 22:51:23 GMT
< Content-Type: text/plain
< Content-Length: 8164
< Connection: keep-alive
< Keep-Alive: timeout=20
< Vary: Accept-Encoding
<
BSON::InvalidObjectId: illegal ObjectId format: proof-of-the-yeti
	/var/lib/gems/2.0.0/gems/bson-1.12.0.rc2/lib/bson/types/object_id.rb:21:in `from_string'
	/var/lib/gems/2.0.0/gems/bson-1.12.0.rc2/lib/bson/types/object_id.rb:21:in `ObjectId'
	/home/ubuntu/projects/openbel-server/lib/evidence/mongo.rb:56:in `to_id'
	/home/ubuntu/projects/openbel-server/lib/evidence/mongo.rb:27:in `find_evidence_by_id'
	/home/ubuntu/projects/openbel-server/app/routes/evidence.rb:108:in `block in <class:Evidence>'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1603:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1603:in `block in compile!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:966:in `[]'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:966:in `block (3 levels) in route!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:985:in `route_eval'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:966:in `block (2 levels) in route!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1006:in `block in process_route'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1004:in `catch'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1004:in `process_route'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:964:in `block in route!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:963:in `each'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:963:in `route!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1076:in `block in dispatch!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `block in invoke'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `catch'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `invoke'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1073:in `dispatch!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:898:in `block in call!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `block in invoke'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `catch'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `invoke'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:898:in `call!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:886:in `call'
	/var/lib/gems/2.0.0/gems/rack-1.6.0/lib/rack/logger.rb:15:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:210:in `call'
	/var/lib/gems/2.0.0/gems/rack-1.6.0/lib/rack/head.rb:13:in `call'
	/var/lib/gems/2.0.0/gems/rack-1.6.0/lib/rack/methodoverride.rb:22:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/show_exceptions.rb:21:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:180:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:2014:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:945:in `forward'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1019:in `route_missing'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:980:in `route!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:976:in `route!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:976:in `route!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:976:in `route!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1076:in `block in dispatch!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `block in invoke'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `catch'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `invoke'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1073:in `dispatch!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:898:in `block in call!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `block in invoke'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `catch'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `invoke'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:898:in `call!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:886:in `call'
	/var/lib/gems/2.0.0/gems/rack-1.6.0/lib/rack/logger.rb:15:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:210:in `call'
	/var/lib/gems/2.0.0/gems/rack-1.6.0/lib/rack/head.rb:13:in `call'
	/var/lib/gems/2.0.0/gems/rack-1.6.0/lib/rack/methodoverride.rb:22:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/show_exceptions.rb:21:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:180:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:2014:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:945:in `forward'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1019:in `route_missing'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:980:in `route!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:976:in `route!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:976:in `route!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:976:in `route!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1076:in `block in dispatch!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `block in invoke'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `catch'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `invoke'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1073:in `dispatch!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:898:in `block in call!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `block in invoke'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `catch'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1058:in `invoke'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:898:in `call!'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:886:in `call'
	/var/lib/gems/2.0.0/gems/rack-1.6.0/lib/rack/logger.rb:15:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:210:in `call'
	/var/lib/gems/2.0.0/gems/rack-1.6.0/lib/rack/head.rb:13:in `call'
	/var/lib/gems/2.0.0/gems/rack-1.6.0/lib/rack/methodoverride.rb:22:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/show_exceptions.rb:21:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:180:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:2014:in `call'
	/var/lib/gems/2.0.0/gems/rack-cors-0.3.1/lib/rack/cors.rb:72:in `call'
	/var/lib/gems/2.0.0/gems/rack-1.6.0/lib/rack/deflater.rb:35:in `call'
	/var/lib/gems/2.0.0/gems/rack-1.6.0/lib/rack/logger.rb:15:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:210:in `call'
	/var/lib/gems/2.0.0/gems/rack-1.6.0/lib/rack/head.rb:13:in `call'
	/var/lib/gems/2.0.0/gems/rack-1.6.0/lib/rack/methodoverride.rb:22:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/show_exceptions.rb:21:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:180:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:2014:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1478:in `block in call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1788:in `synchronize'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:1478:in `call'
	/var/lib/gems/2.0.0/gems/puma-2.11.0/lib/puma/rack_patch.rb:13:in `call'
	/var/lib/gems/2.0.0/gems/sinatra-1.4.5/lib/sinatra/base.rb:217:in `call'
	/var/lib/gems/2.0.0/gems/puma-2.11.0/lib/puma/configuration.rb:82:in `call'
	/var/lib/gems/2.0.0/gems/puma-2.11.0/lib/puma/server.rb:507:in `handle_request'
	/var/lib/gems/2.0.0/gems/puma-2.11.0/lib/puma/server.rb:375:in `process_client'
	/var/lib/gems/2.0.0/gems/puma-2.11.0/lib/puma/server.rb:262:in `block in run'
	/var/lib/gems/2.0.0/gems/puma-2.11.0/lib/puma/thread_pool.rb:104:in `call'
* Connection #0 to host next.belframework.org left intact
	/var/lib/gems/2.0.0/gems/puma-2.11.0/lib/puma/thread_pool.rb:104:in `block in spawn_thread'

Thanks 😊!


Adding new devices re-using the same app id / secret id

So far a user needs to add app id / secret id for every new device.
To evaluate if entering them once and then having the possibility to add new devices with just one click

Won't fix since based on #77 there are scenarios in which using different app id and secret is required


Make a scope-limited query when "limit search to scope" is on

Previously, "limit search to en:  yes" did nothing as far as I can tell.
Also, default store.db.entries to [] (I was getting store.db.entries.push is not a function testing locally).

Thank you! That was an oversight on my part as far as I can tell.


Test GET requests for invalid dataset id

statswalesr implementation (ua = user agent)
request <- httr::GET(url, ua)
if (httr::http_error(request)) {
message("Dataset was not found. Check your dataset id for typos. If your dataset id is correct, the API might be unavailable.")

return(NULL)

}
else {
message("Downloading StatsWales dataset...")
}

Tried changing the try/except in the function from a ValueError to a HTTP error and the function can't handle that! Will wait to have another look some time in the week. The best way to do the internet connection bit is definitely requests and I will add that in myself this week I think.

I've put the HTTP error handling in my functions if that helps :)


Add support for commenting out packages in detach.txt and shitty to run module from terminal

Please add support for commenting out packages in /sdcard/detach.txt file. And also, it would be useful to be able to run this module from terminal without having to call the full path of the detacher.
Also, i downloaded the source to try to do this myself, but the source.gz actually doesn't contain the source, but does contain the already compiled module, which we can already obtain by just downloading the module. Is there any way to get you to publish the source? If so, then someone could help.
Best regards and thanks

added support for commenting out with #
and release the source here https://github.com/j-hc/mindetach-magisk/tree/master/detacher


Turn RepoRef and RepoAssignment back into func(*Context) (#15372)

Backport #15372
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

To Anyone reviewing this: to make it easier to review turn off whitespace changes.

Yeah sorry about that!
One major benefit of this pr is substantially reducing the indentation of those functions.

🚀


Android Box 5.0 no video playback

I'm submitting a ...

[ ] bug report

General infomration
On an old huawei box 5.0 i cannot playback any netflix video
Prerequisites
Android Lollipop 5.0
Kodi 18 beta2 (beta 3 crash on that box)
Description
No video playback
Operating System

[ ] Android

Additional informatin on the environment
[Descripe your environment a bit more detailed, are you using LibreElec f.e.]
Debug log
15:55:12.245 T:18446744072045174912  NOTICE: ADDON: skin.estuary v2.0.12 installed
15:55:13.231 T:18446744072386573056 WARNING: CGUIMediaWindow::OnMessage - updating in progress
15:55:25.583 T:18446744072187621248   ERROR: GetDirectory - Error getting
15:56:06.310 T:18446744072386573056   ERROR: Previous line repeats 6 times.
15:56:06.310 T:18446744072386573056  NOTICE: VideoPlayer::OpenFile: plugin://plugin.video.netflix/?action=play_video&infoLabels=%7B%27rating%27%3A+0%2C+%27season%27%3A+None%2C+%27tvshowtitle%27%3A+%27%27%2C+%27mediatype%27%3A+%27movie%27%2C+%27director%27%3A+u%27James+DeMonaco%27%2C+%27duration%27%3A+6548%2C+%27year%27%3A+2016%2C+%27genre%27%3A+u%22Thriller+d%27azione%22%2C+%27plot%27%3A+u%27Invoca+che+il+caos+possa+terminare%2C+ma+per+vedere+un+futuro+senza+terrore%2C+dovr%5Cxe0+superare+la+notte.%27%2C+%27episode%27%3A+%27%27%2C+%27title%27%3A+u%27La+Notte+del+giudizio%3A+Election+Year%27%2C+%27mpaa%27%3A+%27MiBAC-VM14%27%2C+%27writer%27%3A+%27%27%2C+%27cast%27%3A+%5Bu%27Elizabeth+Mitchell%27%2C+u%27Mykelti+Williamson%27%2C+u%27Frank+Grillo%27%2C+u%27Edwin+Hodge%27%2C+u%27Betty+Gabriel%27%2C+u%27Joseph+Julian+Soria%27%2C+u%27Kyle+Secor%27%2C+u%27Terry+Serpico%27%5D%7D&video_id=80094662&pin=True
15:56:06.313 T:18446744071938137088  NOTICE: Creating InputStream
15:56:06.539 T:18446744071938137088   ERROR: AddOnLog: InputStream Adaptive: Key system request: com.widevine.alpha
15:56:07.659 T:18446744071939800064   ERROR: Traceback (most recent call last):
15:56:07.659 T:18446744071939800064   ERROR:   File "/home/jenkins/workspace/Android-ARM/tools/depends/xbmc-depends/arm-linux-androideabi-21-release/lib/python2.7/SocketServer.py", line 290, in _handle_request_noblock
15:56:07.661 T:18446744071939800064   ERROR:   File "/home/jenkins/workspace/Android-ARM/tools/depends/xbmc-depends/arm-linux-androideabi-21-release/lib/python2.7/SocketServer.py", line 318, in process_request
15:56:07.662 T:18446744071939800064   ERROR:   File "/home/jenkins/workspace/Android-ARM/tools/depends/xbmc-depends/arm-linux-androideabi-21-release/lib/python2.7/SocketServer.py", line 331, in finish_request
15:56:07.664 T:18446744071939800064   ERROR:   File "/home/jenkins/workspace/Android-ARM/tools/depends/xbmc-depends/arm-linux-androideabi-21-release/lib/python2.7/SocketServer.py", line 652, in init
15:56:07.666 T:18446744071939800064   ERROR:   File "/home/jenkins/workspace/Android-ARM/tools/depends/xbmc-depends/arm-linux-androideabi-21-release/lib/python2.7/BaseHTTPServer.py", line 340, in handle
15:56:07.667 T:18446744071939800064   ERROR:   File "/home/jenkins/workspace/Android-ARM/tools/depends/xbmc-depends/arm-linux-androideabi-21-release/lib/python2.7/BaseHTTPServer.py", line 328, in handle_one_request
15:56:07.668 T:18446744071939800064   ERROR:   File "/mnt/sdcard/Android/data/org.xbmc.kodi/files/.kodi/addons/plugin.video.netflix/resources/lib/MSLHttpRequestHandler.py", line 67, in do_GET
15:56:07.673 T:18446744071939800064   ERROR:     dolby, hevc, hdr, dolbyvision)
15:56:07.674 T:18446744071939800064   ERROR:   File "/mnt/sdcard/Android/data/org.xbmc.kodi/files/.kodi/addons/plugin.video.netflix/resources/lib/MSL.py", line 186, in load_manifest
15:56:07.681 T:18446744071939800064   ERROR:     request_data = self.__generate_msl_request_data(manifest_request_data)
15:56:07.681 T:18446744071939800064   ERROR:   File "/mnt/sdcard/Android/data/org.xbmc.kodi/files/.kodi/addons/plugin.video.netflix/resources/lib/MSL.py", line 490, in __generate_msl_request_data
15:56:07.682 T:18446744071939800064   ERROR:     plaintext=self.__generate_msl_header())
15:56:07.683 T:18446744071939800064   ERROR:   File "/mnt/sdcard/Android/data/org.xbmc.kodi/files/.kodi/addons/plugin.video.netflix/resources/lib/MSL.py", line 583, in __encrypt
15:56:07.685 T:18446744071939800064   ERROR:     return json.dumps(self.crypto.encrypt(plaintext, self.nx_common.get_esn(), self.sequence_number))
15:56:07.685 T:18446744071939800064   ERROR: AttributeError: 'MSL' object has no attribute 'sequence_number'
15:56:07.687 T:18446744071938137088   ERROR: CCurlFile::FillBuffer - Failed: Server returned nothing (no headers, no data)(52)
15:56:07.687 T:18446744071938137088   ERROR: CCurlFile::Open failed with code 0 for http://localhost:55150/manifest?id=80094662&dolby=true&hevc=false&hdr=false&dolbyvision=false:
15:56:07.688 T:18446744071938137088   ERROR: AddOnLog: InputStream Adaptive: Cannot download http://localhost:55150/manifest?id=80094662&dolby=true&hevc=false&hdr=false&dolbyvision=false
15:56:07.689 T:18446744071938137088   ERROR: AddOnLog: InputStream Adaptive: Could not open / parse mpdURL (http://localhost:55150/manifest?id=80094662&dolby=true&hevc=false&hdr=false&dolbyvision=false)
15:56:07.700 T:18446744071938137088   ERROR: CVideoPlayer::OpenInputStream - error opening [plugin://plugin.video.netflix/?action=play_video&infoLabels=%7B%27rating%27%3A+0%2C+%27season%27%3A+None%2C+%27tvshowtitle%27%3A+%27%27%2C+%27mediatype%27%3A+%27movie%27%2C+%27director%27%3A+u%27James+DeMonaco%27%2C+%27duration%27%3A+6548%2C+%27year%27%3A+2016%2C+%27genre%27%3A+u%22Thriller+d%27azione%22%2C+%27plot%27%3A+u%27Invoca+che+il+caos+possa+terminare%2C+ma+per+vedere+un+futuro+senza+terrore%2C+dovr%5Cxe0+superare+la+notte.%27%2C+%27episode%27%3A+%27%27%2C+%27title%27%3A+u%27La+Notte+del+giudizio%3A+Election+Year%27%2C+%27mpaa%27%3A+%27MiBAC-VM14%27%2C+%27writer%27%3A+%27%27%2C+%27cast%27%3A+%5Bu%27Elizabeth+Mitchell%27%2C+u%27Mykelti+Williamson%27%2C+u%27Frank+Grillo%27%2C+u%27Edwin+Hodge%27%2C+u%27Betty+Gabriel%27%2C+u%27Joseph+Julian+Soria%27%2C+u%27Kyle+Secor%27%2C+u%27Terry+Serpico%27%5D%7D&video_id=80094662&pin=True]
15:56:07.701 T:18446744071938137088  NOTICE: CVideoPlayer::OnExit()
15:56:21.019 T:18446744072378998912  NOTICE: Trying to open: samplerate: 44100, channelMask: 12, encoding: 4
15:56:21.028 T:18446744072378998912  NOTICE: CAESinkAUDIOTRACK::Initializing with: m_sampleRate: 44100 format: AE_FMT_FLOAT (AE) method: PCM stream-type: PCM-STREAM min_buffer_size: 120416 m_frames: 7526 m_frameSize: 8 channels: 2
15:56:30.139 T:18446744072386573056  NOTICE: stop player
15:56:30.178 T:18446744072386573056  NOTICE: CVideoPlayer::CloseFile()
15:56:30.178 T:18446744072386573056  NOTICE: VideoPlayer: waiting for threads to exit
15:56:30.179 T:18446744072386573056  NOTICE: VideoPlayer: finished waiting
15:56:30.179 T:18446744072386573056  NOTICE: CVideoPlayer::CloseFile()
15:56:30.179 T:18446744072386573056  NOTICE: VideoPlayer: waiting for threads to exit
15:56:30.179 T:18446744072386573056  NOTICE: VideoPlayer: finished waiting
[Please include a link to your debug log (use something like http://sprunge.us/) or similar, please do not paste]
Other information
[e.g. detailed explanation, related issues, suggestions how to fix, links for us to have context, etc.]
Screenshots
[Please add a screenshot if that helps understanding your problem]
[You can erase any parts of this template not applicable to your Issue.]

Having the exact same issue on atvXperience (Android TV 7)
When selecting a video it just loads a bit and then it stops, giving the same errors as provided above

Fixed in current PR for 0.14.0: #519
Keeping this open until the PR gets merged.

Make sure the HEVC are on for android


[BUG]  gradient reduction issues when running training script with latest released model 2-6

是否已有关于该错误的issue或讨论？ | Is there an existing issue / discussion for this?

[X] 我已经搜索过已有的issues和讨论 | I have searched the existing issues / discussions

该问题是否在FAQ中有解答？ | Is there an existing answer for this in FAQ?

[X] 我已经搜索过FAQ | I have searched FAQ

当前行为 | Current Behavior
Excellent work! I am attempting to run a training script using ZeRO Stage 2/3 optimization. However, I have encountered the following issues:
miniconda3/envs/MiniCPM-V/lib/python3.10/site-packages/deepspeed/runtime/zero/stage_1_and_2.py", line 939, in reduce_independent_p_g_buckets_and_remove_grads
assert self.params_already_reduced[param_id] == False,
AssertionError: The parameter 657 has already been reduced.             Gradient computed twice for this partition.             Multiple gradient reduction is currently not supported
Traceback (most recent call last):
I'm using a conda env config provided by the doc. Is there any fix to this issue? Thanks in advance!
期望行为 | Expected Behavior
successfully launch training script with zero 2/3
复现方法 | Steps To Reproduce
No response
运行环境 | Environment
- OS: ubuntu 20
- Python: 3.10
- Transformers: as required by doc
- PyTorch:as required by doc
- CUDA (`python -c 'import torch; print(torch.version.cuda)'`): 12.1

备注 | Anything else?
No response

I'm having the same issue on Python 3.10, CUDA 12.1 and Torch 2.3.1. If I train without Zero 2/3 the issue goes away but this limits me to training only on A100 GPUs which is not very convenient.

I have the same question

I have the same question when setting --per_device_train_batch_size greater than 1.

I have the same question when setting --per_device_train_batch_size greater than 1.

Address by setting use_reentrant=False

training_args.gradient_checkpointing_kwargs = {
        "use_reentrant": False
}
trainer = CPMTrainer(
      model=model,
      tokenizer=tokenizer,
      args=training_args,
      **data_module,
 )

training_args.gradient_checkpointing_kwargs = {
        "use_reentrant": False
}

I did it but get this error
Traceback (most recent call last):
File "/workspace/MiniCPM-V/finetune/finetune.py", line 300, in
train()
File "/workspace/MiniCPM-V/finetune/finetune.py", line 176, in train
) = parser.parse_args_into_dataclasses()
File "/opt/conda/lib/python3.10/site-packages/transformers/hf_argparser.py", line 348, in parse_args_into_dataclasses
raise ValueError(f"Some specified arguments are not used by the HfArgumentParser: {remaining_args}")
ValueError: Some specified arguments are not used by the HfArgumentParser: ['--use_reentrant', 'true']

I have the same question when setting --per_device_train_batch_size greater than 1.

Address by setting use_reentrant=False
training_args.gradient_checkpointing_kwargs = {
        "use_reentrant": False
}
trainer = CPMTrainer(
      model=model,
      tokenizer=tokenizer,
      args=training_args,
      **data_module,
 )

Thanks it works


fix(useLayoutEffect) : useIsomorphicLayoutEffect to declutter Server Logs

When useLayoutEffect runs on server (during server rendered apps), we get multiple repetitive warnings for eg:

We can prevent this by introducing useIsomorphicLayoutEffect which only runs useLayoutEffect when on client and falls back to useEffect when run on server
Thanks !!

Hi @yoyo837 @zombieJ @xrkffgg @vagusX @jueinin @jsomariano , kindly review the PR. We're using this in production, will be grateful if we can have this fix in.
Thanks 😄

How about adding it to https://github.com/react-component/util ?

How about adding it to https://github.com/react-component/util ?

Thanks for the awesome suggestion @yoyo837 , turns out rc-util already has what we need https://github.com/react-component/util/blob/master/src/hooks/useLayoutEffect.ts, hence updated the code to use just that 😉
Cheers !!


Dev Test: Geometric Optics: Basics 1.3.0-dev.1

Dev Test
Mentions: @arouinfar @kathy-phet @KatieWoe
Simulation links

github repository for issues
phet top-level directory
sim: all_phet.html
phet-io wrapper index

Test Matrix
Please include all (non-screen reader) feature testing in these records if applicable.

[x] Latest macOS, Safari (Time =.75 )
[ ] Windows 10, Chrome (Time = )
[] Windows 10/11, Firefox (Time = )
[ ] Latest iOS, Safari (Time = )
[x] Windows 11, Chrome (Time = .5)

Light testing, or optionally skip if time crunch:

[ ] Latest macOS, Chrome (Time = )
[ ] Latest Chrome OS, Chrome (Time = )

If PhET-iO is being tested:

[x] Latest macOS, Safari (Time =1.75)
[ ] Windows 10, Chrome (Time = )
[x] Windows 10, Firefox (Time = .75)
[x] Latest iOS, Safari (Time =.75)
[x] Windows 11, Chrome (Time = .75)

Features included

[x] PhET-iO
[x] Alternative Input
[x] UI Sound

[ ] Sonification
[ ] Description
[ ] Voicing

Focus and Special Instructions
This dev test should be done with https://github.com/phetsims/qa/issues/938 (Dev Test: Geometric Optics 1.3.0-dev.1).
It is not necessary to do a complete test for Geometric Optics: Basics.  It is sufficient to test the differences, which are described in model.md and implementation-notes.md.
Note that the PhET-iO Wrapper Index currently does not contain the "Examples" link, because examples.md was not completed yet. You can skip it for now, and we'll review it in the next test cycle.
Note that the Wrapper Index has this known problem: https://github.com/phetsims/phet-io-wrappers/issues/497

For QA...

General features

What to Test

Click every single button.
If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Try to include browser version numbers
If there is a console available, check for errors and include them in the Problem Description.
Run through the string tests on at least one platform, especially if it is about to go to rc.
Check the Game Up harness on one platform.

PhET-iO features

What to Test

Make sure that public files do not have password protection. Use a private browser for this.
Make sure that private files do have password protection. Use a private browser for this.
Make sure standalone sim is working properly.
Make sure the wrapper index is working properly.
Make sure each wrapper is working properly.
Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
sure the simulation loads without crashing or throwing errors.

Accessibility features

What to Test

Specific instructions can be found above.

Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is
a list of features that may be supported in this test:

Alternative Input
Interactive Description
Sound and Sonification
Pan and Zoom
Mobile Description
Voicing

Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).
Test all forms of input with a screen reader (if applicable).

Screen Readers
This sim may support screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have all of the information
you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening
the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Platforms and Screen Readers to Be Tested

Windows 10 + Latest Chrome + Latest JAWS
Windows 10 + Latest Firefox + Latest NVDA
macOS + Safari + VoiceOver
iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information
We are tracking known screen reader bugs in
here. If you find a
screen reader bug, please check it against this list.

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.
Magnification
This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel controls. Please test magnfication and make sure
it is working as intended and well with the use cases of the simulation. Due to the way screen readers handle user input, magnification is NOT expected to
work while using a screen reader so there is no need to test this case.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

QA, please review examples.md on master when testing this sim:
https://github.com/phetsims/phet-io-sim-specific/blob/master/repos/geometric-optics-basics/examples.md

Calling QA here

Thanks QA team.  We're in good shape here -- 1 issue reopened, 3 PhET-iO issues to address.
Closing.


Allow to upload per-case gene annotation (#575)

Closes: #575
Related-Issue: #575
Projected-Results-Impact: none

Codecov Report
Base: 86.05% // Head: 92.59% // Increases project coverage by +6.54% :tada:

Coverage data is based on head (8176d31) compared to base (5f5970b).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #727      +/-   ##
==========================================
+ Coverage   86.05%   92.59%   +6.54%
==========================================
  Files         157       17     -140
  Lines       19024     4621   -14403
  Branches      399      399
==========================================
- Hits        16371     4279   -12092
+ Misses       2653      342    -2311

Flag
Coverage Δ

javascript
92.59% <ø> (ø)

python
?

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

Impacted Files
Coverage Δ

regmaps/admin.py

genepanels/apps.py

beaconsite/forms.py

variants/submit_filter.py

templatetags/templatetags/json.py

varfish/users/apps.py

config/celery.py

variants/views_ajax.py

svdbs/models.py

variants/serializers.py

... and 130 more

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.


whitespace minification breaks build

What version of Elysia is running?
v1.1.16
What platform is your computer?
Microsoft Windows NT 10.0.22631.0 x64
What steps can reproduce the bug?
Run bun build --minify-whitespace --target=bun --outfile=../dist/server index.ts on my project.
What is the expected behavior?
It shouldn't break.
What do you see instead?
{
  "type": "validation",
  "on": "response",
  "summary": "Property 'totalTime' is missing",
  "property": "/totalTime",
  "message": "Required property",
  "expected": {
    "totalTime": []
  },
  "found": {},
  "errors": [
    {
      "type": 45,
      "schema": {
        "type": "array",
        "items": {
          "type": "integer"
        }
      },
      "path": "/totalTime",
      "message": "Required property",
      "summary": "Property 'totalTime' is missing"
    },
    {
      "summary": "Expected array",
      "type": 6,
      "schema": {
        "type": "array",
        "items": {
          "type": "integer"
        }
      },
      "path": "/totalTime",
      "message": "Expected array"
    }
  ]
}

Additional information
No response
Have you try removing the node_modules and bun.lockb and try again yet?
No response

#724 still happening


Punctuation issue with CJK characters, only in web app

Description
Hi, this Typst code snippet
// C
汉皇重色思倾国，御宇多年求不得。杨家有女初长成，养在深闺人未识。\
天生丽质难自弃，一朝选在君王侧。回眸一笑百媚生，六宫粉黛无颜色。

// J
日本語の音韻は、「っ」「ん」を除いて母音で終わる開音節言語の性格 \
が強く、また標準語を含め多くの方言がモーラを持つ。

// K
(The Korean punctuations are rendered okay, because it uses European punctuations.)
대한항공은 대한민국 국적의 항공사이며, 항공 동맹체인 스카이팀의 창립 항공사로 인천국제공항과 김포국제공항을 허브 공항으로 두고 있다.

was rendered correctly in PDF locally, with the Typst CLI:

but the web app rendered the punctuations differently. Specifically, they are put at the middle of the character boxes, instead of at the corner:

I'm not sure this is a font issue, though -- you may notice the glyph's fonts are different in the local PDF vs the web app (for example,  vs ). The PDF version is generally more common in modern usage.
Maybe @peng1999 has some insights, but this issue only manifests on the web app so maintainers's involvement might be necessary.
Reproduction URL
https://typst.app/project/rFk7tfTxRTj_lwChTsvuV7
Browsers
Chrome
OS
macOS

(Sorry, I didn't mean to assign to reknih@ but it appears GitHub automatically does that)

(Sorry, I didn't mean to put reknih@ on the spot but it appears GitHub automatically assigns this issue)

That intentionally happens on any issue with the web app lavel.

This is font issue. The default CJK fallback font in web app is TW or HK variant of Noto CJK. You should select CN and JP font variant respectively in you document to get right glyphs.

Nice, thx. Probably a question to maintainers: wondering whether this is intentional to have different default fonts in the local PDF vs the web app? That seems a bit surprising to users.

A simple idea is to add a language and region option in template wizard. Then a single #set text(lang: "zh") will fix this issue without touching font fallback machanism.

The default fonts are the same. Here, it's that font fallback happens (which picks any suitable font from all that are available). And the set of available fonts differs in the web app and your local operating system (because we use your system fonts instead of downloading our own 2GB of fonts).


Huge header (in logseq 0.5.8)

Wrong value for --ct-header-height,
For me, the header is huge, the offending setting seems to be
 --ct-header-height: 50px;

However, the computed height of the selected element is 120px :open_mouth:

Could you please confirm if this issue is still present in the latest Logsq release. Also, it would be helpful if you could share the setup and the steps to reproduce the issue.

Seems to work fine now.

Thanks for getting back to me so quickly! I really appreciate your help. I think we can close this issue now.


replace random with secrets; closes iss#5

As far as I could tell, the try/except wasn't doing anything beneficial, so I simplified by removing it.
Regarding the full replacement, it's what's recommended by the random library itself:

The pseudo-random generators of this module should not be used for security purposes. For security or cryptographic uses, see the secrets module.

[ ] All tests pass successfully
[ ] Running from Python returns random passwords

Great point, thanks. I'll have some time to check 2.7 and 3.5 early next week, hopefully and work to make sure it's non-breaking. You're welcome to do updates before as well, of course.


[Feature Request] Tabs for running multiple commands in background

My use case is that I want to use aria2 or wget to download something in background.  Perhaps if the commands that you run could be placed in its own tab (with an indicator if the command is still running or completed), that would allow for multiple commands to be run at the same time and cancelled if the user wishes to do so.

Hey @jivank! Thanks for the suggestion. I think that the command's feature should be redesigned in a more deep manner. Any suggestions? Do you think it should be separated from the Search?

I think having tabs for commands would be a simple way to have a decent experience of adding functionality to this application. It appears you can already run multiple tasks in the background, but you can only see the progress of the last command.
The only idea I had in mind for a more advanced command system is a plugin system (for each whitelisted command like git, wget, aria2) that offers a seamless web interface for each command. Or the custom button functionality that can be tied to a command (as seen on one of the other tickets).

I'm closing this since this repository will be archived. Please read the information on the README for more information. Thanks for all your contributions!


asitop_powermetrics occupying 20gbs in SSD

Hi there,
Been using asitop for a few months, but in the last couple of weeks the asitop_powermetrics file located in private>temp was using a lot of space. I uninstalled asitop and deleted the file but I fear the same thing will happen again soon. Do you guys know what could be causing it and how to avoid my ssd being eaten by this temp file?

Sorry about that, the temp file is supposed to be purged on every startup and exit. If that doesn’t work, you can manually delete the file.


dotnet restore giving: The repository primary signature validity period has expired

Description

Configuration

Regression?

Other information

Sounds like https://github.com/NuGet/Home/issues/10712
What OS and .NET version are you using?

Duplicate of #6595


Corrected ill-placed blank lines

The blank line creation  was misplaced in the scorer preventing the scorer result to be shown (only blank lines were shown). Now the scorer losses are displayed and then the two blank lines are added.

Corrected misplaced blank lines in scorer.

looks like auto-formatting made a wrong indentation again, thank you!


  I am working on a fix now for the TF end of things

Linting added to pipeline and updated to fix all tests from other PRs. Just needs that comment update and we can merge this.

 Cheers, its now a standard in the testing workflow.


moved sending mentions to job

refs TryGhost/Team#2523
-implemented jobsService within mention sending service
-updated tests so we don't need to sleep

@allouis added you as reviewer. I don't love implementing the jobsService within the webmentions package but I'm not seeing another option... It makes the tests a bit awkward as-is.
Also with respect to the webmentions package unit tests, I was torn between the current implementation and moving the job to within sendAll (right where we're sending for each link). Not sure if you've got some thoughts there.


Wrong position of dragged sprite when parent has non default scale.

Godot version:
3.1 aeddb30
OS/device including version:
Windows 10
Issue description:
When I drag & drop a sprite to main viewport, when parent of pasting sprite has scale different than (1,1), then pasted sprite has strange position.
Steps to reproduce:
https://streamable.com/fpzge

CC @groud


CI: Schedule for branch docker doesn't work

Seems like the feature doesn't even exist: https://github.com/orgs/community/discussions/16107
Keeping this issue open until maybe GitHub implements something we can use.

Possible solution:

Rename main branch to gh-pages and remove the empty pages branch
Merge docker and gh-pages workflows and move them into a new main branch

This way, main's sole purpose would be to schedule GitHub workflows. It would need to git checkout the respective branch on a given schedule step.


Add alternative message for reserved keyword and update invalid_criterion error definition

Summary Key Points

Add an alternative message for invalid_sort and invalid_filter errors to handle reserved keywords.
invalid_criterion is renamed to invalid_ranking_rule and add an alternative message to handle reserved keywords.

Pinging @guimachiavelli for information sharing.

Following our discussion this is the new error message when the indexing part fails on a bad geo field:
{
    "message": "
  "meta": "error while processing update content: the document with the id: :docid contains an invalid _geo field: :geo_field.",
    "code": "invalid_geo_field",
    "type": "invalid_request",
    "link": "https://docs.meilisearch.com/errors#invalid_geo_field"
}


Add docker support for running the MIDS Calculator

The image has all the R packages necessary installed and then the container just launches the shiny app through the new dockerApp.R script.
To use:
# build the container (run from the repo root)
docker build -t midscalculator .

# run the container
docker run -p 3000:3000 midscalculator

Thanks! I missed this one as I don't get notifications for some reason. I'll give it a go once I'm back home and have easy access to a Linux machine again. My experiences with wsl2 and docker are not very great.


Update template to make it stable ingress api pathType is mandatory

Now in stable ingress api  pathType is mandatory
since
Kubernetes v1.19 [stable]
I think we must delete the old API capacibility
i cannot install in k3s
because of this error when i enable ingress
spec.rules[0].http.paths[0].pathType: Required value: pathType must be specified
we must maybe add some test and propose to leantime to help to maintain the helm chart ?
Thanks again im searking for tdah task tools because you know how life is hard ^

Here my ingress i had manual in rancher
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: leantime
  namespace: leantime
spec:
  ingressClassName: traefik
  rules:
    - host: leantime.XXXXX
      http:
        paths:
          - backend:
              service:
                name: leantime
                port:
                  number: 80
            path: /
            pathType: Prefix
  tls:
    - hosts:
        - leantime.yodatak.fr

i got wildcard tsl altready

Thanks for that. Ingress at networking.k8s.io/v1beta1 was removed on 1.22, almost 2 years ago. It is safe to remove support for it now. I'll update that and Vaultwarden in the coming days. For reporting the issue and the proposed patch.

Thanks for the PR, there are some additional changes required, I'll push them soon.


What's the status of this project?

With background updates not working (https://github.com/austrianredcross/stopp-corona-ios/issues/107) this app is essentially useless, and I do not see any activity/commits since July 9, which is 5 weeks.
Why is Austria pushing advertisements for an app that seems abandoned and doesn't work as advertised?
Is there a process to help? Could we instead just switch to the german app which is maintained and works?

Is there a process to help?

Generally sending pull requests is possible, I can merge them. That said it's quite tricky to work on and I haven't had much success in getting people to contribute.
As to why the background fetch is unreliable my understanding is that the logic for BatchDownloadScheduler.Timing is not sound and eventually it stops working.

Could we instead just switch to the german app which is maintained and works?

This is a question I cannot answer.

Thank you! Is there a process to see who's an official member of this project and who comments from the community?

the logic for BatchDownloadScheduler.Timing is not sound and eventually it stops working.

Is there anyone working on a fix? I don't see any meaningful commits since July 9.

At the moment there is no active development. As in official members I’m not sure who monitors this issue tracker other than me and @uluckas from accenture.

the logic for BatchDownloadScheduler.Timing is not sound and eventually it stops working.

does this problem only happen on iOS or on android too?
(i've the suspicion there are similar problems on android, because i'm only now seeing one check entry just as i opened the app and the last check entry before now was from 1.10, which feels highly suspicious)

I think this issue can be closed now? 😅


Fixed failing tests in test_common_utils and test_algorithms

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Motivation and Context / Related issue
Two tests were failing:

FAILED tests/core/test_common_utils.py::test_create_one_dim_tr_model - omegaconf.errors.ConfigAttributeError: Missing key target_is_delta
FAILED tests/algorithms/test_algorithms.py::test_mbpo - omegaconf.errors.ConfigAttributeError: Missing key save_video

How Has This Been Tested (if it applies)
python -m pytest tests/core and python -m pytest tests/algorithms
Checklist

[x] The documentation is up-to-date with the changes I made.
[x] I have read the CONTRIBUTING document and completed the CLA (see CONTRIBUTING).
[ ] All tests passed, and additional code has been covered with new tests.

I didn't run MuJoCo tests.

@kajetanj Can you also manually add the changes in this PR, which fix CI tests for this one? (and that one doesn't pass due to the errors you are fixing here)


Fix for generating form ids

Fixes NewSpring/my.newspring.cc#104

@johnthepink is that the right issue?

@jbaxleyiii yea it is. It doesn't make the fix, but the form ID is used in the fix.

@johnthepink gotcha! Thanks for the clarity! Also, pokemon gifs all day today (sorry not sorry)

@jbaxleyiii oh I'm not sorry

@johnthepink you get me


Huawei apks

Hi!
Huawei apks have errors and we can´t decompile it.
It is possibel to insert a decompile/compile ignore option?
Like this we can tweak it and then compile it.
Thanks.
.

Huawei isn't supported due to qualifier changes. Sorry. This however, does not look like a qualifier problem, but I need applications and logs in text.
A screenshot of a log simply isn't enough for me to do anything. If you can attach an apk we can revisit this.

Hi!
This is the Huawei apk that i was trying to decompile.
https://mega.nz/#!9xBU3Z4D!RDi8esxQGA19V26h4szKF-GISWT1mhBYOKicczcEh54
People say that Huawei insert error to avoid decompiling ( i don´t know if is true... )
Thanks

Downloaded. Will check and update ticket. Might need framework files - not sure yet.

Hi!
This is framework:
https://mega.nz/#!41ozxAAL!bqtfZUKAhcdduu07NzTbJNtg6KDlgREfvKOfM-j_peY

This apk has 3 DEFAULT configurations. Usually this is fine because those DEFAULTS are spread among various types or packages.
In this situation in Type 1, we have two DEFAULT configurations which causes duplicate resources. I tweaked apktool to log the qualifier name and then the remaining bytes (Usually the 4 bytes from 52 -> 56 in ResConfigHeader)
➜  Bug1521 apktool debug if framework-res-hwext.apk -t 1521
Listening for transport dt_socket at address: 5005
Remaining: 0x0
0-[DEFAULT]
Remaining: 0x0
1-[DEFAULT]
Remaining: 0x9C00
1-[DEFAULT]
W: Duplicate Resource Detected. Ignoring duplicate: string/wifi_switch_to_pdp_title

So whats happening is we are decoding type 0, default configuration then type 1 default configuration, then another type 1 default configuration. When in fact we can see from the output that is an additional 2 bytes 0x9C of data. This is unknown. We don't know how to translate this to qualifiers, thus errors out.
This is not AOSP, we don't have source to examine and discover the meaning of this extra data. Not to mention this extra 4 bytes purpose was never discovered - https://github.com/iBotPeaches/Apktool/commit/67d80a133fd96bbf992db359725d8909e585f628
Perhaps its not Huawei specific, but only Huawei apks are failing with this error. So maybe they re-used this unknown 4 bytes of data for their own purpose.

So, there is no way to decompile Huawei apks? There are few that works fine...
Hmmmm...
.

Correct. No support for Huawei as of now.

Not sure if it is related but on Huawei mediapad t3 I was successful with decompiling the apk, however, after making minor changes in smali I was unnable to launch the recompiled app (resigned etc.). Even after  decompiling without touching resource files still got an Resources$NotFoundException error.

This is part of roadmap for plugin system since Huawei is reusing qualifiers for something else.
(Maybe not 3+ years later)
but have to clean up tracker - https://github.com/iBotPeaches/Apktool/blob/master/ROADMAP.md#qualifier-plugin-system
Closing.


[IntelliJ Plugin] Update plugin grammar

Purpose
This PR updates ballerina IntelliJ plugin grammar related to,

channels
workers
function definitions

Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[x] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #18412 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #18412   +/-   ##
=======================================
  Coverage   14.82%   14.82%
=======================================
  Files          48       48
  Lines        1268     1268
  Branches      201      201
=======================================
  Hits          188      188
  Misses       1066     1066
  Partials       14       14

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 21f9a53...b40bfda. Read the comment docs.


Properly detect emoticons

#4
it 'preserves emoticons' do
  text = "lol :-D"
  pt = PragmaticTokenizer::Tokenizer.new(text, downcase: false)
  expect(pt.tokenize).to eq(
    ["lol", ":-D"]
  )
end

I've just came across retext-emoji and wonder if it might be smart to convert emoticons to emoji:

When encode, converts short-codes into their unicode equivalent (e.g., :heart: and <3 to ❤)

While I think it might be too much ton attempt to convert all possible emoticons, one could pragmatically do so for the 10-20 most common emoticons very early in the processing, and only later handle remaining punctuation.

Interesting idea. It might be something to consider doing internally so we don't confuse emoticons with other punctuation...however, in the output that is returned to a user I am kind of a purist and think that it should match the original input (i.e. <3 in the input text would not return ❤ as a token)


docs: update docs to include budgets

Fixes #N/A
Description
Adds documentation for budgets
How was this change tested?
make website
Does this change impact docs?

[x] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 82.525%

Files with Coverage Reduction
New Missed Lines
%

pkg/providers/amifamily/ami.go
1
90.32%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
4949

Relevant Lines:
5997

💛  - Coveralls


Actually include image element in onImageLoaded

I don't know why this was missing, this logic exists in
lib/ReactCrop.jsx but it was not in dist/ReactCrop.

Thanks Eli, I should avoid releasing when sick! Another reason to automate
the build, thanks I'll get this released ASAP later
On Friday, 26 February 2016, Eli Ribble<EMAIL_ADDRESS>wrote:

I don't know why this was missing, this logic exists in
lib/ReactCrop.jsx but it was not in dist/ReactCrop.
You can view, comment on, or merge this pull request online at:
https://github.com/DominicTobias/react-image-crop/pull/23
Commit Summary

Actually include image element in onImageLoaded

File Changes

M dist/ReactCrop.js
https://github.com/DominicTobias/react-image-crop/pull/23/files#diff-0
(3)

Patch Links:

https://github.com/DominicTobias/react-image-crop/pull/23.patch
https://github.com/DominicTobias/react-image-crop/pull/23.diff

—
Reply to this email directly or view it on GitHub
https://github.com/DominicTobias/react-image-crop/pull/23.

Now built as 0.1.4 and ensured it won't happen again

Thanks for the quick turnaround


Tech debt

@kbertodatti @savanahmueller
Some notes:
The most major tech debt is in the code itself.
1 I'm sure everyone can think of something, but, the most important one to me is the duplication of logic for single and multi providers when logging in on app launch vs logging in from the additional page. This shared code needs to be merged into single reusable functions which offer the differing  but similarfunctionality, but don't require extensive simultaneous updates every time and testing. It is a complex task that I should take on.
2 In addition, and aligned, would be to separate the concerns in componentDidMount. The current state is messy. This is a general trend in the app that makes it hard to maintain (not enough separation of concerns due to time contraints in implementation).
3 Home.tsx should also be converted to a function component. There are others, but App.tsx and Home.tsx are the most vital because they are more the roots of the app. Small class based components elsewhere are not an issue. Althought, we shouldn't be creating new ones.
4 + 5 We need to resolve all of these compile-time and runtime warnings that are cluttering up the build console and dev console. Not only can they have side effects, but, they also make it hard to notice serious issues. This should be 2 separate tickets (if not more, for individual issues, if needed).
6 Once resolved, we should implement a process where one cannot commit with such bugs via an automatic tool.
I suggest we create tickets for all of these. Note: App.tsx -> function component is already created. I suggested we consider tech debt originally and those are the top issues IMO. Addressing the ones above allows us to work on the project more seamlessly/faster, makes it more maintainable, and not need to test as much/have less chances for bugs.
From there, the order of priority IMO is:
react 18
node js
common style config
I'm not sure about the Null Flavor ticket so not sure where to place it. Is that really tech debt? I don't have an understanding of the req.


[BUG] Rancher crashes and restarts

Rancher Server Setup

Rancher version: 2.6-head commit 4206f57
Installation option (Docker install/Helm Chart): Helm

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): GKE - v1.23.8-gke.1900

Information about the Cluster

Kubernetes version: GKE Hosted downstream - v1.23.9-gke.2100

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom) admin

Describe the bug
[BUG] Rancher crashes and restarts
To Reproduce

Deployed Rancher on GKE cluster
Deployed a downstream GKE hosted cluster.
Automation tests were running on the downtsream cluster, and seems like 3 pods of rancher crashed for different reasons.
Rancher pods 1

2022/09/19 18:08:59 [INFO] Starting management.cattle.io/v3, Kind=RoleTemplate controller
--
Mon, Sep 19 2022 11:08:59 am | E0919 18:08:59.757287 33 leaderelection.go:334] error initially creating leader election record: leases.coordination.k8s.io "cattle-controllers" already exists
Mon, Sep 19 2022 11:08:59 am | 2022/09/19 18:08:59 [INFO] Starting management.cattle.io/v3, Kind=Group controller
Mon, Sep 19 2022 11:08:59 am | 2022/09/19 18:08:59 [INFO] Starting management.cattle.io/v3, Kind=Cluster controller
Mon, Sep 19 2022 11:08:59 am | 2022/09/19 18:08:59 [INFO] Starting management.cattle.io/v3, Kind=User controller
Mon, Sep 19 2022 11:08:59 am | 2022/09/19 18:08:59 [INFO] Starting management.cattle.io/v3, Kind=Token controller
Mon, Sep 19 2022 11:08:59 am | 2022/09/19 18:08:59 [INFO] Starting management.cattle.io/v3, Kind=UserAttribute controller
Mon, Sep 19 2022 11:08:59 am | 2022/09/19 18:08:59 [INFO] Starting /v1, Kind=Secret controller
Mon, Sep 19 2022 11:08:59 am | 2022/09/19 18:08:59 [INFO] Starting management.cattle.io/v3, Kind=GroupMember controller
Mon, Sep 19 2022 11:08:59 am | 2022/09/19 18:08:59 [INFO] Waiting for initial data to be populated
Mon, Sep 19 2022 11:09:02 am | 2022/09/19 18:09:02 [INFO] Waiting for initial data to be populated
Mon, Sep 19 2022 11:09:04 am | 2022/09/19 18:09:04 [INFO] Waiting for initial data to be populated
Mon, Sep 19 2022 11:09:06 am | 2022/09/19 18:09:06 [INFO] Waiting for initial data to be populated
Mon, Sep 19 2022 11:09:09 am | 2022/09/19 18:09:09 [INFO] generated self-signed CA certificate CN=dynamiclistener-ca@1663610949,O=dynamiclistener-org: notBefore=2022-09-19 18:09:09.203214421 +0000 UTC notAfter=2032-09-16 18:09:09.203214421 +0000 UTC
Mon, Sep 19 2022 11:09:09 am | 2022/09/19 18:09:09 [FATAL] failed to setup TLS listener: secrets "tls-rancher" already exists

Rancher pod 2

2022/09/19 18:50:26 [INFO] cluster [c-bwhh5] matches upstream, skipping spec sync
2022/09/19 18:55:26 [INFO] checking cluster [c-bwhh5] upstream state for changes
2022/09/19 18:55:26 [INFO] updating cluster [c-bwhh5], upstream change detected
2022/09/19 18:55:26 [INFO] cluster [c-bwhh5] matches upstream, skipping spec sync
E0919 18:58:15.851646 33 leaderelection.go:330] error retrieving resource lock kube-system/cattle-controllers: Get "https://<IP_ADDRESS>:443/api/v1/namespaces/kube-system/configmaps/cattle-controllers?timeout=15m0s": context deadline exceeded
I0919 18:58:15.851729 33 leaderelection.go:283] failed to renew lease kube-system/cattle-controllers: timed out waiting for the condition
2022/09/19 18:58:15 [FATAL] leaderelection lost for cattle-controllers
E0919 18:58:15.851860 33 leaderelection.go:306] Failed to release lock: resource name may not be empty

Rancher Pod 3

2022/09/19 18:09:06 [INFO] Waiting for initial data to be populated
--
Mon, Sep 19 2022 11:09:09 am | 2022/09/19 18:09:09 [INFO] Listening on :443
Mon, Sep 19 2022 11:09:09 am | 2022/09/19 18:09:09 [INFO] Listening on :80
Mon, Sep 19 2022 11:09:09 am | 2022/09/19 18:09:09 [INFO] certificate CN=dynamic,O=dynamic signed by CN=dynamiclistener-ca@1663610949,O=dynamiclistener-org: notBefore=2022-09-19 18:09:09 +0000 UTC notAfter=2023-09-19 18:09:09 +0000 UTC
Mon, Sep 19 2022 11:09:09 am | 2022/09/19 18:09:09 [WARNING] dynamiclistener [::]:443: no cached certificate available for preload - deferring certificate load until storage initialization or first client request
Mon, Sep 19 2022 11:09:10 am | 2022/09/19 18:09:10 [INFO] certificate CN=dynamic,O=dynamic signed by CN=dynamiclistener-ca@1663610949,O=dynamiclistener-org: notBefore=2022-09-19 18:09:09 +0000 UTC notAfter=2023-09-19 18:09:10 +0000 UTC
Mon, Sep 19 2022 11:09:10 am | 2022/09/19 18:09:10 [INFO] Updating TLS secret for cattle-system/serving-cert (count: 5): map[listener.cattle.io/cn-<IP_ADDRESS>:<IP_ADDRESS> listener.cattle.io/cn-<IP_ADDRESS>:<IP_ADDRESS> listener.cattle.io/cn-<IP_ADDRESS>:<IP_ADDRESS> listener.cattle.io/cn-localhost:localhost listener.cattle.io/cn-rancher.cattle-system:rancher.cattle-system listener.cattle.io/fingerprint:SHA1=14E29385511456D859BCF54E5A1F5F989561BF19]
Mon, Sep 19 2022 11:09:10 am | 2022/09/19 18:09:10 [INFO] Active TLS secret cattle-system/serving-cert (ver=4636) (count 5): map[listener.cattle.io/cn-<IP_ADDRESS>:<IP_ADDRESS> listener.cattle.io/cn-<IP_ADDRESS>:<IP_ADDRESS> listener.cattle.io/cn-<IP_ADDRESS>:<IP_ADDRESS> listener.cattle.io/cn-localhost:localhost listener.cattle.io/cn-rancher.cattle-system:rancher.cattle-system listener.cattle.io/fingerprint:SHA1=14E29385511456D859BCF54E5A1F5F989561BF19]
Mon, Sep 19 2022 11:09:10 am | 2022/09/19 18:09:10 [INFO] generated self-signed CA certificate CN=dynamiclistener-ca@1663610950,O=dynamiclistener-org: notBefore=2022-09-19 18:09:10.15564301 +0000 UTC notAfter=2032-09-16 18:09:10.15564301 +0000 UTC
Mon, Sep 19 2022 11:09:10 am | 2022/09/19 18:09:10 [FATAL] failed to ListenAndServe for fleet: listen tcp :444: bind: address already in use

/backport v2.6.9


Posture Check Types Endpoint Is Out Of Date

Experienced
GET /posture-check-types returns an incomplete list of types (MFA, Process Multi missing) and there are odd non-semver versions included in the OS versions.
Expected
A proper list of types, versions should be removed as providing a comprehensive list of semver versions for the different OSes will mean nothing.
Reproduction

auth
query GET /posture-check-types

This is still an issue as of 7/3/2024. The types are stored in bbolt instead of a static list from code. It is missing at least the MFA type.


QF-1009: disable offline non-geopackages layers for community accounts

Based on #247 which should be reviewed/merged first.
This implements a limitation preventing to use offline layers that are not geopackages for community accounts.
~WIP : implementation should be there, but struggling with the tests as it seems no matter what I try, the workflows don't want to fail... let's see if this also happens in CI !~
See comment in test_packages.py about this.

Task linked: QF-1009 Disable non GeoPackage layers in COMMUNITY

@suricactus Will stop for today, can you review this if CI passes ? (please don't look at the commit history which is pretty ridiculous in regard of the final changes :-D )