Multi-tenant Razor Pages not possible?

Is this a Bug or Feature request?:
Feature
Description of the problem:
How to use RazorPages in an multi tenant szenario? I have two root folders:
The base root /Pages folder and a root folder /Tenants/* where every tenant has its own folder with its RazorPages which can override or extend the base.
I don't know how this is possible currently, beside setting the RootDirectoy to / so that the discovery process scans all folders of the project.
services.AddMvc().SetCompatibilityVersion(CompatibilityVersion.Version_2_1)
                .AddRazorPagesOptions(options => {
                    options.RootDirectory = "/";
                });

Version of Microsoft.AspNetCore.Mvc or Microsoft.AspNetCore.App or Microsoft.AspNetCore.All: 2.1.0-rc1-final

Thanks for your feature request, @seriouz.
As this is not a priority for the upcoming milestone, we're going to move this to the Backlog to consider in the future.

/cc @DamianEdwards


Update repoBaseURL to use updated remote trunk branch

The game data repo renamed its trunk branch from master to main, so the hardcorded URL needs to be updated for pulling data from it to work. This should fix issue #488.

(in a perfect world those consts would probably be configured values instead but I know there's only so many hours in the day)

Eh typically the main branch of a repo doesn't change. Adding visibility for this to the user is unnecessary.


Dead link in System.Threading.Tasks.Extensions NuGet package README

https://github.com/dotnet/maintenance-packages/blob/d0c2a5a83211e271826172a6b0510c25a52dbd53/src/System.Threading.Tasks.Extensions/src/PACKAGE.md?plain=1#L14

@dotnet/area-system-threading-tasks @stephentoub

@gewarren can we add System.Threading.Tasks.Extensions to dotnet-api-docs?

Yes, these APIs are already documented, for example, https://learn.microsoft.com/en-us/dotnet/api/system.threading.tasks.valuetask.iscompleted?view=netstandard-2.0-pp.

Okay, I can fix this by making the link point to the correct namespace, with a small message indicating that the APIs belong to the namespace.


Long running test for mixer v2 on NullVm and WebAssembly.

(This is used to request new product features, please visit https://discuss.istio.io for questions on using Istio)
Describe the feature request We need to do a long running test of mixer v2 on the NullVm and on WebAssembly to determine stability and performance of the respective systems.
Describe alternatives you've considered
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[x] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Additional context

@mandarjog we can probably consider this done? Or is there anything specific we are missing?

This is now done, and is the default for 1.5.


Maybe add a Direction setting to the replicate component for easier usage

In some cases you might want to have the same system to add Replicate on a component on both client and server; but you actually only want to replicate in one direction.
Instead of having to fiddle with the replication-target or removing the Replicate component on either client or server, maybe I can add a setting Direction to specify if the replication is done on both sides, or if one direction is ignored.

I believe this has been added with the Protocol refactor;
when you register a component in the registry, you can specify for which direction this is intended?
This is only for systems-registration. You could have a component marked as Bidirectional, where in some cases you want it from server->client and in others from client->server.
Still, I think the issue is mostly done; we can open a new one when a more concrete issues comes up.


Basic CI/CD pipeline

It would be great to create a quick CI/CD pipeline that should do a couple things

[x] Run a test suite before commits are merged into the main branch, prevent if tests do not pass
[ ] increment the version based on the commit messages

this would require using pre-commit hooks that enforce a commit message style (e.g., fix:, feat:, MAJOR:)
apply this version to the git tags

[ ] automatically produce a change log from previous version

Between pre-commit and the GitHub actions CI, I believe this is sufficient for a v0.0.1 release. We can look at CD and containerizing later when we have more time or becomes necessary.


Using this action after reattaching the head

Hello, I have question - is there a way of using this action after reattaching HEAD?
I have such example
steps:
      - name: Reattach HEAD
        uses: actions/checkout@v2
        with:
          ref: ${{ github.event.pull_request.head.ref }}

      - name: Merge main branch to PR branch
        uses: pr-mpt/actions-merge-branch@v2
        with:
          from: "origin/main"

And I get such error
Run pr-mpt/actions-merge-branch@v2
Run git config user.name "github-actions[bot]"
Run MERGE="git merge origin/main -s recursive -Xtheirs"
merge: origin/main - not something we can merge

ok... I forgot about fetch-depth

Hi! Thank you for your interest in the Action :) I think this error is because origin/main isn't available to git to merge, essentially, the error is "branch not found". I believe this is because you have removed the fetch-depth argument which means it's using the default of 1.
0 = fetch all history for all branches (which includes origin/main)
1 = fetch only the specified ref
I think the following should work:
steps:
      - name: Reattach HEAD
        uses: actions/checkout@v2
        with:
          ref: ${{ github.event.pull_request.head.ref }}

      - name: Merge main branch to PR branch
        uses: pr-mpt/actions-merge-branch@v2
        with:
          from: "origin/main"
          fetch-depth: 0

Ah! We commented at the same time. @403-html I'll improve the documentation and add some error checking so that this (very easy) mistake isn't so difficult to diagnose! Thank you for raising the issue!


Nicehash high pool rejection rate

Description
Using the latest version to run a small pool. A few people use Nicehash under a single worker, so sometimes the worker has 50 ~ 100 times hash power than a real miner.  They got high pool rejection rate (10 ~ 20%) from Nicehash's connection report.
I'm planning to set up a dedicated port for Nicehash connections. In such case, what would be the good values for parameters like:

"blockRefreshInterval": 1000,
"jobRebroadcastTimeout": 60,
"clientConnectionTimeout": 600,
"varDiff": {
"minDiff": 1,
"targetTime": 15,
"retargetTime": 30,
"variancePercent": 30
}

Any suggestions or thoughts would be appreciated.

Couple things I've noticed that seems to help/cause this is the further from your stratum the connection is, the higher the rejection rate.  So if you can setup additional stratums geolocated, it should help.  I've moved everything over to using zeromq so the blockRefreshInterval gets set to 0.  Having a port for the higher difficulty helps as well, on their tester, they fail your connection if the initial diff is less than 100.

I found this link from nicehash, I think this might be useful for you.
https://www.nicehash.com/pool-operators

@climbing-panda According to NiceHash the problem usually comes from the Difficulty, (Diff, VarDiff, MinDiff) not being set correctly. You are correct in that you will have to use a seperate port for NiceHash. I have setup a DGB-scrypt pool in a similar setup. I've used port 3333 for miners in general then a dedicated port (3334) for hash power rentals. This setup works well for DGB, you will probably have to play around with the minDiff depending on what coin you're doing. Here is my config for DGB-Scrypt:
},
"ports": {
"3333": {
"listenAddress": "<IP_ADDRESS>",
"difficulty": 1024.0,
"varDiff": {
"minDiff": 512.0,
"targetTime": 15.0,
"retargetTime": 90.0,
"variancePercent": 30.0
},
"tls": false
},
"3334": {
"listenAddress": "<IP_ADDRESS>",
"difficulty": 1000000.0,
"varDiff": {
"minDiff": 1000000.0,
"targetTime": 15.0,
"retargetTime": 90.0,
"variancePercent": 30.0
},
"tls": false
}

Mine's setup that exact same way.  For most algos, I have a normal port and a high difficulty port.

@calebcall @fathusband @seperatis
I've set up a high difficulty port that does reduce the rejection rate for NiceHash.  Thanks guys!
Now I notice the log has many "Share rejected: low difficulty share" warnings.
After reviewing the code in BitcoinJob.cs (ProcessShareInternal),  I'm thinking if it's because NiceHash 'redirects' many physical miners to the pool under the same worker,  and Miningcore thinks it's dealing with one miner only,  so Miningcore may increase difficulty based on the faster miners,  but then rejects the low-diff shares from the slower miners?

@climbing-panda the high difficulty port is going to reject "low shares", that's the point of having it.
This is why you have a normal port and a high Difficulty port.
A typical NiceHash rental has incredibly more power than say a single Antminer S9, so it needs a higher diff setting to recieve harder work from the pool. If it gets any low "easy work" it'll reject shares b/c it's been set to look for "harder work".
Yes, I believe nice hash turns all your rentals into a single stratum connection.
This is my understanding of how it works, if I've made any mistake someone feel free to jump in and correct me.
A last though: you will probably have some rejected /weird shares when miners first join as the pools VarDiff feature is trying to do its job by adjusting the difficulty based on your setting in config. After some time the variance in diff of the work it's sending to your miners will begin to stabilize. I'd be most concerned about rejected/bad shares during this "stabilized period" rather than bad share count by y itself. Also keep in mind, rejected shares are normal part of a running pool. The danger is when they get higher than they should be, or abnormal to say.

@seperatis Thanks Seperatis.
I examined the miningcore log, and found when the hash power is high, nicehash runs multiple stratum connections under the same worker.
@oliverw From my quick look into the code in BitcoinJob.cs (ProcessShareInternal),  difficulty seems to be adjusted by worker, not by stratum connection? If that's the case, miningcore may be confused by multiple stratum connections under the same worker, e.g.  after connection A is adjusted to high diff, connection B comes in with the previous diff, therefore is rejected as too low diff?

@climbing-panda No, the worker-name is purely used for statistics. Difficulty is adjusted on a per-connection basis.

@oliverw @calebcall Thanks guys!


fix #115: support for longer domain names from ICANN

Removes the limitation of 6 character to the domain, as it is not in ICANN anymore.
I still would like to know why there is the need to double escape the . in
\\.

@racer1988 SwiftValidator already supports longer domain names. Is there a specific example that is not working for you?

If you check the issue i opened
https://github.com/jpotts18/SwiftValidator/issues/115
you can see the email validator support domains names from 2 to 6 characters
However ICANN remove all limitations on domain names
 Labels must be 63 characters or less.

For example:
https://opensource.careers/
careers is 7 characters. So it does not work with swift validator, while it is valid

@racer1988  Email domain names are already able to be more than 6 characters.

@davepatterson No, you used a root domain name of 3 characters: .com
try with
<EMAIL_ADDRESS>
which is a valid email for the domain
https://opensource.careers/
There is no .com in the URL

I see what you mean. Thanks for clarifying! 👍

@davepatterson
actually I have been working on this a bit more and i noticed that the issue is that this email validator only supports latin charset
RFC says that the email is supported with this format:

(?:[a-z0-9!#$%&'+/=?^_{|}~-]+(?:\.[a-z0-9!#$%&'*+/=?^_{|}~-]+)|"(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21\x23-\x5b\x5d-\x7f]|\[\x01-\x09\x0b\x0c\x0e-\x7f])")@(?:(?:a-z0-9?.)+a-z0-9?|[(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?).){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?|[a-z0-9-][a-z0-9]:(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21-\x5a\x53-\x7f]|\[\x01-\x09\x0b\x0c\x0e-\x7f])+)])

which as you can see contains way more symbols.. like
{}~ etc
if you also read this https://en.wikipedia.org/wiki/International_email
you will see that these are valid email addresses

<EMAIL_ADDRESS><EMAIL_ADDRESS>
:O


Test stylelint-config-gds 0.2.0

What
Testing the upcoming release of stylelint-config-gds which upgrades to Stylelint 14 and uses more community rules.
Why
To keep up to date with stylelint
Visual Changes
n/a

I've cherry picked these changes into https://github.com/alphagov/govuk_publishing_components/pull/2709
Thanks @alex-ju (miss you)


Maze size adaptation

How can I run this code on a 25x25 maze with the centre as a 3x3 block

Need the solution a bit urgently

This is experminetal code, not intended for production. It is subject to large changes without warning.
In any case, the Arduino processor is not going to have enough memory to store and flod a maze bigger than 16x16 using the techniques here.

Not really. There is not enough RAM on the processor. Using the methods already there, you would need 576 bytes for the maze and 1152 bytes for the flooding data.

Ohh okay thank you.Appreciate your help
But i tried increasing the maze size to 22x22 which works perfectly. I think the RAM is just sufficient for this size of the maze.

It may well appear to work at some larger sizes but there are two potentially big problems. One is that the cost array used to create a route only holds 8 bit values. When there are more than 256 cells in the maze data, the cost values might overflow and give unpredictable results.
Anothe possible problem is that larger strucures for the maze might well fit in RAM but there will be less memory available for the function stack. This can produce vey hard to find errors where things may appear to work until some particular set of circumstances reveals an error and the robot mysteriously stops working. Code mey appear to work fine until you make some other change that just overflows the stack slightly.
All these can be overcome by re-writing the maze.h code to use less space but that would not be something I would do.

Ohh okay thank you. Appreciate your help. I'll look into it


Enhance documentation: add usage references / examples

For some of the plugins we marked usage examples as "Add reference".
This is a good entry level task for users who want to contribute.
Tagging as "good first issue".

I can take this one

@nirmo I will not assign you on multiple issues in parallel, hope you will understand 😄.
Thank you a lot, you're helping me!

Np, documentation can wait ;)


Can't run live playground

After running "npm install" i get errors when trying to run the storybook.
This is the errors I get:
ERROR in multi preview
Module not found: Error: Cannot resolve module 'webpack-hot-middleware/client' in /Users/sindre/projects/experiments/react-dates
 @ multi preview

ERROR in<EMAIL_ADDRESS>Module not found: Error: Cannot resolve module 'redux' in /Users/sindre/projects/experiments/react-dates/node_modules/@kadira/storybook/dist/client/preview
<EMAIL_ADDRESS>42:13-29

ERROR in ./src/svg/arrow-right.svg
Module build failed: ReferenceError: Unknown plugin "syntax-jsx" specified in "base" at 0, attempted to resolve relative to "/Users/sindre/projects/experiments/react-dates"
    at /Users/sindre/projects/experiments/react-dates/node_modules/babel-core/lib/transformation/file/options/option-manager.js:177:17
    at Array.map (native)
    at Function.normalisePlugins (/Users/sindre/projects/experiments/react-dates/node_modules/babel-core/lib/transformation/file/options/option-manager.js:153:20)
    at OptionManager.mergeOptions (/Users/sindre/projects/experiments/react-dates/node_modules/babel-core/lib/transformation/file/options/option-manager.js:245:36)
    at OptionManager.init (/Users/sindre/projects/experiments/react-dates/node_modules/babel-core/lib/transformation/file/options/option-manager.js:383:12)
    at File.initOptions (/Users/sindre/projects/experiments/react-dates/node_modules/babel-core/lib/transformation/file/index.js:223:65)
    at new File (/Users/sindre/projects/experiments/react-dates/node_modules/babel-core/lib/transformation/file/index.js:140:24)
    at Pipeline.transform (/Users/sindre/projects/experiments/react-dates/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
    at /Users/sindre/projects/experiments/react-dates/node_modules/react-svg-loader/lib/loader.js:71:37
 @ ./src/components/DayPicker.jsx 43:18-51

ERROR in ./src/svg/arrow-left.svg
...

ERROR in ./src/svg/chevron-up.svg
...

ERROR in ./src/svg/close.svg
...

ERROR in ./src/svg/chevron-down.svg
...

Make sure you're on npm v3+
I believe that's what fixed this for me

i had also an issue at install time
$ npm install

npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v6.2.0
npm ERR! npm  v3.8.9

npm ERR! Invalid name: "@kadira/storybook"
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /test/react-dates/npm-debug.log

That may be because you have a custom npm registry set
see https://github.com/kadirahq/react-storybook/issues/15

Actually we fixed this. This project use @kadira/storybook at 1.x.
If you upgrade this to @kadira/storybook to 2.x this issue will be gone.

If not just use NPM3

Certainly nobody anywhere should be using npm 1.x - if you're not on latest 2.x or 3.x of npm, you're going to have a bad time, and nobody should be supporting you :-)

@ljharb I meant @kadira/storybook v1.x. Not NPM :)

aha, gotcha

Hopefully this is fixed by #9.

ok, change thing, but now at npm install i got
npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "i"
npm ERR! node v6.2.0
npm ERR! npm  v3.8.9

npm ERR! Invalid name: "@kadira/react-split-pane"
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /test/react-dates/npm-debug.log

@eMerzh what's npm config get registry print out? If it's not https://registry.npmjs.org/, you might be pointing at an improperly-configured private registry.

$ npm config get registry
https://registry.npmjs.org/

hmm, not sure what's going on there then. https://www.npmjs.com/package/@kadira/react-split-pane definitely exists. Maybe rm -rf node_modules && npm install?

mmh nope :/ didn't help ... i got no node_modules yet .... it's fresh after a clone

@eMerzh and you're on the latest master as of tonight?

yes:
[10:16:05][bmaron@mbp /test]$ git clone https://github.com/airbnb/react-dates.git
Cloning into 'react-dates'...
remote: Counting objects: 203, done.
remote: Compressing objects: 100% (44/44), done.
remote: Total 203 (delta 16), reused 0 (delta 0), pack-reused 159
Receiving objects: 100% (203/203), 361.75 KiB | 0 bytes/s, done.
Resolving deltas: 100% (56/56), done.
Checking connectivity... done.
[10:16:05][bmaron@mbp /test]$ cd react-dates/
[10:16:05][bmaron@mbp /test/react-dates](master)$ npm install
(node:4703) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v6.2.0
npm ERR! npm  v3.8.9

npm ERR! Invalid name: "@kadira/storybook"
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /test/react-dates/npm-debug.log
[10:16:05][bmaron@mbp /test]$ git rev-parse HEAD
ebc0fc87069d043786d45d83b71979881d435b79

@eMerzh I can't conceive of why that doesn't work - that implies that your node and npm (both of which are very recent) can't handle scoped modules, which have been working for quite awhile now. I think I'd file an issue on npm itself for that.


Make old MR more backwards compatible & deprecate

Make old MR more backwards compatible

Remove new API that had been added
Remove new functionality that was added for summarizers and execution hints
Add back non consequential deprecated methods that were dropped

Deprecate core client Map reduce API

This is also work towards #788

I am not sure if the old MR code should be deprecated for 2.0.  It might make sense to keep it for 2.0 and hold off on releasing the MR API until 2.1.  This should give the new API time to mature.

I am not sure if the old MR code should be deprecated for 2.0. It might make sense to keep it for 2.0 and hold off on releasing the MR API until 2.1. This should give the new API time to mature.

I think that is a good idea.  IIRC @ctubbsii had some reasons for separating the MR code from core in the first place though so perhaps he can weigh in on.

I had made a first pass attempt at this also. I will try to reconcile your branch with mine, and add commits to your branch, as my review.

Sounds good.  I won't make any further changes on this branch for now.

@milleruntime I had to force-push to resolve the numerous conflicts with master. I'll continue to reconcile my branch with this one to add my commits on top of yours.

Force pushed again to resolve conflicts with master. I've been sick the last few days, but am slowly working towards wrapping up my changes on top of this PR.

Okay, I've reconciled my working branch with this one, restoring a few additional removed APIs since 1.9, and cleaning up some other stuff, including slight rewording of deprecated javadoc messages.
Tests are broken still, and there may be some opportunity to clean up deprecation warnings from the compiler. I'll work on those issues to wrap this up.


soc: neorv32: NEORV32 core updates and new drivers

Various NEORV32-related updates/fixes:

Update to support core revision 1.9.8. Note that this removes support for previous versions, as maintaining support for multiple versions seems rather impractical due to all the register location changes etc. Since this is a soft CPU core, it is assumed that users can upgrade their logic revision to match, which avoids the burden of trying to maintain support for multiple different versions.
Fixed issues with UART driver in interrupt mode.
Fixed compiled/linked code attempting to use RISC-V atomic instructions which NEORV32 doesn't yet support.
Added support for the XIRQ external interrupt controller.
Added support for watchdog timer.

Core revision updates based on a previous MR https://github.com/zephyrproject-rtos/zephyr/pull/66722 from @VolodymyrSvintozelskyi

Update to support core revision 1.9.8. Note that this removes support for previous versions, as maintaining support for multiple versions seems rather impractical due to all the register location changes etc. Since this is a soft CPU core, it is assumed that users can upgrade their logic revision to match, which avoids the burden of trying to maintain support for multiple different versions.

Think a discussion is needed around that, you are silently breaking a board for all existing users which itself is not a good thing, but for an lts release just does not sit right

Update to support core revision 1.9.8. Note that this removes support for previous versions, as maintaining support for multiple versions seems rather impractical due to all the register location changes etc. Since this is a soft CPU core, it is assumed that users can upgrade their logic revision to match, which avoids the burden of trying to maintain support for multiple different versions.

Think a discussion is needed around that, you are silently breaking a board for all existing users which itself is not a good thing, but for an lts release just does not sit right

It's not entirely clear how widely used the NEORV32 Zephyr port currently is yet in order to know whether this would cause a major issue for anyone. Some of the issues in previous versions of the core were causing some problems that were difficult to fix at the OS level - for example, the implementation-specific peripheral interrupts couldn't be cleared at the CPU core level in a consistent way between devices, meaning that the drivers ended up needing to manipulate the RISC-V CSRs in order to clear the interrupt properly. With the 1.9.8 release that is no longer needed. So I think it would be pretty difficult to support the existing core versions like 1.8.6 in general.

It looks like the failing checks at the moment seem to be some test infrastructure issues (403 errors)?

Update to support core revision 1.9.8. Note that this removes support for previous versions, as maintaining support for multiple versions seems rather impractical due to all the register location changes etc. Since this is a soft CPU core, it is assumed that users can upgrade their logic revision to match, which avoids the burden of trying to maintain support for multiple different versions.

Think a discussion is needed around that, you are silently breaking a board for all existing users which itself is not a good thing, but for an lts release just does not sit right

It's not entirely clear how widely used the NEORV32 Zephyr port currently is yet in order to know whether this would cause a major issue for anyone. Some of the issues in previous versions of the core were causing some problems that were difficult to fix at the OS level - for example, the implementation-specific peripheral interrupts couldn't be cleared at the CPU core level in a consistent way between devices, meaning that the drivers ended up needing to manipulate the RISC-V CSRs in order to clear the interrupt properly. With the 1.9.8 release that is no longer needed. So I think it would be pretty difficult to support the existing core versions like 1.8.6 in general.

It's still a board with an implementation which people might be using though, and if someone gets zephyr 3.6 and builds for neorv32 and uses it (note: no version in the board name), then it works fine, then gets zephyr 3.7 and builds for neorv32 then suddenly it doesn't work, that's not good. Other boards use board revisions properly, for example<EMAIL_ADDRESS>and<EMAIL_ADDRESS>both versions are supported.

It's still a board with an implementation which people might be using though, and if someone gets zephyr 3.6 and builds for neorv32 and uses it (note: no version in the board name), then it works fine, then gets zephyr 3.7 and builds for neorv32 then suddenly it doesn't work, that's not good. Other boards use board revisions properly, for example<EMAIL_ADDRESS>and<EMAIL_ADDRESS>both versions are supported. Maybe having a new version added and deprecating the old one if the old one has issues, but I don't think it should be removed for at least 2 zephyr releases that the new one has been added to, then it can be removed.

Not sure why the revision is not visible in the board target for the neorv32 board. The board does have a revision (I introduced that for the exact problem outlined above). Shouldn't https://github.com/zephyrproject-rtos/zephyr/blob/main/boards/others/neorv32/board.yml cause the board to have revision 1.8.6?

It's still a board with an implementation which people might be using though, and if someone gets zephyr 3.6 and builds for neorv32 and uses it (note: no version in the board name), then it works fine, then gets zephyr 3.7 and builds for neorv32 then suddenly it doesn't work, that's not good. Other boards use board revisions properly, for example<EMAIL_ADDRESS>and<EMAIL_ADDRESS>both versions are supported. Maybe having a new version added and deprecating the old one if the old one has issues, but I don't think it should be removed for at least 2 zephyr releases that the new one has been added to, then it can be removed.

Not sure why the revision is not visible in the board target for the neorv32 board. The board does have a revision (I introduced that for the exact problem outlined above). Shouldn't https://github.com/zephyrproject-rtos/zephyr/blob/main/boards/others/neorv32/board.yml cause the board to have revision 1.8.6?

Yes, but that's the default version so people will be using cmake -DBOARD=neorv32 app and that'll be it, now with these changes that will not change but suddenly it's building for a different soc version and will not build on the old one

Update to support core revision 1.9.8. Note that this removes support for previous versions, as maintaining support for multiple versions seems rather impractical due to all the register location changes etc. Since this is a soft CPU core, it is assumed that users can upgrade their logic revision to match, which avoids the burden of trying to maintain support for multiple different versions.

Think a discussion is needed around that, you are silently breaking a board for all existing users which itself is not a good thing, but for an lts release just does not sit right

It's not entirely clear how widely used the NEORV32 Zephyr port currently is yet in order to know whether this would cause a major issue for anyone. Some of the issues in previous versions of the core were causing some problems that were difficult to fix at the OS level - for example, the implementation-specific peripheral interrupts couldn't be cleared at the CPU core level in a consistent way between devices, meaning that the drivers ended up needing to manipulate the RISC-V CSRs in order to clear the interrupt properly. With the 1.9.8 release that is no longer needed. So I think it would be pretty difficult to support the existing core versions like 1.8.6 in general.

It's still a board with an implementation which people might be using though, and if someone gets zephyr 3.6 and builds for neorv32 and uses it (note: no version in the board name), then it works fine, then gets zephyr 3.7 and builds for neorv32 then suddenly it doesn't work, that's not good. Other boards use board revisions properly, for example<EMAIL_ADDRESS>and<EMAIL_ADDRESS>both versions are supported. Maybe having a new version added and deprecating the old one if the old one has issues, but I don't think it should be removed for at least 2 zephyr releases that the new one has been added to, then it can be removed.

For most of the DTS changes it would be possible to split up the files by version, though the question remains about how many versions we would eventually accumulate or need to support. It's a bit dirtier in that it's not just a difference at the board level but at the SoC level, so we would need to maintain separate .dtsi files for each version.
The bigger problem comes in with the actual code changes. In soc/neorv32/soc.h a bunch of the bits in the SYSINFO register were moved around, and in soc/neorv32/soc_irq.S some of the core interrupt handling code needs to be different between revisions. I'm not really sure how it's possible to support multiple versions there in a reasonable fashion?
I do suspect that the previous core revision was not widely used "in anger" with Zephyr due to the stability problems caused by some of the interrupt handling issues. This has been cleaned up and made a lot easier to support in current revisions of the core.

I would ask for a decision from @nashif about getting rid of old soc revisions and if there should be any time that it remains for being (deprecated) before being removed

I raised this issue under this NEORV32 discussion: https://github.com/stnolting/neorv32/discussions/172
@stnolting (main NEORV32 developer) commented "In my humble opinion, only the latest/current version should be supported. Anything else would be far too much work in the end." and "this project is under constant development. Breaking changes are not planned, but they happen from time to time, especially when we discover a severe bug. And isn't such a bug-fix ultimately a "breaking" change?"

I have pulled out the UART driver changes into https://github.com/zephyrproject-rtos/zephyr/pull/72385 as they are not directly dependent on anything else in the core updates. The WDT driver can't be extracted yet as it's dependent on some core device tree updates. If we agree on a path forward on the core updates, I can pull that out as a separate PR once the core changes go in.

This PR needs some updates according to some feedback, but it's ultimately still waiting for a decision or discussion about whether we need to continue supporting old versions of the NEORV32 core in Zephyr. NEORV32 upstream suggests that would be too big of a maintenance burden, and I would tend to agree given that they tend to make changes in register mappings etc. on a somewhat regular basis.

I haven't had much time to look at this lately, but if there are no objections to the general approach of just supporting the latest/recent version of NEORV32, then I can get this brought up to date and split up as needed..

I haven't had much time to look at this lately, but if there are no objections to the general approach of just supporting the latest/recent version of NEORV32, then I can get this brought up to date and split up as needed..

No objections from my side. That would be a welcome addition.


autodetect architecture of remote nodes

this depends on this issue here  but once that's done we need to do something like the following

[ ] update the tests to include one for arm64 based nodes (on k8s is fine)
[ ] send a remote call to detect the server types for all nodes
[ ] for each type of arch that exists export a binary (so if there are no amd64 nodes and only arm64 nodes export just the amd64 binary, if both are present then do both)
[ ] make sure each mode gets the appropriate binary for it

wrong repro


Adding lines are very slow

VSCode Version: Vsiaul Studio Code - Insiders 1.50.0
OS Version: Windows_NT x64 10.0.19041

Steps to Reproduce:

Type some lines
Using enter key to add multiple lines or backspace to remove multiple lines

video_and_cpu.zip

Does this issue occur when all extensions are disabled?:  Yes
Extension : 0
I assume Windows update affect vscode performance.

@twepo Does this slowness reproduce when closing all vs code instances and starting with code --disable-renderer-accessibility ?


Illegal memory access on Windows

One of my unit test cases on odbc starts to fail after I upgrade to the latest code base.  I compiled the code on a Windows box with Visual Studio 2013 and 2015.  Both exhibits the same behavior.
I traced the error to
prepare_temp_type &operator,(use_container<T, Indicator> const &uc)
Before rcpi_->exchange(uc); is called, rcpi_ is in a good state:
rcpi_  0x0000000000262780 {intos_={ size=0 } uses_={ size=0 } }
One step forward, in ref-counted-prepare-info.h,
template <typename T, typename Indicator>
void exchange(use_container<T, Indicator> const &uc)
 { uses_.exchange(uc); }

is also fine.
One more step forward to bind-value.h,
class use_type_vector: public std::vector<use_type_base *>
{
    template <typename T, typename Indicator>
    void exchange(use_container<T, Indicator> const &uc)
    {
#ifdef SOCI_HAVE_BOOST
        exchange_(uc, (typename boost::fusion::traits::is_sequence<T>::type *)NULL);
#else
        exchange_(uc, NULL);
#endif // SOCI_HAVE_BOOST
    }

For some reason, the use_type_vector is corrupted when it reached exchange.
Corrupted value: 0x00000000002627b8 { size=452126080238279090 }
I also captured the memory addresses:
this	0x000000000029fa48 {rcpi_=0x00000000004df640 {intos_={ size=0 } uses_={ size=0 } } }soci::details::prepare_temp_type *

rcpi_	**0x00000000004df640** {intos_={ size=0 } uses_={ size=0 } }soci::details::ref_counted_prepare_info *

this	0x000000000029fa48 {intos_={ size=0 } uses_={ size=0 } }soci::details::ref_counted_prepare_info *
          &intos_ 	0x000000000029fa90 { size=0 }
          &uses_ 	0x000000000029fab0 { size=0 }

this	**0x00000000004df640** { size=452126080669924939 }	soci::details::use_type_vector *

soci::details::ref_counted_prepare_info * shared the same memory address as soci::details::use_type_vector *?
I also tried disabling boost, didn't help.
The last version of the code that I compiled and worked fine was mater on Feb 17, 2016.

We really need to be able to reproduce it in the SOCI test suite itself, it's very hard to understand what happens here without this.

I can only compile with Visual Studio.  Any plan to fix the failed builds on AppVeyor soon?

Sorry, I don't understand this. What's the problem with compiling SOCI test suite using MSVC?
As for the problem with AppVeyor, I haven't even noticed it somehow, but I hope @msobczak can look at it as this seems due to #486.

Once it compiles, I can work on a test case and have it run on AppVeyor for everybody to see.
I tried starting from checking code out and it appears the problem has to do with regenerating project files in cmake using different settings.  I am also on boost 1_60.  It would be great if we can upgrade to 1_60.

If you can reproduce the problem in a test when running it locally, please do it and open a PR with a patch adding the (failing) test. This will be sufficient to allow others to debug it already, fixing AppVeyor build would definitely be nice but is absolutely not a prerequisite for doing this and fixing this bug.

@vadz I can't reproduce the problem after I start with a fresh copy of the code.  I ran cmake in the same directory with different commits and different settings.  That probably messed up the configuration.
I included boost in one of the runs which referenced version 1_60, and it didn't complain about not finding the fusion header.


TypeScript Mongoose Schema

Hey there, cool project. .
Saw your mongoose models, you kinda use the "javascript" style.
Tho you could rework it to this: https://typegoose.github.io/typegoose/docs/guides/quick-start-guide/
Example:
class Job {
  @prop()
  public title?: string;

  @prop()
  public position?: string;
}

class Car {
  @prop()
  public model?: string;
}

class User {
  @prop()
  public name?: string;

  @prop({ required: true })
  public age!: number; // This is a single Primitive

  @prop({ type: () => [String] })
  public preferences?: string[]; // This is a Primitive Array

  @prop()
  public mainJob?: Job; // This is a single SubDocument

  @prop({ type: () => Job })
  public jobs?: Job[]; // This is a SubDocument Array

  @prop({ ref: () => Car })
  public mainCar?: Ref<Car>; // This is a single Reference

  @prop({ ref: () => Car })
  public cars?: Ref<Car>[]; // This is a Reference Array
}

Ill put it into consideration, ill have to test out this method first on other projects before pushing it to DCTinder, thanks!

Well you can just write some tests within a test(ing) folder. If you use js it’s fine but with ts I wouldn’t use that


Convert Guidelines to use 19135, rather that 11179

19135 seems to be more easily used for IRI registries than 11179, so we should convert to that.
Might be able to preserve mappings to 11179.

19135 is used in geo community, but 11179 is encountered more often in the broader community


restoring a wallet

Hi,
I am trying to restore the wallet.dat file backup to a new install on a new computer but the wallet now is empty.
I copied the wallet.dat in the roaming\sibcoin folder to replace the wallet.dat from the new install.
Is there another process to restore a backup wallet in a new install?
Thanks.

Hi! Did you synced you Sibcoin Core with network?


Update OLX parser

The OLX parser got broken, the scope of this task is to update it.

Changes were merged, closing the issue.


DBCC UPDATEUSAGE - best practices

[Enter feedback here]
In the second sentence of the following paragraph from "Best Practices", the bolded fragment can be made much more clear.
Do not run DBCC UPDATEUSAGE routinely. Because DBCC UPDATEUSAGE can take some time to run on large tables or databases, it should not be used only unless you suspect incorrect values are being returned by sp_spaceused.
For example:
Routine use of DBCC UPDATEUSAGE should not be necessary, as SQL Server will properly maintain the metadata under most circumstances. It is appropriate to use DBCC UPDATEUSAGE on an occasional basis, such as when you suspect incorrect values are being returned by sp_spaceused.

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

ID: 6fab3e01-f317-6e83-9081-73f69d2a8b50
Version Independent ID: d9625c39-cacd-c36a-e545-edd5402950bf
Content: DBCC UPDATEUSAGE (Transact-SQL) - SQL Server
Content Source: docs/t-sql/database-console-commands/dbcc-updateusage-transact-sql.md
Product: sql
Technology: t-sql
GitHub Login: @rwestMSFT
Microsoft Alias: umajay

@LonnyNiederstadt -- Lonny, thank you for your suggestion.  I am updating the article.

Thank you for your feedback.  I have updated the documentation and it should be live by tomorrow.


correctly handle empty object name

There's unit test failure.

Codecov Report

Merging #289 (2a61866) into main (f025028) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #289   +/-   ##
=======================================
  Coverage   80.18%   80.18%
=======================================
  Files          44       44
  Lines        4865     4865
=======================================
  Hits         3901     3901
  Misses        742      742
  Partials      222      222

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 f025028...2a61866. Read the comment docs.

There's unit test failure.

This issue is not related to this PR, and it happens randomly, I cannot reproduce it by now.


It only works the first time with jquery mobile

I'm building an app in HTML5 with Jquery Mobile and I'm using the Slick slider for showing a gallery of images but it only works the firts time I change to the gallery page, the next ones it crashes.
$('#roller').on('pageshow',function(){
	console.log("TRIGGER");
	$('.divroller').slick({
		arrows:false,
		dots:false,
		infinite:false,
		slidesToShow:4,
		swipe:true,
		swipeToSlide:true,
		initialSlide:0
	});
});

the images are loaded from a JSON string that returns the html for the divroller div

[SOLVED]. slick adds two classes (slick-initialized and slick-slider) to de divroller div the first time that $('#roller').on('pageshow') triggers. So for the other times to work, the both classes inserted by slick must be removed in order to trigger the slider again


suggestion: prevent typo on some attributes

I just lose 5min because I typed "propsTypes" instead of "propTypes". It might be cool to add some warning about that ?
I am sure there is other keywords we can handle.
Not sure if this should be handled by this plugin.

Note that this problem changes form with ES6 type classes. In that case you would do something like
export default class Note extends React.Component {
  constructor(props: {
    task: string;
    onEdit: Function;
  }) {
    super(props);

    this.state = {
      edited: false
    };
  }
}

Note that I've annotated my example using Flow but you get the idea. Overall ES6 definitions simplify things a lot since we can declare our defaults at the constructor.

I am afraid that typos handling produce a lot of false-positive errors. I find this kind of rule a bit hazardous and I'm not really comfortable with this :|
With the prop-types rule activated you should get a warning that the propTypes attribute is missing and quickly find out the problem.

True say. I get some deactivated rules because of static properties in classes.


Add functionality to hear Differential Revisions too

This allows hubot to listen for mentions of a Differential Revision, and respond using genericInfo from phabricator lib, calling the phid.lookup endpoint, similar to how it's currently behaving for mocks, builds, etc.

Looks great. I will do a release with this improvement asap. Thanks!

Here you are, version 2.4.5 includes your code :+1:

Thank you so much for the quick turnaround! :1st_place_medal:


emilua: 0.7.2 -> 0.7.3, reformat

Description of changes
emilua build is failing on Hydra. This PR updates it to the latest version, released three days ago. Besides reformatting with nixfmt-rfc-style and the version update, nothing else was touched. Let's see if it now builds fine.
All tests pass:
emilua> Ok:                 291
emilua> Expected Fail:      0
emilua> Fail:               0
emilua> Unexpected Pass:    0
emilua> Skipped:            0
emilua> Timeout:            0

Things done

Update versions

Reformat with nixfmt-rfc-style

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage

[x] Tested basic functionality of all binary files (usually in ./result/bin/)

24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Line 87 is no longer required in this new release; this issue was fixed in this commit.
(lib.mesonOption "ipc_actor_msg_max_members_number" "40")

Line 87 is no longer required in this new release; this issue was fixed in this commit.
(lib.mesonOption "ipc_actor_msg_max_members_number" "40")

Makes sense! I've removed that line. Locally, it builds and passes tests just fine. Thanks for the feedback!


Various runhcs shim fixes

Adds Windows shim reconnect logs support
Decrease shim timeout on pipe not found
On Windows because of the way the log pipe is forwarded to the shim there is a
condition where the pipe listener may not yet be active when a client tries to
connect. To handle this case we allow polling on the file and retry on pipe not
found. This limits the pipe not found retry to 5 seconds but leaves the connect
timeout alone as if there is a listener we want to connect to it normally.
Handle shim delete workdir on Windows

One more issue, but LGTM.
There seems to be some unwanted whitespaces
3aef60f - FAIL - has whitespace errors. See `git show --check 3aef60f97960a7bdc6e4a07077602ee2672a02e3`.

@mlaventure - Can you tell me what the build failure was? This builds/tests/verifies locally just fine. Do you have any ideas?

Codecov Report

Merging #2692 into master will increase coverage by 1.42%.
The diff coverage is 68.13%.

@@            Coverage Diff            @@
##           master   #2692      +/-   ##
=========================================
+ Coverage   43.07%   44.5%   +1.42%
=========================================
  Files         100     101       +1
  Lines       10606   10918     +312
=========================================
+ Hits         4569    4859     +290
+ Misses       5316    5307       -9
- Partials      721     752      +31

Flag
Coverage Δ

#linux
47.06% <0%> (-0.03%)
:arrow_down:

#windows
40.74% <68.13%> (+0.5%)
:arrow_up:

Impacted Files
Coverage Δ

runtime/v2/shim/util_windows.go
0% <0%> (ø)
:arrow_up:

runtime/v2/shim/shim.go
0% <0%> (ø)
:arrow_up:

runtime/v2/shim/shim_windows.go
40.85% <73.8%> (+40.85%)
:arrow_up:

remotes/docker/authorizer.go
66.49% <0%> (ø)

metadata/content.go
47.64% <0%> (+5.7%)
:arrow_up:

remotes/docker/resolver.go
70.02% <0%> (+8.69%)
:arrow_up:

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 ac01f20...ab20312. Read the comment docs.

the whitespace error was fixed on the last push; CI passing now


[Test] Delete ErrorBridgedStatic test.

This test checks that error bridging with ObjC bridging works when the stdlib is statically linked. We no longer support static linking of the stdlib on platforms with ObjC interop.
rdar://problem/49699316

@swift-ci please smoke test and merge


Uses deprecated brew sha1 method

The brew formula uses the deprecated sha1 method. We should upgrade to sha256 for security.
Warning: Calling Formula.sha1 is deprecated!
Use Formula.sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/dnsmasq.rb:6:in `<class:Dnsmasq>'

Version: 2.0.1

This was fixed in https://github.com/boxen/puppet-dnsmasq/pull/21.

Thanks!


Live rescans don't convert sent payments to payment-to-self until restart

Use vanitygen to create a key/address pair.
Send bitcoins to the address from your Core wallet.
Import the private key to the Core wallet (with rescan).
Observe transaction list still shows merely the send.
Restart the client.
Observe the transaction list now shows payment-to-self correctly.

Expected behaviour: The rescan should change the transaction immediately.
Not sure if this affects RPC, but it does at least the GUI.
Moved from bitcoin/bitcoin#9421.

This still happening, although descriptor wallets do not support the importprivkey, does this have any mapping to descriptor wallets?


Fix deploy

I broke this in #30 because the files created by the docker images are
owned by the root user. This is easily fixed by a chown command.
Test plan: removed the check for being on the master branch temporarily
to test this, and seems to work:
https://circleci.com/gh/cruise-automation/webviz/170

Is this the canonical way to avoid this issue with Docker or should we be configuring the Docker container with a build arg that sets the user/group or something like that?

Yeah I tried doing that but it seems not possible or at least not easy?


Failed to import SPDX "PACKAGE-MANAGER" vs. "PACKAGE_MANAGER"

We cannot import some SPDX docs because of a small mess between 2.3 and 2.3.1 schemas in JSON and other parts.
We also need to decide on the best format for output.
We should accept PACKAGE-MANAGER and PACKAGE_MANAGER on export.
See the mini mess here:

https://github.com/spdx/spdx-spec/issues/792

Basically thanks to this, both should be supported on reading.
I am not sure which one is the best to export/write as a standard.

The JSON schema at https://github.com/nexB/scancode.io/blob/30c1d8ef8ba2fba01d9549e8b1a3a254a91c2ea2/scanpipe/pipes/schemas/spdx-schema-2.3.json#L325 is using dash

2.3.1 supports both.
https://github.com/spdx/spdx-spec/blob/8a595028b0386138c84f7188237787c374f6a6cf/schemas/spdx-schema.json#L332

In all cases we would need to support both 2.3 and 2.3.1 import and decide on the most popular output string to use.

Schema updated in https://github.com/nexB/scancode.io/pull/1139
Both "PACKAGE-MANAGER" and "PACKAGE_MANAGER" are now valid.


Managed Service Identity authentication is only supported by abfss file scheme

Hi
I keep getting this error anytime I execute the manifestToSQL script on the azure function app

NB: I have setup the the AzureWebJobsStorage__accountName with the value as the storage account name in the Configuration but for some wired reasons, the CREATE external table script failed.
I can establish that the function app can access the manifest, just the external table creation failed

Did you try to create the external table in Synapse serverless pool or dedicated pool?

Eventually got this to work, had to use the adlss link rather than the https link to the manifest file


Fix Pact Given states

Normalise all of the states to "I am a Lay Team user", which is a properly supported provider state
SP-972 #patch

Codecov Report

Merging #123 (ac0beab) into main (75b2e51) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #123   +/-   ##
=======================================
  Coverage   51.57%   51.57%
=======================================
  Files          15       15
  Lines         539      539
=======================================
  Hits          278      278
  Misses        210      210
  Partials       51       51

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 75b2e51...ac0beab. Read the comment docs.


Test functionality against all feature sets

Previously, all functional tests used the default environment feature set when running, i.e. only tested code generated for Java 8 with Guava.

Parameterize all functional tests with the six feature set combinations currently supported (Java 6, 7 + 8, each with or without Guava).
There are now over two thousand unit tests; run them 4-way parallel so a build takes 8 minutes (on my machine) instead of 20.
Parameterize OptionalMapperMethodTest with the Optional type (Java 8, Guava) instead of duplicating all tests.
Clean up two unnecessary code.feature(SOURCE_LEVEL) calls left during refactoring.
Use CompilationUnitBuilder.formatSource in formatter tests.

This PR has got too big; will split it up.


fix: change wording when Builder cannot handle complex query

What does this PR do?
Add extra sentence to wording when Builder cannot handle complex query
What issues does this PR fix or reference?
W-9154690

FYI: Changed the sentence to: Consider using a text editor to edit the query as suggested by Sonal


miru: init at 4.5.5

Description of changes

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Please rebase

@d4ilyrun Sorry this has languished without getting a proper review.
We can try to get it moving, but unfortunately I'll have to ask you to jump through a few more hoops...:

You'll need to rebase against nixpkgs master again. It looks like both pkgs/top-level/all-packages.nix and maintainers/maintainer-list.nix have merge conflicts to fix.

Please update the PR title to match the new version target (it still indicates 2.2.2, but the commit indicates 3.10.6).

The CI report from your last push indicates at least 2 problems:

Your maintainer entry isn't in the right order alphabetically. It looks like you appended it to the end, but it'll need to go in the right spot. At the time I'm writing this, I imagine that means it needs to go between cyplo and dadada.

When you updated the PR to target version 3.10.6, you didn't update the hash/sha256. You'll need to update it to match the new source (and make sure the project still builds/works without needing additional changes).
(You likely didn't notice this problem on your end since you'd already built the 2.2.2 version on your system. Nix uses this hash to look for an existing copy in the store--it won't rebuild if you change the version but leave the hash alone. If you empty the hash string and try to build it, Nix will pull the source again and let you know what the new hash is.)

@onny marked your PR as a draft when he asked you to rebase, which lets reviewers know that the PR needs some work or changes before it's reviewable. Once you make the changes on my list and re-push, please also mark it as ready for review!

(Fair warning: I'm just asking for the things I'm pretty sure you'll need to get this ready for review. Reviewers will likely request at least one more round of changes, if not a few.)

I noticed there's another draft PR open to add this package. If you decide to put additional effort into this one, check up on its progress first:

#238429

If it bogs down, you can also use the review feedback it received as a reference to help handle some issues before review.

Hello @abathur !
Sorry I took so long, I just rebased my branch and followed your advice, it should be good for another review now 😄

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2966

There's a new convention for packages path: by-name.
In this case, pkgs/applications/video/miru/default.nix should be moved to pkgs/by-name/mi/miru/package.nix.

I'm not a decider on this and don't know if we've concluded all new packages must follow the by-name convention--and it's moot if the author eagerly adopts the convention--but I do want to ask anyone making a review/merge call on this point to weigh the risk of bogging down this long-deferred PR over something that wasn't a norm when it was opened and can almost certainly be handled during the eventual auto-migration.

Fair point, @abathur.

Reviewed points
Result of nixpkgs-review pr 172872 run on x86_64-linux 1

1 package built:

miru

[X] package name fits guidelines
[X] package version fits guidelines
[X] package builds on x86_64-linux
[X] executables tested on x86_64-linux
[X] all depending packages build
[X] AppImage application states its sourceProvenance as binaryNativeCode

Possible improvements

The mainProgram meta attribute does not match the binary under $out/bin:
instead of miru, there's a miru-4.5.5. An explicit copy of the
binary to $out/bin/miru should fix it.

Oh sorry I did not see there was a new way of adding packages.
I updated everything to follow the new convention, and renamed the resulting binary's name.

I think most of the stuff can be copy pasta from here https://github.com/heisfer/nixdot/blob/main/pkgs/miru/default.nix

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1450


1.9.0-rc3 random network related build failures

$ uname -a
Linux compooter 4.2.3-1-ARCH #1 SMP PREEMPT Sat Oct 3 18:52:50 CEST 2015 x86_64 GNU/Linux

$ docker info
Containers: 199
Images: 253
Server Version: 1.9.0-rc3
Storage Driver: overlay
 Backing Filesystem: extfs
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.2.3-1-ARCH
Operating System: Arch Linux (containerized)
CPUs: 4
Total Memory: 7.709 GiB
Name: compooter
ID: GKSI:YHZC:YPNI:PAGO:EYPD:AYME:K6BY:BAIH:EBKQ:SOAK:WUFP:6MJM
Username: viktorstanchev
Registry: https://index.docker.io/v1/

$ docker --version
Docker version 1.9.0-rc3, build 2100b94

I'm building with this Dockerfile:
FROM ubuntu:trusty

RUN apt-get install -y curl

RUN bash -c 'curl http://nginx.org/download/nginx-1.8.0.tar.gz | tar -xz -C /tmp'

I get these errors almost every time:
Step 3 : RUN bash -c 'curl http://nginx.org/download/nginx-1.8.0.tar.gz | tar -xz -C /tmp'
 ---> Running in d6f95022d249
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
 26  812k   26  216k    0     0   320k      0  0:00:02 --:--:--  0:00:02  321k
curl: (56) Recv failure: Connection reset by peer

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

It's always a different number of bytes before the connection gets reset by the other side.
If I remove the bash -c from the RUN command instead of the connection being killed right away after it stops receiving data, it hangs indefinitely until the other side closes the connection.
I can't reproduce this when writing to a file instead of piping to tar.
I can't reproduce this on Ubuntu 14.04 on AWS
I can't reproduce this when running outside of docker.
I also can't reproduce with wget -O -

I can't reproduce this anywhere any more. I have no idea what it was.

@vikstrous should we close this one if you're no longer able to reproduce?


NTR: [endoplasmic reticulum membrane biogenesis]

Please provide as much information as you can:

Suggested term label:

endoplasmic reticulum membrane biogenesis

Definition (free text)

The process in which an endoplasmic reticulum membrane is synthesized, aggregates, and bonds together.

Reference, in format PMID:#######

https://pubmed.ncbi.nlm.nih.gov/34617598/
https://pubmed.ncbi.nlm.nih.gov/24373967/
https://pubmed.ncbi.nlm.nih.gov/19825355/

Gene product name and ID to be annotated to this term

ICE2, SGD:S000001352, P40499

Parent term(s)

GO:0044091 membrane biogenesis

Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?

none

Synonyms (please specify, EXACT, BROAD, NARROW or RELATED)

ER membrane biogenesis

Cross-references

For enzymes, please provide RHEA and/or EC numbers.

Can also provide MetaCyc, KEGG, Wikipedia, and other links.

Any other information

anyone able to add this one for me?

@pgaudet

@pgaudet

+[Term]
+id: GO:0160031
+name: endoplasmic reticulum membrane biogenesis
+namespace: biological_process
+def: "The process in which an endoplasmic reticulum membrane is synthesized, aggregates, and bonds together."


Design QA: Trading Page - Outcomes

Design: https://www.figma.com/file/fLWVwmanAwetVZbujQquEi/Market-Page?node-id=209%3A915

[x] Outcomes header: update text style

[x] Labels: update styles

Outcome Rows

[x] Active outcome row should be highlighted with the hover state colour. See design
[x] Outcome name now has a different text styling. Please update
[x] Update number stylings
[x] Dark grey divider lines shouldn't go full width. see design
[x] Add tooltip next to invalid. Copy: "A market may resolve as Invalid if its details or outcome are ambiguous, subjective or unknown. Because Invalid is a resolvable outcome, traders may buy/sell shares in it."

seems done?


Org owner can't access Access tokens

I am an org owner and cannot access the Access tokens content. I get a message that I am not authorized to access that page.

Actually, looks like I exist twice now, and only 1 of me is an Owner. Before I try Remove Users on my other self I want to leave this open so someone can look into why this happened.

@cbaksik We're aware of the duplicate user display issue for org owners and have an existing issue to deal with it: https://github.com/pod4lib/aggregator/issues/638
The issue with accessing tokens is unrelated. I believe a recent change to the application is causing org owners not to be able to access tokens. I've put in a pull request to revert the change, which I'll deploy as soon as it's merged.

Duplicate user display being addressed via https://github.com/pod4lib/aggregator/issues/638


[BUG] Could not pass  ClientConnectionEvent$Disconnect$Impl

Type /rj bugreport and paste here the result.
[20:53:08] [Server thread/INFO] [minecraft/DedicatedServer]: » Running RocketJoin v2.0 by Lorenzo0111!
[20:53:08] [Server thread/INFO] [minecraft/DedicatedServer]: » Command not found, use /rocketjoin help for a command list
Explain your issue.
Whenever a person joins the server, the error below is thrown.
Are there any errors in the console? Use: link.rocketplugins.space/paste
Link is no longer valid, so here's a pastebin: https://pastebin.com/HdguqyKr
Here's the config too: https://pastebin.com/bYzN8bKZ

What sponge version are you using?

Close because of inactivity


Discard mempool transactions containing a nullifier already accepted

fixes #1381

Codecov Report

Merging #1386 (bda7d2b) into master (828364b) will decrease coverage by 8.81%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1386      +/-   ##
==========================================
- Coverage   50.51%   41.70%   -8.82%
==========================================
  Files         145      145
  Lines        7544     9435    +1891
==========================================
+ Hits         3811     3935     +124
- Misses       3066     4859    +1793
+ Partials      667      641      -26

Impacted Files
Coverage Δ

pkg/core/consensus/testing/node.go
0.00% <0.00%> (-93.55%)
:arrow_down:

...ore/consensus/blockgenerator/candidate/testutil.go
0.00% <0.00%> (-90.91%)
:arrow_down:

pkg/core/consensus/testing/utils.go
0.00% <0.00%> (-75.61%)
:arrow_down:

...core/consensus/blockgenerator/candidate/genesis.go
0.00% <0.00%> (-69.24%)
:arrow_down:

...nsensus/blockgenerator/candidate/blockgenerator.go
0.00% <0.00%> (-64.29%)
:arrow_down:

pkg/gql/query/transactions.go
12.60% <0.00%> (-53.38%)
:arrow_down:

pkg/rpc/client/session.go
21.42% <0.00%> (-47.15%)
:arrow_down:

pkg/util/nativeutils/eventbus/eventbus.go
57.14% <0.00%> (-42.86%)
:arrow_down:

pkg/rpc/client/client.go
3.73% <0.00%> (-36.61%)
:arrow_down:

pkg/core/consensus/reduction/aggregator.go
56.25% <0.00%> (-35.06%)
:arrow_down:

... and 166 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 31f056a...bda7d2b. Read the comment docs.


Updating instructions in examples/transports tut

Updated part 1  (1.js)

2022-05-03 conversation: there are two things in this PR:

moving back to CJS
some new/helpful content

We don't want the move back to CJS given we are making js-libp2p ESM-only.  We do want the new/helpful content.
@walkerlj0 : if you are wanting to contribute more here, please reduce to #2 only.  Otherwise, it will get picked up once the EMS-only js-libp2p is released.

@walkerlj0 libp2p 0.37.0 has finally been released with ESM-only exports.
Can you try to make the examples run against the latest version?

@walkerlj0: are you able to incorporate the feedback so the PR can be merged?

I will try and run it in the next coupld days, so sorry, been swamped!

@walkerlj0 we converted it to draft state until you are ready.

@mpetrunic tried running transports/1.js and got this error, advice on how to troubleshoot?
`file:///Users/lindsayjowalker/Git/js-libp2p/examples/transports/1.js:3
const Libp2p = require('libp2p')
^
ReferenceError: require is not defined in ES module scope, you can use import instead
This file is being treated as an ES module because it has a '.js' file extension and '/Users/lindsayjowalker/Git/js-libp2p/examples/package.json' contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.
at file:///Users/lindsayjowalker/Git/js-libp2p/examples/transports/1.js:3:16
at ModuleJob.run (node:internal/modules/esm/module_job:185:25)
at async Promise.all (index 0)
at async ESMLoader.import (node:internal/modules/esm/loader:281:24)
at async loadESM (node:internal/process/esm_loader:88:5)
at async handleMainPromise (node:internal/modules/run_main:65:12)`

@mpetrunic tried running transports/1.js and got this error, advice on how to troubleshoot?
**Note I did fetch upstream from libp2p:master
file:///Users/lindsayjowalker/Git/js-libp2p/examples/transports/1.js:3
const Libp2p = require('libp2p')
               ^

ReferenceError: require is not defined in ES module scope, you can use import instead
This file is being treated as an ES module because it has a '.js' file extension and '/Users/lindsayjowalker/Git/js-libp2p/examples/package.json' contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.
    at file:///Users/lindsayjowalker/Git/js-libp2p/examples/transports/1.js:3:16
    at ModuleJob.run (node:internal/modules/esm/module_job:185:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:281:24)
    at async loadESM (node:internal/process/esm_loader:88:5)
    at async handleMainPromise (node:internal/modules/run_main:65:12)

If you fetched latest master, do npm install in root followed by npm run build. Also do npm install in the examples directory. You shouldn't have require statement anywhere, if you have you probably have some local changes or you didn't pull latest libp2p:master.
Gonna close this PR as examples work just fine for me locally!


"Predict" operators throw an error when no instance is found

When no instance is found on a given frame (which can easily be simulated using SolidColor) Predict nodes crash.
The runner object returns a valid output. However, when trying to allocate the data from the TFTensor to a numeric array the operation returns: "Array must not be jagged".  E.g.:
https://github.com/bonsai-rx/sleap/blob/04c4512a5dc0641bbff12230946ca028f422334d/Bonsai.Sleap/PredictCentroids.cs#L93
I believe the best solution is to return an empty Collection of tracked objects. Users can then filter this Collection by simply checking Count > 0.

Fix in #3


Is there a way to hardcode “response” in @ApiResponse annotation of swagger?

I've the below Swagger annotation for one of my api methods:
@ApiResponse(code = 200, message = "OK", response = String.class)
Is there a way I can hard-code the response ?
I'm NOT keeping any domain objects in my service; my service is a kind-of wrapper service that connects with a third party vendor service and returns the json as-it-is to the caller. So, is there a way I can hardcode the json schema in the response element ?
I know that if I define a domain object and mention its .class, I'll get the json schema in the output but as I mentioned I need to find a way without defining a domain object.
Also providing the hardocded json schema in message attribute will not make sense as because, I believe, this attribute is more for describing the status code, correct ?
Thanks to provide any pointers/suggestions.

I would recommend that your "wrapper" service also delegate to the origin service to provide the swagger documentation. It doesnt make any sense for this "wrapper" service to own the service documentation.
The other option is to serve static swagger service documentation generated from the origin service.

Thanks for responding, Dilip.
Agree with your feedback but I do not own the 3rd party service and not even sure if they have any swagger doc implemented for their endpoints (most probably they don't; their documentation does not mention anything about it).
Looking at the swagger json, it appears that the endpoints refer to the schema via "schema"/"$ref" path that in-turn has a logical reference to "definitions".
Is there a way I can hardcode my json schema under the "definitions" section and then pass on this swagger json to the swagger ui (instead of swagger ui generating its on swagger json via v2/api-docs) ?

you can use http://editor.swagger.io,

This is simply awesome ! Tx Dilip !!!


add anthropic agent

adds basic anthropic agent for #57

going to make an issue for consolidating chatgptagent and this one (since the code is very similar)


adjust BEEFY client logging

Move gossip filter logging to level=trace because it's very spammy.
Move some debug-relevant logs from trace to debug.

bot merge force

bot merge


Only validateCapabilites() after a write has occured, not on a read

Linux Build 3114 outcome was FAILURE using a merge of 1779f13636a8b2bbc85517a32da5772725866b9d
Summary: Execution timeout (new); tests passed: 3046, ignored: 48 Build time: 01:00:11

retest this please


Upload

User Story
As a User
I want to upload a picture
so that I can use my own event-picture
AC

[ ] In the create form should be a possibility to upload a image file

[ ] The Image shuold be saved in the database

[ ] The Image should be shown in the event card

Task

[ ] create new branch
[ ] implement upload-function in form component
[ ] implement uploaded image in event card

Complexity
L

looks good to me, curious to see your own event pictures soon


Add map trail glow

Discussion Reference
All new features must be discussed prior to code review.  This is to ensure that the implementation aligns with other design considerations.  Please link to the Discord discussion:
https://discord.com/channels/531175899588984842/534490472224391169/1283529780494602293
Is this a breaking change?
Breaking changes require additional review prior to merging.  If you answer yes, please explain what breaking changes have been made.
No
This probably has more then a few code style issues, if you point them out I can clean them up. Tried to generally copy the gist of the code style but probably messed up in more then a few spots.

Okay, a couple of things that we need to think through / adjust:

There are too many settings for this single feature.  Let's please decide on some reasonable defaults and keep only what is necessary.

If you think folks will want to tinker, we can use the AdvancedDefaults.cs to add the nitty gritty settings to the advanced.yaml file.

The glowing chase lights are only visible on sections of the trail that are translucent.  By default, the trails are opaque unless there is a verticality difference.  Took me a while to figure out why I couldn't see them at all.  😅

What is the public Distance property for?

Ah. Didn't think that trails were opaque by default. I tried messing around with color of beads but couldn't seem to find something that worked super well. Maybe brightening/darkening the beads according to whether its closer to white or black (as to avoid the previous issue with brightening white trails being invisible)?
As for removable/hideable settings Length can definitely be removed. It's not super noticeable what it does and would probably be more confusing than anything. Speed and Count both feel useful to me, and opacity/brightness is probably useful so it stands out less egregiously from the rest of the trail should you want that.
Distance is the value of the total distance covered by the trail when following it directly (Like how long a drive is when following the directions instead of directly from point A to B). I made it public on the off chance it could be useful in other situations, but it's entirely subjective and can be changed.

@dlamkins are more changes needed?

@dlamkins are more changes needed?

I'll be able to take a closer look later this week.

Also, is there a reason this all happens in its own draw pass instead of around the same area where the trails themselves are drawn?
I'm not entirely sure what you mean. On StandardTrail.Minimap#45-47 it will render the glow bead using the same spritebatch. It doesn't just recolor the existing segment of the line because then the line couldn't be shortened to ensure all beads are of similar length. Distance/angle/opacity need to be recalculated for the same reason. Hopefully that answers your question?

I will try to review this again either this weekend or next.


rollup: pass output.name only if format is umd

The name: pkgGlobals[name]. It's not an error and Rollup doesn't fail for now, but still. It's unnecessary.

Thx for advice, but why should care about it if they emit same outputs anyway?

It's not clean, it may be misleading to beginners looking at the code, it's not safe against future rollup/API (breaking) changes - not future-proof.
:P It's style, self preference. But a good habit. :)

This package is strict TypeScript based, and if rollup API changed for this tiny option, then a big BREAKING CHANGE would be possible, so then we will have to refactor the code anyway.
I don't want to add redundant logic if it won't change anything.


Fix for Business Lic Exp Date submission

Issue:

bcgov/entity/issues/23551

Description of changes:

Fix for Business Lic Exp Date submission

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

/gcbrun

Temporary Url for review: https://strr-ui-dev--pr-212-3ettrw37.web.app


Bottleneck and Stream Delay in get_frames_as_ndarray() Method

I am experiencing stream delay due to a bottleneck in the get_frames_as_ndarray() method. This method is currently fetching only one frame at a time, which is causing the delay. Below is the line of code identified as the bottleneck:
ndarray_frames = self.kvs_fragment_processor.get_frames_as_ndarray(fragment_bytes, one_in_frames_ratio)
I need assistance in optimizing this method to enhance performance and reduce the delay.

@Swapnild-mobinext I am facing the same issues. Did you get any ideas on why it is so slow? For me, it took 3-4 seconds to get a frame.

I found this exciting: when decoding fragment_bytes.
frames = iio.imread(io.BytesIO(fragment_bytes), plugin="pyav", index=...)
It usually takes 3-4 seconds to extract all 30 frames in my case.
I just want to get the newest frame, so I'll change it.
newest_frame = iio.imread(io.BytesIO(fragment_bytes), plugin="pyav", index=-1)
It reduces the bottleneck from 3-4 seconds to 500 milliseconds.


Allow users to specify the acceptable algorithms for crypto operations

Add a collection and a delegate to token validation parameters to allow
a user to specify which cyrpto algorithms are considered acceptable.
fixes #1224

/azp run

/azp run

/azp run

@keegan-caruso can you squash, rebase on top of dev and commit?


Better Documentation

Can you please help me, since I'm a linux noob, to get your cool library working on my system?
I'll tell you which errors it throws me. :)


update(Files): Drag and drop to upload a file

What this PR does 📖
1. Upload any file, dropping it on dropzone
a. Show file path on dropzone when it is over it
b. Just upload a file if it is inside dropzone when we drop
https://user-images.githubusercontent.com/63157656/205096906-97295aea-adc4-4ed0-967a-d6c3be08fa3f.mov
1.1 Upload multiple files in a row
https://user-images.githubusercontent.com/63157656/205107690-88cf0f51-1d9e-4957-a7c4-0927c7792d87.mov
2. To be possible to upload a file, was necessary using with_file_drop_handler on app builder, to recognize file dragging on app
a. True return on final, is to avoid macOS behavior to open file dropped when we drop a file in any place of the app

b. A global variable DROPPED_FILE was created to move file path to other app components, it was a struct to carry drag event and file path, and used rwLock to global variable for security reasons

3. Upload component
a. When we use with_file_drop_handler on app builder, some element functions stop to work like ondrop, ondragexit, oninput (drag and drop), ondragend, so was necessary to use other strategy to be able to identify a drop
b. Used a coroutine to identify if is able or not to drop a new file and upload it

c. drag_over_dropzone is used as ref, and change its value to allow drop and upload a new file, this variable is manipulated on some drag actions

d. If it is true, so we can read DROPPED_FILE variable and see if file was dropped or not to upload it

e. JS scripts were used to change UI, when a file is dragging over dropzone and show its path as well, and back to normal when is dragging out dropzone or was dropped

Which issue(s) this PR fixes 🔨

Resolve #378

Special notes for reviewers 🗒
- If it is possible, test it on macOS, Windows and Linux
Additional comments 🎤

Awesome Lucas! 🔥

Looks good after @dariusc93's mentioned changes

@lgmarchi  this is very nice. I haven't successfully dropped a file on Linux though. I locally added the with_file_drop_handler from the target_os = "macos" section, which stopped Uplink from crashing (panicked on an error), but now i get "File not able to upload ". Also, the ongragover event is re-triggering unnecessarily.
tail -f warp-gui.log.2022-12-02-14 | grep uplink
2022-12-02T14:52:41.962056Z DEBUG uplink::components::reusable::sidebar: rendering reusable Sidebar
2022-12-02T14:52:41.962462Z DEBUG uplink::components::reusable::nav: rendering reusable Nav
2022-12-02T14:52:41.963976Z DEBUG uplink::components::reusable::toolbar: rendering reusable Toolbar
2022-12-02T14:52:41.964276Z DEBUG uplink::components::reusable::nav: rendering reusable Nav
2022-12-02T14:52:41.968237Z DEBUG uplink::components::main::files::browser: updating files list
2022-12-02T14:52:46.277768Z DEBUG uplink::components::reusable::toolbar: rendering reusable Toolbar
2022-12-02T14:52:49.796832Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:49.897721Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:49.999205Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:50.099897Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:50.201490Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:50.303106Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:50.403736Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:50.505111Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:50.605683Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:50.707286Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:50.807868Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:50.909555Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:51.011141Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:51.111705Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:51.213073Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:51.314007Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:52:51.438893Z  INFO uplink::components::main::files::upload: File not able to upload
2022-12-02T14:52:53.955332Z  INFO uplink::components::main::files::upload: File not able to upload
2022-12-02T14:53:08.727457Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:53:08.828595Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:53:08.930249Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:53:09.030949Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:53:09.132490Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:53:09.234179Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:53:09.334792Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:53:09.436368Z  INFO uplink::components::main::files::upload: File on dropzone
2022-12-02T14:53:09.671258Z  INFO uplink::components::main::files::upload: File not able to upload
2022-12-02T14:53:10.771846Z  INFO uplink::components::main::files::upload: File not able to upload

I pushed my changes to a new branch: feat/drag-and-drop-for-non-mac, to capture the latest changes from dev.


Create a DIY Hardware Wallet using Signatory $500 bounty

Create a DIY Hardware Wallet using Signatory $500 bounty
Prize amount
500 USD paid in ETC
Challenge Description
Signatory is an offline transaction and message signer for the Ethereum Stack. The module can run as a standalone server and implement into nodejs projects. We want you to use this module to create a hardware wallet that can sign messages and transactions for an EVM-based network. Your hardware wallet should be a Rasberry Pi, or another single-board computer that is accessible for purchase in most countries.
Motivation
Hardware wallets are a more secure method of storing private keys and signing transactions. This challenge aims to give Ethereum Stack users a DIY hardware wallet solution. Signing EVM-based transactions through a single board computer can have many uses cases including IoT.
Acceptance Criteria

Submission must contain documentation in a DIY tutorial format. Video documentation is a plus (doesn't have to be fancy just showing the solution working)
Submission must allow a user on a desktop/ laptop to sign a transaction or message on an EVM-based network with a single board computer that's utilizing the Signatory module.
Submission must have some type of interfacing or optimized user experience than simply booting up the module on the hardware device. Think of a DApp user plugging this device in their computer with a minimal setup to sign transactions.
Submission must use a single board computer that is accessible for purchase in most countries (For example, Rasberry Pi). Include links to materials used, but this should be implied in your project documentation.

Submission Requirements

Work on your fork of this repository, include your documentation, resources, usage examples,
Complete code and related source files must be included.
Do not delete Pristine template files such as BUILDING.md, CONTRIBUTING.md
, CONVENTIONAL_COMMITS.md, LICENSE.md, etc.

Submission Deadline
The deadline for submissions is April 6.
Judging Criteria
The price will be awarded upon valid and highest quality submission.
Winner Announcement Date
The submission will be reviewed by April 10. Winner announcements and price payouts will occur before April 30.

Bounty owner: Stev
Contact: @stev#0710 on ETC Labs Discord
Discord invite: https://discord.gg/F9nrQm7

@stevanlohja So it turns out I do not have the micro controller board I need, and with the longer shipping times right now, I might not be able to do this in time. I still have a raspberry pi zero, but I was going for both compatibility and customizability. Because of this set back, I might not ending up competing. I'll keep you posted. I still might be able to make this work.

Some progress:
My approach is implement a desktop client that talks to the signatory server running in a single-board computer. Just released v0.1.0 of the desktop client https://vbstreetz.github.io/signatory-client/. For now, the user has to manually install the signatory server in the single-board computer and expose its port.
The initial release allows one to:

Import accounts from saved mnemonic or keystore files
Generate new mnemonic phrases or keystores
Sign and verify messages

Todos:

Sign transactions
Broadcast signed transactions
Ability for the app to install and manage the signatory server in the single-board computer.

Change of plans:
Ditched the idea about a separate desktop app that interfaces with the server running in the pi to a web client that also runs in the single-board computer.

My Plan:
1、bundled DApp project with Signatory and running in docker container.
2、use systemd to auto start the DApp to provide a wallet welcome page

Yo! Some quick demo video on my progress so far:
https://youtu.be/g6LZ1osKw8k
Will appreciate any feedback on it especially on things I may have missed ...

Ok. I have been working on this for a little while now, but it looks like the scale of the project I started is too large to complete in time. I will still continue work but will not have anything remotely finished ready for the hackathon end. Hopefully I'll get a working version ready in the next couple weeks.
If you were unfamiliar with what I am making, I am in the process of creating not only a hardware wallet, but a platform to share components for a modular hardware wallet system so users can have maximum customizability.

@vbstreetz Is the winner. I will close this issue once the polished PR created and merged on his part.


Bug: Overlay triggers for ANY user interacting with Waterfall

This is an authorization issue, where any user regardless of login state can change the overlay by interacting with the waterfall.
We may want to connect this somehow with a token

I wonder if this should be as simple as "only trigger the overlay for the same user who selected something on the waterfall"


Probability maps of some regions not loading

When selecting some areas - for example, "LB (Amygdala) right hemisphere", no probability map is shown in the viewer, despite one being available in siibra-python:
import siibra
from nilearn import plotting
atlas = siibra.atlases['human']
lb_r = atlas.get_region('lb right')
pmap = lb_r.get_regional_map('mni152',maptype='continuous')
plotting.plot_stat_map(pmap.fetch())

After selecting this area in siibra-explorer, it keeps just showing the label mask:

output of the siibra-python snippet above:

issue seems to be fixed (likely related to ebrains tokens, so also resolved by https://github.com/FZJ-INM1-BDA/siibra-api/releases/tag/0.0.2)

will leave issue open until a monitoring step is setup

fixed as of 2.7.6


More Codec documentation.

Adding new pages for AV1, HEVC and MJPEG and and update for h264.

Closing this for now, I've split it into smaller PR.


Heroku To Eliminate Free Dynos

Our service is currently hosted on Heroku free dyno, which is unfortunately going to be no longer available starting November 28, 2022.
We're searching for an alternative hosting platform.

Planning to host this service on our own server set up at home.

I've successfully set up and deploy this service on my own server.
Now sn.nekogc.com is hosted by myself in Taiwan.


Functioning Error in Login-Attempts-Based adaptive authentication script

The Login-Attempts-Based adaptive authentication script is not functioning as the required claim of "failedLoginAttemptsBeforeSuccess" is not added.
Related PR
https://github.com/wso2/carbon-identity-framework/pull/1976/

Hi @GANGANI, Did it work after adding the "failedLoginAttemptsBeforeSuccess" manually?

Hi @GANGANI, Did it work after adding the "failedLoginAttemptsBeforeSuccess" manually?

@madurangasiriwardena
No. It didn't work even after the claim is added manually as the above mentioned related PR depends on #1975 and wso2-extensions/identity-event-handler-account-lock#49

The issue resolves after adding failedLoginAttemptsBeforeSuccess claim manually, with a mapped attribute.
@GANGANI can you re-check?


Do you have a plan to implement training code?

Thank you for sharing awesome code!
Do you have a plan to implement training code?

Would love if you could share a training script

Please share code for training.

Also looking for the training code!

+1 Looking forward to training code

According to this: https://github.com/kjsman/stable-diffusion-pytorch/issues/7
The weights are from a Stable Diffusion pretrained model, so there likely isn't training code.