feat(web): Support TLS encryption

Summary
Implementing #253 (HTTPS/TLS support).
This is to run the server on HTTPS instead of plain HTTP.
Two considerations are worth mentioning:

The options are just the minimum to have TLS. There are many more options and one could add a full section for configuration of TLS. (See e.g. here: https://github.com/PowerDNS/go-tlsconfig/blob/master/config.go). But for my purposes the simple setup is more than enough. If people want more options, they can also use a reverse proxy or load balancer.
At first I wanted to add tests. But then I saw that the serving part of the controller is already untested now. I would have introduced a lot of additional complexity into the testing suite (create certificates, actually run the server, run queries against it) with possibly additional dependencies for creating the certificate. If we instead add hardcoded test certificates, most security scanners would remark that there are credentials in the repo.  And all of this to test just a few calls into the standard library. So I'd like to ask first whether such a test should be added or rather be left out.

How to test it:
Create a certificate pair:
openssl ecparam -genkey -name secp384r1 -out server.key
openssl req -new -x509 -sha256 -key server.key -out server.crt -days 3650

Configure gatus to use the keypair in the config.yaml:
web:
  port: 4443
  cert_file: "server.crt"
  key_file: "server.key"
endpoints:
  - name: example
    url: https://example.org
    interval: 30s
    conditions:
      - "[STATUS] == 200"

Run gatus.
Checklist

[X] Tested and/or added tests to validate that the changes work as intended, if applicable. (I tested it locally)
[X] Added the documentation in README.md, if applicable.

@TwiN Any chance of including this? I tried to make it as consistent as possible with the existing code

Could you add some tests?

It isn't straight-forward with the certificates. What way would you prefer:

Add hardcoded test certificates to the repository (which is simple, but linters ususally don't like it)
Generate a self-signed certificate on the fly with Go (which might need additional dependencies?). Here is an example of such code: https://go.dev/src/crypto/tls/generate_cert.go
Generate a self-signed certificate locally on the dev environment & on github actions before running the test suite

Generate a self-signed certificate on the fly with Go (which might need additional dependencies?). Here is an example of such code: https://go.dev/src/crypto/tls/generate_cert.go

I personally prefer this one.
Based on what I can see in the example you linked, the dependency is only used for building anyways:
//go:build ignore

Alright. Now the code is almost fully tested with certificates which are generated on the fly.
It was actually not as complicated as I expected. I didn't know that go has all the necessary tools already in the standard library.
I'm looking forward to see the CI do its job. On my machine two tests in "client" and "core" are failing. But they don't seem to have any connection with my changes.

Codecov Report
Base: 82.80% // Head: 82.72% // Decreases project coverage by -0.08% :warning:

Coverage data is based on head (66d885d) compared to base (be88af5).
Patch coverage: 65.21% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #322      +/-   ##
==========================================
- Coverage   82.80%   82.72%   -0.09%
==========================================
  Files          54       54
  Lines        3902     3924      +22
==========================================
+ Hits         3231     3246      +15
- Misses        521      527       +6
- Partials      150      151       +1

Impacted Files
Coverage Δ

controller/controller.go
82.75% <37.50%> (-12.70%)
:arrow_down:

config/web/web.go
90.00% <80.00%> (-10.00%)
:arrow_down:

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

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

@TwiN I added tests and updated from master again.

@chr1st1ank @TwiN Any updates on this? I would rather have TLS directly with gatus than adding NGINX

@chr1st1ank I noticed there's no support for ClientCert auth, which is very useful for enterprise environments.
It basically requires adding a field for a CA, and adding a boolean option to verify that the incoming certs are signed by the same CA as the server.
This could probably be added later.

I can resolve the conflicts to master and make it mergeable again, but only if there is an interest for this PR. @gaby the client certificates I'd really rather take separately

@chr1st1ank If you can resolve the conflicts, I'll merge it.
Sorry for the trouble 😔

@chr1st1ank If you can resolve the conflicts, I'll merge it. Sorry for the trouble pensive

Alright, no problem. I've merged master into my branch again and tested it locally. Looks ready to go unless you find any remaining flaws.

@chr1st1ank Thank you so much for your contribution (and patience 😂), I appreciate it!


fix(cache-inmemory): swapped docs for CachedEmoji

The docs for CachedEmoji::available and CachedEmoji::animated were swapped by accident.

Thanks!


Maybe add some labels?

It's a good practice to add a labels.
Currently there is no "New feature request" and "Idea".
Maybe some other labels can be handy.

Just added "feature request" & "RFC"

Was able to sort all existing issues with existing labels so I think we are all set now.


Award sequences

looking forward from #28 the award sequences could be supported too in dynamic hiding to get more visual clarity. An award sequence is an awards group like

Dig 1 dirt
Dig 10 dirt
Dig 20 dirt
Dig 200 dirt
Dig 1000 dirt

If no dirt was digged, only the award 1 (next) is visible, all other are hidden.
If award 1 is reached, the award 1 (completed) and 2 (next) are visible.
If award 2 is reached, award 1 is hidden, 2 (completed) and 3 (next) are visible, the 4,5 are still hidden.
If the last award 5 is reached, only the 5 (completed) remains visible.

That sounds more like “multi-level” award. As in some modern games, where you can complete a level with different rating (e.g. 1 to 3 stars).

Yeah, I'm wondering whether this should actually be displayed in one award as a rating, and the progress to the next rating.

An award sequence could be not linear, like

dig stone
dig tree
craft furnance
smelt steel
craft steel axe

Maybe something like dependency tree?
3 requires 1
4 requres 3
5 requires 2 and 4
...
Hide open awards if not all dependencies reached (Show 5 only if 2 AND 4 reached)
Hide completed awards if "next" awards exits and all reached (Hide 1 if 3 is reached)

You don’t need to dig a tree to craft an axe, you could get sticks in some other way.

You don’t have to dig a tree to craft an axe, you could get sticks in some other way.

This was an example, but you are right, the player can always find ways to skip current award and reach the next one. In multiplayer really easy because you can obtain items and use furnances from other players.
The question is the expected mod behaviour in this case.

you cannot reach the award till the award is "unlocked". Means all axe craftings are ignored till the "dig a tree" is reached (as implemented?)
Award is just hidden, but reachable (unlocked on reach). That means if an axe is crafted before "dig a tree", the award appears and will be visible (my initial expectation)
The award is reachable, but remains hidden if reached. That means if you craft the axe, you do not get the award instantly. If you dig the tree after them, you get both awards because both reached. (behaviour seen in some mobile games, multiple awards appears if an outstanding award is reached,

I prefer 3 for now
@rubenwardy do you reopen this issue or should a new issue be open?

I prefer (2). The behavior you describe in (3) is annoying.
В Thu, 05 Apr 2018 21:00:09 -0700
bell07<EMAIL_ADDRESS>пишет:

You don’t have to dig a tree to craft an axe, you could get sticks
in some other way.

This was an example, but you are right, the player can always find
ways to skip current award and reach the next one. In multiplayer
really easy because you can obtain items and use furnances from other
players.
The question is the expected mod behaviour in this case.

you cannot reach the award till the award is "unlocked". Means all
axe craftings are ignored till the "dig a tree" is reached (as
implemented?) 2. Award is just hidden, but reachable (unlocked on
reach). That means if an axe is crafted before "dig a tree", the
award appears and will be visible (my initial expectation) 3. The
award is reachable, but remains hidden if reached. That means if you
craft the axe, you do not get the award instantly. If you dig the
tree after them, you get both awards because both reached. (behaviour
seen in some mobile games, multiple awards appears if an outstanding
award is reached,

I prefer 3 for now
@rubenwardy do you reopen this issue or should a new issue be open?


Implementation of pelican object stat

The initial implentation of object stat command. This allows users to run the command pelican object stat on an object in a namespace and get the following information: Name, Size, ModTime, and IsDir. The only current issue is that if we stat a directory we are currently unable to give a size as the webdav client does not support it.

Making a draft since it still needs unit testing. Just want to start documenting progress.


Bugfix theme upload

This fixes upload such that a request to upload will upload all files instead of having to specify the exact files.

Also fixes a bug with git repositories
Makes filters work within the theme client so filtering should come for free now

Will this be available for windows x64 download? I'm not sure how to apply a patch to the current version I have.

Just replace the binary.

I had downloaded the file from the downloads area and had to append  the .exe to the end. I'm not that familiar with git and binaries.

I found where I needed to be, thanks again for these fixes!

I just fixed the build script so future releases shouldn't have that missing .exe file extension anymore.

Thanks!


Add a Makefile and Dockerfile

Not sure if you are interested in this or not, but these are the standard Makefile/Dockerfile I use for most repos so that I don't have to install go on my host.
They could be used to run CI as well.

I'd rather not complicate it that much for a project as simple as this.

Fair enough


Support FAST RGB Segment Displays

This PR adds support for the FAST colored segment displays.

ColorSegmentDisplay Device
This new device extends the SegmentDisplayPlatformInterface to a new ColorSegmentDisplayPlatformInterface which supports color setting.
Note: the segment display must be run at baud rate 230400.
hardware:
  platform: fast
  driverboards: fast
  segment_displays: fast

fast:
    driverboards: fast
    ports: /dev/tty.usbserial-14100
    baud: 230400

Segment Display Player

A color: payload can be submitted with any segment_display_player: command, or the action: set_color payload will update the color without affecting the text.
A single color value can be provided for all seven characters, or a list of colors for each character.
segment_display_player:
    timer_seven_seg_display_timer_tick.1{ticks%3==0}:
        7_seg_display_1:
            text: "{machine.high_score:>7}"
            color: 000033, 003300, 330000, 330033, 003333, 333300, 333333
    timer_seven_seg_display_timer_tick.2{ticks%3==1}:
        7_seg_display_1:
            color: 3f0099
            action: set_color
    timer_seven_seg_display_timer_tick.3{ticks%3==2}:
        7_seg_display_1:
            text: "ABCDEFG"
            color: f12711, f23e12, f25414, f36b15, f48216, f49818, f5af19

Other Adjustments

Not all serial devices support low latency mode, this PR adds an error catch so these platforms won't crash
The FAST segment displays require a specific baud rate. This PR adds support for per-serial-bus baud rates on FAST hardware
This PR sets explicit serial communication terms EIGHTBITS, PARITY_NONE, STOPBITS_ONE. If this is overly broad and should be configurable per-connection, please let me know.

Huge thanks to @ecurtz for the foundational work on this one, I'm just the touchup guy here :)

Thanks for the PR guys! Some small nags but generally looks good. Guess we want some unit tests to prevent stuff from breaking over time. As you know if it ain't tested consider it broken ;-).

I will implement this for light_segment_displays as well. The interface fits nicely for those as well. Just waiting for you to finish. Will create a PR afterwards.

Any unclear stuff or problems with the return types or overrides is 100% me being unfamiliar with Python and copy/pasting from the example, rather than being intentional so please go ahead and fix them, no need to check with me.

@jabdoa2 To make prospector happy, I implemented empty set_color() methods on the P-Roc and LISY devices, so color is now possible to configure on any segment display. I got rid of the ColorSegmentDisplay device, so that's one less thing to worry about.
Thanks for the great feedback!


Add disabled date range

It would be great if we could define a disabled date range, like http://amsul.ca/pickadate.js/date/#disable-dates
$('.datepicker').pickadate({
  disable: [
    { from: [2016,2,14], to: [2016,2,27] }
  ]
})

I would like to force users to select dates within a pre-defined date range.

Actually; we have min-max date option but it's not documented yet. Please see: https://github.com/Adphorus/react-date-range/pull/34

Aah 👌.  Will test


Typescript typings do not exist for latest version

The typescript typings for version 2.x do not exist.  It looks like they only exist for version 1.1.  I'm not sure if you're maintaining these, but I just wanted to make you aware if you are doing that.
https://www.npmjs.com/package/@types/klaw-sync
https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/klaw-sync

@jmquigley I am not maintaining that. However, I am aware of it. Thanks for informing me about it though!

Closed since we don't maintain the typescript module here. @jmquigley if you still experience any issues, please reopen or refer that to the typescript module.


Add apt_package_security_updates fact

Add a apt_package_security_updates fact, similar to apt_package_updates but which only lists security updates.

Lines 63-67 (fact apt_security_updates) are about the number of security updates (it returns apt_package_updates[1].length), this adds the list of security updates.

@jle64 Yup i agree, totally makes sense. 👍  Apologies for what i am about to ask
Could you please have a look at replicating the facter tests https://github.com/puppetlabs/puppetlabs-apt/blob/bd3b3fbe990bfa824ebed3504c0c82175d7c7ec9/spec/unit/facter/apt_package_updates_spec.rb for this new fact.
With this new fact, could you add a line or two to the readme explaining this cool new thing

Thanks for the PR #703  is merged. I just added a test.


chore(buf): stop usage of deprecated plugins

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5228

Relevant Lines:
6094

💛  - Coveralls


Count contributions by type

Instead of just returning pairs of ['login', 'full name'] we're returning objects of the form {login, name, url, count} where count is the number of contributions of the given type by the given user withing the specified timeframe. Lots of constraints.
Addresses #34  and #35.
Note: #35 refers to reactors and commit authors, but those are coming in #32. The format will be correct when they do.

Love it. Thank you!


Docs: Why say you likely want CommonJS?

https://www.typescriptlang.org/tsconfig#module
https://github.com/microsoft/TypeScript-Website/blob/695541b6912f2a493672178c6bdd249f34cf3fa1/packages/tsconfig-reference/copy/en/options/module.md

The docs say that You very likely want "CommonJS" but without any explanation.  This was mentioned in #594 also.
It would be very helpful to know why CommonJS is assumed to be the preferred module format over the other options.

Cool, good feedback. I've changed it to "You very likely want "CommonJS" in node projects" which is generally the dominant way people use TypeScript. 👍🏻

Can I suggest thinking through this sentence again? 😅 @orta I can create a new issue if that is better.
Now that all active Node versions support the EcmaScript module system it makes sense to encourage to use the standard; which ended up being ESM.
Some information on the state of EcmaScript module (ESM) support in the Node world: Node 10 didn't support ESM but reached end of life earlier this year, Node 12 supports ESM behind a flag, and from Node 14 ESM is considered a stable feature according to the docs.


joe update

Why vendoring https://github.com/github/gitignore?
Why not adding a joe update command that will do a git pull --quiet --force of the gitignore repository?
The initial clone can be done automatically at first call
And why not allowing to update from another repository (with custom gitignore files (see #9))

Looking into it.

We might want to do what's being proposed in #9. For any platform, we make a ~/.joe folder where all gitignore files can reside.
Post installation, we run joe update which pulls in the submodules and structures the folder as:
- .joe
---- github/gitignore  # submodule
--------- Global
---- custom   # custom files can go in here

This is not a submodule but a simple git repository.
Personally, I would follow XDG specs and store data in ~/.local/share/joe

+1 Great idea!

You could use the Github API so that you don't need to worry this at all. The API automatically pulls the latest version from the gitignore repo. I suppose using the API would conflict with using gitignore.io.

+1

+1. For now joe is not synced with python-ignore. Notice the .eggs folder.
After running pip install --upgrade joe, now I am using joe 0.0.6


post files with other normal params such as input values

I know this has been a long time, but do you mind rebasing on the current head?

@ioquatix done

Thanks for your help improving the documentation.


RTC SWITCH turned OFF 0: ano:1

How can I debug this issue?
RTC SWITCH turned OFF 0: ano:1
It happens 9 out of 10 times!

Robot controller executes a robot program using RTC_SWITCH during ROS control.
This robot program may be holded due to something (error, external hold, etc.).
Could you look at your teach pendant and check the status of robot program named "rb_rtc1"?

I mean it is fine exactly the same as RTC_SWITCH turned off!
RUN > MOTOR > CYCLE [green] and I can see rb_rtc1 as well
I think after CYCLE, I should not UpdateState very fast ... I should wait a little for RTC_SWITCH to sync? Is that right?

I think after CYCLE, I should not UpdateState very fast ... I should wait a little for RTC_SWITCH to sync? Is that right?

Driver waits a RTC_SWITCH's ON when ACTIVATING state is run, so it may be not a problem...
Could you show the entire terminal output?

This is a sample output:
[2020-05-13 16:51:51.366] [info] [khi_driver.h:201] [KhiKrnxDriver] KRNX Linux64 DEV 008 2019/02/04 17:43
[2020-05-13 16:51:51.366] [info] [khi_driver.h:201] [KhiKrnxDriver] Connecting to real controller: <IP_ADDRESS>
[2020-05-13 16:51:53.004] [info] [khi_driver.h:169] [KhiKrnxDriver] State CHANGE 0: NOT_CONNECTED -> CONNECTED
[2020-05-13 16:51:54.085] [info] [khi_driver.h:169] [KhiKrnxDriver] State CHANGE 0: CONNECTED -> ACTIVATING
[2020-05-13 16:51:55.402] [info] [khi_driver.h:169] [KhiKrnxDriver] State CHANGE 0: ACTIVATING -> ACTIVE
[2020-05-13 16:51:55.404] [error] [khi_driver.h:211] [KhiKrnxDriver] RTC SWITCH turned OFF 0: ano:1
[2020-05-13 16:51:55.409] [info] [khi_driver.h:169] [KhiKrnxDriver] State CHANGE 0: ACTIVE -> CONNECTED
[2020-05-13 16:51:55.473] [error] [khi_driver.cpp:261] An error has occured, to resume control of the robot:

[2020-05-13 16:51:51.366] [info] [khi_driver.h:201] [KhiKrnxDriver] KRNX Linux64 DEV 008 2019/02/04 17:43

Your driver is old alpha test version (not released in this GitHub repository) and may have some ploblems.
Could you try our latest version (master) instead of old one?

By adding some delay (time.sleep(x)) between activation and rtc switch, it has been solved.


ur: add no-std support

Codecov Report

Merging #183 (00d6540) into master (f2171c6) will increase coverage by 0.00%.
The diff coverage is 96.29%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           master     #183   +/-   ##
=======================================
  Coverage   96.19%   96.20%
=======================================
  Files           5        5
  Lines        1235     1237    +2
=======================================
+ Hits         1188     1190    +2
  Misses         47       47

Impacted Files
Coverage Δ

src/bytewords.rs
95.18% <66.66%> (ø)

src/ur.rs
90.27% <75.00%> (ø)

src/fountain.rs
96.96% <98.00%> (+<0.01%)
:arrow_up:

src/sampler.rs
99.06% <100.00%> (+<0.01%)
:arrow_up:

src/xoshiro.rs
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@jeandudey this is an alternative to your https://github.com/dspicher/ur-rs/pull/163
Wanna give it a review?


Fix build

Describe the bug
The build script does not produce functional umd and es5 modules.
To Reproduce
Steps to reproduce the behavior:

npm run build
See the errors

Expected behavior
A clear and concise description of what you expected to happen.
Additional context
The rollup packages are heavily outdated.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: Aggregate Transaction View. Changed AggregateBonded signing flow. Inner transaction presentation and Transaction Graphic.

Added Aggregate Transaction Details view
Added support of all transaction types (aggregate inner only)
Added Transaction Graphic (Inner Transactions tab)
Added new sign flow for Aggregate Bonded transactions
Added (Your address) label nex to the current address in the TableView
Improved nested table support in TableView
Added boolean field to TableView (Checkmark and cross)
Added compact view to TableView
Fixed Mosaic field styles

Probably it'd be also good to get @AnthonyLaw and @bassemmagdy's reviews on this one.

@OlegMakarenko You may want to disable sonar cloud for the line of code.
https://github.com/symbol/mobile-wallet/blob/5e563b6f80018693273c3f96ef4d9201b6bbb79a/src/store/network.js#L98

@OlegMakarenko Can you please fix the LGTM issues?
https://lgtm.com/projects/g/symbol/mobile-wallet/rev/pr-70333075811b7da820f168663f2d319cb8eb55d9

@yilmazbahadir @OlegMakarenko could you build APK for me? Looks like Jenkins agent is off again.

@OlegMakarenko below my comments

For key links (voting, address, VRF, node) and address/mosaic alias there is one icon no matter if this is LINK or UNLINK operation. In explorer for UNLINK we have a strike-through icon, for LINK it's not a strike-through. In a mobile wallet, it's always strike-through not matter if it's LINK or UNLINK.

Transaction Details -> About transaction. For bonded aggregates "Received Cosigntures" are not presented correctly. It's always "n/a". Also in the desktop wallet, this field has: "Co-signatures received" label.

For mosaic definition transactions there is a missing "divisibility" field.

Secret proof/lock and Account metadata. Right side of arrow is not resolved to "You" if the address matches. For example: https://testnet.symbol.fyi/transactions/FEF92C4765139C9E4C89AFE614F9A75A815E59FCE15C4421562C80FEEE718301

Mosaic global restriction:

There is missing "Previous restriction value" field
Restriction types are presented as operators for example =, but in explorer, it's word "Equal"

Namespace registration / mosaic creation / has lock / secret locks:

Would be possible to present also human-readable values instead of only blocks? For example add 30d 0h 0m instead only value 86400?
it will require additional calls to present the estimated rental fee for mosaic and namespace? If not we can add that.

"Mosaic address restriction". In explorer on the right side of arrow, we have "mosaic" icon. In mobile wallet it's target address.

https://testnet.symbol.fyi/transactions/0627321705D4D0424BA7EC796E3A621D85212860A9023C9DD3C78EC6E40884ED

Target address is presented without dashes for mosaic address restriction, account/namespace/mosaic metadata). Same with Account address restriction / multisig modifications and address additions/deletions.

Maybe we should change "Waiting for your signature" to Waiting for your review"?

I think that we should present transactions unfold by default. The user should review all of them.

@cryptoBeliever

For key links (voting, address, VRF, node) and address/mosaic alias there is one icon no matter if this is LINK or UNLINK operation. In explorer for UNLINK we have a strike-through icon, for LINK it's not a strike-through. In a mobile wallet, it's always strike-through not matter if it's LINK or UNLINK.

Fixed.

Transaction Details -> About transaction. For bonded aggregates "Received Cosigntures" are not presented correctly. It's always "n/a". Also in the desktop wallet, this field has: "Co-signatures received" label.

Fixed. Label text updated.

For mosaic definition transactions there is a missing "divisibility" field.

Fixed. The 0 values should be diplayed correctly.

Secret proof/lock and Account metadata. Right side of arrow is not resolved to "You" if the address matches. For example: https://testnet.symbol.fyi/transactions/FEF92C4765139C9E4C89AFE614F9A75A815E59FCE15C4421562C80FEEE718301

Fixed.

Mosaic global restriction:
There is missing "Previous restriction value" field

Fixed. The 0 values should be diplayed correctly.

Restriction types are presented as operators for example =, but in explorer, it's word "Equal"

In the Explorer's Transaction Graphic it also displayed as operators.

Namespace registration / mosaic creation / has lock / secret locks:
Would be possible to present also human-readable values instead of only blocks? For example add 30d 0h 0m instead only value 86400?
it will require additional calls to present the estimated rental fee for mosaic and namespace? If not we can add that.

Sounds good. Let's add it in the next PR (to the Explorer as well).

"Mosaic address restriction". In explorer on the right side of arrow, we have "mosaic" icon. In mobile wallet it's target address.
https://testnet.symbol.fyi/transactions/0627321705D4D0424BA7EC796E3A621D85212860A9023C9DD3C78EC6E40884ED

Yes, we should fix it in the Explorer as well.

Target address is presented without dashes for mosaic address restriction, account/namespace/mosaic metadata). Same with Account address restriction / multisig modifications and address additions/deletions.

Fixed.

I think that we should present transactions unfold by default. The user should review all of them.

Added.

Maybe we should allow user to quit here too by adding "Cancel"/"I don't recognize transaction" button? User can close by "x" button but it's not so visible and can force user to just sign because it's easier from UI part.

The extra button will make the purple panel large, and it will be hard to review transaction

@OlegMakarenko
I.

Restriction types are presented as operators for example =, but in explorer, it's word "Equal"
In the Explorer's Transaction Graphic it is also displayed as operators.

I mean here restriction type in explorer it's as text (Equal) but in mobile, it's =:
https://testnet.symbol.fyi/transactions/B60BBCBF46E8015BF05A344A2D64957AD2C6D6C2F058207119608D3754005E75

II.

"Mosaic address restriction". In explorer on the right side of arrow, we have "mosaic" icon. In mobile wallet it's target address.
https://testnet.symbol.fyi/transactions/0627321705D4D0424BA7EC796E3A621D85212860A9023C9DD3C78EC6E40884ED

Yes, we should fix it in the Explorer as well.
It's not a mosaic icon in explorer and an address icon in mobile. How it should be presented?
III.

I think that we should present transactions unfold by default. The user should review all of them.
Added.

I meant here to show transaction details by default. Now user has to click to see details of single inner tx. What you think about it?
IV.

Maybe we should allow user to quit here too by adding "Cancel"/"I don't recognize transaction" button? User can close by "x" button but it's not so visible and can force user to just sign because it's easier from UI part.

The extra button will make the purple panel large, and it will be hard to review transaction
I'm afraid people will accepting by default
V.
Maybe we should change "Waiting for your signature" to Waiting for your review"?
What you think about it?

Would be good to check on IOS if all looks good. @yilmazbahadir we need to push to TestFlight and ask @NikolaiB to verify.

@cryptoBeliever Jenkins is failing to build the IOS and the android artifacts seem to be corrupted. Will try to do it manually today.


Importing TensorFlow causes argparse_flags.ArgumentParser to fail when specifying an argument_default

Basically just the title. This code fails:
import tensorflow as tf
from absl.flags.argparse_flags import ArgumentParser

ArgumentParser(argument_default=42)

Here it is in Colab.
Edit: I should clarify, it only fails if tensorflow is imported

Thanks for filing the bug. Looks like argument_default= simply doesn't work if you have any absl.flags flag defined. This is because a default= argument is passed to custom actions when argument_default= is supplied, but our _FlagAction and _BooleanFlagAction don't support it. Since absl.flags use dest=argparse.SUPPRESS and the default value is never seen through the argparse namespace, we can simply add a default= argument and ignore it.

Is there a workaround?

There isn't a good workaround before we put out a fix, but you could monkey patch these methods to have an extra default= argument:
https://github.com/abseil/abseil-py/blob/4d8ea27b446c943a10a3e9ec60c9a7a2980508ba/absl/flags/argparse_flags.py#L240
https://github.com/abseil/abseil-py/blob/4d8ea27b446c943a10a3e9ec60c9a7a2980508ba/absl/flags/argparse_flags.py#L267


money from mobs

*Description of issue:
Players earn money by killing mobs from a slimefun electricspawner. Not from normal spawners. (I don't want to they get money from the electricspawners)
Server Type (Spigot/Paperspigot/etc):
Paper
Server Version (using /ver):
Paper version git-Paper-216 (MC: 1.16.3) (Implementing API version 1.16.3-R0.1-SNAPSHOT)
Relevant plugins (Delete if this isn't needed):
slimefun, electricspawners

Disable enable-pay-near-spawner in generalConfig

I have it set.

Then "electricspawner" does not supports CreatureSpawnEvent which will get fired when an entity spawns from egg/spawner. You should contact the author of that plugin to make available for other plugins to call CreatureSpawnEvent to avoid for "spawner" plugins adding as dependency.

ok.


Re-run canopy cover

Discussions with @ZongyangLi and myself yielded several updates to canopy cover:

add thresholding so images below quality threshold are not processed (avoid bad values e.g. May 7)
on fieldmosaic step, set "NoData" value separate from the 0 that denotes soil in soil masked images
rerun RGB images for 05/07 and RGB_mask
regenerate fieldmosaic using the NoData fix to generate a % of the visible area for partial plot scans
resubmit canopycover to bety with fixed values

check if geotiff supports NoData or null, if not can we encode -99 as standard NoData value

alpha band for opacity, or a synthetic band 0/1 representing soil, categorized band with multiple settings (NoData, Soil, Mask)
Can we assign a NoData value to VRT before translating to geotiff? it's possible that the source file not having NoData is resulting in (0,0,0)

Add documentation, tests, if an OGC standard for encoding missing data
See also https://aggateway.atlassian.net/wiki/spaces/SG/pages/258670684/AgGateway+Post-Image+Collection+Specification+PICS for ideas

-a_nodata NoData works for gdal_translate.

After lots of different experimentation, gdal_translate seems to conflate NoData and 0,0,0 pixel values during the VRT -> TIF conversion process regardless of VRT NoData settings given to gdalbuildvrt command, or parameters given to gdal_translate.
I set that aside in order to get fundamental process working, and am using -add_alpha flag in gdalbuildvrt to make the fullfield mask an RGBA image instead of RGB, with alpha=255 where the photos exist in the image and alpha=0 where no data exists (between rows) leaving the 0s for soil removed from photos intact. Just modified and tested cc algorithm on a small fieldmosaic of 5 images:

...got a cc value of 98.84% for the whole image. Deploying test on actual fullfield date next, then can rerun all cc data over weekend if it looks correct.

Currently still running but spot checks are looking good:

range 52 (top) and 51 (bottom), columns 9-14
          9 10 11 12 13 14
    ------------------
ROW 52 - 29 36 91 89 75 29
ROW 51 - 87 87 90 84 86 87

These percentages are much closer to what one would expect. I've applied a NoData maximum of 75% (larger than it was before) to push partialplots scans through the pipe, so things like Column 16 will be omitted in those cases:

Expect it to finish Friday or Saturday.

Some more QA tidbits...

on 2018-07-01, 3 of the 5 scans run were full field. The same scan with 'shade' in the name was run twice, and a third scan with 'sun' in the name.

shade  average CC, all plots - 86%
shade2 average CC, all plots - 84%
sun    average CC, all plots - 97%

The sunlit scans are around ~10% higher consistently:

The two shade scans were fairly consistent on average, but a small handful of plots (19/766) had differences above 10% for the shade scans. This is likely attributable to the sensitivity in our rgb_mask algorithm:
Shade2 Mask - 57.8%

Shade1 Mask - 81% , this was also a 2-pass partialplot scan instead of 1-pass (more coverage)

Sun Mask - 85%, nice and bright, more pixels retained here.

I would argue that this doesn't merit further delays for more reprocessing, but it'll be important for data consumers to understand this kind of phenomena when we have multiple differing CC values per-day.
Maybe simplest suggestion is just use the maximum observation for a given day, I doubt over-estimation will be a common problem except in rare cases where e.g. a reflectance test panel or something is on the dirt field and reads as > 0 canopy cover.

We shouldn't use a 'max' per day as a workaround for an algorithm that doesn't function as expected.
The best way to fix the problem is to fix the algorithm. But that may take a while to fix.
Otherwise, if the data are known to be in error, e.g. if the algorithm can't handle sunlit scans, then we shouldn't include that data in the database.
In the end, If we have three measurements from a day then having a single that under-estimates by 10% is a small issue.

That sounds good. To be clear, there are 2 shady scans and 1 sunny - the sunny seems to correctly report the higher value, and the 2 shady scans seem to be under-estimating. Adjusting the RGB mask thresholds could address this case, but it could have other repercussions. Not sure if I'd go so far as to  call it an error.

sorry I got that backward. If it isn't as far as an error, I think adding this caveat to the documentation (README) under known limitations would be okay.

@ZongyangLi and @abby621 can these exceptions be added as test cases to the extractor?

I started uploading the CSVs to bety and noticed a small number of files from May were being omitted from the field mosaics so I paused the upload. Closer examination revealed the omitted mask images had a different TIF header than the majority:
Band 1 Block=2472x1 Type=Float32, ColorInterp=Gray
Band 2 Block=2472x1 Type=Float32, ColorInterp=Undefined
Band 3 Block=2472x1 Type=Float32, ColorInterp=Undefined

The data type was Float32 and the RGB color bands aren't properly indicated (the data itself is fine). But these headers meant GDAL rejected them from the VRT creation because they differed from the other expected header data:
Band 1 Block=2472x1 Type=Byte, ColorInterp=Red
Band 2 Block=2472x1 Type=Byte, ColorInterp=Green
Band 3 Block=2472x1 Type=Byte, ColorInterp=Blue

I'm not sure why the headers are different - perhaps the small number of May files were generated with an older version of the extractor and didn't get re-run properly. The good news is that the fix to data type and RGB header is a simple GDAL command:
gdal_translate -ot Byte -colorinterp red,green,blue source_file out_file
rm source_file
mv out_file source_file

This forces the output file to have properly registered RGB channels and data type.
I'm running a small script to correct these, but it looks like the issue doesn't occur later so I will proceed to upload the remaining CSVs in the meantime. I don't anticipate this will impact the results being sent to bety, we just might get some more plots from early May scans once done.
Should be able to close this issue then, and upload a few of the test images I've been using for future checks.

created #590 to follow on QA process for this.


[ISSUE #8283]optimisation cold data cg ctr service

https://github.com/apache/rocketmq/issues/8283

Codecov Report
Attention: Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.

Project coverage is 42.86%. Comparing base (3ecc73b) to head (4cbf0a1).

Files
Patch %
Lines

.../rocketmq/broker/coldctr/ColdDataCgCtrService.java
0.00%
3 Missing :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #8284      +/-   ##
=============================================
- Coverage      42.88%   42.86%   -0.03%
+ Complexity     10396    10388       -8
=============================================
  Files           1274     1274
  Lines          88956    88955       -1
  Branches       11438    11438
=============================================
- Hits           38151    38129      -22
- Misses         46102    46116      +14
- Partials        4703     4710       +7

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

maybe this pr can merge


Find counties that can be access via API

Our scraper assumes that for most counties, the only way of collection case records is to write a scraper. However, we've heard that some newer versions of Odyssey allow court cases to be queried via an HTTP endpoints.
Scope
Review some of the counties listed in our directory, and see if any of them will allow for direct access. Include any details about rate limitations, or other considerations when getting data in this way.
Links

Counties: https://github.com/open-austin/Odyssey-Court-Records-to-JSON/blob/main/resources/texas_county_data.csv

Afaik, v2 sites' cases can be enumerated directly
On Sun, Aug 21, 2022, 5:11 PM Dan Minshew @.***> wrote:

Our scraper
https://github.com/open-austin/Odyssey-Court-Records-to-JSON/tree/main/src/scraper
assumes that for most counties, the only way of collection case records is
to write a scraper. However, we've heard that some newer versions of
Odyssey allow court cases to be queried via an HTTP endpoints.
Scope
Review some of the counties listed in our directory, and see if any of
them will allow for direct access. Include any details about rate
limitations, or other considerations when getting data in this way.
Links

Counties:
https://github.com/open-austin/Odyssey-Court-Records-to-JSON/blob/main/resources/texas_county_data.csv

—
Reply to this email directly, view it on GitHub
https://github.com/open-austin/Odyssey-Court-Records-to-JSON/issues/31,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTDEAIY2YWGHVVCCKN2JZDV2KSSJANCNFSM57FUMLMA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


bug(List): When list is empty, the checkbox all item status should be unchecked

When list is empty, the checkbox all item status should be unchecked. Now it's checked.

I think it should be absent or disabled too

Good idea! +1 for disabled.

I am closing this because #129 has been merged.


pkl: Exec format error in Dockerfile

Hi, I'm trying to use pkl inside of my Dockerfile. Currently the Dockerfile has something like this:
# Use the official Python image from the Docker Hub
FROM python:3.11-slim

# Install pkl.
# https://github.com/apple/pkl/releases/tag/0.25.3
ARG PKL_BINARY=pkl-linux-amd64
RUN curl -L -o /opt/pkl https://github.com/apple/pkl/releases/download/0.25.3/${PKL_BINARY} \
  || { echo 'Failed to download pkl'; exit 1; }

# Ensure pkl is executable.
RUN chmod +x /opt/pkl

# Add pkl to the PATH.
ENV PATH="/opt:${PATH}"

...

When this image runs on AWS ECS with Linux, the pkl commands work, but when I build and run the image locally on my Mac with M2 chip I get this error.
$ docker build --build-arg PKL_BINARY=pkl-macos-amd64 -f .../Dockerfile -t my-app ./
$ docker run -p 3000:3000 my-app
sh: 1: pkl: Exec format error

The binary you are using is pkl-linux-amd64, which is for Intel/amd64/x86_64 architecture processors. To run on ARM processors like the one in your M2 Mac, you need to use the pkl-linux-aarch64 binary.
If you are building a multi-architecture container image then you can use the TARGETARCH arg to choose the right binary to download. See the Docker documentation on how to use this arg: https://docs.docker.com/build/guide/multi-platform/

Closing as this is not a Pkl problem (see @HT154's comments)


Update dev dependencies

Changes

Removed @nrwl/nx-cloud v15 (already replaced by nx-cloud v16)
Replaced rollup-plugin-terser with @rollup/plugin-terser
Removed eslint-config-standard, eslint-config-standard-react, eslint-plugin-standard, eslint-plugin-node
Moved babel-eslint, eslint-plugin-flowtype out of root
Updated rollup plugins
Updated tsup
Updated vite plugins
Updated vitest
Updated @testing-library/react, solid-testing-library

Codecov Report
Patch coverage has no change and project coverage change: +30.13 :tada:

Comparison is base (9b285d9) 58.82% compared to head (11ea30b) 88.95%.

:exclamation: Current head 11ea30b differs from pull request most recent head f88bc2a. Consider uploading reports for the commit f88bc2a to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff             @@
##            alpha    #5466       +/-   ##
===========================================
+ Coverage   58.82%   88.95%   +30.13%
===========================================
  Files          14       70       +56
  Lines         102     2382     +2280
  Branches       15      624      +609
===========================================
+ Hits           60     2119     +2059
- Misses         36      218      +182
- Partials        6       45       +39

see 58 files with indirect coverage changes

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


Facet values starting with - are considered exclusions by default

Do you want to request a feature or report a bug?
bug
Bug: What is the current behavior?
When facet values displayed in a refinement list (or menu, hierarchical menu) are starting with a dash like temperature: -80C then clicking on those values will fail because it will be understood as a facet exclusion by the Algolia engine.
Example: https://codesandbox.io/s/jpkzxoo20v
Clicking on any refinement won't change anything
Bug: What is the expected behavior?
Clicking on refinements should refine. Values should be automatically escaped.
Bug: What is the proposed solution?
We could automatically escape refinement values to "-80C", since doing a refinement list with excludes is not today a feature. And if it is a feature at some point then it will be explicit not based on the data.
What is the version you are using? Always use the latest one before opening a bug issue.
Latest

I wonder if this is a method or option on the existing method in the Helper we could have, for example escapeFacetValues, in this case about things relevant for Algolia though, not about the option against XSS injection. Not sure what a better name can be and which other values need to be escaped


[Designer] Make everything accessible at high zoom levels

Related Issue
Fixes #6263
Description
A bevy of fixes for the designer on small screens. Pushes a bunch of runtime-defined CSS styles into classes so that they can be overridden by media queries at render time. Below 500px width, we shift to a vertical scroll model which, while not ideal from a usability perspective, at least allows the user to access all of the content, which was not possible before. Having a more usable experience is something that will require design resources which we'll have to engage at a later time (see #6313).
Screenshots
Before
Main
(note: no scrollbars)

New Card Dialog
(large margins)

After
Main

New Card Dialog

How Verified
Manual testing
Microsoft Reviewers: Open in CodeFlow

Looks good overall, however:

In "mini" mode, dragging a new element onto the card makes the card basically disappear. I believe this happens because the associated item in the treeview is forced into view, which works with the normal layout but not when all panes are stacked on top of each other

the scroll-in-to-view fix was pretty easy, but the drag/drop overlay fix was a little gnarly (there was some math that didn't account for scroll position (because there wasn't a need to before)).

You apparently have the threshold set to 501px horizontally, but the designer starts being unusable well before that. Would it make sense to change the threshold to something a little higher?

I set it to 651px since that's about as small as you can go and still sort of use everything...


iCloud Photo Not Displaying

Good evening!  I have been trying to configure this module to work with my public iCloud Photos album for a few days now (off and on).  I have not been successful in getting the source to work for it.  When I use Bing or Chromecast as the source, it works great!
This is likely user error, but I would greatly appreciate any help you are able to provide!
I've tried the following for the source line:
source: "icloud:https://www.icloud.com/sharedalbum/<assigned#>" - This give me a black screen
source: "https://www.icloud.com/sharedalbum/<assigned#>" - This give me a black screen
source: "icloudphoto:https://www.icloud.com/sharedalbum/<assigned#>" - This defaults back to bing
source: "icloudphotos:https://www.icloud.com/sharedalbum/<assigned#>" - This defaults back to bing
Entire Module for reference:
modules: [
{//https://github.com/kolbyjack/MMM-Wallpaper
module: "MMM-Wallpaper",
position: "fullscreen_below",
config: {
source: "icloud:https://www.icloud.com/sharedalbum/<assigned#>",
filter: "grayscale(0.5) brightness(0.5)",
orientation: "auto",
crossfade: true,
updateInterval: 60 * 60 * 1000,
slideInterval: 5 * 60 * 1000 // Change slides every minute
}
},

It should be just be icloud:<assigned#>

That worked! Just for reference, the iCloud link had a # sign starting that specific code.  I tried it with the # sign and it dit not work.  I removed it and it did!  This just made my weekend!  Thanks!

Where can I get the Assigned ID please? I can not find it anywhere. Thanks

I got it. Thanks

For assigned ID, you have to use a Mac device and open Photos. There you can identify the shared folder and the ID will be embedded on the URL when you view the shared album on a browser. The ID is the number following the # symbol.


Allow user to tune LRU size

1024 seems to be a pretty arbitrary number for the LRU size. Is there any way that we can change it? Even in compile time is fine.
Code:
https://github.com/intel/ideep/blob/a861d8c2b2cceddb4d17b924b75bc1ce0a20eec0/include/ideep/lru_cache.hpp#L293

Yes, its arbitrary. What's your scenario and suggestion?

Caching excessive primitives and their buffers will cause memory bloat. And I believe this cache is per-thread, right? @gujinghui and @jgong should know about the use case more, say rcnn.

I see. I'll talk to them go gather more information. Meanwhile, I think the problem might be per-operator cache will accumulate same amount of ops, that's a point we can immediately optimize.

@yinghai How about we allow the control of these sizes via some environment variables, just like OMP env flags?

Hi folks, I think removing per-op caching and having environment variable are both good solutions.

@yinghai can I close this issue now?

@mingxiaoh I don't think we have implemented a solution for this issue. We may close after that.

Done in https://github.com/intel/ideep/commit/f088c56ee78bab675d922c1892018e3e93bb9eef


Add Configuration.Taml.Net

Fixes https://github.com/csharpfritz/TAML/issues/63

Thank you so much for putting this together so quickly!  I noticed that the folder and project name is not spelled correctly:  Configuration.Taml.NET
I'll review more of the code

I don't think we should reference the Taml.NET project directly, but rather go through a NuGet package reference so that consumers get that NuGet package installed as well.

I like the inline TAML in the tests!

but rather go through a NuGet package reference so that consumers get that NuGet package installed as well.

This shouldn't be necessary. By referencing the nuget package Configuration.Taml.Net will always be one package behind. Also dotnet pack would detect that TAML.NET is a package and add that to the dependencies of Configuration.Taml.Net.

I'm going to review and merge this in today's stream.   We'll add a GitHub action to publish a NuGet package as well. HUGE thanks for the contribution!


js code generator

first cut of javascript code generator - generates the model classes based on specifications

@natabal pls review

@killanch Just for my understanding, can you summarise the capabilities of this initial version?
As i understand from the current code, it just creates the base entities with its properties, but no reference to children or relations, correct? Also missing the session object or root object to start the connection towards VSD.
(Want to understand the status :))
Thanks!

@pdellaert yes, it just creates the base entities. similar to,
https://github.mv.usa.alcatel.com/Architect/vsd-react-ui/blob/master/src/lib/models/NULocation.js

@natabal addressed alignment, and other es-lint reported errors in generated file. pls merge PR.

@natabal pls find sample file generated.
Since github wasn't allowing .js extension file to be attached, Ive renamed the file with .txt extension
NUEnterprise.txt


Multi Fallback Language

Describe the bug
The issue is when define fallbackLng as an object with multiple fallback options deson't work
  fallbackLng: {       'en-eg': ['en'],   }
it only works if I defined the fallbackLng as a string like
fallbackLng: 'en'
after some investigation on the library itself i found this block of code
  if (typeof config.fallbackLng === 'string') {               initialI18nStore[config.fallbackLng] = {};             }
which means the fallback language assigned if it's a string only.
Occurs in next-i18next version
8.2.0
Steps to reproduce

in the next-i18next.config.js file add this as i18n  object

module.exports = {
  i18n: {
    locales: ['en-eg', 'ar-eg', 'en', 'ar'],
    defaultLocale: 'en-eg',
  },
  supportedLngs: ['en-eg', 'ar-eg', 'en', 'ar'],
  debug: true,
  lowerCaseLng: true,
  defaultLanguage: 'en-eg',
  otherLanguages: ['ar', 'en', 'en-eg', 'ar-eg'],
  whitelist: ['ar', 'en', 'en-eg', 'ar-eg'],
  fallbackLng: {
    'en-eg': ['en'],
    'ar-eg': ['ar'],
  },
};

add the local files in the following path

try to use a translation key that exists on the en/common.json while your language is
en-eg. you will find that the key is not translated hover it's defined as a fallback language
`
Expected behavior
if  you define a fallback language for a specific language it should be working probably
Screenshots
If applicable, add screenshots or a GIF to help explain your problem.
OS (please complete the following information)

Browser: [e.g. Chrome  89.0.4389.90 ]

I believe this is fixed by #1197, right?

@isaachinman yes it's fixed :+1:

@isaachinman do you plan to create a new release with this fix soon?
Thanks :)

Released in v8.4.0.


feat: add run-chain to run a chain of pods

Now there's a "run chain" button to run a chain of pods connected with arrows.

Update: wait for the execution result before running the next pod, i.e., run the chained pods one by one. This chained behavior applies to the pods with the vanilla Run button as well. Show a loading indicator of all pods scheduled for running. Screenshot:


MINOR: require final on variables and parameters

@mjsax Here you go!

Rebased on the flaky test fix.
I'll merge when the tests pass.


fixes call to get API endpoint

fixes an issue where we are not fetching the GOALERT_ENDPOINT_URL from env vars and setting it to the literal string. This was causing the operator to crash

1.6972086990330393e+09	ERROR	Error sending HTTP request	{"controller": "goalertintegration", "controllerGroup": "goalert.managed.openshift.io", "controllerKind": "GoalertIntegration", "GoalertIntegration": {"name":"osd","namespace":"configure-goalert-operator"}, "namespace": "configure-goalert-operator", "name": "osd", "reconcileID": "3a64d4d1-49a8-4cca-a0d5-547a02d5068b", "controller": "goalertintegration", "error": "Post \"**GOALERT_ENDPOINT_URL**/api/v2/identity/providers/basic\": unsupported protocol scheme \"\""}

/lgtm

Codecov Report
Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 10.39%. Comparing base (6cb636e) to head (dad096f).
Report is 24 commits behind head on main.

Files with missing lines
Patch %
Lines

...oalertintegration/goalertintegration_controller.go
0.00%
1 Missing :warning:

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #56   +/-   ##
=======================================
  Coverage   10.39%   10.39%
=======================================
  Files          12       12
  Lines         664      664
=======================================
  Hits           69       69
  Misses        586      586
  Partials        9        9

Files with missing lines
Coverage Δ

...oalertintegration/goalertintegration_controller.go
0.00% <0.00%> (ø)


Split Actors interface betweeen runtime and internal

Related to #6538
Splits the Actors interface into two parts:

Actors includes methods that actors can invoke only, such as calling actors, working with timers and reminders
ActorsRuntime is the main actor runtime. It embeds Actors and it offers additional methods that are only used internally

This change makes it possible to expose to internal actors (such as workflow) a subset of methods. It will make it easier to create more internal actors (see #6538).
Otherwise, this PR doesn't include any changes in functionality. Changes can be considered mostly cosmetic.

/ok-to-test

/test-sdk-all


Laravel 6.0 Support

Are there any plans to upgrade to laravel 6.0?

Hello,
Critical for our project as well. Do you have a time line for Laravel 6.0?
Thanks

please add support for laravel ^6.0

Open to PR's people :)
Very busy at the moment so haven't had much time to update my packages.

Hi Joedawson, This package is a very helpful package, Please investigate your time on it and we are here to help you with the donation if you want.

I have submitted a pull request which should work with Laravel 6 and 7.
https://github.com/joedawson/youtube/pull/115

Thanks @artisansweb - merged and tagged for release (5.0.0)!


train.py problem

patrick@123:~/Desktop/Dog-Cat-Classifier-master$ python predict.py test_cat.jpg Using TensorFlow backend. 2019-10-25 00:19:23.323125: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 2019-10-25 00:19:23.340188: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz 2019-10-25 00:19:23.340916: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x694d4f0 executing computations on platform Host. Devices: 2019-10-25 00:19:23.340974: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (0): Host, Default Version [[1. 0.]] [0] It is a cat !
I have entered train.py
without removing or adding any image
but accurancy prints [[1. 0.]]
could you tell me why?
thanks.

First number shows the possibility of being a cat in image. When you tested with cat image, you would get 1.0 and 0.0, so it is %100 cat and %0 dog.

When I tested with dog image, I got the same result.
The accurancy is correct after using predict command: python3 predict.py
But It it goes wrong after I used model training: train.py

It is because the model has been retrained. you can try with other photos. Or you can share the training result with us.


Running SCDF in 2 HA Kubernetes cluster

I would seek help to understand as how we can run a HA setup for the SCDF running on K8S, we would like to get this setup done by using the GTM/LTM setup, LTM will redirect to the NGINX for the PKS clusters. But how it can be achieved for the Production usage.
Thanks in advance

You should open an issue here https://github.com/spring-cloud/spring-cloud-dataflow


Factor out default constructor implementations

The default constructor implementations should be available from the library under other names, such as initializeRecord initializeVariant etc., so that T() can be overloaded without losing access to the base implementation.

fixed by @Blei in #211


End Of Round Summary window shows gamemode preset instead of actual gamemode

Description
on the end of round summary, instead of saying the actual gamemode it says the gamemode preset, which usually means it says "secret" instead of "traitors", "revolutionaries", "survival", etc
Reproduction

finish round
look at end of round screen
"gamemode was secret"
:mistake:

Dupe of #31592


feat: How to create a multi-column and multi-row?

Describe the feature you'd like to request

Describe the solution you'd like to see

Additional information
No response

just like notion


Bonuses for phase1

do we have any? @tomergd
if we do need to handle whitelisted/unwhitelisted
if we dont need to remove API calls

We don't have any rewards on phase 1 @sirpy

call was disabled
the menu is displayed on the right side
Checked on DEV V0.21.1-0
Desktop: Windows 10 // Google Chrome 83.0.4103.61


Fix Flux redeploy script

Body was a Readable stream and needed to be converted to JSON

chris says fetch changes fixed this


An error occurs when creating a purchase invoice for an asset.

Information about bug
When creating a purchase invoice with update stock checkbox, if the item is a fixed asset and the option to create the asset upon purchase is enabled, the following error occurs:

Module
assets
Version
Assets: v0.0.1 (pre-prod)
ERPNext: v15.34.0 (pre-prod)
Frappe Framework: v15.41.0 (pre-prod)
Installation method
None
Relevant log output / Stack trace / Full Error Message.
No response

Fixed https://github.com/8848digital/Assets/pull/49

issue resolved


Investigate unexplained CI unit-test hanging failure

Unit tests sometimes run endlessly (hits 5 minute timeout). Error message seemed to indicate zero-copy test. https://github.com/infinyon/future-aio/runs/1318014539?check_suite_focus=true

can close this?


Avoid capability checks on ID values. They are not literals

Works around issue 248 by weakening the test:
https://github.com/KhronosGroup/SPIRV-Tools/issues/248
The validator should try to track (32-bit) constant values, and then
for capability checks on IDs, check the referenced value, not the
raw ID number.

Request a review by @umar456 and either @antiagainst or @AWoloszyn

LGTM as a temporary workaround

LGTM, +2

Rebased and pushed into master


Maven is now able to run TestNG own tests

FYI: There's 15 tests failed when build & tests runned using maven.

Thank! I didn't have the problem because I had gradle directory with available files.
I will fix it asap.


Not able to click on child component

As title, I'm not able to click on any TouchableHighLight which is the child of Drawer.
I have configured as the following snippet
<Drawer ref={c => this.drawer = c}         type={'displace'}         openDrawerOffset={100}         closedDrawerOffset={0}         panOpenMask={.1}         panCloseMask={.9}         relativeDrag={false}         content={navLayout}         styles={drawerStyles}         tapToClose={false}         negotiatePan={true}         side={'left'}> CHILD COMPONENT </Drawer>

It seems that pan gesture has taken over touch gesture, how can I fix it?

I came across the exact issue and what I did was adjusting panCloseMask so that the child component onPress event get triggered, not very ideal but it works for now

I had to do some dirty hack by overriding onStartShouldSetPanResponderCapture (for more info read: https://facebook.github.io/react-native/docs/panresponder.html) so that the panOpenMask would stop messing with my top left corner button.

What work for me was to set PanCloseMask to a lower value panCloseMask: .2

Any updates?


Segmentation fault on building and running latest version

Hi,
I built the package on Ubuntu 18.04 and tried running some sample example tests.
However each one of the tests failed due to seg faults and core being dumped. Did some basic troubleshooting and I find that the memory consumption is going very high and ultimately runs out of memory.
I suspect this to be issue with incompatible libroaring.so version. Which is the version of the CRoaring you have found to be working?
I am trying with an older version of CRoaring but there are so many builds so this might be time consuming. I will report if I find something working in the trials.
The build process pull the latest version of CRoaring v0.2.52 of the library. Is there any way to configure the version in the build process?
Thanks,
Manohar

This is the generated progressivis.egg-info
``
Pillow>=4.2.0
numpy>=1.11.3
scipy>=0.18.1
numexpr>=2.6.1
tables>=3.3.0
pandas>=0.19.1
scikit-learn>=0.18.1
toposort>=1.4
tdigest>=<IP_ADDRESS>
flask>=0.11.1
tornado>=4.4.2
h5py>=2.6.0
zarr>=2.1.4
numcodecs>=0.5.2
bcolz>=1.1.2
datashape>=0.5.2
pyroaring==0.1.7
msgpack-python>=0.4.8
boto
s3fs
sqlalchemy
memory_profiler
tabulate
requests
``
From the above  pyroaring==0.1.7 gets required.
I could not find a working release of libroaring for me; tested several combination from v0.2.0 to v0.2.30.  Lower versions failed to link.
Any suggestions on how to get it to work?

Found the issue!
The initial pip install takes input from requirements.txt and there pyroaring is set to 0.0.7 which causes the problem. I will submit a PR to correct this.
However, the test still crashed with memory issues but maybe this requires a different ticket to analyze.

Hi,
Thanks for your feedback! The requirements.txt has been fixed, I'll try to reproduce the memory issues.


Check for overflow when creating transfer

Thank you for submitting this pull request :)
Fixes #2078
Short description
Add am overflow check for the amount of the locked transfer before sending it.
Definition of Done

[x] Steps to manually test the change have been documented
[x] Acceptance criteria are met
[ ] Change has been manually tested by the reviewer (dApp)

Steps to manually test the change (dApp)

Thanks for the review! I'll fix the points. As for the other locations: I saw there were more issues, so I just wanted to this to get up to speed.
Do you have any idea why the tests would fail? I can't really interpret the errors.

@palango to ease reading the logs (specially when it was a single failure, like your error), I suggest piping the url from Open Raw Step Output CircleCI action with curl to less, and backwards-searching (?) for FAIL, it should take you directly to the failed test logs.
In this case, it seems the expected action simply wasn't there, and if you look into the end of the output array, there's no transfer.success or transfer.failure for your request. This is probably caused by you violating some expectation with the type assertion, by telling the compiler to trust you that BigNumber is a UInt<32>, while it's just outside of the range. Use a value in the range, and it should pass, the rest of the test seem ok.


Crash when running game if an entity has a non existing script attached to it. #414

Fixes #414

SonarQube analysis reported 6 issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 ScriptManager.cpp#L651: Memory leak: value
 ScriptManager.cpp#L655: Memory leak: value
 ScriptManager.cpp#L659: Memory leak: value
 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)
 ScriptManager.cpp#L673: The function 'GetScripts' is never used.
 ScriptManager.cpp#L681: The function 'ExecuteScriptMethod' is never used.

SonarQube analysis reported 6 issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 ScriptManager.cpp#L651: Memory leak: value
 ScriptManager.cpp#L655: Memory leak: value
 ScriptManager.cpp#L659: Memory leak: value
 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)
 ScriptManager.cpp#L673: The function 'GetScripts' is never used.
 ScriptManager.cpp#L681: The function 'ExecuteScriptMethod' is never used.

SonarQube analysis reported 6 issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 ScriptManager.cpp#L651: Memory leak: value
 ScriptManager.cpp#L655: Memory leak: value
 ScriptManager.cpp#L659: Memory leak: value
 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)
 ScriptManager.cpp#L673: The function 'GetScripts' is never used.
 ScriptManager.cpp#L681: The function 'ExecuteScriptMethod' is never used.


Don't send live content to draft content store.

This was happening during dependency resolution
because the GetLatest query will return drafts if
they exist.

LGTM


Allow kill multiple ports at once

@brunolemos thanks for the suggestion! I just added it on v1.3.0 👍

@tiaanduplessis nice! I made this tweet to share this lib: https://twitter.com/brunolemos/status/1013541511231868933


Remove HarfBuzzSharp dependency for Avalonia.Direct2D1

Is your feature request related to a problem? Please describe.
I think the title is pretty self-explanatory. I think it would be good if Avalonia.Direct2D1 didn't depend on HarfBuzzSharp. SharpDX.Direct2D1 already has a text renderer (DirectWrite), which led me to think that HarfBuzzSharp was not used a lot and it turns out that there are only two file that uses it:
TextShaperImpl.cs
GlyphTypefaceImpl.cs
Describe the solution you'd like
Replace the uses of HarfBuzzSharp with their DirectWrite counterpart (If said counterpart exists).
Additional context
One of the benefit would be to remove the last native dependency for a Win32 and Direct2D1 application. libHarfBuzzSharp.dll is the last native file in a self-contained single-file .Net 6 app (You can remove it using by setting IncludeNativeLibrariesForSelfExtract to true but I don't think it's the right solution).

Feel free to change the implementation to use https://docs.microsoft.com/en-us/windows/win32/api/dwrite/nf-dwrite-idwritetextanalyzer-getglyphs

SharpDX isn't covering everything we need and many parts don't work with Spans etc. so we need to allocate extra memory. I prefer HarfBuzzSharp over additional API's that are exposed via SharpDX.

@Gillibald I understand that one might be better than the other. But if one supports everything Avalonia.Direct2D1 needs (Which I think SharpDX.Direct2D1 does), I think we should take it. The reason I wanted to only have SharpDX.Direct2D1 is because it's already used in a lot of place in Avalonia.Direct2D1 while HarfBuzzSharp is used in 2 files.

The moment there is a modern maintained Direct2D1 binding I am willing to remove the HarfBuzz dependency from the Direct2D1 backend.


Possibility to list only reports w/ changes

Hi! This PR is my first PR are not angry with me :/...
This PR was opened to solve the issue #127 ... review please!
Thanks! ;)

@rafaelhenrique can you squash this into a single commit?

Sure! And i need create a new PR after this??

Could someone tell me how to proceed after the squash?

Squash the commits. Then git push -f origin master

Thanks @nibalizer I'll do it now

Done... review please ;)

:+1:

I've tested it. It works as expected. :+1:

And anyone can merge? If not explain to me please ... :/

I don't fell confident merging this since this is really @daenney's project. We'll see if he has time to review it soon and if not we'll decide what to do then.

Ok. Thanks ;)

@rafaelhenrique if you can rebase this against master we can move forward with merging it.

Done @nibalizer :+1:

?

Is there still interest in this patch? Sorry we've been unresponsive. There is a big load and we're always looking for more contributors.

I vote for this patch! It is more interesting to be able to se what has happened than that nothing happened. Perhaps there should be a label with the last report just to validate that it has run.

@janorn or @rtib can you try the re-upload of this on #160 then ping me aggressively until I merge it? For the record the best place to yell is on irc in #puppet-community or on twitter.

Too late


invalid option: -r

Therefor there is an issue as I have always the following output at the end of the executing of my tests no matter the test pass or not:
invalid option: -r

minitest options:
    -h, --help                       Display this help.
    -s, --seed SEED                  Sets random seed
    -v, --verbose                    Verbose. Show progress processing files.
    -n, --name PATTERN               Filter run on /pattern/ or string.

Known extensions: pride
    -p, --pride                      Pride. Show your testing pride!

This return a code different than 0 so mark my build as failed while it should not.
This behaviour seems to be since the use of the 2.0.0.beta.3.

Sorry @tooky I will try by tomorrow or during next week.

@zedtux that would be great. Thanks.

@mattwynne @tooky I've tried to upgrade my brewformulas.org project to the latest version of all the gems, including the version 2.0.0.rc3 of Cucumber and I don't see the reported issue.
Or I don't have this issue in this project or the issue has been solved since.
I can try with the version 2.0.0.beta3 in order to check if the issue is present or not.

Well I have this error with the beta 3:

lib/cucumber/mappings.rb:208:in <class:MapStep>': undefined method initializer' for Cucumber:Module (NoMethodError)

Yeah that's probably because of an incompatibility in the new version of the core with that beta version of cucumber. To be honest, I suggest we just close this and move on with our lives. If it comes up again we can tackle it then.
OK with you @zedtux?

I'm fine and I do it :)

Thanks @zedtux!


Full support of options parameter for POST/PATCH/PUT entities

Describe the solution you'd like
As listed in https://fiware-orion.readthedocs.io/en/master/orion-api.html#update-attribute-value-put-v2entitiesentityidattrsattrnamevalue. There are the following options parameters. For example, flowControl and forcedUpdate are currently not implemented in Filip.

Options
Description

keyValues
When used, the response payload uses the keyValues simplified entity representation. See Simplified Entity Representation section for details.

append
Force an append operation.

overrideMetadata
Replace the existing metadata with the one provided in the request. See Metadata update semantics section for details.

forcedUpdate
Update operation have to trigger any matching subscription, no matter if there is an actual attribute update or no instead of the default behavior, which is to updated only if attribute is effectively updated. Check also the entityUpdate alteration type for the same effect.

flowControl
Enable flow control mechanism, to avoid saturation under high-load scenarios. It is explained in this section in the documentation.

Seems that flowControl is functional duplicated with the throttling in subscription model. Therefore, this option will not be implemented for now.


[TwigComponent] Poorly formatted deprecation in toolbar

Symfony version(s) affected
6.4-RC
Description
I'm seeing a deprecation error in the toolbar that is poorly formatted

Even in the profiler page, it looks wrong:

The actual error is in vendor/symfony/ux-twig-component/src/DataCollector/TwigComponentDataCollector.php
on line 93, which I imagine will get fixed soon, but a related question is why this deprecation is showing up as it is.
How to reproduce
I can provide a repo if that helps, but at the moment I haven't been able to reproduce it with a simple repo.
(This issue was originally reported at https://github.com/symfony/symfony/issues/52757)

As i said there, i'llfix tonight.
The weird thing is i cannot reproduce myself ...

Could you share the TwigComponent profiler screen ? (in private if needed)

profiler: 6.4-RC1
twig-component v2.13.1

@tacman can you check this PR fixes things ? https://github.com/symfony/ux/pull/1297

I forget how to test another fork/branch!
   "symfony/web-profiler-bundle": "dev-twig-component-profiler-int-float"

 "repositories": {
        "profiler":   {
            "type": "vcs",
            "url": "git@github.com:smnandre/ux.git"
        },

I get
composer update
Loading composer repositories with package information
Restricting packages listed in "symfony/symfony" to "^6.4"
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires symfony/web-profiler-bundle dev-twig-component-profiler-int-float, found symfony/web-profiler-bundle[2.0.7, ..., 2.8.x-dev, v3.0.0-BETA1, ..., 3.4.x-dev, v4.0.0-BETA1, ..., 4.4.x-dev, v5.0.0-BETA1, ..., 5.4.x-dev, v6.0.0-BETA1, ..., 6.4.x-dev, v7.0.0-BETA1, ..., 7.1.x-dev] but it does not match the constraint.
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
even with minimum-stability set to dev.

As UX is on a monorepo, it can be a bit trickier i guess
What i advice you is:
Let's say your app is in /home/your-app
Create a directory outside your app's one
mkdir /home/ux-fix

ChoiceA: If you use the github cli
cd /home/ux-fix
gh repo clone symfony/ux
gh pr checkout 1297

ChoiceB: or if you want to do it manually
Download the source code of the UX monorepo (of my PR)
--> https://github.com/smnandre/ux/archive/refs/heads/fix/twig-component-profiler-int-float.zip
link the symfony UX packages to your vendors
cd /home/ux-fix/ux
php link /home/your-app

test if everything is OK
restore your vendors where they were
php link /home/your-app --rollback

Thanks!  I wasn't familiar with the gh pr checkout command, so much easier than the approach I was trying.
Yep, that fix works:


[Question] Batch size vs Inference throughput

Hi,
I'm hoping to get some advice on speeding up inference throughput. I'm cranking up --batch-size to the maximum possible allowed by my GPU, but am observing that throughput degrades after a point. In the example log below, throughput increases nicely from 8.8 sent/sec to 164 sent/sec as I increased batch-size from 1 to 48. However, for very large batch-sizes like 496, throughput degrades to 34 sent/sec.
batch-size= 1		[INFO:__main__] Processed 1982 lines. Total time: 223.3541, sec/sent: 0.1127, sent/sec: 8.8738
batch-size= 16		[INFO:__main__] Processed 1982 lines. Total time: 17.3007, sec/sent: 0.0087, sent/sec: 114.5619
batch-size= 32		[INFO:__main__] Processed 1982 lines. Total time: 13.5477, sec/sent: 0.0068, sent/sec: 146.2979
batch-size= 48		[INFO:__main__] Processed 1982 lines. Total time: 12.0154, sec/sent: 0.0061, sent/sec: 164.9549
batch-size= 64		[INFO:__main__] Processed 1982 lines. Total time: 13.0415, sec/sent: 0.0066, sent/sec: 151.9768
batch-size= 80		[INFO:__main__] Processed 1982 lines. Total time: 14.6610, sec/sent: 0.0074, sent/sec: 135.1889
batch-size= 96		[INFO:__main__] Processed 1982 lines. Total time: 15.1953, sec/sent: 0.0077, sent/sec: 130.4352
batch-size= 112		[INFO:__main__] Processed 1982 lines. Total time: 21.9354, sec/sent: 0.0111, sent/sec: 90.3560
batch-size= 128		[INFO:__main__] Processed 1982 lines. Total time: 22.2047, sec/sent: 0.0112, sent/sec: 89.2603
batch-size= 144		[INFO:__main__] Processed 1982 lines. Total time: 22.0464, sec/sent: 0.0111, sent/sec: 89.9013
batch-size= 160		[INFO:__main__] Processed 1982 lines. Total time: 22.4970, sec/sent: 0.0114, sent/sec: 88.1008
batch-size= 176		[INFO:__main__] Processed 1982 lines. Total time: 27.4229, sec/sent: 0.0138, sent/sec: 72.2754
batch-size= 192		[INFO:__main__] Processed 1982 lines. Total time: 27.6460, sec/sent: 0.0139, sent/sec: 71.6920
batch-size= 208		[INFO:__main__] Processed 1982 lines. Total time: 27.2893, sec/sent: 0.0138, sent/sec: 72.6292
batch-size= 224		[INFO:__main__] Processed 1982 lines. Total time: 27.8482, sec/sent: 0.0141, sent/sec: 71.1715
batch-size= 240		[INFO:__main__] Processed 1982 lines. Total time: 22.1057, sec/sent: 0.0112, sent/sec: 89.6599
batch-size= 256		[INFO:__main__] Processed 1982 lines. Total time: 35.5982, sec/sent: 0.0180, sent/sec: 55.6770
batch-size= 272		[INFO:__main__] Processed 1982 lines. Total time: 36.2583, sec/sent: 0.0183, sent/sec: 54.6633
batch-size= 288		[INFO:__main__] Processed 1982 lines. Total time: 36.8745, sec/sent: 0.0186, sent/sec: 53.7499
batch-size= 304		[INFO:__main__] Processed 1982 lines. Total time: 37.1267, sec/sent: 0.0187, sent/sec: 53.3847
batch-size= 320		[INFO:__main__] Processed 1982 lines. Total time: 43.5072, sec/sent: 0.0220, sent/sec: 45.5557
batch-size= 336		[INFO:__main__] Processed 1982 lines. Total time: 43.5024, sec/sent: 0.0219, sent/sec: 45.5607
batch-size= 352		[INFO:__main__] Processed 1982 lines. Total time: 43.9264, sec/sent: 0.0222, sent/sec: 45.1210
batch-size= 368		[INFO:__main__] Processed 1982 lines. Total time: 44.6195, sec/sent: 0.0225, sent/sec: 44.4201
batch-size= 384		[INFO:__main__] Processed 1982 lines. Total time: 52.0728, sec/sent: 0.0263, sent/sec: 38.0621
batch-size= 400		[INFO:__main__] Processed 1982 lines. Total time: 52.4995, sec/sent: 0.0265, sent/sec: 37.7528
batch-size= 416		[INFO:__main__] Processed 1982 lines. Total time: 52.4904, sec/sent: 0.0265, sent/sec: 37.7593
batch-size= 432		[INFO:__main__] Processed 1982 lines. Total time: 53.5615, sec/sent: 0.0270, sent/sec: 37.0042
batch-size= 448		[INFO:__main__] Processed 1982 lines. Total time: 41.8074, sec/sent: 0.0211, sent/sec: 47.4078
batch-size= 464		[INFO:__main__] Processed 1982 lines. Total time: 43.0432, sec/sent: 0.0217, sent/sec: 46.0468
batch-size= 480		[INFO:__main__] Processed 1982 lines. Total time: 57.1638, sec/sent: 0.0288, sent/sec: 34.6723
batch-size= 496		[INFO:__main__] Processed 1982 lines. Total time: 57.5007, sec/sent: 0.0290, sent/sec: 34.4691

Using the MXNet profiler, it looks like API calls like MXNDArraySyncCopyToCPU and operators like Concat are taking much more time in the very-large batch-size inference runs. Do you have any advice on how to improve the throughput for larger batch-sizes? Currently I'm running python -m sockeye.translate --batch-size 48 .... without any additional options.
Any tips would be appreciated. Thanks in advance for your help!
Best,
Kevin
ps. Below are some excerpts from the profiler (note timing is different from above since these are different runs):
batch-size=48
[INFO:__main__] Processed 1982 lines. Total time: 16.0220, sec/sent: 0.0081, sent/sec: 123.7045
[INFO:__main__]
Profile Statistics:
        Note the difference in units for different entries.
 Total time: 31.6795, sec/sent: 0.0160, sent/sec: 62.5641
[INFO:__main__]
Profile Statistics:
        Note the difference in units for different entries.
 To get that plus other potentially useful info you could run Mxnet diagnostics:
curl --retry 10 -s https://raw.githubusercontent.com/apache/incubator-mxnet/master/tools/diagnose.py | python3

By the way, great analysis of the problem!

Thanks! I'm using Sockeye version 2.3.10. Feb 5, 2021 commit: https://github.com/awslabs/sockeye/commit/c3870e38f0a446ae5bf3920d5872908d282444d4
Here's the output of diagnose.py:
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                40
On-line CPU(s) list:   0-39
Thread(s) per core:    2
Core(s) per socket:    10
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 85
Model name:            Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz
Stepping:              4
CPU MHz:               2200.000
BogoMIPS:              4400.00
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              1024K
L3 cache:              14080K
NUMA node0 CPU(s):     0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38
NUMA node1 CPU(s):     1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb cat_l3 cdp_l3 intel_ppin intel_pt ssbd mba ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts pku ospke spec_ctrl intel_stibp flush_l1d
----------Python Info----------
Version      : 3.6.13
Compiler     : GCC 7.3.0
Build        : ('default', 'Feb 23 2021 21:15:04')
Arch         : ('64bit', '')
------------Pip Info-----------
Version      : 21.0.1
Directory    : /home/...(username).../.conda/envs/sockeye2/lib/python3.6/site-packages/pip
----------MXNet Info-----------
Version      : 1.7.0
Directory    : /home/...(username).../.conda/envs/sockeye2/lib/python3.6/site-packages/mxnet
Commit Hash   : 64f737cdd59fe88d2c5b479f25d011c5156b6a8a
64f737cdd59fe88d2c5b479f25d011c5156b6a8a
64f737cdd59fe88d2c5b479f25d011c5156b6a8a
64f737cdd59fe88d2c5b479f25d011c5156b6a8a
64f737cdd59fe88d2c5b479f25d011c5156b6a8a
64f737cdd59fe88d2c5b479f25d011c5156b6a8a
64f737cdd59fe88d2c5b479f25d011c5156b6a8a
64f737cdd59fe88d2c5b479f25d011c5156b6a8a
64f737cdd59fe88d2c5b479f25d011c5156b6a8a
64f737cdd59fe88d2c5b479f25d011c5156b6a8a
Library      : ['/home/...(username).../.conda/envs/sockeye2/lib/python3.6/site-packages/mxnet/libmxnet.so']
Build features:
✔ CUDA
✔ CUDNN
✔ NCCL
✔ CUDA_RTC
✖ TENSORRT
✔ CPU_SSE
✔ CPU_SSE2
✔ CPU_SSE3
✔ CPU_SSE4_1
✔ CPU_SSE4_2
✖ CPU_SSE4A
✔ CPU_AVX
✖ CPU_AVX2
✔ OPENMP
✖ SSE
✔ F16C
✖ JEMALLOC
✔ BLAS_OPEN
✖ BLAS_ATLAS
✖ BLAS_MKL
✖ BLAS_APPLE
✔ LAPACK
✔ MKLDNN
✔ OPENCV
✖ CAFFE
✖ PROFILER
✔ DIST_KVSTORE
✖ CXX14
✖ INT64_TENSOR_SIZE
✔ SIGNAL_HANDLER
✖ DEBUG
✖ TVM_OP
----------System Info----------
Platform     : Linux-3.10.0-862.11.6.el7.x86_64-x86_64-with-centos-7.5.1804-Core
system       : Linux
node         : mynode
release      : 3.10.0-862.11.6.el7.x86_64
version      : #1 SMP Tue Aug 14 21:49:04 UTC 2018
----------Hardware Info----------
machine      : x86_64
processor    : x86_64
----------Network Test----------
Setting timeout: 10
Timing for MXNet: https://github.com/apache/incubator-mxnet, DNS: 0.0053 sec, LOAD: 0.2918 sec.
Timing for Gluon Tutorial(en): http://gluon.mxnet.io, DNS: 0.0126 sec, LOAD: 0.1466 sec.
Error open Gluon Tutorial(cn): https://zh.gluon.ai, <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)>, DNS finished in 0.02597522735595703 sec.
Timing for FashionMNIST: https://apache-mxnet.s3-accelerate.dualstack.amazonaws.com/gluon/dataset/fashion-mnist/train-labels-idx1-ubyte.gz, DNS
: 0.0187 sec, LOAD: 0.3718 sec.
Timing for PYPI: https://pypi.python.org/pypi/pip, DNS: 0.0099 sec, LOAD: 0.1934 sec.
Error open Conda: https://repo.continuum.io/pkgs/free/, HTTP Error 403: Forbidden, DNS finished in 0.00069427490234375 sec.
----------Environment----------
OMP_NUM_THREADS="1"

Thanks for all the details, Kevin!
I'm afraid I don't have too many suggestions. Do you set the --chunk-size parameter which determines the amount of data that is read in and sorted to create batches?  If not I wonder whether increasing it has any effect on larger batch sizes.
I'm not 100% sure but MXNDArraySyncCopyToCPU taking long may be an indirect affect of the asynchronous nature of calling operations, similar to how asnumpy usually shows up as taking a lot of time as it is the synchronisation point that requires waiting for all previous operations that had been submitted  asynchronously.
The Concat operator taking such a long time on the other hand is certainly concerning and maybe worth looking into.

I'm not sure how to investigate the Concat operator, but I did experiment with chunk-size a bit. Previously I didn't set the --chunk-size parameter, so it defaults to 500xbatch_size. I tried increasing this value to 1000xbatch_size, 2000xbatch_size, etc. but it didn't change inference time much. (For my small test set of ~2000 sentences, increasing chunk-size further wouldn't matter much, but I've also confirmed this result on much larger test sets). Reducing it so that chunk-size = batch_size did slow down total inference time, as expected.
That said, for the larger test set, the degradation in throughput didn't seem as stark. (Previously for the smaller test set, throughput dropped from 164 sent/sec for batch-size=48 to 34 sent/sec for batch-size=496.) Below the throughput drop is less severe (these runs use chunk-size=500xbatch_size and I'm not reporting the different chunk-size results because they don't vary much):
batch-size= 16		[INFO:__main__] Processed 169178 lines. Total time: 1522.8703, sec/sent: 0.0090, sent/sec: 111.0915
batch-size= 48		[INFO:__main__] Processed 169178 lines. Total time: 834.4161, sec/sent: 0.0049, sent/sec: 202.7502
batch-size= 80		[INFO:__main__] Processed 169178 lines. Total time: 828.2768, sec/sent: 0.0049, sent/sec: 204.2530
batch-size= 112		[INFO:__main__] Processed 169178 lines. Total time: 989.3987, sec/sent: 0.0058, sent/sec: 170.9907
batch-size= 144		[INFO:__main__] Processed 169178 lines. Total time: 965.6615, sec/sent: 0.0057, sent/sec: 175.1939
batch-size= 176		[INFO:__main__] Processed 169178 lines. Total time: 937.7360, sec/sent: 0.0055, sent/sec: 180.4111
batch-size= 208		[INFO:__main__] Processed 169178 lines. Total time: 1024.1092, sec/sent: 0.0061, sent/sec: 165.1953
batch-size= 240		[INFO:__main__] Processed 169178 lines. Total time: 1011.7889, sec/sent: 0.0060, sent/sec: 167.2068
batch-size= 272		[INFO:__main__] Processed 169178 lines. Total time: 968.1724, sec/sent: 0.0057, sent/sec: 174.7395
batch-size= 304		[INFO:__main__] Processed 169178 lines. Total time: 1180.9515, sec/sent: 0.0070, sent/sec: 143.2557
batch-size= 336		[INFO:__main__] Processed 169178 lines. Total time: 1165.3356, sec/sent: 0.0069, sent/sec: 145.1753
batch-size= 368		[INFO:__main__] Processed 169178 lines. Total time: 1137.2546, sec/sent: 0.0067, sent/sec: 148.7600
batch-size= 400		[INFO:__main__] Processed 169178 lines. Total time: 1120.8494, sec/sent: 0.0066, sent/sec: 150.9373
batch-size= 432		[INFO:__main__] Processed 169178 lines. Total time: 949.7257, sec/sent: 0.0056, sent/sec: 178.1335
batch-size= 464		[INFO:__main__] Processed 169178 lines. Total time: 954.9413, sec/sent: 0.0056, sent/sec: 177.1606

@tdomhan & @bricksdont - thanks for the various tips so far! I'll do some more experimentation on my side. It's fine to close this issue; I'll let you know again if I find anything interesting. I'll also look into other methods for speeding up inference, such as low-precision computation and model distillation.

Thanks for the update! I will close the issue for now, but feel to reopen with further findings!


Smart BMS JK-PB2A16S-20P extra settings required

Is the Smart BMS JK-PB2A16S-20P with Active Balancer supported by this integration? This is the new model that talks to inverters.
https://www.jkbms.com/product/jk-pb2a16s20p-jk-pb2a16s-20p/

It might work. Let me know if you try it. There is no risk of harm.

Just to confirm that it works but I see the following only:

Would it be possible to add/update the following:

Would like to see toggle buttons for balance and float mode, like for charge/discharge
Temp sensors 3 and 4 are missing, only 1 and 2 showing

Just to confirm that it works but I see the following only:  Would it be possible to add/update the following:

Would like to see toggle buttons for balance and float mode, like for charge/discharge
Temp sensors 3 and 4 are missing, only 1 and 2 showing

JKBMS FW is v14.17

Hello,
Can you walk me through this setup? MQTT Broker finds the inverter, but i am not able to populate any of the info

I've added the other 2 temperature sensors.
@silviudc What is float mode? Can you post a screenshot of the app screen with that button?

@fl4p The same problem here. It would be perfect to have a "Float Mode" switch in Home Assistant. All the other settings work perfectly!

float_charge.patch
Maybe it will be useful for someone. Made a small patch that adds a "Float Charge" switch for the JKBMS PBx series. Personally, I need this switch for correct automation in Home Assistant. Use only at your own risk, since I do not know how this change will work for other JK BMS boards. My BMS is PB2A16S20P v15.24


remove more duplication in menus #431

Codecov Report

Merging #497 into master will increase coverage by 0.66%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #497      +/-   ##
==========================================
+ Coverage   89.62%   90.29%   +0.66%
==========================================
  Files          47       39       -8
  Lines        3567     2967     -600
==========================================
- Hits         3197     2679     -518
+ Misses        370      288      -82

Impacted Files
Coverage Δ

vent/menu.py
81.31% <100%> (ø)
:arrow_up:

vent/menus/tools/tool_forms.py
100% <100%> (ø)
:arrow_up:

vent/menus/tools/tools.py
95% <0%> (ø)
: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 ee9bae4...6a30127. Read the comment docs.


Use project minSdkVersion and default to 16

Current build is failing with the following error:
Error:
        uses-sdk:minSdkVersion 16 cannot be smaller than version 21 declared in library [com.facebook.react:react-native:0.66.5]

This MR simply allows to set the minSdkVersion from the project root

This will be modified from version 1.9.0


View More

View more is not appearing on my blog, Help

@Dru-Go please explain your issue!

I wanted the instant view to appear on the telegram desktop apps, but now i can see that the feature is just for mobile apps

Yes

I wanted the instant view to appear on the telegram desktop apps, but now i can see that the feature is just for mobile apps

Yes! Sadly this feature is not available on Telegram Desktop yet! We sincerely apologize for this misfortune accident.
Please do open this issue on https://github.com/telegramdesktop/tdesktop, since our library can't do anything about it, thanks.


Adding audio streaming and better definitions of all the sub commands that are available

Something that would really make this project shine is the ability to add audio along with the video source, this way full microphone and video setups could run just off the raspberry pi! This might be a bit much to request but if its possible I bet it would be a great addition.
Another feature could be the ability to see all the config options or pass options in the command line. The changelog shows that you can add config parameters but doesn't say where.

Agreed on the audio - that would make a nice addition. I don't currently have any audio capture equipment for the Raspberry Pi, and as such can't test this. Perhaps it's something I'll look at when I have an audio capture card. In the mean time, feel free to have a crack at it and raise a PR for it!
For the config options, see the example configuration file raspindi.conf.default. This details all the options that are available.

For the config options, see the example configuration file raspindi.conf.default. This details all the options that are available.

Thanks! I cant find this in the already compiled code on my pi, must be something I have to change before building. maybe in the future adding a way to pass arguments via the command line before starting the service would be a good feature to have.
thanks for the quick reply!

They're read when the program executes. The file is found in /etc/raspindi.conf on a live system.

Oh I see now, thanks!


Hasmany

wrapping this dev effort up as impl for story
2408

abandoning this.  changes were merged by PR #19


implement covid business rule verification

I have a pending commit which passes all the test cases.
What’s missing is a good source for country rules. I asked around regarding sources in https://github.com/eu-digital-green-certificates/dgc-participating-countries/issues/10#issuecomment-891236663

I could give you the Belgian rules if you want :)

Thank you for the offer! Are you talking about a publically accessible Belgian rule source that the coronaqr package/program could query? We need a live source, not a one-time snapshot for any country’s rules to be useful :)

If you want I commit to provide that resource. In what format should it be delivered?
At the moment these are the rules:
If you are vaccinated twice, you are allowed if your last vaccine was 2 weeks ago
If you have a negative CRT test, you are allowed up to 48h after the certificate has been issued
If you have a negative RAT test, you are allowed up to 24h after the certificate has been issued
If you have a "recovery certificate" you are allowed it is was issued 11 days ago, but not longer than 180 days after your positive CRT test.

The format is certlogic as specified in https://github.com/ehn-dcc-development/dgc-business-rules, see https://github.com/eu-digital-green-certificates/dgc-business-rules-testdata/blob/main/FR/VR-FR-0004/rule.json for an example from France.
The Belgian government is supposed to provide these rules expressed in certlogic somewhere, if I understand correctly. Do you have a Belgian open-source corona app? That would be a good place to check first.
I don’t see a BE directory in https://github.com/eu-digital-green-certificates/dgc-business-rules-testdata yet, which is a bit surprising. Perhaps whoever is responsible for maintaining the Belgian certlogic rules can submit them into the dgc-business-rules-testdata repository as a pull request?


[tsserver] Format command ignores "options" argument

TypeScript Version: 2.2.0-dev.20170108
Code
Sending the following command to tsserver:
{
  "line": 1,
  "offset": 1,
  "endLine": 81,
  "endOffset": 1,
  "options": {
    "indentSize": 2,
    "tabSize": 2
  },
  "file": "/source.ts"
}

Expected behavior:
Expect the file to be formatted using 2 spaces for indentation.
Actual behavior:
The project indentation settings are used instead (defaults to 4 spaces).

Going to assume this has been fixed by now or was user error. Please refile with a more complete repro otherwise. Thanks!


Nuget is not fable compatible

Hi @tforkmann it seems that the nuget package doesn't include any Fable sources which means it will break when installed from a project

You need to include the sources using
<ItemGroup>
    <Content Include="*.fsproj; *.fs; *.js;" Exclude="**\*.fs.js" PackagePath="fable\" />
</ItemGroup>

Also the dependency should be a non-dev dependency so you can remove DevDependency="true" from the femto metadata
Also this packages take too many nuget packages as dependencies

You only need Feliz as a dependency (update paket.references to only require Feliz).
Preferably the target framework can be netstandard2.0 for maximum compatibility with Fable projects that aren't using dotnet 5.0

Hi Zaid,
will try to fix over the weekend!
Best,
Tim

Should be fine now.

Closing with 7e22576