Why restore resolution through deconv instead of HRNet?

Compared to HRNet, the newly added deconv operation can restore the resolution again. But why not directly use 1/2 resolution in the first stage of HRNet, so that the final 1/2 resolution can be directly restored in the style of HRNet.
Is there any limitation or deficiency? This really confuses me, thank you for your answer.

@jialeli1 hi, could you share your thoughts about this ?


Generate QR Code and add it as process variable (type File?)

The service is already there but not called. I guess I didn't find a way to save the code as file in Zeebe.

added as base64 encoded string


Demo App Server Error

With the demo app here: http://www.reactrails.com/? the following message is displayed if a name is entered but no text is entered:

Your comment was not saved! A server error prevented your comment from being saved. Please try again.

If a value for text is required, this should be indicated and a more appropriate error message should be displayed as it initially appears the app is broken.

See: https://github.com/shakacode/react-webpack-rails-tutorial/issues/295


Add documentation to webhooks

Current coverage is 100% (diff: 100%)

Merging #377 into 1.0.0 will not change coverage

@@           1.0.0   #377   diff @@
===================================
  Files         23     23
  Lines       1536   1536
  Methods        0      0
  Messages       0      0
  Branches     183    183
===================================
  Hits        1536   1536
  Misses         0      0
  Partials       0      0

Powered by Codecov. Last update 3bdd354...2d6a06d

@kavdev should be g2g now 👍

@aleccool213: some quick commas will get this merged :)

messed up this PR somehow, need to fix

@kavdev should be all good now haha


Loading hosting.json fails silently on OS X

I've been struggling with problem on what happended to hosting.json. I was pointed to changes to default configuration and this discussion:https://github.com/aspnet/Hosting/issues/737. I've rewritten code and still nothing. Maybe I misunderstood something but I'm adding configuration to Program.cs (following aspnet/Templates content):
public static void Main(string[] args)
{
    var config = new ConfigurationBuilder()
      .AddJsonFile("hosting.json", optional: true)
      .AddEnvironmentVariables(prefix: "ASPNETCORE_")
      .AddCommandLine(args)
      .Build();

    var host = new WebHostBuilder()
        ..UseConfiguration(config)
        .UseUrls(Environment
  .GetEnvironmentVariable("ASPNETCORE_URLS"))
        .UseKestrel()
        .UseContentRoot(Directory.GetCurrentDirectory())
        .UseIISIntegration()
        .UseStartup<Startup>()
        .Build();

    host.Run();
}

Above does not work and configuration from hosting.json is not used to configure host.
The problem seems to be that AddJsonFile cannot read at all files within main, quickly tested with:
.AddJsonFile("hosting.json", optional: false)

this results in exception and failure:

dotnet run
Project StarterWeb (.NETCoreApp,Version=v1.0) was previously compiled. Skipping compilation.
Unhandled Exception: System.IO.FileNotFoundException: The configuration file 'hosting.json' was not found and is not optional.
   at Microsoft.Extensions.Configuration.FileConfigurationProvider.Load()
   at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build()
   at StarterWeb.Program.Main(String[] args)

Using full path does not help:
.AddJsonFile(Path.Combine(Directory.GetCurrentDirectory(), "hosting.json"), optional: false)

Unhandled Exception: System.IO.FileNotFoundException: The configuration file '/Users/piotrblazejewicz/git/recipes/src/gulp-dotnet-browser-sync/StarterWeb/hosting.json' was not found and is not optional.
   at Microsoft.Extensions.Configuration.FileConfigurationProvider.Load()
   at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build()
   at StarterWeb.Program.Main(String[] args)

Thanks!

You need to actually use the configuration you setup by calling UseConfiguration
var config = new ConfigurationBuilder()
      .AddJsonFile("hosting.json", optional: true)
      .AddEnvironmentVariables(prefix: "ASPNETCORE_")
      .AddCommandLine(args)
      .Build();

    var host = new WebHostBuilder()
        ...
        .UseConfiguration(config)
         ...
        .Build();

    host.Run();

@davidfowl Thank! I've been updating snippet
No, that's not that problem. I've found a tip here:
https://github.com/aspnet/Configuration/issues/421#issuecomment-206569908
I had to explicitly call SetBasePath:
.SetBasePath(Directory.GetCurrentDirectory())

var config = new ConfigurationBuilder()
  .SetBasePath(Directory.GetCurrentDirectory())
  .AddJsonFile("hosting.json", optional: true)
  .AddEnvironmentVariables(prefix: "ASPNETCORE_")
  .AddCommandLine(args)
  .Build();

var host = new WebHostBuilder()
    .UseConfiguration(config)
    .UseUrls(Environment
.GetEnvironmentVariable("ASPNETCORE_URLS"))
    .UseKestrel()
    .UseContentRoot(Directory.GetCurrentDirectory())
    .UseIISIntegration()
    .UseStartup<Startup>()
    .Build();

host.Run();

Thanks!


Update OCI due to outdated packages

Issue
Security scan report:
Revision r61 (amd64; channels: 14/edge)
 * libc-ares2: 6164-1

Solution
Rebuild and update rock

Rolled into #185


JEP-15 String Slices

This PR implements JEP-15 String Slices from JMESPath Community.
This PR proves surprisingly hard to design as the JMESPath AST hard-wires slices inside a projection.
Therefore, there is no easy way to know if we should keep the result of evaluating children if they do not return an array that would be illegal before this PR.
Consider the following two expressions:

foo[*].bar the grammar specifies this as a sub-expression but the Python implementation produces the following AST instead:

{
  "type": "projection",
  "children": [
    {"type": "field", "value": "foo"},
    {"type": "field", "value": "bar"}
  ]
}

Contrast with the following expression:

foo[::-1] The grammar specifies this as an index-expression and, close enough, the Python implementation produces the following AST:

{
  "type": "projection",
  "children": [
    {
      "type": "index_expression",
      "children": [
        {"type": "field", "value": "foo"},
        {"type": "slice", "children": [ null, null, -1 ]}
      ]
    },
    {"type": "identity"}
  ]
}

In both cases, we see that there is an additional "projection" AST node that wraps the parsed construct and is used for evaluation.
I had to resort to special-case visit_projection with the exact shape of the AST to recognize slices and accept string results.
        allow_string = False
        first_child = node['children'][0]
        if first_child['type'] == 'index_expression':
            nested_children = first_child['children']
            if len(nested_children) > 1 and nested_children[1]['type'] == 'slice':
                allow_string = True

        if isinstance(base, string_type) and allow_string:
            return base

I think there should be a better way. 😥

I think the concept of projection should not be an AST node, but instead should be promoted to a first-class runtime concept. That is, evaluating a node should either return:

One of valid JSON-compatible "scalar" outputs: string, null, boolean, number, array and object.
Or a new first-class output: projection.

A projection is a concept similar to an array, with the exception that a projection is not evaluated as a whole by downstream nodes. Instead, each of its constituting parts is unwrapped and sent to downstream nodes for evaluation. The results are then collected to produce a single output.
By default, the output is also a projection, unless a pipe-expression is evaluated which demotes the projection to a regular array. If the output of the whole expression yields a projection, it is likewise demoted to an array before returning.
A projection would be a runtime decision of evaluating a node, rather than hard-wired by the shape of the AST.
For instance, visit_slice could decide to return either a string or a projection.


yarn start failed

node:internal/modules/cjs/loader:571
throw e;
^
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/tokenize' is not defined by "exports" in /Users/bhargav/Documents/SAMPLE-REACT/React-app/node_modules/react-scripts/node_modules/postcss/package.json
at new NodeError (node:internal/errors:399:5)
at exportsNotFound (node:internal/modules/esm/resolve:361:10)
at packageExportsResolve (node:internal/modules/esm/resolve:697:9)
at resolveExports (node:internal/modules/cjs/loader:565:36)
at Module._findPath (node:internal/modules/cjs/loader:634:31)
at Module._resolveFilename (node:internal/modules/cjs/loader:1061:27)
at Module._load (node:internal/modules/cjs/loader:920:27)
at Module.require (node:internal/modules/cjs/loader:1141:19)
at require (node:internal/modules/cjs/helpers:110:18)
at Object. (/Users/bhargav/Documents/SAMPLE-REACT/React-app/node_modules/react-scripts/node_modules/postcss-safe-parser/lib/safe-parser.js:1:17) {
code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}
Node.js v18.15.0
Needed some help....

Hey, can you share some more details?
It seems like you are trying to import something which is not exported by default.


README update

Bug/issue #, if applicable:  N/A
Summary
Improvements made to the README file that aims to reduce confusion and guidance on how to use the tool.
It also provides a link to a starter template with the essentials to start writing a DocC catalog.
Dependencies
N/A
Testing
N/A
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

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

Thanks for the feedback!
Most of the comments were resolved in the latest commit (https://github.com/apple/swift-docc/pull/695/commits/410c4d477809636c7504e995e1bf9cc82d6616a8)
@Kyle-Ye @heckj @natikgadzhi @daniel-grumberg @ethan-kusters

@swift-ci please test


Lab 6, Ex 7, Task 4

Module: 6
Lab/Demo: 6
##Exercise: 7
Task: 4
Step: 3-4
The email the user receives might not have this subject and text. It depends what payload you selected when setting up the spear phishing simulation in Exercise 5.

Thanks Annette. I have updated the steps accordingly. Please note that I'm releasing an update to MS-102 on 6/14. This includes a number of minor updates to the labs. This fix will be included in that release.

Thanks Tony.  Will the changes to MS-102 later this month be very extensive? I'm just trying to work out how much prep I'd need to do for the updated version.


PDF Generation

The goal of this epic is to Add creating PDFs to DCS.
The user should be offered some basic layout options like double column and double spacing, margins and page size:
Private Zenhub Image
The user should be presented with a typical print dialog:
Private Zenhub Image

@larsgson @richmahn I've made an epic here. Please add specific issues to this epic so you can work on them during the next sprint.


Unhide the Convert Button and make it function, swapping sats between BTC wallet (Breez-SDK) and USD wallet (IBEX)

[ ] Unhide Convert button, change label to "Swap"
[ ] Show Balances on each Wallet in the convert-details screen
[ ] Get the toggle button to work, toggling between BTC->USD and USD->BTC
[ ] Complete the conversion using breez-sdk calls and IBEX GraphQL calls instead of the galoy flow.

dunno why the screenshots are so big lmao


add distance matrix API

Google Distance Matrix API
I updated the tests, but they are brittle because Google will return different data over time (latitude, longitude, etc.) and we can't pattern match using doc tests (at least I don't know how to).

Thank you so much! I agree on the doctests, as I couldn't find a good way to deal with the results either.
Would you mind updating the README to include this new API?

README is updated now


Upgrade of jackson to >2.6.X to be compliant with elasticsearch 2.X

What about graviteeio-definition-jackson module ?
Do we have to upgrade it also ?

No, it's not necessary but we can...


[BUG] Webpage loading fails after run azd up, occasionally reloads successfully

Description
After run command azd up, click the endpoint to load web page, an error occurred, and in 5 reload results, 2 were successful and 3 had this error, as follows:

Repro steps

Run azd auth login.
Run azd init --template cosmos-db-nosql-dotnet-quickstart.
Run azd up.
Click the web link.

Expected behavior
After running azd up, the web page can be loaded successfully and stably.
Environment

Azd version: azd version 1.10.3 (commit 0595f33fe948ee6df3da492567e3e7943cb9a733)
OS: Windows
Templates: https://github.com/azure-samples/cosmos-db-nosql-dotnet-quickstart

@hemarina and @seesharprun for notification.

This is a transient bug I'm seeing with ACA related to websocket ports. I'm switching the deployment to App Service to see if that permanently resolves this port issue.

This has been fixed by setting up WebSocket polling

After testing the latest code, web page loading still fails, and occasionally reloading succeeds. The error page is as follows:

There seems to be an issue with the HTTPS transport in Azure Container Apps.

Related to #57

This should now be fixed.


Generate bindings in CI and error if not up-to-date

Alternatively, should it auto-update the bindings and commit?

@tjjfvi this is no longer relevant if I'm not mistaken? Can we close?


2.4.0 Release: Run Google Internal Tests

Looks like the only commits since the last Google import are docs changes.


Implement process-based plugins

Faster plugin responses! Concurrency! What's not to love?

FYI, created a separate repository where I've been working on a framework for process-based plugins: https://github.com/JohnMaguire/pplugins
Consider it the yapsy of multiprocessing. It seems to be working pretty well at this point. I plan to write some unit tests and then implement it here.

I just hit 100% test coverage! Will be implementing in Cardinal soon.

Not gonna do this. Instead, we'll use more Deferreds in Twisted.


Upgrade to Polkadot v0.9.37

Because of Cumulus not released 0.9.34 and 0.9.35 so we upgrade from 0.9.33 to 0.9.37
https://github.com/paritytech/polkadot/releases/tag/v0.9.34
https://github.com/paritytech/polkadot/releases/tag/v0.9.35
https://github.com/paritytech/polkadot/releases/tag/v0.9.36
https://github.com/paritytech/polkadot/releases/tag/v0.9.37
https://github.com/paritytech/substrate/compare/polkadot-v0.9.33...polkadot-v0.9.34
https://github.com/paritytech/substrate/compare/polkadot-v0.9.34...polkadot-v0.9.35
https://github.com/paritytech/substrate/compare/polkadot-v0.9.35...polkadot-v0.9.36
https://github.com/paritytech/substrate/compare/polkadot-v0.9.36...polkadot-v0.9.37
Breaking changes:

https://github.com/paritytech/substrate/pull/12891

Notable changes:

https://github.com/paritytech/substrate/pull/12310
https://github.com/paritytech/substrate/pull/12775
https://github.com/paritytech/substrate/pull/12813
https://github.com/paritytech/substrate/pull/12844
https://github.com/paritytech/substrate/pull/13045
https://github.com/paritytech/substrate/pull/13066
https://github.com/paritytech/substrate/pull/13080

In addition:

Sync Phala to https://github.com/Phala-Network/phala-blockchain/commit/c5056e01edc0a8747cf6164742bd3636de3cfaef
Use Rust nightly-2023-02-03

Because of we need to run migrations for assets and balances in this version, I think we should upgrade Phala parachain as well
We need test migration carefully
TODO:

Evaluate that should we bump tx version? @h4x3rotab

https://github.com/paritytech/cumulus/issues/2017#issuecomment-1361582387
For Phala, we skip too much versions and we bumped for Khala before, should we do for Phala?

Evaluate assets pallet migration @tolak

https://github.com/paritytech/cumulus/pull/1742

Evaluate balances pallet migration @tolak

https://github.com/paritytech/cumulus/pull/1943
https://github.com/paritytech/substrate/pull/13009
the migration trigger again on Statemint on 0.9.36 https://github.com/paritytech/cumulus/pull/2031

(not blocking) wating reply from Parity about --state-pruning issue

NOTE:
test memdb::tests::consolidate ... FAILED
test memdb::tests::memorydb_remove_and_purge ... FAILED

failures:

---- memdb::tests::consolidate stdout ----
thread 'memdb::tests::consolidate' panicked at 'called `Option::unwrap()` on a `None` value', crates/phala-trie-storage/src/memdb.rs:579:56

---- memdb::tests::memorydb_remove_and_purge stdout ----
thread 'memdb::tests::memorydb_remove_and_purge' panicked at 'called `Option::unwrap()` on a `None` value', crates/phala-trie-storage/src/memdb.rs:547:52
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    memdb::tests::consolidate
    memdb::tests::memorydb_remove_and_purge

test result: FAILED. 1 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

Relates to Phala repo

Re. tx version: Let's check how tx version affects the blockchain behavior in substrate. If it's only for external signer (e.g. hardware or mobile wallet) to distinguish changes in extrinsic args, we'd rather just keep it as is. However, if it affects the security of the blockchain, we have no choice but update it.

I shall merge this, feel free to double check it


Help me I dont know what im doing

Hi how do I use this. I'm not too smart with computers just wanna listen to music

Hi @serikbol … this is an app that displays lyrics for whatever song you're currently listening on Spotify. That being said, you should download and install Spotify first.
Once that's done you can download Lyricfier from the releases section. Unless you're rocking some old hardware, you probably want the x64 version for your platform (Windows, Linux, or Mac)

Maybe the issue here is a better readme and nicer download buttons for each plattform? @silvestreh ?

Thanks I've gotten that far but are the lyrics supposed to show up when I
play music? Because they're not showing up
On 20 Oct 2016 00:40, "Emilio Astarita"<EMAIL_ADDRESS>wrote:

Maybe the issue here is a better readme and nicer download buttons for
each plattform? @silvestreh https://github.com/silvestreh ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/emilioastarita/lyricfier/issues/8#issuecomment-254961972,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AV4X-KGd0SLbddqNwsH8KRjWWxZlkIIRks5q1px3gaJpZM4KbWbt
.

Yes. If you have spotify and lyricfier open, lyricfier it's supposed to show the lyric of the current song.
Could you provide the message that you see at the bottom box of the lyricfier app when you change the song ? Do you see any error or anything?

open spotify
open lyricfier
play a song
take a look at lyricfier, should show lyric actually
that's all

Hope do I open lyricfier because I only see vlc files and other stuff
On 20 Oct 2016 15:45, "Emilio Astarita"<EMAIL_ADDRESS>wrote:

Yes. If you have spotify and lyricfier open, lyricfier it's supposed to
show the lyric of the current song.
Could you provide the message that you see at the bottom box of the
lyricfier app when you change the song ? Do you see any error or anything?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/emilioastarita/lyricfier/issues/8#issuecomment-255109977,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AV4X-N0VXUuBNQ8OkxpsyZw9oDcGSM0gks5q13CBgaJpZM4KbWbt
.

K realised I was being stupid so thanks and sorry for letting me waste your
time
On 23 Oct 2016 16:46, "Endru Reza"<EMAIL_ADDRESS>wrote:

open spotify
open lyricfier
play a song
take a look at lyricfier, should show lyric actually
that's all
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/emilioastarita/lyricfier/issues/8#issuecomment-255592628,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AV4X-F07TG3PpyZkbYWHiHOFcy1XVytrks5q23MwgaJpZM4KbWbt
.

@serikbol Lyricfier doesn't open any type of file. What it does is find lyrics for whatever song you're currently listening on Spotify and only Spotify.


bug on inactivityTimeout

I create a WebSocketLink to use it with my graphql client
The config specify an inactivityTimeout of one hour
But when i subscribe or connect with the link the connection keeps reseting

Code:
SocketClientConfig config = SocketClientConfig(
      initialPayload: () => {"Authorization": "Bearer $token", "Language": appInfo.myLocale.languageCode},
      autoReconnect: true,
      inactivityTimeout: const Duration(hours: 1),
    );
    link = WebSocketLink(
      useProd
          ? kWSProdUrl
          : useLab
              ? kWSLabUrl
              : usePreprod
                  ? kWSPreprodUrl
                  : "",
      config: config,
    );

But i get every 30s this message and this reset my connection :

Logs:
I/flutter ( 7372): Disconnected from websocket.
I/flutter ( 7372): Initialising connection

device / execution context
I tested on iOS simulator & android physics device same problem
additional context
Backend work nice my coworker with vue.js client don't get this problem

Fixed by #1145


php: builder

Towards #240

[x] Add a builder
[ ] ~Add php examples~ (need the builder merged first)
[x] dev shell
[x] Update php docs
[x] more robust semver implementation
[x] discoverer

Disable packagist.org repo for composer, use artifact or path repositories.

Tested on https://github.com/composer/composer, build and devShell both work as expected.

[ ]  ~Add php examples~ (need the builder merged first)

That should not be necessary. You can add the example flake under /examples/php/flake.nix, and then execute from the repo root: nix run .#tests-examples php
Alternatively navigate to /examples/php, then run:
nix flake lock --override-input dream2nix ../../
and
nix run .#resolveImpre / nix build ..etc.

I just added an example via e77c129ad6643cf7deb26d71e00c551e89ab285b. Working fine.

It seems like the composer example adds significant overhead to the test execution. That is probably because of the slow nix git fetching. Maybe we can replace the example with a project, that doesn't have many dependencies.

@DavHau
I've disabled checks on the composer example, which speeds it up a little.
Running the tests locally I get:
Execution times:
1 sec: _d2n-indexer
37 sec: php_composer        <<--
44 sec: nodejs_workspace
52 sec: _d2n-extended-new-subsystem
56 sec: _d2n-init-pkgs
56 sec: rust_ripgrep
83 sec: nodejs_prettier
85 sec: _d2n-extended
131 sec: nodejs_eslint
143 sec: debian-binary
144 sec: rust_set-rust-toolchain
155 sec: rust_no-cargo-lock
163 sec: nodejs_mattermost-webapp
175 sec: python_aiohttp
209 sec: haskell_stack-lock
210 sec: nodejs_eslint-aggreagted
281 sec: haskell_cabal-plan

Thanks for this, I recently tried this builder on one of the projects but got this error:
error: Constraint "as" could not be parsed

The project composer.json uses aliases as described here:
https://getcomposer.org/doc/articles/aliases.md#aliases

@aszenz
The builder does not handle some less-common composer features at the moment (like composer plugins, php version constraints, composer api, aliases, ...).
Could you link to the project or if it's a private, make a small example of the composer.json that produces this error?

@aszenz Thank you for noticing and reporting this. The builder does not handle some less-common composer features at the moment (like composer plugins, php version constraints, composer api, aliases, update/install script hooks, ...). Could you link to the project or if it's a private, make a small example of the composer.json that produces this error?

Sure here's a sample project on which running nix build .#packages.x86_64-linux.app/php fails with:
error: Constraint "as" could not be parsed
https://github.com/aszenz/php-app-nix
If i remove the as then i get an error about missing extensions, seems like the php extensions mentioned in composer.json are not available when the build runs

@aszenz
#296 fixes both issues (inline version alias, extra php extenstions)


Update sv-SE.ts

Description

Edited the swedish localization package to more match the en-US package that is managed by the clerk team. This to make us swedes have a more complete authentication system in swedish and not mix swedish and english as before.
Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[x] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Fixed the reverts, we should be good to go now!


Added Keepalive interval login settings

Changes
Resolves https://github.com/codefori/vscode-ibmi/issues/2074
This PR adds a new input to the Logins settings to let the user define a custom SSH Keepalive interval.

How to test this PR
Set a breakpoint in src/api/IBMi.ts on line 126.

Open an existing connection
Define a custom Keepalive interval
Connect
Check the connectionObject.keepaliveInterval field is set with the custom value.

Checklist

[x] have tested my change

@sebjulliand Code works as expected - but the setting does not prevent the disconnect, unfortunately... 😞
I'm not sure how or if we can fix #2069... would have thought the keepalive setting was the solution, but apparantly not...
Maybe you should break this PR into two PR and isolate the other fix for private key path in its own PR?

Maybe you should break this PR into two PR and isolate the other fix for private key path in its own PR?
@chrjorgensen absolutely. I removed the private key fix from here and put it there: https://github.com/codefori/vscode-ibmi/pull/2082

absolutely. I removed the private key fix from here and put it there: #2082

@sebjulliand Great! I changed this PR to draft... when we find a solution we can continue here if necessary...

@sebjulliand is this actually ready to be reviewed?

@worksofliam welp, it was changed to draft since it doesn't seem to fix the original issue, even though the keepalive is adjusted (checkout @chrjorgensen comment above).

@sebjulliand I suspect it's also related to the timeout as set by the OS. @chrjorgensen What do you see with CHGTCPA? I believe there is a timeout option there too which might be similar.


Adding support to get details for TargetPrefix

This PR adds the functionality needed in this code changes: https://github.com/gruntwork-io/terragrunt/pull/1507
With this PR we can:

get the TargetPrefix specified for a state bucket with enabled access logging

Issue linked: https://github.com/gruntwork-io/terragrunt/issues/1437

Took me a while in the midst of support to come back here (I thought it would require a lot more changes, but turns out it was this quick).
Another look would be very appreciated!

Thanks Jim!


WIP: Resolve: "Move Docker Container to Arch Linux"

Closes #95

CodeFactor is not happy with the changes, but some of them have to be made in order to get Scuba to work on macOS. Waiting for input from @JamesOrson since he's better at Docker than anyone else on the team.

CodeFactor is not happy with the changes, but some of them have to be made in order to get Scuba to work on macOS. Waiting for input from @JamesOrson since he's better at Docker than anyone else on the team.

CodeFactor is complaining about the last user being root, but from what I can tell, scuba needs that to create users.


Minor thing with View file not found exception...

View/View.php:178
throw new \InvalidArgumentException('View file not found: '.$file);
when throwing exception prints only: "'View file not found: "
I think there is a place for small improvement:
throw new \InvalidArgumentException('View file not found: '.$view);
when exception will be thrown it  will #print: "'View file not found: not-existing-view-file.php"

Good catch. Thanks. Will have that fixed momentarily.

Fixed in a1f71ea6a3fe38408cf25c9cbd3495c68973cb9a


Fix OAuth prompt should store in turn.token, not dialog.token

Fixes:

Composer docs issue 121
Related Composer issue 6767.
Also see Jonathan's pr 5660

Description
This fixes the tests covering Jonathan Fingold's patch in the file Microsoft.OAuthInput.schema. He changed "dialog.token" to "turn.token".
Specific Changes
The same change made in tests/Microsoft.Bot.Builder.TestBot.Json/testbot.schema and tests/tests.schema.

Pull Request Test Coverage Report for Build 252749

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 78.903%

Totals

Change from base Build 252652:
0.0%

Covered Lines:
18188

Relevant Lines:
23051

💛  - Coveralls


Side bar leaves a blank white space when window is resized

Fix side bar resize (M-UI)

upgrade Material UI side bar component?

duplicate of #277


build: bump MSRV to 1.65

The latest version of the time crate requires Rust 1.65.0
cargo +1.64.0-x86_64-apple-darwin test --no-default-features \
  --features serde,crossterm,all-widgets --lib --tests --examples
error: package `time v0.3.21` cannot be built because it requires rustc
1.65.0 or newer, while the currently active rustc version is 1.64.0

The calendar widget added a dependency on time v0.3.11 (though a quick check suggests that 0.3.9 compiles, I'm unsure if the later bug fixes are notable for ratatui. Regardless, the dependency requirement is satisfied by any version later than 0.3.11. Later versions require rust 1.65.0, so our MSRV is 1.65.0.
I don't think there's an obvious way to only specify a MSRV for a specific set of features (i.e. 1.59 if you're not using termwiz/calendar), though perhaps we leave this as 1.59, and create a specific 1.59 test in the ci that doesn't test calendar and termwiz. I'm not certain I know why we'd do that (ping @rhysd for input on what the reason for supporting 1.59 was in https://github.com/tui-rs-revival/ratatui/pull/85
I'm a rust noob, so my experience with the impact of choosing an MSRV is limited. I've seen a few libraries that state a policy of supporting stable minus 2 version, which seems reasonable on the face of it. If we took that approach, we'd go with 1.67 which was released Jan (26 2023). But we only "need" to go to 1.65 for now.

Re: failures - I didn't know numeric types had From<bool> now!
Re msrv and dependencies and how they interact - that's still open and ongoing discussion: https://github.com/rust-lang/cargo/issues/9930
I think bumping this is fine, probably a good idea to make clippy happy at the same time.

Pushed clippy fixes (and added the following to the commit):
Also fixes several clippy warnings added in 1.63/1.65. Although these
have been since moved to nursery / pedantic, it doesn't hurt to fix
these issues as part of this change:
- https://rust-lang.github.io/rust-clippy/master/index.html#derive_partial_eq_without_eq (nursery)
- https://rust-lang.github.io/rust-clippy/master/index.html#bool_to_int_with_if (pedantic)

Interestingly enough, when I run cargo-msrv it says the MSRV is 1.60.0.
However if I run cargo msrv -- cargo check --features all-widgets then the MSRV is 1.63.0

For some reason, I get different results from this PR. Is there any other way to validate?

For some reason, I get different results from this PR. Is there any other way to validate?

Yep, run cargo update - the time crate is at 0.3.21 which requires rust 1.65.0.
❯ cargo msrv -- cargo check --all-features
Fetching index
Determining the Minimum Supported Rust Version (MSRV) for toolchain x86_64-apple-darwin
Using check command cargo check --all-features

Check for toolchain '1.63.0-x86_64-apple-darwin' failed with:
┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ error: package `time-core v0.1.1` cannot be built because it requires rustc 1.65.0 or newer, while the currently active rustc version is    │
│ 1.63.0                                                                                │
└─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
Check for toolchain '1.66.1-x86_64-apple-darwin' succeeded

Check for toolchain '1.64.0-x86_64-apple-darwin' failed with:
┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ error: package `time v0.3.21` cannot be built because it requires rustc 1.65.0 or newer, while the currently active rustc version is 1.64.0 │
└─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
Check for toolchain '1.65.0-x86_64-apple-darwin' succeeded
   Finished The MSRV is: 1.65.0   ████████████████████████████████████████████████████████████████████████████████████████████████████ 00:00:06

Yep, run cargo update - the time crate is at 0.3.21 which requires rust 1.65.0.

Good point! I got 1.65.0 as MSRV now.


Use common columns for incremental schema changes

resolves https://github.com/dbt-labs/dbt-core/issues/4144
Description
In this PR, process_schema_changes is modified to return the dict with schema changes information so that the column changes in incremental materialization can be managed by plugins (dbt-bigquery, dbt-snowflake).
Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR => tests on adapters
[x] I have updated the CHANGELOG.md and added information about my change

@Kayrnt I really like the approach you're taking, here + in dbt-labs/dbt-snowflake#38 + dbt-labs/dbt-bigquery#51.
When would you feel ready for a review?

I had little free time so far this week (lot of work) but hopefully I'll have some time this weekend, I think it should be working but I didn't had time to test so far. TBH I'm quite struggling on how to have a local build of DBT bigquery / snowflake packages packaged locally and integrated with a local DBT build as well if you have some contributing guide such as https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md for those package that would be pretty helpful! (I couldn't have setuptools to work as intended) 🙏
So far what I think I have to do:

Test locally the PR fixes the issue on BQ (I don't have a snowflake env)
Add/modify an IT on Snowflake

@github-christophe-oudar Makes sense! You're right, we should update the contributing guide to talk about coordinating changes to multiple (non-Postgres) adapters.
What I do, roughly, is clone each package (dbt-core, dbt-bigquery, dbt-snowflake) locally, and then:
cd scratch-project
python3 -m venv env
source env/bin/activate
pip install -e <path/to/core/repo>/core -e <path/to/snowflake/repo> -e <path/to/bigquery/repo>

Since the only change to dbt-core are to macros (process_schema_changes etc), you can also test the changes in your local project by copy-pasting the edited versions of those macros into your local macros/ folder. That might be easier, you just need to remember to copy the edited macros back into the dbt-core PR when you're done :)

Thanks for the commands @jtcohen6!
I used pip install -e  ../../tools/dbt-bigquery -e  ../../tools/dbt -e  ../../tools/dbt-snowflake and it worked... but the code from the dbt-core part wasn't used at the runtime: it's weird because changes on dbt-bigquery are properly reflected with that pip install. However I used the /macros directory trick from my model project and verified it worked as intended... actually there was a bug I fixed (it's the source and not the target for add column as target = table existing, source = the tmp table).
However I'm not sure for the snowflake part :/
Could you help me with that?

Hello @jtcohen6, thank you for your suggestions!
Indeed I didn't look into Postgres/Redshift but if those DBs also support incremental on DBT, that would be a shame not to support them too.
I'll have a look at your other review on BQ adapter.
I thought too that the branching was a bit overkill, it was a "safety measure" in case of a custom strategy that wouldn't update the target table in the DB before the merge code that would result in failing query.
I'll remove it and I guess we can expect someone making a custom strategy making the appropriate changes if needed.
I cherry-picked your commit and added the review change to the changelog.
It looks like tests are passing.

I thought too that the branching was a bit overkill, it was a "safety measure" in case of a custom strategy that wouldn't update the target table in the DB before the merge code that would result in failing query.
I'll remove it and I guess we can expect someone making a custom strategy making the appropriate changes if needed.

That's a fair thought! The alternative is, rather than having process_schema_changes return the full schema_changes_dict, it could return just the list of common_columns (i.e. dest_columns to use when merging/upserting). Then, the materialization code just pulls in the returned value:
    {#-- Process schema changes. Returns dict of changes if successful. Use source columns for upserting/merging --#}
    {% set dest_columns = process_schema_changes(on_schema_change, tmp_relation, existing_relation) %}
    {% if not dest_columns %}
      {% set dest_columns = adapter.get_columns_in_relation(existing_relation) %}
    {% endif %}

If a user overrides the on_schema_change macro family with a custom mode, they'd just need process_schema_changes to return the right set of columns as a last step, and they wouldn't need to reimplement the incremental materialization as well.
What do you think?

(closing and re-opening to trigger Postgres integration tests, now that I've added ok to test label)

I'm ok with both approaches:

Either we have a quite exhaustive set of generic columns related informations (source, target, intersection, disjunction, ...) as done in this PR so far and then the incremental strategy pick what's matching.

If we want to keep it lean, going for returning as little as necessary might be better indeed (especially since this is done on every run from all users of incremental models).
Let me know if you think I should make the change.

@github-christophe-oudar Let's go lean!
I suppose it is possible to imagine an incremental strategy that would want other information, besides the set of common columns (post-schema evolution). All strategies that exist today want to operate on a single set of shared columns, named dest_columns. Nor is it possible for users to define and register totally new incremental strategies, without also reimplementing several other macros and/or the incremental materialization (but it's worth thinking more about: #2366).

Ok I updated the 3 PRs with related code 👍
You're right, as so far, I don't really see a common incremental strategy that would require more than those common fields.

Sure let's go ahead for this one! 🚀
Regarding dbt-snowflake & dbt-bigquery, sure I can handle adding a new integration test case, I gotta go but I should be able to get those added in the evening. I'll see if I can get one more in dbt-redshift as well.
I'm used to fetch & rebase whenever I push so no worry we should be good 👍

Great that we're able to move quite fast on this topic!
I think it's one of my latest pain point regarding DBT! I'm looking forward to using these changes in production 🙌
Merci de passer une partie de ton dimanche pour faire avancer tout ça ! 🙏


Use attribute 'temporarilyOffline' instead 'offline' for enabling/disabling nodes.

Using the 'offline' attribute to decide whether to toggle the state of nodes on activation/deactivation results in incorrect behavior. If a previously activated node is offline, e.g. because there is no connection, and you use the noce enable function, it will be actually deactivated. The attribute 'temporarilyOffline' must be used instead.
Also see https://github.com/pbelskiy/ujenkins/pull/9.

Using the 'offline' attribute to decide whether to toggle the state of nodes on activation/deactivation results in incorrect behavior. If a previously activated node is offline, e.g. because there is no connection, and you use the noce enable function, it will be actually deactivated. The attribute 'temporarilyOffline' must be used instead.
Also see pbelskiy/ujenkins#9.

Thanks for PR. What about jenkinsapi approach? When to prevent this they raise exception, when node online but disconnected.
https://github.com/pycontribs/jenkinsapi/blob/master/jenkinsapi/node.py (207 line)
I suggest to do the same, and also add new function to nodes module, like launch_agent.
So you can do something like that in your case:
import asyncio
import aiojenkins

jenkins = aiojenkins.Jenkins('http://your_server/jenkins', 'user', 'password')

async def main():
    try:
        await jenkins.nodes.enable('some_node')
    except aiojenkins.JenkinsNodeError:
        await jenkins.nodes. launch_agent('some_node')

asyncio.run(main())

What do you think? And what disadvantages of this?

There is some problem with coveralls and PRs, I gotta fix it firstly.

I think if the attribute "temporarilyOffline" is false and a previously disrupted connection to the agent is re-established, the agent will start on its own.
Also with the jenkinsapi method, you have no way to disable nodes that are not currently connected.

@manox Hello! Could you rebase please? I've probably fixed coveralls problem on PRs

Coverage remained the same at 97.084% when pulling 1de11a175859bd12cf7966b23c3fc404bf19cfcb on manox:master into 65cebf802b774014865ed66281d4f34d51f26139 on pbelskiy:master.

There are three states of a node:

disconnected (offline is True and temporarilyOffline is False)
enabled (temporarilyOffline is True)
disabled  (temporarilyOffline is False)

enable():

disconnected -> skip or raise NodeError?
enabled (temporarilyOffline is True)
disabled  (temporarilyOffline is False)

disable():

disconnected -> skip or raise NodeError?
enabled -> disable node
disabled -> pass

With the described division of the states, they are not unique. I think about the states differently. In my way of thinking there are the following 3 states:
1) online (`offline` is False and `temporarilyOffline` is False)
2) offline (`offline` is True and `temporarilyOffline` is False)
3) disabled (`temporarilyOffline` is True)

For example official Java client of Jenkins are so poor, and has only toggle method.
https://github.com/jenkinsci/java-client-api/blob/master/jenkins-client/src/main/java/com/offbytwo/jenkins/model/ComputerWithDetails.java


RzGate(alpha).to_matrix() is missing

In order to refactor qiskit/extensions/quantum_initializer/ucg.py, there is a need for RzGate(alpha).to_matrix().

This issues if fixed in current master. Probable via #4565


Create Sound Swapper Plugin

A generic Sound Swapper plugin.
Allows the user to enter a list of comma-separated sound names (e.g. blood_cast,warhammer_crush,fire_bolt_all) and replaces those sounds with matching .wav files in the RuneLite root directory (e.g. blood_cast.wav).
This is based on the list currently on the OSRS wiki here: https://oldschool.runescape.wiki/w/List_of_in-game_sound_IDs

I'm not really sure why you've split SoundIds into two maps instead of just one. (You mention hitting some "max size"... Maps don't have a max size defined.)
Rather than having users put sound files directly inside ~/.runelite, create a directory under there which is specific to this plugin.

It was actually a Java issue. There is a byte limit (65535) on the amount of code that can make up any single function, object, etc. Never heard of it before this, but also never dealt with a multiple thousand line map before.
Will do for the directory. Should I be generating this directory with the plugin or just ask the user to drop the files in a directory with the plugin name?

You can build the maps using an immutable map builder or something instead. We use that pattern in numerous places in the core client.
This directory should definitely be created by the plugin so that users can't make one with the wrong name or anything like that by mistake.

Got it, thanks!

Updated to use a folder in the .runelite directory to hold sound files.
I looked into the ImmutableMap.Builder and decided to stick with the double HashMap instead. There is no "ImmutableHashMap" and I prefer to use hashing here for 0(1) searches since the list is so long.


Adding a test for infinite time token generation

Purpose
Fixes: https://github.com/wso2/product-apim/issues/9541
Goals
Adding a test for infinite time token generation
Approach

Added a test to generate an infinite time token and invoke an API (for both Production and Sandbox endpoints)

Related PRs

https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/1507

Test environment

JDK 1.8.0_251
Ubuntu 20.04.2 LTS

@wasuradananjith  could you please update the branch with master


Fixed error in the Dockerfile

VOLUMES is not a Dockerfile command, VOLUME is, fixed the typo so not the build completes.

I did this too with #7, with no response yet. @jacksoncage would you like to merge one of these?


feat: log to cloudwatch (+minor refactor)

VULN4OS-189
Secure Coding Practices Checklist GitHub Link

https://github.com/RedHatInsights/secure-coding-checklist

Secure Coding Checklist

[x] Input Validation
[x] Output Encoding
[x] Authentication and Password Management
[x] Session Management
[x] Access Control
[x] Cryptographic Practices
[x] Error Handling and Logging
[x] Data Protection
[x] Communication Security
[x] System Configuration
[x] Database Security
[x] File Management
[x] Memory Management
[x] General Coding Practices

Codecov Report
Base: 59.00% // Head: 58.67% // Decreases project coverage by -0.33% :warning:

Coverage data is based on head (4377900) compared to base (41d6525).
Patch coverage: 47.82% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #153      +/-   ##
==========================================
- Coverage   59.00%   58.67%   -0.34%
==========================================
  Files          42       44       +2
  Lines        2520     2582      +62
==========================================
+ Hits         1487     1515      +28
- Misses        855      888      +33
- Partials      178      179       +1

Flag
Coverage Δ

unittests
58.67% <47.82%> (-0.34%)
:arrow_down:

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

Impacted Files
Coverage Δ

cleaner/cleaner.go
0.00% <0.00%> (ø)

manager/middlewares/logger.go
0.00% <0.00%> (ø)

base/utils/logger_cloudwatch.go
30.00% <30.00%> (ø)

base/utils/config.go
78.76% <42.85%> (-4.07%)
:arrow_down:

base/api/client.go
64.81% <100.00%> (ø)

base/utils/kafka.go
77.35% <100.00%> (ø)

base/utils/logger.go
60.00% <100.00%> (ø)

cleaner/cluster.go
67.27% <100.00%> (ø)

digestwriter/digestwriter.go
17.50% <100.00%> (ø)

expsync/expsync.go
33.78% <100.00%> (ø)

... and 6 more

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

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


I am using cypress along with next.js, cypress/code-coverage and swc-plugin-coverage-instrument. But it is giving me error when running npm run dev and npx run cypress opem

Error when running npm run dev:-
warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
thread 'thread '' panicked at '' panicked at 'thread '' panicked at 'called Result::unwrap() on an Err value: LayoutError', called Result::unwrap() on an Err value: LayoutError', called Result::unwrap() on an Err value: LayoutError', /Users/ojkwon/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rkyv-0.7.42/src/impls/core/mod.rs:/Users/ojkwon/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rkyv-0.7.42/src/impls/core/mod.rs:266:67/Users/ojkwon/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rkyv-0.7.42/src/impls/core/mod.rs:266:67
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
266:67
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
thread 'thread '' panicked at '' panicked at 'failed to invoke plugin: failed to invoke plugin on 'Some("/Users/jyotiyadav/Desktop/web-dubuy-express/node_modules/next/dist/client/dev/amp-dev.js")'
Caused by:
0: failed to invoke /Users/jyotiyadav/Desktop/web-dubuy-express/node_modules/swc-plugin-coverage-instrument/target/wasm32-wasi/release/swc_plugin_coverage.wasm as js transform plugin at /Users/jyotiyadav/Desktop/web-dubuy-express/node_modules/swc-plugin-coverage-instrument/target/wasm32-wasi/release/swc_plugin_coverage.wasm
1: RuntimeError: unreachable
2: unreachablefailed to invoke plugin: failed to invoke plugin on 'Some("/Users/jyotiyadav/Desktop/web-dubuy-express/pages/_app.tsx")'
Caused by:
0: failed to invoke /Users/jyotiyadav/Desktop/web-dubuy-express/node_modules/swc-plugin-coverage-instrument/target/wasm32-wasi/release/swc_plugin_coverage.wasm as js transform plugin at /Users/jyotiyadav/Desktop/web-dubuy-express/node_modules/swc-plugin-coverage-inst', rument/target/wasm32-wasi/release/swc_plugin_coverage.wasm
1: RuntimeError: unreachable
2: unreachablethread '/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/swc-0.226.26/src/plugin.rs:', 216:14' panicked at '
failed to invoke plugin: failed to invoke plugin on 'Some("/Users/jyotiyadav/Desktop/web-dubuy-express/node_modules/next/dist/client/next-dev.js")'

Error when running npx run cypress open:-
warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
 [webpack-dev-server] Project is running at:
 [webpack-dev-server] Loopback: http://<IP_ADDRESS>:8080/
 [webpack-dev-server] Content not from webpack is served from '/Users/jyotiyadav/Desktop/web-dubuy-express/public' directory
thread 'thread '' panicked at '' panicked at 'called Result::unwrap() on an Err value: LayoutError', called Result::unwrap() on an Err value: LayoutError/Users/ojkwon/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rkyv-0.7.42/src/impls/core/mod.rs:', thread '' panicked at 'called Result::unwrap() on an Err value: LayoutError', 266:67/Users/ojkwon/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rkyv-0.7.42/src/impls/core/mod.rs:266:67/Users/ojkwon/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rkyv-0.7.42/src/impls/core/mod.rs:
266:67
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
thread '' panicked at 'failed to invoke plugin: failed to invoke plugin on 'Some("/Users/jyotiyadav/Desktop/web-dubuy-express/cypress/component/useGetOtp.cy.tsx")'
Caused by:
0: failed to invoke /Users/jyotiyadav/Desktop/web-dubuy-express/node_modules/swc-plugin-coverage-instrument/target/wasm32-wasi/release/swc_plugin_coverage.wasm as js transform plugin at /Users/jyotiyadav/Desktop/web-dubuy-express/node_modules/swc-plugin-coverage-instrument/target/wasm32-wasi/release/swc_plugin_coverage.wasm
1: RuntimeError: unreachable
2: unreachable
Stack backtrace:
0: _wasmer_vm_raise_trap
1: _wasmer_vm_raise_trap
2: _napi_register_module_v1
3: _napi_register_module_v1
4: _napi_register_module_v1
5:
6:
7:
8:
9:
10:
11:
12:
13:
14: ', /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/swc-0.226.26/src/plugin.rs:216:14
thread '' panicked at 'failed to invoke plugin: failed to invoke plugin on 'Some("/Users/jyotiyadav/Desktop/web-dubuy-express/cypress/component/useFetchArea.cy.tsx")'

Package.json file
"dependencies": {
"@dpw/ecomm-ui": "0.0.26",
"@formkit/auto-animate": "1.0.0-beta.5",
"@newrelic/next": "0.3.0",
"@tailwindcss/line-clamp": "0.4.2",
"@tanstack/react-query": "4.16.1",
"@tanstack/react-query-devtools": "4.16.1",
"@tanstack/react-table": "8.5.22",
"@types/ua-parser-js": "0.7.36",
"axios": "0.27.2",
"clsx": "1.2.1",
"embla-carousel-react": "7.0.2",
"express": "4.18.2",
"i18next": "21.8.14",
"i18next-browser-languagedetector": "6.1.4",
"next": "12.3.1",
"node-cache": "5.1.2",
"node-schedule": "2.1.0",
"react": "18.2.0",
"react-dom": "18.2.0",
"react-hook-form": "7.39.5",
"react-i18next": "11.18.1",
"tailwind-merge": "1.5.1",
"tailwindcss": "3.1.7",
"ua-parser-js": "1.0.32"
},
"devDependencies": {
"@bgotink/playwright-coverage": "0.1.3",
"@cypress/code-coverage": "^3.12.15",
"@next/bundle-analyzer": "12.2.5",
"@percy/playwright": "1.0.4",
"@playwright/test": "1.24.2",
"@types/node": "17.0.35",
"@types/react": "18.0.9",
"@types/react-dom": "18.0.5",
"autoprefixer": "10.4.7",
"cypress": "^13.6.1",
"dotenv": "^8.2.0",
"eslint": "^8.21.0",
"eslint-config-next": "^12.2.4",
"eslint-config-prettier": "^8.5.0",
"husky": "^8.0.1",
"lint-staged": "13.0.3",
"postcss": "8.4.14",
"prettier": "2.7.1",
"swc-plugin-coverage-instrument": "^0.0.20",
"tailwindcss": "3.2.7",
"typescript": "4.7.2"
},
next.config.js configuration
experimental: {
swcPlugins: [['swc-plugin-coverage-instrument', {}]]
},
reactStrictMode: true,
assetPrefix: envConfig.ASSET_URL,
@kwonoj  , and everyone , Thanks a lot in advance in resolving this

This is not a @swc/core issue, it's plugin issue.

@kwonoj  Is there any suggested way to use "swc-plugin-coverage-instrument" for instrumentaion along with cypress code coverage?


[ldd-img] autoexposure additions for supercam

Need several attributes added for the supercam autoexposure algorithm, under img:Autoexposure:
auto_exposure_lower_threshold - card 0-1, int any
Specifies the lower threshold DN value for which a specified number of pixels is permitted to exceed. The auto_exposure_lower_limit defines the number of pixels allowed to exceed this threshold.
auto_exposure_lower_limit - card 0-1, int 0-any
Specifies the maximum number of pixels that are allowed to be below the lower threshold defined by auto_exposure_lower_limit.
auto_exposure_upper_threshold - card 0-1, int any
Specifies the upper threshold DN value for which a specified number of pixels is permitted to exceed. The auto_exposure_upper_limit defines the number of pixels allowed to exceed this threshold.
auto_exposure_upper_limit - card 0-1, int 0-any
Specifies the maximum number of pixels that are allowed to be above the upper threshold defined by auto_exposure_upper_limit.
auto_exposure_roi_lines - card 0-1, int 0-any
Specifies the number of lines in the autoexposure region of interest.
auto_exposure_roi_samples - card 0-1 int 0-any
Specifies the number of samples in the autoexposure region of interest.
auto_exposure_roi_first_line - card 0-1 int 0-any
Specifies the (1-based) starting line for the autoexposure region of interest.
auto_exposure_roi_first_sample - card 0-1 int 0-any
Specifies the (1-based) starting sample for the autoexposure region of interest.

added for forthcoming IMG v<IP_ADDRESS>


why continue training after the max trial reached?

I set num_trials to be 15, training starts from trial_0 to trial_14, but when trial_14 was finished, it continue to run trial_0. This happend on two different tasks. Why it happend?

Could you provide a minimally reproducible example + log output? I'm assuming you are referring to ImagePredictor.

My task is image classification and hpo was used. This is the log:

I believe the last trial 0 is the final run, it will load the best config from trial 0-14 and perform the training with combined train/valid data

@Innixma @zhreshold  I agree that it should be clearer in the logs, and write the final trail results into .trial instate of overwriting the .trail_0

@zhreshold How autogluon calculate valid_acc at the last trial_0 when train/valid data were combined?

I believe the last trial 0 is the final run, it will load the best config from trial 0-14 and perform the training with combined train/valid data

I checked the code, it dose load the best config from trial, but dose not training with the combined train/val data

This issue has been fixed in #1282, and because of it, model quality will be greatly improved in general when HPO is enabled as prior it was re-training the best model config but running out of time, causing the model to be quite bad in many cases.


Check if logic on index.js for deploy commands and events can be moved to deploy-commands.js

Explanation
There is a file deploy-commands.js that is imported on index.js, and seems like it does the same that index on lines 15-30.
It seems like the bot is doing the job twice, loading commands twice. This task is to validate that, if that is the case, move the code that deploy commands on index.js to deploy-commands.js so we have index.js a bit more clean.
Also, create a new file deploy-events and move the logic for deploy the events to this file instead of have it on index.js
Screenshots

Checklist
This issue can be closed when the following tasks are complete:

[ ] The logic for deploy commands and events are separated in files instead of be on index
[ ] All work as before
[ ] The bot is not doing the same work twice

I think the code on deploy-commands and the code on index do the same on that part, and we could move it completly to deploy-commands file. @YoelFerreyra do you know if it is actually like I say?

I think the code on deploy-commands and the code on index do the same on that part, and we could move it completly to deploy-commands file. @YoelFerreyra do you know if it is actually like I say?

On theory it looks very similar, although both codes are necessary. I will try to unify both


how to get ledger data in enclave chaincode.

Can FPC developer get local ledger or block data?  I noticed that shim.h in this release(v1.0-rc1
) only expose interface to contact with world state  DB.
Or if it's possible to get transaction data from  shim_ctx_ptr_t ctx and just put data into world state DB?

how to get ledger data in enclave chaincode

For this purpose, the FPC shim exposes the get_state function, which ends up calling the GetState function in the Fabric shim.

Can FPC developer get local ledger or block data? I noticed that shim.h in this release(v1.0-rc1) only expose interface to contact with world state DB.

For the moment there's no notion of "local" or "block" data for FPC chaincodes. An FPC chaincode can only read/write key-value pair to/from its own namespace/world-state.

Or if it's possible to get transaction data from shim_ctx_ptr_t ctx and just put data into world state DB?

An FPC chaincode can get the cleartext transaction data, as it was sent by the client through the EvaluateTransaction (if using the FPC client sdk) or the fpc-peer chaincode invoke (if using the FPC CLI).
Inside the FPC chaincode, this can be achieved through the get_func_and_params. See an example here.


/// keep-sorted for switch statements

Clear and concise description of the problem
Hey there, I'm back with another suggestion: /// keep-sorted for switch statements. The idea comes from this file
Suggested solution
Basic
/// keep-sorted
switch (x) {
  case "b":
    doB();
    break
  case "a":
    doA();
    break;
}

// ->

/// keep-sorted
switch (x) {
  case "a":
    doA();
    break
  case "b":
    doB();
    break;
}

Complex/weird
/// keep-sorted
switch (x) {
  case "fallback":
    falling();
  case "c":
  case "b":
    common();
    break;
  case "d":
  case "a":
    aOrD();
    break;
}

// ->

/// keep-sorted
switch (x) {
  case "a": // `a` comes before `fallback`
  case "d":
    aOrD();
    break;
  case "fallback":
    falling();
  case "b":
  case "c":
    common();
    break;
}

Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I am not so sure about this. Switch is order sensetive, and this move could potentially change the logic by a lot. personally, I don't think it's a common case where you write switch with orthogonal logic while having so many cases to sort.

Maybe if the rule is limited to static identifiers and forbids falling-through cases (only aliases, like the file in the first message) it might be safe


Functorize SectionList

The previous Version doesn't had a satisfying user experience.
Previously

module UIExplorerApp = {
  include ReactRe.Component;
  type props = {components: array ExampleList.item};
  let name = "UIExplorerExampleList";

  let renderItem sectionProps => {
      <Text>(ReactRe.stringToElement (sectionProps##item: ExampleList.item).key)</Text>
  };

  let render {props} => {
      <View style=styles##listContainer>
        <SectionList
            sections=[| SectionList.section data::props.components key::"components"  ()|]
            renderItem=renderItem
           keyExtractor=(fun item _ => item.key)
        />
    </View>
    };
};

include ReactRe.CreateComponent UIExplorerApp;

Notice that the compiler cannot infer the type of item in renderItem.
First I changed that renderItem takes a record instead of a Js.t ... object since I found the sudden contact with the FFI akward and now it resembles more the usual render function.
This resulted in the problem that a pattern match is only possible if the record is defined in the same module (without explicit annotation).
To get everything working as I want, I had to pick bigger weapons.
Now

module UIExplorerApp = {
  include ReactRe.Component;
  include SectionList.Make {type item = ExampleList.item };
  type props = {components: array ExampleList.item};
  let name = "UIExplorerExampleList";
  let renderItem {item} => <Text> (ReactRe.stringToElement item.key) </Text>;
  let render {props} =>
    <View style=styles##listContainer>
      <SectionList
        sections=[|SectionList.section data::props.components key::"components" ()|]
        renderItem
        keyExtractor=(fun item _ => item.key)
      />
    </View>;
};

include ReactRe.CreateComponent UIExplorerApp;

The SectionList module is now a functor which just takes its item type as argument.
We include the resulting module to get the type definitions in the current module.
Our ReactComponent has again the SectionList module name which overwrites the SectionList from ReactNative.

Instead of include SectionList and include ReactRe,Component, Section.Make could return a ready to use Reason component. If somebody wants for example state with it, then they put the returned component in their own stateful one.

Not sure about that since if you want to have a stateful component you have another level of indirection...

Yeah, but that's good. You compose it on top of this component.

made some changes!

How is the current API used? Do you like it?

Sorry didn't see your previous comment.
I like your second proposal (the first one has again problems with pattern matching since the record types are specified elsewhere), but for example itemSeparatorComponent is an optional argument but would have to be in the "bundle".  Obviously we could that with an option, this doesn't become pretty...
To the keyExtractor thing: In JS you could specify your key in each item, but since our items could be records the JS component doesnt recognize that keys are avaiable. So I made it a required prop since I stumbled on it last night.

I tend to just go with the current solution and iterate later if we have some more feedback. Are you fine with that?

How does one use the current API? There seems to be additional nested SectionList module. Does that mean that I'd have to do the following?
<ImageSectionList.SectionList />


Connection issues the Azure Sphere MT3620 starter kit

(1)	I have recently received the MT3620 to test, but I’m with some problems when I execute this command:
azsphere tenant create --name
Error: The device is not responding. The device may be unreponsive if it is applying an Azure Sphere operating system update; please retry in a few minutes.
Error: Failed to retrieve device ID from attached device: 'Could not connect to the device; please ensure it is attached.'
(2)	Follow the items that I have already checked:

Change the USB port that the hardware is connect.
Uninstall and reinstall the SDK.
Check if I have only one TAP windows adapter and confirm that the IP Addres is <IP_ADDRESS>:
Restart the Azure Sphere Device Communication Service
Restart my computer
Check the 3 Ports COM

(3)	It was not possible to execute the following steps, because I did'nt find the folder APPDATA:
Save a copy of this file: c:\windows\serviceprofiles\localservice\appdata\local\Azure Sphere Tools\restore.json
Delete this file
Run the Services Manager (services.msc).
Restart the "Azure Sphere Device Communications Service"
(4)	Follow attached the hardware photo

@millena7, happy to help. Mind sharing the related Azure documentation so we are investigate further?

@millena7, happy to help. Mind sharing a link to the related Azure documentation so we can investigate further?

Thank you for helping.
Follow the documentation about this hardware:
https://docs.microsoft.com/en-us/azure-sphere/hardware/mt3620-product-status

Hi,
I deleted the file restore.json as recommended by Microsoft. It was in a hidden folder.
But the error still the same.

test

test

Hello @millena7 you mentioned that you are following what's described on this doc though I need to be sure that you followed all the steps as described here: Overview of set-up procedures ?
This is you installed the proper software , set up the development environment, claimed the device and just then tried to create a new tenant?
Thanks!

Hello @millena7 you mentioned that you are following what's described on this doc though I need to be sure that you followed all the steps as described here: Overview of set-up procedures ?
This is you installed the proper software , set up the development environment, claimed the device and just then tried to create a new tenant?
Thanks!

Hi!
I installed Azure SDK (Visual Studio) for Windows, set up the development environment but before claim the device, it is necessary to create a new tenant. See at picture below:

So that, it was not possible to claim.

Thanks for the details @millena7 ,
Can you check the related thread on MSDN and try the following:

If you are connected to a VPN, disconnect from the VPN and try again

Verify that the com ports all have the correct driver (troubleshooting guide should have covered that)

Verify that the "Azure Sphere Device Communication Service" service is running.  Try to restart it.

What do you get when doing "azsphere device show-attached -v" ?

Please also confirm that you are using SDK version 20.01

Thanks

António, thank you for helping.
1. If you are connected to a VPN, disconnect from the VPN and try again
I already did this test.
2. Verify that the com ports all have the correct driver (troubleshooting guide should have covered that)

3. Verify that the "Azure Sphere Device Communication Service" service is running. Try to restart it.
The service is running and I already tried to restart it.
4. What do you get when doing "azsphere device show-attached -v" ?

5. Please also confirm that you are using SDK version 20.01
The version is <IP_ADDRESS>5.

Thanks for the details @millena7 , can you also try the command "azsphere device recover -v" ?
If you continue to see the issue after trying to recover please run "azsphere get-support-data --output logs.zip" and send the logs to me on email.
Thanks!

Hi!!
Good news!

Thank you!! It's working :)

Glad that you are up and running now :). Please reach out if other help is needed. Happy coding!
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Client: Make form validations more verbose, they're almost invisible

Somehow done - there is a message telling something is wrong.


Coveralls

temporary use different coveralls token so all the data is in the right place + update travis.yml
https://coveralls.io/builds/4330304

↑ overall project coverage (python + js)

LGTM


Override org CLA if repo CLA exists

In a complex company, one scenario is that a few repos need different CLA from the org CLA. So I think it's good to override org CLA if a repo CLA exist. Any thought?

Coverage decreased (-0.5%) to 91.3% when pulling 340e7c58207158388cc0035ff6f1da89fd8566f8 on MichaelTsengLZ:miczeng/overrideOrgCLAIfRepoCLAExist into b1f41e4f9e725b654ef85e2930d2ae3faac14ac1 on cla-assistant:master.

Will add more test latter.

Coverage decreased (-0.2%) to 91.566% when pulling 7c1b986491ff46b65ffde060c7035065fde291b1 on MichaelTsengLZ:miczeng/overrideOrgCLAIfRepoCLAExist into b1f41e4f9e725b654ef85e2930d2ae3faac14ac1 on cla-assistant:master.

Coverage decreased (-0.04%) to 91.767% when pulling 141568c433b240aaad73dd247e8ae90777baac6b on MichaelTsengLZ:miczeng/overrideOrgCLAIfRepoCLAExist into b1f41e4f9e725b654ef85e2930d2ae3faac14ac1 on cla-assistant:master.

Coverage increased (+0.2%) to 91.976% when pulling b1cd5ea5127dabb1d9e6f32116e2a22b46994cc2 on MichaelTsengLZ:miczeng/overrideOrgCLAIfRepoCLAExist into b1f41e4f9e725b654ef85e2930d2ae3faac14ac1 on cla-assistant:master.

@willbar @jeffwilcox @KharitonOff @thojansen
Feel free to review this PR.

Close it to add more feature.
TODO:

Remove exclude repo list for org. Instead, enable user to add 'null' type CLA for repo if they don't want to link the repo when the corresponding org is linked.


Can't install eta on Ubuntu 17.10

I first tried downloading the etlas binary, but running etlas update gave me an error message saying I should create an issue here. Instead, I thought maybe I'd have more luck doing a full installation from source. However, after cloning, I get the following error message running install.sh.
stack will use a locally installed GHC
For more information on paths, see 'stack path' and 'stack exec env'
To use this GHC and packages outside of a project, consider using:
stack ghc, stack ghci, stack runghc, or stack exec

'--local-bin-path' will be removed in a future release.
Please use '--local-bin' instead.

Copying from /home/dcpdev/eta-dev/eta/.stack-work/install/x86_64-linux/lts-6.27/7.10.3/bin/eta to /home/dcpdev/.local/bin/eta
Copying from /home/dcpdev/eta-dev/eta/.stack-work/install/x86_64-linux/lts-6.27/7.10.3/bin/eta-build to /home/dcpdev/.local/bin/eta-build
Copying from /home/dcpdev/eta-dev/eta/.stack-work/install/x86_64-linux/lts-6.27/7.10.3/bin/eta-pkg to /home/dcpdev/.local/bin/eta-pkg
Copying from /home/dcpdev/eta-dev/eta/.stack-work/install/x86_64-linux/lts-6.27/7.10.3/bin/etlas to /home/dcpdev/.local/bin/etlas
Copying from /home/dcpdev/eta-dev/eta/.stack-work/install/x86_64-linux/lts-6.27/7.10.3/bin/example to /home/dcpdev/.local/bin/example

Copied executables to /home/dcpdev/.local/bin:
- eta
- eta-build
- eta-pkg
- etlas
- example

WARNING: Installation path /home/dcpdev/.local/bin not found on the PATH environment variable
Cleaning files in rts/build, libraries/*/dist
# etlas (for clean)
Welcome to Etlas, the awesome build tool for the Eta programming language!

We are working hard to make the best platform for pure functional programming
on the Java Virtual Machine.

Etlas will periodically send usage statistics to help us:

* Make decisions on how to evolve the language

* Build a community portal that displays the data we collect in visual form

* Build an Etlas package repository that will accurately display package popularity

* And more!

For more details, please consult our privacy policy:

        http://eta-lang.org/docs/html/privacy-policy.html

Would you like to help us make Eta the fastest growing programming language,
and help pure functional programming become mainstream? (y/n)

y
Thank you for trying out Eta.

If you face any issues, you can:

* File an issue at:
      https://github.com/typelead/eta/issues/new

* Post your question on Eta-Discuss:
      https://groups.google.com/forum/#!newtopic/eta-discuss

* Ask on the Gitter channel:
      https://gitter.im/typelead/eta

Config file path source is default config file.
Config file /home/dcpdev/.etlas/config not found.
Writing default configuration to /home/dcpdev/.etlas/config
cleaning...
# etlas (for clean)
cleaning...
# etlas (for clean)
cleaning...
# etlas (for clean)
cleaning...
Build completed in 0:04m
# eta (for uninstall)
Cleaning files in /home/dcpdev/.eta/<IP_ADDRESS>
Build completed in 0:01m
# eta (for install)
# eta-pkg (for install)
# etlas (for install)
Downloading the latest package lists from:
- hackage.haskell.org
- etlas.typelead.com
Updating binary package index.
Error when running Shake build system:
* install
user error (Development.Shake.cmd, system command failed
Command: etlas update
Exit code: 1
Stderr:
/home/dcpdev/.etlas/binaries/cdnverify.eta-lang.org/index: openFile: does not exist (No such file or directory)
)

/home/dcpdev/.etlas/binaries/cdnverify.eta-lang.org/index: openFile: does not exist (No such file or directory)

Hi @bkyrlach, it seems there is some problem with the fetching of files needed by etlas.
The installation should have installed etlas, eta and eta-pkg in /home/dcpdev/.local/bin. Please, execute etlas update -v3 to get a more verbose output and share it here.

./etlas update -v3
no user package environment file found at /home/dcpdev/.local/bin
Downloading the latest package lists from:
- hackage.haskell.org
- etlas.typelead.com
Searching for curl in path.
Found curl at /usr/bin/curl
Searching for powershell in path.
Cannot find powershell on the path
Searching for wget in path.
Found wget at /usr/bin/wget
Selected http transport implementation: curl
Updating index cache file
/home/dcpdev/.etlas/packages/hackage.haskell.org/01-index.cache ...
Searching for git in path.
Found git at /usr/bin/git
/usr/bin/git --version
etlas: Could not read index. Did you call 'checkForUpdates'?

@bkyrlach Can you try etlas update --http-transport=wget and etlas update --http-transport=plain-http and see if that helps?

$ ./etlas update --http-transport=wget
etlas: unrecognized 'update' option `--http-transport=wget'
$ ./etlas update --http-transport=http
etlas: unrecognized 'update' option `--http-transport=http'

A few things worth mentioning...

My MacBook that I have previously installed eta-lang on is no longer able to successfully update using etlas update
I'm doing this from work, and my work does have a fairly restrictive proxy
Trying to hit https://cdnverify.eta-lang.org/index gives me a 404 in the browser.

Here's the response XML I get in my browser.
<?xml version="1.0" encoding="utf-8"?><Error>ResourceNotFound<Message>The specified resource does not exist.
RequestId:2b18f264-001e-012b-1e32-c1083f000000
Time:2018-03-21T16:33:59.1522376Z</Message></Error>

@bkyrlach The link you should be trying is https://cdnverify.eta-lang.org/eta-binaries/index. So you're saying in an older version you were able to successfully download stuff behind the same restrictive proxy? The main difference from before and now is that before, the binaries were being downloaded over HTTP and recently we shifted it to HTTPS to make it more secure. By chance is this causing a problem?
@jneira is also behind a proxy on Windows and he's reporting similar problems.

In the output from etlas update, it looks like it's trying to hit the URL I posted. I am able to access the URL you provided without an issue.

Note that this binary was made using install.sh from a fresh clone of the eta repo as of yesterday. etlas --version returns the following.
./etlas --version
etlas version <IP_ADDRESS>
compiled using version <IP_ADDRESS> of the etlas-cabal library

Hmm it seems the state of your eta clone is corrupt since the current version of etlas on master should be <IP_ADDRESS>! Are you sure that you added the --recursive flag when cloning? You can also run:
git submodule sync
git submodule update --init --recursive
./cleaninstall.sh

etlas versions older than <IP_ADDRESS> can no longer perform binary installations because they have a bug where it doesn't add the eta-binaries prefix as you observed above. Have you tried downloading etlas-<IP_ADDRESS> from the main website?

I'm super confused. I did initially try using the etlas binary from the website with similar results. However, downloading a fresh copy today, I was able to install. I think we can close this issue now. Sorry for the bother.

@bkyrlach Dont worry, maybe the original error with the etlas binary was caused with a temporal problem with the servers hosting the required files. Happy hacking with eta!


@EqualsAndHashCode should also copy field annotations (similar to #1634)

@EqualsAndHashCode should copy field annotations the same way #1634 added this to builder, getter, and setter methods.
I am trying out Facebook's Infer static analyzer, and its Eradicate checker for @Nullable annotations complains about the methods generated by @EqualsAndHashCode:
[snip]/AccountInfoContainer.java:10: warning: ERADICATE_PARAMETER_NOT_NULLABLE
  `AccountInfoContainer$AccountInfo.equals(...)` needs a non-null value in parameter 1 but argument `other.getAccountInfo()` can be null. (Origin: call to getAccountInfo() at line 10).
  8.   import lombok.Data;
  9.
  10. > @Data
  11.   public class AccountInfoContainer {
  12.     @Nullable private AccountInfo accountInfo;

I don't understand what you mean. What should we mark nullable?
This sounds like the static analyser isn't inferring nearly enough and not something lombok can or should address.
Which nullable should we even generate? If it involves resolution, the answer is no, we can't do this.
parked: without feedback, close issue if after 2019-07-25.

I was thinking the annotation could be copied from a field, but it makes sense that that won't be available... if there were a way to configure an annotation to put on the other parameter to the equals method, though, that would fix this.

We could add @Nullable to all generated equals method's, but that doesn't really make sense.
Since equals is defined in java.lang.Object and its contract is well documented, static code analyzers should assume the parameter other in equals(Object) is always nullable.


[2pt] Add tests for controllers

Create request specs for the controllers.

Implemented in this PR https://github.com/Reem-lab/house-booking-back-end/pull/30


made minor changes

📝 Description
Add a brief description.
💣 Is this a breaking change (Yes/No):

[ ] Yes
[x] No

🚧 How to migrate?
Don't need.
📝 Additional Information
lol

Hi, Please review


dpaste unreliability?

PP:'ing
local uv vim.loop → Ok
;; local uv vim.loop → "no content given"
(local uv vim.loop) →
--------------------------08b6e6dad0073ff4--

Should not need to escape content when sending it as an arg as exec should be doing this for us but something is obviously incorrect, perhaps upstream parser was updated or ...?
Using (fmt "%s=%q" key content) corrects the ---<garbage> response but newline slashes are double escaped so each new line in the paste is postfixed with \.
Possible solution: copy 0x0st, write paste content to file and try attaching that instead.
(also: include warning that some providers use file to send content and secrets may remain if a post fails / provider fails to clean up after itself)

Error is related to curls -F parsing ; intentionally in various ways.
-F content=@file doesn't work ("no content given").
--data-binary does not work, --data-urlencode content@filename does work, on the commandline.