changes to generator tool project to allow it to be installed via dot…

Make it possible to install on the CLI via dotnet install -g .
Before merging - I've got some questions;

seems reasonable to remove the  tag, confirm?  So the .exe is installed as generate_appcast.exe - which would match user expectations better.
should the  be in this change?

Comments welcome - I'm new to this so please excuse any potentially stupid questions.

@johncclayton THANK YOU for doing this and for doing the research in #115.
I went ahead and merged this based on my limited time recently -- didn't want to force everyone to wait another X days for me to have time again, and with your research in #115, I think I knew what to do/what would work.
I'll say more in #115 once I have confirmed that things are working and once I've updated the README.

 I'm very happy to get some help and contributions around here. Thank you! :)


Upload to AppStore - ITMS-90426: Invalid Swift Support

Hello,
I'm encountering an issue while trying to upload to the AppStore.
Previously, I've successfully uploaded the app even with a shared Rust codebase. The main difference this time is that I'm using cargo swift instead of building the .xcframework myself 📦.
After the upload, I received this error:
ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing.
Rebuild your app using the current public (GM) version of Xcode and resubmit it.

I've explored various solutions online to no avail. I'm uncertain if this is related to cargo swift 🤔
Any insights or suggestions would be greatly appreciated! 🙏

That's a tough one. I'll look into it, but no idea so far what is causing this.
Did you build the Swift package with the --release flag? Currently that's necessary.

Thank you for getting back so swiftly, as always 💪.
Using --lib-type static solved the "issue"! 🥳
My apologies, I should've looked into that earlier. It's quite logical now that I think about it.

I'm glad this solved the issue. (This was just a random guess 😅)
Thanks for reporting this, maybe I should deprecate the dylib option entirely (or find out if there is something missing that allows using dylib in App Store)

I must say I'm partial to the dylib option. Given that I manage three separate repositories (iOS, Android, and Shared code), the ability to check in all necessary files is highly beneficial. Working with .a files poses challenges due to their size, especially when dealing with Git. If we could pinpoint what's preventing the use of dylib in the App Store, that would indeed be invaluable. 🙏

Did you have a successful App Store build so far with dylibs?

Let's move this discussion to #36


Spectrum scan range blacklist doesn't hide bar

First of all congrats on the spectrum scan range feature! It is great!
STEPS TO REPRODUCE:
I've noticed though that blacklisting a channel doesn't hide the bar, so essentially the display shows bar above squelch line even though there is no reception and scan continue.
EXPECTED BEHAVIOR:
When blacklist is clicked current bar is hidden/zeroed until it is rescanned again.

You can fix it by adding:
rssiHistory[ScanRangeidx()] = RSSI_MAX_VALUE;
to the Blacklist() function.


Add spec conformance tests for floating-point-literal

Description:
https://ballerina.io/ballerina-spec/spec.html#floating-point-literal

We are closing this issue because it is not being actively worked on. Let's reopen when we resume conformance test efforts.


Add Back Button to 'Make Note' Page in Side Panel

there's no back button on the "Make Note" page in the side panel.


Discussion: how to specify indentation of blocks

In #75 and #125, the inheritance spec was discussed at length. An issue that has been discussed, but undecided, is how it interacts with the notions of standalone tags and indentation.
Setting the stage
Currently, it is specified that when a standalone partial tag is indented, the entire corresponding partial template will be indented by the same amount before rendering and interpolation.
template.mustache
    {{>partial}}

partial.mustache
Hello there!

output
    Hello there!

Try the above example in the playground by pasting the following code:
{"data":{"text":"null"},"templates":[{"name":"template","text":"    {{>partial}}"},{"name":"partial","text":"Hello there!"}]}

A parent tag is essentially a partial tag with a matching closing tag, allowing it to have internal structure.
template.mustache
{{<partial}}{{/partial}}

output
Hello there!

Try the above example in the playground by pasting the following code:
{"data":{"text":"null"},"templates":[{"name":"template","text":"{{<partial}}{{/partial}}"},{"name":"partial","text":"Hello there!"}]}

A block tag essentially enables us to define and expand an embedded partial template inside a larger template. Such a block can be passed to a parent template.
template.mustache
{{<introduction}}{{$title}}Professor{{/title}}{{/introduction}}

introduction.mustache
I'm {{$title}}Darth{{/title}} {{$name}}Vader{{/name}}.

output
I'm Professor Vader.

Try the above example in the playground by pasting the following code:
{"data":{"text":"null"},"templates":[{"name":"template","text":"{{<introduction}}{{$title}}Professor{{/title}}{{/introduction}}"},{"name":"introduction","text":"I'm {{$title}}Darth{{/title}} {{$name}}Vader{{/name}}."}]}

From the recursion spec, it follows that blocks are passed across multiple inheritance levels even when intermediate levels leave the block implicit. While not directly relevant to the current issue, I will be exploiting this in some of my examples, because it enables me to separate the indentation of the parent tag from the indentation of the block tags on both ends.
template.mustache
{{<intermediate}}{{$name}}Moder{{/name}}{{/intermediate}}

intermediate.mustache
{{<introduction}}{{/introduction}}

output
I'm Darth Moder.

Try the above example in the playground by pasting the following code:
{"data":{"text":"null"},"templates":[{"name":"template","text":"{{<intermediate}}{{$name}}Moder{{/name}}{{/intermediate}}"},{"name":"introduction","text":"I'm {{$title}}Darth{{/title}} {{$name}}Vader{{/name}}."},{"name":"intermediate","text":"{{<introduction}}{{/introduction}}"}]}

The problem
In the previous section, I intentionally omitted indentation in the demonstration of parent and block tags, because there is currently no specification of how that should behave. Since a parent tag pair without blocks is basically just a partial, the following interpretation would probably be uncontroversial:
template.mustache
    {{<partial}}{{/partial}}

output
    Hello there!

Adding blocks to the mix, most people will probably also agree with the whitespace in the following example.
template.mustache
{{<intermediate}}
{{$greeting}}
high five
{{/greeting}}
{{/intermediate}}

intermediate.mustache
Hi,
    {{<invitation}}{{/invitation}}

invitation.mustache
please give me a:
    {{$greeting}}
    hug
    {{/greeting}}

output
Hi,
    please give me a:
        high five

The above examples are relatively clear-cut because all tags are standalone and the block is only indented in the place of expansion (in invitation.mustache). Things become fuzzier when indentation appears in more places,
template.mustache
{{<intermediate}}
    {{$greeting}}
        high five
    {{/greeting}}
{{/intermediate}}

invitation.mustache
please give me a:
    {{$greeting}}
        hug
    {{/greeting}}

or when some tags don't clear on both sides.
template.mustache
{{<intermediate}}{{$greeting}}
high five
{{/greeting}}{{/intermediate}}

invitation.mustache
please give me a:
    {{$greeting}}hug{{/greeting}}

Hence, in order to promote consistent behavior across different Mustache implementations, I'm suggesting to specify how template inheritance and whitespace should interact (credits to @gasche for first suggesting this). I'll open the discussion with my current ideas of what might be the best way to approach this. Before I do that, though, let me introduce some concepts that I think are relevant.
Exploring the problem space
Template space vs. comment space
Comment tags introduce "dead" space within a template that is never rendered.
before {{! never rendered }} after

To highlight this distinction, let's paint the comment space black.
before {{!████████████████}} after

Per the spec, the contents within a pair of parent open/close tags default to being comment space, too.
{{<parent}} never rendered {{interpolation}} {{/parent}}

{{<parent█████████████████████████████████████████████}}

This also visually highlights the similarity between a parent and a partial.
{{>parent}}

By way of exception, block tags can "punch holes" in the comment space within parent tag pairs, creating what could be considered "template islands", with "comment barriers" in between them.
a {{<parent}} b {{$block}} c {{/block}} d {{/parent}} e

a {{<parent███████$block}} c {{████████████████████}} e

Within a regular, continuous stretch of template space, everything is linearly ordered. As a result, everything that comes before a particular tag will directly influence the position of everything that comes after that tag.
If this wasn't here... {{#section}} ... this would be more to the left. {{/section}}

Comment barriers provide a visual way to remind us that there is no such direct relationship within and across parent tags. Blocks need not appear in the same order within a parent tag pair as within the corresponding parent template, or might even be ignored. Also, a block may be significant within a parent tag pair, but play only a minor role within the parent template.
{{<parent████$block}} If this wasn't here... {{███████████████████}} ... this might as well be just as much to the left.

We could say that the larger template outside of the parent tag pair and the template islands within them act like "parallel worlds" that don't really interact, until everything "lands" in the parent template.
Parameter blocks vs. argument blocks
A block outside any parent tag pair marks a place in the template that can be configured. It acts as a parameter of the template. If not configured from the outside, its contents serve as the default.
{{$parameter}} default {{/parameter}}

A block inside a parent tag pair provides the external configuration for such a parameter. It acts as an argument for another template.
{{<parent████$parameter}} argument {{███████████████████████}}

Definition vs. expansion
As I mentioned before, the contents of a block can be thought of as an embedded partial template. To illustrate, compare the following pair of templates:
block.mustache
{{<parent████$block}}Hello there!{{█████████████████}}

parent.mustache
{{$block}}{{/block}}

with the following:
block.mustache
Hello there!

parent.mustache
{{>block}}

The output is the same in both cases (Hello there!) and in both cases, content from one template is inserted in the other. In both cases, this content is defined inside block.mustache while parent.mustache is the place where it is expanded. The main differences are (1) which template is "outermost" and (2) how much of a template file is dedicated to the definition of the "transplanted" content. In partials, the definition is always the entire file, while in blocks, it never is.
It is important to distinguish definition from expansion, because the site of expansion can be identical to the site of definition, which might hide the distinction. In blocks, this happens when a parameter block is never configured from the outside and the default ends up being rendered.
{{$block}}Hello there!{{/block}}

There are several asymmetries between block definitions and expansions, and between parameter and argument blocks. A parameter block is a site of both definition and expansion, while an argument block is only a site of definition. Every parameter block ends up being expanded into, but not every defined block is expanded. A block defined in argument position can only be expanded elsewhere, while a block defined in parameter position can never be expanded elsewhere.
Clearance
For most tag types, it is specified that they should not introduce blank lines just by existing. This is why
a
{{!████}} b
c

renders into
a
 b
c

while
a
{{!████}}
c

renders without the middle line.
a
c

We say that the latter comment is "standalone" while the former is not. For those tag types where it is specified unambiguously, standalone always means that there is start clearance, i.e., no content except for whitespace between the preceding line start and the opening delimiter ({{) of the tag, as well as end clearance, no content expect for whitespace between the closing delimiter (}}) of the tag and the following line end.
For parent and block tag pairs, a more nuanced concept of standalone is likely necessary, due to the previous distinctions between template and comment space, parameter and argument blocks, and definition and expansion. Let's first consider the state space for a single tag ({{!}} below). There are four possible combinations depending on whether it clears on the start and end or not:
┌───────────┬─────────────────────┐
│ start     │    end clearance    │
│ clearance │   yes   ╷    no     │
│      ╶────┼─────────┼───────────┤
│       yes │ a       │ a         │
│           │ {{!}}   │ {{!}} b   │
│           │ b       │           │
│      ╶────┼─────────┼───────────┤
│        no │ a {{!}} │ a {{!}} b │
│           │ b       │           │
└───────────┴─────────┴───────────┘

In the original tags such as section, comment and change delimiter, we consider the yes/yes case in the top left as standalone and the other three as "not standalone". In order to distinguish the other three cases from each other as well, let's name all combinations with a letter: B when the tag clears on both delimiters, S when it clears only at the start, E when it clears only at the end and N when it clears on neither delimiter.
In blocks, the opening and closing tags may independently have each of the four types of clearance, so we end up with sixteen possible combinations for the block as a whole:
┌─────────┬─────────────────────────────────────────────────────────────┐
│ opening │                     closing tag                             │
│ tag     │     B     ╷     S     ╷        E        ╷        N          │
│       ╶─┼───────────┼───────────┼─────────────────┼───────────────────┤
│       B │ a         │ a         │ a               │ a                 │
│         │ {{$}}     │ {{$}}     │ {{$}}           │ {{$}}             │
│         │ b         │ b         │ b {{/}}         │ b {{/}} c         │
│         │ {{/}}     │ {{/}} c   │ c               │                   │
│         │ c         │           │                 │                   │
│       ╶─┼───────────┼───────────┼─────────────────┼───────────────────┤
│       S │ a         │ a         │ a               │ a                 │
│         │ {{$}} b   │ {{$}} b   │ {{$}} b {{/}}   │ {{$}} b {{/}} c   │
│         │ {{/}}     │ {{/}} c   │ c               │                   │
│         │ c         │           │                 │                   │
│       ╶─┼───────────┼───────────┼─────────────────┼───────────────────┤
│       E │ a {{$}}   │ a {{$}}   │ a {{$}}         │ a {{$}}           │
│         │ b         │ b         │ b {{/}}         │ b {{/}} c         │
│         │ {{/}}     │ {{/}} c   │ c               │                   │
│         │ c         │           │                 │                   │
│       ╶─┼───────────┼───────────┼─────────────────┼───────────────────┤
│       N │ a {{$}} b │ a {{$}} b │ a {{$}} b {{/}} │ a {{$}} b {{/}} c │
│         │ {{/}}     │ {{/}} c   │ c               │                   │
│         │ c         │           │                 │                   │
└─────────┴───────────┴───────────┴─────────────────┴───────────────────┘

We can identify each combination by concatenating the letters for the opening and closing tags, so from left to right, the combinations at the top row would be named BB, BS, BE and BN. If we want to promote consistent behavior across implementations, the specification will need to address unambiguously what should happen with the whitespace in all sixteen combinations.
Proposal
I suggest a small set of rules, which should unambiguously specify what happens with whitespace in all cases and which I hope will also be acceptable to most people. The following rules were in part inspired by ideas previously shared by @gasche.
0. Standalone tags
Individual block and parent tags should not introduce blank lines in the output when they clear on both delimiters. I'm numbering this rule zero, because it is not really a new rule.
1. Standalone pairs
The pair of a parent tag and its matching end section tag as a whole is standalone if the opening tag clears at the start and the closing tag clears at the end (so that's BB, BE, SB or SE). This corresponds to the intuitive notion that such a parent pair should behave like a single standalone partial tag. Another, independent justification of this rule is that the internal delimiters of the pair should not be taken into account because they are in comment space.
Like in standalone tags, the external clearance around a standalone pair should be considered part of the tags rather than part of the literal contents within the surrounding template.
The exact same notion of a standalone pair is also applicable to parameter blocks, because these are sites of template expansion, too. It does not apply to argument blocks, because those are not template expansion sites and also because their outer delimiters are in comment space.
The outermost pair in each of the following examples is standalone:
{{<parent}}{{$block}}
{{/block}}{{/parent}}

{{$block}}{{/block}}

    {{$block}}
    {{/block}}

2. Intrinsic indentation
If the opening tag of an argument block or a standalone parameter block clears at the end (so that's BB, BS, BE, BN, EB, ES, EE or EN for argument blocks but only BB or BE for parameter blocks), then the intrinsic indentation of the block is the whitespace at the start of the first line after the opening block tag.
In all remaining cases, the intrinsic indentation of a block is the empty string.
The justification for taking only the opening side of the internal clearance into account is that the absence of start clearance at the closing tag is equivalent to an external partial template that lacks a final line end.
In all examples below, the intrinsic indentation of the block is four spaces:
{{$block}}
    content
{{/block}}

{{$block}}
    content{{/block}}

{{<parent}}{{$block}}
    content
{{/block}}{{/parent}}

In all examples below, the intrinsic indentation of the block is the empty string:
{{$block}}content{{/block}}

    {{$block}}content{{/block}}

    {{$block}}
content
    {{/block}}

    a {{$block}}
    content
    {{/block}}

    {{$block}}
    content
    {{/block}} b

{{<parent}}
    {{$block}}content{{/block}}
{{/parent}}

3. Deindentation at block definition time
The intrinsic indentation of a block definition is removed from each of its lines before anything else happens with its contents.
The following example block,
    {{$block}}
        text
        {{#section}}
            text
        {{/section}}
    {{/block}}

is equivalent to an external partial template with the following content.
text
{{#section}}
    text
{{/section}}

4. Indentation at template expansion sites
This rule is a generalization of the indentation rule that already exists for standalone partial tags.
The indentation of a partial tag, parent pair or parameter block pair is determined as follows. If it is a block with intrinsic indentation, then the intrinsic indentation is used. Otherwise, if the tag or pair is standalone, then the indentation of the single tag or the pair's opening tag is used. In all remaining cases, the empty string is used.
Note that the indentation used is always whitespace that is not part of the literal contents of the template.
The indentation thus determined is added to each line of whichever (external) template or block ends up being expanded in the position of the tag or pair, before that template or block is rendered.
In each of the following examples, four spaces of indentation will be added to each line of whichever template or block ends up being expanded on site.
    {{>partial}}

    {{<parent}}{{/parent}}

    {{$block}}{{/block}}

{{$block}}
    default content
{{/block}}

In each of the following examples, no indentation (the empty string) will be added.
{{>partial}}

{{<parent}}{{/parent}}

{{$block}}
{{/block}}

Full circle
Let's revisit some of the examples that appeared earlier in this post, and see how they would render according to the above rules. The playground implements those rules faithfully, so playground savestates are provided.
The straightforward example
template.mustache
{{<intermediate}}
{{$greeting}}
high five
{{/greeting}}
{{/intermediate}}

intermediate.mustache
Hi,
    {{<invitation}}{{/invitation}}

invitation.mustache
please give me a:
    {{$greeting}}
    hug
    {{/greeting}}

output
Hi,
    please give me a:
        high five

Try the above example in the playground by pasting the following code:
{"data":{"text":"null"},"templates":[{"name":"template","text":"{{<intermediate}}\n{{$greeting}}\nhigh five\n{{/greeting}}\n{{/intermediate}}"},{"name":"intermediate","text":"Hi,\n    {{<invitation}}{{/invitation}}"},{"name":"invitation","text":"please give me a:\n    {{$greeting}}\n    hug\n    {{/greeting}}"}]}

The complex indentation example
template.mustache
{{<intermediate}}
    {{$greeting}}
        high five
    {{/greeting}}
{{/intermediate}}

invitation.mustache
please give me a:
    {{$greeting}}
        hug
    {{/greeting}}

output
Hi,
    please give me a:
            high five

Try the above example in the playground by pasting the following code:
{"data":{"text":"null"},"templates":[{"name":"template","text":"{{<intermediate}}\n    {{$greeting}}\n        high five\n    {{/greeting}}\n{{/intermediate}}"},{"name":"intermediate","text":"Hi,\n    {{<invitation}}{{/invitation}}"},{"name":"invitation","text":"please give me a:\n    {{$greeting}}\n        hug\n    {{/greeting}}"}]}

The mixed clearance example
template.mustache
{{<intermediate}}{{$greeting}}
high five
{{/greeting}}{{/intermediate}}

invitation.mustache
please give me a:
    {{$greeting}}hug{{/greeting}}

output
Hi,
    please give me a:
        high five

Try the above example in the playground by pasting the following code:
{"data":{"text":"null"},"templates":[{"name":"template","text":"{{<intermediate}}{{$greeting}}\nhigh five\n{{/greeting}}{{/intermediate}}"},{"name":"intermediate","text":"Hi,\n    {{<invitation}}{{/invitation}}"},{"name":"invitation","text":"please give me a:\n    {{$greeting}}hug{{/greeting}}"}]}

Discussion
What do you think? Can you think of edge cases where the proposed rules would give undesirable results? Can you think of rules that would give acceptable results in more cases, or simpler rules that would give equally acceptable results?
I hereby offer to write the specs if we reach an agreement. In that case, I will try them with my own implementation before submitting a pull request.
CC to all implementers and contributors who have been recently active around the spec (in random order): @gasche @softmoth @adam-fowler @Danappelxx @pvande @splumhoff @bobthecow @sayrer @spullara

(Thanks for the ping through #131!)
In my best experiment with indentation, I used two guiding principles:

a tag, or pair of matching stag, is "visible" if its rendering emits output; "standalone" is redefined to "not visible"
partials (with or without parameters) and blocks have indentation; when rendering a line, I add the indentation of the partials it is included in, and remove the indentation of the parameter blocks

(I did use a rule such that "if the start-block tag is followed by whitespace and a newline, then its indentation is the indentation of the first non-whitespace line below", similar to your "intrisic indentation" concept.)
Your system is, on the surface, more complex, but it has the advantage of being solely driven by the (whitespace) syntax of the input, without any semantic consideration. ("visible" or not depends on how the item will be rendered.) I think it makes it simpler to implement, and to integrate into existing implementations.
I don't know if the two approaches give the same results in all cases, or most cases. Intuitively I think they are very similar.
Three remarks:

I should dig up my own implementations around this to give as a pointer. (TODO)
We should probably build prototype implementations of whichever spec we have in mind, to test on various examples to understand how these things behave.
Some of the notions (standalone pairs) would naturally apply to other tags (section tags, for example), and this would in fact improve the result in these settings. You have not proposed this, I suppose for backward-compatibility reasons.

Pointers to my previous explorations in this area:

My specification of how to measure "indentation" is given in this github comment. I think it is essentially identical to the notion of "intrisic indentation" that you propose, which suggests that the proposal is "natural".
The implementation of the "visibility" criterion is in this patchset (which ended up not merged in ocaml-mustache upstream as I preferred to stick to the standard behavior). (I understand that the code may be less accessible to people unfamiliar with OCaml, but the comment at least gives the ideas.)

I have updated the opening post to include links to and savestates for my newly developed Mustache playground. I hope this will reduce barriers for readers to experiment with the examples.
The playground is powered by my own implementation, Wontache. Because of that, it fully implements the latest spec as well as the rules proposed here. It aims to be a general, more powerful alternative to the "demo" on the official Mustache website. Whitespace is handled correctly, lambdas are supported and it is possible to enter multiple named templates alongside each other, so that partial and parent tags can be used effectively. And as demonstrated above, it is possible to share sessions with other people by copy-pasting chunks of JSON code.
Feedback welcome (@gasche)!


Publish on F-Droid

Metadata in this branch:
https://gitlab.com/io7m/fdroiddata/-/tree/exfilac?ref_type=heads
Running into problems building the code due to having a non-standard build setup (due to Gradle being pure undiluted excrement).

First issue: The fdroidserver package has a bug. It was first documented here two years ago, and apparently fixed:
https://gitlab.com/fdroid/docker-executable-fdroidserver/-/issues/15
But now with the most recent fdroidserver package from git, the problem is back:
2024-09-19 17:41:59,006 INFO: Cleaning Gradle project...
2024-09-19 17:41:59,006 DEBUG: Directory: build/com.io7m.exfilac
2024-09-19 17:41:59,006 DEBUG: > /home/rm-work/git/fdroidserver/fdroidserver-env/lib/python3.12/site-packages/gradlew-fdroid clean
2024-09-19 17:41:59,006 ERROR: Could not build app com.io7m.exfilac: OSError while trying to execute /home/rm-work/git/fdroidserver/fdroidserver-env/lib/python3.12/site-packages/gradlew-fdroid clean: [Errno 2] No such file or directory: '/home/rm-work/git/fdroidserver/fdroidserver-env/lib/python3.12/site-packages/gradlew-fdroid'
2024-09-19 17:41:59,009 DEBUG: skip deploying full build logs: not enabled in config
2024-09-19 17:41:59,010 DEBUG: skip deploying full build logs: not enabled in config
2024-09-19 17:41:59,010 INFO: Finished
2024-09-19 17:41:59,010 INFO: 1 build failed
2024-09-19 17:41:59,010 DEBUG: skip deploying full build logs: not enabled in config
2024-09-19 17:41:59,010 DEBUG: skip deploying full build logs: not enabled in config

Second issue: We put the version code in gradle.properties to make it possible for external tools to do version updates without having to involve Gradle. fdroid doesn't know how to extract the version code:
2024-09-19 17:49:14,260 ERROR: ...checkupdate failed for com.io7m.exfilac : Couldn't find any version information
2024-09-19 17:49:14,261 DEBUG: Traceback (most recent call last):
  File "/builds/io7m/fdroidserver/fdroidserver/checkupdates.py", line 751, in main
    checkupdates_app(app, options.auto, options.commit)
  File "/builds/io7m/fdroidserver/fdroidserver/checkupdates.py", line 537, in checkupdates_app
    (version, vercode, tag) = check_tags(app, pattern)
                              ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/builds/io7m/fdroidserver/fdroidserver/checkupdates.py", line 270, in check_tags
    raise FDroidException(_("Couldn't find any version information"))
fdroidserver.exception.FDroidException: Couldn't find any version information

Third issue: fdroid deletes the bundled version of Gradle included in the repository, meaning that the build then fails (because make/Make.java expects ./gradlew to exist).

Now the build fails because there are extra jar files left over:
2024-09-20 15:14:39,533 INFO: Scanning source for common problems...
2024-09-20 15:14:39,537 DEBUG: scanner is configured to use signature data from: 'suss'
2024-09-20 15:14:39,537 DEBUG: downloading 'https://fdroid.gitlab.io/fdroid-suss/suss.json'
2024-09-20 15:14:39,731 DEBUG: write 'suss.json' to cache
2024-09-20 15:14:39,733 DEBUG: next suss.json cache update due in 23:59:59.996205
2024-09-20 15:14:39,762 ERROR: Found Java JAR file at xstructural.jar
2024-09-20 15:14:39,762 ERROR: Found Java JAR file at ktlint.jar
2024-09-20 15:14:39,765 ERROR: Found Java JAR file at scando.jar
2024-09-20 15:14:39,765 ERROR: Found Java JAR file at sqlite.jar
2024-09-20 15:14:39,767 INFO: Removing gradle-wrapper.jar at gradle/wrapper/gradle-wrapper.jar
2024-09-20 15:14:39,779 ERROR: Found shared library at com.io7m.exfilac.main/src/main/jniLibs/arm64-v8a/libsqlitejdbc.so
2024-09-20 15:14:39,779 ERROR: Found shared library at com.io7m.exfilac.main/src/main/jniLibs/x86/libsqlitejdbc.so
2024-09-20 15:14:39,780 ERROR: Found shared library at com.io7m.exfilac.main/src/main/jniLibs/armeabi/libsqlitejdbc.so
2024-09-20 15:14:39,780 ERROR: Found shared library at com.io7m.exfilac.main/src/main/jniLibs/x86_64/libsqlitejdbc.so
2024-09-20 15:14:39,793 ERROR: Could not build app com.io7m.exfilac: Can't build due to 8 errors while scanning
2024-09-20 15:14:39,793 DEBUG: Error encountered, stopping by user request.
Uploading artifacts for failed job

I don't know why any of these are problems.

Submitted: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/15804

Merged. Should start appearing in F-droid soon.


improving Ondat CLI deployment manifest

Changes made:

removing cat as a dependancy in the code snippet.
using secrets as environment variables for the username and password instead of plaintext.
updated the Ondat CLI image tag version.

lets not merge this PR until 2.9.0 is released, as we should update the new CLI version at the same time.

ERROR: 1 dead links found!
[✖] https://coreos.com/operators/prometheus/docs/latest/user-guides/getting-started.html → Status: 0

This is now fixed in https://github.com/ondat/documentation/pull/256 - the recommendation would be to merge #256 first and then re-run the workflow for new changes to be picked up.


BVTCK-179 Adding tests for ConstraintViolationSetAssert

https://hibernate.atlassian.net/browse/BVTCK-179

Perfect! Merged, thanks!


[cPP Correction] CRT_DRBG Requirements

Provide the location of the issue
Section <IP_ADDRESS>, FCS_RBG_EXT.1.2
Application Note 16, Paragraph 2
What is the correction request for the cPP? Please describe.
Consistency now that Hash and HMAC DBRGs specify individual algorithms.
Describe the solution you'd like
Update the CTR_DRBG to require the selection of key size(s).
Delete "While any of the identified hash functions (SHA-1, SHA-256, SHA-384, SHA-512) are allowed for Hash_DRBG or HMAC_DRBG, only AES-based implementations for CTR_DRBG are allowed." Since this explanation is when the options were "any" and "AES". Now that there are selections, the options are self explanatory in the SFR.

Recommendation...
Accept Kenji's recommendation as stated in the issue description.

Agreed.


fix: update DistanceMatrixResponse to add caution about parsing b/130399550

Fixes b/130399550. Adds caution to origin-addresses and destination-addresses not to parse the formatted addresses, which are meant to be human-readable. Also adds backticks to a mention of origin_addresses to format it properly.
Thank you for opening a Pull Request!

Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open a GitHub issue as a bug/feature request before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes b/130399550 🦕

/update-dist


[FEAT] Add Review Functionality - User Rating and Comment Feature

Description:
Add a feature enabling users to rate and comment on different aspects of the website, enhancing engagement and feedback.
Requirements:

Create a review button.
Enable rating on a scale and comment submission.
Validate input before submission.
Allow viewing existing reviews with moderation options.
Ensure responsiveness and accessibility.

hey @singodiyashubham87
kindly assign me this issue under #ssoc24

@Atanu789 No need as of now.


Fail/Crash to open app after installing react-native-webview dependency

Bug description:
I installed the latest version of the lib and when I run yarn react-native run-android everything goes fine, but I can't get my app to open on the emulator after it. It keeps crashing. If I remove react-native-webview dependency my app opens normally.
I've tried to install older versions of the lib but the same happens.
I already wiped the emulator settings and cleared cache to see if it would work, but with no success.
Screenshots/Videos:

App Crashing when react-antive-webview is installed.

App opens when I remove the dependency

Environment:

OS: Android
OS version: 11
react-native version: 0.63.4
react-native-webview version: 11.6.2

hi,
I've started facing the same problem after adding minHeight attribute to the style property, like this:
<WebView
    ...
    style={{backgroundColor: 'transparent', flex: 1, minHeight: '300px'}}
    ...
 />

replacing the minHeight's value to a number works fine:
<WebView
    ...
    style={{backgroundColor: 'transparent', flex: 1, minHeight: 300}}
    ...
 />

Environment:

OS: Android
OS version: 11
react-native: 0.63.4
react-native-webview: ^11.4.3

I have a very similar android specific issue with version: ^11.6.4
Like yourself, I have ONLY installed the package via yarn add react-native-webview and my detox tests have been failing with the following error:
DetoxRuntimeError: Failed to run application on the device

    HINT: Most likely, your main activity has crashed prematurely.

    Native stacktrace dump: java.lang.NoSuchMethodError: No direct method <init>(ILjava/lang/Class;Ljava/lang/String;Ljava/lang/String;I)V in class Lkotlin/jvm/internal/FunctionReferenceImpl; or its super classes (declaration of 'kotlin.jvm.internal.FunctionReferenceImpl' appears in /data/app/~~tVQXRextVO2nUllF1-6L6g==/com.whichmobileapp-R1eVS54uc89qIOHE9sUwbg==/base.apk)

What makes it even more confusing is that I haven't even started using the < WebView /> component anywhere in the code base.
Environment:
OS: Android
MacOS 10.15.7
react-native: 0.64.2
react-native-webview: ^11.6.4

To resolve the issue I had with detox, I had to use a lower version of the kotlin-gradle-plugin which can be found in android/settings.gradle
classpath 'org.jetbrains.kotlin:kotlin-gradle-plugin:1.3.71'


Papers Regarding differentiation in GPy

Hi,
Dunno if opening an issue is the right way to ask, but:
Is there any paper that I can cite for the formulas used in GPy.kern.stationary.gradients_X
Thanks,
Nikitas

Not directly, I'm afraid. @jameshensman are you aware of any publications for the gradients_X setup?

Hi,
I have not looked into GPy.kern.stationary.gradients_X but have found this document useful in the past...
http://mlg.eng.cam.ac.uk/mchutchon/DifferentiatingGPs.pdf


lua51Packages.luaexpat: Removing broken meta attribute.

Motivation for this change
Luaexpat has been mistakenly marked as broken during a
20.03 a zero hydra failures tree-wide commit. Removing the broken meta
attribute.
I discovered this problem when trying to rebuild the prosody XMPP server. Prosody itself is still green on Hydra. I assume marking an input as broken does not change the overall hash hence do not trigger a rebuild? Not sure...
I'm still not 100% sure why this was marked as broken, the build does not seem to be flaky. My current best assumption here is a tooling failure. I'm now wondering whether this same bug could happen somewhere else.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

cc @worldofpeace

Looks like it builds, perhaps it is just flaky.


update practitioner nav docs + registry

Description

this should not impact the ai practitioner nav
registry wont be updated in this preview
@anita-trimbur i decided against removing the dropdown quiet yet, but i removed some items, pls make a followup issue

fixes https://github.com/pulumi/docs/issues/8965
pls test out on various screen sizes, thank you!!
things that need to be fixed

[x] marketing top nav menus

Checklist:

[x] I have reviewed the style guide.
[x] If blogging, I have reviewed the blogging guide.
[ ] I have manually confirmed that all new links work.
[x] I added aliases (i.e., redirects) for all filename changes.
[ ] If making css changes, I rebuilt the bundle.

looks so much airier now!! what do you think about the filled icons on white, too heavy or no?

@anita-trimbur ah i missed that those changed in your designs, we should def make those outline icons

alright @anita-trimbur can ya give this another look?


Remove deprecation messages

UK & US address were deprecated ~30 versions ago.

This file was automatically generated using rake reference... might want to look at that script instead. Thanks for the PR, but running the rake task again (which will probably happen when new methods get implemented) will just override these again.

Hello, @rstacruz! What about removing UK & US methods from those modules? They were extracted a long time ago (4 years).

ping @rstacruz

that idea gets a :+1: for me but I'd rather see what the feedback of other maintainers are on this as well :)


Add Badges

Build status
Crates.io
License

Codecov Report
Base: 66.54% // Head: 66.54% // No change to project coverage :thumbsup:

Coverage data is based on head (de91003) compared to base (7f24eb0).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #16   +/-   ##
=======================================
  Coverage   66.54%   66.54%
=======================================
  Files           4        4
  Lines         559      559
=======================================
  Hits          372      372
  Misses        187      187

Flag
Coverage Δ

unittests
66.54% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out 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.


how to check if a user has the permission to broadcast message to a channel?

if find although the user is the creator of the channel, chatPermission in chat object returned by getChat indicates the user has no right to send message.
part of the log
[ 3][t 1][1678353734.471293687][Td.cpp:2923][!Td][&td_requests]	Receive request 17: getChat {
  chat_id = ***4402
}
[ 3][t 1][1678353734.471417903][MessagesManager.cpp:35006][!GetChatRequest]	Search for server message 146 in chat ***4402 found 0xaaaaf2c19c30
[ 3][t 1][1678353734.471545219][Td.cpp:3980][!Td][&td_requests]	Sending result for request 17: chat {
  id = ***4402
  type = chatTypeSupergroup {
    supergroup_id = ***4402
    is_channel = true
  }
  title = "test"
  photo = null
  permissions = chatPermissions {
    can_send_messages = false
    can_send_media_messages = false
    can_send_polls = false
    can_send_other_messages = false
    can_add_web_page_previews = false
    can_change_info = false
    can_invite_users = false
    can_pin_messages = false
    can_manage_topics = false
  }
  ...
[ 3][t 1][1678353819.953547954][Td.cpp:2923][!Td][&td_requests]	Receive request 18: getSupergroup {
  supergroup_id = ***4402
}
[ 3][t 1][1678353819.953650951][Td.cpp:3980][!Td][&td_requests]	Sending result for request 18: supergroup {
  id = ***4402
  usernames = null
  date =<PHONE_NUMBER>
  status = chatMemberStatusCreator {
    custom_title = ""
    is_anonymous = false
    is_member = true
  }
  member_count = 2
  has_linked_chat = true
  has_location = false
  sign_messages = false
  join_to_send_messages = true
  join_by_request = false
  is_slow_mode_enabled = false
  is_channel = true
  is_broadcast_group = false
  is_forum = false
  is_verified = false
  restriction_reason = ""
  is_scam = false
  is_fake = false
}

The permissions in chat.permissions is for non-administrator members. If you want to check permissions for a single user you must use getChatMember.
chat.permissions:
https://github.com/tdlib/td/blob/1543c41f3411bd6aa74713c8aba4e93fa8d952c7/td/generate/scheme/td_api.tl#L1318

The permissions in chat.permissions is for non-administrator members. If you want to check permissions for a single user you must use getChatMember.
chat.permissions:
https://github.com/tdlib/td/blob/1543c41f3411bd6aa74713c8aba4e93fa8d952c7/td/generate/scheme/td_api.tl#L1318

okay, got it.
thx for your reply.

For self you can also check that supergroup.status is chatMemberStatusCreator, or it is chatMemberStatusAdministrator and status.rights.can_post_messages == true.


✨ add asset allocate command

Current dependencies on/for this PR:

main

PR #30   👈

This comment was auto-generated by Graphite.


[Bug]: Hosting on non-root path URI broken after 0.26.1

The Problem
Hosting/running on a non-root URI like "/spdf" breaks the whole experience in versions after 0.26.1 by introducing absolute paths for js and css dependencies. As far as I can tell commit f43fe15193ce257245221472e34336cdf4983cf8 broke this.
PS: I haven't checked further, but includes for icons, etc. are likely also impacted by this.
Version of Stirling-PDF
0.28.1
Last Working Version of Stirling-PDF
0.26.1
Page Where the Problem Occurred
http://localhost/spdf/
Docker Configuration
No response
Relevant Log Output
No response
Additional Information
includes in home from 0.26.1 (working):
    <!-- jQuery -->
    <script src="js/thirdParty/jquery.min.js"></script>
    <script src="js/thirdParty/jquery.validate.min.js"></script>
    <script src="js/thirdParty/jszip.min.js"></script>

    <!-- Bootstrap -->
    <script src="js/thirdParty/popper.min.js"></script>
    <script src="js/thirdParty/bootstrap.min.js"></script>
    <link rel="stylesheet" href="css/bootstrap.min.css">

    <!-- Bootstrap Icons -->
    <link rel="stylesheet" href="css/bootstrap-icons.min.css">

    <!-- PDF.js -->
    <script type="module" src="./pdfjs-legacy/pdf.mjs"></script>

    <!-- PDF-Lib -->
    <script src="js/thirdParty/pdf-lib.min.js"></script>

    <!-- Custom -->
    <link rel="stylesheet" href="css/general.css">
    <link rel="stylesheet" href="css/theme/theme.css">
    <link rel="stylesheet" href="css/theme/componentes.css">
    <link rel="stylesheet" href="css/theme/theme.light.css" id="light-mode-styles">
    <link rel="stylesheet" href="css/theme/theme.dark.css" id="dark-mode-styles">
    <link rel="stylesheet" href="css/rainbow-mode.css" id="rainbow-mode-styles" disabled>
    <link rel="stylesheet" href="css/tab-container.css">
    <link rel="stylesheet" href="css/navbar.css">

from 0.28.1 (not working):
    <!-- jQuery -->
    <script src="/js/thirdParty/jquery.min.js"></script>
    <script src="/js/thirdParty/jquery.validate.min.js"></script>
    <script src="/js/thirdParty/jszip.min.js"></script>

    <!-- Bootstrap -->
    <script src="/js/thirdParty/popper.min.js"></script>
    <script src="/js/thirdParty/bootstrap.min.js"></script>
    <link rel="stylesheet" href="/css/bootstrap.min.css">

    <!-- Bootstrap Icons -->
    <link rel="stylesheet" href="/css/bootstrap-icons.min.css">

    <!-- PDF.js -->
    <script type="module" src="/pdfjs-legacy/pdf.mjs"></script>

    <!-- PDF-Lib -->
    <script src="/js/thirdParty/pdf-lib.min.js"></script>

    <!-- Custom -->
    <link rel="stylesheet" href="/css/general.css">
    <link rel="stylesheet" href="/css/theme/theme.css">
    <link rel="stylesheet" href="/css/theme/componentes.css">
    <link rel="stylesheet" href="/css/theme/theme.light.css" id="light-mode-styles">
    <link rel="stylesheet" href="/css/theme/theme.dark.css" id="dark-mode-styles">
    <link rel="stylesheet" href="/css/rainbow-mode.css" id="rainbow-mode-styles" disabled>
    <link rel="stylesheet" href="/css/tab-container.css">
    <link rel="stylesheet" href="/css/navbar.css">

Browsers Affected
No response
No Duplicate of the Issue

[X] I have verified that there are no existing issues raised related to my problem.

    <!-- Icons -->
    <link rel="apple-touch-icon" sizes="180x180" href="/spdf/apple-touch-icon.png">
    <link rel="icon" type="image/png" sizes="32x32" href="/spdf/favicon-32x32.png">
    <link rel="icon" type="image/png" sizes="16x16" href="/spdf/favicon-16x16.png">
    <link rel="manifest" href="/spdf/site.webmanifest" crossorigin="use-credentials">
    <link rel="mask-icon" href="/spdf/safari-pinned-tab.svg" color="#ca2b2a">
    <link rel="shortcut icon" href="/spdf/favicon.ico">
    <meta name="apple-mobile-web-app-title" content="Stirling PDF">
    <meta name="application-name" content="Stirling PDF">
    <meta name="msapplication-TileColor" content="#00aba9">
    <meta name="theme-color" content="#ffffff">

    <!-- jQuery -->
    <script src="/spdf/js/thirdParty/jquery.min.js"></script>
    <script src="/spdf/js/thirdParty/jquery.validate.min.js"></script>
    <script src="/spdf/js/thirdParty/jszip.min.js"></script>

    <!-- Bootstrap -->
    <script src="/spdf/js/thirdParty/popper.min.js"></script>
    <script src="/spdf/js/thirdParty/bootstrap.min.js"></script>
    <link rel="stylesheet" href="/spdf/css/bootstrap.min.css">

    <!-- Bootstrap Icons -->
    <link rel="stylesheet" href="/spdf/css/bootstrap-icons.min.css">

    <!-- PDF.js -->
    <script type="module" src="/spdf/pdfjs-legacy/pdf.mjs"></script>

    <!-- PDF-Lib -->
    <script src="/spdf/js/thirdParty/pdf-lib.min.js"></script>

    <!-- Custom -->
    <link rel="stylesheet" href="/spdf/css/general.css">
    <link rel="stylesheet" href="/spdf/css/theme/theme.css">
    <link rel="stylesheet" href="/spdf/css/theme/componentes.css">
    <link rel="stylesheet" href="/spdf/css/theme/theme.light.css" id="light-mode-styles">
    <link rel="stylesheet" href="/spdf/css/theme/theme.dark.css" id="dark-mode-styles">
    <link rel="stylesheet" href="/spdf/css/rainbow-mode.css" id="rainbow-mode-styles" disabled>
    <link rel="stylesheet" href="/spdf/css/tab-container.css">
    <link rel="stylesheet" href="/spdf/css/navbar.css">
    <link rel="stylesheet" href="/spdf/css/home.css">
    <link rel="stylesheet" href="/spdf/css/fileSelect.css">
    <link rel="stylesheet" href="/spdf/css/footer.css">
    <script src="/spdf/js/thirdParty/fontfaceobserver.standalone.js"></script>

    <!-- Google MD Icons -->
    <link rel="stylesheet" href="/spdf/css/theme/font.css">

    <!-- Help Modal -->
    <link rel="stylesheet" href="/spdf/css/errorBanner.css">

    <script src="/spdf/js/cacheFormInputs.js"></script>
    <script src="/spdf/js/tab-container.js"></script>
    <script src="/spdf/js/darkmode.js"></script>

If I can't reproduce it, can you tell us more about your system

fwiw, I'm also encountering this issue with 0.28.1 and 0.28.2, 0.26.1 works fine.
The html itself (served through apache reverse proxy) loads, but js and css don't as /js and /css don't point to a path relative to stirling-pdf.
0.28.2: <script src="/js/thirdParty/jquery.min.js"></script>
0.26.1: <script src="js/thirdParty/jquery.min.js"></script>
I have not changed any settings of stirling-pdf itself and could not find any setting for custom paths.
Relevant parts of the apache2 config:
<VirtualHost *:443>
        ServerName              omitted
        ProxyPass               /stirling-pdf/ http://<IP_ADDRESS>:8080/
        ProxyPassReverse        /stirling-pdf/ http://<IP_ADDRESS>:8080/

Please let me know what additional information I can supply to help narrowing down the issue.

To confirm for the above issues have you set SYSTEM_ROOTURIPATH in stirling pdf

To confirm for the above issues have you set SYSTEM_ROOTURIPATH in stirling pdf

Thank you for following up. No, SYSTEM_ROOTURIPATH is currently not set in my environment.
Setting it to /stirling-pdf as per my reverse proxy configuration leads to the app 404'ing.

So for the path change to work correctly stirling-pdf needs to be informed via SYSTEM_ROOTURIPATH, which will then make stirlingpdf itself be on /stirling-pdf
however since you managed to get this working without stirling-pdf knowing it could be your latest settings are conflicting somehow with this, pointing to / and forwarding to /stirling-pdf instead of pointing to /stirling-pdf and forwarding to /stirling-pdf etc

Thank you. I can confirm that setting SYSTEM_ROOTURIPATH and changing the reverse proxy accordingly works for 0.28.2.
Paths to includes are now generated correctly, e.g.: <script src="/stirling-pdf/js/thirdParty/jquery.min.js"></script>.

Sorry for the late response, I got no notification for some reason.
I'm not sure if I ever tried setting SYSTEM_ROOTURIPATH in the past. Thanks for pointing it out in any case! It works not after also including this path in my reverse proxy configuration.


java.lang.ClassNotFoundException: Didn't find class "android.permission.POST_NOTIFICATIONS"

In my Ionic 7 App with cordova engine,
if I add into config.xml this code
<uses-permission android:name="android.permission.POST_NOTIFICATIONS" />
App crash at startup with error:
java.lang.ClassNotFoundException: Didn't find class "android.permission.POST_NOTIFICATIONS"

I solved something similar in Cordova today. It looks like the build system caches references to classes, and sometimes it might not clean up correctly as you add/remove plugins, so at some point you might add a plugin and the build system doesn't add the class because it believes it's already added. solution: nuke it from orbit. clean out the build artifacts and the platform, remove all plugins, re-add them, re-add the platform, and then recompile.
basically "turn it off and on again"

Closing as not specifically caused by this plugin


Update sequencing group 'project:' filter to parse names, not ids

Having some issues with my queries because the GraphQL project: filter seems to be expecting project IDs, however it only accepts string input so I can't get it to parse anything. I tried these changes in dev environment and they got my queries working again, however I'm not sure if this might impact anything else.
Understand there were a lot of changes to the project table recently, the speed improvements have been amazing 🏎

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (dd1ba37) 71.39% compared to head (6265b34) 71.39%.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #585   +/-   ##
=======================================
  Coverage   71.39%   71.39%
=======================================
  Files         116      116
  Lines        9283     9283
=======================================
  Hits         6628     6628
  Misses       2655     2655

Files
Coverage Δ

api/graphql/schema.py
75.90% <0.00%> (ø)

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

Paging @michael-harper  who was running into this yesterday

Added an equivalent fix for filtering sample based on project as that had the same issue. Co-opted one of the existing tests that already used sequencingGroup as the root with project as an existing filter.


fix: function:serve shows undefined port in url

Summary
Fixes #4116

When a Netlify site is served using netlify functions:serve locally, the function URL shown at the terminal contains an undefined port which is incorrect albeit confusing to users when they click on it. This is caused by the use of an undefined NetlifyFunction:settings:port property composed within the NetlifyFunction:url (getter) property. This PR fixes the issue and includes relevant tests.
NOTE: Although I scoured the codebase for a valid usage of NetlifyFunction:settings:port to no avail, I’m not particularly fond of the current solution but left it there with comments (and for compatibility) should anyone wish to take a closer look.

Thx for adapting the tests! 🐳

@karagulamos, do you mind resolving the merge conflict? The test file was renamed in https://github.com/netlify/cli/pull/4164


Upgrade Python

In #450 @yannickperrenet said

For the time being we will stay on Python3.8 because of the base images we use for the orchest-api, auth-server, orchest-webserver and update-server: tiangolo/meinheld-gunicorn-flask, which does not yet have a Python3.9 version available.

For the record, looks like tiangolo/meinheld-gunicorn-flask supports Python 3.9 already https://hub.docker.com/r/tiangolo/meinheld-gunicorn-flask/tags?page=1&name=3.9
There is an open PR to support Python 3.10 that hasn't received much attention though https://github.com/tiangolo/meinheld-gunicorn-docker/pull/52 (@/tiangolo is probably focused on FastAPI these days!). The good news is that the Dockerfile is quite simple https://github.com/tiangolo/meinheld-gunicorn-docker/blob/master/docker-images/python3.9.dockerfile so I don't think it should block us from deciding what Python version we want Orchest to run on.
Python 3.8 will be 3 years old this October, when 3.11 is released. I'd argue that it is positive to try to keep it up to date, to enjoy new language features (PEP 584 union operators to dict, PEP 585, type hinting generics in standard collections, PEP 615 zoneinfo, PEP 626 precise line numbers for debugging and other tools) and the upcoming performance improvements and improved tracebacks of Python 3.11.

Maybe worth revisiting when we restore the testing infrastructure.

https://github.com/orchest/orchest/commit/75e1bb8a63f9ed68629efc3402b1dba593ebdfe2 -> updates to Python 3.9

I don't think it should block us from deciding what Python version we want Orchest to run on.

Agreed. Although slightly more work is involved so I opted for the quick and easy upgrade path.


Defund New Haven Police Department

Hi @jmarion16 ,
To add your city, please provide email addressed and an email so we can add it! Check out the guidelines here and submit an new request: https://github.com/defund12/defund12.org/blob/gh-pages/EMAIL_TEMPLATE_STYLE_GUIDE.md
Thanks!


CSV seperators & dev activity

hi @pnadolny13,
You seem to be the most active maintainer on this project so I took the liberty to ping you.
I am wondering if there is currently any dev activity on this project? most of the commits apears to be dependabot generated.
If there is dev activity I was wondering if there is anything going on with regards to adding support for other csv sepperators, spessifically ;.
Thanks in advance for your help.

Hey @svenkerud - yep I've been the primary maintainer. Happy to review PRs or help get new features added!
I think this is a reasonable and generically useful feature to add. In https://github.com/MeltanoLabs/tap-csv/blob/3769f4e3676483b3c93bba80e8533f748a89a748/tap_csv/client.py#L84 we load the csv with csv.reader() which takes a bunch of optional arguments https://docs.python.org/3/library/csv.html#csv-fmt-params that we're not using right now. We could probably expose those to the tap config, maybe under a single csv_format object?
Is this something you'd consider contributing a PR for?

Briliant thanks for the repy.
I am happy to look into this issue as this is deffinetly something we need.
I will ping you once i have a PR ready.

@svenkerud a PR just merged to add configurable encoding https://github.com/MeltanoLabs/tap-csv/pull/58. I think your new setting could basically replicate that same pattern. I take back what I said about using a single csv_format key. The files config dict at the file level is probably a fine place for it to go.

I made #70 to implement the intended configuration. I needed it too, and I could not find a follow-up on this discussion

@Bartman0 @svenkerud the PR was merged so I'm closing this issue. I will cut a new release, after I merge the dependabot PRs.


point eth sdk to develop

instead of default which is master, which is a problem as app-eth on master branch points to eth sdk develop

An other solution could be to have default == develop
This would solve another issue we have: third party developers not knowing that the develop branch exists and is the place to get the changes from, and push their merge requests to.
What do you think @lpascal-ledger ?

yeah, we should aim for stability facing external devs, that's why I am keen on staying on released branches as much as possible.

@adrienlacombe-ledger @fbeutin-ledger I don't quite understand the issue here.
The tests are failing alright, you know the root cause? Last PR does not seem to be linked with the SDK.

Yeah the root cause is a mismatch between versions @lpascal-ledger

@lpascal-ledger I think the issue is that master eth-app points to develop eth-sdk

Indeed this a issue of the Ethereum application. master submodule is not correctly updated to its appropriate version.
We will fix this in Ethereum. Thanks!

Thank you Ser :beau:

This PR would resolve this issue.

Thank you! Closing this one then :)


Prevent Pushover attempting to send push to blank key

Checks the database to ensure the pushover user/group key is not 0 - aborts the attempt.
Prevents Node-Pushover crashing the entire app when the key isn't set

Merging :) I might clean up that part of the code a bit as it's getting a little hard to read, will ping you on PR in a sec


added youtube video links to outputs

Sara asked to allow for YouTube videos to be embedded in the Output section of the website. I've added functionality for these to be added by the user submitting just the YouTube video ID and the website converting this into an embedded video. I've also updated the list view to show when an output contains a video.

thanks @rpep hadn't come across that before, but that's a nice touch. easier for researchers to paste a full URL than try to figure out the video Id from it.
I've switched over to that now and is working fine.


proto_format: Shift proto_sync to bazel

Commit Message:
Additional Description:
This doesnt resolve the performance issues with proto_format/sync but is the first step, bringing these into bazel will allow performance to be addressed subsequently.


Model load_state_dict issue with 'focalnet_base_iso_16.pth'

Hello @jwyang:
I have another problem when I try the isotropic focalnets model of 'focalnet_base_iso_16.pth':
I initialize the model by
# isotropic FocalNets
model = FocalNet(depths=[12], patch_size=16, embed_dim=768, focal_levels=[3], focal_windows=[3], use_layerscale=True, use_postln=True).cuda()

and load 'focalnet_base_iso_16.pth' by
ckpt_path = "focalnet_base_iso_16.pth"
ckpt = torch.load(ckpt_path)
model.load_state_dict(ckpt['model'])
model.eval()

but I have the error as below:

_Error(s) in loading state_dict for FocalNet:
Unexpected key(s) in state_dict: "layers.0.blocks.0.modulation.ln.weight", "layers.0.blocks.0.modulation.ln.bias", "layers.0.blocks.1.modulation.ln.weight", "layers.0.blocks.1.modulation.ln.bias", "layers.0.blocks.2.modulation.ln.weight", "layers.0.blocks.2.modulation.ln.bias", "layers.0.blocks.3.modulation.ln.weight", "layers.0.blocks.3.modulation.ln.bias", "layers.0.blocks.4.modulation.ln.weight", "layers.0.blocks.4.modulation.ln.bias", "layers.0.blocks.5.modulation.ln.weight", "layers.0.blocks.5.modulation.ln.bias", "layers.0.blocks.6.modulation.ln.weight", "layers.0.blocks.6.modulation.ln.bias", "layers.0.blocks.7.modulation.ln.weight", "layers.0.blocks.7.modulation.ln.bias", "layers.0.blocks.8.modulation.ln.weight", "layers.0.blocks.8.modulation.ln.bias", "layers.0.blocks.9.modulation.ln.weight", "layers.0.blocks.9.modulation.ln.bias", "layers.0.blocks.10.modulation.ln.weight", "layers.0.blocks.10.modulation.ln.bias", "layers.0.blocks.11.modulation.ln.weight", "layers.0.blocks.11.modulation.ln.bias".

It seems the architectures are different, is any code part out of date here please, I am still in the visualization.ipynb to run.
Thank you!
And also about the model choices:
I see the visualization in huggingface you shared last time is quite good of the attentions visualisation, the model behind should be 'focalnet_base_iso_16.pth' right? as I checked the files there and if I understand correctly.
If my focus is to generate attention scores for all pixels in images, what models do you recommend, if pre-trained model: focalnet_base_iso_16.pth is best/good?  or I'd better training one on my own data (mostly online advertisments images) based on some pre-trained-model? (It seems there is no way to evaluate the performance of attentions scores of the models except by eyes/intuitions.)
Sorry a bit long questions... Thanks a lot!
Best wishes,
Wen

got the answer, thanks.


Added Frameless

Thanks

Thanks
cc @stakes

That's the spirit @jayhickey @dkhamsing I'm much obliged :+1: :100:


Add new role users seeders for member, admin, superadmin

Go see the WIKI

Seeder OK. Was even able to login with created user.


Test TensorWaves on CPU cluster

Ongoing work by @Leongrim. We may have to look into mpi4jax.

Closed by #278, bug in ZenHub


Cache docker layers in CI build

This should speed up successive Docker image builds.

Which workflow is used for deployment? I'll copy this over.

I see the python-app-ci.yaml
It's not too much different to integrate it into a docker build command though you do have to change it to use docker buildx rather than docker build, which is pretty much the same.
I see the --no-cache option in the docker build command though:
docker build -f .github/workflows/interop/Dockerfile --no-cache -t ${{ env.GITHUB_REPOSITORY_NAME }}/keripy-interop:${{ env.CACHE_KEY_INTEROP }} .

Is the --no-cache necessary? If so then we can close this PR as caching would be irrelevant.


Feature Request: Ability to overlay Linechart on top of stacked bar chart

If there is already a way to do this, I sincerely apologize for wasting your time. I wasn't able to figure out how to get this to work though. Is there a way to make this chart today?

Hi @danconger thank you for your request. This suggestion has been surfaced several times already. We will take it into consideration in our next planning.

Hey @severinlandolt @mitrotasios If this is not picked yet. Can I look into this and raise the pull request?

I wanted to put my vote in for this feature. Any sense of where it fits into your current priorities, @severinlandolt?

would also love to have this, as we would use it to indicate certain limits that have been exceeded or not by a bar


About whether it is possible to annotate enum values？

Is this necessary? Is it more friendly to add comments to enumeration fields for future maintainers?
Because people like me who are new to this project may want to understand the function of this enumeration value, do I need to add a comment? If it is not necessary, just pretend I didn't say it.  😂

@aozeyu Of course you can, just do it and make your PRs, remember to use english and the code check-style when you add comments.

@love-star Ok, thanks for your reply, I thought I could add it 😂.

@garyli1019 perhaps this issue can be closed?


Upgrade windows Agent golang

In prep for steve we need to update the golang version for our build containers for the windows agent.

https://github.com/rancher/golang/pull/3

https://github.com/rancher/rancher/pull/25968

This task should fix https://github.com/rancher/rancher/issues/25948

@sowmyav27 You coudl consolidate issues if you'd like.

Verified on latest -master-head - commit id: 5ee70d014

Windows cluster is deployed successfully - 3 linux nodes - 1 etcd, 1 control plane and 1 worker node and 3 windows worker nodes.
command kubectl get all -A works. Output:

e.g. kubectl get all
> kubectl get all -A
NAMESPACE       NAME                                          READY   STATUS      RESTARTS   AGE
cattle-system   pod/cattle-cluster-agent-698d67bdd6-qb6wr     1/1     Running     0          27m
cattle-system   pod/cattle-node-agent-hjskj                   1/1     Running     0          27m
cattle-system   pod/cattle-node-agent-jvtj6                   1/1     Running     0          26m
cattle-system   pod/cattle-node-agent-rjr5x                   1/1     Running     0          27m
cattle-system   pod/cattle-node-agent-windows-7slnl           1/1     Running     0          23m
cattle-system   pod/cattle-node-agent-windows-gz77h           1/1     Running     0          23m
cattle-system   pod/cattle-node-agent-windows-tvqwm           1/1     Running     0          23m
ingress-nginx   pod/default-http-backend-67cf578fc4-pcrbj     1/1     Running     0          28m
ingress-nginx   pod/nginx-ingress-controller-l8xlm            1/1     Running     0          26m
kube-system     pod/coredns-7c5566588d-jh9n8                  1/1     Running     0          28m
kube-system     pod/coredns-autoscaler-65bfc8d47d-5j6kf       1/1     Running     0          28m
kube-system     pod/kube-flannel-8d8gt                        2/2     Running     0          28m
kube-system     pod/kube-flannel-kd7k2                        2/2     Running     0          26m
.......

Automation was run on windows.
workloads are deployed successfully.
Steve dashboard is enabled on windows cluster.


[stable/kiam] Update Kiam AppVersion

What this PR does / why we need it:
This PR will update Kiam AppVersion from 3.2 to 3.3
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] [DCO] signed
[X] Chart Version bumped
[X] Title of the PR starts with chart name

/assign @maorfr

/ok-to-test
/lgtm


"More Tweets" not being hidden again

This bug seems to be back: #97
As explained here https://github.com/insin/control-panel-for-twitter/issues/97#issuecomment-1213512040 this only seems to happen when I'm not logged in and the URL contains tracking information.
Settings:

Screenshot:

System: Windows 10
Browser: Firefox 110.0

This has been replaced with "Discover more", which we're currently able to hide and will keep fixing as Twitter changes break it


scanchain.v

1.) NUM_IOS is undefined when interface is declared. Suggest adding parameter in module definition.
module scanchain #(
parameter NUM_IOS = 8
)
2.) Add missing port connections to instances.
.VPB (1'b1),
.VNB (1'b0)

Yes, already fixed in an updated unreleased version
What missing connections ? All instances have that AFAICT.


fix numeric rule ordering

Numeric is used everywhere in the code and examples, but concat isn't numeric by default.

Will this not break the module for users that are using strings though?


"double free or corruption (out)" crash when calling clap_plugin->destroy()

When I call clap_plugin.destroy() one of these example plugins, I get a crash saying double free or corruption (out).
I've made sure that I'm only calling clap_plugin->destroy() once. I've tried some other clap plugins and they don't crash, so maybe it's something wrong with these plugins?

Hmm, is it necessary to call clap_plugin->stop_processing() before calling clap_plugin->destroy()?


Systest: update README

Motivation
I've noticed a few discrepancies when going through systest installation process. So here are a few changes to make this process cleaner.
DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

@evt do you want to merge it?

@evt do you want to merge it?

@dshulyak just added some more bits into README. Also shall we change limits like attached may be as long as tests work with them?

@evt sure lets decrease limits

bors try

bors merge

bors try

bors try

bors try

bors try

bors try

bors try

bors merge


No content for document https://kubernetes.io/docs/setup/independent/high-availability/#set-up-master-load-balancer

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
no content for https://kubernetes.io/docs/setup/independent/high-availability/#set-up-master-load-balancer
Proposed Solution:
Add content for https://kubernetes.io/docs/setup/independent/high-availability/#set-up-master-load-balancer
Page to Update:
https://kubernetes.io/docs/setup/independent/high-availability/#set-up-master-load-balancer

Is this a feature request or do you see a link somewhere for https://kubernetes.io/docs/setup/independent/high-availability/#set-up-master-load-balancer that directs to a location that has no content?

I change it to feature request. Also I think it is unclear for Setting up an HA etcd cluster section(because of no clear definition for step), I don’t understand the meaning of  For Option 2: you can skip to the next step.  Should I go to Acquire etcd certs section, or  should I go to Generate etcd client certs section?

/close
duplicate of #9034


disable multisig wallet functionality for goldchain accounts

Goldchain currently has no multisig wallet support yet. Please disable any multisig support for a logged in account in case the account.chain_type == "goldchain".
This means:

no multisig wallets that can be owned/created by the account
no multisig wallets that are shown on the account page
no multisig wallets in the address book
no multisig wallets as destinations
no multisig wallet transfer tab
... ?

> I can still add multisig wallet contacts in address book (So I imagine I also still see them appearing as well if I do)
Please remove multisig wallet functionality from address book (in frontend) as well. Thank you!


Profile performance [5]

Particular attention to be given to:

Firefox Seen non-responsive script errors. See https://github.com/modilabs/enketo/issues/453. XPath Evaluations are significantly slower in FF than in Chrome (checked in May 2013)
low-end mobile device such as the horrible Samsung Tab2. Obviously low-end devices are slower, but it would be interesting to see if the distribution of time per action is similar to desktop browsers or if particular operations are far more significant on a very low CPU/memory device. There are some indications that the latter may be the case, but it has never been tested.

profile the difference in speed between model.evaluate('/path/to/node', 'string', null, null, true) and model.node('/path/to/node').getVal()[0]
Same for model.evaluate('/path/to/node', 'node', null, null, true) and model.node('/path/to/node').get()

conclusion: seems worth it to replace $.fn.xfind with model.evaluate()


What do the loc layer and conf layer do??

I am newer in DL, please tell me the detail.

I am newer in DL, please tell me the detail.

The loc layer is the estimation of location layer, which outputs feature maps and its dim is
batch_size x dim x dim x number_of_prior_boxes_at_each_position *4
(4 means the x_min, y_min, x_max, y_max). The conf layer is the classification layer, which outputs the feature maps and its dim is
batch_size x dim x dim x number_of_prior_boxes_at_each_position * number_of_classes(including background)

@zieitokk So the loc layer and conf layer are the term of the SSD model, no the trick of coding or debugging?

Yes, they are included in the SSD model. Neither of them is the trick of coding or debugging.

@hahanigehaha233 can i ask you question?


fix typo in configuration.md

The file name is mistaken "yaml.epoch" should be "epoch.yaml".

@jur0  @zp-sd  Can we merge this ?

@mradkov merged, thanks!


How to build image directly from an existed Dockerfile with jib.

I already have a complex Dockerfile, but there is no docker daemon in my development environment. Converting Dockerfile to xml configuration is difficult work, but I also hope to use Dockerfile build image with jib without docker daemon.

It's hard to say without knowing what's in your dockerfile. Perhaps we will be able to help if you provide us with more information.
Jib does not build using dockerfile. It is a different build mechanism that produces container images.

Thanks, I don't know if there is a corresponding tool to directly convert the Dockerfile to jib configuration

There is not. Again, we cannot help you without more information.

I understand, thank you, I will try it myself


Targets file requires SolutionDir to be set

The targets file uses SolutionDir as the root to find the NuSpec files if there's nothing in the NuSpecFile ItemGroup.  In the MSBuild and CoreFx repos (and maybe others), we don't use a solution file for our command-line build, so this property isn't set.
If the SolutionDir property isn't set, it would be nice if the targets file would do something like just use the project folder or one level up from it.

Pull requests welcome ;)

Seriously though, what do you think are the best options -- you prob know MSBuild better than I do.... the only catch is that a full path is required, though ....\ should be ok.

I would use $(MSBuildProjectDirectory)\..\ if the SolutionDir isn't defined.  I don't think it needs to be a full path, but if it does need to be you can call Path.GetFullPath using this syntax:
$([System.IO.Path]::GetFullPath($(MSBuildProjectDirectory)\..\)

How many level's up should I search? And what's the best way? Multiple NuSpecFile  conditional on the previous one being blank?
It is just a default/convention; it can always be directly specified.

Since it's just the default, I would go with just one level up until someone else complains :-)

fixed in 1.3.2


ARROW-833: [Python] Add Developer quickstart for conda users

cc @mrocklin @cpcloud, would you mind giving this a shot to make sure I haven't missed anything idiosyncratic from my environment?

I was able to copy-paste my way through this in a little under 2 minutes; let me know if you run into any problems.

Probably want to move this to Sphinx once we set up our publishing toolchain to arrow.apache.org

+1. It would be good if we can expand this document with:

Development lifecycle tips (e.g. maybe a file with some bash functions for automating various toolchain update steps)
Building on Windows (as part of ARROW-734 and followups)


[BUG] Deleted backup because of a recurring backup scheduled is seen in backuplist page

Describe the bug
Deleted backup because or a recurring backup scheduled is seen in backuplist page
To Reproduce

Enable recurring backups for a volume. - retention count is 2 (backupstore - S3)
Navigate to the backup list page, in a couple of minutes
3 backups will be available - b1, b2, b3 (if the timing is right, i.e. user navigates to backuplist page when the creation and deletion of a backup is happening because of the scheduled recurring backup , ideally b3 - should be deleted)
Restore option is enabled for b3.
When a user tries to restore from this backup b3, user sees a 502 error
When the user navigates to Backup page and naviagtes back to the backup list page for the volume, the backup b3 is not available anymore.

Expected behavior
Deleted backups should not be listed in the backuplist page, it gives an incorrect impression to the user that, the particular backup is available for restore.
Environment:

Longhorn version: master - 05/27/2020
Kubernetes version: 1.17.5
Node OS type and version: 18.04 linux

Can it be just b3 was deleted a moment later? The result is the real-time result from the S3. We don't have cache.

Snapshots section in volume details page, refreshes when an event like creation of a recurring snapshot or deleting a recurring snapshot, automatically and does NOT require a hard refresh of the page. We can have a similar behavior for the backups.

@sowmyav27 it cannot be done for the backup page since the mechanism you mentioned is implemented by using WebSocket and event notification from Kubernetes CRD changes. We don't have CRDs for backups. We are polling backups instead of waiting for the event at this moment.

remove stale due to the incorrect exempt label

We've Backup CRD #1761 from v1.2.0.
This issue could be closed.
cc @innobead


Add capability to hudl-flash.sh to automate move to 'flash' mode

If the Huddle has USB debugging enabled and the host has adb installed then hudl-flash.sh should use adb reboot bootloader to put the attached Hudl into the state ready to flash.

'command -v adb` to discover the path to adb, if it is installed (builtin in both bash (ubuntu) and ash (tce), our 2 targets)

try_adb=1
echo "Waiting for a connected Hudl in flash mode ..."
while ! lsusb -d 2207:310b 1>/dev/null 2>&1
do
        lsusb -d 0e79: 1>/dev/null 2>&1
        if [ $? -eq 0 ]
        then
                if [ $try_adb -eq 1 ]
                then
                        # See if we can use adb to put us in flash mode:
                        echo "Trying to reboot Hudl into flash mode using adb (needs USB debugging enabled)."
                        echo "If this fails then do it manually by holding vol+ and pressing reset."
                        adb reboot bootloader
                        # TODO Should check for availability of adb command, and shoudl catch failure here
                        sleep 5
                fi
                try_adb=0
        fi
done
echo "Hudl in flash mode, starting to flash ..."


Close event for sockets

Is there a close event one can react to? For instance to notify other participants in a chat that someone lost the connection?

Hi @AuspeXeu,
Yes, the socket type used in this library is this one, meaning that you should be able to subscribe to the 'close' event in the same way that you subscribe to 'message' events.

@HenningM works like a charm, thanks a lot!


Unable to add class on input

I am trying to add a class on input so I did as you wrote in docs but the class I am trying to apply is always being applied on the parent div.
<autocomplete-vue
       id="getProducts"
       placeholder="Autocomplete"
       :list="{{ $productList }}"
       requestType="get"
       :property="'title'"
       :inputClass="'form-control'"
></autocomplete-vue>

I solved this by using the following
input-class="form-control"


Chatterino blocked users problem

Checklist

[X] I'm reporting a problem with Chatterino
[X] I've verified that I'm running the most recent nightly build or stable release
[X] I've looked for my problem on the wiki
[X] I've searched the issues and pull requests for similar looking reports

Describe your issue
there is a limit of 100 blocked accounts that chatterino saves, when I restart chatterino, every account that Ive blocked other than the 100 that are already saved gets unblocked in chatterino but are still blocked on my twitch account.
I am using the 7tv version but it did the same exact thing on 2.3.5
Screenshots
No response
OS and Chatterino Version
Chatterino 7.3.5 (commit 132b406cc) on Windows 10 Home 21H1 19043.1645

duplicate of #2767

Duplicate of #2767


Add a testing option to end-to-end tests to clear the search path for all tests so that we have search-path-independence tested throughout

https://github.com/timescale/promscale/pull/707#pullrequestreview-716511911

@jgpruitt the PR linked above was merged a while ago. Is there more work left?

@ramonguiu yes. The linked PR fixed a few known bugs. This issue is a reminder to enhance our tests to catch any future bugs of the same kind that might get introduced


Update concept-metrics.md

@bjqian : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[WIP] Multi-Module repo

Signed-off-by: Artem Belov<EMAIL_ADDRESS>Description
Make multi-module repository to have minimal dependencies for clients.
https://github.com/golang/go/wiki/Modules#faqs--multi-module-repositories
Motivation and Context
#1577
How Has This Been Tested?

[ ] Covered by existing integration testing
[ ] Added integration testing to cover
[ ] Tested locally
[ ] Have not tested

Types of changes

[ ] 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 not work as expected)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

@nickolaev Could you have a look here?


[SPARK-30815][SQL] Add function to format timestamp with time zone

What changes were proposed in this pull request?
Whenever timestamps are turned into strings (Column.cast(StringType), date_format(timestamp, format), Dataset.show()) the default time zone is used to format the string. This default time zone is either the java default zone user.timezone, the Spark default zone spark.sql.session.timeZone or the default DataFrameWriter zone timeZone. Currently there is no way to format a single column in a different timezone.
scala> spark.conf.set("spark.sql.session.timeZone", "Europe/London")
scala> spark.range(10). \
         select(concat(lit("2020-02-01 0"), $"id", lit(":00:00")).cast(TimestampType).as("time")). \
         select(
           $"time",
           date_format($"time", "uuuu-MM-dd HH:mm:ss ZZZZZ").as("local"),
           date_format_tz($"time", "uuuu-MM-dd HH:mm:ss ZZZZZ", "Europe/Berlin").as("Berlin")
         ). \
         show(false)
+-------------------+---------------------+--------------------------+
|time               |local                |Berlin                    |
+-------------------+---------------------+--------------------------+
|2020-02-01 00:00:00|2020-02-01 00:00:00 Z|2020-02-01 01:00:00 +01:00|
|2020-02-01 01:00:00|2020-02-01 01:00:00 Z|2020-02-01 02:00:00 +01:00|
|2020-02-01 02:00:00|2020-02-01 02:00:00 Z|2020-02-01 03:00:00 +01:00|
|2020-02-01 03:00:00|2020-02-01 03:00:00 Z|2020-02-01 04:00:00 +01:00|
|2020-02-01 04:00:00|2020-02-01 04:00:00 Z|2020-02-01 05:00:00 +01:00|
|2020-02-01 05:00:00|2020-02-01 05:00:00 Z|2020-02-01 06:00:00 +01:00|
|2020-02-01 06:00:00|2020-02-01 06:00:00 Z|2020-02-01 07:00:00 +01:00|
|2020-02-01 07:00:00|2020-02-01 07:00:00 Z|2020-02-01 08:00:00 +01:00|
|2020-02-01 08:00:00|2020-02-01 08:00:00 Z|2020-02-01 09:00:00 +01:00|
|2020-02-01 09:00:00|2020-02-01 09:00:00 Z|2020-02-01 10:00:00 +01:00|
+-------------------+---------------------+--------------------------+

Why are the changes needed?
Formatting timestamps in timezones other than the default one requires a laborious UDF while a very similar operation date_format with all the code exists already.
Does this PR introduce any user-facing change?
Yes, it introduces a new SQL operation date_format_tz. I could not get the existing date_format take an optional third tz argument.
How was this patch tested?
Unit tests.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

This also holds for date_format, still it exists. This should be added for the sake of completeness.

Can one of the admins verify this patch?

I'm interested in getting this PR in. Although its absolutely true that it can be done as @MaxGekk suggests with a Scala UDF, the same does not apply in SQL.

@aray @EnricoMi @MaxGekk How about the other data processing/management systems? Do they have the built-in functions that provide the same functionality?

There is a comparable function in BigQuery:
FORMAT_TIMESTAMP(format_string, timestamp[, time_zone])
see
https://cloud.google.com/bigquery/docs/reference/standard-sql/timestamp_functions#format_timestamp


Orbit example in Docs requires Motion UI which is not included in Foundation CSS CDN (Leads to confusion)

Was helping a newbie learn to make websites and she had trouble getting Orbit to work because of unclear documentation.
She did the initial setup from the docs but the Orbit carousel wasn't working because it required the Motion UI CSS package (which as far as I could tell was not explicitly mentioned in the instructions on the Foundation Installation Docs page - there were just links to the CDN for foundation.min.js and foundation.css.
I'm recommending that Motion UI CSS gets added to the instructions on how to setup Foundation.

How can we reproduce this bug?
1.Follow the instructions on the Foundation Installation Docs
2. Copy and paste the Orbit Example Code
3. Load the page
What did you expect to happen?
You will expect to have a working carousel as in the docs
What happened instead?
Instead you will find that the carousel doesn't work. It doesn't go past second slide.
Test case:
http://codepen.io/anon/pen/reqqVv

Added a PR: https://github.com/zurb/foundation-sites/pull/8710

Thanks to @seanmavley this docs fix has now been merged.


Account Types disappear after creating a new account

Navigate to Payment entry page
Click add account button
Complete the add account form
Submit
Re-open the add account dialog
Expand Account Type

Expected: All account types are populated in the dropdown
Actual: Only cash shows in the dropdown

Can i take this Up if it's not already being worked by someone?

Can i take this Up if it's not already being worked by someone?

Hi there.  Sorry for the delayed response.  You are welcome to take this one.  Thanks for your willingness to do so.

Thanks, I’ll work on this😊


useCookieValue Storybook example is broken

What docs page needs to be fixed?

Section:

Page:
https://react-hookz.github.io/web/?path=/docs/side-effect-usecookievalue--example

What is the problem?
It's crashing
 TypeError: Object(...) is not a function
What should be changed to fix the problem?

looks like it's broken again

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


No tests currently working on pd 0.54-1

Hello,
I am trying to run the shipped tests on pd-0.54-1 but none of them work. I have no idea why. I am wondering if this is as a result of a change in PD as of 0.51 (see picture below).

Many thanks,
Nakul

I have been working on updating the code to be compliant with modern javascript. I think the next step is to create a corresponding patch in PureData and then we'll have the complete External, just like NodeForMax!

I figured out why the tests weren't working...Now I'm working on improving code.

I figured out why the tests weren't working

please comment what the issue was in case anyone else runs into this.


Updating a comment does not show an error when an error is thrown

Testing #59278
Throw an error in editComment method and Update comment in the UI does not show the error
'use strict';
// The module 'vscode' contains the VS Code extensibility API
// Import the module and reference it with the alias vscode in your code below
import * as vscode from 'vscode';

// this method is called when your extension is activated
// your extension is activated the very first time the command is executed
export function activate(context: vscode.ExtensionContext) {

    const _onDidChangeDocumentCommentThreads = new vscode.EventEmitter<vscode.CommentThreadChangedEvent>();

    vscode.workspace.registerDocumentCommentProvider({
        onDidChangeCommentThreads: _onDidChangeDocumentCommentThreads.event,
        provideDocumentComments: async (document: vscode.TextDocument, token: vscode.CancellationToken): Promise<vscode.CommentInfo> => {
            return {
                threads: [{
                    threadId: '1',
                    resource: document.uri,
                    range: new vscode.Range(new vscode.Position(0, 0), new vscode.Position(0, 0)),
                    comments: [{
                        commentId: '1',
                        body: new vscode.MarkdownString('hello world'),
                        userName: 'me',
                        gravatar: '',
                        canEdit: true,
                        canDelete: true
                    }]
                }],
                commentingRanges: []
            }
        },
        createNewCommentThread: async (document: vscode.TextDocument, range: vscode.Range, text: string) => {
            throw new Error('Not implemented');
        },
        replyToCommentThread: async (document: vscode.TextDocument, range: vscode.Range, thread: vscode.CommentThread, text: string) => {
            throw new Error('Not implemented');
        },
        editComment: async (document: vscode.TextDocument, comment: vscode.Comment, text: string, token: vscode.CancellationToken) => {
            throw new Error('Not implemented');
        },
        deleteComment: async (document: vscode.TextDocument, comment: vscode.Comment, token: vscode.CancellationToken) => {
            return null;
        }
    });
}

// this method is called when your extension is deactivated
export function deactivate() {
}

Same with delete comment

Duplicate of https://github.com/Microsoft/vscode/issues/59348, this should already be fixed - what version of insiders are you using?

You are right. I was on one day old version in linux. Closing this.


Select All should select content of focused text input

Currently, Ctrl-A appears to always select the entire page contents, but I believe users would expect a special case when a text input is focused, as is the case in other browsers.

Fixed by #1284


fix: TopicMessageQuery#unsubscribe() attempts to re-subscribe

🆕🐥 First Timers Only
This issue is reserved for people who have never contributed to Hedera or any open source project in general.
We know that creating a pull request (PR) is a major barrier for new contributors.
The goal of this issue and all other issues labeled by 'good first issue' is to help you make your first contribution to Hedera.
👾 Description of the issue
Problem
When using TopicMessageQuery to subscribe to a topic and then attempting to unsubscribe, an error is thrown that suggests the system is trying to re-subscribe rather than cleanly disconnect:
  const subscription = new TopicMessageQuery()
    .setTopicId(topicId)
    .subscribe(client, myCallback);
  subscription.unsubscribe();

This results in the following error:
Error subscribing to topic 0.0.3745107 during attempt 0. Waiting 250 ms before next attempt: 1 CANCELLED: Cancelled on client

The expected behavior is that unsubscribe() should terminate the subscription without attempting a re-subscription. This error likely affects users working on subscribing to topics in the Hedera network and needs a fix to ensure proper subscription management.
Steps to reproduce

Set up this project
Execute the script provided in the repo, located at: checkpoint-subscribe.js.

Expected Behavior
unsubscribe() should end the subscription without attempting any further reconnection attempts or retries.
Additional context

Relevant discussion can be found in the Slack thread: TopicMessageQuery Conversation

Hedera network
testnet
Version
2.42.0
Operating system
macOS
📋 Step by step guide to do a contribution
If you have never contributed to an open source project at GitHub, the following step-by-step guide will introduce you to the workflow. More information and concrete samples for shell commands for each step can be found in our CONTRIBUTING.md file.
A more detailed general documentation of the GitHub PR workflow can be found here.

[ ] Claim this issue: Comment below that you are interested in working on the issue
[ ] Wait for assignment: A community member with the given rights will add you as an assignee of the issue
[ ] Fork the repository: You can do that in GitHub (by simply clicking the 'fork' button).
[ ] Check out the forked repository
[ ] Create a feature branch for the issue. We do not have a hard naming definition for branches but it is best practice to prefix the branch name with the issue id.
[ ] Solve the issue in your branch.
[ ] Commit your changes: Here, it is needed to add sign-off information to the commit to accept the "Developer Certificate of Origin" (https://developercertificate.org). More details can be found in our CONTRIBUTING.md
[ ] Start a Pull Request (PR): We have a pattern for naming pull requests that a GitHub Action checks. We use that pattern to support the creation of automatic release notes.
[ ] Check GitHub Actions: Several GitHub Actions will be triggered automatically for each PR. If a GitHub Action fails and you do not understand the cause of that error do not hesitate to add a comment to the PR and ask the Hedera developer community for support.
[ ] Wait for reviews: Members of the Hedera developer community will review your PR. If a reviewer finds any missing pieces or a problem, he or she will start a discussion with you and describe the next steps for solving the problem.
[ ] You did it 🎉: We will merge the fix in the develop branch. Thanks for being part of the Hedera community as an open-source contributor ❤

🎉 Contribute to Hacktoberfest
Solve this issue as part of the Hacktoberfest event and get a chance to receive cool goodies like a T-Shirt. 🎽
🤔 Additional Information
If you have any questions, just ask us directly in this issue by adding a comment. You can join our community chat at Discord. A general manual about open-source contributions can be found here.

Hey @bguiz, the linked file checkpoint-subscribe.js is broken. Did you mean checkpoint-04-subscribe.js?  Kindly update on how to replicate the issue

Can I work on this issue?

Can I work on this? I have never contributed to an open-source project before.

Hey @bguiz
I would like to work on this issue

Hey @hendrikebbers i have an update regarding the issue
i tested various scenarios and i think its working okay

this is the screenshot of the output
the error due to continue subscribe process is not coming
is there anything else to do?
Thankyou .

Hi @Manav958, in order to reproduce it, can you test this snippet against testnet, at the end you should receive
Error subscribing to topic 0.0.4963755 during attempt 0. Waiting 250 ms before next attempt: 1 CANCELLED: Cancelled on client

Hey @agadzhalov i tested the snippet and after 3 messages got sent it threw this error.
what further steps should i take?

Hi @Manav958, the expected result is to fix the bug and at the end the error not to be thrown. As a hint you can spend more time looking in the different Topic classes, also you can investigate the subscribe and unsubscribe methods.

The expected behavior is that unsubscribe() should terminate the subscription without attempting a re-subscription

Ok ,
I am improving on it

Hi all,
@Manav958, thank you for the effort. I like how you ask questions. Go forward.
@Jexsie, It Looks like you created a PR without being assigned to the issue. Please always make sure that you are assigned. Otherwise, two people will work on the issue.
I can not say if the PR by @Jexsie fixed the complete issue. Here I would like to hear @agadzhalov
If it fixes all we will find a good other issue for @Manav958 Otherwise we can merge it and let @Manav958 do the rest of the work. By doing so you both did a PR :)

Thank you @hendrikebbers .
If @Jexsie agrees we can work together on the issue , two better than one.

Hi @Manav958 @hendrikebbers. I've just tested @Jexsie's fix and seems to be working as expected. So may be @Manav958 can focus on some other good first issues


[clkmgr] Fix documentation ambiguity around clock switching

Documentation fix specifically for clkmgr in #9273
This PR is dependent upon the changes in #9347

Signed-off-by: Timothy Chen<EMAIL_ADDRESS>

updated! please have a look.


Divide configuration and model

Currently the model contains 1) the slides themselves and 2) the configuration, which mostly consists of functions.
Both 1 and 2 should be removed from the model, so that:

the model is cleaner and more debug-friendly
a live slide editor can be implemented more consistently

These will be breaking changes, so I'll implement these with Elm 0.18, when people have to update their code anyway.

Closed by https://github.com/xarvh/elm-slides/pull/3


chat history from barcelona-js/gitup

@trevorah any way to recover?

We need to properly solve this via https://github.com/gitterHQ/gitter/issues/153, but we can migrate them over with our handy dandy script for now.

done!

woop - nice work


Support JWT Token Authentication in Support Dashboard

Is your feature request related to a problem? Please describe.
Dashboard does not support authentication using JWT token
Describe the solution you'd like
We can support JWT token authentication for the dashboard.

https://github.com/apache/pulsar/pull/3945


clear operation times out in Workbench

Observed in M1 build: the clear operation in the workbench times out and eventually fails with an "unregistered transaction" error.

This issue duplicates #91