[C-Api] initial commit to add c-api @open sesame 02/05 19:53

Add nnstreamer native api and build script.
Signed-off-by: Jaeyun<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #6. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/6-202102051845300.70082402229309-721035085ffa4ea0072e5001786ef05707629ea6/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/6-202102051940210.47434401512146-3059612eaf4a6f66154afee0ebb6eaf4ce6d8eee/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/6-202102051953100.81651997566223-3059612eaf4a6f66154afee0ebb6eaf4ce6d8eee/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/6-202102052012350.0074210166931152-06aba187ec59794c48eccc13f24ca23c30a0dea4/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/6-202102052039400.92127299308777-0d6c82242d8f8f0b618a47bad8128952ad2f7de6/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/6-202102052045000.72545909881592-d752d913b3ca852d0df5455c8091be1934668b03/.

This PR requires https://github.com/nnstreamer/nnstreamer/pull/3052 to fix dependency in tizen build.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/6-202102081624500.911052942276-775f706ca897577dc53c17b0fbed36c77ee68406/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/6-202102081726290.094644069671631-06e8dde5d24fac33ff17505d5752ac6b6db5439e/.

To reviewers,
As @myungjoo requested to change package name to 'machine-learning', I added new commit to update pkg name in tizen and ubuntu.
Please review the changes again.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/6-202102081823300.50113701820374-136a7f56e0550b4b28f7d3cf50727936b3c2c1e0/.

To reviewers,
As @myungjoo requested to change package name to 'machine-learning', I added new commit to update pkg name in tizen and ubuntu.
Please review the changes again.

You still need

Let's define Tizen package name: "capi-machine-learning-inference" and let it provide capi-nnstreamer (for backward compatibility)

Provides: capi-nnstreamer = %{version}-%{release}

With the main capi package.
Then, you will need to do group-SR with nnstreamer (removing capi package from nnstreamer's spec file) to avoid "have choice for" OBS/GBS errors.

For the build error of Tizen, you will need to wait for https://dashboard.tizen.org/index.code?sr=submit/tizen/20210209.021014 and let GBS clean-up and rebuild everything.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/6-202102091732090.055906057357788-61be8b879414d2d47c93b0f03eb1e5c3c1886c31/.

Now, please update and test with tizen.org and its infra.

@jaeyun-jung You may merge it. (I'm leaving this to you so that you can read the above comment)

Merge this PR now.


First unittests

PR based on #10
Introducing unittests (and they already found an issue which is also fixed in this PR).
Run them using nose in the ./uws directory (requires requirements-dev.pip to be run):
nosetests .

please resolve conflicts with master.

implicit +1 by Jochen


always_divide_middle doesn't affect tabs

Self Checks

[x] I'm using the latest lualine.
[x] I didn't find the issue in exsisting issues or prs.

How to reproduce the problem
init.vim:
" Specify a directory for plugins
call plug#begin(stdpath('data') . '/plugged')

Plug 'nvim-lualine/lualine.nvim'

" Initialize plugin system
call plug#end()

lua << EOF
require('lualine').setup {
    options = {
        always_divide_middle = false,
        },
    tabline = {
        lualine_b = { {'tabs', separator ={left='', right=''}, max_length=99, mode=2}}

        }
    }
EOF

Expected behaviour
(taken from vanilla nvim)

Actual behaviour

Can't reproduce .
Is this the only call to lualine.setup in your config ?

yes, it is..
I run it with nvim -u init.vim and then spam :tabnew init.vim. With max_length removed, the issue still persists.
I have found out that changing width of the terminal window hides/shows some tabs.

Still, large portion of the screen remains unused.

Oh right max width, forgot about that .
Try this then
require('lualine').setup {
    options = {
        always_divide_middle = false,
        },
    tabline = {
        lualine_b = { {'tabs',
            separator ={left='', right=''},
            max_length=function() return vim.go.columns end,
            mode=2}}
        }
    }

That works, thanks!


Fix .eslintrc to allow the use of the styleMap() Lit directive

ESLint is triggering one warning and one error on the use of Lit  styleMap() directive in the file ResultsTab.js

The recomended ESLint plugins doesn't solve the issue. It might be a VS Code bug.


Group join Improvements

I thought it'd be a good idea if groupList is a list like storeList, so I created a joinGroupList page which displays only the groups you are not part of.

Codecov Report

Merging #557 into master will decrease coverage by 0.14%.
The diff coverage is 80%.

@@            Coverage Diff             @@
##           master     #557      +/-   ##
==========================================
- Coverage   98.53%   98.39%   -0.15%
==========================================
  Files         235      239       +4
  Lines        3696     3732      +36
==========================================
+ Hits         3642     3672      +30
- Misses         54       60       +6

Impacted Files
Coverage Δ

client/app/components/_groupList/groupList.spec.js
100% <ø> (ø)

.../app/components/_groupList/groupList.controller.js
100% <ø> (ø)

...t/app/components/_groupList/groupList.component.js
100% <ø> (ø)

...app/components/joinGroupList/joinGroupList.spec.js
100% <100%> (ø)

...omponents/joinGroupList/joinGroupList.component.js
100% <100%> (ø)

client/app/components/_groupList/groupList.js
100% <100%> (ø)

...mponents/joinGroupList/joinGroupList.controller.js
40% <40%> (ø)

...ient/app/components/joinGroupList/joinGroupList.js
60% <60%> (ø)

... and 3 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 73eb68d...1f087b3. Read the comment docs.

I think a group list should also be available for anon visitors, complementary to the map on the landing page.

I think a group list should also be available for anon visitors, complementary to the map on the landing page.

@tiltec  Didn't quite get it. You mean we should have a page with the list of all groups, for logged out users?

You mean we should have a page with the list of all groups, for logged out users?

Yes. Groupinfo shows public infos for all kinds of users, and as a user I expect to be able to go "back" to a group list. That's what I implemented here.

You mean we should have a page with the list of all groups, for logged out users?

Yes. Groupinfo shows public infos for all kinds of users, and as a user I expect to be able to go "back" to a group list. That's what I implemented here.

@tiltec So, should we create a seperate list of all groups, and link to it on the landing page then? Or just add a grouplist to the landing page? I just thought it was odd that it's a mixture of join group (with the url and the header "Which group would you like to join?") and a group list that just lists all groups on FS.world.

Maybe show different content, depending if the user is logged in or not? It could make sense to show the full list if the user is not logged in. For logged-in users it makes sense to filter out joined groups.

Oops, I didn't mean to merge this yet. But it's fine, we can just add the mentioned changes on top of master.
@D0nPiano I can do the changes that I proposed in my last comment if you are happy with it.

From my point of view a seperate, full list makes more sense somehow (then logged-in users could also access the complete list, and we would have the "join-group" URL for logged out users) - but I would be fine with it either way. So if you have something in mind, I'd definitely be happy with you changing it 🙂

I think that having two lists (which show similar content) could be confusing. I sometimes confuse group and store views because they look so similar.
Maybe we just mark the "already joined" groups differently, e.g. different color

Yeah, makes Sense. Different colors sound good, too 👍
And should it be able to be accessed by logged out users? And if so, should we put a button on the landing page then?

Yes logged out users should be able to access it. A simple button on the landing page could be good, maybe below the map.


assertDatabaseHas() fails on dates - due to date-serialization change

Laravel Version: 7.0
PHP Version: 7.3.11
Database Driver & Version: sqllite

Description:
After upgrading from 6.x to 7.x I found existing assertDatabaseHas() tests are failing, due to the date-serialization change https://laravel.com/docs/7.x/upgrade#date-serialization.
I would expect these tests to still pass, is my expectation correct?
Steps To Reproduce:
A simple example is to save a model to the database then assert the database has it exists. eg. for a post model;
$this->assertDatabaseHas('posts' , $post->toArray());

The new date serialisation changes don't affect how dates are stored in the database. It only affects how the are serialised when casting to an array or JSON string using the toArray() and functions alike.

if this is the case what are peoples recomendations on the best approach to test that all attributes of a model are correctly saved on the database?
on laravel 6 I have usually called toArray() eg $this->assertDatabaseHas('posts' , $post->toArray());

The above will fail since calling toArray() will serialise the date differently to the database. I would manually create the array, formatting the dates yourself. This is also safer.

Please take the approach @ryangjchandler suggested. There's nothing wrong with the assertDatabaseHas method.

Hi @driesvints I seem to be having the above issue as well but without the array serialisation. I've replicated it in a very simple test:
public function testBasicTest()
{
    Schema::create('users', function (Blueprint $table) {
        $table->id();
        $table->date('date_of_birth');
    });
    User::forceCreate(['date_of_birth' => Carbon::parse('2020-04-15')]);

    $this->assertDatabaseHas('users', ['date_of_birth' => '2020-04-15']);
}

vagrant@homestead:~/Code/tmp$ vendor/bin/phpunit
PHPUnit 8.5.3 by Sebastian Bergmann and contributors.
.F                                                                  2 / 2 (100%)
Time: 2.06 seconds, Memory: 24.00 MB
There was 1 failure:

Tests\Feature\ExampleTest::testBasicTest
Failed asserting that a row in the table [users] matches the attributes {
"date_of_birth": "2020-04-15"
}.

Found: [
{
"id": "1",
"date_of_birth": "2020-04-15 00:00:00"
}
].
/home/vagrant/Code/tmp/vendor/laravel/framework/src/Illuminate/Foundation/Testing/Concerns/InteractsWithDatabase.php:25
/home/vagrant/Code/tmp/tests/Feature/ExampleTest.php:29
FAILURES!
Tests: 2, Assertions: 2, Failures: 1.
The user model has the cast type set to date.

@jamiehd try ['date_of_birth' => Carbon::parse('2020-04-15')->toDateTimeString()]

@paul-a-byford

@paul-a-byford
Ran into this issue too, just been digging through the framework and getAttributes() seems to do the trick in replicating the old toArray().  Just replaced on my tests and all passed.
Few more keystrokes but easier than adding serializeDate to all your models or generating arrays for all DB tests

@paul-a-byford
Ran into this issue too, just been digging through the framework and getAttributes() seems to do the trick in replicating the old toArray() in database tests. Just replaced on my tests and all passed.
Few more keystrokes but easier than adding serializeDate to all your models or generating arrays for all DB tests
I don't tend to you use casts much, so not sure of any affects when using casts with this method.

@colinhall17 legend! that is ideal for my use case and as lot more straightforward than manually generating arrays. Thanks for the advice

I just found another option in the Laravel Documentation. You can add the following code to your model and it will allow you to use the toArray() method in your tests.
/**
* Prepare a date for array / JSON serialization.
*
* @param  \DateTimeInterface  $date
* @return string
*/
protected function serializeDate(DateTimeInterface $date)
{
    return $date->format('Y-m-d H:i:s');
}

Hi @jringeisen
Yes you can do that on all your models, or extend another base model, but the reason it was changed in Laravel was to bring API dates into an ISO-8601 standard, which is what we are told we should be doing to make our API's standard.
APi's utilise the toArray function, which will then serialize the date into the correct ISO standard format for when its returned.
If we override on the model we are losing the ISO standard..
So the best for me is to use getAttributes in tests and keep it so we can have correctly formatted ISO API dates.

https://github.com/laravel/framework/issues/31920#issuecomment-624274363

@paul-a-byford
Ran into this issue too, just been digging through the framework and getAttributes() seems to do the trick in replicating the old toArray() in database tests. Just replaced on my tests and all passed.
Few more keystrokes but easier than adding serializeDate to all your models or generating arrays for all DB tests
I don't tend to you use casts much, so not sure of any affects when using casts with this method.

This does the job.

Guys, if you are running Laravel 8.83 then you solve this problem by adding this funcion on Model; Notice that $data has
hint: Carbon.
protected function serializeDate(Carbon $date)
{
return $date->format('Y-m-d H:i:s');
}


Handshake timed out error  (1.4.0 - MacOS)

I've noticed that Nebula (client/non-lighthouse) is reporting handshake timed out errors constantly after initially connecting without a problem.  My clients connect to the (remote) lighthouse and then it starts timing out after about 2 minutes.  This happens constantly.  It appears to happen for 1.4.0 but not 1.3.0.
HOWEVER, when I use the nebula network the handshake stops timing out.  For a bit.  Then it times out again.

The lighthouse host is reachable - I have long running ssh tunnels connected.
I've regenerated my CAs and host keys - it's still a problem
I've changed my IP ranges and my CIDRs
I've tried using both IP addresses and domain names for my lighthouse

Still is a problem.
I've tested clients on Linux, MacOS and Android.  It consistently happens on MacOS.  I can't consistently reproduce in Android.
Lighthouse
Nebula Version: 1.4.0
Linux
MacOS (client)
Nebula Version: 1.4.0
OS: MacOS / Darwin Kernel Version 19.6.0 / Catalina 10.15.7
Android (client)
App: 0.0.41-50 (sha: 93b106f)
Nebula: 1.4.1
Linux (client)
Nebula Version: 1.3.0  -- No apparent time out
Sample error message
INFO[2021-08-02T16:40:43.742-10:00] Firewall rule added                           firewallRule="map[caName: caSha: direction:outgoing endPort:0 groups:[] host:any ip: proto:0 startPort:0]"
INFO[2021-08-02T16:40:43.742-10:00] Firewall started                              firewallHash=b6......
INFO[2021-08-02T16:40:43.745-10:00] Main HostMap created                          network=<IP_ADDRESS>/8 preferredRanges="[]"
INFO[2021-08-02T16:40:43.745-10:00] UDP hole punching enabled
INFO[2021-08-02T16:40:44.045-10:00] Nebula interface is active                    build=1.4.0 interface= network=<IP_ADDRESS>/8 udpAddr="[::]:54540"
INFO[2021-08-02T16:40:44.053-10:00] Handshake message sent                        handshake="map[stage:1 style:ix_psk0]" initiatorIndex=3371186316 udpAddrs="[a.b.c.d:6666]" vpnIp=<IP_ADDRESS>
INFO[2021-08-02T16:40:44.162-10:00] Handshake message received                    certName=mylighthouse durationNs=112420748 fingerprint=32... handshake="map[stage:2 style:ix_psk0]" initiatorIndex=3371186316 remoteIndex=3371186316 responderIndex=2307878206 sentCachedPackets=1 udpAddr="a.b.c.d:6666" vpnIp=<IP_ADDRESS>
INFO[2021-08-02T16:42:10.352-10:00] Handshake timed out                           durationNs=9207428700 handshake="map[stage:1 style:ix_psk0]" initiatorIndex=2336252132 remoteIndex=0 udpAddrs="[]" vpnIp=<IP_ADDRESS>
INFO[2021-08-02T16:42:27.753-10:00] Handshake timed out                           durationNs=9536335534 handshake="map[stage:1 style:ix_psk0]" initiatorIndex=1956456100 remoteIndex=0 udpAddrs="[]" vpnIp=<IP_ADDRESS>

I suspect the reason why this is not obvious in v.1.3.0 is that there is no timed out warning/error message.

I changed to having a lighthouse on my local network.  The timed out error still occurs.
My config.yaml for the Mac if anyone is interested is below.  It is identical to the config.yaml I'm using for my linux hosts that don't have this error.
pki:
  ca: ./ca.crt
  cert: ./host.crt
  key: ./host.key

static_host_map:
  "<IP_ADDRESS>": ["<IP_ADDRESS>:4242"]

lighthouse:
  am_lighthouse: false
  hosts:
    - "<IP_ADDRESS>"

listen:
  host: <IP_ADDRESS>
  port: 4242

punchy:
  punch: true

local_range: "<IP_ADDRESS>/24"

tun:
  disabled: false
  dev: nebula1
  drop_local_broadcast: false
  drop_multicast: false

logging:
  # level: info
  level: debug
  disable_timestamp: false
  timestamp_format: "2006-01-02T15:04:05.000Z07:00"

firewall:
  conntrack:
    tcp_timeout: 12m
    udp_timeout: 3m
    default_timeout: 10m
    max_connections: 100000

  outbound:
    - port: any
      proto: any
      host: any

  inbound:
    - port: any
      proto: icmp
      host: any

I have observed this issue on macOS after the host woke from sleep, i.e., nebula was started before sleep and survived (?) it. The issue seems to occur between macOS hosts, affects both Big Sur and Catalina. All nebula endpoints are 1.4.0.
In three terminals:

ping the lighthouse (Ubuntu focal LTS) nebula address: no issues, ping responds every second
ping a Raspberry Pi (buster) nebula address: no issues, like above
ping another macOS host's nebula address: no ping response and all pings stop

On the pinging host:

nebula is completely frozen and does not recover (at least within 5-10min)
when killed, nebula logs an entry for getting the SIGTERM, but does not actually exit
there are no log entries for initiating the handshake to the other macOS host: there is one entry for completing the handshake to the rpi and then an entry for the SIGTEM, nothing in between
use kill -9 to get it to quit

On the pinged host:

there are log entries for the incoming handshake from the pinging host and then the timeout messages

This is macos doing some probing of the broadcast ip in your nebula network, you can tell by vpnIp=<IP_ADDRESS> in the logs (given your nebula network is <IP_ADDRESS>/8. The other thing to note in the logs is that udpAddrs="[]" is saying "I have no clue who lives at this address" because your lighthouses can't answer for it, because there is no host there.
You can tell nebula to drop broadcast packets (and avoid seeing this log message) by flipping this to true https://github.com/slackhq/nebula/blob/7801b589b6a393898f89b238c39a5a8dced1df84/examples/config.yml#L154

@nbrownus I am also seeing this error, except in my case, my lighthouse most definitely knows and has a udpAddr for my remote host and my mac host.  Trouble is, my mac nebula host doesn't seem to be able to find out about the udpAddr for the other remote host.
Here is what I see on my lighthouse:
Nov 15 10:26:14 hostname nebula[1478]: time="2021-11-15T10:26:14-05:00" level=info msg="Handshake message sent" certName=pc1 fingerprint=2733666f6007c2b508475b269fdb332a240343c49ba36b3973c5ffc31f999151 handshake="map[stage:2 style:ix_psk0]" initiatorIndex=1797597823 issuer=298e1986b9d3e1f20316a9b3389ebb037dcfe465932453e2b25c4f949e3e0217 remoteIndex=0 responderIndex=1842167964 sentCachedPackets=0 udpAddr="<redacted public IP>:48415" vpnIp=<IP_ADDRESS>
And here is what my mac nebula client reports:
INFO[0868] Handshake timed out                           durationNs=9382057076 handshake="map[stage:1 style:ix_psk0]" initiatorIndex=788921434 remoteIndex=0 udpAddrs="[]" vpnIp=<IP_ADDRESS>
Now, the lighthouse log absolutely shows both of these separate hosts properly, with different, correct public udpAddrs assigned for each.  The other remote host (<IP_ADDRESS>) is correctly reporting the udpAddr for the mac client, but the mac client never seems to get or find out about a udpAddr for the remote host (udpAddrs="[]", as seen above).
Why is this?  Is this a bug in the darwin nebula client that no one has reported yet?

@turtlewax OPs error is a log line indicating nebula could not find a host at the broadcast ip for their nebula network, which is expected, as there is no host actually residing at the broadcast IP for their nebula network.
It sounds like you are having a different problem, please open a new issue.

@nbrownus Done, new issue #585.  Apologies for misreading this one to begin with.


Mod Breaks Server

The mod made my server not being able to interact with any blocks. players could not in any way interact with blocks. open doors or chests, etc.

@Volt-0001 What version did you use?

sorry for not including. 1.18.2-1.1.2

@dadoirie Based on the logs I can see that you're using fastentitytransfer-forge-1.19.x-1.1.2.jar,  which is not the newest version.
This issue was fixed for forge1.19.x in version 1.2.0
You can download the most recent versions on: CurseForge, Modrinth and Github

issue is still present - forge (43.2.3) 1.19.2 linked to the line where placed a block and block got removed next second with the error on console regarding Exception caught during firing event: Attempted to load class net/minecraft/client/Minecraft for invalid dist DEDICATED_SERVER Exception caught during firing event: Attempted to load class net/minecraft/client/Minecraft for invalid dist DEDICATED_SERVER

Now all versions for Forge 1.14-1.20 are fixed. Just need to do the same for Fabric


Feature request: upgrade hubhop events after installation

Since HubHop is now an integral part of how MobiFlight works for both MSFS2020 and X-Plane, I wonder if we should just
automatically update the latest events from hubhop when you run MobiFlight for the first time after installation / upgrade?
Because there is currently an issue where your events will get replaced with an older copy depending on the age of the snapshot that was included in a new release. And for a new installation of stable MobiFlight this means the data might be weeks or months old, depending on when the latest stable version of MF was released.
What if we just didnt ship the snapshot data at all, but rather just downloaded it on the first run?

Yes, I like the idea.

I think presets should be bundled just in case you have some problem with internet connection. It is very unlikely since you just downloaded the copy from the website.

An automated check and reminds every time that your presets are older than 7 days.

If there is no time stamp on the database, how would it know it is older than 7 days?
Would it register a time stamp every time the database is updated?

the first step would be to use the creation date of the file. it would be the day when the release was packaged and then every time you download again from hubhop.


smart_open in other languages

I have a few questions:

Is "smart open" (or something similar) available in other languages? (like maybe GO, or java)
Does the gensim library from same group use this same tool/ approach?
I see running things like streaming in data from s3 is very CPU( and IO) intensive and not much memory intensive. Would multi-threading approach a good way to parallelize reading many and huge files(logs) from s3?  Or would it be worthless?, let's say if I'm parsing the json and then writing to a relational data warehouse; since the write on the db would be single threaded?

Hi @modqhx, sorry for late answer

Probably yes, but not from us, we have only python version
gensim use smart_open almost always (especially for save/load stuff)
If you will read in multiple threads & write with one thread, probably bottleneck will be in DB writing in this case (read more per sec that you can write), in some cases it can work (with very fast databases), but in general, the idea isn't the best.


Support safety v3

See https://github.com/pyupio/safety/releases/tag/3.0.0

@dotlambda
Thanks for the information
poetry-audit-plugin has started using Safety v3 from 0.4.0


[???] operator -> from none(white default) to orange

@sainnhe I faced a problem. In C++ this "arrow" -> is an operator via documentation. So logically it should be orange.

But it will probably overload the total codeflow.

So designer verdict is really required.

When encountering this type of problem, a criterion is "Which choice can be accepted by more people".
This time you can go ahead and choose the design, I don't want to interfere your decision too much.

Okey.
Anyway I want your advice. C++ syntax looks ugly with lot of mistakes. But default dark+ theme looks ok(not ideal but less mistakes). As i read microsoft work a lot with C++ tokenization and add a lot of new tokens. I'd like to create a new brach and try to optimize C++ syntax. What do you think about it?

Of course yes! Those file types are only roughly optimized and are guaranteed to basically work, they need more precise optimization.
I think maybe we should notice this in README.

Yes, that's true, I saw a lot of people blaming themes instead of vscode for C++ syntax.

I already started to work with C++ syntax and one of the most funny things is that it looks much better without cpp scopes

@sainnhe Need your help. I'd like to compare vscode and vim themes, does vim need some plugins for C/C++ or it has a good builtin support of syntax?

The built-in syntax is VERY BAD, it cannot even highlight function name.
Vim users often need to install some additional plugins to get better syntax highlighting support, currently there are 3 types of syntax highlighting plugins:

Enhanced syntax files. The traditional way to highlight a scope in vim is writing a syntax file using vim script based on regex, this type of plugins implement a more advanced syntax files.

Semantic highlighting provided by language server, just like it is in vscode.

Tree-sitter based highlighting. Tree-sitter is a code parsing library, the newest neovim(community fork of vim) integrates tree-sitter api so users can write a tree-sitter based plugin to provide support for syntax highlighting, incremental selection, text object, code completion, etc. IMO, this is the most advanced way to highlight the code. The highlighting is very accurate, and the performance is very high. Unlike semantic highlighting provided by language server which only supports a very limited amount of programming languages, tree-sitter supports almost all of the common programming languages. Unfortunately, looks like MS has no plan to support tree-sitter based highlighting, they are focus on semantic highlighting recently.

Thanks for information!

I just rewrote C/C++ highlights https://github.com/sainnhe/gruvbox-material-vscode/commit/0a3463701b9283fd7792d6e6a650e8b5317dce83
Close this since it has been solved.


Update fread() clobber conditions

I said we may clobber when the amount read is greater than 4k, but it's greater than or equal to.

@stwish-msft : Thanks for your contribution! The author, @, has been notified to review your proposed change.

@corob-msft: Please confirm that this PR is ready for merge. Thank you.


Set local user mute on join

How to set audio and video track mute on join by default?
I tried this code but it doesnt work
    hmsSDK.join(config: config, delegate: self)
    hmsSDK.localPeer?.localAudioTrack()?.setMute(true)
    hmsSDK.localPeer?.localVideoTrack()?.setMute(true)

You need to listen to
on(track: HMSTrack, update: HMSTrackUpdate, for peer: HMSPeer)
callback where update is trackAdded and peer.isLocal == true and setMute for each track there

@gzerad Thanks. It works :)


Recent additions shows totals of all piece for a place

It would appear that we are showing the total number of records for all pieces of a place when 1 piece is added.
See the following for SFK

Listing the pieces show 2 pieces only one of which is recent.

Records online is correct but is misleading as the recent addition was only part of the total.
Perhaps the recent additions page should report what has been added and the total to be clear.
Colchester in Essex in 1891 is another example

Suggest we add an extra column

Updated Recent Additions to show single column 'New Records Online'.


add startup To HaaS 506

add startup To HaaS 506

 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.


dhparam doesn't work without 'ensure'

This doesn't create the file unless ensure is uncommented, which should be the default operation.
dhparam { '/etc/openvpn/dh2048.pem':
    size         => 2048,
    require    => Package['openvpn'],
    # ensure => 'present'
 }

It might be I'm just not using it correctly. Though the docs say this:
dhparam { '/etc/openvpn/dh2048.pem':
    size         => 2048
}

should work.

OK. Requiring ensure doesn't shock me, so would it be acceptable to update the docs?

Seems reasonable. Not sure what happens when no params are used at all.
Both cases might need to be updated.
On Aug 9, 2017 5:15 AM, "Raphaël Pinson"<EMAIL_ADDRESS>wrote:

OK. Requiring ensure doesn't shock me, so would it be acceptable to
update the docs?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/camptocamp/puppet-openssl/issues/90#issuecomment-321200381,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXmRMl4DEskdX5Q08oCDAo2Zh5LjQtWks5sWXiagaJpZM4OwxR5
.

@anthonyheckmann I think sticking the openssl:: at the beginning is what you want so it collects 'present' by default from the puppet type.  This happened to me too just before AND also while doing stuff with openvpn!
openssl::dhparam { '/etc/openvpn/dh2048.pem':
    size         => 2048
}

Agree with updating the doc to reflect this!


Expanding machine_options documentation

\cc @jkeiser @fnichol @randomcamel

An example I frequently use for convergence_options is
convergence_options: {
  :chef_version => "12.2.1"
},

@gmiranda23 Thanks!


Fix lifetime issues in tests

A number of tests were failing with the -Onone lifetime changes.
Regardless of what happens with that change, I'd like to keep our tests
passing with the stricter rules since we also test in release builds.

@swift-ci please test


[6.0] Adding some more tests for [U]Int128 in BinaryInteger+FormatStyleTests.swift and JSONEncoderTests.swift

Clone of https://github.com/apple/swift-foundation/pull/806 for 6.0
Summary:

Add some more testTypeCoercion in testTypeCoercion()
Add some more check [U]Int128 in testNumericStringRepresentation_builtinIntegersLimits()
Correct typo comment from resovled to resolved at URL.swift

Modifications:

Sources/FoundationEssentials/URL/URL.swift
Tests/FoundationEssentialsTests/Formatting/BinaryInteger+FormatStyleTests.swift
Tests/FoundationEssentialsTests/JSONEncoderTests.swift

Reviewers: @parkera , @stephentyrone

Dear @parkera , @stephentyrone ,
Could you please help me to review the PR?
Thanks,
Lam

This is not needed for 6.0.


Generated JQL doesn't work, if Jira is set to Non-English languages

Hi,
I just gave 2.3.0-rc1 a test.
When creating a new subscription using labels the German translation "Stichwörter" is used. This generates a JQL like:
Project = IT AND IssueType IN (Serviceanfrage) AND Stichwörter IN (test)
Problem is, that "labels" is translated to German in the Mattermost UI, but must not be translated when generating the JQL. The generated JQL does not work. It should be:
Project = IT AND IssueType IN (Serviceanfrage) AND labels IN (test)
Will there be a support for the components field? This gives us much more functionality than labels?
Otherwise: GREAT WORK! APPRECIATED!!!

Hi,
not sure, if this is only a UI problem. I set the Jira language to English & checked the subscriptions in MM: All fine. So maybe the generated JQL preview is language dependent but the executed JQL is not.
I already set up all our service desk channels to only display the relevant issues. This is really great!

Seems like the JQL preview should be using "system" names as opposed to the display names of the fields. It appears that the actual filtering is working correctly.

The JQL search inside of Jira does not allow you to use the system names. This is why the display names are used instead.
The JQL preview output is not used to handle Jira events. It is only there to show an approximate equivalent to what the subscription is set up to handle. There is no guarantee that the JQL will be a valid query that you can copy and paste into the Jira UI.

Will there be a support for the components field? This gives us much more functionality than labels?

The plugin currently has a lack of support for Components. It is something that we plan to include. Thank you for letting us know the value it has in your system @jprusch

Resolving, will not fix. Support for Components is(?) tracked separately.

Sehr geehrte Damen und Herren,
ich bin vom 12.12. bis 5.1. nicht im Hause und habe daher leider keinen Zugriff auf meine E-Mails.
Ihre Mail wird NICHT weitergeleitet und nach meiner Rückkehr bearbeitet.
In dringende Fällen wenden Sie sich bitte an Hr. Tarrach<EMAIL_ADDRESS>Mit freundlichen Grüßen
i.V. Jan-Peter Rusch
TEL +49 (0)571-502-145 | FAX +49 (0)571-502-66-145
<EMAIL_ADDRESS>
Schäferbarthold GmbH
Erbeweg 2-12 | 32457 Porta Westfalica | Deutschland
www.schaeferbarthold.de
Schäferbarthold GmbH: Amtsgericht Bad Oeynhausen HRB 3748
Geschäftsführer: Dr. Volker Schäferbarthold, Dr. Christian Schäferbarthold, Wolfgang Schäferbarthold


Update pyyaml for openstack plugin compatibility

@geokala Can we merge your PR? I have created similar. I'm struggling with failing UI system tests, because of the problem with this dependency. What's the problem with CircleCI here? Are we using Python 2.6?

Closed: As this PR is more than six months old without having been merged. Please reopen (and rebase if necessary) if it is still relevant.


Update dependency management

Add dependabot config
Add requirements.in file
Update pre-commit config

Hmm yeah I'm not so sure about keeping coverage in the requirements file. It's true that the tests are being called via coverage but nothing is being done with the report. Even if that's changed though, I'd lobby for installing coverage in travis (as is done with pre-commit rather than declaring it as an app dependency.

Need to add coverage to the pip install step in Travis :)


Implement TCoord rendering mode

@Meakk could you add some context to this issue ? It could then be added a the good-first-issue.

I think this one can be closed. My idea was to use a checkboard to display the texture coordinates, but we can just use the --texture-base-color and it should work.


Allow a healthcheck label for docker backendconfigs

What version of Traefik are you using (traefik version)?
[root@2ef5302562ab /]# /traefik version
Version:      v1.1.2
Codename:     camembert
Go version:   go1.7.4
Built:        2016-12-15_10:27:40AM
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml...)?
   labels:
     - "traefik.backend=search"
     - "traefik.frontend.rule=PathPrefix:/search/v3"
    - "traefik.port=10010"

What did you do?
I am trying to run traefik as a proxy with a docker backend configuration.  We are using docker version 1.11 and it does not support HEALTHCHECK.
What did you expect to see?
Traefik should be able to hit an url to check the health of the backend instead of relying  on docker's health check alone.  Please support a label like traefik.backend.health.url or something similar.

With 1.2.0, you will already be able to define health checks statically in your provider template file. Look for "healthcheck" in the docs to find out how.
Support for defining the health check path dynamically through a label is tracked by #1232. I think that's what you'd ideally like to have, so let's use your ticket to track support in Docker.

Would be ideal to have this support for docker swarm backend

+1

When this is implemented, will this be the correct usage for docker?

Fixed by #1982

@timoreimann do you agree with @ldez this is closed by #1982? You noted in #1232 that docker label support was tracked here. If you agree this is closed, does that mean docker labels will not be supported, only dockerfile healthcheck?

Sorry I did not see the note in #1232


Deprecate the HTML5Rocks Service Worker doc

http://www.html5rocks.com/en/tutorials/service-worker/introduction/ seems superseded by https://developers.google.com/web/fundamentals/primers/service-worker/
CC @jpmedley

Ping? https://developers.google.com/web/fundamentals/getting-started/push-notifications/step-03?hl=en also links to the HTMLRocks page.
CC @gauntface, @PaulKinlan

Fixed in https://github.com/html5rocks/www.html5rocks.com/pull/1445 - now we just need to get it deployed.


Analysis Description for Report Part B

CS130: Project Part B Requirements
Due: 2/12/2021, 4:00 PM PST
Analysis Description
Analyze the functional requirements of your application and capture it with UML Diagrams.
Link to Part B requirements
https://drive.google.com/file/d/1DJaRWSe_30WRYawSxNVxWtfKlgVX7YVi/view?usp=sharing

As we completed our goal for analysis description part for the Part B, I will mark this as done!


Fix cluster auditing task page

Fix some iffy Markdown. Cut down version of PR #23099
Cc @savitharaghunathan

/milestone 1.19
/assign


Question about flight_data_to_arrow_batch is_little_endian endian option

I found arrow2 introduce a  new  option named is_little_endian in  flight_data_to_arrow_batch:
https://github.com/jorgecarleitao/arrow2/blob/main/arrow-flight/src/utils.rs#L147-L152
I don't know for what reason to introduce this parameter.
Will this make the  interaction between different architecture platforms be not compatible?
Thanks

The Arrow IPC format accepts writing values in big endian: it is part of the specification. When reading from IPC, arrow2 needs to know whether the serialized data is little or big endian to correctly swap bytes if platform endianess != file endianess.
Arrow-rs does not check the endianess of the IPC file and assumes that it is little endian.

Ok, since we have flight_data_from_arrow_batch and flight_data_to_arrow_batch

flight_data_from_arrow_batch can convert RecordBatch to flight data without option is_little_endian
But in my server[intel I5 X86 ubuntu], use  flight_data_to_arrow_batchto convert flight data to record batch, I must set the is_little_endian to true, otherwise it'll throw error.

https://github.com/sundy-li/learn/blob/master/arrow-vs-arrow2/examples/appender.rs


Custom Modal, trigger after modal show ?

can show any example please
can't understand how use alteditor:add_dialog_opened
please help

solved:
    $(document).on('alteditor:add_dialog_opened', function (e) {
      console.log(e);
      console.log('fghfghfgh');
      //$.fn.dataTable.tables( {visible: true, api: true} ).columns.adjust();
    });

how i can assign for specific table?

#173
take a look at it
altEditor-extended have

addModalOpen
editModalOpen
deleteModalOpen

with these options you can assign modal for specific table

usage of above options is just like altEditor options:

onAddRow
onEditRow
onDeleteRow

i need change already showed modal form via js, successful solved already
why form contain undefined field? this is bug?


this library does not run on react native 0.70

Following error happened when running in rn 0.70
`Invariant Violation: ViewPropTypes has been removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types'.`

Was this a false issue @hk-ng, or is this a problem in RN >= 0.70?


Sync and more translation for zh_CN

I'm a bit surprise by the size of the diff. Do you know why so many things were changed? I synced the PO files with the POT yesterday.

@akien-mga I just synced with tools/translations/extract.py and make..

Weird... Is your repo up-to-date with the upstream master branch?  I always get such a large diff when run extract.py and make.
The version of gettext is 0.19.7, I use Arch Linux.

Here's the "clean" diff if I apply your patch and then sync with make: http://paste.fedoraproject.org/372991/64709682/

Note that make runs extract.py for you already. (but it shouldn't really matter here)

@akien-mga How can I get the "clean" version?

I guess you could rebase your commit away and apply my diff instead, if it looks to you like it has all the changes you made: http://paste.fedoraproject.org/372991/64709682/
BTW I notice this you might want to check:
 #: tools/editor/io_plugins/editor_texture_import_plugin.cpp
 msgid "Inserting"
-msgstr "插入中"
+msgstr ""

Otherwise, we need to investigate this huge diff bug. Apparently @bojidar-bg can reproduce it too on Arch.

@akien-mga Well... I will do that and make it clean.
Some translations are not appropriate so I removed them.

Ok we found that the issue is probably that somehow the algorithm used to parse all code files lists them in a different order depending on the system: https://github.com/godotengine/godot/blob/master/tools/translations/extract.py#L24-L33
So I'll add a matches.sort() to ensure we all have the same order (will produce a huge diff for everything, so I'll do this after I've merged your new file).

@akien-mga Thanks for your help, I have applied your patch.
And I'm glad to hear that your find the reason :)


#2489 is bloating the log

The log in one of the runs is pretty bloated with NetCDF info statements, added in (I think #2489):
[ Info: Computing diagnostics:
--
  | [ Info: - orog_inst (NetCDFWriter)
  | [ Info: - ts_1d_average (NetCDFWriter)
  | [ Info: - ta_1d_average (NetCDFWriter)
  | [ Info: - thetaa_1d_average (NetCDFWriter)
  | [ Info: - ha_1d_average (NetCDFWriter)
  | [ Info: - pfull_1d_average (NetCDFWriter)
  | [ Info: - rhoa_1d_average (NetCDFWriter)
  | [ Info: - ua_1d_average (NetCDFWriter)
  | [ Info: - va_1d_average (NetCDFWriter)
  | [ Info: - wa_1d_average (NetCDFWriter)
  | [ Info: - hfes_1d_average (NetCDFWriter)
  | [ Info: - ts_1d_max (NetCDFWriter)
  | [ Info: - ts_1d_min (NetCDFWriter)
  | [ Info: - hur_1d_average (NetCDFWriter)
  | [ Info: - hus_1d_average (NetCDFWriter)
  | [ Info: - clw_1d_average (NetCDFWriter)
  | [ Info: - cli_1d_average (NetCDFWriter)
  | [ Info: - hussfc_1d_average (NetCDFWriter)
  | [ Info: - evspsbl_1d_average (NetCDFWriter)
  | [ Info: - pr_1d_average (NetCDFWriter)
  | [ Info: - rsd_1d_average (NetCDFWriter)
  | [ Info: - rsu_1d_average (NetCDFWriter)
  | [ Info: - rld_1d_average (NetCDFWriter)
  | [ Info: - rlu_1d_average (NetCDFWriter)
  | [ Info: - rsdcs_1d_average (NetCDFWriter)
  | [ Info: - rsucs_1d_average (NetCDFWriter)
  | [ Info: - rldcs_1d_average (NetCDFWriter)
  | [ Info: - rlucs_1d_average (NetCDFWriter)
  | [ Info: Computing diagnostics:
  | [ Info: - orog_inst (NetCDFWriter)
  | [ Info: - ts_1d_average (NetCDFWriter)
  | [ Info: - ta_1d_average (NetCDFWriter)
  | [ Info: - thetaa_1d_average (NetCDFWriter)
  | [ Info: - ha_1d_average (NetCDFWriter)
  | [ Info: - pfull_1d_average (NetCDFWriter)
  | [ Info: - rhoa_1d_average (NetCDFWriter)
  | [ Info: - ua_1d_average (NetCDFWriter)
  | [ Info: - va_1d_average (NetCDFWriter)
  | [ Info: - wa_1d_average (NetCDFWriter)
  | [ Info: - hfes_1d_average (NetCDFWriter)
  | [ Info: - ts_1d_max (NetCDFWriter)
  | [ Info: - ts_1d_min (NetCDFWriter)
  | [ Info: - hur_1d_average (NetCDFWriter)
  | [ Info: - hus_1d_average (NetCDFWriter)
  | [ Info: - clw_1d_average (NetCDFWriter)
  | [ Info: - cli_1d_average (NetCDFWriter)
  | [ Info: - hussfc_1d_average (NetCDFWriter)
  | [ Info: - evspsbl_1d_average (NetCDFWriter)
  | [ Info: - pr_1d_average (NetCDFWriter)
  | [ Info: - rsd_1d_average (NetCDFWriter)
  | [ Info: - rsu_1d_average (NetCDFWriter)
  | [ Info: - rld_1d_average (NetCDFWriter)
  | [ Info: - rlu_1d_average (NetCDFWriter)
  | [ Info: - rsdcs_1d_average (NetCDFWriter)
  | [ Info: - rsucs_1d_average (NetCDFWriter)
  | [ Info: - rldcs_1d_average (NetCDFWriter)
  | [ Info: - rlucs_1d_average (NetCDFWriter)

@Sbozzolo, can you silence these if they're added one variable at a time?

The fact that the output is produced twice is a mistake (that I am fixing in https://github.com/CliMA/ClimaAtmos.jl/pull/2516). I would like to have the list of diagnostics that are registered: it helps a lot when debugging any problem related to diagnostics not produced correctly (the first question is always, was the diagnostic correctly added?). Moreover, given that the diagnostics are obtained from a combination of default ones and parsing YAML, I thought it would be useful for the user too to know what is being calculated.
I thought that adding ~ 30 lines to the log wouldn't be considered bloat, and I chose that as opposed to having everything on one line, which is ugly and harder to visually parse.
I am open to suggestions to reduce the length, but I find this list very useful.

Ah, ok, maybe that's not quite so bad. Is this logging format going to scale, though? I imagine that the log could get really full as we add more diagnostics

If you don't want to typically print it, use @debug: this can then be switched on and off via JULIA_DEBUG

If you don't want to typically print it, use @debug: this can then be switched on and off via JULIA_DEBUG

I do want to typically print it in our automated runs. This allows me to check if the diagnostic was correctly registered when someone reports something wrong with a diagnostic in one of their runs. Having to rerun the thing would defy part of the purpose.

Ah, ok, maybe that's not quite so bad. Is this logging format going to scale, though? I imagine that the log could get really full as we add more diagnostics

Yes, I thought about that, and I initially postponed the problem. However, looking at the most complex EDMF cases, it is clear that it is best to tackle this now. I will open a PR soon to reduce the number of lines by grouping the diagnostics.


Support open "current content page" in browser

This is pretty cool.
Fixes #3643

This is pretty cool.

This is really, really awesome!  Totally love this new feature!  Thank you Bjørn!
One minor detail that did get me confused though: the demo at https://twitter.com/GoHugoIO/status/879065641315119104, it Hugo not only get the web browser jumps to the current page, but it almost seems like it jumps to the current section!  (No, wait, I am just imagining things... Hoho!)

but it almost seems like it jumps to the current section! (No, wait, I am just imagining things... Hoho!)

That would be magic!
But I agree, this is a feature that I really want myself, and is golden for site-wide edits (copy-edits etc.).
Thanks for testing it! I need some Windows user to take it for a spin, but I will ask in the forum.

This feature is really nice and might have been a timer saver for @rdwatters during the rewrite of the docs ;).

Thanks for testing it! I need some Windows user to take it for a spin, but I will ask in the forum.

I tried it too and it worked perfectly. But I'm on Linux as well.

I need some Windows user to take it for a spin, but I will ask in the forum.

I could reboot into Windows 10 and do some testing there too.  Hope I can post my result within half an hour?  :-)

There is no rush with the testing, I assume it "just works" and it is some time before we release this to the public. This should work, the only gotcha would be path issues on Windows.

Preliminary result under Windows 10:

Using Notepad as the editor, it works with both Internet Explorer 11, Microsoft Edge, and Google Chrome.  Hurray!

Source changed "C:\\Users\\Anthony\\go\\src\\github.com\\gohugoio\\hugo\\docs\\content\\release-notes\\release-notes.md": WRITE
INFO 2017/06/26 15:00:11 rereading C:\Users\Anthony\go\src\github.com\gohugoio\hugo\docs\content\release-notes\release-notes.md

filename = C:\Users\Anthony\go\src\github.com\gohugoio\hugo\docs\content\release-notes\release-notes.md
GetContentPage(): rel = release-notes\release-notes.md
GetContentPage(): pos = 114

Using Vim (from Git Bash, MINGW64) as the editor: No go... for some unknown reason, it generates a WRITE event on the directory instead of the file:

Source changed "C:\\Users\\Anthony\\go\\src\\github.com\\gohugoio\\hugo\\docs\\content\\release-notes": WRITE
Source changed "C:\\Users\\Anthony\\go\\src\\github.com\\gohugoio\\hugo\\docs\\content\\release-notes\\release-notes.md": RENAME
Source changed "C:\\Users\\Anthony\\go\\src\\github.com\\gohugoio\\hugo\\docs\\content\\release-notes\\release-notes.md": CREATE
Source changed "C:\\Users\\Anthony\\go\\src\\github.com\\gohugoio\\hugo\\docs\\content\\release-notes\\release-notes.md": WRITE
INFO 2017/06/26 15:04:58 rereading C:\Users\Anthony\go\src\github.com\gohugoio\hugo\docs\content\release-notes\release-notes.md
INFO 2017/06/26 15:04:58 rereading C:\Users\Anthony\go\src\github.com\gohugoio\hugo\docs\content\release-notes\release-notes.md
INFO 2017/06/26 15:04:58 rereading C:\Users\Anthony\go\src\github.com\gohugoio\hugo\docs\content\release-notes\release-notes.md

filename = C:\Users\Anthony\go\src\github.com\gohugoio\hugo\docs\content\release-notes
GetContentPage(): rel = release-notes
GetContentPage(): pos = -1

Using Vim (from Git Bash, MINGW64) as the editor: No go... for some unknown reason, it generates a WRITE event on the directory instead of the file:

But it ALSO generates one for the file. So, I should adjust my logic to pick the first file WRITE event. I will create a new PR with a fix tomorrow. Thanks for the testing.

But it ALSO generates one for the file. So, I should adjust my logic to pick the first file WRITE event. I will create a new PR with a fix tomorrow. Thanks for the testing.

  Yes, I am looking at pickOneWritePath() now too, and was wondering about the same.  :-)  I will create a PR too as an exercise for myself, but if it turns out to be an inefficient or incorrect way of doing it, please feel free to ignore my PR (if I ever get it done, haha).
Have a good night!

) I will create a PR too as an exercise for myself

Yea, that would be better -- so you could test it yourself. I can look at it. We really should get some automatic server tests running, but that will have to wait for another day.


docs: add one WeChat Bot to readme

Thanks 🙏

Looks good 🙏  btw I'd recommend adding some screenshots / images to your readme :)

ok


[WIP] Update the driver for the Mink 2.0 API

This updates the driver for changes done in https://github.com/Behat/Mink/pull/427
Ref https://github.com/Behat/Mink/issues/415

Closing in favor of #199 as the driver does not need to change anymore for Mink 2.0


Fix for issue #28 Plots v1.37.2 breaks plotting of MVTSeries

Thank you for fixing this. I have been trying to think this through how dividing durations / MITs could be used and it mostly makes sense, but with some possible uncertainty about the proper units:
Dividing duration by duration
The simple case, which we support is with the same frequency.
10 years / 2 years = 5
The more complex (but potentially common case) could be different frequencies. Here I am a bit uncertain about the proper unit:
1 year / 1 quarter = 4 (quarters?)
The current fix doesn't support this, which I think is fine. One thing we may want to eventually add to the frequencies branch is fconvert of durations, but I don't think that is needed just yet.
Dividing an MIT with a duration.
When the frequencies are the same, this is basically converting it to an Int, so your implementation makes sense:  2022Y / 1 year = 2022. 2022Q1 / 1 quarter = 8088
For different frequencies I could see people trying something convoluted like:
2022Y1 / 1 day - 2020Y1 / 1 day = [duration in days].
Of course, the proper way to do this would be fconvert(Daily, 2022Y1)-fconvert(Daily, 2020Y1), so disallowing this also makes sense for now.
Dividing a duration by an MIT
I don't think this would make sense unless the MIT is being mistakenly treated as a duration (i.e. 2Y). Currently attempting this throws an argument error: ArgumentError: Invalid arithmetic operation with Duration{Yearly} and MIT{Yearly}, which makes sense.

Thanks Jason for the comments. I agree with you. I think the main point is that for now we're not allowing the user to mix frequencies, but we are thinking about it and planning for what that will look like some day.
For the MIT-by-Duration division, in my mind that's not a valid operation. The only thing that justifies it is if we implicitly re-interpret the MIT as a duration. We get a Duration by subtracting two MITs, so we need a reference point to subtract from the given MIT. My choice of MIT{F}(0) for the reference point is arbitrary.


🐞 Unable to type when you open a new file

Description
You are unable to write anything on the new blank file, and I am unable to proceed further. However, this doesn't have when you open an existing file
To Reproduce

go to welcome screen
Click on a new file.
Try to type and observe the cursor on the file.

Expected behavior
The cursor should move, and the document should register the keystrokes from the keyboard.
Version information
CodeEdit: 1.0 dev
macOS: 12.6.1
Xcode: 14.2
Additional context
No response

Issues fixed in 1.0(1)

is it though? https://github.com/CodeEditApp/CodeEdit/issues/897


Support spring bean as mock value

<dubbo:reference id="hystrixTestServiceC"
interface="corg.apache.dubbo.demo.HystrixTestServiceC"
mock="hystrixTestServiceCCallback" />

Codecov Report

Merging #6159 into master will decrease coverage by 0.04%.
The diff coverage is 50.00%.

@@             Coverage Diff              @@
##             master    #6159      +/-   ##
============================================
- Coverage     60.90%   60.86%   -0.05%
+ Complexity      494      493       -1
============================================
  Files           999      999
  Lines         39898    39909      +11
  Branches       5744     5747       +3
============================================
- Hits          24301    24291      -10
- Misses        12907    12925      +18
- Partials       2690     2693       +3

Impacted Files
Coverage Δ
Complexity Δ

...java/org/apache/dubbo/rpc/support/MockInvoker.java
85.12% <50.00%> (-4.88%)
0.00 <0.00> (ø)

...e/dubbo/remoting/transport/netty/NettyChannel.java
55.68% <0.00%> (-4.55%)
20.00% <0.00%> (-1.00%)

...g/apache/dubbo/rpc/protocol/rest/RestProtocol.java
68.21% <0.00%> (-3.11%)
0.00% <0.00%> (ø%)

...pache/dubbo/registry/support/AbstractRegistry.java
78.06% <0.00%> (-1.49%)
0.00% <0.00%> (ø%)

...g/apache/dubbo/registry/consul/ConsulRegistry.java
62.11% <0.00%> (-0.63%)
30.00% <0.00%> (ø%)

.../apache/dubbo/config/bootstrap/DubboBootstrap.java
52.74% <0.00%> (-0.19%)
0.00% <0.00%> (ø%)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cb2f6af...30acb9a. Read the comment docs.


Decide what to do with OAS schema properties

I want to propose to decide what to do with OpenAPI Schema properties which users are using in our schema.
This thread begun here - https://github.com/asyncapi/spec/issues/1031
In JAsyncAPI I have implemented strict validation, that's why I have enfaced with multiple questions from users.
For example, last questions, from folks at Specmatic:

https://github.com/asyncapi/jasyncapi/issues/163
https://github.com/asyncapi/jasyncapi/issues/164

This is strange situation for me, when de jure, strict specification implementation must interpret them as specification error, but de facto, users can use them
Let's decide what to do and how to sync validation process in different tools
@fmvilas @derberg @dalelane @smoya @char0n @GreenRover
upd:
task for new validation process: https://github.com/asyncapi/spec/issues/957

@Pakisan if they're using OpenAPI Schemas, they should specify so in the schemaFormat field, i.e., it should be application/vnd.oai.openapi;version=3.0.0.
Example with v3:
asyncapi: 3.0.0
info:
  title: Account Service
  version: 1.0.0
  description: This service is in charge of processing user signups
channels:
  userSignedup:
    address: user/signedup
    messages:
      UserSignedUp:
        $ref: '#/components/messages/UserSignedUp'
operations:
  sendUserSignedup:
    action: send
    channel:
      $ref: '#/channels/userSignedup'
    messages:
      - $ref: '#/channels/userSignedup/messages/UserSignedUp'
components:
  messages:
    UserSignedUp:
      payload:
        schemaFormat: application/vnd.oai.openapi;version=3.0.0
        schema:
          type: object
          properties:
            displayName:
              type: string
              description: Name of the user
            email:
              type: string
              format: email
              description: Email of the user

This is the schema parser in charge of interpreting it for the JS/TS parser: https://github.com/asyncapi/openapi-schema-parser.

@Pakisan if they're using OpenAPI Schemas, they should specify so in the schemaFormat field, i.e., it should be application/vnd.oai.openapi;version=3.0.0.
Example with v3:
asyncapi: 3.0.0
info:
  title: Account Service
  version: 1.0.0
  description: This service is in charge of processing user signups
channels:
  userSignedup:
    address: user/signedup
    messages:
      UserSignedUp:
        $ref: '#/components/messages/UserSignedUp'
operations:
  sendUserSignedup:
    action: send
    channel:
      $ref: '#/channels/userSignedup'
    messages:
      - $ref: '#/channels/userSignedup/messages/UserSignedUp'
components:
  messages:
    UserSignedUp:
      payload:
        schemaFormat: application/vnd.oai.openapi;version=3.0.0
        schema:
          type: object
          properties:
            displayName:
              type: string
              description: Name of the user
            email:
              type: string
              format: email
              description: Email of the user

This is the schema parser in charge of interpreting it for the JS/TS parser: https://github.com/asyncapi/openapi-schema-parser.

Hi, Fran. Thanks for schemaFormat example.
Where I can find all supported formats?
I agree with you, that in case of provided schemaFormat we can interpret is as Avro, OAS, ...
But I want to clarify validation behavior when users didn't provide any schemaFormat so it must be interpreted as AAS schema
asyncapi: 3.0.0
info:
  title: Account Service
  version: 1.0.0
  description: This service is in charge of processing user signups
channels:
  userSignedup:
    address: user/signedup
    messages:
      UserSignedUp:
        $ref: '#/components/messages/UserSignedUp'
operations:
  sendUserSignedup:
    action: send
    channel:
      $ref: '#/channels/userSignedup'
    messages:
      - $ref: '#/channels/userSignedup/messages/UserSignedUp'
components:
  messages:
    UserSignedUp:
      payload:
        schema:
          type: object
          properties:
            displayName:
              type: string
              description: Name of the user
              example: Pavel
              nullable: true
              readOnly: true
              examples:
                - Pavel
                - Peter
            email:
              type: string
              format: email
              description: Email of the user
              example<EMAIL_ADDRESS>              readOnly: true
              examples:
                -<EMAIL_ADDRESS>

But I want to clarify validation behavior when users didn't provide any schemaFormat so it must be interpreted as AAS schema

The behaviour should be to fail. The examples you mentioned are not valid AsyncAPI schemas. Just because they're similar it doesn't mean we have to behave differently.


Find index for a relevant saccade to look at the peripheral target from the center

This finds a index about a relevant saccade to look at the peripheral target among multiple saccades in a given trial. If there are multiple relevant saccades, it finds the saccade with the largest eye movement distance.

the logic seems good, but i think it can be simplified significantly to make it easier to read and run faster. see my suggestion


About network

I notice that almost all the semi-supervised segmentation models used resnet-deeplab as the network, any special to be considered? will it be better by using transformer network?

Hi, this is because resnet-deeplab is a classic algorithm.
I think a good semi-supervised algorithm could generalize to different network structures well.


Generate image checksums during build time

This is a follow up of https://github.com/rancher-sandbox/cOS-toolkit/issues/107 which was a spike.
Looks like its possible to create such utility and would be helpful to implement as its needed as part of https://github.com/rancher-sandbox/cOS-toolkit/issues/95
See https://github.com/vbatts/go-mtree for a working utility that already does this.
Requirements

[x] Accepts a dir and generates a checksum
[x] Accepts a dir and a checksum file and compares it
[x] plugin for luet based of luet-mtree https://github.com/Itxaka/luet-mtree
[x] generate the checksums during the build process https://github.com/rancher-sandbox/cOS-toolkit/pull/166
[ ] Push the checksums (along the image? as part of metadata?)

Up to my understanding our mandatory need and primary use case is to validate the installation and upgrade process, meaning we should be capable to compare the installed/upgraded filesystem with the downloaded image. For that I assume we will use this tool inside the upgrade and installation scripts. So I don't see the need of comparing two files for now, I would drop that as a requirement for now.

Yes, to add on top, we should just be able to hash what gets into this phase: https://github.com/rancher-sandbox/cOS-toolkit/blob/master/packages/installer/upgrade.sh#L116 which is basically unpacking the content from a docker image.
What we need to be able to get from the CLI is the hash of the content of what's in /tmp/upgrade in our case, after we have pulled the content, or even better by reading the img file after it gets umounted, so we can verify directly the generated image files also outside the upgrade context (e.g. a user could verify an image that is being used currently at boot, by comparing the hashes with the one provided by us)

luet plugin has been created at https://github.com/Itxaka/luet-mtree which currently allow to generate and check a file/dir against a mtree-based checksum file

@Itxaka I think we can close this one, right? https://github.com/rancher-sandbox/cOS-toolkit/pull/179 was merged, I'm opening a new issue to track the CLI work separately

Indeed! Now that we push it along the metadata, this part is finished!


Allow optional irf implementation for simulations

Maybe we should implement an optional variant for the item response function,
irf(::ItemResponseModel, theta, beta)

This would allow us to create a single framework for simulations.
We probably need some kind of trait to check whether this is implemented or not.

This is now obsolete. Calling functions with parameters instead of item indices is now implemented in ItemResponseFunctions.jl


[Feature] ViewButton

We have EditButton component, can we create a ViewButton component? If you are ok with this, I can work on it, thanks.

Do you mean <ShowButton>? It's already there.

Yes, sorry!


Example for how to configure CookieAuthentication in ASP.NET Core 2 Preview

Is there an example somewhere on how to configure Cookie Authenticaiton in the preview?
The old configuration mentioned in the documentation  now breaks, and so is no longer valid.
Any examples on how to configure Cookie authentication would be useful. In the meantime app's broken which is kind of sad given that this was working and now fails with a hard compiler error.

https://github.com/aspnet/Security/blob/bdd4d219962201907393734d9fab2903921fec9d/samples/CookieSample/Startup.cs#L16-L21

The gist of the changes are that things were moved from middleware into services.

How would you do something like this?
https://github.com/damienbod/AspNetCoreMvcAngular/blob/master/AspNetCoreMvcAngular/Startup.cs#L91-L112

https://github.com/aspnet/Security/blob/bdd4d219962201907393734d9fab2903921fec9d/samples/OpenIdConnectSample/Startup.cs

Hi @Tratcher
The new way is more complicated than before. Why was this changed?
Greetings Damien

The startup changes for any individual auth aren't really that different except that they have moved to ConfigureServices as opposed to Configuring a middleware.  You can see https://github.com/aspnet/Announcements/issues/232 for more details.
The main things that are different in startup is moving the concept of AutomaticChallenge/Authenticate out of each options into a shared place eliminating the possibility of multiple auth setting these flags, and having only a single UseAuthentication() middleware.

Thanks for some of the links but neither of those show how to set specific values for the cookie authentication.
My old code used this to specify custom login path:
    app.UseCookieAuthentication(new CookieAuthenticationOptions()
            {
                AutomaticAuthenticate = true,
                AutomaticChallenge = false,
                LoginPath = "/api/login"
            });

I can't find the place (or whatever replaced them) where I can apply these options.

        public void ConfigureServices(IServiceCollection services)
        {
            services.AddCookieAuthentication(o => o.LoginPath = "/api/login");
        }

        public void Configure(IApplicationBuilder app)
        {
            app.UseAuthentication();
        }

Aaargh - yes thank you. This is a case where Visual Studio Intellisense didn't show the AddCookieAuthenitcation() and tried working off AddAuthentication() only which didn't have the right settings to set.
This gets me a little further:
public void ConfigureServices(IServiceCollection services)
{
	services.AddCookieAuthentication(o =>
    {
		o.LoginPath = "/api/login";
		o.LogoutPath = "/api/logout";
    });
}

and app.UseAuthentication() in Configure().
However this gets me:

No authentication handler is configured to handle the scheme: Cookies

So there's something else missing here.
+++ Rick ---

Stack trace? The calling methods also changed. See the announcement.

The announcement doesn't give much info. I'm not sure what I can't figure out what this is trying to say:
   context.Authenticate|Challenge|SignInAsync("scheme"); // Calls 2.0 auth stack

Here's what I have in my existing auth method that works in 1.1:
        [AllowAnonymous]
        [HttpPost]
        [Route("api/login")]
        public async Task<bool> Login([FromBody]  User loginUser)
        {
            var user = await accountRepo.AuthenticateAndLoadUser(loginUser.Username, loginUser.Password);
            if (user == null)
                throw new ApiException("Invalid Login Credentials", 401);

            var identity = new ClaimsIdentity(CookieAuthenticationDefaults.AuthenticationScheme);
            identity.AddClaim(new Claim(ClaimTypes.Name, user.Username))    ;

            if (user.Fullname == null)
                user.Fullname = string.Empty;
            identity.AddClaim(new Claim("FullName", user.Fullname));

			//context.Authenticate | Challenge | SignInAsync("scheme"); // Calls 2.0 auth stack

			await HttpContext.Authentication.SignInAsync(CookieAuthenticationDefaults.AuthenticationScheme,
                new ClaimsPrincipal(identity));

            return true;
        }

Stacktrace:
Application started. Press Ctrl+C to shut down.
fail: AlbumViewerAspNetCore.ApiExceptionFilter[0]
      No authentication handler is configured to handle the scheme: Cookies
System.InvalidOperationException: No authentication handler is configured to handle the scheme: Cookies
   at Microsoft.AspNetCore.Http.Authentication.Internal.DefaultAuthenticationManager.<SignInAsync>d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at AlbumViewerAspNetCore.AccountController.<Login>d__2.MoveNext() in C:\projects2010\AlbumViewerVNext\src\AlbumViewerNetCore\Controllers\AccountController.cs:line 43
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.Internal.ObjectMethodExecutor.<CastToObject>d__38`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeActionMethodAsync>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextActionFilterAsync>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextExceptionFilterAsync>d__15.MoveNext()

I also tried this in addition to AddCookieAuthentication() in ConfigureServices():
services.AddAuthentication(o =>
			{
				o.DefaultAuthenticateScheme = CookieAuthenticationDefaults.AuthenticationScheme;
			});

but no luck. Something is still missing?

HttpContext.Authentication.SignInAsync is the old  auth 1.0 stack. Drop the authentication. We will depreciate the old apis in preview2 so it will be more obvious in the future.

I'm not sure what you're saying? What do you mean drop the authentication? I have an API that needs to create a signin cookie.
Are you saying this isn't implemented in this preview?

The authentication system of ASP.NET CORE is nightmarishly over-engineered.
What in the world happened to the simplicity override the Authorize method that used to exist in ASP.NET MVC?
I get that Microsoft is trying to do everything possible to eliminate people from rolling their own auth by making it pretty much impossible to roll your own, but that one size fits all is a very naive end product. Especially when Identity and the schema/models it uses is almost wholly wrong IMO.
I feel like we've taken multiple steps backwards. Literally since 2010 one of the chores of .NET has always been rip out all of the membership and identity stuff and roll your own on top of FormsAuthentication to ensure properly cookie protection. Now Identity is even worse than the Membership stuff.
Crazy and very sad at the same time.

@RickStrahl I mean you need to call httpContext.SignInAsync instead to call the 2.0 authentication stack.

LOL! Sure enough that's it!
Miscommunication. So this now works:
		[AllowAnonymous]
		[HttpPost]
		[Route("api/login")]
		public async Task<bool> Login([FromBody]  User loginUser)
		{
			var user = await accountRepo.AuthenticateAndLoadUser(loginUser.Username, loginUser.Password);
			if (user == null)
				throw new ApiException("Invalid Login Credentials", 401);

			var identity = new ClaimsIdentity(CookieAuthenticationDefaults.AuthenticationScheme);
			identity.AddClaim(new Claim(ClaimTypes.Name, user.Username))    ;

			if (user.Fullname == null)
				user.Fullname = string.Empty;
			identity.AddClaim(new Claim("FullName", user.Fullname));

			//context.Authenticate | Challenge | SignInAsync("scheme"); // Calls 2.0 auth stack

			await HttpContext.SignInAsync(CookieAuthenticationDefaults.AuthenticationScheme,
				new ClaimsPrincipal(identity));

			return true;
		}

I'll write that up tonight for my own sanity.
Thank you.

@dotnetchris It doesn't have to be all difficult. The code I use here is an example of a very simple auth implementation that's no more complicated than Forms Auth in classic ASP.NET. You still need the config stuff, but the new config that's mentioned here is actually less than 10 lines of code, so not exactly difficult.
I do agree if you go full bore with the entire identity system then things are  a lot more complicated. But if you just need to do the auth and let a backend application deal with customer/user mapping (as is usually the case anyway), it's not that difficult to make that happen.

hoping someone can help me as I have had a similar issue and i am stuck with using this code  described in this thread here and getting this error
No IAuthenticationSignInHandler is configured to handle sign in for the scheme: Cookies
any ideas?

@dotnetchris completely agree with you after battling this new stuff for an entire week in an attempt to get something running that was trivial in forms auth.

AddCookieAuthentication() doesn't seem to work for me. I thought i added the correct packages. any thoughts? gettting:
InvalidOperationException: No IAuthenticationSignInHandler is configured to handle sign in for the scheme: Cookies
with following code:
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddAuthorization(o =>
        {
            o.AddPolicy("Users", p => p.RequireClaim("Users"));
            o.AddPolicy("SuperUsers", p => p.RequireClaim("SuperUsers"));
            o.AddPolicy("PlatformUsers", p => p.RequireClaim("PlatformUsers"));
        });

        services.AddAuthentication(options =>
        {
            options.DefaultSignInScheme = CookieAuthenticationDefaults.AuthenticationScheme;
            options.DefaultAuthenticateScheme = CookieAuthenticationDefaults.AuthenticationScheme;
            options.DefaultChallengeScheme = CookieAuthenticationDefaults.AuthenticationScheme;
            options.DefaultScheme = CookieAuthenticationDefaults.AuthenticationScheme;
        }).AddCookie("Cookieauth", options =>
        {
            options.LoginPath = new PathString("/login");
            options.AccessDeniedPath = new PathString("/error?unauth");
        });

        services.AddMvc();
    }

Your scheme names don't match. That should be
        services.AddAuthentication("Cookieauth")
        .AddCookie("Cookieauth", options =>
        {
            options.LoginPath = new PathString("/login");
            options.AccessDeniedPath = new PathString("/error?unauth");
        });

@Tratcher @HaoK can we list out the all registered schemes in the exception message?

It's possible, and may help people that keep mismatching their scheme names. https://github.com/aspnet/Security/issues/1502

Hi
I know this topic is closed but I still have question where I can't find the answer for.
in core 1.1 I can do
app.UseCookieAuthentication(_cookieOptions);
            app.UseJwtBearerAuthentication(new JwtBearerOptions()
            {
                Audience = ...,
                ClaimsIssuer = ...,
                AutomaticAuthenticate = true,
                RequireHttpsMetadata = !env.IsDevelopment(),
                TokenValidationParameters = new TokenValidationParameters
                {
                    ValidateIssuer = true,
                    ValidIssuer = ...,
                    ValidateAudience= true,
                    ValidAudience = ...,
                    RequireExpirationTime= false,
                    ValidateIssuerSigningKey = true,
                    IssuerSigningKey = new SymmetricSecurityKey(Encoding.ASCII.GetBytes(...))
                }
            });

when i create the cookie and de jwt token with the same claims, i can get the claims in a middelware from (httpContext.User.Identity as ClaimsIdentity).Claims
in core 2.0
I do this
services.AddAuthentication(options =>
            {
                options.DefaultAuthenticateScheme = <<AUTHENTICATIONSCHEME>>;
                options.DefaultScheme = JwtBearerDefaults.AuthenticationScheme;
            }).AddCookie(<<AUTHENTICATIONSCHEME>>,options =>
            {
                options.LoginPath = new PathString("/Account/login");
                options.AccessDeniedPath = new PathString("/Account/login");
                options.LogoutPath = new PathString("/Account/Logoff");
            })
            .AddJwtBearer(JwtBearerDefaults.AuthenticationScheme,options =>
            {
                options.Audience = ...;
                options.ClaimsIssuer = ...;
                options.RequireHttpsMetadata = !_hostingEnvironment.IsDevelopment();
                options.TokenValidationParameters = new TokenValidationParameters
                {
                    ValidateIssuer = true,
                    ValidIssuer = ...,
                    ValidateAudience = true,
                    ValidAudience = ..,
                    RequireExpirationTime = false,
                    ValidateIssuerSigningKey = true,
                    IssuerSigningKey = new SymmetricSecurityKey(Encoding.ASCII.GetBytes(...))
                };
            });

in the middleware I can read the claims from the cookie but nor for the jwt token
the request I'm using is adding in the header Key:Authorization, value: bearer <>
can someone explain me why this was working in 1.1 and not in 2.0
Thanks


Closes #270: Shake phone to go back to scan mode

Description
Just shake the phone and you are ready to scan the products
Related issues and discussion
#270

@teolemon  I will fix the conflicts once "opff" is completely fixed otherwise travis will not pass.

Does this work from anywhere within the app?

@Karljoones Yes , it works in all activities .

Fantastic, can you have a quick look at the conflicts and then we can merge?

Hey @PrajwalM2212,
Something went wrong with the build.
TravisCI finished with status errored, which means the build failed because something unrelated to the tests, like a problem a dependency or the build process itself.

Hey @PrajwalM2212,
Your changes look good to me!

Hey @PrajwalM2212,
Something went wrong with the build.
TravisCI finished with status errored, which means the build failed because something unrelated to the tests, like a problem a dependency or the build process itself.

@Karljoones Conflicts resolved .

Hey @PrajwalM2212,
Your changes look good to me!

@Karljoones good to merge ?

Merged, thanks @PrajwalM2212


Add option to get train and extra as one dataset

All state of the art networks train on both train and extra data together. I added this option.

Thanks for the PR.
While I think that the PR is ok as is, I'd like to point out that this functionality could be implemented by using a concatdataset from tnt. I think it's generic enough so that it could be merged into master.
Let me check what the others think.
In any case, I noticed that you also subtracted one from the labels (making it zero-based), and this change should be kept.

The failing checks are related to lint which has some error about flake8 not related to my pull request.
Thanks for considering the pull request and informing me about the concatdataset option.  I still think the pull request is relevant because most do not see the "extra" dataset from svhn as an independent dataset but instead as something that should be optionally included with the train dataset.  As such it would be nice to have it as option from the start.
I ran into errors in pytorch with 1 based indexing for different loss functions so I added in this fix as well.  Let me know if you think there are any changes that I should make before the pull request is accepted.


Added support for the typst language

Good evening,
I have added support for the Typst language, a modern alternative to LaTeX.
The implementation is tested and functional, with images displaying correctly.

Thank you for your time and for maintaining such a fantastic plugin!
Best regards,
Etienne

This is great, thank you!


Strange spike and box interactions

While you could see vibrations sometimes when throwing boxes, especially onto spikes, in level 5 if you throw the wooden box in this position

the box will slowly rise on the top of the spikes
Specifications

Version: alpha 3
Browser: Firefox 84.0.1 64-bit
Operating System: Win 10 64-bit

Phaser has this weird thing where if you want a character to die when they step on a tile, the tile itself can't be collidable (you can just walk right through it), which makes things x100 harder especially when you dont want to kill everything that steps on a spike, like a box.
I've been getting around this by making the box "float", which has the side-effect of bouncing when its at the top. :(
This is the issue of #11 aswell

just a little finding from now, boxes are pushed in the direction the spikes are facing and also downwards and in the case of non upwards facing spikes boxes can end up phasing through the spikes completely

Fixed in v6 Alpha


Allowance report

Extract allowance page from Progress summary, and make it as a stand alone report
Add it to JCA portal under Project Control
Report Id: pp-allowance

@JoneUE is this already verified?

@ken-mellem Report is ready, just need to be pushed to prod

@MagnusGjosund @Noggling Jone tells me this can be put into PROD now.
See https://github.com/equinor/lighthouse-client/pull/1354

The report is out in prod. PBI need to publish it in reports admin. @JoneUE follows this up.
Should i close the issue or should we wait for @aman-riaz or @BenSvend to publish it in reports admin?


Better handling of legacy vs eip-1559 txs

The gas price related logic is a mess. We should use eip-1559 transactions everywhere if possible, but at the same time Ignition should work fine in non-London environments.

@morgansliman I know we talked about this, but is it something we still have to do?

An update: #387 has support for EIP1159, and not legacy txs.

Done in #387