WFCORE-1432 PersistentResourceXMLDescription#marshallAttributes does …

…not marshall defined values if they match default values
Jira
https://issues.jboss.org/browse/WFCORE-1432
Blocks
https://issues.jboss.org/browse/JBEAP-3773

Core - Full Integration Build 2831 outcome was FAILURE using a merge of 5a34214d64a312d098030bdc6785c3c06c91ef98
Summary: Tests failed: 1 (1 new), passed: 3307, ignored: 194 Build time: 01:03:35
Failed tests
org.jboss.as.test.integration.domain.mixed.eap640.DomainHostExcludes640TestCase: org.jboss.as.test.integration.management.util.MgmtOperationException: Management operation failed.
	at org.jboss.as.test.integration.domain.management.util.DomainTestUtils.executeForResult(DomainTestUtils.java:160)
	at org.jboss.as.test.integration.domain.mixed.DomainHostExcludesTest.readChildrenNames(DomainHostExcludesTest.java:302)
	at org.jboss.as.test.integration.domain.mixed.DomainHostExcludesTest.stopSlave(DomainHostExcludesTest.java:111)
	at org.jboss.as.test.integration.domain.mixed.DomainHostExcludesTest.setup(DomainHostExcludesTest.java:93)
	at org.jboss.as.test.integration.domain.mixed.eap640.DomainHostExcludes640TestCase.beforeClass(DomainHostExcludes640TestCase.java:40)
------- Stdout: -------
[Host Controller]  [0m [0m01:06:50,894 INFO  [org.jboss.as.domain.controller] (management task-5) WFLYHC0026: Unregistered remote slave host "slave" [0m
 [0m01:07:08,043 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
 [0m [0m01:07:08,172 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
 [0m[Host Controller]  [0m01:07:08,676 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final [0m
[Host Controller]  [0m [0m01:07:08,896 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final [0m
[Host Controller]  [0m [0m01:07:08,943 INFO  [org.jboss.as] (MSC service thread 1-4) WFLYSRV0049: WildFly Full 10.1.0.Final-SNAPSHOT (WildFly Core 2.1.0.CR3-SNAPSHOT) starting [0m
[Host Controller]  [0m [0m01:07:09,533 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'permgen-size' in the resource at address '/host=master/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. [0m
[Host Controller]  [0m [0m01:07:09,534 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'max-permgen-size' in the resource at address '/host=master/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. [0m
[Host Controller]  [0m [0m01:07:09,615 INFO  [org.xnio] (MSC service thread 1-3) XNIO version 3.3.5.Final [0m
[Host Controller]  [0m [0m01:07:09,626 INFO  [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.3.5.Final [0m
[Host Controller]  [0m [0m01:07:09,644 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1) [0m
[Host Controller]  [0m [0m01:07:09,723 INFO  [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 4.0.18.Final [0m
[Host Controller]  [0m [0m01:07:09,778 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) WFLYRMT0001: Listening on [::1]:9999 [0m
[Host Controller]  [0m [0m01:07:11,115 INFO  [org.jboss.as.connector] (Controller Boot Thread) WFLYJCA0093: The 'enable' operation is deprecated. Use of the 'add' or 'remove' operations is preferred, or if required the 'write-attribute' operation can used to set the deprecated 'enabled' attribute [0m
[Host Controller]  [0m [0m01:07:11,170 INFO  [org.jboss.as.connector] (Controller Boot Thread) WFLYJCA0093: The 'enable' operation is deprecated. Use of the 'add' or 'remove' operations is preferred, or if required the 'write-attribute' operation can used to set the deprecated 'enabled' attribute [0m
[Host Controller]  [0m [0m01:07:11,195 INFO  [org.jboss.as.ejb3] (Controller Boot Thread) WFLYEJB0486: Parameter 'default-clustered-sfsb-cache' was defined for the 'add' operation for resource '/profile=ha/subsystem=ejb3'. This parameter is deprecated and its previous behavior has been remapped to attribute 'default-sfsb-cache'. As a result the 'default-sfsb-cache' attribute has been set to '"clustered"' and the 'default-sfsb-passivation-disabled-cache' attribute has been set to '"simple"'. [0m
[Host Controller]  [0m [0m01:07:11,216 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'default-stack' in the resource at address '/profile=ha/subsystem=jgroups' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. [0m
[Host Controller]  [0m [0m01:07:11,245 INFO  [org.jboss.as.connector] (Controller Boot Thread) WFLYJCA0093: The 'enable' operation is deprecated. Use of the 'add' or 'remove' operations is preferred, or if required the 'write-attribute' operation can used to set the deprecated 'enabled' attribute [0m
[Host Controller]  [0m [0m01:07:11,272 INFO  [org.jboss.as.connector] (Controller Boot Thread) WFLYJCA0093: The 'enable' operation is deprecated. Use of the 'add' or 'remove' operations is preferred, or if required the 'write-attribute' operation can used to set the deprecated 'enabled' attribute [0m
[Host Controller]  [0m [0m01:07:11,273 INFO  [org.jboss.as.ejb3] (Controller Boot Thread) WFLYEJB0486: Parameter 'default-clustered-sfsb-cache' was defined for the 'add' operation for resource '/profile=full-ha/subsystem=ejb3'. This parameter is deprecated and its previous behavior has been remapped to attribute 'default-sfsb-cache'. As a result the 'default-sfsb-cache' attribute has been set to '"clustered"' and the 'default-sfsb-passivation-disabled-cache' attribute has been set to '"simple"'. [0m
[Host Controller]  [0m [0m01:07:11,297 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'default-stack' in the resource at address '/profile=full-ha/subsystem=jgroups' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. [0m
[Host Controller]  [0m [0m01:07:11,329 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'max-permgen-size' in the resource at address '/server-group=main-server-group/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. [0m
[Host Controller]  [0m [0m01:07:11,329 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'max-permgen-size' in the resource at address '/server-group=other-server-group/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. [0m
[Host Controller]  [0m [0m01:07:11,609 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://[::1]:9990/management [0m
[Host Controller]  [0m [0m01:07:11,609 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled [0m
[Host Controller]  [0m [0m01:07:11,609 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final-SNAPSHOT (WildFly Core 2.1.0.CR3-SNAPSHOT) (Host Controller) started in 3348ms - Started 44 of 47 services (14 services are lazy, passive or on-demand) [0m
INFO  [org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil] HostController started in 4170 ms
[Host Controller]  [0m [0m01:07:12,693 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 10.1.0.Final-SNAPSHOT (WildFly Core 2.1.0.CR3-SNAPSHOT) stopped in 57ms [0m
[Host Controller]  [0m [0m01:07:12,694 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 10.1.0.Final-SNAPSHOT (WildFly Core 2.1.0.CR3-SNAPSHOT) starting [0m
[Host Controller]  [0m [0m01:07:12,760 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'permgen-size' in the resource at address '/host=master/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. [0m
[Host Controller]  [0m [0m01:07:12,761 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'max-permgen-size' in the resource at address '/host=master/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. [0m
[Host Controller]  [0m [0m01:07:12,763 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1) [0m
[Host Controller]  [0m [0m01:07:12,850 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) WFLYRMT0001: Listening on [::1]:9999 [0m
[Host Controller]  [0m [0m01:07:13,007 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'default-stack' in the resource at address '/profile=ha/subsystem=jgroups' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. [0m
[Host Controller]  [0m [0m01:07:13,033 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'default-stack' in the resource at address '/profile=full-ha/subsystem=jgroups' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. [0m
[Host Controller]  [0m [0m01:07:13,048 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'max-permgen-size' in the resource at address '/server-group=main-server-group/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. [0m
[Host Controller]  [0m [0m01:07:13,048 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'max-permgen-size' in the resource at address '/server-group=other-server-group/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. [0m
[Host Controller]  [0m [0m01:07:13,190 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://[::1]:9990/management [0m
[Host Controller]  [0m [0m01:07:13,190 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://[::1]:9990 [0m
[Host Controller]  [0m [0m01:07:13,190 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final-SNAPSHOT (WildFly Core 2.1.0.CR3-SNAPSHOT) (Host Controller) started in 494ms - Started 44 of 47 services (14 services are lazy, passive or on-demand) [0m
 [0m01:07:13,551 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.6.Final-redhat-1
 [0m [0m01:07:13,663 INFO  [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
 [0m[Host Controller]  [0m01:07:14,216 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.6.Final-redhat-1 [0m
[Host Controller]  [0m [0m01:07:14,348 INFO  [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1 [0m


fix(fuselage): Using Pre Wrap For System Message

Proposed changes (including videos or screenshots)
Before :

After :

reason of change :  https://github.com/RocketChat/Rocket.Chat/pull/27080

Issue(s)

Further comments

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Can you add screenshots so we now how it changed visually? Also a description so we could understand the issue better would help. Thanks!

Done check now

Hey @nishant23122000 ! I'll be checking with design to see if this is the desired UI/UX for this. If we're all in agreement, I'll review the code and merge this.

Hello @nishant23122000, José from Rocket.Chat's design team here. I was wondering what prompted your need to work on longer system messages, in our experience they usually are no longer than 4 or 5 words. So we don't actually see a need for this particular improvement.
Either way I'm excited to find a solution to this problem in the coming releases, but this particular one doesn't agree with the spacing standards we set up for the platform. Hope you understand.

If words are less than 4 or 5 then it makes sense to don't do these changes.
but I think the agent can write long sentences also in some cases.

The UX problem, IMHO, is that the receiving agent will not have access to that comment in full, which is usually very important for the chat handling.
Isn't there a way to allow that message to be shown, like on mouse hover?


Decrement _openRequests when mimetype isn't supported

Fixes #144. Big problem, small solution. The indefinite hangup of the crawler was due to the fact that I had flipped downloadUnsupported to false (and this problem was triggered in that case).

As a sidenote, it seems this issue was introduced in b00e91b5e56372900877d99374cf252944878805

Oh, wow. headdesk
Sorry about causing you so much hassle — and thanks for finding the issue! I see you've got a good test there for replicating it. I'll try get it out to npm ASAP.

Haha that's ok! Happy to find that the root of the problem was something easy to fix. Yeah, it'd be great if you could ping me once you've published!


fix(tearsheet): resolve disabled first element focus issue

Closes #5819
What did you change?
Implemented check to verify the element is not disabled or display: none.
How did you test and verify your work?
Storybook

@matthewgallo bump


Production DOM loaded about 2 seconds on Heroku

Changes Unknown when pulling 1a3ab59d48f56b23bbb366beaae1760d4b497e49 on master into ** on production**.


Increase lint deadline to 10min

What type of PR is this?
/kind failing-test
What this PR does / why we need it:
This should address the failing macos GitHub action.
Which issue(s) this PR fixes:

None
Does this PR have test?
None

Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

Codecov Report

Merging #1614 (68f9db8) into main (8f8b217) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1614   +/-   ##
=======================================
  Coverage   48.65%   48.65%
=======================================
  Files          69       69
  Lines        6785     6785
=======================================
  Hits         3301     3301
  Misses       3353     3353
  Partials      131      131

@kubernetes-sigs/security-profiles-operator-maintainers PTAL


[第三章] 第92页 关于impl 特化

页码与行数:

第92-93页

代码清单 3-78:(随书源码)
#![feature(specialization)]
struct Diver<T> {
    inner:T
}
trait Swimmer {
    fn swim(&self){
        println!("swimming")
    }
}
impl<T> Swimmer for Diver<T>{}
impl Swimmer for Diver<&'static str> {
    fn swim(&self){
        println!("drowning, help!")
    }
}
fn main(){
    let x = Diver::<&'static str> { inner: "Bob" };
    x.swim();    //drowning, help!
    let y = Diver::<String> { inner: String::from("Alice") };
    y.swim();    // swimming
}

错误信息:
   Compiling playground v0.0.1 (/playground)
error[E0520]: `swim` specializes an item from a parent `impl`, but that item is not marked `default`
  --> src/main.rs:12:5
   |
10 |   impl<T> Swimmer for Diver<T>{}
   |   ------------------------------ parent `impl` is here
11 |   impl Swimmer for Diver<&'static str> {
12 | /     fn swim(&self){
13 | |         println!("drowning, help!")
14 | |     }
   | |_____^ cannot specialize default item `swim`
   |
   = note: to specialize, `swim` in the parent `impl` must be marked `default`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0520`.
error: could not compile `playground`.

To learn more, run the command again with --verbose.

修改为如下:
#![feature(specialization)]
struct Diver<T> {
    inner:T
}
trait Swimmer {
    //如果是impl 特化, 此方法始终不会运行
    //fn swim(&self){
    //    println!("swimming")
    //}

    fn swim(&self);
}
impl<T> Swimmer for Diver<T>{
    //必须存在此default fn
    default fn swim(&self){
        println!("swimming")
    }
}
impl Swimmer for Diver<&'static str> {
    fn swim(&self){
        println!("drowning, help!")
    }
}
fn main(){
    let x = Diver::<&'static str> { inner: "Bob" };
    x.swim();    //drowning, help!
    let y = Diver::<String> { inner: String::from("Alice") };
    y.swim();    // swimming
}

在线测试

@jellybobbin 感谢反馈


Disabling Body Scroll on 'touchstart'

Hi,
I am looking to implement this when using the 'touchstart' rather than click.
Is this currently supported? As it doesn't seem to work for me on iOS Mobile Safari?
(iPad/Android seems to be ok in this case)
Kind regards,
Tom

I'm not sure i get your use case. touchstart on what element exactly?

Hi,
I ended not using the functionality in the end, but this was roughly the code I was trying to use:
(I think I got confused over the intended purpose of the package as I wasn't using it on a scrollable element, but was still trying to get the body to lock during a touch event)
$(document).on("touchstart", ".choose-reaction-btn", function (event) {     if ($(event.target).hasClass('touch-choose-reaction') && !iOS) {         // Prevent page scrolling while selecting reaction         var targetElement = document.querySelector('.choose-reaction-btn');         disableBodyScroll(targetElement);     ...     } });
Other browsers were working fine using disableBodyScroll within a touchstart but iOS Safari seemed not to like it.
Cheers,
Tom


Update to miniaudio v0.10.4

This is the minimal change to update to v0.10.4.
There seems to be quite a bit of unsafe.Pointer violations here that probably should be fixed, but I avoided the large scale changes in this update.

Great, many thanks!


How do I scroll through the page when my content exceeds the page size in BMView

Hi,thanks for the widget first,i have some questions when i use the BMview widget.
How do I scroll the page when I have more content than the size of the page, and now I have a situation where the content is not complete, and I can't scroll the page.

The basic view widget doesn't do scrolling at all. The solution is to use a scroll view if you expect scrolling might be required.
I will close this and instead focus on the separate issue you opened on scroll view.

ok,thanks


Japanese examples use simplified Chinese hanzi

It's hard to read if you only know Japanese.

Thanks for your suggestion.


Test suite

Currently the testing process of the application is not automated enough to catch possible invalid code. This might causes serious stability issue on the application when used in production.
Current plan:

[x]  Having automated test suite for invalid data in Database
[x]  Having automated test suite to test database engine operations
[x]  Having tests to test critical internal utilities

cleared


JScrollbar mouse hover problem

@vincenzopalazzo
I just noticed that the problem still exists that was fixed here:
https://github.com/atarw/material-ui-swing/issues/75
But this time it is for JScrollbar

Hi @Reap00r,
Thanks the problem is the border button, I have not noticed this before, sorry I will correct as soon as you give me more info on #73  so as to correct both

@Reap00r I hope this bug no longer exists :)

@vincenzopalazzo,
unfortunately your fix did not completely remove this bug, see the GIF

Maybe this is related to Windows / Linux again

Hi @Reap00r,
Sorry for this problem, I was not able to reproduce this error and so I didn't know what nature it was, I made the same changes that I had placed in the previous components but I see that it wasn't enough.
Sorry if I can't give you a pull request where all the problems are solved, I'll work on it.
Sorry

Hi @Reap00r,
Before running the pull request can you test if the bug has been fixed with this version?
https://github.com/vincenzopalazzo/material-ui-swing/releases/tag/V9.9
This is an example my fix

Hi @vincenzopalazzo,
I just downloaded v9.9 and it is still not fixed.
I can see in your example that is seems to work, but unfortunately not for me :/
Could it be related to the color of the button (mine is blue and the border around the scrollbar turns blue as well)

@Reap00r,
Very probable that the bug is not in the jscrollbar but in the mouse hover effect, I will try to look at the code and propose a new solution, unfortunately when I release the solution you'll have to act as a tester :) since I can't reproduce your error on Windows and Linux.

Hi @vincenzopalazzo,
no problem. Just tell me when you got an update and I will test it asap ;)

Hi @Reap00r,
I released another fix for this problem, I introduce a new component MaterialUIStaticMoviment , this component haven't a wake effect, it was thought for the effect mouse hover on the button for component static, an example: JSpinner, JScrollBar, KComboBox.
The version fixed (I hope)
I attend your feedback for creating an official pull request :)

Hi @vincenzopalazzo,
unfortunately this is still not fixed. I didn't have a closer look into the code changes, but I saw that you added a swing set to your new version. Would this be necessary for the fix?
See my test results here:

@atarw can you reopen this issue, please?
Hi @Reap00r,
The swing set is the first version demo for this theme, it's not necessary for the function od the look and feel.
Before refactoring the code I would like to ask you about things, in this version a good rule was introduced, before creating new effects with MaterialUIMoviment you have to clean up all the listeners.
So I will now ask you if you have added new effects to any buttons because if it were so could you kindly use this code before adding the mouse hover effect to the button?
MaterialManagerListener. removeAllMouseListener(yourButton); buttonWarning.addMouseListener(MaterialUIMovement.getMovement(yourButton, MaterialColors.YOUR_COLOR));
if you added the listener whit MaterialUiMovement, try this code.
I attend your feedback

Hi @vincenzopalazzo,
at first I pulled the latest changed and tried the new version but it still didn't work.
Now I tried a few things:
At first, this is the current version:

Now I removed the All the mouse listeners as you mentioned (WITHOUT adding one)

Now I removed them and added one

I hope that helps

Thanks, @Reap00r,
in this example, the effect is wrong, right?

Now I removed the All the mouse listeners as you mentioned (WITHOUT adding one)

Thanks for this example and another question, you have change a color mouse hover with the LITE_BLUE? if you change the mouse hover color on button into equals color mouse hover JScroll bar you have a Effect OK, right?

Hi @vincenzopalazzo,
in all of my examples the effect is wrong. it should stay gray without the strange border.
Even changing the button hovercolor to grey, it still get partly painted in blue (maybe cause of the normal color of the button)

@Reap00r I repaint new border, try this version and if it's work I will create a pull request
This is version https://github.com/vincenzopalazzo/material-ui-swing/releases/tag/V9.9

Hi @vincenzopalazzo,
I tried your version and it still doesn't work unfortunately. In my test I didn't remove all the mouse listeners, because I wouldn't be able to handle this in my project.

Hi @Reap00r,
I added new change, you try it https://github.com/vincenzopalazzo/material-ui-swing/releases/tag/V9.9
if the error persists, I will create a version for debugging your application so by analyzing the output we will be able to understand what's wrong, in the meantime I have removed the BasicButtonArrow and I set the icons manually, try and let me know

Hi @vincenzopalazzo,
just to be sure I am doing this stuff right. When I click on the link you provided, I see this:
vincenzopalazzo released this 11 days ago
Now when I download your asset (material ui design), is this the latest version?
Since I was not sure about that I cloned your project and build the version myself today in the morning.
Now I tried to pull and build it myself but there were no changes that I could pull.
Thanks for helping me figuring that out

The jar should be the one I loaded, but to avoid working on projects that are not up to date I will now commit the latest version, which you can easily build the jar with maven

Hi @Reap00r,
The jar should be the one I loaded, but to avoid working on projects that are not up to date I will now commit the latest version, which you can easily build the jar with maven

@Reap00r the version are online, I attend your feedback :)

@vincenzopalazzo,
hopefully I wasn't the problem all along.
I just saw that I used your fixedsomeissue branch and not the master and maybe that's the reason why your changes didn't work.. maybe because they were not in my version?!
Well.. anyway.. with the master branch it is WORKING :D
Great work and thanks for your help as always!

Now I Creating a pull request, the pull request resolve this problem, @atarw can you close this issue, please?


New package: JanFiala.PSPad.507.64b version <IP_ADDRESS>5

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hi @JaFi-cz,
Should this manifest be merged with #151446 to create a single manifest, utilizing the Architecture parameter to specify which installer to use? Or is it possible to install these versions side by side?
Should the version number be in the PackageIdentiifer? This is common when different versions can be installed side by side, similar to the above scenario.
What are your thoughts? Should a single manifest for JanFiala,PSPad be added instead of these 2 manifests?

Hello
Both packages is possible install side by side so please keep it separatelly
Version number can be in the package identifier if it is common praxis
Jan Fiala
Dne po 29. 4. 2024 16:58 uživatel Stephen Gillie @.***>
napsal:

Hi @JaFi-cz https://github.com/JaFi-cz,
Should this manifest be merged with #151446
https://github.com/microsoft/winget-pkgs/pull/151446 to create a single
manifest, utilizing the Architecture parameter to specify which installer
to use? Or is it possible to install these versions side by side?
Should the version number be in the PackageIdentiifer? This is common when
different versions can be installed side by side, similar to the above
scenario.
What are your thoughts? Should a single manifest for JanFiala,PSPad be
added instead of these 2 manifests?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/winget-pkgs/pull/151450#issuecomment-2082969356,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT5VHKXZUPUNLH7D7KXHXQTY7ZNYJAVCNFSM6AAAAABG53JMLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBSHE3DSMZVGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@stephengillie - This commit introduces casing conflicts with JanFiala.PSpad and needs to be reverted, as it breaks Git commands


Minor issues in the dictionary part in /13-constrained-optimization.ipynb

In the dictionary part, I think it should be 10 and not 0 in the comment, or vice-versa:
d.get("NotHere", 10)  # 0 is the alternative, you can choose anything that makes sense
There is also a small typo in "alternative" in the sentence before this cell.

Thanks!


How to compute logits output in parallel for all the input sequence?

This is the code I run:
from ctransformers import AutoModelForCausalLM, AutoTokenizer
model = AutoModelForCausalLM.from_pretrained("TheBloke/LLaMa-7B-GGML", hf=True)
tokenizer = AutoTokenizer.from_pretrained(model)

tokens = tokenizer.encode("Hello world! What's up?")
output = model(tokens[None,:])

I got output[0].shape = torch.Size([1, 32000])
I was expecting to get output.logits.shape = torch.Size([1, 7, 32000])
Witch is what I got when I run model from huggingface library.
I dont want exactly the same behavior as hugging face, I just want to get the logits of all the tokens at ounce, instead of having only the next token of the sequence.
There's any way to do that with this library?

There is at least one hacky way:
import torch
from transformers import AutoTokenizer
from ctransformers import AutoModelForCausalLM

model = AutoModelForCausalLM.from_pretrained("marella/gpt-2-ggml", hf=True)
tokenizer = AutoTokenizer.from_pretrained("gpt2")

text = "a b c d"  # exactly 4 tokens

input_ids = tokenizer.encode(text, return_tensors="pt")[0]
logits = []
for i in range(1, 1 + len(input_ids)):
    tokens = input_ids[:i]
    logits.append(model(tokens[None, :], return_dict=True).logits)
logits = torch.cat(logits, dim=1)

assert logits.shape == (1, len(input_ids), tokenizer.vocab_size)

I'm not yet familiar w/ the backend of GGML or ctransformers. But I'm pretty sure it's super slow b/c it re-computes a lot. Maybe there's a way to avoid that?

Noted with Thank @kddubey


Add Armada-based kind k8s cluster deploys

Support Armada-abstracting-kind k8s cluster deployments in CI.
Allows us to use Armada for multicluster management and custom
networking, vs duplicating common bash between many repositories.
Defaults to using Armada, but keeps the old bash-based logic for now. It
can be removed once we have confidence enough to fully move to Armada.
Can also be removed in a distinct commit to make it easy to revert.
Closes #291
Signed-off-by: Daniel Farrell<EMAIL_ADDRESS>

@dfarrell07 ping

That's twice now that the Helm job has failed, then passed when retriggered. :\

Checking runtimes, don't merge yet

@mkolesnik we are kind of blocked on this PR for overlapping cidrs use-case. I understand your concern regarding the runtime. Since we are not deleting the existing bash installation, can we get this PR in and in-parallel work on improving/fixing the deployment time?

@mkolesnik can you revisit your vote if you think it's ok to go on with armada?

@mkolesnik talking with @tpantelis, @mangelajo, @skitt, @sridhargaddam, @manosnoam, @aswinsuryan and others about the de-duplication effort (including Go vs Bash Armada-esque logic), my summary of the relevant bits:

Go is easier to test and maintain than Bash.
The current Go-based implementation is much more flexible than the current Bash-based implementation. For example, it can deploy any number of nodes with any combination of CNIs and other extras.
The current Go-based implementation has support for deploying with overlapping CIDRs, which is needed quickly by others. That feature would have to be added to the Bash-based logic.
We don't expect significant performance differences between the two implementations, as the costly steps are similar. Either implementation will need refactoring in that regard.

IMHO let's merge this ASAP, making it easier for myself and others to do related follow-up work.

Really sorry guys I was out sick most of last week and didn't even touch the computer.
What I observed is that the time is more or less the same, BASH is much less complex, and armada is much more taxing on the machine (one run caused load to go to 50x, i.e. 5000% CPU utilization).
I was working on an alternative to improve the bash scripts deployment to make it more maintainable and extendible. Since I was sick I didn't have time to continue on it most of last week, but I pushed it as PR #425 so that you can take a look.
I was rooting for Armada, but replacing ~80 lines of bash code with ~3000 lines of go code (and many hundreds of YAML lines) won't make it better IMHO. The main promise of Armada was to improve the build, and I feel it didn't deliver.
BTW regarding the local registry I think regardless of bash/armada we should check out this possibility to reduce the build time and perhaps make the whole build even simpler.
Let's discuss this a bit further before we push a whole bunch of complicated code that doesn't add much benefit.

I was rooting for Armada, but replacing ~80 lines of bash code with ~3000 lines of go code (and many hundreds of YAML lines) won't make it better IMHO. The main promise of Armada was to improve the build, and I feel it didn't deliver.

From my perspective and understanding, the main purpose of armada was for de-duplication.

I was working on an alternative to improve the bash scripts deployment to make it more maintainable and extendible. Since I was sick I didn't have time to continue on it most of last week, but I pushed it as PR #425 so that you can take a look.

Some nice ideas there, but I'm concerned that we're continuing to develop both implementations, vs making a decision and focusing on one. For example, your work to make the create nginx/netshoot functions generic is already implemented as armada deploy netshoot nginx-demo in Armada. The work to refactor the create_kind_cluster function would also become obsolete.

I was rooting for Armada, but replacing ~80 lines of bash code with ~3000 lines of go code (and many hundreds of YAML lines) won't make it better IMHO.

We've talked about this concern quite a lot, and it seems there's more nuance. Using Go certainly does add more code, but it also seems to make the code more flexible, maintainable and testable. I tried to summarize some of those thoughts above, but here are a few more:

Most of the Go-based Armada code is actually test code that adds substantial coverage not provided by the Bash path.
A substantial additional chunk of the additional LoC are related to the proper command structure of Go-based Armada, which isn't a feature currently provided in Bash. It'd take a lot of scripting around the Bash control flow (already overly complex) to do more than our current static/prescribed deployments. This flexibility out-of-the-box with Go-based Armada would enable devs to easily add scenarios, ie scale deployments or mixed-feature deployments.
From what I see of the YAML, it's either providing a feature not provided by Bash (Calico, Flannel) or already exist in the Bash path (Netshoot, Nginx, Weave).

The main promise of Armada was to improve the build, and I feel it didn't deliver.

As @tpantelis said and we talked about quite a lot last week, the consensus seems to be that the goal of "Armada" in the architure is to de-duplicate managing multicluster deployments in CI. The question is how to best architect that. The current ideas are basically:

Refactor the Bash-based "Armada" to be generic/flexible enough to be used in all submariner-io/* deployment needs. Share that Bash in CI, likely via the dapper-base image.
Extract all the "deploying K8s multiclusters with kind" logic into Go-based Armada (as is already done). Share and consume in CI parallel to the current use of subctl for the Submariner abstraction layer. Very simple Bash scripting to basically pass params from the Makefile to Armada.

Finally, I'll highlight that at least having Go-based Armada as an option would unblock a substantial number of PRs that have been waiting on this one to go in.

I was working on an alternative to improve the bash scripts deployment to make it more maintainable and extendible. Since I was sick I didn't have time to continue on it most of last week, but I pushed it as PR #425 so that you can take a look.

Some nice ideas there @mkolesnik, but I'm concerned that we're continuing to develop both implementations, vs making a decision and focusing on one. For example, your work to make the create nginx/netshoot functions generic is already implemented as armada deploy netshoot nginx-demo in Armada. The work to refactor the create_kind_cluster function would also become obsolete.

Yes though my patch turns it into a generic 5 line function (first 4 lines are more for clarity than actual logic) which can deploy anything.
The armada, OTOH, has dedicated "command" which are specific to "netshoot" and "nginx" and are 100s of LOC. Say you want to deploy another thing, mysql, then what would you do? Add 100s more lines for such a command?

I was rooting for Armada, but replacing ~80 lines of bash code with ~3000 lines of go code (and many hundreds of YAML lines) won't make it better IMHO.

We've talked about this concern quite a lot, and it seems there's more nuance. Using Go certainly does add more code, but it also seems to make the code more flexible, maintainable and testable. I tried to summarize some of those thoughts above, but here are a few more:

Using go also adds a lot of boierplate code, don't forget.

* Most of the Go-based Armada code is actually test code that adds substantial coverage not provided by the Bash path.

If you test needless functions, is that test really worth something?

* Another substantial chunk of the additional LoC is related to the proper command structure of Go-based Armada, which isn't a feature currently provided in Bash. It'd take a lot of scripting around the Bash control flow (already overly complex) to do more than our current static/prescribed deployments. This flexibility out-of-the-box with Go-based Armada would enable devs to easily add scenarios, ie scale deployments or mixed-feature deployments.

Which is overkill right now for the bash, but can be added with not so much effort should we actually decide we need it.

* From what I see of the YAML, it's either providing a feature not provided by Bash (Calico, Flannel) or already exist in the Bash path (Netshoot, Nginx, Weave).

Yes as I said there's a lot of YAMLs there as well with logic hidden in them, it's not better of worse than the bash, except for all those "features" that you mentioned that we aren't actually even using.

The main promise of Armada was to improve the build, and I feel it didn't deliver.

As @tpantelis said and we talked about quite a lot last week, the consensus seems to be that the goal of "Armada" in the architure is to de-duplicate managing multicluster deployments in CI. The question is how to best architect that. The current ideas are basically:

From my many discussions with Dima on this project, he emphasized the "time saving" as one of the key features in Aramada.

1. Refactor the Bash-based "Armada" to be generic/flexible enough to be used in all submariner-io/* deployment needs. Share that Bash in CI, likely via the dapper-base image.

2. Extract all the "deploying K8s multiclusters with kind" logic into Go-based Armada (as is already done). Share and consume in CI parallel to the current use of `subctl` for the Submariner abstraction layer. Very simple Bash scripting to basically pass params from the Makefile to Armada.

On this one I agree, deduplication can be either done solely in bash (and probably on the dapper image level as you suggest) or in Armada. Though in the end you'll still have a bash wrapper that you'll need to (possibly) use everywhere as well, so not sure how much it really saves us.

Finally, I'll highlight that at least having Go-based Armada as an option would unblock a substantial number of PRs that have been waiting on this one to go in.

Do you have a list of them?

After extensive discussions (and this prototyping work, to show the details) with @tpantelis, @mkolesnik and many others, we decided not to go with Go-based Armada.


handler description & help

I would find it useful if the handlers introduced with #89 had an option to set a description and a category.
This would mean that you could automatically generate a 'help' handler.
The main problem that I see is that adding more arguments to the Handle func would be a breaking change (but on the other hand it's not that bad as the handler was only introduced 5 days ago).

Automatic /help handler is a sound idea very much indeed. That said, I find myself implementing /help differently every single time. Sometimes you want to have some sort of a FAQ, sometimes it's just a brief explanation of core mechanics, but usually you don't want it auto-generated.
I also believe that such auto-generated /help implementation must also account for Telegram's recent i18n support (see language_code within User) and at this point I can't really tell whether such feature is worth it.

adding more arguments to the Handle func would be a breaking change

Not necessarily. Handle is a set-up function and isn't supposed to be used heavily (only a handful of times, during the bot init process), we can rely on reflection to add "optional" arguments:
// Definition
func (b *Bot) Handle(prefix string, features ...interface{}) {}

// Uses
bot.Handle("/action", func (c Context) {})
bot.Handle("/action", "Description", func (c Context) {})

Closing for the time being.


[MINOR][CORE] Renamed long URL with shortened version

What changes were proposed in this pull request?
We found that Scalastyle was disabled in BlockReplicationPolicy.scala because there was a URL in there that caused the line length to be exceeded. The URL was to a stackexchange.com site which actually accepts shortened versions of their normal URL as well. So we could replace the URL with the officially supported shortened version and enable Scalastyle again since this no longer exceeds the line length. I also changed the URL from http to https since the site automatically redirects to https anyway.
How was this patch tested?
We tested this by running ./dev/lint-scala. First we ran it with the long URL to ensure that it actually detects the violation. Then we changed this to the shortened URL and ran it again. This time it said Scalastyle checks passed.
Co-contributors:
@chialun-yeh
@Hrayo712
@vpourquie

Can one of the admins verify this patch?

Can one of the admins verify this patch?

This change has been included in #20880 so a separate PR isn't necessary for it.


PLAT-78104: Fix Input refocusing on touch on iOS

Checklist

[X] I have read and understand the contribution guide

[X] A CHANGELOG entry is included

[ ] At least one test case is included for this feature or bug fix

[X] Documentation was added or is not needed

[ ] This is an API breaking change

Issue Resolved / Feature Added
Regression from #2187 in which the pointer lock thought it was capturing focus when tapping off of an input but wasn't properly cleaned up because iOS doesn't issue a click event if the target of the tap isn't focusable.
Resolution
Add a touchend handler to ensure we clean up properly.

I'm seeing the same. Thanks for the report!

I think it's fixed up. I added preventDefault to the handleTap handler. For click events, it shouldn't have any effect (afaik) but for touchend it will prevent dispatching a click event in Chrome which "reopens" the ExpandableInput in the same update cycle.


Adds support for MCD12Q1 landcover

Description
Added support for reading MODIS IGBP landcover (MCD12Q1) within LDT that can now use annual landcover datasets

Testcase
/discover/nobackup/projects/eis_freshwater/sahmad3/LIS_AMAZON/LDT_LCchange_TESTCASE

Good morning @sahmad3
Can you provide a test case for this new capability?

@emkemp sorry it took a bit long, here's the test case for this capability: /discover/nobackup/projects/eis_freshwater/sahmad3/LIS_AMAZON/LDT_LCchange_TESTCASE

Hi @sahmad3
I don't see any output in the testcase directory, just input.  Can you please rerun your test case and add the lis_input.*.nc file so we can compare?

PING
Hi @sahmad3
I don't see any output in the testcase directory, just input. Can you please rerun your test case and add the lis_input.*.nc file so we can compare?

Hi @emkemp
Apologies! Due to some reason, I kept missing these messages. I just ran the test case and added the lis_input* there (/discover/nobackup/projects/eis_freshwater/sahmad3/LIS_AMAZON/LDT_LCchange_TESTCASE).
Please let me know if any other file is needed for comparison.

Hi @sahmad3
I have compiled your code with the intel compiler and have run your testcase.  Can you give me permission to access /discover/nobackup/projects/eis_freshwater/sahmad3/LIS_AMAZON/LDT_LCchange_TESTCASE/lis_input_AmazonExtn_2001.nc so I can compare our output?
Assuming I can replicate your output, before merging, there are three other things that will need to be taken care of:

I receive an error when I compile your code with the gnu compiler.   I will message you off github so we can find a time to take a look.
Documentation in ldt.config.adoc needs to be updated to reflect the new Landcover data source: parameter, MCD12Q1.
The minor conflict in LDT_param_pluginMod.F90 will need to be resolved.  I need to consult with Jim on how best to handle that.

Thanks!

Hi @cmclaug2
I opened the permission to the lis_input.  Let me know if you want me to update the documentation with this change.
Thanks for your help!

Hi @sahmad3,
Thank you!  I confirm I was able to replicate your lis_input*.nc file.
Yes, can you please update the documentation to reflect the new support for MCD12Q1?

Hi @cmclaug2,
I added the MCD12Q1 landcover option to the doc. Because the .adoc file in my previous commit was outdated, I pulled the latest file and made changes there. Let me know if you see any issues there that need my attention.
Thanks!

This code compiles with intel and gnu compilers.  I am able to reproduce the testcase with the intel compiler.  I am able to nearly reproduce the testcase with the gnu compiler (with minor differences due to floating point calculations).
I accept this pull request.

Thanks @cmclaug2 for all your help!


[Document Intelligence] Add changelog and release updates

API change check
API changes are not detected in this pull request.


Added WebSocket router declerations

Added definitions for WebSocket Router.
https://github.com/theturtle32/WebSocket-Node/blob/master/lib/WebSocketRouter.js
https://github.com/theturtle32/WebSocket-Node/blob/master/lib/WebSocketRouterRequest.js

@joshheyse Thanks mate!


Presentation-specific behaviors do not appear in manifest flat GET

When you POST a new manifest to /manifests, the returned JSON will show a behavior field containing what was defined in the payload, like so:
  ...
  "modified": "2024-11-21T15:30:20Z",
  "createdBy": "Admin",
  "@context": [
    "http://tbc.org/iiif-repository/1/context.json",
    "http://iiif.io/api/presentation/3/context.json"
  ],
  "id": "https://presentation-api.dlcs.digirati.io/52/manifests/74nrg5qi9h4h3fqla2rq",
  "type": "Manifest",
  "label": {"en":["Example Manifest"]},
  "behavior": [
    "public-iiif",
    "paged"
  ],
  ...

But if you request GET on the same manifest's flat URL afterwards, any behaviour specific to Presentation (e.g public-iiif) will be omitted:
  ...
  "modified": "2024-11-21T15:30:20Z",
  "createdBy": "Admin",
  "@context": [
    "http://tbc.org/iiif-repository/1/context.json",
    "http://iiif.io/api/presentation/3/context.json"
  ],
  "id": "https://presentation-api.dlcs.digirati.io/52/manifests/74nrg5qi9h4h3fqla2rq",
  "type": "Manifest",
  "label": {
    "en": [
      "Example Manifest"
    ]
  },
  "behavior": [
    "paged"
  ],
  ...

Not a bug - Manifests shouldn't have these behaviours.

Reopened - the bug is that the custom items are returned in POST body, rather than them being missing from GET.
I will fix alongside #62


Update pin manifest digest step

The pinning step returns a dirty flag based on if there are any changes
in manifest references. The pinning step can be also skipped by setting
pipeline test_mode parameter.
JIRA: ISV-849

@amisstea @MarcinGinszt Please review

LGTM


Expand drag area on item coloums

What's the Problem?
Trying to change the width on item coloums really difficult as the drag area is very small

Solution/Idea
Widen the drag area
Alternatives

Priorities
No response
Files Version
No response
Windows Version
No response
Comments
No response

So i have notice it bigger then shown sometimes. When the columns not highlight it still dragable but the drag icon isnt shown. Other times it doesnt do it at all and others will have a good amount with the icon showing it can be draged.

Does this look good?

This issue should be resolved with #8947


page.setUserAgent is not a function when using Playwright

Describe the bug
Error thrown when using newInjectedPage with playwright.
To Reproduce
import { chromium } from 'playwright';

(async () => {
    const browser = await chromium.launch({ headless: false });
    const context = await newInjectedContext(
        browser,
        {
            fingerprintOptions: {
                devices: ['mobile'],
                operatingSystems: ['ios'],
            },
        },
    );

    const page = awai newInjectedPage(browser, {
      fingerprintOptions: {
        devices:          ['mobile'],
        operatingSystems: ['ios']
      }
    });

})();

Expected behavior
Execute as normally, injecting a fingerprint into the page.
System information:

OS: MacOS
Node.js version: v18.15.0

Additional context
newInjectedContext works fine.

Please note that the newInjectedPage function is for use with Puppeteer only. This is reflected in the function's type annotation - it shouldn't be possible to pass the Playwright browser instance to the method. With Playwright, use the newInjectedContext function instead.
I'll close this issue now as it's a wontfix, but I'll look into improving the documentation (and parameter validation), so the divide is more clear. Cheers!


Conda tree should default to current environment

The conda tree commands default to the root environment, even if another environment is currently activated. This feels a bit misleading:
$ conda activate myenv

<myenv> $ conda tree leaves
# shows root environment instead

<myenv> $ conda tree -n myenv leaves
# feels unnecessary, I already have the myenv environment activated

(Wonderful tool BTW!)

I agree ! I meant to do that for a while, but I always forget.
a new version should be built and released in the next days.

Great, thanks!


Putting the caret behind the character and pressing the enter causes the creation of an empty space at first

I do not know if the bug has been reported,
I searched but could not find,
The application I'm working on is very difficult to move here but I have worked a miniature application that summarizes the problem,
I hope you understand me well:

Expected Behavior

Make the caret behind the number 0
Press enter repeatedly until you reach the end of the window, you will notice the text stops descending (continue to press enter)
Select text from 0 to above You will notice that there is a large blank space due to pressing enter

Reproducible Demo
public class Bug extends Application {

 public void start(Stage primaryStage) {
        var area= new InlineCssTextArea();
        area.setPrefSize(400,600);
        var pane= new AnchorPane(area);
        var scene= new Scene(pane);
        for(var i=0;i<25;i++){
            area.appendText("\n");
            area.appendText(String.valueOf(i));
        }
        primaryStage.setScene(scene);
        primaryStage.show();
 }

}

Environment info:

RichTextFX Version: <0.9.0>
Operating System: <Windows 10>
Java version: <10>

Unfortunately, I'm having a hard time understanding you.
After I run the above code, I am supposed to do the three steps you mention in "Expected Behavior," correct? However, since you put that under the "Expected Behavior" section, what actually occurs when I do that?

Please can you tell me what you did not understand?
Maybe my English is bad
But if you do the three steps you'll notice creating a blank space above the text(in Top) instead of going down the text to the bottom
This is written in the title

Are you wrapping your area inside a VirtualizedScrollPane?
On Sat, May 12, 2018, 8:57 AM Saif Al Mutory<EMAIL_ADDRESS>wrote:

Please can you tell me what you did not understand?
Maybe my English is bad
But if you do the three steps you'll notice creating a blank space above
the text(in Top) instead of going down the text to the bottom
This is written in the title
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/FXMisc/RichTextFX/issues/748#issuecomment-388564529,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIBfbZkWryNVrOFdoxFJXJJkA7ku3pI9ks5txwZagaJpZM4T8bCF
.

No, this can not be in my project

Please can you tell me what you did not understand?

Given this code below:
public class Bug extends Application {

 public void start(Stage primaryStage) {
        var area= new InlineCssTextArea();
        area.setPrefSize(400,600);
        var pane= new AnchorPane(area);
        var scene= new Scene(pane);
        for(var i=0;i<25;i++){
            area.appendText("\n");
            area.appendText(String.valueOf(i));
        }
        primaryStage.setScene(scene);
        primaryStage.show();

        // User interaction
 }

}

which produces an area like the following:
|--- Area Top
|
|0
|1
|2
|...
|24
{

(empty space)

}
|--- Area Bottom

I understand that at the comment // user interaction, I am supposed to do three things:

Move the caret behind the number 0 (where ^ represents the caret):

|--- Area Top
|
|^0
|1
|2
|...
|24
{

(empty space)

}
|--- Area Bottom

Press enter repeatedly until the last line reaches the bottom of the viewport

|--- Area Top
|
|
|
|
|
|^0
|1
|2
|...
|24
|--- Area Bottom

[My paraphrase of what you said:] If you continue to press enter, you will notice the text does not continue to descend. Also, if you select the text from 0 to above, you will notice that there is a large blank space due to pressing enter

Correct. This is entirely what I expect it to do. So, what is it actually supposed to do?
It sounds like you want the viewport to "freeze." In other words, something like this...
|--- Area Top
|
|
|
|
|
|^0
|1
|2
|...
|24
|--- Area Bottom

... will change to the following after pressing enter once:
|--- Area Top
|
|
|
|
|
|^0
|1
|2
|...
|23
|--- Area Bottom
|24 // not rendered

Yes, that's exactly what I'm trying to say
is this normal?

See the showParagraph prefixed methods, which you'll need to call to insure the viewport does not change (e.g. get the last visible paragraph index, insert the newline, call showParagrahAsLast (something like that) using the argument lastParagraphIndex - 1).
You might also want to override the default behavior with your own so that the enter does not trigger a requestFollowCaret() call.


Question About Usage

Hello,
Let me apologize in advance for dumb question.
I am trying to figure out a cross-platform way to store and access structs via memory mapped files.
I guess the question is how do I perform operations with mio on types wider than byte or char?
Thanks in Advance
struct Tick
{
   double Price;
  int Volume;
};

   const auto path = "ticks.bin";

      std::error_code error;

      mio::mmap_sink rw_mmap = mio::make_mmap_sink(path, 0, mio::map_entire_file, error);

      for(Tick *t = rw_mmap->begin(); t != rw_mmap->end(); ++t)
      {
          t->Price = 5; //
      }

I would need this too.
Any idea how to easily implement this on top of 'mio' for this int-double struct?

What I have currently:
struct indval {
  int i;
  double x;
};

std::error_code error;
mio::mmap_source ro_mmap;
ro_mmap.map(path, error);
const indval * data = reinterpret_cast<const indval*>(ro_mmap.data());
cout << data->i << " // " << data->x << std::endl;

@privefl what you're doing is bound to break because of padding and alignment. you can use Boost.serialization or, if you prefer something smaller, cereal

I'm doing exactly what @privefl suggested and it works. When the original file is created sizeof(indval) bytes is written to disk. This will include any padding bytes added by the compiler. It's just a binary blob of bytes. As long as you use the same padding the bytes on disk and in memory are the same. This highly non portable of course

I've finally used two doubles, for safety.


cudaCheckError() failed : invalid device function

hi， ‘make install’ is succeed，but running ‘make test’ occurs some errors.
`cd test-files && python test.py
--- Initial checks for forward ---

Checking 1D CPU ...
PASSED
Checking 1D GPU ...
cudaCheckError() failed : invalid device function
Segmentation fault (core dumped)
Makefile:9: recipe for target 'test' failed
make: *** [test] Error 139
`

This seems like a CUDA or hardware related issue. Can you post some info about:
A. Your system (i.e. GPU model)
B. How you installed:

CUDA and cuDNN
PyTorch

Best,
Alex

This seems like a CUDA or hardware related issue. Can you post some info about:
A. Your system (i.e. GPU model)
B. How you installed:

CUDA and cuDNN
PyTorch

Best,
Alex

This seems like a CUDA or hardware related issue. Can you post some info about:
A. Your system (i.e. GPU model)
B. How you installed:

CUDA and cuDNN
PyTorch

Best,
Alex

I found the same error here.
My environment info is:
GPU: 2080 Ti
CUDA: 10.0.130
cuDNN: 7.6.0
PyTorch: 1.6.0
Thank you.

This seems like a CUDA or hardware related issue. Can you post some info about:
A. Your system (i.e. GPU model)
B. How you installed:

CUDA and cuDNN
PyTorch

Best,
Alex

I found the same error here.
My environment info is:
GPU: 2080 Ti
CUDA: 10.0.130
cuDNN: 7.6.0
PyTorch: 1.6.0
Thank you.

Hi @rumsyx,
This sounds like an NVCC/CUDA runtime version mismatch for your system. Check #62 issue in PyTorch and ensure that your NVCC and CUDA runtime versions are correct.
Best,
Alex

Hi @rumsyx,
This sounds like an NVCC/CUDA runtime version mismatch for your system. Check #62 issue in PyTorch and ensure that your NVCC and CUDA runtime versions are correct.
Best,
Alex

may by your install more CUDA version.
so
make clean
CUDA_HOME=/mnt/lustre/share/cuda-10.2 make install

may by your install more CUDA version.
so
make clean
CUDA_HOME=/mnt/lustre/share/cuda-10.2 make install

make clean
CUDA_HOME=/usr/local/cuda-10.2 make install
then can make test

make clean
CUDA_HOME=/usr/local/cuda-10.2 make install
then can make test

Closing due to inactivity. Feel free to open a new issue for future problems with the installation process.

Closing due to inactivity. Feel free to open a new issue for future problems with the installation process.


Add filtering to graphql

Close: #130, Close: #131

Codecov Report
Base: 50.73% // Head: 40.48% // Decreases project coverage by -10.24% :warning:

Coverage data is based on head (de3a21f) compared to base (62f141f).
Patch coverage: 79.59% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #134       +/-   ##
===========================================
- Coverage   50.73%   40.48%   -10.25%
===========================================
  Files          10        9        -1
  Lines        1163      862      -301
===========================================
- Hits          590      349      -241
+ Misses        573      513       -60

Impacted Files
Coverage Δ

src/ingestion.rs
18.58% <75.75%> (+18.58%)
:arrow_up:

src/graphql.rs
80.80% <80.95%> (+20.02%)
:arrow_up:

src/graphql/log.rs
86.66% <100.00%> (-11.50%)
:arrow_down:

src/graphql/network.rs
87.40% <100.00%> (-5.23%)
:arrow_down:

tests/common.rs

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

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


KAFKA-5690: Add support to list ACLs for a given principal (KIP-357)

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@lindong28 @junrao  This is minor PR for KIP-357: Add support to list ACLs per principal
Appreciate your votes and review for this KIP/PR.

Merged to trunk.

It seems that the vote for the KIP has not passed. I will revert this commit..

@lindong28 Thanks for the review.  vote has passed now.

Thanks for the update @omkreddy. Merged to trunk.


Software Update 2<IP_ADDRESS>_GA

Why

Update to latest miner, config and diag
How

Bump miner, diag and config containers to latest versions.
References

https://engineering.helium.com/2021/09/14/major-blockchain-release-pocv11-support-snapshot-updates-performance-improvements.html

Need to test on testnet before rolling out


Checks that document.doctype is an HTML doc before injecting

This fixes #356
The document.doctype should always be defined for HTML documents.  See https://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-B63ED1A31
Guarding against this should protect from injecting the content scripts into non-HTML pages.
Tested in Firefox and Chrome.

This isn't ready for merge, I don't really like the solution. Let me look into the Firefox issue more before falling back on this.

ok, thanks a lot for taking a look!

#385 addresses the same issue and instanceof seems to be a stricter check - does that look like a somewhat ok solution?

ping @clarkbw

Yes, that looks like a much cleaner solution!  💯


Overlay quicklooks on feature geometry

In plot_coverage(), add an optional quicklooks=True Argument that enables overlaying the quicklooks on the feature geometries (georeferenced using matplotlib transformations)

Closing, tracked in Jira.


suggest to add a new type: element

There are many scenario that use custom components as a list.
In that scenario, we may indicate a custom class name that represent a components.
the config may looks like:
document.addEventListener('DOMContentLoaded', function () {
  new ShowMore('.element', {
    config: {
      type: "element",
      childClassName: "ele-node",
      limit: 3,
      more: "→ read more",
      less: "← read less"
    }
  });
});

And the HTML may looks like:

According to the config, the child node of .element class node may hide the last direct child node.
Would this possible to be implemented ?

Thanks for comment.
But I'm not really going to expand the library like that. I try to make it as simple and easy to use as possible.
The html you showed can be converted to ul + li and it will have the same effect :)

a

b

c

d

e

f

g

h

i

j

k

l

I will not add this possibility for one more reason.
In such a div element, you can actually add another element, in which case it would be difficult to control the content.

and the ul + li element has only one construction possibility, otherwise it would be inconsistent with the html semantics.
Thanks again for the idea but I will not use it.
Maybe you can find a library that can handle this problem.
Good luck


calico-apiserver pod won't start Error: unknown shorthand flag: 'v' in -v=5

Following https://projectcalico.docs.tigera.io/maintenance/install-apiserver won't work.
The pod will never start. Crash loop back
The log shows:
Version:      v3.23.2
Build date:   2022-06-24T17:06:31+0000
Git tag ref:  v3.23.2
Git commit:   a52cb86db
Error: unknown shorthand flag: 'v' in -v=5
Usage:
   [flags]

Flags:

...

E0705 13:11:46.003843       1 apiserver.go:53] server exited unexpectedly (unknown shorthand flag: 'v' in -v=5)

Manifest

For now, you can simply remove the line with         - -v=5.
Looks like we'll need to fix that manifest, and perhaps investigate why the verbosity option was removed.

I'd take this one, Can I have this?


lean_packages/manifest.json → lake-manifest.json

Dependency version pinning usually happens at the root project directory for many languages.
It also clears the .gitignore and repo structure because there wouldn't be the need to keep a directory with just a json file.

@gebner, @Kha what do you think?

It was my very first thought when I saw the current file path to be honest, but I didn't want to start a discussion if it's just me (and also I'm not exactly a regular Lake user). But if we're renaming anyway, I really think we should just name it lakefile.lock like the cool kids, which looks quite nice in directory listings. Somehow my first thought when hearing "manifest" is "Java".

I'd also prefer lakefile.lock.  But please let's not make this configurable. I'm willing to put up with any convention as long as it is consistent.

But please let's not make this configurable. I'm willing to put up with any convention as long as it is consistent.

I should note that literally everything else about the package layout is configurable, so having this be the one thing that wasn't was honestly more inconsistent. I doubt it being configurable matters. I imagine virtually everyone will stick with the defaults unless there is some real issue preventing them from doing so.

I really think we should just name it lakefile.lock like the cool kids, which looks quite nice in directory listings.

Here is my two cents on this: I absolutely hate this naming convention.
For one, it is not a real lock file. Before this become a common convention for package managers, a .lock file was a mutex (i.e., an actual lock) to prevent simultaneous edits by a program to a directory (e.g., Git's .git/index.lock).  Instead, the file is really a manifest. I am especially disappointed that Cargo of all things did not use this term, since one definition of a manifest is a "certified list of a ship's cargo", fitting perfectly with the theme.
Second, it does not have the proper file extension (e.g., json) indicating its data format, which is very bad (e.g., for opening the file with a proper editor, for open file dialogs for things that care about file types,, and for syntax highlighting), Furthermore, different package managers use different data formats (e.g., TOML for Rust, JSON for NPM/Yarn), so there isn't even a standard data format of a .lock file to associate the extension with.

I, on the other hand, don't care much about the name, really. But I do believe that placing a file in a folder that will hold a single file on every git repository is not the best default option

@arthurpaulino Yeah, I think your suggested change is reasonable. I am otherwise occupied for the next 2 weeks, but afterwards I plan to do a v4 maintenance release of Lake that should include this change.

I am especially disappointed that Cargo of all things did not use this term

Ah, but it does - Cargo.toml is described as the manifest file in the documentation. So while manifest seems to be a pretty muddled term, I really can't think of a clearer term than lockfile in the context of a package manager. As you said, it's become a common convention.

Second, it does not have the proper file extension (e.g., json) indicating its data format

I'm pretty sure that's exactly as intended to signify that the file is generated and not meant for human consumption.

Regarding the file name, here's an alternative idea: use YAML and call it lake_dependencies.yml. And then have a comment at the very top saying

This file is automatically generated and managed by Lake

Please don't use YAML for generated data. Actually any kind of data, but I can accept other opinions there.

A bit off-topic, but I think YAML is even worse for user-provided data than for generated data.  At least the generator won't fall into the true/YES/yeah trap.  (For the uninitiated, all three are valid YAML syntax.  But the first two parse to the same boolean value, while the third is of course a string.)

If I can also add my 2 cents (and a "feature request"), it would be great if the chosen target file can be easily readable by Nix, e.g. commonly used file formats and enough data to download everything (hashes, etc.) without external assistance.

@RaitoBezarius The current manifest format should already fit this (it uses JSON and has hashes etc.)

Ah, but it does - Cargo.toml(!) is described as the manifest file in the documentation. So while manifest seems to be a pretty muddled term,

But its not a manifest file? It is order about what packages to download, not a "certified list"  of which ones were downloaded. Thus,, I do not feel we should adopt their misuse of the English language.

As you said, it's become a common convention.

In my view, bad conventions should be broken. Especially if the convention is jargon and not helpful to new user's understanding.

I'm pretty sure that's exactly as intended to signify that the file is generated and not meant for human consumption.

But Lake's manifest is. As mentioned in #70 manually altering the manifest may be necessary to fix conflicts.


Display progress of Quick Upload

There should be some form of visual feedback when user is uploading a big file.
Adding a progress indicator should be possible when changes listed in https://github.com/ipfs/js-ipfs-api/issues/608 are released 🤔

What ought to be the file-size recommendations/limits for file uploads?

This remains an open question.
I suspect there will be different choke points depending on what IPFS node type is used:

If extension is set up to use external IPFS node, then we have potential transfer speed limits introduced by js-ipfs-api (HTTP API Client library) and then storage characteristics of go-ipfs come to play.
If embedded js-ipfs is used, then we have limits imposed by browser vendor on memory use and max local storage size per extension.

In addition to the above, if upload is performed via window.ipfs object, then there may be a small speed overhead introduced by ipfs-postmsg-proxy.
Expect these to be benchmarked at some point, but looking at https://benchmark-js.ipfs.io I am rather optimistic about every day use.

Progress indicator shipped with v2.3.0.  Works best with embedded node.
There are remaining issues such as long buffering when external node is used, but these things will be addressed in upstream libraries.


Implement non-intrusive SafeBrowsing

We want to have SafeBrowsing as an option where the user can download a database every 30 minutes without having to send site information to Google or any other threat intelligence provider.

Suggest looking at https://github.com/chromium/chromium/blob/master/chrome/browser/safe_browsing/incident_reporting/incident_report_uploader_impl.cc

It would be nice to explore if having multiple or the ability to choose threat intelligence providers is feasible.

The Yandex Safe Browsing API looks to be a drop in replacement but I've never played with it.

SafeBrowsing Standard is what we want but we need to ensure that the /fullHashes API is not used which can expose what sites you visit. /threatListUpdates is all we want.


Feature Request: Day of the Week and seconds

I absolutely love this watch face but am missing that my previous one gave me the day of the week and seconds. You can probably fit seconds into the time box and maybe the day of the week in 3-4 characters to the left or right of the month and day (maybe as a "Status condition"?).
If others don't like it, maybe add the ability to toggle it using the watch face settings?

Thank you for the feedback. I added your feature requests to my list.
Here is, what I think so far:

Probably the day of the week will be shown above the health bar. Let's see if I'm able to apply an easy "status condition" style. If not, it will look like the level but be aligned to the right.
The display of seconds needs to be configurable as I prefer to turn it off to save battery.
If I get the configuration done, I may also add date format and display of week numbers.

If you are able to do the "status condition" idea, you could base each day off of a status condition so one can determine the day by how it looks, but that is probably overkill. There are 5 non-volatile status conditions as far as I can tell. Burn, Freeze, Paralysis, Poisoned/Badly Poisoned, and sleep. Don't know what you may use for the others if any.

Maybe possibly add an indicator for if the watch is in silent mode? Sorry, I just start creating a list of stuff...

after the page refreshes and I see your reply Oh. That works just fine! I love it and I understand not making it more complicated! Thank-you! Also, the smaller number for seconds is mostly for readability.
The silence thing is still an option if you want to though. You don't have to. I just find myself sometimes opening the main menu just to check if the watch is in silent mode.

I just the released the new features. Let's see if it works well and if you like my idea for displaying an active quiet time.

The quiet time looks nice! I was going to see if I could implement better painting for the seconds to extend battery life, but I am not sure how to install the SDK and set up the dev environment and such.
Some things I have found while looking at the documentation is there is a method to paint onto a portion of a bitmap. https://developer.rebble.io/developer.pebble.com/docs/c/Graphics/Drawing_Text/index.html graphics_dra_text looks to be of interest? I don't know if you can paint straight to the screen or not. There is also graphics_draw_bitmap_in_rect, where you could possibly render to a small bitmap and then to the screen?

Yes, getting the SDK ready got complicated as the official documentation no longer works. I updated the projects README with some alternatives. You can go with Docker as I do, if you are on Linux. On Windows I would recommend VirtualBox and the prebuilt disk.
How bad is the battery impact when seconds are activated? My mobile runs on Sailfish and the settings page for the watchface does not work there - so I'm not able to activate seconds rendering for daily use.

I am not sure for sure. I haven't been keeping good tabs on how long my watch battery lasts I will recharge tonight and see how long it lasts without and then with the seconds.

So, without seconds, I got 2 days and 20 hours. With seconds I got < 50 hours. Maybe around 45? So doing some optimization might be a good idea.

Thanks for the test. I agree with your opinion on doing some optimization. Let's see what can be done. But it may take a while.

OK, I did a quick test on my first guess:
The pebble needs to redraw the whole screen with each update, even if nothing changed but the current second.
In the release 2.1 I now added a cache for the "battlefield". This allows the watchface to restore everything unrelated to date and time in one (hopefully performant) step. Let's see if it helps - but this is probably the only thing I can do...

Ok. I will test that.

I got a out 47 hours that time? And I actually caught it less than 30 minutes after it died, so this one is probably more accurate... I am doing a test run with the old/other watch face to see how it compares. The Battery+ app seems to be giving a pessimistic view with that. It may be the same. I will let you know when that one is finished.

So... The "control" actually did worse that yours XD. It only got about 35 hours... That being said, there may be a way to save battery and show seconds, though I have no right to request it since I have asked for so much already...
I don't need to see the seconds display all of the time. If I could just toggle it on and off from the watch when I need it, that would save draws. We can't use long presses on any buttons since they are taken by shortcuts. Single presses of the right buttons are reserved. Pressing the back button lights up the watch. Mabye pressing the back button twice to toggle the seconds if the seconds option is not enabled?
As I said, you don't have to. I greatly appreciate that you have done so far.

I also did some measurements and checked the time needed to render the window (code, not hardware). I only checked with the emulator and with limited precision. Let's call the minimal precision a tick. The original version took 3 to 4 ticks and the cached version needs 2 ticks. By also caching the date and day of week it gets down to 1 tick. This will come with the next version and seems to be the absolute minimum.
So the remaining battery seems to be drawn by the secondly wake-ups and the hardware to draw the rendered window.
Now for your idea:
Actually a watchface is not allowed to detect button "clicks". So the only input type is a accelerometer tap event. I may add an option to only update seconds for a minute or so after a tap event is detected. If used together with "render seconds" the seconds will just not update until the next event. If used without, the time will be replaced by seconds for that time.

Excellent 👍 thanks!


Add achievements to walkthrough

As per the title; the walkthrough doesn't show how to get all the achievements (and I'm already out of ideas).

Acknowledged! I found it hard to balance giving people hints about what to do with not spoiling too much at once.
I think I have some good ideas for a "see it all" walkthrough that can only spoil one achievement at a time. While it may take more than a day, it's a good goal, and it's one I wish I'd started on before the comp release.
Thanks again for reporting these bugs. They're a big help.

I added the walkthroughs to source control. They should be on itch.io next time I compile the binaries, etc.


[BUG] UnsupportedOperationException: Path not associated with default file system.

Error on my nested jar

Will the https://github.com/Sinytra/Connector/blob/1.20.1/src/main/java/org/sinytra/connector/loader/ConnectorEarlyLoader.java#L35-L37 work?

it does, just forgot to backport.


Improve error handling for 'package-registry login' command

Motivation:
When running login with --netrc and --netrc-file options and the custom netrc file doesn't exist, the command fails immediately with file not found error:
swift-package-registry --netrc --netrc-file ./netrc-test login
Error: Did not find netrc file at /Users/appleseed/netrc-test.

Which can be confusing.
Modifications:
Rearrange logic so that we initialize AuthorizationProvider first thing and display better error messages to user.
Error: credential store is invalid: did not find netrc file at /Users/appleseed/netrc-test

@swift-ci please smoke test

cc @Palleas

@swift-ci please smoke test

@swift-ci please test Windows platform

@swift-ci pleases test Windows platform

@swift-ci pleases test Windows platform

@swift-ci pleases smoke test

@swift-ci pleases smoke test

@swift-ci please smoke test

@swift-ci pleases test Windows platform

@swift-ci please smoke test

@swift-ci please test Windows platform


The requested URL returned error: 404

Installing docker-in-docker fails to curl, not sure what url. How can I fix this?

[dev_containers_target_stage 6/6] RUN --mount=type=bind,from=dev_containers_feature_content_source,source=docker-in-docker_1,target=/tmp/build-features-src/docker-in-docker_1     cp -ar /tmp/build-features-src/docker-in-docker_1 /tmp/dev-container-features  && chmod -R 0755 /tmp/dev-container-features/docker-in-docker_1  && cd /tmp/dev-container-features/docker-in-docker_1  && chmod +x ./devcontainer-features-install.sh  && ./devcontainer-features-install.sh  && rm -rf /tmp/dev-container-features/docker-in-docker_1:
0.474 ===========================================================================
0.474 Feature       : Docker (Docker-in-Docker)
0.474 Description   : Create child containers inside a container, independent from the host's docker instance. Installs Docker extension in the container along with needed CLIs.
[2024-08-14T14:52:48.241Z] 0.474 Id            : ghcr.io/devcontainers/features/docker-in-docker
0.474 Version       : 2.11.0
0.474 Documentation : https://github.com/devcontainers/features/tree/main/src/docker-in-docker
0.474 Options       :
0.474     VERSION="latest"
[2024-08-14T14:52:48.241Z] 0.474     MOBY="true"
0.474     MOBYBUILDXVERSION="latest"
0.474     DOCKERDASHCOMPOSEVERSION="v2"
0.474     AZUREDNSAUTODETECTION="true"
0.474     DOCKERDEFAULTADDRESSPOOL=""
0.474     INSTALLDOCKERBUILDX="true"
0.474     INSTALLDOCKERCOMPOSESWITCH="false"
0.474 ===========================================================================
0.500 Distro codename  'focal'  matched filter  'bookworm buster bullseye bionic focal jammy noble'
1.005 Get:1 https://packages.microsoft.com/repos/azure-cli focal InRelease [3596 B]
[2024-08-14T14:52:48.241Z] 1.032 Get:2 https://packages.microsoft.com/repos/microsoft-ubuntu-focal-prod focal InRelease [3632 B]
1.058 Get:3 https://download.docker.com/linux/ubuntu focal InRelease [57.7 kB]
1.163 Get:4 http://security.ubuntu.com/ubuntu focal-security InRelease [128 kB]
1.171 Get:5 http://archive.ubuntu.com/ubuntu focal InRelease [265 kB]
1.192 Get:6 https://packages.microsoft.com/repos/azure-cli focal/main amd64 Packages [1713 B]
1.230 Get:7 https://packages.microsoft.com/repos/azure-cli focal/main all Packages [4113 B]
1.328 Get:8 https://packages.microsoft.com/repos/microsoft-ubuntu-focal-prod focal/main all Packages [2714 B]
1.358 Get:9 https://packages.microsoft.com/repos/microsoft-ubuntu-focal-prod focal/main amd64 Packages [308 kB]
1.460 Get:10 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages [58.5 kB]
1.682 Get:11 http://archive.ubuntu.com/ubuntu focal-updates InRelease [128 kB]
1.723 Get:12 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 Packages [30.9 kB]
1.806 Get:13 http://archive.ubuntu.com/ubuntu focal-backports InRelease [128 kB]
1.842 Get:14 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages [3867 kB]
1.946 Get:15 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages [11.3 MB]
2.758 Get:16 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [3885 kB]
3.431 Get:17 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages [1256 kB]
3.853 Get:18 http://archive.ubuntu.com/ubuntu focal/restricted amd64 Packages [33.4 kB]
3.853 Get:19 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages [177 kB]
3.874 Get:20 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [1275 kB]
3.999 Get:21 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages [33.5 kB]
4.012 Get:22 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [1543 kB]
[2024-08-14T14:52:48.241Z] 4.175 Get:23 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [4351 kB]
4.488 Get:24 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages [4018 kB]
[2024-08-14T14:52:48.241Z] 4.805 Get:25 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 Packages [28.6 kB]
4.812 Get:26 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 Packages [55.2 kB]
6.670 Fetched 33.0 MB in 6s (5650 kB/s)
6.670 Reading package lists...
8.464 Docker / Moby CLI and Engine already installed.
8.464 Finished installing docker / moby!
8.717 compose_version=2.29.2
8.717 (*) Installing docker-compose 2.29.2...
8.859 curl: (22) The requested URL returned error: 404
8.863 Error: Failed to install docker-compose v2.29.2
8.864 chmod: cannot access '/usr/local/bin/docker-compose': No such file or directory
8.865 ERROR: Feature "Docker (Docker-in-Docker)" (ghcr.io/devcontainers/features/docker-in-docker) failed to install! Look at the documentation at https://github.com/devcontainers/features/tree/main/src/docker-in-docker for help troubleshooting this error.

I think I see the issue. It is trying to curl https://github.com/docker/compose/releases/download/v2.29.2/docker-compose-Linux-x86_64 acording to the releases, that version does not exist, latest is 2.29.1 https://github.com/docker/compose/releases/
https://github.com/devcontainers/features/blob/b2c7d17f0a8320895c3b52df8485c645398854e1/src/docker-outside-of-docker/install.sh#L332

https://github.com/docker/compose/releases/download/v2.29.2/docker-compose-Linux-x86_64 is now available. I guess its publishing was delayed and the script picked up the version from the repository's tags. Maybe the script could fall back to the previous tag when the current doesn't have a download yet.

This happened again for v2.30.0, but worked again within 10 minutes.

This disrupted me briefly this morning but fixed itself quickly.

https://github.com/docker/compose/releases/download/v2.29.2/docker-compose-Linux-x86_64 is now available. I guess its publishing was delayed and the script picked up the version from the repository's tags. Maybe the script could fall back to the previous tag when the current doesn't have a download yet.

The fallback method has been implemented in other features as well including this one, but it's been implemented in all of these in a manner that only when the desired version is configured to be the latest it comes in play, so if major version is only given instead of latest as given here, these will start failing again and thus whenever there's a gap between updating of tags by the repo maintainers and availability of source binary for it due to deployment happening there will be such issues


Build.md

I've mainly fixed the issues in the POM under waltz-data. I also added a sql server command for creating the waltz db.

Thank you for your contribution and Welcome to our Open Source Community!
To make sure your pull request is accepted successfully, we ask all our open source contributors to sign a Contributor License Agreement.
Having reviewed our contributor list, we require a CLA for the following people : (@strangetobefree).
If you need help obtaining a CLA, please read the Requirements for Contributions section of our CLA wiki or email<EMAIL_ADDRESS>with your questions.
Thanks once again for your contribution. Let us work with you to make the CLA process quick, easy and efficient so we can move forward with reviewing and accepting your pull request.
cc @finos-admin

Hi Steve, I don't think the waltz-data\pom.xml changes are actually needed. We usually only make these changes to force the IDEs (IntelliJ) to recognise dependencies correctly (it gets confused due to conditional selection of DB dependencies).
But for building Waltz, these are not needed. I was able to build for MSSQL without this change in the waltz-docker project:
https://github.com/rovats/waltz-docker
The issue you faced must have been because of another reason.
Also, because Waltz supports multiple DBs, we won't be able to merge this MSSQL specific change to waltz-data\pom.xml in the main codebase, as these DB dependencies are selected conditionally based on which maven profile the code is being built with.
PS: Waltz now provides a waltz-mssql-alt profile which uses newer MSSQL JDBC drivers (I remember you mentioned you weren't able to find the older drivers used by waltz-mssql profile).

Closing as we can't make the database a fixed option (Rohit explained it well).   I've updated the build.md file with the improved documentation.  Thanks!


Pass -l:libfoo.a to linker directly.

Fix #148 .

Something need to be changed

Something need to be changed

Done.

Thanks！


Support for uint256/int256

Is your feature request related to a problem?
Description
The most commonly used data types for smart contracts and token math on the blockchain are uint256 and int256. Currently, people in the crypto community are resorting to inefficient methods like converting to float or string because there is no native support for these data types. For example, paradigmxyz/cryo exports duplicate data columns in various formats (float, binary, string) due to the absence of native support in polars
Describe the solution you'd like
Native first class support for int256
Describe alternatives you've considered
convert to float64
Additional Context
Polars issue:
https://github.com/pola-rs/polars/issues/15443
https://github.com/recmo/uint
Would you like to implement a fix?
No

Seems similar to #2889, wonder if we could knock out two birds with one stone... @colin-ho

Similar, probably not in one stone though. We would need to implement all the casting / ffi / kernels, which is a lot of work.
This is not a priority for us at the moment, assigning this as backlog. Open to PR contributions though.


mc.get_coords() returns None

Describe the bug
Following the myCobot 280 M5 demo code, got error.
To Reproduce
Steps to reproduce the behavior:

pip install pymycobot --upgrade
copy paste demo/myCobot_280_demo/280_draw_gcode.py and modify the usb port for linux use
run demo script

Expected behavior
demo code should work but mc.get_coords() returns None.
Env (please complete the following information):
ubuntu, python3.11 venv

Did you select Transponder > USB UART > OK before running the demo script?
The robot needs to establish a connection before it can be programmed

Select menu:
miniRoboFlow v2.30 -> Transponder -> USB UART
Showing:
Connect test
Atom: OK

You can write a simple test script like this to see if there is any output。
from pymycobot import MyCobot
import time
m = MyCobot("com5")

for _ in range(10):
    print(m.get_angles())
    time.sleep(0.1)
    print(m.get_coords())
    time.sleep(0.1)


Theodore/proofnarrowing

Add proof narrowing capabilities to the tree: given a range proof, supply two sets of leafs (contiguous with the edges of the original range), to generate a proof for the remaining sub-range.
This feature is useful for generating proofs of individual blobs in a Celestia namespace using the full-namespace proof returned by the GetSharesByNamespace RPC call.

Actually your comment about the ranges is spot-on - the current test was missing a whole bunch of edge cases due to being non-inclusive. Whoops!
I'm fixing that now, and then it will probably be fine to assert that "it seems to work".
Happy to add some more comments and explanations, especially now that I've slept on it and can look at it from a slight distance!

By the way, the codecov.io token seems dead, so the badge in the README isn't updating anymore


fix(rxjs): export ConnectableObservable

Coverage increased (+0.0004%) to 97.524% when pulling f61b7f3de131ef3a48069fb3271bdb4ac6528e40 on jasonaden:add_connectable_observable into 4465a9f980213ca0a6149427c0f5569f4adeaafa on ReactiveX:master.


Optimize S2 data loading by computing and applying (conservative) cloud mask

We would like to exclude entire observations depending on the amount of pixels marked as HIGH_PROBA_CLOUDS in the SCL layer. So far we implemented an UDF that directly generates a mask either covering the entire observation, or being totally empty (only 0s). We managed to run the UDF locally but running on open-eo poses a problem:

Running using apply_neighborhood requires specifying an area, and padded zones of the array can cause problems on the computation of the occurrence of HIGH_PROBA_PIXELS. Does OpenEO has a standard value for padded pixels? This way we can try to ignore those values. Also the output mask needs to be matching the input size.
Running using apply does it pixel-wise, so running the UDF like so is not possible.
Additionally, how can we make this work when it comes with the extraction of samples? Here especially, we are running extractions on 64x64 pixel tiles.

Minimal example is:
import openeo
from tempfile import NamedTemporaryFile
from shapely import box
from shapely.geometry import mapping

from openeo.udf import execute_local_udf, XarrayDataCube
from openeo import UDF

connection = openeo.connect('https://openeo.dataspace.copernicus.eu').authenticate_oidc()

spatial_extent = mapping(
    box(4.591687083409023, 51.11455367032077, 4.607750156043775, 51.129320859000856)
)

cube = connection.load_collection(
    "SENTINEL2_L2A",
    spatial_extent=spatial_extent,
    temporal_extent=["2022-01-01", "2022-03-01"],
    bands=["B04", "B03", "B02", "SCL"]
)

mask = cube.filter_bands(["SCL"]).apply_neighborhood(
    process=UDF.from_file("../src/openeo_gfmap/preprocessing/udf_cldmask.py", context={}),
    size=[
        {"dimension": "x", "unit": "px", "value": 1024},
        {"dimension": "y", "unit": "px", "value": 1024},
    ],
    overlap=[],
).rename_labels("bands", ["MASK"])

cube = cube.merge_cubes(mask)

job = cube.create_job(
    title="Full cldmask test",
    out_format="netcdf",
)

job.start_and_wait()

With udf_cldmask.py being:
import numpy as np
import xarray as xr
from openeo.udf import XarrayDataCube

def apply_datacube(cube: XarrayDataCube, context: dict) -> XarrayDataCube:
    """
    Computes a cloud mask covering a full observation or nothing depending on the percentage of
    high probability cloud pixels. If the amount of before mentioned pixels is higher than 95%,
    then returns a mask covering the whole observation, otherwise returns an empty mask.
    """
    array = cube.get_array().transpose("t", "bands", "y", "x")

    output_array = np.zeros(
        shape=(array.shape[0], 1, array.shape[2], array.shape[3]),
        dtype=np.uint8
    )

    for i in range(array.shape[0]):
        high_proba_count = (
            (array[i] == 9) * 1
        ).sum()
        high_proba_percentage = high_proba_count / (array.shape[2] * array.shape[3])

        if high_proba_percentage > 0.95:
            output_array[i] = 1

    output_array = xr.DataArray(
        output_array,
        dims=["t", "bands", "y", "x"],
        coords={
            "t": array.t,
            "bands": ["mask"],
            "y": array.y,
            "x": array.x,
        },
    )

    return XarrayDataCube(output_array)

I see two options in general:

using apply_polygon + the UDF
using aggregate_spatial on the scl mask to count number of clouded pixels, then convert this count back into a raster using vector_to_raster, and then applying a threshold to turn count into binary mask again

We would need to check performance of both options. Aggregate_spatial has the advantage that it does not require tiles to be grouped by polygon, and also not requiring UDF.
@JeroenVerstraelen  Do you think the aggregate_spatial approach would already work, based on latest improvements?

By default it will be NaN, but the process has a 'mask_value' parameter for user-defined padding:
https://processes.openeo.org/#apply_polygon

The option with apply_polygon would process full timeseries per polygon, which is a bit heavy.
Hence we're looking at option 2. I already have basic code, but we're finishing up a backend feature to make it work. (It was already in progress for another usecase.)
I think the code for that option would look like this:
    cube = connection.load_collection("SENTINEL2_L2A", temporal_extent=("2022-03-01", "2022-09-20"),
                                      spatial_extent=extent, bands=["SCL"], max_cloud_cover=85)
    cube = (cube ==9) | (cube ==8)
    mask = cube.polygonal_mean_timeseries(poly).vector_to_raster(cube).apply(lambda x:x>0.5)

    bands = connection.load_collection("SENTINEL2_L2A", temporal_extent=("2022-03-01", "2022-09-20"),
        spatial_extent = extent, bands = ["B02"],max_cloud_cover=85).mask(mask)

@jdries any update on this one?

@JeroenVerstraelen or @VincentVerelst  can you post here when the vector_to_raster from aggregate_spatial works?

As I tried to explain in the  meeting today, there might be an approximating alternative too, that does not depend on experimental features like vector_to_raster, but just apply_kernel.
In (pseudo)code:
scl_band = connection.load_collection("SENTINEL2_L2A", bands=["SCL"], ...).band("SCL")
clouds = (scl_band ==9) | (scl_band ==8)
cloud_mask = clouds.apply_kernel(kernel) > threshold

cube = connection.load_collection("SENTINEL2_L2A", bands=["B02"], ....).mask(cloud_mask)

The trick here is to approximate aggregate_spatial(polygons).vector_to_raster()  with apply_kernel(kernel).
For example if the kernel is a normalized disk/rectangle with large enough support (e.g. order of patch size I think), all pixels in the blurred output will be close to the fraction of cloud pixels in that area. If you apply a thresholding, the result should be pretty close to the exact result of aggregate_spatial(polygons).vector_to_raster().
I hope this explanation makes some sense

I will close this issue for the moment, as this issue is taking us too much time and it is still uncertain how much optimization it will bring


[fog][DEPRECATION] Unable to load Fog::Rackspace::CDN

I just did a bundle update in updating rails and I'm getting this error when running my tests:
[fog][DEPRECATION] Unable to load Fog::Rackspace::CDN
[fog][DEPRECATION] The format Fog::CDN::Rackspace is deprecated
The trouble is twofold:

I don't actually use the code Fog::Rackspace::CDN in my app
it doesn't tell me where it is failing, so I am not even sure where to look among my gems.

Any ideas on how to go about fixing this?

I am getting the same thing. Looks like it works, but the message is annoying, and at some point I'm assuming it will stop working.

Actually seems like its similar to #29

I'll close in favor of that one then.


Select statement: false positive

The following statement will produce an error of "Binary operator 'select' arguments must be [(Array,Number),(Array,Boolean),(String,Array),(Array,Code),(Config,Number),(Array,Array)] (lhs is String, rhs is Boolean)":
animationState player select [9, 3] in ["eva", "spr"]

Removing the 'in' check from the statement will no longer produce the error however:
animationState player select [9, 3]

Both statements work without error in-game.

Are you sure this hasn't been fixed with commit 0b952c1b08514ed3ca5086e0c2aa9dc78a44ba08?
I am not sure if that's published on pip yet.

Yes, pulled the latest commit (0b952c1) and install using pip install -e ..

This is a particular example of issue #7. I will close this one so we can focus on the broader problem there.


Balder/provide initial buffer

@bratseth PR
The first 2 commits are just cleanup.
The last is the important one.

Intentionally not. It will grow to number of requests concurrently being encoded/written. Absolute upper bound is number of threads in the thread pool. This will only be reached if there is a plug preventing data going out over the network. So I do not see any need for extra protection here.
All the other objects being held alive by a Request will be far larger than this encoded buffer.

Ok then