Reprocess attestations

Is your feature request related to a problem? Please describe.
Right now when an (unaggregated) Attestation or AggregateAndProof are ignored until the voted block reach the node and gets processed
Jan-03 02:14:14.116 [NETWORK]         debug: gossip - beacon_attestation - ignore slot=2055371, subnet=17, index=17, code=ATTESTATION_ERROR_UNKNOWN_BEACON_BLOCK_ROOT, root=0x7c8054d7137308f036d977d796a9bff70cea774efb275f7eb3c4b0d7c5600cdb
Jan-03 02:14:14.116 [NETWORK]         debug: gossip - beacon_attestation - ignore slot=2055371, subnet=12, index=12, code=ATTESTATION_ERROR_UNKNOWN_BEACON_BLOCK_ROOT, root=0x7c8054d7137308f036d977d796a9bff70cea774efb275f7eb3c4b0d7c5600cdb
Jan-03 02:14:14.117 [NETWORK]         debug: gossip - beacon_attestation - ignore slot=2055371, subnet=36, index=36, code=ATTESTATION_ERROR_UNKNOWN_BEACON_BLOCK_ROOT, root=0x7c8054d7137308f036d977d796a9bff70cea774efb275f7eb3c4b0d7c5600cdb
Jan-03 02:14:14.663 [CHAIN]         verbose: Block processed slot=2055371, root=0x7c8054d7137308f036d977d796a9bff70cea774efb275f7eb3c4b0d7c5600cdb

Describe the solution you'd like

We should be able to cache and reprocess them.
Make sure we don't have performance issue with this
Make sure the cache is properly bounded

The best way to test is to confirm this error code ATTESTATION_ERROR_UNKNOWN_BEACON_BLOCK_ROOT rarely happens

In a node which subscribe to all subnets, contabo server, this happened a lot
grep -e "UNKNOWN" -rn beacon*.log | wc -l
40026990

however in mainnet node with a stronger machine and 39 connected validators, the result is way lower
grep -e "UNKNOWN" -rn beacon*.log | wc -l
1691073


Add Aliases for Amazon Echo Dot 3 & 4

Hi,
I kept track of the releases and heard Amazon Echo deices were supported - yay. However, after trying and trying I found out that the IDs are different when not using the official integration. There's a popular unofficial version (free) that is available on HACS but those use a different ID.
I added both the aliases as I have both devices in HA. Repo for custom component is: https://github.com/custom-components/alexa_media_player

@wranglatang @Mirabis @sockmonkey0223
There are also two other issues created where there are other model ID's referenced.
Let's also resolve that in this PR.
See #1568 and #1569
C78MP8 seem to be model id for Gen3 (In the original PR D91029T)
I cannot find anything in Google for D91029T, so I don't know where you got that model id from @wranglatang.
B7W644 for Gen4 (in the original PR B7W64E)
Only difference here seems to be the color, so B7W644 can be added as alias as well. @Mirabis Can you add that?

I just read the Model ID off the bottom of the device but i have recently noticed that when using the unofficial Alexa Media Player integration the model ID's are different. Seems like we have a few different options
Gen 3:

D91029T - Bottom of Device
ECHO A32DOYMUN6DTXA - Alexa Media Player Integration
C78MP8 - Not sure where this has come from

Gen 4:

B7W64E - Bottom of Device
ECHO A2U21SRK4QGSE1 - Alexa Media Player
B7W644 - Not sure where this has come from

I just read the Model ID off the bottom of the device but i have recently noticed that when using the unofficial Alexa Media Player integration the model ID's are different. Seems like we have a few different options
Gen 3:

D91029T - Bottom of Device
ECHO A32DOYMUN6DTXA - Alexa Media Player Integration
C78MP8 - Not sure where this has come from

Gen 4:

B7W64E - Bottom of Device
ECHO A2U21SRK4QGSE1 - Alexa Media Player
B7W644 - Not sure where this has come from

Here is my Gen 3 Echo DOT Charcoal:

C78MP8 - Bottom of device
ECHO A1RABVCI4QCIKC - Alexa Media Player

My Gen 4 Echo DOT Glacier White:

B7W64E - Bottom of device
ECHO A2U21SRK4QGSE1 - Alexa Media Player

Hmm okay, so looks like different models for different colours -_- Maybe its best to just have the model as Gen3 & Gen4 and then the user just selects that in the GUI or code.

My Black Echo Dot 4 (B7W64E) shows up as A2U21SRK4QGSE1 in the integration;
@sockmonkey0223's Glacier White (B7W64E) Echo Dot 4 shows up as A2U21SRK4QGSE1 in the integration.

Those are identical, so most likely the model doesn't change for colour but for features. The version with clock has B7W644, other variants may have other IDs as well. Echo Plus Gen 2 reports as ALEGCNGL9K0HM for instance.
@bramstroker  I've updated the PR for the specified issues and double checked the ID's in the other repo. More aliases should be added later on, but I do not have all the device types nor time (at the moment) to dig through the logs people post on the custom integration.

Thanks. Looks fine like this. Think we can merge.
Btw you don't have to touch supported_models.md next time. That will be autogenerated, so you can save time.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.003%) to 98.34%

Files with Coverage Reduction
New Missed Lines
%

custom_components/powercalc/discovery.py
2
98.48%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
2785

Relevant Lines:
2832

💛  - Coveralls


Whats up with Akatarawa crustal ruptures

With scriptCrustalInversionRunner example running NZ CFM crustal data we see rupture permutations grow exponentially as the maxDistance parameter increases above 0.25 (km).
Further investigation is needed to understand what's behind this, and to compare this with the StandaloneRuptureGen approach used before the Ucerf3 refactoring in July. In this case, minDistance wqas set to 0.5km and much smaller rupture sets were produced. FYI @mcg-gns
Todo

[x] refactor (add filter) to focus on 'akatarawa' faults
[x] scale minDistance between 0.2 and 0.5 capturing outputs

Notes on filtering Akatarawa ruptures
In an effort to reduce memory consumption and to focus on the root causes I wrote a small parent Section ID plausablity filter filter class.
This will discard any ruptures that do not include parent  section ID from the passed in list. In this akatarawa case, with only a single parent fault section the list was just [2].
A new feature was added to opensha-ucerf3/ support this filter.
It turns out this filter doesnt' appear to have much impact on memory requirements during the rutpure building. It has been  useful for subsequent debugging efforts.

Diagnostic strategies
The following have been discussed with Matt, Russ, Kiran, Lizzie

Discard small ruptures using existing filters (minSections >2 could be minSections >100) could workaround memory issues and provide insights to the large problematic ruptures.
Status Parked as a) the filter doesn't actually exist, and b) it may not actually work based as memory issues may not be alleviated much by discarding?

Histogram analysis to find sections participation rate, since this is a "needed feature" anyway.
Status Parked as I'm not clear how we can use this to hone in on our root cause.

Diagnostic logging along with configurations to print information about which jumps cause the Akatarawa rupture to explode. This has been useful , see below.

Diagnostic logging findings for Akatarawa
With maxDistance set to either 0.2 or 0.25,  our outputs are identical with 94 ruptures after processing the Akatarawa cluster, and a grand total of 702 ruptures involving the Akatarawa fault section when all fault sections are processed:
Have 94 ruptures after processing cluster 2: Akatarawa
Have 254 ruptures after processing cluster 277: Moonshine
Have 323 ruptures after processing cluster 377: Otaki Forks 1
Have 440 ruptures after processing cluster 378: Otaki Forks 2
Have 472 ruptures after processing cluster 635: Wellington Hutt Valley 1
Have 512 ruptures after processing cluster 636: Wellington Hutt Valley 2
Have 544 ruptures after processing cluster 637: Wellington Hutt Valley 3
Have 600 ruptures after processing cluster 638: Wellington Hutt Valley 4
Have 656 ruptures after processing cluster 639: Wellington Hutt Valley 5
Have 702 ruptures after processing cluster 668: Whitemans Valley

using config...
-fsdFile ./data/FaultModels/DEMO2_crustal_opensha.xml
-o /tmp
-maxFaultSections 1200
-skipFaultSections 0
-maxLength 0.5
-maxDistance 0.2
-inversionMins 1
-syncInterval 5
-runInversion false
-faultIdIn 2

Here we see output from some diagnostic logging that prints jump information as ruptures are evaluated. (TODO commit  & link to relevant code here).
This logging is not exhaustive, but it provides insight into where the geometries are allowing jumps to occur.
maxDistance set to 0.25
Here the cluster is completed, and processing moves on
Have 0 ruptures after processing cluster 1: Ahuriri River
New largest rup has 10 subsections with 6 jumps and 0 splays. 4 rups in total
	Rupture jump:2[14]=>638[3734], 0.008 km ; from Akatarawa, Subsection 0 to Wellington Hutt Valley 4, Subsection 0
	Rupture jump:638[3734]=>668[3894], 0.123 km ; from Wellington Hutt Valley 4, Subsection 0 to Whitemans Valley, Subsection 2
	Rupture jump:668[3894]=>277[1807], 0.137 km ; from Whitemans Valley, Subsection 2 to Moonshine, Subsection 2
	Rupture jump:277[1805]=>2[15], 0.000 km ; from Moonshine, Subsection 0 to Akatarawa, Subsection 1
	Rupture jump:2[15]=>377[2331], 0.000 km ; from Akatarawa, Subsection 1 to Otaki Forks 1, Subsection 0
	Rupture jump:377[2332]=>378[2335], 0.000 km ; from Otaki Forks 1, Subsection 1 to Otaki Forks 2, Subsection 2
Have 94 ruptures after processing cluster 2: Akatarawa

maxDistance set to 0.275
on my dev system I run out of memory before the the Akatarawa cluster is processed, but the diagnostic output is interesting..
New largest rup has 280 subsections with 32 jumps and 0 splays. 2297 rups in total

Rupture jump:2[14]=>638[3734], 0.008 km ; from Akatarawa, Subsection 0 to Wellington Hutt Valley 4, Subsection 0
Rupture jump:638[3734]=>668[3894], 0.123 km ; from Wellington Hutt Valley 4, Subsection 0 to Whitemans Valley, Subsection 2
Rupture jump:668[3894]=>277[1807], 0.137 km ; from Whitemans Valley, Subsection 2 to Moonshine, Subsection 2
Rupture jump:277[1807]=>341[2134], 0.253 km ; from Moonshine, Subsection 2 to Ohariu Central, Subsection 3
Rupture jump:341[2134]=>344[2142], 0.011 km ; from Ohariu Central, Subsection 3 to Ohariu South 3, Subsection 3
Rupture jump:344[2139]=>343[2138], 0.000 km ; from Ohariu South 3, Subsection 0 to Ohariu South 2, Subsection 1
Rupture jump:343[2137]=>342[2136], 0.000 km ; from Ohariu South 2, Subsection 0 to Ohariu South 1, Subsection 1
Rupture jump:342[2135]=>623[3667], 0.174 km ; from Ohariu South 1, Subsection 0 to Wairau 3, Subsection 0
Rupture jump:623[3668]=>622[3664], 0.000 km ; from Wairau 3, Subsection 1 to Wairau 2, Subsection 0
Rupture jump:622[3666]=>621[3650], 0.000 km ; from Wairau 2, Subsection 2 to Wairau 1, Subsection 0
Rupture jump:621[3663]=>624[3669], 0.000 km ; from Wairau 1, Subsection 13 to Wairau A, Subsection 0
Rupture jump:624[3675]=>27[195], 0.121 km ; from Wairau A, Subsection 6 to Alpine Springs Junction to Tophouse, Subsection 0
Rupture jump:27[209]=>24[141], 0.000 km ; from Alpine Springs Junction to Tophouse, Subsection 14 to Alpine Kaniere to Springs Junction, Subsection 0
Rupture jump:24[153]=>159[1051], 0.087 km ; from Alpine Kaniere to Springs Junction, Subsection 12 to Hope Taramakau, Subsection 5
Rupture jump:159[1046]=>197[1320], 0.000 km ; from Hope Taramakau, Subsection 0 to Kelly, Subsection 9
Rupture jump:197[1316]=>61[405], 0.189 km ; from Kelly, Subsection 5 to Browning Pass, Subsection 5
Rupture jump:61[405]=>24[154], 0.123 km ; from Browning Pass, Subsection 5 to Alpine Kaniere to Springs Junction, Subsection 13
Rupture jump:24[158]=>197[1311], 0.000 km ; from Alpine Kaniere to Springs Junction, Subsection 17 to Kelly, Subsection 0
Rupture jump:197[1311]=>23[140], 0.000 km ; from Kelly, Subsection 0 to Alpine Jacksons to Kaniere, Subsection 39
Rupture jump:23[133]=>626[3681], 0.062 km ; from Alpine Jacksons to Kaniere, Subsection 32 to Waitaha, Subsection 0
Rupture jump:626[3685]=>292[1887], 0.125 km ; from Waitaha, Subsection 4 to Mungo, Subsection 0
Rupture jump:292[1889]=>225[1496], 0.260 km ; from Mungo, Subsection 2 to Lord Range, Subsection 0
Rupture jump:225[1503]=>23[130], 0.181 km ; from Lord Range, Subsection 7 to Alpine Jacksons to Kaniere, Subsection 29
Rupture jump:23[127]=>293[1892], 0.157 km ; from Alpine Jacksons to Kaniere, Subsection 26 to Murchison 1 - Ice Lake, Subsection 0
Rupture jump:293[1899]=>493[3029], 0.093 km ; from Murchison 1 - Ice Lake, Subsection 7 to Straight Creek, Subsection 1
Rupture jump:493[3028]=>55[360], 0.251 km ; from Straight Creek, Subsection 0 to Black Blob - Haast Ridge, Subsection 4
Rupture jump:55[356]=>23[123], 0.249 km ; from Black Blob - Haast Ridge, Subsection 0 to Alpine Jacksons to Kaniere, Subsection 22
Rupture jump:23[101]=>25[173], 0.000 km ; from Alpine Jacksons to Kaniere, Subsection 0 to Alpine Milford to Jacksons, Subsection 14
Rupture jump:25[159]=>22[100], 0.000 km ; from Alpine Milford to Jacksons, Subsection 0 to Alpine Caswell to Milford, Subsection 14
Rupture jump:22[86]=>26[194], 0.000 km ; from Alpine Caswell to Milford, Subsection 0 to Alpine Resolution, Subsection 20
Rupture jump:26[174]=>124[776], 0.000 km ; from Alpine Resolution, Subsection 0 to Fiordland, Subsection 0
Rupture jump:124[847]=>51[342], 0.000 km ; from Fiordland, Subsection 71 to Barn, Subsection 9

!! OutOfMemory

@andy22b @rvd-gns @mcg-gns @willic3 can you see any distances here that are obviously incorrect??
I could hone in on 3D visualisations if I knew what was most suspicious in here.
Matt's suggested a possible calculation error in the opensha code so this might help us find some good test cases.
I guess it's also possible that something in our CFM data or transforms is wrong, i.e perhaps incorrect dips and or depths could make these distances possible?

@kevinmilner @mcg-gns cc'ing you on this issue and also #31.
I suspect they're related as this testing is being done without any azimuth filtering in place and this table shows it has a big impact...

new support and tests added for these essential filters - yay!


Use page/chapter in another shelf without having to move the entire book

Describe the feature you'd like
We're treating each business unit and customers as a shelf (i.e. Operations, Delivery, Hosting, Client information), with a book = technology (Network, security, O365, etc), and  chapters = sub topics and pages = the how to guides.
Operations (shelf) > Network (book) > Routing (chapter) > Page (how to guide for specific issue). This structure works fine for general wiki. However, struggling to add customer specific information under this section  from  "Clients" shelf.
Ideally would like to be able to share page/chapter across - without having to move the entire book.  What we'd like is to be able to add customer specific information into  a different shelf/book.
Describe the benefits this would bring to existing BookStack users
Ability to relate information across different shelves. Provides the ability for the user to quickly see specific information
Can the goal of this request already be achieved via other means?
We've tried playing around with tags and templates, but it doesn't work as well with what we're trying to achieve.
Have you searched for an existing open/closed issue?

[X] I have searched for existing issues and none cover my fundamental request

How long have you been using BookStack?
Under 3 months
Additional context
No response

Thanks for the request @sdutt593.
Related to #1036, #1360 and #182. If this does not evolve in discussion, I may close this in favor of re-opening #1036 since that reflects prior support.

We've tried playing around with tags and templates, but it doesn't work as well with what we're trying to achieve.

Can you explain why tags fell short for your use-case?
Knowing this may help plan an upgrade of tags to suit your needs rather than a more complex change to shelves.

Just want to be able to embed various pages from different books on different shelves.

Sure, but could you explain why? What is the use case, and what is the general goal? Or what is the value in achieving this?
Right now you're asking for a specific technical implementation/solution to a problem, but I don't understand the core problem, which I'd like to know to help me explore potential alternatives.

This is so we can have a general area and customer specific area  under Operations (shelf). For the team to view it in one place, rather than navigating to different shelf.
Embedding pages from different books will help have the relevant information grouped under one area.
Customer specific how to guides can sit within customer shelf, but having these pages referenced under Operations shelf in the specific area (i.e. Operations > Network > Routing > Asymmetric routing causing voice issue for Customer XYZ)

Thanks for the info @sdutt593.
As a follow-up,  what's currently lacking from tag searches for this use-case? Compared to the idea of mixed content in shelves.

Tags work, when we search, the specific information pops up. It's just we would like to have mixed context in shelves

Sure, I totally get that, but I'm just wondering why. What is is about shelves that that make you desire this functionality there, compared to tag searches?

We want to be able to access to relevant shelves to appropriate teams. I.e. Operations team will have access to Operations shelf, customer shelf, etc. Whereas the hosting team will not have access to Operations shelf.
This way we can display relevant/specific information to the appropriate audience/team


Remove all references to Test1 on backend: BEGINNER ~ 10 minutes

Delete Test1 class
Delete anything in BlindCsApplication class except for

public static void main(String[] args) {
        SpringApplication.run(BlindcsApplication.class, args);
}

Hello,
I'd like to contribute to this
can I have it assigned to me

Yep, feel free to assign yourself any issues you would like to contribute on

Ok thank You.


clean up various things related to e2e testing

use /usr/bin/env to select bash on mac this allows me to install a newer bash version which gets picked up
don't build fat images for e2e testing
fix e2e script

Fixes: https://github.com/knative-sandbox/net-contour/issues/638.

/retest


Publish testing packages.

Scope
Upload testing packages to fix #9.
Changes
Used public SFTPPlus instance to add an HTTPS service named Bin Chevah, using a bin user rooted in /srv/sftpplus-bin, with the following rights: allow-list, allow-traverse, allow-create-folder, allow-write, allow-rename.
A batch file is generated after building the dist file, to be uploaded through OpenSSH's sftp. New sub-dirs (such as ubuntu2204/x64) are created as needed.
Drive-by changes:

Added .gitattributes to fix #3.
Use the more standard short git ID for packages.
Added ngrok-based debugging for Windows runners.
Removed malfunctioning skip-ci steps.
Removed the uploading of artifacts.

Testing
Please review changes.
Check the automated tests.
Download testing packages from https://bin.chevah.com:20443/testing/python/.
Use them in brink.conf to get a Python 3 runtime?

But is this a real problem? :-] If yes, we could easily fix it with a repo secret…

Well... we used the different port for security by obscurity ... if we make the port public we are no longer "protected"  by obscurity :)
Great that this was moved to SFTPPlus :)

Well... we used the different port for security by obscurity ... if we make the port public we are no longer "protected" by obscurity :)

Yes, there's a bit of security through obscurity. But for me changing default SSH port is more of a thing of convenience. The main purpose being to substantially reduce the number of probes that pollute SSH logs.

For some reason, packages uploaded through GitHub actions are not using the latest commit id…
E.g. for the current last commit, instead of naming the package python-<IP_ADDRESS>3ec187-ubuntu2004-x64.tar.gz, it is named python-<IP_ADDRESS>429be3-ubuntu2004-x64.tar.gz.
Any ideas?

Hhmm, this is still present: Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.

No more warnings from SFTP through including the host fingerprint for the current IP for bin.chevah.com. Turned on StrictHostKeyChecking too while at it.
Also, git commits are the same no matter if you build the package locally or through GitHub Actions. However, bumping for the nth time into the 8 vs. 7 digits for the short git ID, I have reverted to the standard short 7 digits one. This also fits with what you see in GitHub's web interface.

Surprisingly for how little changes there are, this was quite hard to get right, as you can guess from the amount of commits above. :-]

Maybe also enable full directory (or at least traversal) for https://bin.chevah.com:20443/testing/python/ and https://bin.chevah.com:20443/testing/python/ubuntu2004

allow_traverse is enabled for user bin, as documented in the PR text. What exactly is to be improved?

we also need to enable a read-only theme for the public account... but this is something for salt-master ...and maybe improve the configuration in SFTPPlus

What is a read-only theme? And why is that a problem? (Again, honest questions.)
[…]
I'll add an issue for publishing production packages. Don't know what would be best at the moment…

https://bin.chevah.com:20443/testing/python/ubuntu2004

When I go there, I get an empty page and not the listing with x64 folder visible.

What is a read-only theme? And why is that a problem?

A read-only theme as a GUI theme in which all the delete file / upload file / create folder buttons are hidden.
It's not a big problem... but those buttons have no usage...and we have customers asking for this feature.

Thanks for the update. Nice work :)

https://bin.chevah.com:20443/testing/python/ubuntu2004

When I go there, I get an empty page and not the listing with x64 folder visible.

OK, I see the difference now, thanks! But what permissions would allow that to work alongside https://bin.chevah.com:20443/testing/python/ubuntu2004/ (with an ending /)?
Current list is allow-list, allow-traverse, allow-create-folder, allow-write, allow-rename. I've tried adding allow-read, but it didn't help. The remaining ones seem unrelated, except maybe allow-full-control, which is out of the question.
On a related note, I've noticed the files can be overwritten by the user bin over SFTP. So I'm not sure in what way they are protected by excluding allow-delete-file anyway… :-]

What is a read-only theme? And why is that a problem?

A read-only theme as a GUI theme in which all the delete file / upload file / create folder buttons are hidden.
It's not a big problem... but those buttons have no usage...and we have customers asking for this feature.

OK, I've realized this also at some point yesterday. It doesn't bother me, specifically because the main use case is for the files to be downloaded with wget/curl.
But yes, it would be nice if this would work akin to FTP anonymous access or a simple HTTP listing of files. Now you are shown as Logged in as bin and capable of uploading stuff when simply accessing https://bin.chevah.com:20443/testing/python/ubuntu2004/.
Combining this with the "related note" above, you can anonimously overwrite any file by simply uploading another file with the same name.

OK, I see the difference now, thanks! But what permissions would allow that to work alongside https://bin.chevah.com:20443/testing/python/ubuntu2004/ (with an ending /)?

Good question.... I don't think there is any... so this can be a feature request.

On a related note, I've noticed files can be overwritten by user bin over SFTP. So I'm not sure in what way they are protected by excluding allow-delete-file anyway… :-]

Yes. We need a new allow-create permission that will allow writing new files only if they don't exists...and also allow renaming then,


2.x DnsResolver query dns on-demand per resolve()

DnsResolver query dns on-demand per resolve() call instead of maintaining a background task to constantly poll dns.

NetflixOSS » eureka » eureka-pull-requests #168 SUCCESS
This pull request looks good

NetflixOSS » eureka » eureka-pull-requests #171 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » eureka » eureka-pull-requests #172 SUCCESS
This pull request looks good


lte/alt1250: Correspond to shutdown

Summary
ALT1250 daemon to support shutdown.
Impact
Only ALT1250 dameon.
Testing
Test with Spresense LTE board.

@pkarashchenko  it's strange that apps ci always fail but nuttx ci always, do you know why?


Update MKO

Related to #301
Closes #311

[ ] MKO Photometry

Made too many mistakes with creating JSON files corresponding to the wrong filters name so I will start this over in a new pull request V2.

Starting over in #352


tomcat85: 8.5.11 -> 8.5.14

Motivation for this change
security fix in Tomcat
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Actually, doing a bit more testing first.

Merged in 024ddb32a7137c81c0e86ba59876c0cf4d5425e7
Backported in 0b7406e86be54015e66774675fb6dc9414b8a2f3
Thank you!


Idomatic variable names (closes #13)

This is in reference to: https://github.com/ahmednafies/go-covid/issues/13

This PR has been here for a while :thinking:


fix(jsonls): update cmd for windows support

Try to close: #1500
This is my first contribution ever to any open source so please be kind :)
I tested other lsp like html, cssls, and eslint, but I don't know if it is better to have multiple PR per lsp or one PR with multiple lsp.

Thanks :)


Cannot update firmware to version 2.4.5

Hardware
ESP32
Firmware version
v2.4.4
Application version
v2.4.4
What happened? What did you expect to happen?
HA notified me of new firmware being available. But when I try to install it I get the following error:
Failed to call service update/install. tuple index out of range.

How to reproduce it (step by step)
1. Go to device page
2. Click on firmware update
3. Click on install

Logs
No response

Just noticed that this error only happened when trying to update by connecting to HA via Nabu Casa URL. When using a local IP address, then it has updated without a problem.

I have the same issue, and I am not using the Nabu Casa URL. The same error is thrown when clicking the backup button on the device's page

Here the same issue, and as @larserhardsen said it's for both Nabu Case and local URLs.

This issue is fixed with the last update : https://github.com/rstrouse/ESPSomfy-RTS-HA/releases/tag/v2.4.5

Unfortunately I cannot test it as I already updated to the latest version using another approach before. But thanks a lot for looking into it.

On 21 Jun 2024, at 20:56, Jezza @.***> wrote:
This issue is fixed with the last update : https://github.com/rstrouse/ESPSomfy-RTS-HA/releases/tag/v2.4.5
—
Reply to this email directly, view it on GitHub https://github.com/rstrouse/ESPSomfy-RTS/issues/406#issuecomment-2183292557, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2QG7TFTWZHFCULEGJVJEDZIRZOBAVCNFSM6AAAAABJUTBYWWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBTGI4TENJVG4.
You are receiving this because you authored the thread.

I am going to close this.  The cause of this is well understood and addressed in later versions.


Request for typescript development environment

Curious on the development environment your using @zaaack, if i want to add some functionality / features to the repo.

@DanielTamkin Hi, I'm using VSCode to develop my TS projects, it has out-of-box support for TypeScript. If you want to develop keyv-file, you can simple git clone the repo, then run
yarn // or npm i
npm test


MySQL: utf8mb4?

Concerning MySQL, tables on a fresh install are now created with utf8mb4_unicode_ci collation (and utf8mb4 charset)
I wonder if that's intended?
Because you stated not so much time ago about that https://github.com/umami-software/umami/issues/786
and there's no conversion/migration for the already created utf8_general_ci tables.
I don't know much about the consequences it might have on umami, but switching to utf8mb4 also implies some lengths concerns.
For reference, here is an interesting link
https://mathiasbynens.be/notes/mysql-utf8mb4
(with a side note that the 767 bytes length limit for index has since been increased in newer MySQL versions)

Related to #1261. We need to update the migration file. Will track there.


Doesn't detect all hashtags

I have this kind of string "#beautiful",                 "#travelling",                 "#goodlife",                 "#beautiful",                 "#travelling",                 "#goodlife",                 "#beautiful",                 "#travelling",                 "#goodlife",                 "#beautiful",                 "#travelling",                 "#goodlife",                 "#beautiful",                 "#travelling",                 "#goodlife",                 "#beautiful",                 "#travelling",                 "#goodlife",                 "#beautiful",                 "#travelling",                 "#goodlife",                 "#beautiful",                 "#travelling",                 "#goodlife",                 "#beautiful",                 "#travelling",                 "#goodlife". This textview detects only first 3 hashtags and other doesn't detect at all. Any reason behind it ?

i had also same problem and see that words.filter filtering same words and i do like that and it's worked for me -
Change this
for word in words.filter({$0.hasPrefix(wordPrefix)}) {
let range = textString!.range(of: word)
attrString?.addAttribute(NSAttributedString.Key.foregroundColor, value: color, range: range)
attrString?.addAttribute(NSAttributedString.Key(rawValue: attrName), value: 1, range: range)
attrString?.addAttribute(NSAttributedString.Key(rawValue: "Clickable"), value: 1, range: range)
attrString?.addAttribute(NSAttributedString.Key.font, value: font, range: range)
}
--- with this---
do {
let nsText = textString
let regex = try NSRegularExpression(pattern: "(@[A-Za-z0-9-._]*)", options: [])
for match in regex.matches(in: text, options: [], range: NSRange(location: 0, length: nsText!.length)) {
print(match.range)
print(nsText!.substring(with: match.range))
let range = match.range
attrString?.addAttribute(NSAttributedString.Key.foregroundColor, value: color, range: range)
attrString?.addAttribute(NSAttributedString.Key(rawValue: attrName), value: 1, range: range)
attrString?.addAttribute(NSAttributedString.Key(rawValue: "Clickable"), value: 1, range: range)
attrString?.addAttribute(NSAttributedString.Key.font, value: font, range: range)
}

} catch {
//handle error
print(error)
}


Python 3.12 distutils deprecation error

System Info
accelerate 0.26.1, Windows 11, Python 3.12.1

Information

[ ] The official example scripts
[x] My own modified scripts

Tasks

[ ] One of the scripts in the examples/ folder of Accelerate or an officially supported no_trainer script in the examples folder of the transformers repo (such as run_no_trainer_glue.py)
[X] My own task or dataset (give details below)

Reproduction
To reproduce behaviour:

In Python 3.12 install latest accelerate with
pip3 install accelerate --upgrade
Try to initialise accelerate with:

from accelerate import Accelerator
accelerator = Accelerator()

This results in the error caused by https://github.com/huggingface/accelerate/blob/f88661b5d9f4977b5a1555a92e64ef3cd359cbc9/src/accelerate/utils/environment.py#L19

The fundamental issue is deprecation of distutils as part of https://peps.python.org/pep-0632/
Expected behavior
Accelerate should not depend on deprecated package and be compatible with Python 3.12+

Thanks! It looks like we should replace this with shutil.which instead (with zero logic changes)
would you like to make a PR?

Thanks! It looks like we should replace this with shutil.which instead (with zero logic changes)
would you like to make a PR?

Sure. I’ll look into it next week. Does seem fairly straightforward.


Augmented Reality support

I just want to know Augmented Reality(AR) support in near future or any such supported implementation with mapbox in react native application.
Looking forward any suggestion or recommendation.

@mfazekas any comment about AR support in mapbox


Mangas no Sekai no ID manga

Source information
Mangas No Sekai 1.4.42
Source language
Spanish
Steps to reproduce

Abrir cualquier manga
Recargar pagina
No actualiza el manga

Expected behavior
Actualizas el manga y salen los nuevos capitulos
Actual behavior
Actualizas el manga y te salta un error de id que no genera los capitulos nuevos
Mihon/Tachiyomi version
Tachiyomi 0.15.3
Android version
Android 13
Other details
Aparte de no actualizar los capitulos, el apartado de mangas recientes no se actualiza igual que el del WebView
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[ ] I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

"I have the same issue. The manga ID couldn't be obtained."


merge from utilities-1

Fix bold font in output. Eliminate compile warnings. Add configure and Makefile.in (and the files to generate them)

OK, how did this get in without review?
We DO NOT want autotools files for building anything -- it is a maintenance nightmare.


[BEAM-7640] Create amazon-web-services2 module and AwsOptions

This creates the canvas for the new Amazon Web Services IO module based on AWS SDK for Java 2.
So far the PR includes the AwsOptions Definition as well as the Module to map objects from/to json.
R: @aromanenko-dev

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Need to fix the build

Run JavaPortabilityApi PreCommit

Seems to be ok now @cmachgodaddy


add: specify types with docstrings in swin_transformer_v2.

@rwightman
I removed the initially added docstrings and added type annotations.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


East US 2 Gateway Address Typo?

Hello, I see this invalid IP address (<IP_ADDRESS>) listed as a gateway address for the East US 2 region.  Is this a typo?  Please correct it?

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

ID: e1a62365-4312-8aad-d2f1-bb5c4184adf1
Version Independent ID: 2ba5b809-8025-d7ee-c756-d6d1bab033fb
Content: Azure SQL Database and SQL Data Warehouse Connectivity Architecture
Content Source: articles/sql-database/sql-database-connectivity-architecture.md
Service: sql-database
Sub-service: development
GitHub Login: @rohitnayakmsft
Microsoft Alias: rohitna

Why is this IP invalid? I can confirm this IP address is valid and resolves to this Gateway in East US2

nslookup cr4.eastus2-a.control.database.windows.net
…
Non-authoritative answer:
Name:    cr4.eastus2-a.control.database.windows.net
Address:  <IP_ADDRESS>

Rohit Nayak
Sr. Program Manager – SQL Db Security Team
From: bjax22<EMAIL_ADDRESS>Sent: Friday, July 12, 2019 3:18 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Rohit Nayak<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [MicrosoftDocs/azure-docs] East US 2 Gateway Address Typo? (#35058)
Hello, I see this invalid IP address (<IP_ADDRESS>) listed as a gateway address for the East US 2 region. Is this a typo? Please correct it?

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

ID: e1a62365-4312-8aad-d2f1-bb5c4184adf1
Version Independent ID: 2ba5b809-8025-d7ee-c756-d6d1bab033fb
Content: Azure SQL Database and SQL Data Warehouse Connectivity Architecturehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsql-database%2Fsql-database-connectivity-architecture%23feedback&data=02|01|rohit.nayak%40microsoft.com|e27a17f3a3524c18a9bb08d70716c13e|72f988bf86f141af91ab2d7cd011db47|1|0|636985666621991932&sdata=z2GCvcS7uQiwW8kEPD6indWA12h4B%2BOYQCuH3%2FUgQhE%3D&reserved=0
Content Source: articles/sql-database/sql-database-connectivity-architecture.mdhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fazure-docs%2Fblob%2Fmaster%2Farticles%2Fsql-database%2Fsql-database-connectivity-architecture.md&data=02|01|rohit.nayak%40microsoft.com|e27a17f3a3524c18a9bb08d70716c13e|72f988bf86f141af91ab2d7cd011db47|1|0|636985666621991932&sdata=MNV9rSWEEp%2BfaFwQ13q8F4gO3rLEFE%2B6E1kgHWPmQkU%3D&reserved=0
Service: sql-database
Sub-service: development
GitHub Login: @rohitnayakmsfthttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frohitnayakmsft&data=02|01|rohit.nayak%40microsoft.com|e27a17f3a3524c18a9bb08d70716c13e|72f988bf86f141af91ab2d7cd011db47|1|0|636985666622001929&sdata=f%2BrlGonrvQ95UCjRjDh%2Fb8YpmZGoOb04%2BZACd5lFLDU%3D&reserved=0
Microsoft Alias: rohitna

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F35058%3Femail_source%3Dnotifications%26email_token%3DAD3RWHQQHC7SQN7PHYBCFZTP7D7IJA5CNFSM4ICSKDAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G67KOLA&data=02|01|rohit.nayak%40microsoft.com|e27a17f3a3524c18a9bb08d70716c13e|72f988bf86f141af91ab2d7cd011db47|1|0|636985666622011925&sdata=gX4nwoQ8IPs4vx4pisg7g90RviR5wyjTYnCkQVPBXOY%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD3RWHSJCUSX463JMPTUSA3P7D7IJANCNFSM4ICSKDAA&data=02|01|rohit.nayak%40microsoft.com|e27a17f3a3524c18a9bb08d70716c13e|72f988bf86f141af91ab2d7cd011db47|1|0|636985666622011925&sdata=qYwyItK%2FVh3GGwLinb8R%2FyAcm8o3rTWLucuRdXoSgBA%3D&reserved=0.

Boy am I foolish.  I mistakenly figured since it was a .0 address, it must have been a network address (not a host address).   Clearly I did not factor in the possibility of a net mask larger than /24.  I withdraw my comment and apologize for wasting your time.  :)

@bjax22, It’s not a problem! Thanks for leveraging Azure Docs feedback channel and sharing your valuable feedback, that's really appreciated. As Rohit's response was helpful we will close this issue out.


Add Intan loader

Converted to draft to accommodate different Intan file format.

rhs_perchannel_loader.py is the one developed to read per channel data. The rest of the files are taken from https://github.com/datajoint/load-rhs-notebook-python. Note that there is a COPYING file, which is the original license from the same repo.

Please do not spend time on correcting the rhsutilities.py. It's not our code.

@tdincer Which function will we use to read from the single *.rhs file which contains the metadata and raw data from all channels?

@tdincer Which function will we use to read from the single *.rhs file which contains the metadata and raw data from all channels?

We will use the one in the intanrhsreader as follows:
from intanrhsreader import load_file

rhsdata = load_file('filename.rhs')


All three algorithms implemented chunk wise

SHA256, MD5 and SHA1
Outputs have changed since the previous commit because of chunking, but are consistent if you don't change versions.
I could fix that by reading fixed chunks instead of lines. Let me know if I need to do that.
@PhoenixFlame101
Fixes #2
PES2UG21CS477 Sanket Padhi

Check my PR pls, thx. @PhoenixFlame101

The code is broken at master, please make sure it compiles at least before pushing.


fix: indicator doesn't update after mask as read

fix #147

Thank you 🙏

Hi @tjx666 , thanks for handling this, but it seems there are still issues.
Notification status still doesn't get updated after clicking Mark as Read button.
I inspected the dot indicator and found --notifications-icon-indicator-display is always none， even when there are unread notifications.

I don't know how to debug extension locally, could you take another look?

Will investgate it when I have free time

@euxx https://github.com/fregante/notifications-preview-github/pull/157

@euxx #157

That's great. Thanks you!


(PDB-4576) Update clj-parent to 2.7.2

clj-parent differences since 2.6.0

updated jackson-databind for CVE-2019-14439
updated jvm-ssl-utils for minor security fixes
nrepl updates
use clojure 1.10.1

CLA signed by all contributors.


Underscore is added when typing a text

Using:
"@angular/common": "^2.3.1"
angular2-text-mask": "^8.0.0"
"text-mask-addons": "^3.5.0"
I've created a number mask like the following:
    public amountMask = createNumberMask({
        prefix: '',
        suffix: ' €',
        thousandsSeparatorSymbol: ".",
        decimalSymbol: ",",
        allowDecimal: true,
        guide: false,
    });

All correct, I can't type non numeric chars, but when an input have a value, and I select all the data, and then type a word, and underscore "_" appears

+1

I seem to have solved the trailing slash with max-length="5" on the form field. Any update would be greatly appreciated. Thanks

Getting the same error on Internet Explorer. When the field is empty, and I focus it, then unfocus, the underscore appears in the text field, like _$. The config is very similar to the OP.

This is a duplicate of #294 I'll close this one and we can keep track of it there.
Unfortunately I don't know how to fix this - I can't reproduce it.  However, I'm not an angular develper.
If someone could setup a repository with an example reproducing the error, then I will have something to debug and can work on it - but until then I can't debug it if I can't reproduce it.


Update naming of templates imported from a catalog

Is your enhancement related to a problem? Please describe.
Improve readability of imported templates.
Describe the solution you'd like
For templates imported from a catalog, generate template name as <catalog-name>/<template-name>. Trim "terraform-" prefix if it is present in the repository name.
For example,
github.com/terraform-aws-modules/terraform-aws-rds from catalog aws-modules results in aws-modules/aws-rds

Environment

Walrus version: main 66a2214c8ea5dfb7fd8542fecb5e87a3778fc07e
UI version: dev-7449733

Test Result: pass


Making method compatible with parent

Duplicate of #117 ?

Ha, sorry about that. I do a lot of these small corrections when I use libraries so it becomes blurry which corrections I do. I will close this one ;)


Allow 'color' formatting on messages

See: https://www.hipchat.com/docs/api/method/rooms/message
It would be really nice to be able to send red, yellow, gray, green and blue messages. The rest api allows this, but I haven't found a way with this module.

@amaltson is correct. The node wrapper hipchatter can be used instead very simply.
Hubot + hubot-hipchat + hipchatter:
I currently use these three in conjunction to continue to easily connect to Hipchat and manipulate Hubot command. Whenever a command is brought up that needs to alert Hipchat with an error, Hipchatter is used within a Hubot CoffeeScript in order to easily customize a message.
If you have any questions or concerns about my implementation of those please let me know!

@AdamAld how do you convert the msg.message.room to something that can be used with hipchatter? It seems they are lowercased and spaces swapped with underscores, rather than the proper hipchat room name.


Depth Image Undistortion

Hi,
I'm interested in obtaining annotations, particularly the depth maps, in a pinhole rectified format. I'm aware that there are some code snippets in the documentation and the Jupyter notebook tutorial for rectifying the fisheye format of the raw RGB sensor. However, when I attempt to retrieve the rectified depth map using the provided code, I encounter an error. Is there a code snippet available for rectifying the depth modality without losing the distance information? The provided code rectifies the depth map only for visualization purposes, causing the information to transition from distance to color.
Thank you for your time and collaboration.

Hello,
Here is what you can do for ASE Aria Synthetic Environments)

see the almost last line for the work around

from projectaria_tools.projects import ase
device = ase.get_ase_rgb_calibration()

frame_id = str(frame_idx).zfill(7)

rgb_path = rgb_dir / f"vignette{frame_id}.jpg"
depth_path = depth_dir / f"depth{frame_id}.png"
instance_path = instance_dir / f"instance{frame_id}.png"

rgb = Image.open(rgb_path)
depth = Image.open(depth_path)
instances = Image.open(instance_path)

from projectaria_tools.core import data_provider, calibration
pinhole = calibration.get_linear_camera_calibration(
    device.get_image_size()[0],
    device.get_image_size()[1],
    device.get_focal_lengths()[0])

raw_image = np.array(rgb)
undistorted_image = calibration.distort_by_calibration(raw_image, pinhole, device)

raw_image = np.array(instances)
undistorted_image = calibration.distort_by_calibration(raw_image, pinhole, device)

# raw_image = np.array(depth) # Will not work
raw_image = np.array(depth).astype(np.float32) # WILL WORK
undistorted_image = calibration.distort_by_calibration(raw_image, pinhole, device)

If you are in ADT Aria Digital Twin

I will let @YLouWashU chime in

Thank you so much @SeaOtocinclus !
The code snippet helped me to solve the problem.

hello everyone, i have a question , does get_linear_camera_calibration works for all depth and rgb images in the ASE dataset ?what is the fourth parameter of the function (which is a string), even though while using get_linear_camera_calibration  to undistort the images, the pointcloud is still distorted, any help, maybe with the distortion process or the pointcloud generation? thanks a lot :)

`
read data
from projectaria_tools.projects import ase
from projectaria_tools.core import data_provider, calibration
device = ase.get_ase_rgb_calibration()
frame_id = str(frame_idx).zfill(7)
rgb_path = rgb_dir / f"vignette{frame_id}.jpg"
depth_path = depth_dir / f"depth{frame_id}.png"
instance_path = instance_dir / f"instance{frame_id}.png"
rgb = Image.open(rgb_path)
depth = Image.open(depth_path)
instances = Image.open(instance_path)
undistort data
pinhole = calibration.get_linear_camera_calibration(
device.get_image_size()[0],
device.get_image_size()[1],
device.get_focal_lengths()[0],device.get_label())
raw_image = np.array(rgb)
undistorted_rgb = calibration.distort_by_calibration(raw_image, pinhole, device)
raw_image = np.array(instances)
undistorted_instances = calibration.distort_by_calibration(raw_image, pinhole, device)
raw_image = np.array(depth).astype(np.float32) # WILL WORK
undistorted_depth = calibration.distort_by_calibration(raw_image, pinhole, device)
Convert images to numpy arrays
rgb_array = np.array(rgb)
instances_array = np.array(instances)
depth_array = np.array(depth)
Get the height and width of the depth image
height, width = undistorted_depth.shape
Generate pixel coordinates
y, x = np.indices((height, width))
pixel_coords = np.stack((x, y), axis=-1).reshape(-1, 2)
Flatten the depth image to create a 1D array of depth values
depth_values_flat = undistorted_depth.flatten()
instance_values_flat = undistorted_instances.flatten()
Initialize an array to store 3D points
points_3d = []
valid_instances = []
for pixel_coord, depth, instance in zip(pixel_coords, depth_values_flat, instance_values_flat):
# Ensure the depth value is valid
if depth > 0:
# Format the pixel coordinate for unproject (reshape to [2, 1])
pixel_coord_reshaped = np.array([[pixel_coord[0]], [pixel_coord[1]]], dtype=np.float64)
    # Unproject the pixel to get the direction vector (ray)
    direction_vector = device.unproject(pixel_coord_reshaped)

    if direction_vector is not None:
        # Replace the z-value of the direction vector with the depth value
        # Assuming the direction vector is normalized
        direction_vector_normalized = direction_vector / np.linalg.norm(direction_vector)
        point_3d = direction_vector_normalized * depth

        # Append the computed 3D point and the corresponding instance
        points_3d.append(point_3d.flatten())
        valid_instances.append(instance)

Convert the list of 3D points to a numpy array
points_3d_array = np.array(points_3d)
points_instances = np.array(valid_instances)`

How should I change the camera extrinsics after the rotation?


Adding more TryAdd overloads, this will make MVC service registration…

… much more succinct.

:shipit:


[cdk-drag-drop] Support snap effect.

Please describe the feature you would like to request.
https://codepen.io/dlouise/pen/NPZMjo , http://jqueryui.com/draggable/#snap-to in this example, the draggable element has snapping effect when dragged. Please support this effect, with some @input.
What is the use-case or motivation for this proposal?
I has more standalone draggable element, and need this snapping effect, that the user will can drop the elements exactly next to each other. And without this effect is so hard. But with this effect he can drag the elements with 4 or 8 or (n pixels) distance only.
Is there anything else we should know?
I made a little research, and i think this isn't a hard thing:
With an @input value can overwrite the function getTransform like this:
private _initialSnapEffect?: number;

function getTransform(x: number, y: number): string {
  // Round the transforms since some browsers will
  // blur the elements for sub-pixel transforms.
  // Need this Round before calculate the snap effect.
  x = Math.round(x);
  y = Math.round(y);
  // If have initialSnapEffect, then the translate effect only will change if the input x and y can
  // divided with this._initialSnapEffect number and no remainder.
  if (this._initialSnapEffect) {
     if (x % this._initialSnapEffect !== 0) {
        x = (x - (x % this._initialSnapEffect));
     }
     if (y % this._initialSnapEffect !== 0) {
        y = (y - (y % this._initialSnapEffect));
     }
  }
  return `translate3d(${x}px, ${y}px, 0)`;
}

Hi!
Some news?

@Flashunt - This was added in #15137.

Closing since this should've been covered by #15137.


remove buffer prefix in three

After r125, the BoxGeometry will be a buffer geometry and the default geometry doesn't exist anymore. It can still use BoxBufferGeometry but you'll get the same result. Using BoxGeometry is simpler and also being recommended in three.js community nowadays.
Learn more: https://discourse.threejs.org/t/three-geometry-will-be-removed-from-core-with-r125/22401

great to know, thank you!


Semantics of multiply_uint64_hw64

Can it be replaced by any other uint64_t multiply? I need to map 64-bit multiplies to 32-bit multiplies to use GPU instructions.

The semantics is to multiply two 64-bit integers and return the high 64-bit word.


Hotfix 0.5.1

Reverted the System.Web.Mvc dependency from v<IP_ADDRESS> back to v<IP_ADDRESS>.
As this is causing issues with environments that have not yet been patched with v<IP_ADDRESS> yet.
This patch should resolve issue #27.

Oops, targeted develop instead of master - doh!


Updates for the 2023 paper?

Will this repo be updated with research that happened with 2023 paper on dynamics multi-view CTVI?
Or has it already been updated via the commits in December?
I know in your abstract you reference this other repo: https://github.com/dsj96/TKDD, but it is not updated since the 2021 paper.
Thank you

HI, [NewAlexandria]!
Thank you for your attention to our work. The most difference between CTVI and TKDD is the objective function. For details, you can refer to the following.

https://github.com/dsj96/TKDD/blob/e1a64ac12ba7c423d4c142a79568dc4f0b9780ef/jinan_optuna.py#L394

https://github.com/dsj96/CTVI-master/blob/593609fc6ec0151180daa8a8335ffd92075395f1/jinan_optuna.py#L213
I hope my reply can provide you with some help.


Add support for PolyLoss in torchvision

🚀 The feature
The goal would be to add a PolyLoss PyTorch module behaving exactly the same way as any PyTorch core loss module. And the implementation would follow the following paper: https://arxiv.org/abs/2204.12511
One question still pending though: where should this be located in torchvision?
Motivation, pitch
As discussed in #6323, some losses have popped up over the last year. Before they can make their way to core, we should integrate those in torchvision first.
Alternatives
No response
Additional context
No response

My bad, GH created a duplicate as I refreshed the page after connection issue :sweat_smile:


Timeout unless explicit set Kin Version to v4

You get a timeout unless you set the KinVersion to 4 explicitly.
https://github.com/kinecosystem/agora/blob/master/client/client.go#L111

has this been resolved?

has this been resolved?


Fixes #653

deleteOnExit deletes when the JVM terminates, so delete after we've replicated.

@kosarko I don't see the changes of https://github.com/DSpace/DSpace/pull/653 in the commits

@kosarko I don't see the changes of DSpace#653 in the commits or is it already part of clarin-dev ?
I think you referenced the wrong issue by mistake the fix is for #653 ?

@amirkamran Yes, the fix is definitely for https://github.com/ufal/clarin-dspace/issues/653. Seems that somehow github linked it with upstream


consider global nodeSelector if not specified on the api level

/retest-required

/test images

@stuggi: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name 	Commit 	Details 	Required 	Rerun command
ci/prow/images 	9387b9f link 	true 	/test images
Full PR test history. Your PR dashboard.

I think this is caused by the Prow infrastructure issues that Sandeep mentioned.  We'll have to wait until they resolve before this can pass.

/test images

/test glance-operator-build-deploy-kuttl

/test glance-operator-build-deploy-kuttl


[NEW]: Ponzi scheme with fake smartbots

Date
2024-08-26
Description
Those bots, that automatically deploy smart contracts to provide liquidity for flash loans, were, unfortunately, as fake, as the purported payments by Gemini. It was all a multi million dollar ponzi scheme. And the brother did not disclose to his victims that he had a history in financial crime! I am shocked. Shocked!
Links
https://www.sec.gov/newsroom/press-releases/2024-107
https://www.sec.gov/files/litigation/complaints/2024/comp-pr2024-107.pdf
Agreement

[X] I irrevocably agree to release my contribution under the CC-BY 3.0 License

Attribution name
Daniel AJ Sokolov
Personal link
https://social.heise.de/@newstik

Looks like we were reading this at the same time :) https://www.web3isgoinggreat.com/?id=adam-brothers-charged-by-sec


Question about DNS challenge failed with "Could not determine the zone"

We tried to use DNS challenge to get certificate, but it ended up with the error "Could not determine the zone" which came from here
The domain is zhiminx-debug-predictor-default.zhiminx.kn.ml1.crt.nuance.com
We have set up the ClusterIssuer and DNS servers for it.
Some related logs from cert-manager:
I0409 18:28:26.686261       1 dns.go:121] cert-manager/controller/challenges/Check "msg"="checking DNS propagation" "dnsName"="zhiminx-debug-predict
or-default.zhiminx.kn.ml1.crt.nuance.com" "domain"="zhiminx-debug-predictor-default.zhiminx.kn.ml1.crt.nuance.com" "resource_kind"="Challenge" "reso
urce_name"="route-0e0568b5-132e-443a-9319-d90a755bf6d7-306686497-3227296467-456947003" "resource_namespace"="zhiminx" "type"="dns-01" "nameservers"=
["<IP_ADDRESS>:53"]
E0409 18:28:26.762446       1 sync.go:184] cert-manager/controller/challenges "msg"="propagation check failed" "error"="Could not determine the zone
 for \"_acme-challenge.zhiminx-debug-predictor-default.zhiminx.kn.ml1.crt.nuance.com.\": Unexpected response code 'SERVFAIL' for _acme-challenge.zhi
minx-debug-predictor-default.zhiminx.kn.ml1.crt.nuance.com." "dnsName"="zhiminx-debug-predictor-default.zhiminx.kn.ml1.crt.nuance.com" "resource_kin
d"="Challenge" "resource_name"="route-0e0568b5-132e-443a-9319-d90a755bf6d7-306686497-3227296467-456947003" "resource_namespace"="zhiminx" "type"="dn
s-01"

We are wondering what went wrong here.
Environment details::

cert-manager version: 0.13.1V

/cc @jeffgriffith for details about kubernetes version and cloud provider.

Thanks @ZhiminXiang
Kubernetes 1.15.10 (Azure AKS)
Cert-Manager 0.13.1
Knative 0.13.2
Istio 1.3.8 w/ SDS
AzureDNS:
A and TXT records with token are there for the request
$ nslookup _acme-challenge.zhiminx-debug-predictor-default.zhiminx.kn.ml1.crt.nuance.com
Server:  mt-opendns01.nuance.com
Address:  <IP_ADDRESS>

Name:    _acme-challenge.zhiminx-debug-predictor-default.zhiminx.kn.ml1.crt.nuance.com

DNS looks great up until we enable autoTLS. The cert requests happens, then fails as above with "unable to determine zone".
The cluster issuer looks like this with some edits for privacy. hostedZoneName is set to crt.nuance.com.
spec:
  acme:
    email: xxx
    privateKeySecretRef:
      name: letsencrypt-crt.xxx.com
    server: https://acme-v02.api.letsencrypt.org/directory
    solvers:
    - dns01:
        azuredns:
          clientID: xxxx
          clientSecretSecretRef:
            key: client_secret
            name: azuredns-config-xxx-com
          hostedZoneName: crt.nuance.com
          resourceGroupName: xxxx
          subscriptionID: xxxxxx
          tenantID: xxxxxx
status:
  acme:
    lastRegisteredEmail<EMAIL_ADDRESS>    uri: https://acme-v02.api.letsencrypt.org/acme/acct/82675785
  conditions:
  - lastTransitionTime: "2020-04-06T18:23:45Z"
    message: The ACME account was registered with the ACME server
    reason: ACMEAccountRegistered
    status: "True"
    type: Ready

It turns out that even though there is nothing strange here as far as our DNS config goes, setting dns01-external-nameservers fixed this problem for us. Don't know if it was Azure AKS related or our own OpenDNS servers. Perhaps the latter but not sure precisely.
--dns01-recursive-nameservers=<IP_ADDRESS>:53,<IP_ADDRESS>:53
This should not seem necessary based on the docs but apparently helps us work this.

Can you check if your DNS server filters or modifies any SOA records?

Thanks for your reply @meyskens . it must be something like that. i don't have easy access to corporate dns settings so i think we'll stick with just bypassing it :-)


Add home-manager search feature

Home manager has several services and config options available at https://github.com/nix-community/home-manager/tree/master/modules which are similar to nixos configuration options.
Searching through these manually or using github search is rather tedious.
Using search.nixos.org to search through these feels like a natural extension of it's feature set.

If I see correctly home manager expenses it's modules in it's flake definition.I'm working on flake support for nixos-search right nowAfter that it is a configuration issue I assume. ---- On Thu, 24 Jun 2021 20:54:23 +0200  @.***  wrote ----
Home manager has several services and config options available at https://github.com/nix-community/home-manager/tree/master/modules which are similar to nixos configuration options.
Searching through these manually or using github search is rather tedious.
Using search.nixos.org to search through these feels like a natural extension of it's feature set.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.

in the meantime you can find all options here: https://rycee.gitlab.io/home-manager/options.html

The blocker got merged a while ago.

Decide how to expose the options in home-manager (see https://github.com/nix-community/home-manager/issues/2297#issuecomment-1079698898), and then reflect that in the nixos-search backend, probably also with a frontend change to separate HM options from NixOS options.

We currently do not track flake options (iirc) but should be able to.
However merging them with the nixos optionswould be more of a ui challenge and homeManager (as well as nix-Darwin for that matter) is special as it introduces its own framework separate from a configuraton.nix (although able to integrate)

Did some work towards this in https://github.com/nix-community/home-manager/pull/2971 (not solving the main problem).

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/the-nix-module-in-home-manager-and-nixos/20999/11

Citing pinpox:

What needs to be done to get this working now?


When there are multiple actions in the queue, only call the "updated" methods for the last action

This is a prototype to solve for https://github.com/adamghill/django-unicorn/discussions/696. It changes the semantics of how the updated methods work, though -- instead of getting called for every action, when there are multiple actions in a queue (for example with deferred), the updated method would only get called once for the last action.
I do wonder:

If adding a new method (instead of using "updated") would be more appropriate, although I can't think of a good name for it.
Could I pass another argument along with the property value which indicates it's the last value in a queue? I can't think of a nice argument name for that either. Something like this arg name feels very messy, but would be "correct": def updated_search(self, search, is_last_or_only_action.
Another option would be add something to the component instance (aka self) which could be used, but this feel like it would expose a lot of internals that probably aren't all that useful to most people. But, theoretically I could add component_request to self, so then component code to do something with the last action would look something like this:

def updated_search(self, search):
    action_queue = self.component_request.action_queue

    if len(action_queue) > 1:
        last_action = action_queue[-1:][0]

        if last_action.payload.get("name") == "search" and last_action.payload.get("value") == search:
            print(f"this is the last one action: {search}")

That seems like a lot of boilerplate code for something that should be easier for users of the framework.

Sorry for the lag in responding here.  Number 1 above seems to be the cleanest API, avoiding many of the issues you list for the others (like exposing too many internals).  In particular it makes it easy for devs to implement both "updated" semantics when they really want to handle every event, as well as just the last event.
After thinking a while I wonder if each_update and last_update would be good names?

After thinking a while I wonder if each_update and last_update would be good names?

Makes sense. I think, to prevent changing the existing API, I would keep updated as-is, but add another method for the last update.

last_updated_{field}
final_updated_{field}
finished_updated_{field}
finished_{field}

Any of those sound ok? Or something else maybe?

I was looking at synonyms for "completed" and ran across "resolved". I think that works and has the right connotation. So, my plan is to add a resolved_search(self, value) method that could be added to components which will only ever fire once with the last value for the field.

This sounds logical!


[Bug] Keep reverting to old config after update

It happen again when update to v0.44.29-beta (before is when update to v0.44.28-beta).
After update it uses or reverting to "old" config not the latest config running before update... all proxy provider created gone and the one which already deleted back again.
Thanks

delete the /tmp/openclash before update

ic2...thanks


Alexa not discovering the device

I set it all up, but none of my alexas see the device. I got the wifi right and its talking with my devices, and even home assistant. But neither even see it on their end.

The serial port of the aurdino should be spitting out messages about the discovery process - this will be your friend in figuring out why
Get Outlook for iOShttps://aka.ms/o0ukef

From: Justnthenick @.***>
Sent: Thursday, August 29, 2024 5:44 PM
To: kakopappa/arduino-esp8266-alexa-multiple-wemo-switch
Cc: Subscribed
Subject: [kakopappa/arduino-esp8266-alexa-multiple-wemo-switch] Alexa not discovering the device (Issue #80)
I set it all up, but none of my alexas see the device. I got the wifi right and its talking with my devices, and even home assistant. But neither even see it on their end.
—
Reply to this email directly, view it on GitHubhttps://github.com/kakopappa/arduino-esp8266-alexa-multiple-wemo-switch/issues/80, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJFRJWRCGYVVLV6ULUCDMZTZT2YLXAVCNFSM6AAAAABNJUX7IOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ4TGNJQGIZTINQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Feature request: plot type Candlestick

Hey there,
I'd love to use nim-plotly to draw Candlestick charts: https://plot.ly/python/candlestick-charts/
Please let me know if this is something that could be easily implemented. Otherwise I may try to hack something working and send over a PR. I see I can easily extend the plot types but the Candlestick has a slightly different set of inputs I need to understand how to pass in.
Cheers,
Nicola

Hi, I looked at candlestick and they are one of the more complex.
You can do this by:

adding Candlestick to the PlotTypes enum

add the required attributes to the Trace object here

updating the unfortunately long % proc for Trace here

add an example to examples/

Hey Brent!
I really appreciate your fast reply. Thanks for the guideline, I'll see if I can get it to work.

No problem. I would follow the javascript docs here: https://plot.ly/javascript/candlestick-charts/
since that's what nim-plotly is directly using.
Looks like you'll need to add at least close, high, low, open all of type seq[T] to the Trace

Alright thanks again I'll be looking into it the coming days.

closed by #14


handlebars-helpers

Hi, great work with this gem! I managed to include my handlebars-partials into an existing project, which did not work with handlebars until now. Really great, thanks!
Now i wondered about one thing: I created some of those handlebars-templates with the npm-handlebar-helpers from assemlbe.io, therefore my question:
Would it be possible to include those helpers on ruby-side, that tilt knows them and renders HTML correctly? Currently i got errors on views, where i used those helpers...
Many thanks for your help!

Yes, thank you for putting together this gem! It's very helpful.
I realize it's been quite some time since this issue was opened, but was there any progress made on this front? Also happy to dig into it myself, but was just curious if anyone got further with including external helpers into tilt-handlebars.

@ptrikutam Sorry, I haven't had much time to give this any TLC. But I will gladly accept pull requests. Unit tests are especially appreciated.

@bluerouse @ptrikutam
Do either of you have any follow up for this issue?
Both Ruby and JavaScript functions can now be added as helpers.
See https://github.com/gi/handlebars-ruby.

Sorry, I can't remember exactly what I was working on when I posted this issue. I don't think we ended up continuing to use this library.

Thanks for responding. No worries.


Remove ibm_db, jdbc and merge pybase into base

I think all that's left here is to merge pybase in to base, no?

Closed by #25

Closed by #25


mainpage can't display before new mesos or kubernetes worked

Rancher Versions:
Server: 1.4
healthcheck: v0.2.3:rancher/healthcheck:v0.2.3
ipsec: v0.0.4:rancher/net:holder
network-services: v0.0.10: rancher/metadata:v0.7.0 rancher/network-manager:v0.4.5
scheduler: v0.4.0:rancher/scheduler:v0.6.3
kubernetes/mesos (if applicable): any
**Docker Version:
1.12.5
**OS and where are the hosts located? (cloud, bare metal, etc):
centos7
**Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node rancher
**Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Mesos/Kubernetes
Steps to Reproduce:
when i create a new [mesos or kubernetes]
if mesos is not work well
i cant  see the main page
like: http://<IP_ADDRESS>:8080/env/1a5/mesos
Results:
a page only displayed with background color

@godcong - I am unable to reproduce your issue.  I created a CentOS7 machine through Digital Ocean and put rancher on it.  I then created a Kubernetes and Mesos environment and went to those environment and the page came up fine.  Can you provide more information?

today is ok...
i think i missed some steps...

godcong, what did you do in order that it works now?


Check for equal namespaces in the sameVnode function

This is quite the edge-case I thought of, but the sameVnode function might be problematic if there are two elements with the same selector and key but different namespaces. For example, an <a> element may be used inside or outside SVG and it will have different namespaces.
I'd say the sameVnode should be something like:
function sameVnode(vnode1: VNode, vnode2: VNode): boolean {
  return vnode1.key === vnode2.key && vnode1.sel === vnode2.sel && vnode1.ns === vnode2.ns;
}

Please forgive my laziness for creating an issue instead of submitting a PR. :-)

I just noticed that the namespace is actually not stored in the virtual node but in its data, so the code above should be slightly different: probably with some boring isDef data checks.
Either that or move the namespace to the virtual node itself. :-D

I wonder when would this be helpful. When would elements of possibly different namespaces be compared?

Why would there be "two elements with the same selector and key"? Wouldn't that be unsupported?

This issue is so old and I've dealt with Snabbdom so long ago that I may not remember exactly all the nuances but, from what I remember, Snabbdom should be able to patch any element against any other element.
I find it unlikely that someone would actually run into this in practice, which is why I called this "quite the edge-case". However, theoretically, I can't see why you can't patch an element with selector S, key K, and namespace N1 against an element with selector S, key K, and namespace N2. The (at the time the issue was opened) function that compares virtual nodes would state the the two elements are the same, when in fact that isn't true due to different namespaces.

I wonder when would this be helpful. When would elements of possibly different namespaces be compared?

I'd say that it wouldn't be helpful 99.9% of the times. However, for sake of correctness, it might make sense to add the check.

Why would there be "two elements with the same selector and key"? Wouldn't that be unsupported?

I don't see why it would be unsupported.
Do what you think is best regarding this issue (close it if you think it makes sense), it's been too long since I've played around with Snabbdom. :)

Snabbdom should be able to patch any element against any other element.

Agree.

On second thought two elements having the same selector and key seems common.


#44 Customisation: named slots

This PR adds the feature #44
What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

The PR fulfills these requirements:

[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing

Looks great! I will review it this week end.


fix: refreshMetadata should retry if topic does not exist and allowAu…

…toTopicCreation is set
fix: #815
Not sure why it happens but it happens randomly. Seems like a race condition when 2 client try to create the same topic at the same time. This fix is tested and working

will this be merged soon?

When will this be fixed and merged? @Nevon

Any idea when this will be merged?

This PR looks promising in fixing part (or all of) of https://github.com/tulios/kafkajs/issues/815
Basically ever since Kafka moved from Zookeeper to KRaft there seems to have been a breaking change in auto-topic creation on subscription. It looks like with zookeeper back in the day you could subscribe to a non-existent topic just fine, it would be created behind the scenes and the subscription succeeds. now with KRaft subscribing to a non-existent topic throws KafkaJSProtocolError: This server does not host this topic-partition but still creates the topic afterwards, if auto-topic-creation is enabled.
With this PR the (correct) action of retrying the subscription after waiting a bit seems to be used.
As this PR does not have any reviewers maybe you could have a look @tulios ?

The PR would also close https://github.com/tulios/kafkajs/issues/1563

This looks good to go to me.

Any updates on this @Nevon @tulios, can this be merged?

This would be nice to have in a new release? :pray: @Nevon @tulios


Fix compiler crash for returning xml|error from service function

Purpose
$subject
Fixes #33120
Approach
The XML sequence store instruction returns an XmlValue and the relevant type casting (<xml|error>) is not added for the return statement at Desugar level. This PR adds that type cast expression.
Samples
public service class Service {
    function bar() returns xml|error {
        return xml `<grand_total>${1d}</grand_total>`;
    }
}

public function main() {
    Service s = new();
    xml|error result = s.bar();
}

Remarks
Added implementations for xml subtypes & xml specific instructions in BIR emittter.
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Patch coverage is low due to BIR Emitter changes.


Organisations are not loading

The demo generator worked just fine a few weeks back but not now it does not show any oraganisations for me to choose saying "Could not load your organizations. Please check if the logged in Id contains the Azure DevOps Organizations or change the directory in profile page and try again." I've signed out and signed in many times, selected the correct directory where I see all my DevOps organisations, tried from different workstations but the issue persists. The only change I remember doing since the last time it worked was to create a new DevOps organisation in the same directory and connect an Azure Pass subscription to it. I've tried deleting the newly created organisation as well but no improvements. I want to load the projects from demo generator so how can we fix this?

I managed to fix it after trying many things for some time. I think what worked is,

Revoke the Azure DevOps Demo Generator from Authorizations in the My Information page.
Select the correct Directory again.
Sign out.
Sign into Azure DevOps Demo Generator.

The issue was still present so I had to do the sign out and sign in couple times more. I guess we need to wait around 5-15 minutes after the revocation perhaps?

Authorise the app again.
Organisations are now visible.

I created my new organisation yesterday and as far as I know, everything worked fine until yesterday. So, perhaps, there is limitation in the authorisation process where it fails to work when a new organisation is created after the app has been authorised. I'm not sure.

@aut0pil0t Thank you for reaching us. You might be seeing the following error message.

This might occur when your logged-in directory doesn't have any organization to list.
We have provided the solution within the Azure DevOps Demo Generator, you can opt for Switch Directory option, which redirects you to My Information page, you can change the directory.
once you click on that, you will see a link to sign in again

with this, the organizations will be loaded immediately after you sign in, don't have to wait for 5 mins.


[RFE] Improve steve cache or re-evaluate caching technique.

Is your feature request related to a problem? Please describe.
Currently steve implements caching using an LRU cache. It caches a configured number of requests. The problem with this is that it does not consider the size of each request. If the size of a request eclipses that of everything else it still poses a memory risk.
Describe the solution you'd like
First an attempt at configuring the amount of data that can be cached by memory. If this is not feasible then reevaluate how caching is being done. If the first part is possible this is more of an enhancement than an RFE.
Describe alternatives you've considered
The RFE portion of this issue would be for the dev to explore, consider, design, and get reviewed.
Additional context
May add to this later.

SURE-6377

Ran benchmarks described here https://github.com/rmweir/scalability-tests/blob/20230927_steve_cache_tests/docs/20230927 - multi users steve cach test.md. Both the current steve cache technique and the update here use an unreasonable amount of memory in a scaled environment.
Here some adjustments were made that improved the memory usage significantly. However, after reviewing long term goals and assessing that pursuing an enhanced approach requires a lot of effort for an interim solution. This setup also still suffers from issues with list that commonly update, such as ConfigMaps. Considering those two reasons we have decided not to pursue them and instead accelerate the timeline for Vai as a solution which aims to reach many of the same goals and should be able to handle cases such as constantly changing lists.


Can the depth and color images of different resolutions obtain the corresponding coordinate positions?

Required Info

Camera Model
{  D400 }

Operating System & Version
Ubuntu 16

Platform
PC

Language
python }

Issue Description
The resolution of the depth image is 848480, and the resolution of the corresponding color image is 1280720. Can I find the color coordinates of the points in the depth image by "projectoion"?

Hi @nevynwong   You can find the depth of a specific color pixel using the instruction rs2_project_color_pixel_to_depth_pixel
Because you have different resolutions for depth and color, this instruction on its own may not provide an accurate result.  The approach taken by the script of a RealSense Python user in the link below, using alignment and deprojection, may work better for you.
https://github.com/IntelRealSense/librealsense/issues/6749#issuecomment-654185205

Hi @MartyG-RealSense  This seems to be about the coordinate conversion method of the same resolution, is there any coordinate conversion method about different resolutions?

If alignment is used, like in the Python script in the link, then the align processing block should automatically make adjustments if there is a difference in resolutions.

Can I understand that the alignment still projects all the coordinates in the depth image into the color image? Using the rs2_project_color_pixel_to_depth_pixel function?

Depth to color alignment maps the depth coordinates to the color coordinates.  If you are using a RealSense camera model where the depth field of view is larger than the color field of view (D435 / D435i) then some of the outer areas of the depth image may get cut off once aligned to the color field of view.   Cameras where the depth and color field of view are the same size are D415 and D455.
My understanding is that you would use rs2_project_color_pixel_to_depth_pixel OR depth to color alignment, not both techniques.   If both depth and color had the same resolution then rs2_project_color_pixel_to_depth_pixel may be sufficient.   If you have two different resolutions then depth to color alignment with the processing block is likely to work better for you due to the automatic calculations that the align processing block makes.

@MartyG-RealSense  Thanks, I understand. But I would like to know what is the exact operation about Align? Is there any open source code to learn?

The SDK has an example Python depth to color alignment script called align-depth2color.py that you could study.
https://github.com/IntelRealSense/librealsense/blob/master/wrappers/python/examples/align-depth2color.py

Hi @nevynwong   Do you require further assistance with this case, please?   Thanks!

I have no more questions. Thank you for your help.

I have no more questions. Thank you for your help.

Thanks very much @nevynwong for the update!

Thanks very much @nevynwong for the update!


Refine app

Pre-Flight checklist

[ ] Testing

[ ] Changes have been manually tested

What are the relevant tickets?
Part of #519
What's this PR do?
This adds a barebones refine application for local development only for now.
How should this be manually tested?
Run docker-compose up and verify you can reach the dashboard at http://mitxonline.odl.local:8016/

Codecov Report

Merging #518 (5240c50) into main (8968919) will decrease coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #518      +/-   ##
==========================================
- Coverage   86.33%   86.27%   -0.07%
==========================================
  Files         106      106
  Lines        4639     4640       +1
  Branches      731      731
==========================================
- Hits         4005     4003       -2
- Misses        524      526       +2
- Partials      110      111       +1

Impacted Files
Coverage Δ

main/settings.py
93.96% <100.00%> (+0.03%)
:arrow_up:

main/urls.py
81.25% <100.00%> (ø)

ecommerce/discounts.py
71.92% <0.00%> (-5.27%)
:arrow_down:

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 8968919...5240c50. Read the comment docs.


[rt.openssl.org #4671] Bug: pkcs8 application limits output passwords to 50 characters

Migrated from rt.openssl.org#4671 (status was 'new')
Requestors:

<EMAIL_ADDRESS>
From<EMAIL_ADDRESS>on 2016-09-04 18:39:09:
The pkcs8 application limits output keyfile passwords to at most 50
characters if -passout parameter is not used.  This seems to be because
the buffer used for password input in pkcs8.c has a fixed size of 50.

This has a small security impact: the limitation leaks the maximum
length of a password used on some PKCS#8 keys.

How to reproduce:

    ---8<---8<---
    $ openssl genrsa -out rsa.key
    $ openssl pkcs8 -topk8 -in rsa.key -out key.pkcs8
    Enter Encryption Password:123456789012345678901234567890123456789012345678901
    ---8<---8<---

Actual result:
    pkcs8 exits without output and returns value 1.

    ---8<---8<---
    $ echo $?
    1
    ---8<---8<---

Expected result:
    pkcs8 prompts to verify the password and uses said password for
    encryption.  It should be possible to use passwords of arbitrary
    length.

Workaround:
    Use the -passout parameter, e.g. "-passout stdin".

Versions tested:
    ---8<---8<---
    $ uname -srm
    NetBSD 7.0.0 amd64
    $ openssl version
    OpenSSL 1.0.2h  3 May 2016
    $ /usr/bin/openssl version
    OpenSSL 1.0.1p 9 Jul 2015

    $ uname -srm
    NetBSD 7.0.1 amd64
    $ openssl version
    OpenSSL 1.0.1t  3 May 2016
    ---8<---8<---

--
Jarmo Jaakkola

fixed in 1.1.0 and master.


TLS certificate expired

The TLS certificate on https://www.googleplaymusicdesktopplayer.com/ expired on 1st December, so now it shows a warning if anyone tries to access it.

Seems to be fixed now?

Yeah, looks like it's OK now.


Update connect-query-nodejs.md

Fix typo in docs for commented out code on how to connect to mssql with node and AAD.

Learn Build status updates of commit 802f757:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azure-sql/database/connect-query-nodejs.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@dzsquared
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


handle set_buffer_scale and output_scale

Add set output scale, get output scale,get output scaled size api
with @david50407 's help
for fixing https://github.com/Cloudef/wlc/issues/57
I'm not sure about whether the pointer handling is right, I don't know how to check the recursive part.
Wish to make some progress to HiDPI support XD.

@ss1h2a3tw : You should squash the coding style fixes into single commit via git rebase -i.

Does the client expect coordinates it receives to be as if they were on 1x scale. That is we need to map for example 2x, mouse movement over surface to 1x scale coordinate system?
Looking at this PR, it may be enough to simply just handle scaling in the wlc_view_get_bounds and wlc_view_get_visible_bounds function, and everything else will work as normal (hit testing, culling, rendering, input..) As input already does coordinate scaling to surface size which is the 1x size without scaling. Can you try this and report that other changes are not needed?
For other things, I mentioned above wlc_output_set_scale sounds weird, but perhaps it can be useful to set custom scale on output. However does EDID / drm / etc.. give this information for us? Or does weston simply just use scale parameter in ini configuration as well.

I will test it later, thanks for your reply.

As only modifying get_bound result in the cursor's position differ between rendered on screen and inside client.

in the photo , the cursor is in the title bar of weston-terminal (right middle in "progs"),
but the play button in the rhythmbox is highlighted.
using the code below
https://github.com/Cloudef/wlc/compare/master...ss1h2a3tw:test

@Cloudef
Maybe changing line number 290 of surface.c can help?
It seems like it is directly copy the size of buffer, which explains why I need to divide surface size by scale.

Dividing surface's size is enough for eveything to work? That sounds like good idea to me if so. Do we actually need the 2x size information anywhere now?

Yeah, looks like buffer_scale can be handled as dividing surface's size.
supporting output scale will need to change seat/pointer.c , gles2.c

Ok, so the steps we have done here.

Divide surface size with its scale (1 == unaffected, 2 == half, so on..)
Multiply input coordinates with output's scale, divide boundary by output scale.
Render surfaces by multiplying surface geometry with output scale. (1 == unaffected, 2 == multiple of size, so on..)

1 and 3 seems like good idea as it avoids conditional calculation depending if surface size is less or more than output scale and so on.
What's the purpose of step 2? How does this work with scale 1 surfaces on scale 2 output? I assume the client treats coordinates in its native coordinate space, not in the scale 2 coordinate space. I assume this is just done so that scale 2 surfaces work on scale 2 output (?), if so maybe the better way is to modify the coordinate_transform structure in surface.c instead.
Apart from the coordinate transformations still being unclear and the need of get_scaled_output_size() I think we are on right track.

The reason of dividing boundary is that client use the coordinate of their surface,
when output scale=2, client is using the coordinate of resolution dividing the output scale.
So the pointer coordinate is half of output, when printing the cursor, we need to multiply by output scale.
And the input coordinate is right with my code.

weston-terminal scale=1
rhythmbox scale=2

Could the output scale taken into account in surface's coordinate_transform when it's attached to output here: https://github.com/Cloudef/wlc/blob/35caed59fa992a82774711622d86ac1172abd07b/src/resources/types/surface.c#L299 ?

OK I will try it later.

Also, probably good idea to include scale = 3 surface in your test too, this should in theory be downscaled to scale 2 output.

After my test,modify coordinate transform doesn't work.
Since
https://github.com/Cloudef/wlc/blob/309ddb03ee91b66ad4189d29ee651ac532d266a5/src/compositor/seat/pointer.c#L246
Subtracting offset first will make the offset been scaled by output scale too.
Since buffer_scale is informed by client,
I need to find some test client that I can define its buffer scale, or need some dirty hacking to test it.

Probably best way is to modify e.g. weston-simple-shm https://cgit.freedesktop.org/wayland/weston/tree/clients/simple-shm.c#n316, you may send custom scale with wl_surface_set_buffer_scale. I'll test this PR too to get sense how the coordinate transformations go, and that the visual coordinates match the logical ones, (even if client gets correct coordinates, it's easy to break coordinates compositor side, so hit detection, culling etc fails)

I found that simple-shm is using compositor version 1 so I need to change not only wl_surface_set_buffer_scale,
and I found simple-damage support scale as argument,
So I'm using it to test downscaling , seems working perfectly.

Ok that seems quite promising. I'll pull the code and test too.

After my test of output scale = 3,4 upscale is working well as 2,
but because of the pointer coordinate is divide by output scale, it need move at least 3 pixels when output scale = 3, 4 pixels when output scale =4 and so on
Maybe there's a better way for handling pointer coordinate.

I locally managed to do this with only changing output.c and surface.c, I'm killing some other bugs at the same time, I'll post some diffs for testing then.

I found that subsurface is rendering in the wrong position, I will fix it in few days.

I already fixed that locally, and also the fact subsurfaces were not scaled properly when buffer size is being stretched (due to minimum size). I'll try to get my code out this week for testing.

OK, Is there anything more I can help?

I'll push the code for testing when ready. The work here is great resource on what needs to be done.

https://github.com/Cloudef/wlc/tree/hidpi <- can you try this branch? For further fixes issues, probably good idea to open new PR against this.

I have test it, and I found two problems.
When spawning a client which support buffer scale at scale = 1,then change output scale to 2, but it doesn't set the buffer scale into 2.
Another problem is not quite related to scale, when using weston-subsurface to test , the pointer event seems not sending or sending wrong when the cursor is on subsurface.
I will add some screenshot later.

When spawning a client which support buffer scale at scale = 1,then change output scale to 2, but it doesn't set the buffer scale into 2.

As far as wlc goes, it should send the new output information. It may be that the client just doesn't support this case.

Another problem is not quite related to scale, when using weston-subsurface to test , the pointer event seems not sending or sending wrong when the cursor is on subsurface.

The pointer event problems may have been caused by unrelated change, that is basic support for "input area" of surfaces, but in sense it's incomplete as it only checks the area of views, not subsurfaces.

The third problem is Xwayland seems not rendering in right scale.

I wonder if X11 has equivalent protocol to wayland scale that I should be aware of.. I really doubt it. Neverthless something to look into.

X11 has no similar protocol I know of, but many programs respect the "Xft.dpi" variable you may set in .Xresources. Additionally many GUI frameworks have custom environment variables.
GDK/GTK: GDK_SCALE=2
Qt: QT_AUTO_SCREEN_SCALE_FACTOR=2
Elementary: ELM_SCALE=2
I do not know, if wlc is supposed to set environment variables, but there should be at least a callback for changed scale factors, so an actual compositor might set those variables.

output.resolution callback already gets called, however it may be good idea to break the API of this callback and include from_scale and to_scale in the arguments as well. So you don't lose the information of old scale.

Did some initial work on getting this branch working with sway. My branch is here. A few things I've noticed (some of this may be sway's fault and some of it may be wlc's fault, not sure yet):

subsurfaces are 4x scaled if I use 2x scaling
window borders are fucked up
x windows are stretched rather than setting the xwayland DPI (this is a difficult one, since x only supports one DPI for the whole thing)

Screenshot
Use output [name] scale 2 or similar to set the scale factor on sway.

@SirCmpwn  please use the branch https://github.com/Cloudef/wlc/tree/hidpi
my branch here have bug handling subsurface scale

Tried again with wlc's hidpi branch, works better. Pushed a new version to my hidpi branch.

Merged into master.


Alias Task

Add alias_task support. It includes documentation/explanation and tests.

Hey Lee! Finally I accomplished to clean my messy repository.
The pull request is ok now (without undesired commits).
I hope don't repeat it again, sorry :)
Regards
2011/9/24 Lee Hambley <
<EMAIL_ADDRESS>
Can you interactively rebase this branch please @rgo? When it's one single
commit I can pull it then quite easily.
--
Reply to this email directly or view it on GitHub:
https://github.com/capistrano/capistrano/pull/50#issuecomment-2186564

Can you link some documentation, even if it's a simple wiki page with usage steps?

Ok, I'll write something.

I wrote a wiki page to document the usage:
https://github.com/rgo/capistrano/wiki/Ticket-193---alias_task-method


Offload all possible errors to cairo

Closes ##1896
Introduced changes

Offload all possible errors to cairo

Are there any possible tests to prove that it's working?

Every where Got an exception while executing a hint: Hint Error: was removed. If you see some case how we can extra text this i will add it. @Arcticae

Are there any possible tests to prove that it's working?

Every where Got an exception while executing a hint: Hint Error: was removed. If you see some case how we can extra text this i will add it. @Arcticae

Anywhere where we can verify that in fact the logic that was added is working, i.e. when testing i/o we can test for the non-existing file error being passed down to cairo. Rest of cases is up to you.


Car 9732

Fix Date Interface. Related PR

@Averethel Date is the type of lastServiceDate, lastInspectionDate and firstRegistrationDate and for all 3 it works as follow:

if only the year is filled, the month is set up to January by default
if only the month is filled, then we considered that there's no date at all and we return null
It's either this format { year: number, month: number }, or null
I tested it in both DH and listings and it worked fine but I'll ask QA to have a look before merging


How to run the codes in examples?

I create a test_native_spark project and copy codes in make_rdd.rs to the project's main.rs
Then run this project using cargo +nightly-2019-09-11 run got some errors:
thread 'main' panicked at 'Unable to open the file: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/libcore/result.rs:1165:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

How can I solve this?

First, Install Cap'n Proto
Then, run these following steps for local mode:(Tested only on Linux)
1. git clone https://github.com/rajasekarv/native_spark/
2. cd native_spark
3. copy hosts.conf file in config_files directory to your home directory. cp config_files/hosts.conf ~/hosts.conf
4. export SPARK_LOCAL_IP=<IP_ADDRESS>
5. cargo run --example make_rdd
Note: Initial build time can be very long. In my machine, it takes around 3 mins just for debug build.
If it is still not working, let me know.

It works.


Need "Add Content Type" button in the header

Should also settle on calling them "Content Type" anywhere they appear.

Fixed in 82c7a02dabeb94ba353519630a3eea1f5cbca70d


Update config.yml for workshop schedule doc

made a new folder and copied and updated the old doc for this version of the code-a-thon
https://docs.google.com/document/d/1ZD-w0vc3Vtv1vf95h6323zaaxORg9vC7Hp4I_IUeW0I/edit?usp=sharing

@avahoffman wanted to make sure you are ok with my update


Investigate using TypeScript for Non Exhaustive checks

https://basarat.gitbooks.io/typescript/docs/types/discriminated-unions.html
(scroll down a bit)
Currently else {throw "Non Exhaustive Check"} is manually thrown a lot in the code.
This causes issues because TypeScript tends to omit comments between if/else blocks
which makes ignoring those lines code coverage reports hard.

This wont fit all scenarios and the coverage related issues have already been resolved.


Unitary Events RuntimeWarning

Generating the plot for UEA occasionally results in multiple instances of the following warning:
RuntimeWarning: invalid value encountered in greater_equal
  sig_idx_win = numpy.where(Js_dict['Js'] >= Js_sig)[0]

To Recreate:
import elephant.unitary_event_analysis as ue
import numpy as np
import quantities as pq
from elephant.spike_train_generation import homogeneous_poisson_process as hpp
from viziphant import unitary_event_analysis

np.random.seed(10)

spiketrains1 = [hpp(10 * pq.Hz, t_start=0.0*pq.ms, t_stop=2000*pq.ms) for _
                in range(5)]
spiketrains2 = [hpp(50 * pq.Hz, t_start=0.0*pq.ms, t_stop=2000*pq.ms) for _
                in range(5)]

data = np.vstack((spiketrains1, spiketrains2)).T
winsize = 100 * pq.ms
bin_size = 5 * pq.ms
winstep = 20 * pq.ms
pattern_hash = [3]
ue_dict = ue.jointJ_window_analysis(data, bin_size, winsize,
                                    winstep, pattern_hash)

significance_level = 0.05
plot_params = {'events': {}}
fig = unitary_event_analysis.plot_ue(
    data, ue_dict, significance_level, bin_size, winsize,
    winstep, pattern_hash, plot_params
)

The issue was fixed in the v0.1 release but the fix introduced another bug that is fixed in #32.