Update fastutil to 8.5.3

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "it.unimi.dsi", artifactId = "fastutil" } ]

labels: library-update, semver-minor

Superseded by #130.


IngestPrefix is added twice

https://github.com/Azure/azure-kusto-spark/blob/4b0c07b23ecc57ea4640730cdf24d7765e41c1ab/connector/src/main/scala/com/microsoft/kusto/spark/utils/KustoDataSourceUtils.scala#L298-L300
It seems as if the IngestPrefix check is not negated here, the IngestPrefix is added when it is already present. Should it be added at all?
I have a an error where I get:
AADSTS500011: The resource principal named //ingest-ingest-<cluster>.westeurope.kusto.windows.net was not found
Note the double "ingest-",  which I suspect is originating from this or something similar.
I'm probably misunderstanding what the EngineUrl is supposed to be.

hi
engine url is without the ingest-
the engine url is used to query and issue commands on tables
ingest url is used for ingestion

So then that function (getEngineUrlFromAliasIfNeeded) is wrong? Since it's adding the IngestPrefix, instead of removing it.

right

for now please remove the "ingest" from the url yourself


Instant View Issue: Unable to follow links in 'https://t.me/iv?url=' format

https://github.com/UnigramDev/Unigram/issues/2820

This should be fully supported in TDLib 1.8.7.


Update the value of the grounded_configuration global variable

after the reconfiguration is successful the grounded_configuration global variable should be updated to the new value

I've added the lock to solve the error from the reasoner to this PR


feat(README.md): add install method for nix users

Hello!
This plugin is really fun and works perfect! Thanks.
I added an installing description for NixOS user!

Hey, appreciate the contribution but I don't think this is necessary. Does it only work on NixOS if you use the nix develop command?

No, but it is great because I don't install rust globally.
This instruction is similar to this plugin https://github.com/eraserhd/parinfer-rust#vim-plug
As you use nix in this repository, this is good instruction I think

I believe Nix support was introduced in #96 - doesn't that already cover setting up Rust in the project? I haven't used NixOS myself, so I'm unsure if it's indeed a good approach. I'd rather not to add extra stuff to the README unless absolutely necessary.
Not everyone uses Nix or even Linux, so it seems a bit excess to include those steps for every installation option, which I plan to extend in the near future.

It's your OSS, so you don't like it close it.

It's your OSS.
If you don't like this PR, I don't care, just close it.
I'm so sorry that I send a PR which is not following your preference.


[type:fix]Fix namespace plugin enable switch

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

related #5717


react-navigation v6にバージョンアップ

対応内容
v5系からのマイグレーション
https://reactnavigation.org/docs/upgrading-from-5.x/

Found screens with the same name nested inside one another. Check:

Home, Home > Home

This can cause confusing behavior during navigation. Consider using unique names for each screen instead.
at node_modules/@sentry/utils/dist/instrument.js:111:20 in <anonymous>
at src/Router.tsx:5:0 in <global>
at node_modules/@react-navigation/core/src/useOnAction.tsx:135:9 in React.useCallback$argument_0

たぶん、これを使う
https://reactnavigation.org/docs/upgrading-from-5.x/#new-group-component


[feature] Internationalization support (English)

Users should be able to choose English as their preferred language and the webpage should be in english

[http://p-o.co.uk/tech-articles/howto-multilingual-website-with-pythons-django-and-mezzanine/](Howto Multilingual Website with Django and Mezzanine)

Zanata project


ONNX and TensorRT conversion

Hi, I'm trying to convert a SlowFast pytorchvideo model to ONNX and TensorRT to get faster real time speed on embedded platforms, does pytorchvideo currently support this? If not, how should I write a convert script for ONNX? Thank you!

Hi, I'm trying to do the same with the X3D_S model! My goal is to convert the model to OpenVINO. The first step is to convert it to ONNX. When I try it I get the error:
RuntimeError: ONNX export failed: Couldn't export Python operator SwishFunction

@MGReyes seems like this repo doesn't support exportable version of SwishFunction, see this https://github.com/lukemelas/EfficientNet-PyTorch/blob/master/efficientnet_pytorch/utils.py and https://github.com/lukemelas/EfficientNet-PyTorch/blob/master/efficientnet_pytorch/model.py where they implemented a swish function for export.

@MGReyes or you can change swish function to RELU or sth https://github.com/dusty-nv/jetson-inference/issues/1199

@MGReyes would you mind sharing your onnx conversion script?

@namKolorfuL I replaced SwishFunction by nn.SiLU and convert successfully, but my trt model is slower than torch model about 4 time. Did you convert successfully, how about speed of your trt model or onnx model?

@hongsamvo did you convert and infer the model on the same jetson/pc? It has to be on the same device or the performance will suck. Btw, did you add fp16 flag during the trt conversion?

@namKolorfuL yes, I convert and infer x3dm on the same jetson NX, pytorch take ~70-80ms, and trt take ~380ms, I have tried fp16 but I don't see the improvement.


Stream upload from user to S3

Unsurprisingly, trying to upload a large file causes the service to crash since it runs out of memory. Should be streaming the file from the user to S3 and not pulling it all into memory to do that.

#26 was a lie or this has started to happen in a whole new way


upgrade to slf4j 2.0.12

https://www.slf4j.org/news.html

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (59551e4) to head (0e2df8a).
Report is 186 commits behind head on master.

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #12761       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436     2387       -49
  Lines        133233   130982     -2251
  Branches      20636    20289      -347
=============================================
- Hits          82274        0    -82274
- Misses        44911   130982    +86071
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
?

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
0.00% <ø> (-61.75%)
:arrow_down:

skip-bytebuffers-true
?

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

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

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


Parse https m3u files

Could you elaborate on this? I'm not sure what you're asking.

Closing due to lack of response.


Auto Bug

when enabling auto and starting a map, it is still possible to ruin auto by spamming z and x

(auto was on for this play)

Yeah thats a problem, i recently disabled moving the mouse with auto but ill make a change to prevent mouse clicks as well

Disabled user control of keyboard if using auto mods
Resolved in v0.13.0b

Could you put a switch in settings that allows you to actually ruin the gameplay to make it believable? I have friends that have never seen osu! and i want to impress them.

so you'd like an option for slightly random gameplay to look like a player is playing?

Sorry for the late reply but yes


Packge pak.datasets.EPFL_Campus

Dear @jutanke ,
Thanks for sharing one of your great work.
I would like to ask for the package pak. How can I install this package?
Thanks so much for your time.

Dear @jutanke ,
I have found here: https://github.com/jutanke/pak
Thanks.


If None is provided as command prefix for commands.Bot it should suppress the warning as well

Summary
If None is provided as command prefix for commands.Bot it should suppress the warning as well
What is the feature request for?
disnake.ext.commands
The Problem
Let's assume there's a bot that works entirely on slash commands and doesn't need to access messages content so doesn't have message_content intent enabled. If the command prefix is None meaning it is not supposed to scan messages contents for prefixes there would be a warning telling that "Prefix is configured but message_content intent is not enabled, provide commands.when_mentioned to suppress this warning". And this is what doesn't make any sense in this situation. None basically means "no prefix", not an empty string, just no prefix at all, while commands.when_mentioned is actually a prefix function which means "this bot uses prefix".
The Ideal Solution
I think it would be better to check for None instead of checking for when_mentioned
https://github.com/DisnakeDev/disnake/blob/6769f80d5ad346752777755cf006031928d80767/disnake/ext/commands/bot_base.py#L154-L157
it would check
if (
    command_prefix is not None
    and not self.intents.message_content  # type: ignore
):

The Current Solution
Described in The Problem
Additional Context
I am not so sure what exactly providing None as command_prefix does but there's no mention of it in documentation, so I think the documentation should also be updated

Thanks for the report! While this is a minor bug and will be fixed by #689, the proper solution in most cases is using InteractionBot or AutoShardedInteractionBot - those are essentially drop-in replacements for their Bot and AutoShardedBot counterparts, but without any of the prefix command handling code, which should be what you're looking for.


additionalFields are not inferred if BetterAuthOptions are extracted

It is not possible to extract BetterAuthOptions and have additionalFields inferred in the user type.
working:

export const auth = betterAuth({
  user: {
    additionalFields: {
      example: {
        type: "string",
      },
    },
  },
  [... more config]
});

export const getServerAuthSession = () =>
  auth.api.getSession({
    headers: headers(),
  });

type GetServerAuthSessionResult = NonNullable<
  Awaited<ReturnType<typeof getServerAuthSession>>
>;

type _test = Expect<ToHaveKey<GetServerAuthSessionResult["user"], "example">>; // true

In the below example instead, additionalFields are not inferred.

const user:BetterAuthOptions["user"] = {
  additionalFields: {
    example: {
      type: "string",
    },
  },
}

export const auth = betterAuth({
  user: user,
  [... more config]
});

export const getServerAuthSession = () =>
  auth.api.getSession({
    headers: headers(),
  });

type GetServerAuthSessionResult = NonNullable<
  Awaited<ReturnType<typeof getServerAuthSession>>
>;

type _test = Expect<ToHaveKey<GetServerAuthSessionResult["user"], "example">>;  // false

I am using MacOs
project is Nextjs + TRPC + drizzleORM
Also I am running on  0.4.12

typescript will not infer types like that since the default will be cased. If you need to extract the options make sure, to use satisfies instead.
const options = {
   //your config
} satisfies BetterAuthOptions


:pencil2: improve documentation waf rules

:tada: This PR is included in version 1.3.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update summary.R

Hi Ciro!
When we run this pipeline with just one library got this error:
Error in rownames<-(*tmp*, value = c("AAACCCAAGACATAAC-1", "AAACCCAAGCGTTACT-1",  :
attempt to set 'rownames' on an object with no dimensions
As the library is just one, the command "extra_meta_donor_e <- extra_meta_donor[meta_donor$donor, ]" returns just one vector, and in the line below  "rownames" can't assign the names because there aren't rows. Make the object a dataframe solves this problem and we think doesn't affect if there are more libraries.

Thank you, Emmanuel!
I made a less disruptive change by using df[, , drop = FALSE] instead of data.frame().
I am still not convinced this is the explanation because this table is regarding donors, no libraries.


problem with ingrass nginx Grafana , If you're seeing this Grafana has failed to load its application files

I have this message
If you're seeing this Grafana has failed to load its application files

1. This could be caused by your reverse proxy settings.

2. If you host grafana under subpath make sure your grafana.ini root_url setting includes subpath

3. If you have a local dev build make sure you build frontend using: yarn start, yarn start:hot, or yarn build

4. Sometimes restarting grafana-server can help

ingress:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    ingress.kubernetes.io/force-ssl-redirect: "true"
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/rewrite-target: /$1
  creationTimestamp: "2020-02-19T09:44:24Z"
  generation: 14
  labels:
    app: grafana
    chart: grafana-4.3.2
    heritage: Helm
    release: monitor
  name: monitor-grafana
  namespace: monitoring

spec:
  rules:
  - host: ****.com
    http:
      paths:
      - backend:
          serviceName: monitor-grafana
          servicePort: 3000
        path: /grafana/?(.*)
status:
  loadBalancer: {}

with :

grafana.ini:
     [server]
         root_url = %(protocol)s://%(domain)s:%(http_port)s/grafana/

where is the problem?!

Im having the same issue

Im having the same issue

Just add this to the grafana.ini file
[server]
root_url = "https://<YOUR_DOMAIN>/grafana"
domain = "<YOUR_DOMAIN>"

We attempted that to no success @waelghaith97. We ended up taking everything down and creating it again, that fixed the issue.


Invalid attributes added to generated JSON

I have noticed that in version 3.3.1 it seems all the values, whether I've explicitly specified or not, are generated for the parameters block. This isn't a bad thing in general, but it is generating invalid JSON for the OpenAPI 3.1 schema. Specifically, the parameters allowEmptyValue and allowReserved are generated for parameters with "in": "path" but these parameters are only valid for query parameters. I feed this generated API into Readme which raises these validation errors.
For example:
"parameters" : [ {
          "name" : "ownerId",
          "in" : "path",
          "description" : "The id of the owner",
          "required" : true,
          "deprecated" : false,
          "allowEmptyValue" : true,
          "explode" : false,
          "allowReserved" : true,
          "schema" : {
            "title" : "String",
            "type" : "string"
          }
        } ],

Relevant parts of the OpenAPI 3.1 spec:

There's another syntax error in the generation I'm working through. This is an invalid schema name (can't have brackets). Suggestion would be to replace this name with "kotlinArrayString". I am going to try doing this on my side but I think it should generate correctly by default.
"kotlin.Array<kotlin.String>" : {
        "title" : "Array<String>",
        "required" : [ "size" ],
        "type" : "object",
        "properties" : {
          "size" : {
            "title" : "Int",
            "type" : "integer",
            "format" : "int32"
          }
        }
      },

@SMILEY4 wondering if you have any thoughts on the above. Thanks!

Hi, thank you for reporting these issues.
i just created version 3.4.0 that should fix both of these problems.
The problematic attributes are removed by default and I added options to customize the name/path of the schemas more easily. There are also new options for schema paths and titles that are valid for openapi - for paths this is now the default. (see https://github.com/SMILEY4/schema-kenerator/releases/tag/1.2.0

Amazing - thank you! I'll give this a try and report back.


Staging branch to merge main into develop

This is a staging branch to merge main into develop

Conflicts resolved in https://github.com/voxel51/fiftyone/pull/3954.


FunctionType.instantiate doesn't handle generic typedefs properly.

Consider the following typedef:
typedef F<T> = T Function<U>(U p);

If an analyzer FunctionType is created for F using the FunctionTypeImpl.forTypedef constructor, and then that type is instantiated using .instantiate([objectType]), the resulting type is (U) -> Object.  This is a nonsense type since it refers to the free type variable U.
One might argue that it doesn't really make sense to try to create FunctionType objects for typedefs like F, because F doesn't represent a type at all; it represents a thing that can be instantiated to form a type (languages like Haskell call this a "type constructor").  But the analyzer does create such a type when building the element model, so it seems like it should behave sensibly.  And IMHO the only sensible way for it to behave is for the result of .instantiate([objectType]) to be <U>(U) -> Object.
Note: this is a bug in the analyzer API, not a bug in the analyzer's analysis of source code.  If the user actually writes F<Object> in their source code, the analyzer manages to instantiate it properly to <U>(U) -> Object.

I believe this is fixed now, with strict FunctionType(s).


feat: add ELO Chess Club place

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
298

Relevant Lines:
456

💛  - Coveralls


fix fix two problems for force_olap_table_replication_allocation

follow https://github.com/apache/doris/pull/32916
there are two problem:

create table failed while only dynamic_partition.replication_num is set,
normal user(exclude root and admin) can not read and write, because of there default resource_tag.location = default

Proposed changes
Issue Number: close #xxx

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

run buildall

run cloud_p1

run cloud_p1


ClassificationRequest.imageCropAndScaleOption = VNImageCropAndScleOption.centerCrop

Can't compile code.
I get Type 'VNImageCropandScaleOption' has no member 'centerCrop' I added the inceptionV3Model model

Hi @kerinzeebart ,
Which XCode Beta are you using?

It appears that: Xcode 9 beta 1 and Xcode 9 beta 2 - both use
"VNImageCropAndScaleOptionCenterCrop" instead of "VNImageCropAndScleOption.centerCrop"
changing to that should fix it. Again, this is all experimental beta code currently.


Power isolation needed when wireless

At the moment the assumption is that the servos run off 4xAA batteries (ish 6v) and that any arduino is tethered and as such it, plus any sensors run off 5V usb.
I noticed at CampJS that when running an arduino + motors + bluetooth all off the battery pack that current draw on the servos would occasionally reset the arduino. This obviously got worse as the battery discharged.
Suggestion then on having 2 supplies when in "wireless" mode to supply the MCU + sensors and then the main pack for the servos / motors. Other than that, doing some kind of supply filter stuff to smooth out any drops.
Would be good to get opinions on this; ping: @nog3 @geekscape

:+1:
I think this is why, once I connected the wireless to my simplebot, it would only respond for a very short time before (I assume) resetting.

Yep I think for next time we'll have a look at some other battery
options... We've always shied away from lipos because peeps don't generally
have balancing chargers but we'll see what paths we can go down.
On Sun, Jul 26, 2015 at 9:32 AM tommy-carlos williams <
<EMAIL_ADDRESS>wrote:

[image: :+1:]
I think this is why, once I connected the wireless to my simplebot, it
would only respond for a very short time before (I assume) resetting.
—
Reply to this email directly or view it on GitHub
https://github.com/nodebotsau/simplebot/issues/3#issuecomment-124914467.


Error: [contenttweaker]: Error executing {[0:contenttweaker]:ContentTweaker.zs}: null

While I was using Contenttweaker i made an item with an IItemUse function and got this error message:
Error: [contenttweaker]: Error executing {[0:contenttweaker]:ContentTweaker.zs}: null
ErroredScript.txt
What does this mean?

The stack trace below that line in the creafttweaker.log explains the error. Please include your crafttweaker.log file.

java.lang.NegativeArraySizeException
probably is not workin because of pos.getOffset("south", -1);
crafttweaker.txt

no thet did not work

found the error. Apparently zenscript does not like &&.


feature: Expand NacosLoadBalancer to conveniently support custom service list …

Expand NacosLoadBalancer to conveniently support custom service list filtering and load balancing algorithms
Describe what this PR does / why we need it
At present, neither the official loadbalancer provided by Spring Cloud nor the existing NacosLoadBalancer can meet personalized load balancing requirements.

The official offers RandomLoadBalancer and RoundRobinLoadBalancer
SCA provides a NacosLoadBalancer based on Nacos weights

In order to conveniently and quickly meet various personalized load balancing needs, NacosLoadBalancer has been extended to support custom service list filters and custom load balancing algorithms.
Does this pull request fix one issue?
NONE
Describe how you did it

Add interface com.alibaba.cloud.nacos.loadbalancer.ServiceInstanceFilter to expand the service list filter.
Add interface com.alibaba.cloud.nacos.loadbalancer.LoadBalancerAlgorithm to expand the load balancing algorithm.
Add class com.alibaba.cloud.nacos.loadbalancer.DefaultLoadBalancerAlgorithm implementation of default load balancing algorithm, and register as a Bean in LoadBalancerNacosAutoConfiguration.
Adjust the construction method and creation process of NacosLoadBalancer, and add relevant logic for custom service list filtering and custom load balancing algorithm in the getInstanceResponse method.

Describe how to verify it

Set the environment variable spring.cloud.loadbalance.nacos.enabled to true to enable NacosLoadBalancer.
When custom service instance list filter, implement the interface ServiceInstanceFilter and register it as a bean.
When expanding the load balancing algorithm, implement the interface LoadBalancerAlgorithm and register it as a bean.

Special notes for reviews
NONE

@yuluo-yx Please review this new feature. If you think it's good, I will update it to the 2021. x and 2022. x branches.

@yuluo-yx Please review this new feature. If you think it's good, I will update it to the 2021. x and 2022. x branches.

cc @ruansheng8 @steverao


Backport stutter typo fix

https://github.com/AdoptOpenJDK/openjdk-jdk/commit/08eb67b941ee4f9a490fc17535bc0c9209b91071#diff-c638e872b60894dedf26ea7893bf9e54d191d8fa2036a741d93c38b708c7ad52

This may well be an issue that could be fixed, but licensing means that I can't do it as OopenJDK is GPL licensed. It would need a clean room PR from someone who hasn't looked at the OpenJDK PR.


replace old parameter names with new key parameter names

numberToDial replaces sendToNumber
textMessageBody replaces msg

I volunteer to change other locations under cSharp if you give me rough
directions or point me to java examples that I can use to model

How you naming numberToDial & textMessageBody? What is the reason?
If it because of https://gist.github.com/mheadd/665617/revisions, I think should modify the content in that url.
BTW, https://github.com/tropo/tropo-webapi-java is  java examples link.
Thank you.

My company uses tropo and is a C# shop.  We want to send text messages to our customers.  There are 3 ways for tropo to communicate that to their API users.   API documentation, example code
and revisions.   I like example code the best because I can just copy it and get it working (test harness) in minutes.      Tropo no longer uses sendToNumber and msg  so I recommend that C# examples be changed to reflect that.    Is Java or some other language more up to date?


added build.gradle, so we can use org.json

I resolved the merge conflicts so don't worry - it's ready to be merged


Add current new logo

This PR adds the current new logo which we agreed on assuming that the app name will be "Themis". Hopefully it will be.
I want to see the new icon in TestFlight :-)

Probably would be best, yes


chore: add Workflows 5.11.0 to versions

Can you also update LATEST_VERSION?

Can you also update LATEST_VERSION?

It gets auto-bumped in this repo:
LATEST_WORKFLOWS_VERSION = ROSETTA_VERSIONS.keys()[0]


Handle null version strings

Fixes #3

Thank you @ashwinkey04  for your contribution. I am excited about the prospect of your future contributions."

You're welcome @vishesh005. But I suppose you meant to merge this PR, this was closed instead.

@ashwinkey04  Done.


Json serialization of ControlledGate and ControlledOperation

Also override 'gate' property of ControlledOperation
Also fix overly-specific type annotation of control_qid_shape

Fixes https://github.com/quantumlib/Cirq/issues/2422

Automerge cancelled: Need a fresh :cookie:.

Automerge cancelled: The automerge label was removed.


Update multiple-ingress.md

What this PR does / why we need it:
Fixes typo in the commands provided for the lab
Which issue(s) this PR fixes:
Fixes #860

Nevermind, the command at the beginning of the tutorial was supposed to fail.


Support a platform-dependent dependency mapping

Currently, online packaged buildpacks must download their contributed dependency from the open internet.  There are situations where the URIs for those download locations are blocked from within a corporate network.  libpack's DependencyCache should noticed the existence of an artifact or artifacts in /platform that defines a mapping between a buildpack's dependency (id/version) and a different URL that it should be downloaded from. This should happen transparently (save for a different log message) to both the buildpack author using DependencyCache and the application developer using a buildpack that uses DependencyCache.

ConfigMap with entry-per-buildpack, TOML array per dependency.
[[mapping]]
id = "jdk"
version = "8.0.242"
uri = "https://internal:8080/jdk8.tar.gz
[[mapping]]
id = "jdk"
version = "11.0.6"
uri = "https://internal:8080/jdk11.tar.gz
[[mapping]]
id = "jre"
version = "8.0.242"
uri = "https://internal:8080/jre8.tar.gz
[[mapping]]
id = "jre"
version = "11.0.6"
uri = "https://internal:8080/jre11.tar.gz

@ekcasey You're looking for DependencyResolver and you'll want a single log message when you detect this directory.  A single line mentioning that you're using platform overrides for downloading, and then the URIs will reflect that in their normal log message.


Test GitHub Actions

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/11137/
Test FAILed.


Use decimal separator associated with selected number format

Is your feature request related to a problem? Please describe.
The temperatures are always displayed using a period/dot for the decimal separator.

Describe the solution you'd like
The temperatures would be better displayed using the decimal separator associated with selected language (for example: can be a comma https://en.wikipedia.org/wiki/Decimal_separator#Usage_worldwide).

You're right -- I think it just needs a call to the number format utility in custom-card-helpers.

Yes, I just found out that there is a "Number format" setting on the profile page:

I think this setting should be used for number display

Can you try 2.3.3-beta.0 and let me know if it works for you?

Unfortunately it does not work with 2.3.3-beta.0, temperatures are still displayed with period as a separator no matter which number format or language I chose :frowning_face:

Oops, I made the release wrong. Try 2.3.3-beta.1

Works like a charm! Thanks for your work :rocket:

Released in 2.3.3


[New game]: Circus Charly

🎮 Game Request
One of the most common obstacles in Circus Charlie is the fire ring. These rings are located throughout the levels and Charlie must jump over them to avoid being burned. Another common obstacle is the ring of death. This ring is located at the end of each level and Charlie must jump through it to complete the level.
  The game ends when Charlie loses all of his lives.
Point down the features
Circus Charly is another most popular Console Game in which the character is on the running Lion and we have to make the lion jump without getting collided with the Fire and Ring.
Assign me this
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @linga66 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

@kunjgit assign me

/assign

Hey @linga66 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


deps: Bump rules_apple -> 0.33.0

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue] Fix #19658
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

this one seems to be fighting with rules_swift - not sure if that means they need to be updated together, or i have missed a patch or somesuch
	File "/build/tmp/_bazel_envoybuild/b570b5ccd0454dc9af9f65ab1833764d/external/build_bazel_rules_swift/swift/internal/build_settings.bzl", line 73, column 34, in <toplevel>
		build_setting = config.string(
Error in string: string() got unexpected keyword argument 'allow_multiple'

https://dev.azure.com/cncf/envoy/_build/results?buildId=99822&view=logs&j=1c04237c-5f52-5959-5f83-5522b3556331&t=db3f3889-c922-566b-fa2e-4bc4948bc467&l=217

cc @junr03

actually this seems to be failing for bazel 5 related reasons - its not recognizing lambdas which are only added in bazel 5 as part of the starlark syntax

Yep we'll have to update to bazel 5.x first

/lgtm deps

@wrowe i think this one is ready to land


Binary Search Tree Level-Order Traversal

Hello, I am a participant of GSSOC'21, I propose the addition of BST Level-Order Traversal, please assign this issue to me.

I am a participant in GSSOC 2021 I would love to do this using c or java. Please assign this to me!

I would like to do this code in C or C++,please assign me this project

hey @tarun26091999 can i work on this issue in python?
Thank you!

I would like to code for Level Order Traversal in BST using java. Kindly assign me this issue.

@raksha009  please assign this issue to me ,I will implement in c++


Fixes #33 : Fixed renderflex overflow in current command widget

fixes #33
Fixed Renderflex overflow in current commad widget and align the command in centerLeft.
Earlier

Currently

Hmm IIRC, this was supposed to fixed in https://github.com/CCExtractor/ccextractorfluttergui/pull/24/files, and I can confirm this does not happen for me on linux or windows.

But it was showing in my ubuntu, don't know why. And I also fixed the alignment to centerleft. Please review it.

Not reproducible atm


Seems to be sucking up CPU time

Just starting OSCWidgets with a five-button control window results in it using close to 50% of the CPU, as indicated by Process Explorer.  Processor is an Intel Pentium G640 at 2.8 GHz, operating system is Windows 10 Home.

The problem is caused by the LogFile thread:
Even if OSCWidgets is idle (no controls) it consumes all CPU cycles of one core.
By adding a short sleep the problem is solved.
Because the messages are buffered, the sleep can be as long as desired.
I decided to sleep for 100ms.


German Umlaute are destroyd in Keywords

First, thanks for that amazing piece of work, it's great.

If think it's because the writing process is not in utf8
Can you please tell me how to fix that???
Thanks a lot!

I've fixed this..
Remove the _charset decode function and anything calling it.
and
Modify binary()
https://stackoverflow.com/questions/3388133/no-utf-8-when-write-iptc-data-in-jpg-with-iptcembed


window: adding setBounds and getBounds api

Fixes #1445

Fixed, have to test on linux and windows.

Awesome, thanks!

Many thanks, looking forward to release :smile:


Hardware suggestion

Hi Team,
Could you please provide any suggestions on hardware for running the model locally? For example, I am looking for the volume of RAM, GPU, disk and the CPU model.
Thanks for your help in advance.

It very much depends on what type of analyses you want to perform and what software you use. Basic FBA can be run on basically any computer. If your analysis requires repeated FBAs, then it is mostly CPU that affects the speed of simulations.


Shorter descriptions in the schedule

I experimented with a auto automated ways to truncate talk descriptions (omg line-clamp is so so buggy), then I thought noooope, better to do it manually.

@harleenkbatra08 @vschupmann what do you think? https://deploy-preview-275--cds2019.netlify.com/devsummit/schedule/

As a side effect, this will set the meta tags up which will improve social sharing.


[Bug] Cannot find Discord, but I have discord

Describe the Bug

I opened the installer only to find that discord wasnt found. So I click browse to find it myself, but when I searched "discord" (and "DIscord" in case of case sensitivity) from root "/" it didnt find it.
If this is important, I installed Discord through the Ubuntu Software Store
To Reproduce

$ betterdiscordctl --install

Expected Behavior

BetterDiscord Installer finds Discord
Screenshots

Discord Version

Stable 124823 (6ac2437)
Host 0.0.17
Linux 64-Bit (5.13.0-40-Generic)

Additional Context

Ubuntu 20.04.4 LTS is my OS Version

snap installs are not yet supported and betterdiscordctl is not an official BetterDiscord script


SPI doesn't restore after LP1 mode (WDT2_WakupFromLP1())

SPI doesn't restore after LP1 mode (WDT2_WakupFromLP1()).
If I use SPI-analog software command:
// SPI-compat for correct working LP Modes
void WRITE_SPI_Analog(char b)
{
uint8_t i;
for (i = 0; i < 8; i++)
{
GPIO_OutSet(GET_PIN_CFG(ADS1220_SCK));    // 1
asm volatile ("nop");                     // 125 ns
if (b & 0b10000000)
GPIO_OutSet(GET_PIN_CFG(ADS1220_MOSI)); // 1
else
GPIO_OutClr(GET_PIN_CFG(ADS1220_MOSI)); // 0
b <<= 1;
GPIO_OutClr(GET_PIN_CFG(ADS1220_SCK));    // 0
asm volatile ("nop");                     // 125 ns
}
}
all working.

arduino-max326xx repo has been archived and is now read only.


Native client application

New sample walkthrough for native client with AD FS 2016

#hold-off

Followed up via email. Please close. DO NOT MERGE.


TC29 - create new Cryptpad account hangs after TF Connect login

Testlodge TC29 - create new Cryptpad account - hangs after TF Connect login at check of data integrity
Version information

OS: Windows 10
eVDC 2.5
Testlodge Testrun: PK-Test5-deploy2.5-eVDC
Browsers tried:

BRAVE (Version 1.21.74 Chromium: 89.0.4389.72),
Firefox (Version 86.0),
Chrome (Version 88.0.4324.190)

Steps to reproduce
see screenshot log attached
TC29 create Cryptpad account failed 11Mar21.pdf

Will try to recreate now.

Tested and verified.  Newest release VDC on testnet  does not exhibit the same behaviour
@Pkgraz please verify.

For testing you can also log into my deployed cryptpad: https://weynandkuijpers-cryptpad-peterkraftpad.webg2test.grid.tf/drive/

Hi Weynand,
Many thanks for your follow up.
I see still a strange behavior:

While Brave and Chrome browsers still show a spinning wheel,
the connection works fine with Firefox after maybe 10-15 seconds of a spinning wheel and a message "checking data integrity" and a green bar

@.***D71905.C7E58E40]
So the link hangs with Chrome and Brave, but connects with Firefox:
@.***D71905.C7E58E40]
Meanwhile, I have the same behavior with my test-eVDC: after 3 days (!!!) my Firefox Link to my Cryptpad works, so I can continue testing.
Many thanks,
Peter
Von: Weynand Kuijpers @.>
Gesendet: Sonntag, 14. März 2021 08:15
An: threefoldtech/js-sdk @.>
Cc: Pkgraz @.>; Mention @.>
Betreff: Re: [threefoldtech/js-sdk] TC29 - create new Cryptpad account hangs after TF Connect login (#2750)
For testing you can also log into my deployed cryptpad: https://weynandkuijpers-cryptpad-peterkraftpad.webg2test.grid.tf/drive/https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fweynandkuijpers-cryptpad-peterkraftpad.webg2test.grid.tf%2Fdrive%2F&data=04|01||e4b5b5fff4bc41bb234808d8e6b8d166|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637513028743046720|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=sCYzUyvInWScOP8ccqNqiZNlmQSgWevOS8zFRUHgT6g%3D&reserved=0

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fthreefoldtech%2Fjs-sdk%2Fissues%2F2750%23issuecomment-798849739&data=04|01||e4b5b5fff4bc41bb234808d8e6b8d166|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637513028743056714|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=5liOqFHvK7XolBWTH5Uc7UJ%2BQt5xn761RF785jXb3KU%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPNFHYVO6CYYR634KR6EMYDTDRO5TANCNFSM4ZAK3JIA&data=04|01||e4b5b5fff4bc41bb234808d8e6b8d166|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637513028743056714|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=w97uiCDhuoa2q7snA%2Fm6W1wQoSVRFAKxKo3dk5brxVU%3D&reserved=0.

Tested and verified. Newest release VDC on testnet does not exhibit the same behaviour
@Pkgraz please verify.

Verified - works with Firefox only, still hangs on Chrome & Brave...
How can I determine the version of the eVDC deployed?

Tested and verified. Newest release VDC on testnet does not exhibit the same behaviour
@Pkgraz please verify.

How can I determine the version of the eVDC deployed?

Opened a new feature request issue to show the version in the VDC dashboard.
this issue should be closed?

yes.  VDC version feature request will continue.

Deployed a new vdc and confirm that now the Cryptpad account login works fine on Firefox, Chrome & Brave browsers.
Closing issue, many thanks for the quick fix.


Test Slack/Github integration for Issues monitoring

Testing slack/github integration
What version are you using?
What did you do?
What happened?
What did you expect to see instead?

Tested.


chore: update to allow ESM syntax (DNA-1245)

Description
makes ESM syntax work for the scripty parts

Related Issue
DNA-1245
Types of changes

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

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

:tada: This PR is included in version 12.0.0-beta.64 :tada:
The release is available on:

GitHub release
npm package (@beta dist-tag)

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

GitHub release
npm package (@next-major dist-tag)

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 12.0.0 :tada:
The release is available on:

GitHub release
npm package (@next-major dist-tag)

Your semantic-release bot :package::rocket:


Adjust the DPAS instruction order in TritonIntelGPUToLLVM

Adjust the order of the generated DPAS instruction to get better DPAS operands locality in the generated LLVM IR.
The new logic generates a large set of the DPAS instructions which can reuse the A or B operands across multiple DPAS instructions.
Add a new env-var  TRITON_INTEL_AGGRESSIVE_DPAS_REUSE to generate most aggressive DPAS instruction order for experimental. Will make the aggressive order as default when the IGC scalar backend could perfectly generate the best performance kernel in instruction scheduling.

@chengjunlu I have added lambda functions to refactor the loop. The codegen is the same.

Performance run on microbenchmarks: http://benchmarks.glados.intel.com/d/1pXX4hUSz/microbenchmarks?orgId=1&var-tag=ci|reorder_dpas_gen&var-bench=All&var-device=Intel(R) Data Center GPU Max 1550&var-compiler=triton&var-backend=All&var-baseline_backend=triton-ci-XPU 1550&var-target_backend=triton-ci-XPU 1550
Results are essentially on par with CI.


Exported wasm functions are not exposed to js code

When trunk initializes the wasm module and calls into it, it does not expose any exported functions for javascript code to use. This means that javascript cannot easily interact with the wasm code.
For any wasm module, trunk will always generate the following script tag:
<script type="module">import init from '/index-cc05ed39af3d3846.js';init('/index-cc05ed39af3d3846_bg.wasm');</script>

oh, I have the same problem. mark!

Same - I worked around it by injecting my own Js script block that does the imports and calls
I used Trunk.toml property pattern_script in the first case but when I wanted it to be externalised to a file I used the inline asset type of HTML to insert the same Js script block but from file.
It would be really cool if we could specify what functions get imported

With everything being a module but all the modules being done by filename with hashes in it seems really hard for rust to call js and js to call rust. I'm probably missing something like how js modules work ;-)

To add to usagi workaround, here is my current setup:
Trunk.toml:
[build]
pattern_script = """
<script type=\"module\">
import * as bindings from '{base}{js}';
bindings.default('{base}{wasm}').then(wasm=>{
  document.dispatchEvent(new CustomEvent(\"wasmload\", {
    detail: {
      wasm: wasm,
      bindings: bindings
    }
  }))
});
</script>"""

index.js
document.addEventListener("wasmload", event => {
  // event.detail contains bindings and raw wasm
  let bindings = event.detail.bindings
  new bindings.MyRustStruct()
})

I use the custom event, to pass the bindings and raw wasm to my JS files. Currently I register the wasmload event after document load, so that I can access my document.

I'm not currently using Trunk in this way, is anyone else waiting on this functionality?
@thedodd is this planned or are the current workarounds the wanted behavior?

is anyone else waiting on this functionality?

I am :)
While above workarounds solve the problem, I feel like they're a bit too hacky compared to conciseness and beauty of the other parts of trunk :)

I added this to trunk-ng: https://github.com/ctron/trunk/commit/0e9981eb94ece781281715a18772aeb2aa09187b … it should be part of the next release.
In a nutshell, this will create an import like this:
<script type="module">
  import init, * as bindings from '/index-7eeee8fa37b7636a.js';
  window.wasmBindings = bindings;
  init('/index-7eeee8fa37b7636a_bg.wasm');
</script>

It will also be possible to change the name and disable it altogether.

this is released as part of trunk-ng 0.17.16

Albeit @ctron 's improvement mentioned here, unless I am missing something, I don't think that's still not enough to make sure to run our own JavaScript code after wasm was loaded and the binding are ready to use without using "workaround" mentioned by others, and summarized here.
Assume you have a "simple" <script data-trunk src="src/index.mjs"></script> in your index.html, is there a "better" way to make sure you're running src/index.mjs after wasm was loaded, initialized, therefore window.wasmBindings wouldn't be undefined if the first thing you're doing in index.mjs is, for example, console.log(window.wasmBindings)?
If there's no other trunk-blessed way to do this, perhaps emitting a custom event "workaround" might be part of the default trunk installation (and documented accordingly) instead of having to customize build.pattern_script in our Trunk.toml.
Any feedback is greatly appreciated. Thank you! :)

Wouldn't the "initializer" feature work for you? Here's an example: https://github.com/trunk-rs/trunk/blob/main/examples/initializer/src/initializer.mjs
As you might not need to progress part, you can omit that. But you will get access to the wasm instance right after it's been initialized.

Hey, @ctron . Thanks for getting back to me! I appreciate you.
In my experience in both onComplete or onSuccess, console.log(window.wasmBindings) will be still undefined.
Regardless, even if it worked, what I am trying to get here is this "straightforward" use case (which I only assume is something that anyone would expect to work out-of-the-box, but please don't hesitate to give me your feedback):

I write my Rust code and mark some functions with #[wasm_bindgen] to make them available in JavaScript.
I write my JavaScript and import it in index.html with <script data-trunk src="src/index.js"></script>
Within src/index.js I do console.log(window.wasmBindings), but it logs undefined (as window.wasmBindings will be only "ready" later.

I'd naively expect this ⬆ use case to work out-of-the-box, without having to customize the initializer or having to "tap into" Trunk's output generation bits with a custom Trunk.toml file.
--
These two approaches (the first being the current built-in) are doing the same thing, but the latter approach will actually let the user "know" when window.wasmBindings is not undefined:
<script type="module">
  import init, * as bindings from '/index-7eeee8fa37b7636a.js';
  window.wasmBindings = bindings;
  init('/index-7eeee8fa37b7636a_bg.wasm');
</script>

<script type="module">
  import * as bindings from '/index-7eeee8fa37b7636a.js';
  bindings.default('/index-7eeee8fa37b7636a_bg.wasm').then(wasm=>{
    document.dispatchEvent(new CustomEvent(\"WasmLoaded\", {
      detail: {
        wasm: wasm,
        bindings: bindings,
      }
    }))
  });
</script>

I feel like, ultimately, calling init (i.e., __wbg_init or bindings.default) with the wasm file is an async process, therefore it should be either await-ed (or .then() called on its Promise) to let the user know/access bindings when they're truly ready.
What do you think?

I think the "problem" relies more on the fact that <script data-trunk src="src/index.js"></script> gets executed before;
<script type="module">
  import init, * as bindings from '/index-7eeee8fa37b7636a.js';
  window.wasmBindings = bindings;
  init('/index-7eeee8fa37b7636a_bg.wasm');
</script>

Therefore window.wasmBindings will be undefined. Adding a defer to <script data-trunk src="src/index.js"></script> won't work either.
Maybe;
<script type="module">
  import init, * as bindings from '/index-7eeee8fa37b7636a.js';
  window.wasmBindings = bindings;
  init('/index-7eeee8fa37b7636a_bg.wasm');
</script>

Should be added to the output index.html after everything else, right before the body closes? 🤷

So yes, I you run your code before the wasm is initialized (initializer or not), that won't work. That includes downloading and starting the wasm instance.
When you initiate the call from wasm, that ensures that the bindings are ready.
But I agree that it should be possible to call form JS into WASM directly after the initialization. However, it looks like to be a bit more complex. Even adding await to the init call (which feels like a bug) doesn't work. Adding the defer attribute to the script should honor the execution order, but in fact does not (at least on Firefox.
Having such an event would be helpful too. But it also feels a bit like a something that shouldn't be required in the first place.
In any case, I think it makes sense to open a dedicate issue for this.


User input validation

Need to give user feedback on whether the data given is suitable or not and stop the user to perform certain operations which require inserting of data first.

can i try to add this feature ?

can i try to add this feature ?

Yeah sure,
After some progress, you can share initial screenshots of UI
Thanks for your interest

Okay sure..

So like in Binary Tree, a user can add empty numbers. That should be prevented and the user should be given feedback regarding that.

You can see that user can have feedback while using array in this example. Something should be checked and implemented in any required DSA page

@Aashray446 okay understood👍🏻.

Hey , you can start working on the issue, You don't need to wait for the branch to merge, You can start working from the current main branch.


Update README document, and add the version and release version

Update README document, and add the version and release version

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

 All committers have signed the CLA.


Flatpak version

What feature or new tool do you think should be added to DevToys?
Flatpak version of the app.
Why do you think this is needed?
Easy installation on Linux distros with more compatibility.
Solution/Idea
No response
Comments
No response

I'd love to see this as well. There are distros out there like Fedora Silverblue where Flatpaks are the preferred method of app delivery.

Agreed. Alternatively, an AppImage would be fine too.

This way all Linux distros would be able to easily use this software

Flatpak is not a bad idea as the GirCore binaries are build to match the flatpak binaries. This avoids missing dependencies and libraries which are named differently than the flatpak ones.

Hi there,
Is anyone familiar with how to build a flatpak manifest? I'm reading the documentation and I'm getting quite confused by a few things. For your information, I'm quite a beginner at Linux. I learn it slowly while developing DevToys for it. I'm more of a Windows person.
If I base myself on the DEB package, I have a devtoys.desktop file like this:
[Desktop Entry]
Name=DevToys
Comment=A Swiss Army knife for developers.
GenericName=DevToys
Exec=/usr/bin/DevToys
Icon=/opt/devtoys/devtoys/Icon-Windows-Linux.png
Type=Application
StartupNotify=false
Categories=Development;Utility;Office
Keywords=devtoys

DevToys should be installed in /usr/bin/DevToys. The icon should be in /opt/devtoys/devtoys/Icon-Windows-Linux.png.
DevToys also has dependencies on libwebkitgtk-6.0-4 and libadwaita-1-0.
Let's say the built binaries of DevToys, ready to be packed, are in /devtoys-bin on my local machine. What does the flatpak manifest should look like?
I'm not finding a clear answer on how to include the 2 dependencies I mentioned above. I'm also confused by the build-commands section in the manifest and what I should put there in my case.
Can anyone please help me with it? :-)
Much appreciated!

I have not done it myself but there are already dotnet applications being distributed via flatpak:

Pinta has no GirCore release yet but the project is pretty well structured.
All nickvison apps (e.g. Denaro are based on GirCore.

I would recommend comparing both ways to understand things (I have not done this myself yet).But i think it should get you started.
Additionally one day I found this on github: https://github.com/flathub/org.freedesktop.Sdk.Extension.dotnet8
I did not check it out in detail but perhaps it helps.

One more thing: I don't know how it will work with extensions. There would probably be rights needed to access the home directory but if this is sufficient I don't know.

@veler You can take a look at https://docs.flatpak.org/en/latest/conventions.html. Flatpak expects a few conventions.
The Flatpak manifest doesn't only define where to install the application, but also how to build it. It should contain build instructions for the application.
Dependencies are also usually built from source in the manifest. But maybe they're on the GNOME runtime already? https://docs.flatpak.org/en/latest/available-runtimes.html
@badcel Thanks for the links. I have experimented a bit with Flatpak in the past, but didn't get to the point of publishing anything.
I have zero experience with .NET, that's what hinders me a bit here...

@veler You can take a look at https://docs.flatpak.org/en/latest/conventions.html. Flatpak expects a few conventions.
The Flatpak manifest doesn't only define where to install the application, but also how to build it. It should contain build instructions for the application.
Dependencies are also usually built from source in the manifest. But maybe they're on the GNOME runtime already? https://docs.flatpak.org/en/latest/available-runtimes.html
@badcel Thanks for the links. I have experimented a bit with Flatpak in the past, but didn't get to the point of publishing anything.
I have zero experience with .NET, that's what hinders me a bit here...

Thanks @hockdudu . I will read this later today. Maybe it's already explained there but I will ask in case: what if the app is already built? I basically have all the binaries in a folder, ready to be packed in zip, Deb...etc

@veler You could use pre-built binaries, but AFAIK Flathub only allows binaries in exceptional circumstances. That's for auditing / safety reasons. By using sources, you can be sure the package doesn't do anything it shouldn't. With binaries, on the other hand, someone could have tampered it and added additional stuff (malware and the like).
See https://docs.flathub.org/docs/for-app-authors/requirements#best-practices

@veler You could use pre-built binaries, but AFAIK Flathub only allows binaries in exceptional circumstances. That's for auditing / safety reasons. By using sources, you can be sure the package doesn't do anything it shouldn't. With binaries, on the other hand, someone could have tampered it and added additional stuff (malware and the like).
See https://docs.flathub.org/docs/for-app-authors/requirements#best-practices

Just to make it clear : are we talking about building the source code on the user machine, or in my  CI ?
If the first, that sounds horrible. To run, DevToys had no dependencies needed outside of the 2 I mentioned earlier. But to build, it needs NodeJS,.NET, a total of 3 repositories... That will quickly cluter the user's machine.

Just to make it clear : are we talking about building the source code on the user machine, or in my  CI ?

It is build in a CI.
Most apps are build on Flathub's CI on buildbot.flathub.org.
Though a few (like OBS) build on their own CI and push the package to Flathub.

Neither ;)
If submitted to Flathub, the code is built by Flathub themselves. You provide only the manifest and some metadata. Well, you build locally as well for testing, but the productive package is done by their Buildbot.
You can look into repositories for popular apps: https://github.com/orgs/flathub/repositories?q=sort%3Astars
The application is packaged by them and the end-user receives only the binaries. No clutter :D
I looked into a few repositories, and I've noticed many are based off on .deb packages. I suppose I interpreted the section "Best practices" about binaries wrong (maybe only additional, non first-party binaries are refrained upon?) and gave you misinformation regarding binaries, my bad.
You could probably look at e.g. https://github.com/flathub/com.visualstudio.code/blob/master/com.visualstudio.code.yaml for an example of an app built using .deb.
But as stated previously, I experimented with Flatpak a little bit, but I'm no package maintainer or anything. Do also write to the folks at the Matrix chat https://matrix.to/#/#flatpak:matrix.org, they can also help out on the whole process.

So, out of curiosity, I have experimented with creating a functional Flatpak manifest for DevToys. The results can be found in the attached archive.
First of all, I'm not an active maintainer of any Flatpak. I just wanted experiment with packaging this app. And while it is a good starting point, it needs more improvements before it could be submitted to Flathub.
The archive contains a Flatpak manifest, which can, in theory, build the DevToys application from source and package it as a Flatpak.
However, there are a few caveats:
Firstly, Flatpak Builder pulls the dependecies before building, and then runs the build without a connection. AFAIK this is done to improve security and audibility of an Flatpak package.
However, this means dependencies need to cached by Flatpak Builder and the build tools need to use that cache. Thanks to some tooling from the Flatpak team, creating that cache is quite straightforward. The archive contains a index used by Flatpak Builder to cache the required packages, and the commands to update this index can be found in the Readme.
But this means also that I had to patch the build process to point towards said cache, so that Dotnet can build the app inside the build sandbox. Ideally, this patch should make it's way upstream as a build option.
Secondly, the archive also contains a data folder. This contains the desktop file, icons and a Appstream file. The latter is used by software centers like Gnome Software, KDE Discover or the Flathub website to display informations about the app.
Flathub policy is normally that these files are maintained upstream, so this would most likely come up when submitting the app.
Lastly, while I technically have a build Flatpak with the DevToys application, it does not work right now. The application does not start, due to it missing some file.
I suppose though this is because I'm not running the build or install as expected by DevToys.[^1]
Because I haven't found instructions for "building DevToys from a CLI", only from running from some IDE's, I've decided to show the current state for further discussion.
Finally, heres the archive for the Flatpak.
[^1]: Check lines 49 - 51 in the file app.devtoys.DevToys.yml for how I attempt to do it.

A few further notes:
The reason the application did not start in the Flatpak was because is because it has a misdirection for a wwwroot folder. While running it still expects it from the source folder [^1], when it really is in the install folder [^2].
But I'm not sure why this happens.
@veler, it would help if you could provide some information on how you build the existing Linux releases, especially the portable zip. Might show why it expects the wwwroot in the wrong place.
[^1]: Flatpak Builder mounts the sources in /run/build/devtoys/, so the path is /run/build/devtoys/src/app/dev/DevToys.Blazor/wwwroot.
[^2]: From the view of the app, it is installed under /app/lib/app.devtoys.DevToys, so the path should be /app/lib/app.devtoys.DevToys/wwwroot?

Managed to find why the app didn't want to start in the Flatpak. Removing the DevToys.Linux.staticwebassets.runtime.json file from the package makes it run.
With that, I now have a functional Flatpak manifest for DevToys:

Here is the archive with the manifest.
In my view, the contents in the archive should be sufficient for submission to Flathub.
A few things to note:

As mentioned before, Flatpak builds without a connection. Therefore the patches to the build system (found in the patches folder) are neccessary to allow to build it in the Flatpak Builder environment.
The contents in the data folder should ideally be organized somewhere in upstream, as they would also be used by other Linux distribution methods.
If updates should arise, the dependencies need to be updated manually. Flathub does provide a mechanism to automatically check for updates to dependencies, but AFAIK this doesn't apply to Nuget oder NPM sources. The neccessary commands to update these sources are documented in the Readme.

Hi @CodedOre and @hockdudu ,
Sorry for my lack of responsiveness here. Quite busy with many things this summer!
@CodedOre, this is impressive to me, and I have many interogation as Flatpak is still quite obscure to me. Thank you very much for exploring all this though! I really appreciate !

Managed to find why the app didn't want to start in the Flatpak. Removing the DevToys.Linux.staticwebassets.runtime.json file from the package makes it run.

That is interesting. I do not expect this file to be generated when using dotnet publish in Release mode. I looked at the archive you shared and saw that "$DOTNET_EXE" build is used in devtoys.patch (is that correct? is this an auto-generated file?)
Here is what I use in the CI I made (which is different that build.csproj in DevToys repository), perhaps it explains the difference:
dotnet publish DevToys.Linux.csproj --configuration Release --framework net8.0 --runtime linux-x64 --platform x64 --self-contained true /p:PublishSingleFile=false /p:PublishReadyToRun=false /p:PublishTrimmed=false /p:RuntimeIdentifierOverride=linux-x64 /p:Unpackaged=true

And then I delete output folder/wwwroot/_content. Then I copy LICENSE.md to the output folder. Finally, I extract the built NUPKG of DevToys.Tools to output folder/Plugins/DevToys.Tools.

Thanks for the reply, @veler!
Since I haven't much experience with .net, I have based the Flatpak Build on the build.sh script in the folder (which comes from the NUKE Execution Engine?), since it seemed like the expected build system to me.
The build command Flatpak Builder currently uses is this one:
./build.sh --configuration Release --target PublishApp

The $DOTNET_EXE is from said build script.

Here is what I use in the CI I made (which is different that build.csproj in DevToys repository), perhaps it explains the difference:
dotnet publish DevToys.Linux.csproj --configuration Release --framework net8.0 --runtime linux-x64 --platform x64 --self-contained true /p:PublishSingleFile=false /p:PublishReadyToRun=false /p:PublishTrimmed=false /p:RuntimeIdentifierOverride=linux-x64 /p:Unpackaged=true

I see. AFAIK this is more or less the same as with what NUKE eventually runs. But it may make sense to only run dotnet restore and dotnet publish, instead of the whole build system then.
I will look into this later this day.
If you have other questions about the Flatpak build, just ask away.

Thank you :)
I guess, it would certainly help (with flatpak and other...) if I was publishing the CI on GitHub. The reason I kept it private is to try to deter some people from taking DevToys, which is under MIT license, and sell it without any significant change (it's something I saw happening in the past).

The build command Flatpak Builder currently uses is this one:
./build.sh --configuration Release --target PublishApp

Oh I see where it's used now !
Well, since my CI also generates a ZIP, wouldn't be easier (and faster in CPU / server time) to just unzip / use the output folder instead of building, if I integrate this into my CI? How about the part in app.devtoys.DevToys.yml that points to Monaco editor (line 32)? Is it still needed if flatpak doesn't need to build DevToys from the sources?
Note that the CI I currently have privately also takes care of restoring nuget packages, node modules and Monaco Editor, and build DevToys.Tools properly.

Well, since my CI also generates a ZIP, wouldn't be easier (and faster in CPU / server time) to just unzip / use the output folder instead of building, if I integrate this into my CI? How about the part in app.devtoys.DevToys.yml that points to Monaco editor (line 32)? Is it still needed if flatpak doesn't need to build DevToys from the sources?
Note that the CI I currently have privately also takes care of restoring nuget packages, node modules and Monaco Editor, and build DevToys.Tools properly.

Well, in would be possible to build the Flatpak from a build output. You could take the output folder as directory source and only run the install commands with Flatpak Builder. [^1]
However, it also makes it less reproduceable and auditable, as it would basically take an unknown source with binary files.
As the Flathub docs state:

Applications should build all components of the manifest from source when possible.

If a distribution of a pre-build binary is wanted, the source would probably need to be publicly accessible, like the portable zip from the releases.
[^1]: "Install commands" mainly means to copy them to a location inside /app, as this folder is then packaged by Flatpak.

Well, since my CI also generates a ZIP, wouldn't be easier (and faster in CPU / server time) to just unzip / use the output folder instead of building, if I integrate this into my CI? How about the part in app.devtoys.DevToys.yml that points to Monaco editor (line 32)? Is it still needed if flatpak doesn't need to build DevToys from the sources?
Note that the CI I currently have privately also takes care of restoring nuget packages, node modules and Monaco Editor, and build DevToys.Tools properly.

Well, in would be possible to build the Flatpak from a build output. You could take the output folder as directory source and only run the install commands with Flatpak Builder. [^1]
However, it also makes it less reproduceable and auditable, as it would basically take an unknown source with binary files.
As the Flathub docs state:

Applications should build all components of the manifest from source when possible.

If a distribution of a pre-build binary is wanted, the source would probably need to be publicly accessible, like the portable zip from the releases.
[^1]: "Install commands" mainly means to copy them to a location inside /app, as this folder is then packaged by Flatpak.

I see. Building from the source might not be ideal in my case though, because the build process for release isn't as straight forward as it may sound like.

If a distribution of a pre-build binary is wanted, the source would probably need to be publicly accessible, like the portable zip from the releases.

Perhaps I misunderstand this. The portable ZIP and what the deb (on Linux), exe (on Windows) contains are the same. DevToys is literally built once per platform, then the binaries are stored into a zip, or packed in a deb, or in an installer for Windows. It would be the same thing here. The "source" is what there is on GitHub, either in each Release or in the main branch. It's already public. The current CI for generating what is then published on the GitHub Release page is NOT public at the moment. Is that the problem?
Also, are we talking about building DevToys on the customer machine in order to install Flatpak?
If not, I'm not understanding how different from an auditing point of view it is to build the Flatpak from a build output instead of from the source (which... will generate the same build output my CI does).
Sorry for the confusion 😅

The user does not need to build the Flatpak on his machine.
In most cases, Flathub builds the Flatpak from the manifest on its own infrastructure on buildbot.flathub.org. Some, like OBS or Firefox, are build on their own CI's, with the Flatpak then published to Flathub.
The user then downloads and installs the package.
However, the manifest is publicly accessible. If you open any app on Flathub, you can find a link to the manifest file and check how its packaged, and could be audited on the package process.
Also, when submitting a new application, the manifest will be reviewed by the Flathub team.

Now, Flathubs policy is to prefer all components being build from source, if possible.
So, quite a few apps, like OBS, Chromium or Gnome or KDE apps, have the sources and build instructions in the manifest.
It is possible to tell Flatpak Builder to use a archive of pre-buils binaries to create the package, which is what most proprietary and some unverified apps are doing.
This is less auditable (as they are binaries), but generally accepted by the Flathub team.
Still, this needs a accessible location from where to pull the binaries.
And even if you were to package the binaries on your own CI, the reviewers would likely ask for the sources to be externally verifiable.
Which is why I mentioned the portable zip. If a binary distribution is preferred, it would make most sense to use this as source for the Flatpak package.

On a personal note: I choose to build from source because I generally like transparency over an build process, and also because just packaging the binaries wouldn't been a interesting challenge ;-)
But I could create a manifest which just packages the release archive.

As a bit of a sidenote, on how Flatpak Builder works:
Flatpak Builder first downloads the sources to an cache, found in the folder .flatpak-builder (generated in the working directory).
Then, the build commands are run inside a sandbox, using the SDK set in the manifest.
And at the end, the files located in the /app folder are packaged for release.
When the Flatpak is run, this /app folder will be mounted inside a sandbox and the set command is executed.
There are a few expectations on how the /app folder should look like, but those mirror Linux standards, just with /app instead of /usr as the prefix.

Alright, so I updated the manifest to use the publish command directly. I also found a way to update the nuget sources to the Flatpak-provided cache, so no patches a required anymore.
Here is the archive with the updated manifest: DevToys-Source-Flatpak.zip.
Also, I created a second manifest which takes the pre-compiled binaries from the Github Releases, for comparison: DevToys-Archive-Flatpak.zip

I have found a bug, introduced when switching from using the Build project to using the dotnet commands directly, as it does display the wrong version:

I noticed that there is a SetVersion step in the Build system, we probably need to run that or some similar functionality in the Flatpak build.

Then, there is the question of the contents in the data folder.
This folder currently includes a copy of the icons in the folder structure Linux expects, the Desktop file and the Appstream file.
As the Flathub docs states:

These metadata files should directly come from upstream whenever possible.

So, the question is if they could be brought upstream.

When those points are resolved, I think the next step would be submitting the app. The submission process is outlined in this document. But it would mostly mean that the files from my archive would be submitted via an Merge Request on the Flathub repository.
After that it's up to the Flathub team to review and approve the application.
Lastly, there are a few steps to verify the Flatpak as official. In the case of DevToys, this would mean you getting a key from Flathub and storing it in a specific location on your website. Flathub would then use the key to verify that the Flatpak is official. The instructions for that process are located here.
That's basically it!

I have found a bug, introduced when switching from using the Build project to using the dotnet commands directly, as it does display the wrong version:

Ah! Yes! I forgot that... In the CI I made, we also set the version number in some files (and the syntax of it varies). Here is the steps the CI performs:
0. Update the changelog in DevToys.Blazor/Assets

Update the version number in DevToys and DevToys.Tools
Update the splash screen (it changes based on whether it's a preview version or not)
Restore dependencies (nuget, monaco, npm...)
Build the solution (dotnet build)
Run tests
Publish the solution (dotnet publish and pack)
Generate installer, deb, or zips

Ultimately, and based on my understanding of your previous explanation, a good thing to try would be to:

Make the CI public, except whatever I don't want to be public, but there's nothing private for the Linux build as far as I remember.
Update the CI so we can optionally omit steps 4, 5 and 7.
Change the Flatpak manifest so it runs this CI with these omitted steps, and use the generated output as what to install on the user machine, which is ultimately the exact same thing that end up in the published portable Zip.

How does that sound?

These metadata files should directly come from upstream whenever possible.

I'm not sure what they expect. Is the upstream the GitHub repository?

Thanks for sharing your next step! Hopefully I can automate that more with the CI. Currently, I upload the generated packages to GitHub Release manually from each OS (Windows, Mac, Linux), publish an update on Microsoft Store, Homebrew and Winget manually, and soon I will add Chocolatey, and now Flatpak. It starts to add up 😅

Ah! Yes! I forgot that... In the CI I made, we also set the version number in some files (and the syntax of it varies). Here is the steps the CI performs:
0. Update the changelog in DevToys.Blazor/Assets

Update the version number in DevToys and DevToys.Tools
Update the splash screen (it changes based on whether it's a preview version or not)
Restore dependencies (nuget, monaco, npm...)
Build the solution (dotnet build)
Run tests
Publish the solution (dotnet publish and pack)
Generate installer, deb, or zips

Ultimately, and based on my understanding of your previous explanation, a good thing to try would be to:

Make the CI public, except whatever I don't want to be public, but there's nothing private for the Linux build as far as I remember.
Update the CI so we can optionally omit steps 4, 5 and 7.
Change the Flatpak manifest so it runs this CI with these omitted steps, and use the generated output as what to install on the user machine, which is ultimately the exact same thing that end up in the published portable Zip.

How does that sound?

That would sound good.

These metadata files should directly come from upstream whenever possible.

I'm not sure what they expect. Is the upstream the GitHub repository?

In most cases, it is the GitHub repository of the app. However, even a additional repository in the DevToys organization is likely fine.
AFAIK, the main point behind this policy is to ensure that the information in the data files, especially the Appstream file, matches the rest of the apps distribution.

Thanks for sharing your next step! Hopefully I can automate that more with the CI. Currently, I upload the generated packages to GitHub Release manually from each OS (Windows, Mac, Linux), publish an update on Microsoft Store, Homebrew and Winget manually, and soon I will add Chocolatey, and now Flatpak. It starts to add up 😅

Well, submission and verification are steps you only need to do once.
Though updates to the manifest remains a thing.

I do have to ask:
This CI you mentioned, it isn't the NUKE build environment I've used before?
As this seems to perform most steps you've mentioned.

I do have to ask: This CI you mentioned, it isn't the NUKE build environment I've used before? As this seems to perform most steps you've mentioned.

Yes it is. It's a NUKE build. I should probably not use the CI term in here. I understand myself 😅.

I see. Then I should revert to use the ./build.sh script in the manifest.
I do think I can avoid reintroducing the patches, now that I found the trick with updating the nuget source.
One thing I noticed:
You mention as your first step "Update the changelog in DevToys.Blazor/Assets". Is this a step done by the CI?
Reason is: As mentioned before, the Appstream file is used by the Flathub website and Linux software centers to display information about the app. This also involves informations about releases and the changelog (Check the contents of the <releases> tag).
My question now is: If you already have code that updates a changelog from a specific source, could we update said Appstream versions with that as well.

You mention as your first step "Update the changelog in DevToys.Blazor/Assets". Is this a step done by the CI?

No, I do that manually before running the CI. Example: 1c60b39

Alright, so the Appstream file will just have to be updated manually.

I have today looked again at using the NUKE build.sh, but after looking at it today, it has opened a few questions on the best approach. So, let's go through the steps:

Update the version number in DevToys and DevToys.Tools
The build.rs in this repository does start an SetVersion task, but this does only affect the application, but not the version number of the tools. Actually, since Application and Tools are in separate repositories, Flatpak Builder currently runs them in separate steps, and the Tools repository currently has no SetVersion task. We could combine these two steps if needed though.
Update the splash screen (it changes based on whether it's a preview version or not)
Not sure if this is currently present in the publicly visible build instructions, so I'm don't know what exactly this entails.
Restore dependencies (nuget, monaco, npm...)
Mostly unproblematic, expect for the monaco part. The Restore-MonacoEditor.sh script always wants to download currently. So, there would be a switch needed, which uses the pre-loaded archive when running from Flatpak Builder.[^1]
Build the solution (dotnet build)
Fairly unproblematic, expect for the fact that build.sh will not run it when you set the target to PublishApp.
Run tests
Publish the solution (dotnet publish and pack)
Well, this is the difficult part. As of now, the build.sh wants to publish four versions, portable and not, for two architectures, on each run. In the case of Flatpak Builder the architectures part is a bit annoying. The Flatpak Builder would run separate for each architecture, with a base SDK on the other architecture. But with the current build.sh this leads to the publish step wanting to build an ARM build on the x64 SDK, which would require more pre-loaded Nuget packages for no advantage, and vice versa. So, we would want to only run publish for the architecture currently being build.
Generate installer, deb, or zips
That's fairly simple again, as it would only mean to move the finalized files to the right locations inside /app.

All these observations are based on the build system as it can be run from the build.sh script in the DevToys repository. Since you've mentioned that you use a different CI for the actual builds, I wanted to wait with patching this build system until feedback.
[^1]: Sidenote: We can detect if the build runs inside a Flatpak (as with the build) by checking that the environment variable container equals flatpak.

@veler, how do you want to proceed with this?
I see three options for this:

Use the external pipeline you've mentioned. I assume this is a third project, aside of DevToys and DevToys.Tools, which is building both elements. The manifest could be updated to use this, if it's similar to the build pipelines in the DevToys repository.
Updating the existing build systems in DevToys and DevToys.Tools with the points mentioned in my last comment.
Just repackage the released archive.

Since there are multiple options, you would need to decide which option to take.

Hello @CodedOre  :)
Sorry for the late reply.
I finally took the time to remove from our CI what I didn't want to get public, and published 99% of it on GitHub: https://github.com/DevToys-app/Publish
The unpublished part should not be needed unless you want to publish the binaries on Apple Store or Microsoft Store.
With this, my suggestion is to edit that CI to add some logic for the flatpak. There may be a bit of refactoring needed. I do admit that the code in this repository is literal garbage compared to DevToys and DevToys.Tools code.
A good entry point could be here: https://github.com/DevToys-app/Publish/blob/f8d47e1cc833beac5c57e45084ac7ea50f1735a3/src/build/Submodules/DevToys/Packing/Debian/GuiPackingDebian.cs#L14
I'd be happy to help integrating the flatpak to this. You seem to be advanced on the topic now. I'm also happy to let you draft a PR at your own rhythm. Please let me know what you prefer and how I can help :)
Thank you again for everything!

Thanks for publishing the CI, @veler.
I will look at adding the Flatpak part in the coming days.

Alright, to give an update:
I have looked at the CI, and unfortunately, the refactoring required would be more than just "a bit"...

Let's just go through to the ideas I tried in the last few days:
1. Adding Flatpak to the CI
The idea here was to add code to the CI to package the compiled program in a Flatpak and publish this to Flathub.
I did talk today with a few Flathub maintainers over on the Flathub Matrix room, and this seems to be an unlikely option. While some apps are build from external CI's, these are "exceptions for well-known projects". And it was highly recommended to use the normal submission process.
Apart from that, running Flatpak Builder inside the NUKE build environment proved to be surprisingly difficult...
So, I would drop this idea.
2. Running the CI inside Flatpak Builder
The idea here was to run the NUKE build system inside Flatpak Builder.
Well, this would need some major refactoring. Especially when looking at the Publish repository, there a lot of points where it wants to connect to the internet to load additional files, like updating the submodules, or even installing system packages (!)...
The fact that a sudoapt command is present is problematic for multiple factors, like security or incompatibility with other distributions like Fedora or Arch.
All of these are points that make it difficult to run it in the environment of Flatpak Builder. And this is ignoring the fact that it is relatively bloated, building every step and multiple arches, and even the build system on each run...

So, where does this leaves us?
I would suggest on of two options:
Option 1: Rework building entirely
As one of the Flathub maintainers put it:

it would be much simpler to focus on making your build system reliable and off line so that it can reproduce its artifacts. Most of the "we want to build it ourselves" boils down to a fragile build process which lead to more issues

I can't speak much about how this would look for Windows or Mac, but for Linux packaging, especially Flatpak, the ideal case would be an build system that can use pre-loaded dependencies and then builds offline. The build would then be started from the packaging software.
The last DevToys-Source-Flatpak archive already does this in most parts by ignoring the NUKE build. What's basically missing is a script handling the versioning update.
Option 2: Just package an existing release
Alternatively, we could just use the solution in the DevToys-Archive-Flatpak archive, use the released archives and package this. Not ideal, but better than trying to package the Flatpak inside the NUKE CI.

So, that's for the update.

I still did not look it up myself but for example Nickvionapps are Gir.Core based apps wich are packaged on flathub.
Perhaps it helps to get started.
I myself started to use F# and it's script files as build system in combination with the dotnet commandline tool. Those scripts can be called directly via dotnet fsi. They do not require any setup binaries and are providing a complete programming language at your fingertips.

I still did not look it up myself but for example Nickvionapps are Gir.Core based apps wich are packaged on flathub.
Perhaps it helps to get started.

The Nickvision apps use the Cake build system. And more importantly, don't have the build system adapting the version number on build...
Thats more or less the issue.

I myself started to use F# and it's script files as build system in combination with the dotnet commandline tool. Those scripts can be called directly via dotnet fsi. They do not require any setup scripts and are providing a complete programming language at your fingertips.

That sounds good. I think changing the version and splash screen updates to a F# script that can be run without the NUKE build would resolve that part of the issue. Will look at this later today.
@veler, your thoughts?

Question: From what I was understanding, Flatpak packaged are being installed by building sources on a local machine.

Not really. They are build before-hand, but in the case of Flathub, they are build by an CI externally of the project.

That requires all the sources to be present. Is it a bad thing that a few files are being changed on the fly so they have the right version number?

While it is, unconventional, it in itself should not be that problematic from a technical perspective. The main issue is that these steps are tied to the pipeline, which also includes a lot of steps not working well inside Flatpak Builder (e.g. downloading while building).

I'm also not super fan of the second option because a bunch of currently manual steps would need to be done.

The second option I've mentioned would just mean that the Flatpak manifest would load the released binaries from GitHub and package it, so I'm not sure about the "manual steps" you're concerned about.
If its about updates, we can add parameters to the manifest which will tell the Flathub CI to automatically check for an update and prepare the changes needed to the manifest in an pull request.
Its still not fully automatic, but manageable.

Question: From what I was understanding, Flatpak packaged are being installed by building sources on a local machine.

Not really. They are build before-hand, but in the case of Flathub, they are build by an CI externally of the project.

That requires all the sources to be present. Is it a bad thing that a few files are being changed on the fly so they have the right version number?

While it is, unconventional, it in itself should not be that problematic from a technical perspective. The main issue is that these steps are tied to the pipeline, which also includes a lot of steps not working well inside Flatpak Builder (e.g. downloading while building).

I'm also not super fan of the second option because a bunch of currently manual steps would need to be done.

The second option I've mentioned would just mean that the Flatpak manifest would load the released binaries from GitHub and package it, so I'm not sure about the "manual steps" you're concerned about.
If its about updates, we can add parameters to the manifest which will tell the Flathub CI to automatically check for an update and prepare the changes needed to the manifest in an pull request.
Its still not fully automatic, but manageable.

agreed

What about building a flatpak but distributing it manually and not via flathub?
I think this would be inline with the other already build packages and should hopefully solve all the distro specific issues there are currently.

What about building a flatpak via private CI but distributing it manually and not via flathub?
I think this would be inline with the other already build packages and should hopefully solve all the distro specific issues there are currently.
Distributing via flathub could be a separate step.

It would certainly be an option to distribute the Flatpak over an separate repository.
However, the big issue right now is that I wasn't able to integrate Flatpak Builder into the private CI. For context, Flatpak Builder uses the core functionality of Flatpak to install the SDK and probably also to run the build inside the SDK itself.
But for some reason, the environment in with the NUKE CI is running misses something for it to run. I had to stop after a few failed attempts.
In my view, the best approach right now would be to use the Source variant I've created a while ago with a patch which manually sets the right version number and submit this to Flathub to be build by their CI.


[GHSA-r628-mhmh-qjhw] Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning

Updates

Affected products

Comments
Versions before 3.0.0 doesn't have directory cache, hence aren't affected by this vulnerability.
Version 3.0.0 introduced (dirCahce)[https://github.com/isaacs/node-tar/blob/v3.0.0/lib/unpack.js#L44].
While 2.2.2 uses includes only (extract.js)[https://github.com/isaacs/node-tar/blob/v2.2.2/lib/extract.js] which doesn't have any kind of cache.

Hi there @isaacs! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our highly-trained Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

Hi @isaacs, I have made suggested based on on @evpachmanov's analysis, which appears to be correct.  If we are wrong, please correct us.

Seems correct to me. I haven't tested it to be 100% sure, but I think it's fine to update.
Is any action required of me here?

Hi @JonathanLEvans @isaacs , thank you for your prompt response!
@isaacs to my understanding the only action from your end is to update version listed in your project repository.

@isaacs can you please update the version listed in your project repository?


Quotes to output file

Necessary quotes to process the special characters of the output file and avoid errors when writing the results of the scan.
Context
When trying to run prowler in macOS I've had some problems related with writing the results of the scan. The errors are:
./include/outputs: line 72: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 415: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 416: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 417: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 418: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 419: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 420: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 421: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 422: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 423: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 424: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 425: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 426: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 427: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 428: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 429: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 430: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 431: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
./include/outputs: line 432: ${OUTPUT_FILE_NAME}.$EXTENSION_HTML: ambiguous redirect
Description
Quotes have been added in the prowler file and also in the output file. It seems this has solved the situation and now prowler is running nice.
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hi @xavi-bean, I use MacOS to develop and test and I don´t see these errors. Can you provide more information on how to replicate them?

Sorry maybe had to specify I received this error when using -M html output. Apart from this, nothing special: ./prowler -p role -r region -M html

can you try with latest version of prowler from master or at least 2.7? I can´t reproduce it. Also make sure you have bash-5.1

And could you please unify both PR to just one? Thanks in advance!

I think I have put both here now.
Run this afternoon, the version from master directly. Realized was running Python 2.7, so probably for this reason. If this is the fault, it's worth knowing prowler runs with that Python version only quoting the paths :)

$ export MY_VAR="My Value"
$ echo ${MY_VAR}
My Value
$ echo "${MY_VAR}"
My Value
$ echo '${MY_VAR}'
${MY_VAR}

Even if you use zsh Prowler will use Bash. I don't think it is related with Python at all. @xavi-bean see @lazize comment above.


Update AWS SDK to v2

Is your feature request related to a problem? Please describe.
The project is using the stable but outdated AWS SDK and should be upgraded to v2.
Describe the solution you'd like
Upgrade all AWS packages to v2 and refactor unit tests. This will have an impact on X-Ray support that should be addressed as well.
Describe alternatives you've considered
N/A
Additional context
N/A

Hello @jshlbrd , I can work on this. Can you please assign this to me?


Add missing new line in Elasticsearch admin docs

Fixes missing a new line between the text above and the list which results in mangled rendering in MkDocs.
Your pull request should…

[x] have a concise title
[x] close an accompanying issue if one exists
[x] be against the correct branch
[x] include migration scripts and documentation, if appropriate
[x] pass automated tests
[x] have a clean commit history
[x] have proper commit messages (title and body) for all commits

Reference: https://docs.opencast.org/r/9.x/admin/#configuration/elasticsearch/


Change Connect trait to alias Service

After #1782 is done, the Connect trait should be changed to basically an alias for a Service<Destination>. This would allow more composability, being able to use ServiceExt to customize connectors.

I just remember there is also MakeConnection in tower, perhaps that can just be used instead. One difference is that hyper's Connect currently returns a Connected metadata type.

@seanmonstar I totally missed this issue! But we should drop the connected struct and use http_connection::HttpConnection trait. Which pretty much does the same but allows us to be a bit more flexible. I'm honestly in the boat that we should just drop Connect or have it be what https://github.com/tower-rs/tower-http/blob/master/tower-http-util/src/connection.rs#L15 was.


[SITE]com.redphx.better-xcloud

Description
The app is malfunctioning and the app needs updates

The app has been pulled down due to the developer's request.
It has some issues to solve, see https://github.com/redphx/better-xcloud-tv/issues/10.


build: add tooling for changelog generation

Description

What is the purpose of this pull request?

This pull request:

adds tooling for generating changelog files for project packages.

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

@Planeshifter Once this is ready for another review, LMK in this thread.

...or just re-request the review using the UI.

@kgryte The PR is now ready for review after addressing all the feedback from the code review.
I have added an additional package, @stdlib/_tools/changelog/recommend-version-bump, for suggesting a version bump based on a list of commits, and reworked the @stdlib/_tools/changelog/generate return value and publish script to support a new auto option that when enabled will automatically determine the release type in the publishing process (or skip a new release if no new release is warranted.)

Thanks, @Planeshifter! I'll try and get another review in before tomorrow.


Wrong APK like a directory

Hi,
When i run the docker command i get this :
[ERROR] ERROR: Unknown error: [Errno 21] Is a directory: 'myapp.apk'.
didn't understand why... did anyone get this too?

Hi,
It looks like you created a folder named "myapp.apk" while it should be called "myapp". myapp.apk is expected to be a file.
Don't know what I'm talking about ? Run ls -l `find . -name myapp.apk`  in your directory, if you created a file/directory with that name, it should appear. If the first letter is a 'd', you created a directory.

@Ayowel, thanks for the reply!
@b4b857f6ee, let me know what the result of the above answer is.

Hi,
My command is :
docker run -e JAVA_OPTS="-Xms2048m -Xmx2048m" -p 8000:8000 -v /var/lib/docker/volumes/c7eabfc015ae3f7df9ce26b43d2c325bbdc61411b18c176a5c7ac3133f882a22/_data:/myapk -i -t stacoan myapk.apk
i get : [ERROR] ERROR: Unknown error: [Errno 21] Is a directory: 'myapk.apk'.
I already check the file with ls -lsha and i get this :
4.0K drwxr-xr-x 11 root root 4.0K Feb 14 15:27 myapk
5.2M -rw-r--r--  1 root root 5.2M Feb 14 15:26 myapk.apk

Thanks for letting me know and taking time to test this again. I will try to reproduce the issue as soon as I am home.
In a week I will make a drag and drop web interface for stocoan, so these kind of issues will be eliminated.
I really want to make this program as accessible as possible. Will keep you updated!

On 15 Feb 2018, at 18:44, b4b857f6ee<EMAIL_ADDRESS>wrote:
Hi,
My command is :
docker run -e JAVA_OPTS="-Xms2048m -Xmx2048m" -p 8000:8000 -v /var/lib/docker/volumes/c7eabfc015ae3f7df9ce26b43d2c325bbdc61411b18c176a5c7ac3133f882a22/_data:/myapk -i -t stacoan myapk.apk
i get : [ERROR] ERROR: Unknown error: [Errno 21] Is a directory: 'myapk.apk'.
I already check the file with ls -lsha and i get this :
4.0K drwxr-xr-x 11 root root 4.0K Feb 14 15:27 myapk
5.2M -rw-r--r-- 1 root root 5.2M Feb 14 15:26 myapk.apk
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

"drag and drop web interface for stocoan" That's going to be so user friendly :D. And that's how you get the most audience. :)
Good luck!

Update: we are working on the develop branch, so we didn't forget about this issue :) It's not yet done, but I expect to get a merge to master and a new release within the week.

Nice thank you!

Implemented in last commit (Master) and builds. Feel free to re-open this if you keep getting the same issue with the latest build/master code.