Try using expansion/gpu queues

Moving buildkite to the new partitions.

I think it's probably fine? Testing in ClimaCore / ClimaAtmos will be the real stress test since this package doesn't use mpi

I think it's probably fine? Testing in ClimaCore / ClimaAtmos will be the real stress test since this package doesn't use mpi

Yes, I wanted to move ClimaComms too but I there's a problem in how we do tests there when we use MPITrampoline (https://github.com/JuliaParallel/MPI.jl/issues/820).
I'll start merging this one, and I will open a PR in ClimaCore (to see what it looks like, we will merge it down the line)


Gltf Usability: traverse hierarchy by node name

What problem does this solve or what need does it fill?
After loading a Gltf file, i need to traverse the nodes in a hierarchical fashion.
Use Cases:

find a specific node (for example, by following a path of known gltf node names)
add components to each child of a specific node (for example, a node identified by its name)
(my use case: I have multiple empties in the Gltf file that define camera position and rotation)
only add specific nodes from the gltf to the bevy scene, based on name

Problem is: Right now, it seems to be flattened, and the hierarchy is not easily accessible anymore.

What solution would you like?
Two changes are necessary for this.

Allow acces to the the set of root nodes in the top level Gltf or Scene struct.
Allow access to the name of children of a given Gltf node.

Solution A (preferred, because it closely models the gltf specification):
pub struct GltfNode {

    // add this property:
    pub name: Option<String>,

    pub children: Vec<GltfNode>,
    pub mesh: Option<Handle<GltfMesh>>,
    pub transform: bevy_transform::prelude::Transform,
    pub extras: Option<GltfExtras>,
}

pub struct Gltf {
    pub nodes: Vec<Handle<GltfNode>>,
    pub named_nodes: HashMap<String, Handle<GltfNode>>,

    // add this (or maybe add it to the scene)
    pub root_nodes: Vec<Handle<GltfNode>>,

    // ...
}

Solution B (matches the current design, but seems cumbersome):
Extend Gltf::named_nodes and friends to include a hierarchy instead of only a flattened hashmap.
pub struct Gltf {
    pub nodes: Vec<Handle<GltfNode>>,
    pub named_nodes: HashMap<String, Handle<GltfNode>>,

    // add this
    pub name_hierarchy: NameHierarchy,

    // ...
}

pub struct NameHierarchy {
    pub name: String,
    pub node: Handle<GltfNode>,
    pub children: Vec<Hierarchy>
}

More solutions possible.
What alternative(s) have you considered?
There is a very cumbersome workaround. Right now, to find a child with a name, a linear search though the children of a node, combined with a linear search through named_nodes hashmap would be required.
Finding the root nodes is also cumbersome, by starting with a hashset and removing all nodes that are children of other nodes.
Maybe an easy alternative would be for the Gltf loader to attach Name components to the entities it spawns (which are accessible via Gltf::scenes). This might break things though.
Additional context
Technically, all gltf entities can have names, not only nodes. For example, the scenes too.
https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html#indices-and-names

The whole Gltf structure seems to be convoluted to me, sorry. A Gltf has handles to GltfNodes, but GltfNodes each own a copy of their children, instead of using handles? Is each node a separate asset, or are only the root nodes an asset? And the names are a separate hashmap instead of a field on the node? It's a little hard to understand, sorry. There's no way I could actually code that workaround right now

In general, I would appreciate a much more controlled way of loading the GLTF. I'd like to write code that inspects the gltf contents and instantiates selected objects as required. Does this fit the vision of bevy?

Right now, there is Asset<Gltf> containing custom gltf structs, but that also creates a Asset<Scene> containing entities.
I can use the scene representation to traverse the hierarchy and inspect the names. However, that's rather cumbersome, as we need so many indirections (and I hope bevy can improve on that). Meanwhile, it would be a quick win to inspect the gltf hierarchy without all those indirections.


Changing the 'zoom' of the active item?

Is it possible the change how much the active slide zooms/scales?

Never mind, I found it:
inactiveSlideScale


bpf: nodeport: NAT64 cleanups

Clean up a few pieces of the NAT64 nodeport code that were introduced late in the v1.13 cycle, so that we don't have to maintain them further.

/test

/test-1.26-net-next

/test


future Waring regarding DateTime_Functions - series.dt.weekofyear

Hello Antoinecarme,
thanks a lot for all your work done here.
I'm very new in python and programming at all, but thanks to your dokumentation i could start working with forecasting.
I got a FutureWaring as follows:
D:\Python\WPy64-3810\python-3.8.1.amd64\lib\site-packages\pyaf\TS\DateTime_Functions.py:50: FutureWarning:
Series.dt.weekofyear and Series.dt.week have been deprecated.  Please use Series.dt.isocalendar().week instead.
I try to modifiy but that seem to make the problem bigger:
class cDateTime_Helper:
def __init__(self):
    pass

def get_week_of_month(self, series):
    lFirstDayOfMonth = series - pd.to_timedelta(series.dt.day - 1, unit='D')
    return series.dt.weekofyear - lFirstDayOfMonth.dt.weekofyear + 1
    #return series.dt.isocalendar().week - lFirstDayOfMonth.dt.isocalendar() + 1

thanks a lot
Thomas

Hi @TomKetOS
Thanks for your intereset in PAF.
Your fix is OK.
The warning is related to newer versions of python . I try to keep pPyAF compatiblee with newer versions. Latest tested is 3.7.
There is a work in progress around that :
https://github.com/antoinecarme/pyaf/issues/149

You probably need this :
def get_week_of_month(self, series):
    lFirstDayOfMonth = series - pd.to_timedelta(series.dt.day - 1, unit='D')
    return series.dt.isocalendar().week - lFirstDayOfMonth.dt.isocalendar().week + 1

Fixed.


Upgrade rack and sinatra

Upgrade rack to version 2.0.6 or later
Upgrade sinatra to version 2.0.2 or later

it turns out from looking at the vulns in github, these warnings apply to  ci/integration/test-app


Corporal is Company level

Describe the bug
Corporal is brought up to Battalion board.
To Reproduce
Steps to reproduce the behavior:

Go to a promotion board
Promote a Sr. Trooper+ to Corporal
Board needed is only Company, unless Zeta.

Expected behavior
Corporal should only require Company board.
Screenshots

Platform
Chrome latest, modified.
Notes
The rank requirements document has an extensive overview of all the rank requirements, their billet, and board requirements.

Fixed.


Old problems still exists. void VulkanExample::draw(): Assertion `res == VK_SUCCESS' failed.

For the triangle.cpp crashing on the resizing the window.
void VulkanExample::draw(): Assertion res == VK_SUCCESS' failed. Fatal : VkResult is "ERROR_OUT_OF_DATE_KHR" in /home/wjl/projects/Vulkan/examples/triangle/triangle.cpp at line 358 triangle: /home/wjl/projects/Vulkan/examples/triangle/triangle.cpp:358: void VulkanExample::draw(): Assertion res == VK_SUCCESS' failed.
Hardware:
Nvidia 430.26  RTX2070 Max Q
Intel I9-8950HQ
Software:
Ubuntu 18.04.02LTS
kernel 4.18.17

Vulkan version 1.108

Fresh install of Ubuntu 20.04, default drivers (nvidia-driver-440). NVIDIA GTX 1080. Resizing the triangle example I get:
Fatal : VkResult is "ERROR_OUT_OF_DATE_KHR" in /home/orri/Vulkan/examples/triangle/triangle.cpp at line 363
triangle: /home/orri/Vulkan/examples/triangle/triangle.cpp:363: void VulkanExample::draw(): Assertion `res == VK_SUCCESS' failed.
Aborted (core dumped)

Due to the abysmal state of Linux I use this project as a sanity check to see if Vulkan is working correctly (because nothing can be trusted to work) before I work on my vulkan projects. It's not exactly a good sign when even this project, with its 1800+ commits can't even run correctly as it instantly crashes when resizing the triangle demo's window. I don't know why this project asserts instead of handling the out of date error, since it can happen according to the spec, maybe it's assuming that it's handled differently elsewhere, but clearly it's not.

Fresh install of Ubuntu 20.04, default drivers (nvidia-driver-440). NVIDIA GTX 1080. Resizing the triangle example I get:
Fatal : VkResult is "ERROR_OUT_OF_DATE_KHR" in /home/orri/Vulkan/examples/triangle/triangle.cpp at line 363
triangle: /home/user/Vulkan/examples/triangle/triangle.cpp:363: void VulkanExample::draw(): Assertion `res == VK_SUCCESS' failed.
Aborted (core dumped)

Due to the abysmal state of Linux I use this project as a sanity check to see if Vulkan is working correctly (because nothing can be trusted to work) before I work on my vulkan projects. It's not exactly a good sign when even this project, with its 1800+ commits can't even run correctly as it instantly crashes when resizing the triangle demo's window. I don't know why this project asserts instead of handling the out of date error, since it can happen according to the spec, maybe it's assuming that it's handled differently elsewhere, but clearly it's not.

Fresh install of Ubuntu 20.04, default drivers (nvidia-driver-440). NVIDIA GTX 1080. When resizing the triangle window I instantly get this error:

Fatal : VkResult is "ERROR_OUT_OF_DATE_KHR" in /home/user/Vulkan/examples/triangle/triangle.cpp at line 363
triangle: /home/user/Vulkan/examples/triangle/triangle.cpp:363: void VulkanExample::draw(): Assertion `res == VK_SUCCESS' failed.
Aborted (core dumped)

I use this project as a sanity check to see if Vulkan is even working on the system, before I work on my own Vulkan projects. It doesn't exactly inspire confidence in Vulkan and Linux when even this project gets things wrong, with its 1800+ commits. Is it assuming that the out of date error can't happen because it's somehow handled elsewhere differently?

OUT_OF_DATE is handled for all other examples in the example base class. The triangle one doesn't handle it because I wanted to keep it simple. But feel free to add this as a PR.

Oh alright, sorry I'm having a frustrating day with my Linux system! Also sorry for deleting my comment twice, I accidentally included my username which is my name and I wanted to keep that out.

No problem, I've had my fair share of frustrating issues with Linux, both here on my private stuff as well as at work ;)


Feature/quic server arrange the demo server to test with chrome

Arrange the demo server:
1 - Use something like wait_for_activity
2 - Allow to send files
3 - Wait for listener and connection in read_from_ssl_ids()
4 - Use SSL_handle_events() and SSL_poll(SSL_POLL_FLAG_NO_HANDLE_EVENTS)

I have rebased I am testing, I have a small improvement I will commit later today or tomorrow.

@jfclere Just FYI, I've been working on getting our CI setup to test our quic server code using the quic-interop-runner (https://github.com/quic-interop/quic-interop-runner), for which there is a chrome client instance we can use this server to test against.
In my branch (here)[https://github.com/nhorman/openssl/tree/http3-server], I've been experimenting with getting it all working, and as that branch currently stands, its passing the http3 test using our openssl container built with your server from this PR against the chrome client container.  So thats really good news.
It did require some minor modifications however.  The branch has several debug commits, but the important bits are in:

commit 537e739c2ebf3a2c7d9c02a49cec56f1f266bd00, which modifies the content-type header to be application/octet-stream (required to indicate to chrome that the file requested should be downloaded, rather than displayed in a browser window), and the addition of a content-length header, to inform chrome as to the file size (optional I think, haven't tested without it yet).
commit 68ade593fa66c4a791b755f16b468c7de4144406, which modifies the server to allow for the specification of a directory prefix from which to serve files, which the interop harness requires to be able to point the server container at the files to serve to the client.

unsure if you are interested/willing to incorporate these changes into your PR.  If not, I'm happy to do so when this is complete, but if you would be willing, it would really help us out in moving toward getting some robust interop testing going in our quic server side code.  Thanks for considering!

@nhorman We probably need a little more  make_nv(&resp[num_nv++], "content-type"), to allow html/html to text/html.
I will merge and have a closer look on Monday, many thanks for the help.

There is a small glitch with the PREFIX hanging, I prefer to make another PR later, is that OK?

Can you elaborate on what you mean by "The PREFIX hanging"?

The prefix is erased by init_ids() and filename seems incorrect ":path: /kdsavcauux" but "Can't get_file_length /www/kdavcauuux".
I have a fix  if needed.

I had fixed that in my branch, if you look on the branch I provided, init_ids looks like this:
static void init_ids(struct h3ssl *h3ssl)
{
    struct ssl_id *ssl_ids;
    char *prior_fileprefix = h3ssl->fileprefix;
    int i;

    memset (h3ssl, 0, sizeof (struct h3ssl));
    h3ssl->fileprefix = prior_fileprefix;

    ssl_ids = h3ssl->ssl_ids;
    for (i = 0; i < MAXSSL_IDS; i++) {
        ssl_ids[i].id = UINT64_MAX;
    }
    h3ssl->id_bidi = UINT64_MAX;
}

fileprefix is saved and restored in that operation using the prior_fileprefix variable

:path: /kdsavcauux" but "Can't get_file_length /www/kdavcauuux". is due to:
https://github.com/jfclere/openssl/blob/feature/quic-server/demos/http3/ossl-nghttp3-demo-server.c#L294
I only see it when running the interop tests, but:
memcpy(h3ssl->url, h3ssl->url + 1, len - 1);
is looking for problems.
I will prepare a new PR once the  interop tests are running smoothly on my box.
I have:
Test: http3 took 14.440209s, status: TestResult.SUCCEEDED
Run took 0:00:17.198377
+---------+---------+
|         | openssl |
+---------+---------+
| openssl |   ✓(3)  |
|         |         |
|         |   ✕()   |
+---------+---------+
...

24 hours has passed since 'approval: done' was set, but as this PR has been  updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

merged to quic-server branch, thank you


jsonrpc4j to support Spring Boot v3.x

Use latest 3.x version of Spring Boot. Currently we use v2.7.3 because 3.x fails to build with jsonrpc4j.
See: https://stackoverflow.com/questions/74760350/application-fails-on-run-in-a-new-release-of-springboot-3-0-0.
There's an active issue an it seems that this guy is going to make a PR(it won't be his first one): https://github.com/briandilley/jsonrpc4j/issues/303

Seems a PR was opened, but never merged... However, there exists a fork which claims to have solved this. Maybe take a fresher look at this?


LagrangeInterpolation, QuadraticSpline, CubicSpline for data with multiple channels

Hello,
In using DataInterpolations.jl for my own application, I noticed that while ConstantInterpolation, LinearInterpolation and QuadraticInterpolation allow, for example:
u = [randn(4), randn(4), randn(4), randn(4), randn(4), randn(4)]
t = [0.0, 62.25, 109.66, 162.66, 205.8, 252.3]
A = ConstantInterpolation(u,t) # or LinearInterpolation(u,t) or QuadraticInterpolation(u,t)

or
u = [randn(4,5), randn(4,5), randn(4,5), randn(4,5), randn(4,5), randn(4,5)]
t = [0.0, 62.25, 109.66, 162.66, 205.8, 252.3]
A = ConstantInterpolation(u,t) # or LinearInterpolation(u,t) or QuadraticInterpolation(u,t)

, LagrangeInterpolation, QuadraticSpline, CubicSpline do not allow this.
In this pull request, I modified these three functions so that u similar to the above examples are possible. An implementation of neural CDE in Julia does the above with DataInterpolations.jl (although with QuadraticInterpolation).
Preliminary tests of LagrangeInterpolation, QuadraticSpline, CubicSpline on some variants of the above examples seem to pass.
Please let me know what you think of the changes!

This looks good, but it needs tests.

Hi @ChrisRackauckas, I added relevant tests.


I have error ImportError

Hello. I want to use your number range filter, but I got error:
ImportError: cannot import name ‘ugettext_lazy’ from ‘django.utils.translation’

same also hit this

For Django 4:
File "...env/lib/python3.9/site-packages/admin_numeric_filter/forms.py", line 2, in
from django.utils.translation import ugettext_lazy as _
You can fix above error by change "ugettext_lazy" to "gettext_lazy".


Dropdown not updating selection

Describe the bug
When selecting an item in the drop down the selected item is shown in the box, however the information is not updated (i.e. dropdown.selected_option doesn't show the new data)
To Reproduce
Steps to reproduce the behaviour:

Create dropdown
Click down arrow of dropdown
Select option
Inspect object

Expected behaviour
Select an option and have the selected option updated.
Screenshots
Initial load: https://imgur.com/VskdJAA
Changed terrain collision: https://i.imgur.com/fwnE5Wc.png
Inspecting item in code: https://i.imgur.com/bCNe3n2.png
Platform and software (please complete the following information):

OS: Windows 10 64bit
Pygame GUI version 0.4.0
Pygame version <IP_ADDRESS>dev

Additional context
May be related, but the UITextEntryLine widgets aren't responding to clicks or mouse over.
Gist: https://gist.github.com/Snayff/544e478932cc06e6e9c406f4b424bee8#file-skill_editor-py-L128

Is that last screenshot the right one? It appears to show selected_option changed to 'FIZZLE' when your report said that wasn't happening.
Regardless I'll look into it.

Initial value was Fizzle, then changed to Activate. But the variable hasn't changed.


Inspector audio preview is tied to the master bus state

Godot version:
3.1 & 9612303
Issue description:
When trying to preview a sound resource in the inspector, no sound will come out of it.
I closed this as I found out that the audio preview is tied to the master bus state, which was muted in my project. But thinking better about it, why is it tied to the master bus?

But thinking better about it, why is it tied to the master bus?

Do you mean the audio preview should completely bypass existing buses and have its own "Editor bus" or just allow playing on different buses? I was thinking of adding the latter to the preview panel because right now previewing bus effects is quite bothersome and requires an open scene with a AudioStreamPlayer node.

@merumelu I would be nice to be able to do both.

I consider it as a bug that makes the audio buses unusable. Now, when I add or edit effect, I need then turn on autoplay and run the whole scene to hear the effect. This makes the setting audio effects pretty hard and annoying. You need to run the scene after every change of an audio bus because also sync scene changes does not work in this case.

Use case: I'm muting Master when playtesting game features that don't relate to audio and listening to music at the same time on my desktop, so that prevents me from checking SFX files.
Fortunately I have a workaround to only mute BGM.
But I still find it not intuitive that it uses the Master Audio bus expected for runtime. Or there should be an indication about this on the audio preview popup and an option to stop using it to listen to the "raw" file.


Update to Boostrap v4.3.0

REF: https://blog.getbootstrap.com/2019/02/11/bootstrap-4-3-0/

This should fix: #31

Done :)


lock or unlock editing of layouts

thank you for the awesome package!
I am making a midi controller app where people will be able to create their own layouts and play. I want to use this package for that. but, only if there were something like "lock layout editing" feature. so, when they play, they will not be able to accidentally mess up their layouts. Please implement a boolean prop for editability of pane. e.g. editable={false}
Also, it will be helpful if the event listeners for editability of panes are removed when editable=false (less computational load) and when the value is set to true, panes will have their event listeners.
thanks in advance!

You can have this feature already today.
Just set (programically) both minSize and maxSize to be equal to size.

thanks for super fast response!
yes i saw in the documentation that a pane can be locked like that. but i think it will make code messy,
for example:
<Pane minSize="{editable ? actual_min_size : get_current_size_of_pane}"
   maxSize="{editable ? actual_max_size : get_current_size_of_pane}">

instead of
<Pane minSize="{actual_min_size}" maxSize="{actual_max_size}" {editability}>

for all of the panes...
but if you kindly implement this bool, it will be very helpful... and removing the event listeners of the panes will make the app more performant.

thanks for super fast response!

I'm one of the rare Githubers whom accept the Github mail notifications settings.

yes i saw in the documentation that a pane can be locked like that. but i think it will make code messy, for example:
<Pane minSize="{editable ? actual_min_size : get_current_size_of_pane}"
   maxSize="{editable ? actual_max_size : get_current_size_of_pane}">

instead of
<Pane minSize="{actual_min_size}" maxSize="{actual_max_size}" {editability}>

for all of the panes...
but if you kindly implement this bool, it will be very helpful... and removing the event listeners of the panes will make the app more performant.

There is a huge improvement you can do that you miss! You can use Svelte data binding instead of notification listening (something I worked on personally very hard) - you have an official demo for this im the demo pages.
So you can use bind:size={some_variable} and then your editable ? ... stuff with it. Just init the variable some_variable to some number 0-100 (other than null or undefined), and then the code will be clean and automatic.
I kinda want to insist to not create a special property per every possible feature that can be done manually, as long as it not too common but easy to handle.

I understand.
Okay then, currently forgetting about the event listeners of the splitpanes, and trying to focus on implementing the UI logic...
Thank you for showing me the way to get size value for each panes. I guess i will somehow store all the sizes into an object because users will dynamically create lots of panes, and save/load layouts. Lets see where i can go
I want to know another thing:
does the panes remove event listeners when min = size = max ?
Or they are still calculated but nothing is changing?

I understand.
Okay then, currently forgetting about the event listeners of the splitpanes, and trying to focus on implementing the UI logic...
Thank you for showing me the way to get size value for each panes. I guess i will somehow store all the sizes into an object because users will dynamically create lots of panes, and save/load layouts. Lets see where i can go
I want to know another thing: does the panes remove event listeners when min = size = max ? Or they are still calculated but nothing is changing?

I don't remember, so I cannot promise anything. No garentee is promised, but I promise you that the "resize" event will always give the correct sizes of all the panes, so if the panes are "locked" the numbers that would be given(if the event will be fired) would be correct.

@vfxturjo a hint you probably know but I'll say this explicitly:
I didn't want to introduce a new feature here when it's obvious in your case what you should do.
You however implement your own logic in some new wrapper component I.e. CustomPane that calls <Pane> internally, and controls the min/max size stuff by the trick we had discussed, and expose the custom editable prop.

@vfxturjo a hint you probably know but I'll say this explicitly:
I didn't want to introduce a new feature here when it's obvious in your case what you should do.
You however implement your own logic in some new wrapper component I.e. CustomPane that calls <Pane> internally, and controls the min/max size stuff by the trick we had discussed, and expose the custom editable prop.

Thanks for reminding!
that will make my life easier ❤


improve benchmark report

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.
@arnej27959 please review

...


test 6, "allocate_as_barier_proc", failing

See #27 for some context/backstory
Is there a known issue with test 6 "allocate_as_brier_proc" when using OpenMPI and GFortran 5.2? I know from the known issues that "co_reduce" won't work until GFortran 5.3/6.1 but what's the story with this other test?

This question is intended primarily for @afanfa, I believe

relevant to https://github.com/Homebrew/homebrew/pull/46547

Hi, I cannot reproduce the issue with allocate_as_brier_proc. I'm using gcc-5.2, opencoarrays-1.2.0, mpich-3.1.4, cmake-3.1.3 on Ubuntu. Can you post the error you get?

OK let me see what's going on. I was about to say with confidence that it happens with OpenMPI on Mac OS X all the time, however, I just tried it with OpenMPI (and clang for mpicc) and it didn't happen. It was happening with gcc 5.2 for mpicc when building on the travis-ci homebrew test servers. Let me dig around some more and get back to you.

this is maddening.... it seems that there is something from my environment that allows the build and test (by hand) with brewed GCC 5.2, Clang, OpenMPI to work, but when building and testing under the restricted environment of Homebrew this doesn't work.
The output is just simply: "Test failed." It doesn't give any reason. No segfaults or anything like that.

OK upon looking at the definition of the unit test, and reading the output more carefully, it says:
test 6
      Start  6: allocate_as_barrier_proc

6: Test command: /usr/local/bin/mpiexec "-np" "2" "/tmp/opencoarrays20151202-44375-14o6csk/opencoarrays/build/src/tests/unit/init_register/allocate_as_barrier_proc"
6: Test timeout computed to be: 9.99988e+06
6:  Test failed.           1
 6/21 Test  #6: allocate_as_barrier_proc .........***Failed  Required regular expression not found.Regex=[Test passed.
]  1.07 sec

So here me /= 1 but on the following line it does equal 1...
If my memory is correct, deallocate should act as an image control statement/barrier too, shouldn't it? It seems that, perhaps, this is the problem, since the value of me changes from the if statement to the print statement.

Inside the directory chosen for installing opencoarrays with CMake, there a directory called Temporary. Inside that directory the file called LastTest.log reports the output of all the tests. Can you post the output of allocate_as_barrier_proc?

--------------------------------------------------------------------------
A system call failed during shared memory initialization that should
not have.  It is likely that your MPI job will now either abort or
experience performance degradation.

  Local host:  IBB-MBP.local
  System call: unlink(2<EMAIL_ADDRESS>  Error:       No such file or directory (errno 2)
--------------------------------------------------------------------------
<end of output>
Test time =   1.32 sec
----------------------------------------------------------
Test Pass Reason:
Required regular expression found.Regex=[Test passed.
]
"syncall" end time: Dec 02 13:56 EST
"syncall" time elapsed: 00:00:01
----------------------------------------------------------

17/20 Testing: syncimages
17/20 Test: syncimages
Command: "/usr/local/bin/mpiexec" "-np" "32" "/tmp/opencoarrays20151202-56450-hbtpjn/opencoarrays/build/src/tests/unit/sync/syncimages"
Directory: /tmp/opencoarrays20151202-56450-hbtpjn/opencoarrays/build
"syncimages" start time: Dec 02 13:56 EST
Output:
----------------------------------------------------------
 Test passed.
<end of output>
Test time =   0.30 sec
----------------------------------------------------------
Test Pass Reason:
Required regular expression found.Regex=[Test passed.
]
"syncimages" end time: Dec 02 13:56 EST
"syncimages" time elapsed: 00:00:00
----------------------------------------------------------

18/20 Testing: hello_multiverse
18/20 Test: hello_multiverse
Command: "/usr/local/bin/mpiexec" "-np" "2" "/tmp/opencoarrays20151202-56450-hbtpjn/opencoarrays/build/src/tests/integration/coarrayHelloWorld/hello_multiverse"
Directory: /tmp/opencoarrays20151202-56450-hbtpjn/opencoarrays/build
"hello_multiverse" start time: Dec 02 13:56 EST
Output:
----------------------------------------------------------
 Greetings from image  1 of  2
 Greetings from image  2 of  2
 Test passed.
<end of output>
Test time =   0.06 sec
----------------------------------------------------------
Test Pass Reason:
Required regular expression found.Regex=[Test passed.
]
"hello_multiverse" end time: Dec 02 13:56 EST
"hello_multiverse" time elapsed: 00:00:00
----------------------------------------------------------

19/20 Testing: coarray_burgers_pde
19/20 Test: coarray_burgers_pde
Command: "/usr/local/bin/mpiexec" "-np" "2" "/tmp/opencoarrays20151202-56450-hbtpjn/opencoarrays/build/src/tests/integration/pde_solvers/coarrayBurgers/coarray_burgers_pde"
Directory: /tmp/opencoarrays20151202-56450-hbtpjn/opencoarrays/build
"coarray_burgers_pde" start time: Dec 02 13:56 EST
Output:
----------------------------------------------------------
 Time =  0.60065795534754485
 On image            1 u =  -3.6062644769485318E-016  0.55703975723770405        1.1137114029330639        1.6695096165091936        2.2228610006371610        2.7616422370249762        3.1602423341809680        2.5585980904689771
 On image            2 u =   1.9794875987846594E-015  -2.5585980904689749       -3.1602423341809680       -2.7616422370249771       -2.2228610006371614       -1.6695096165091943       -1.1137114029330646      -0.55703975723770482
 Test passed.
<end of output>
Test time =   0.07 sec
----------------------------------------------------------
Test Pass Reason:
Required regular expression found.Regex=[Test passed.
]
"coarray_burgers_pde" end time: Dec 02 13:56 EST
"coarray_burgers_pde" time elapsed: 00:00:00
----------------------------------------------------------

20/20 Testing: co_heat
20/20 Test: co_heat
Command: "/usr/local/bin/mpiexec" "-np" "2" "/tmp/opencoarrays20151202-56450-hbtpjn/opencoarrays/build/src/tests/integration/pde_solvers/coarrayHeatSimplified/co_heat"
Directory: /tmp/opencoarrays20151202-56450-hbtpjn/opencoarrays/build
"co_heat" start time: Dec 02 13:56 EST
Output:
----------------------------------------------------------
 Test passed.
<end of output>
Test time =   0.74 sec
----------------------------------------------------------
Test Pass Reason:
Required regular expression found.Regex=[Test passed.
]
"co_heat" end time: Dec 02 13:56 EST
"co_heat" time elapsed: 00:00:00
----------------------------------------------------------

End testing: Dec 02 13:56 EST

Got it. For reasons that I don't know, your environment is using an optimization flag different from -O0. There is a known issues with GFortran about this phenomena (https://groups.google.com/forum/#!msg/opencoarrays/RZOwwYTqG80/46S9eL696dgJ).

OK, so to clarify, if I'm reading the email thread correctly:
There is a gcc/gfortran bug that causes -O2 optimization to give incorrect results. This problem will be fixed in an upcoming gcc release.
Does the advice about optimization flag apply only to compiling the tests, or also the entire opencoarrays package?

Also, this might be worth adding to the STATUS.md

I suspect the cause of this is passing *std_cmake_args to CMake from the homebrew formula. This results in:
cmake .. -DCMAKE_C_FLAGS_RELEASE= -DCMAKE_CXX_FLAGS_RELEASE= -DCMAKE_INSTALL_PREFIX=/usr/local/homebrew/Cellar/opencoarrays/1.2.0 -DCMAKE_BUILD_TYPE=Release -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_VERBOSE_MAKEFILE=ON -Wno-dev

The culprit is -DCMAKE_BUILD_TYPE=Release I just confirmed this. I think that the CMakeLists.txt should probably be set up to function properly even when a "Release" build type is selected... Maybe I'll file a new issue or submit a PR for that. Thanks for helping me get to the bottom of this, @afanfa, I really appreciate it!

This issue has been in my todo list for too long. It is time to fix it. Thanks for working on this.

PR #43 should take care of this issue, and also update the STATUS.md. PR made against master, so commits will probably need to be git cherry-picked into the branch-1.0.0 branch.

Prematurely closed this before actually fixing the CMakeLists.txt... reopening.

The bug in question has been patched in GCC 5.3 and trunk: https://groups.google.com/forum/#!topic/opencoarrays/038m9fZP2GQ


supporting graph generation based on input dependency

Fixes #24

Support for generating a graph based on a dependency user enters
Coloring the main module incase of the graph of all dependencies
Removed some commented code which was left in #28

@alenkacz I've abstracted the logic for the if and else blocks into separate functions. Hope this provided some more clarity. I've also added tests for all the functions being used in that file 🙂

Thanks for reviewing @alenkacz! Made the changes. Please drop a "lgtm" to merge this if they're okay 🙃

/lgtm


Bug: False positive in some cases when trying to detect if something is touching something

Small demo ced made yesterday: https://sprig.hackclub.dev/?id=c58a2b84fd62f520e993dba0c096eb87
The trellis changes to a vine when the bean is touching. Notice the false positive when the bean is in the left-bottom corner.

fix wen

Fixed now!


Update Cosmos DB extension to version 0.3.2

Please find the vsix package here.

There's an issue with this build. The build with the fix is here. Is it possible to upload the corrected build or should I spin a new version?


Fix PHPCBF error when path to executable is not set

What does this implement/fix? Explain your changes.
When no phpcbf path is set in config, beautifier throws error. This fixes it.
Does this close any currently open issues?
no
Any other comments?
fixing thing I overlooked
Checklist
Check all those that are applicable and complete.

[x] Merged with latest master branch
[ ] Added examples for testing to examples/ directory
[x] Travis CI passes (Mac support)
[ ] AppVeyor passes (Windows support)

Published to v0.28.23


Where can I find the docker images with earlier versions of firefox?

I'm wanting to use imacro's and the most recent versions no longer allow file access so I'd like to use an older version of firefox along with the associated older imacro's version.   Where can I see a list of these versions so I know the proper one to pull?

Releases page ? https://github.com/jlesage/docker-firefox/releases

Thanks.  That only goes back to v58 where I'd have to go to v52.  Guess I'll end up having to build an image myself.  Appreciate the response.


CollectionView#reveal doesn't work

Problem description
I tried to create exact widget structure that exists in the real project. The logic is that when we focus on text input, boundsChanged event is triggered then CollectionView must scroll to the end. However, it doesn't scroll.
Expected behavior
When we run the snippet below and focus on the text input, the CollectionView must scroll to the end.
Environment

Tabris.js version: 2.1.1
Device: iPhone 6
OS: 11.0.3

Code snippet
const {CollectionView, TextInput, Composite, TextView, ui} = require('tabris');

let people = [
  ['Holger', 'Staudacher'],
  ['Ian', 'Bull'],
  ['Jochen', 'Krause'],
  ['Jordi', 'Böhme López'],
  ['Markus', 'Knauer'],
  ['Jordi', 'Böhme López'],
  ['Jordi', 'Böhme López'],
  ['Jordi', 'Böhme López'],
  ['Markus', 'Knauer'],
  ['Moritz', 'Post'],
  ['Ralf', 'Sternberg'],
  ['Tim', 'Buschtöns']
].map(([firstName, lastName]) => ({firstName, lastName}));

let composite = new Composite({left: 0, top: 0, right: 0, bottom: 0}).append(
  new CollectionView({
    left: 0, top: 0, right: 0, bottom: 0,
    itemCount: people.length,
    cellHeight: 256,
    createCell: () => {
      let cell = new Composite();
      new TextView({
        left: 30, centerY: 0, right: 30,
        alignment: 'center'
      }).appendTo(cell);
      return cell;
    },
    updateCell: (cell, index) => {
      let person = people[index];
      cell.apply({
        TextView: {text: person.firstName}
      });
    }
  })
).on('boundsChanged', () => {
  console.log('boundsChanged event is triggered');
  composite.find('CollectionView').first().reveal(-1);
}).appendTo(ui.contentView);

new TextInput({
  bottom: 20, left: 16, right: 16,
  message: 'Type here, then confirm'
}).appendTo(ui.contentView);

Have you tried to use the resize event?

Moritz, the result is the same with the resize event as well.

This is now fixed. See: https://github.com/eclipsesource/tabris-ios/issues/836.


Deprecate whisparr

I don't want or have a need to maintain this here anymore

Done in https://github.com/onedr0p/containers/commit/ad58a2c3f964afb7edd45dee144b1b2d7f768050


[Onboarding] When Play Services install fails, login fails w/o way to resolve issue

Not sure how to repro.


apiMetrics not working (nest v8)

All the apiMetrics aren't showing up in the metrics page, only the default system ones are.
Using the basic snippet.
OpenTelemetryModule.forRoot({
      metrics: {
        hostMetrics: true, // Includes Host Metrics
        defaultMetrics: true, // Includes Default Metrics
        apiMetrics: {
          enable: true, // Includes api metrics
          // timeBuckets: [], // You can change the default time buckets
        },
        defaultLabels: {
          app: process.env.npm_package_name,
          version: process.env.npm_package_version,
        },
      },
    }),

if I only have apiMetrics enabled, I get:
# no registered metrics

as the metrics response. I have no idea how, but one in around 500 tries I saw for a second the needed metrics, but can't reproduce - so in general, it doesn't work.

@danshapir are you using express or fastify ?

Could you share more info about your your project? In the example folder I actually have added an example with nests 8.x.

Using express, pino.
I debugged the code, the API metrics middleware runs and the counters are changing, but not displayed on the metrics endpoint

@pragmaticivan latest version on all packages

@danshapir I'm not able to replicate with any of the examples, would you be able to create a replicable repo I could take a look? Right now it's really hard to figure out what's the problem.

@pragmaticivan My bad! I didnt await the otelSDK.start() in the main.ts.
I'll hijack this issue for another issue. the defaultLabels parameter for the opentelemetryModule doesn't work - it just ignores what I pass in.

Released in 2.5.0.  defaultLabels is available inside apiMetrics property. Some metric plugins don't allow custom labels yet.


📎 Integrate lint/useGroupedTypeImport in organizeImports

Description
useGroupedTypeImport allows factorizing type imports:
- import { type A, type B } from ""
+ import type { A, B } from ""

This behavior should be integrated into organize-imports action.

I'm not sure this should be part of the import sorting. Is there a good reason for doing that?
Are there other tools that do that? If so how?
Cargo for example doesn't join imports.

Actually, you are the one who proposed it 😅
I have no strong opinions about that...

Past ematipico was wise 😆  and present ematipico is grampy. Feel free to ignore my present comment.

Do you mean https://github.com/biomejs/biome/discussions/454? This is not the point of this issue.

No, I wondered why they don't do that since rust is a side-effect-free language so that they can merge imports without possible repercussions. Simply that.

Can I look into this one?

Hi @emab, I will work on #817 in the coming days. I am afraid our works may lead to Git conflict. I will come back here once I addressed #817.

Closing in favor of #3015


[feature] Diff is highlighting whitespace changes even if  "Ignore whitespace" option is ticked

Setup: v<IP_ADDRESS> self hosted with Docker on Ubuntu 22. In "Global filters" of the settings, I have ticked " Ignore whitespace
Ignore whitespace, tabs and new-lines/line-feeds when considering if a change was detected."
Use case: I monitor webpages and get alerted. When I receive an alert, I click on the Diff link and quickly scan the Diff page to see what has changed.
Unexpected behavior: Since I have the "Ignore whitespace" option ticked, I do not expect to see them colored on the Diff page. However, they are. See screenshot.
Why it is bothering: It's not critical. It makes the Diff feature unusable for some pages, because I would scroll the page until I see color. But since many "false positive" changes are colored red and green, I am not able to quickly notice the real changes.

Hi, I filed this one in November 2022 but I do not know how to fix it https://github.com/kpdecker/jsdiff/issues/389
I'm open to a PR if you want to submit something, otherwise, probably this doesnt get fixed soon
If anyone can help with that library, I would be very grateful (and i'de probably find a way to pay you for your help too)

I'm open to a PR if you want to submit something, otherwise, probably this doesnt get fixed soon

Sorry, I'll probably break more things than anything else :)
This issue and https://github.com/kpdecker/jsdiff/issues/389 are different though. If I understand correctly, you want jsdiff to ignore whitespace in chosing when to highlight the lines, but still output whitespace. That'd make the diff more readable indeed! I think the main purpose of a Diff is to highlight relevant changes, before maintaining the layout, so I can live with it.
For this issue, which focuses on the highlighting, maybe I found a workaround:
Currently: even if  Ignore whitespace is selected in Global Filters, opening a https://cd.io/diff/abcdef-123456/ link opens it without the "Ignore Whitespace" tickbox ticked (see screenshot).
Proposed: Pages  https://cd.io/diff/abcdef-123456/ load by default with the "Ignore Whitespace" tickbox set to the status of "Ignore whitespace" in Global Filters at /settings#filters
What do you think?

if you select Words it's a lot easier to see, does that help?

if you select Words it's a lot easier to see, does that help?

Agreed, showing "Words" instead of "Lines" is an improvement compared to the current default.
I'd still think Lines+IgnoreWhitespaceTicked is better, since:

Words+IgnoreWhitespaceUnticked can make it easy to skip through small changes (one letter or one word in a long line), while it's hard to scroll past a whole line highlighted.
Words instead of Lines, without IgnoreWhitespace ticked, still highlights single spaces.

+1 for jbd7 proposal
would also like to have Ignore Whitespace pre-checked on http://<IP_ADDRESS>:5000/diff/... pages


I get "Forbidden" when trying to login/signup.

No error pops up in the npm commandline or inspector. I don't know what's wrong.

Source works on my local machine; this only happens on the ubuntu 16.04 server.
What could be the cause? Sorry for little information... I just don't know what to do. It has to be something related to permissions, maybe with mongodb?

I usually see this when I accidentally access the site without https://.

Sorry to necro... I was just wondering if there was a way to run without ssl? It was running without before, but somehow now it requires ssl =/

You need to see what the server logs say. It may also be caused by an invalid CSRF token.

I'm sorry; which logs to I look in?

The server logs. You need to debug hapi and see why it's returning this in your case.

Okay I'm making a whole new VPS to host aqua on. I know this is very nooby, and I apologize again for the bother I am...
What is the install process if the arch linux server/vps only will be used for aqua?
Install openssh, mongodb, node, configure iptables, etc.?

I just want to make sure I'm on the right track. Thanks ^_^

I'm not really sure about that.


Add community label to new bug reports

Updates the bug reporting issue template to automatically add a "community" label. This label will let us differentiate between community-raised issues (which are potentially subject to our 2 week resolution SLA) and internal defects.
The assumption is that incoming defects via that form will be raised by our community.
Where someone in our team uses the form, they can just remove the community label afterwards.

Should this be the other way around? i.e. we should be on top of keeping an eye on all the things awaiting triage ?

Moving to draft for now, due to the question above.

Fair point @origami-z.
In that case, I suppose the triage process should look at who reported a bug and add the community label as needed.
@joshwooding If you're Ok with that, then I propose the following:

I'll update the bug board in our project to show issues with "awaiting triage" OR "community" labels
I'll update the project automation to add new issues with "awaiting triage" to the project (right now, it only applies to issues with "awaiting triage" AND "community" labels)
I'll add a note to our internal Confluence documentation
Close this PR :-)

Sound good?

Fair point @origami-z.
In that case, I suppose the triage process should look at who reported a bug and add the community label as needed.
@joshwooding If you're Ok with that, then I propose the following:

I'll update the bug board in our project to show issues with "awaiting triage" OR "community" labels
I'll update the project automation to add new issues with "awaiting triage" to the project (right now, it only applies to issues with "awaiting triage" AND "community" labels)
I'll add a note to our internal Confluence documentation
Close this PR :-)

Sound good?

Sounds good to me

Ok, I've implemented those changes now. Therefore closing this PR


DITA OT project publishing - separate temporary files folders for each deliverable

I can set the "clean.temp=no" parameter to specify that the transformation temporary files folder should not be deleted, but right now all deliverables are published using the same temporary files folder, making it hard to debug for each deliverable and see what temporary files have been created for them.
So I think that for each deliverable we should have a separate subfolder in the transformation temporary files folder, to keep the temporary files separately. This would help also if at some point we want to make the processing parallel for all deliverables.

If the memory store is enabled, would it not also need to be partitioned by deliverable where applicable?


phpList integration

Can't wait to get started on this in May/June :) Campaign chain looks amazing! ( @michield )

Hey, a lot of stuff changed since then. We hope you give it a try :)


[BUG] Module cannot be found in the module registry at registry.terraform.io

Community Note

Please vote on this issue by adding a :thumbsup: reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version
1.5.5
AzureRM Provider Version
3.78.0
Affected Resource(s)/Data Source(s)
n/a
Terraform Configuration Files
// Based on https://github.com/claranet/terraform-azurerm-aks-light/blob/ca2f620ac9f08b5a44e9deabdf188eb3deff9489/README.md

module "aks" {
  source  = "claranet/aks-light/azurerm"
  version = "7.0.0" # https://github.com/claranet/terraform-azurerm-aks-light/blob/ddc8b23f06e60757d4e5bb87db441a19640aee4d/VERSION

  // ...
}

Debug Output/Panic Output
...
Downloading registry.terraform.io/claranet/regions/azurerm 7.0.0 for azure_region...
- azure_region in .terraform/modules/azure_region
Downloading registry.terraform.io/claranet/keyvault/azurerm 7.5.0 for keyvault...
- keyvault in .terraform/modules/keyvault
Downloading registry.terraform.io/claranet/diagnostic-settings/azurerm 6.5.0 for keyvault.diagnostics...
- keyvault.diagnostics in .terraform/modules/keyvault.diagnostics
- remote_state_stack_terraform in ../../../../../modules/cadcorp/terraform-azurerm-remote-state
Downloading registry.terraform.io/claranet/rg/azurerm 6.1.0 for resource_group...
- resource_group in .terraform/modules/resource_group
╷
│ Error: Module not found
│
│   on r-aks.tf line 1:
│    1: module "aks" {
│
│ Module "aks" (from r-aks.tf:1) cannot be found in the module registry at registry.terraform.io.
╵

Error: running "terraform init

Expected Behaviour
I'd expect the module "aks" example from the current README.md to work.
Actual Behaviour
See the "Debug Output/Panic Output" section.
Steps to Reproduce

Copy the usage example
Run terraform init

Important Factoids
The registry only lists the aks module superseded by aks-light.

References
No response

Don't know why, it was not on the registry indeed.
I published it again: https://registry.terraform.io/modules/claranet/aks-light/azurerm/latest

@Shr3ps  Awesome, thank you!


[API Integration] OpenClipArt.org (original #169)

This issue has been migrated from the CC Search Frontend repository
Author: janetpkr
Date: Thu Jul 11 2019
Labels: providers,🙅 status: discontinued

per many twitter user requests! https://twitter.com/rejon/status/1141844914168377346
Original Comments:
annatuma commented on Mon Feb 24 2020:

Provider API Endpoint / Documentation

No documentation found, emailed OpenClipArt.org to find out if this integration is possible.
Provider description

This is a clip art provider, with almost 160,000 objects in the collection.
Licenses Provided

All objects are CC licensed.
SECTIONS BELOW THIS POINT NEED TO BE WORKED ON PRIOR TO INTEGRATION
Provider API Technical info

General Recommendations for implementation

The script should be in the src/cc_catalog_airflow/dags/provider_api_scripts/ directory.
The script should have a test suite in the same directory.
The script must use the ImageStore class (Import this from
src/cc_catalog_airflow/dags/provider_api_scripts/common/storage/image.py).
The script should use the DelayedRequester class (Import this from
src/cc_catalog_airflow/dags/provider_api_scripts/common/requester.py).
The script must not use anything from
src/cc_catalog_airflow/dags/provider_api_scripts/modules/etlMods.py, since
that module is deprecated.
If the provider API has can be queried by 'upload date' or something similar,
the script should take a --date parameter when run as a script, giving the
date for which we should collect images. The form should be YYYY-MM-DD (so,
the script can be run via python my_favorite_provider.py --date 2018-01-01).
The script must provide a main function that takes the same parameters as from
the CLI. In our example from above, we'd then have a main function
my_favorite_provider.main(date). The main should do the same thing calling
from the CLI would do.
The script must conform to PEP8. Please use pycodestyle (available via
pip install pycodestyle) to check for compliance.
The script should use small, testable functions.
The test suite for the script may break PEP8 rules regarding long lines where
appropriate (e.g., long strings for testing).

Examples of other Provider API Scripts

For example Provider API Scripts and accompanying test suites, please see

src/cc_catalog_airflow/dags/provider_api_scripts/flickr.py and
src/cc_catalog_airflow/dags/provider_api_scripts/test_flickr.py, or
src/cc_catalog_airflow/dags/provider_api_scripts/wikimedia_commons.py and
src/cc_catalog_airflow/dags/provider_api_scripts/test_wikimedia_commons.py.

source
kgodey commented on Mon Feb 24 2020:

We may need to do this via Common Crawl if there's no API.
source

mathemancer commented on Tue Feb 25 2020:

They have a 'developers' site listing API endpoints, but none seem to work:

https://openclipart.org/developers
source
mathemancer commented on Tue Feb 25 2020:

@annatuma @kgodey Have we had any direct contact with them?  They have an email listed for contact regarding their API:

<EMAIL_ADDRESS>source
annatuma commented on Wed Apr 22 2020:

@annatuma @kgodey Have we had any direct contact with them? They have an email listed for contact regarding their API:

<EMAIL_ADDRESS>
No response on the Feb 24th email, pinged them again.
source
annatuma commented on Mon Apr 27 2020:

Update: they'll be in touch when the API goes live.
source

Open clipart now has an API in beta
Also, they are already included in the meta search feature.

Noticing that we have OpenClipArt images via Wikimedia:
https://api.openverse.engineering/v1/images/0aff3595-8168-440b-83ff-7a80b65dea42/
Not sure if it includes the full dataset but perhaps OpenClipArt can be considered a sub-provider of Wikimedia.


Fix arguments with spaces

This one should fix issue #122. It does so by keeping the arguments separately in a TStringList instead of breaking things up using a space as a delimiter.
I overloaded ParseInput so that it can take both a command as string and values as TStringList just one long string as it originally was. This ensures that existing code that uses ParseInput internally continues to work.
Hope this is ok! :)

Per discussion in #122, this turned out to be a very convoluted way of doing things!


add colab files

@afermg I'm guessing this is good to merge now?

@afermg clarified that this branch should not be merged. He has created a separate branch to host notebooks alone (see https://broadinstitute.github.io/2023_12_JUMP_data_only_vignettes/). These notebooks are autogenerated using a script https://github.com/broadinstitute/2023_12_JUMP_data_only_vignettes/blob/b7bb53816ce51dfe1e9b731998e218e6c09f2b27/tools/deploy.sh


Example Issue 01

This is the first thing I need to do

This issue is finished and will update the milestone progress bar. This shows how close we are to the sprint goal. However, these can't be waited, so easy Issues have the same weight as hard Issues.


Aries Bifold (Mobile Agent React Native) Q2 Roadmap

Aries Bifold (Mobile Agent React Native) Q2 Roadmap
TL;DR
This proposal outlines strategies to enhance Bifold by tackling issues such as a complicated theme file, limited scalability in component customization, and challenges in adding new components. The suggested solutions involve simplifying the process for themes, enabling more in-depth personalization with style sheet overrides, providing ways to replace UI components, and using Bifold as an npm package in individual React Native apps for added flexibility and expanded features.
Medium Term Arcitecture Roadmap
The following issues, identified within our current architecture, are planned to be addressed by the community soon. These issues are primarily derived from the Bifold Summit 2023. The summit not only aids in pinpointing the issues but also provides guidance on potential solutions.
Issues

The existing theme file has become unwieldy, exceeding its original purpose. It's become the default method for customizing all visual aspects of the application, resulting in too many variables for developers to adjust to suit their specific needs.

The existing method to override or inject custom components via the useConfiguration hook is effective but not highly scalable. Developers need a more manageable solution to ensure that the application remains intuitive for developers. This will also facilitate the contribution of clean, easy-to-maintain code.

Currently, there's no straightforward way for developers to inject their own components without starting from scratch and creating their own React application. They then have to import what they need from Bifold and write their own custom components as required.

The project in unable to upgrade past React Native 0.66.5 due to our ability to compile and support related components such as Indy SDK.

Proposed Solutions
We need to find a new pattern that will allow:

Theme

We aim to provide teams with the essential tools to swiftly launch a branded app with minimal effort. This includes transitioning from the current Bifold theme of green and black to, for instance, to Brazil's green and yellow or British Columbia's blue and gold.
The color palette will be confined to colors that significantly influence the application at a high level, as specified by the Bifold style guide. This approach also allows the application to switch between a light and dark theme but restricts the customization of individual components by introducing new styles. For instance, if changing the border color of a button isn't currently possible, this file won't support such a modification unless the addition of this change is first proposed during a Bifold working group meeting.

Style Overrides

In cases where merely altering the color palette is insufficient and a more comprehensive approach to customizing the app is needed, we will offer a method to provide components with their own style sheet overrides. These will then be integrated to create a product where the supplied style either modifies or supplements the existing default style of a component.

Custom Components

In cases where teams find the user interface provided by Aries Bifold unsuitable for their needs, we aim to offer a mechanism that enables easy overriding of any component within the entire application. For instance, if a team desires a significantly different style for UI Buttons, they can import and utilize their own custom component.

Bifold as a UI Component Library

Teams that aspire to extend beyond the capabilities provided by the three mechanisms mentioned above may likely need to take a different approach than what Aries Bifold offers. In such situations, teams will create their own React Native application and use Bifold as an npm package. This allows them to import any desired UI/UX components, offering maximum flexibility while still taking advantage of existing UI components as needed.
Next Steps
Based on the above discussion, we plan to create a series of issues to gradually achieve our technical architecture goals. Each issue should correspond to an identified problem or proposed solution and should include documentation of the implementation.

Issue
Description

Text
Text

Above is the working copy of the document I mentioned on the May 9th Working Group Call. Comments and feedback welcome.


Errors format

Hi!
This is my first try to improve errors format (discussion can be found in #162). I'd like to get review on changes and discuss some points.
At first here are simple example which will be used to show new errors format:
from typing import Dict, List, Union
from uuid import UUID

from pydantic import BaseModel, ValidationError

class TestDict(BaseModel):
    x: int
    y: int
    z: str

class TestModel(BaseModel):
    a: List[TestDict]
    b: int
    c: TestDict
    d: Union[int, UUID]
    e: Dict[int, int]
    f: List[Union[int, UUID]]

try:
    TestModel.parse_obj({
        'a': [
            {
                'x': 'not_int',
                'y': 42,
                'z': 'string',
            },
        ],
        'b': 'string',
        'c': {
            'y': 42,
        },
        'd': 'string',
        'e': {
            'foo': 'bar',
        },
        'f': [
            'string',
        ],
    })
except ValidationError as e:
    print(e.json())

And errors output:
[
  {
    "loc": "a.0.x",
    "msg": "invalid literal for int() with base 10: 'not_int'",
    "type": "value_error"
  },
  {
    "loc": "b",
    "msg": "invalid literal for int() with base 10: 'string'",
    "type": "value_error"
  },
  {
    "loc": "c.x",
    "msg": "field required",
    "type": "value_error.missing"
  },
  {
    "loc": "c.z",
    "msg": "field required",
    "type": "value_error.missing"
  },
  {
    "loc": "d",
    "msg": "invalid literal for int() with base 10: 'string'",
    "type": "value_error"
  },
  {
    "loc": "d",
    "msg": "badly formed hexadecimal UUID string",
    "type": "value_error"
  },
  {
    "loc": "e.key",
    "msg": "invalid literal for int() with base 10: 'foo'",
    "type": "value_error"
  },
  {
    "loc": "f.0",
    "msg": "invalid literal for int() with base 10: 'string'",
    "type": "value_error"
  },
  {
    "loc": "f.0",
    "msg": "badly formed hexadecimal UUID string",
    "type": "value_error"
  }
]

Questions:

Is this format good to go (msg kept for backward compatibility and can be removed, context can be easily added)?
As you can see we are using key postfix if error occurred in dictionary key, is it okay?
As you can see there are two errors for field d (and f.0) because they are complex and contains sub fields, I think we need to expose this information in loc, maybe by using postfix, something like d.sub.0 and d.sub.1. Any ideas?
Big question how to display errors in plain text? For now it's very simple:

a.0.x
  invalid literal for int() with base 10: 'not_int' (type=value_error)
b
  invalid literal for int() with base 10: 'string' (type=value_error)
c.x
  field required (type=value_error.missing)
c.z
  field required (type=value_error.missing)
d
  invalid literal for int() with base 10: 'string' (type=value_error)
d
  badly formed hexadecimal UUID string (type=value_error)
e.key
  invalid literal for int() with base 10: 'foo' (type=value_error)
f.0
  invalid literal for int() with base 10: 'string' (type=value_error)
f.0
  badly formed hexadecimal UUID string (type=value_error)

TODO:

[ ] Discuss all questions
[ ] Write tests for exceptions.py module
[ ] Write tests for new functions in utils.py module
[ ] Introduce additional exceptions like MinLength(ValueError) with context

Also we will need to do something if a key includes a dot.
I'm not sure what the solution is, but I guess the first step is to store the loc as a tuple so users have the option to work on the raw tuple.
We could:

replace with \. using backslashes will be very ugly in json
replace with <dot> then we have to escape lt and gt
maybe clearer to just return a list for loc if it has more than one item.

not sure. ideas?

I don't mind whether we do it in one PR or multiple but I think it'll cause less pain for users if we release all the changes in one go, eg. before we next release we should move to context etc. Maybe a new PR.

Agree with you, better to ship all changes in one release. I want to introduce context in another PR, this PR is too big already and it can be hard to review if I add more changes.

Maybe we should use key to reduce the chance of confusion with a real key?

Good idea, also I think in future we can add ability to change __key__ using config.

I think we should have one error per location. The point here is to provide the most usful information and duplicate error will be a brainfuck for end uers.

I think we can introduce one error, something like:
types = ' or '.join([field.type_ for field in self.sub_fields])
TypeError('f'value is not a valid {types}, got {display_as_type(v)}'')

What do you think?

maybe clearer to just return a list for loc if it has more than one item.

Let's go with this option, it's simple to implement and can be very useful for developers.

@samuelcolvin ping :)

I'm away, will look on Wednesday.

One more example to discuss about sub fields:
class TestDict(BaseModel):
    x: int
    y: int
    z: str

class TestModel(BaseModel):
    d: Union[int, TestDict]

try:
    TestModel.parse_obj({
        'd': {
            'x': 42,
        },
    })
except ValidationError as e:
    print(e.json())

[
  {
    "loc": [
      "d"
    ],
    "msg": "int() argument must be a string, a bytes-like object or a number, not 'dict'",
    "type": "type_error"
  },
  {
    "loc": [
      "d",
      "y"
    ],
    "msg": "field required",
    "type": "value_error.missing"
  },
  {
    "loc": [
      "d",
      "z"
    ],
    "msg": "field required",
    "type": "value_error.missing"
  }
]

Looking at this example I have no idea what to do with errors.

Good idea, also I think in future we can add ability to change key using config.

Regarding multiple errors in the same location. There are basically two cases:
1. all type errors
We get a type error when trying each sub-type. Here we should definitely try to return one saying not an instance of foo, bar or spam, I guess with a type like type_error.union.
This might require some changes to the errors we raise. For example in your example with Union[int, UUID] we should probably change the errors on both int and UUID to always be TypeErrors. This is really correct, since xyz is not of type UUID rather than a bad a value of UUID.
2. value errors / not all type errors.
I guess here we really have to return all the errors. It's ugly, but it's the only way of retaining all the information someone might need.
I'm sorry to change my mind but I guess the best way of doing this is to return each error separately, so have duplicate locations in the list of errors. We can do something pretty when displaying errors so we have
d
  invalid literal for int() with base 10: 'string' (type=value_error)
  badly formed hexadecimal UUID string (type=value_error)

I guess we can add {'union': True} to the context when we implement that to give extra information.

I guess here we really have to return all the errors. It's ugly, but it's the only way of retaining all the information someone might need.
I'm sorry to change my mind but I guess the best way of doing this is to return each error separately, so have duplicate locations in the list of errors.

No problem, it's already implemented so I don't need to change anything.

We can do something pretty when displaying errors so we have

I don't think that we need to merge error messages, let's keep it as simple as possible.
@samuelcolvin please review code and let me know if I need something to improve.

ok, will do, busy today so might be tomorrow.

@samuelcolvin review it again please

awesome, thank you very much. We'll need to remember to update history before the next release.


remove console.log

fixes #3819

Coverage remained the same at 68.199% when pulling b008a6a2aa39e6f355bea887c93328cddb91ce63 on remove-console-log-subflow-js into dc7fef63952548277d7759c327ce2909fdce0a3c on master.


Group and Group Members Data Models Do Not Have Full Name for Setting into Violations

The data accessor does return embedded parents for:
Group,
GroupMembers

After discussing with jiyun, we need to do more research here, i.e. to make sure that group name is unique within the organization.
Or else, we can close this here, as groups is a graph, that can not be represented with full_name.

Confirmed, group name is unique.

Based on discussion with Joe, we will create a full_name that will be unique based on appending the parent to the current member.
Example:
group/my_group<EMAIL_ADDRESS>

Fixed by #1291


The language server immediately crashes upon starting up

Describe the bug**
As soon as I open VSCode, I am greeted with a message that the F# server crashed many times and will not be restarted.
Steps to reproduce

Open VSCode.
Wait for at most 10 seconds.
Look at the bottom-right of the screen.

Link to sample reproduction
https://github.com/teo-tsirpanis/Farkle (it crashes even with a clean repository so no need to build anything)
Expected behaviour
The F# server would not crash.
Screenshots

Machine info

OS: Windows 10
.NET SDK version: 5.0.102
Ionide version: 5.2.0

It seems that my computer has a problem and cannot recognize any .NET SDK.
But still the tools could have shown a nicer message.

It seems that my computer has a problem and cannot recognize any .NET SDK.
But still the tools could have shown a nicer message.

We would welcome any contributions to the startup flow around giving users better error messages.

We would welcome any contributions to the startup flow around giving users better error messages.

I found it. When I uninstalled an old .NET SDK it changed the PATH and Program Files (x86) was put before Program Files.

I found it. When I uninstalled an old .NET SDK it changed the PATH and Program Files (x86) was put before Program Files.

I found it. When I uninstalled an old .NET SDK it changed the PATH and Program Files (x86) was put before Program Files.

I did this too, but what I get from the F# output is a reference to a folder path that ionide seems to send, and it breaks it:
(I've already set FSharp.dotnetRoot)
Unhandled exception: System.ComponentModel.Win32Exception (2): An error occurred trying to start process 'c:\repos\fs\FirstIonideProject\dotnet' with working directory 'c:\repos\fs\FirstIonideProject'. The system cannot find the file specified.
That dotnet folder is not created by default when scaffolding a F# project. To me ionide seems to be failing to look for the dotnet.exe ?
Give me some clues please on where should I look to correct this. I've checked my system path env var, and the first thing there is the path to dotnet sdk.


WDLs to revert/convert between BAM, FASTQ and uBAM

Three different use cases:

[x] Reverting several per-readgroup bams to paired FASTQs
[x] Converting paired FASTQs to uBAM
[x] Reverting multi-readgroup BAM to uBAM

Note that this builds on https://github.com/broadinstitute/wdl/pull/81

[x] Test RevertRGBamsToPairedFastQsWf: 42140ee0-e134-42b1-ae34-b5ef5bfbbb25

I'm considering splitting out the cram to bam conversion to make the revert & sort step more generic.

@vdauwera that seems like a very good idea.

Great, will do that then, @ktibbett.

[ ] Test RevertBamToUnmappedRGBamsWf: abb24610-b621-4b5a-9e10-590be65b2624

Change notes

I stripped the original script down to just RevertSam + SortSam. Converting from CRAM is too specific, and I think validation should be done separately from processing for the generic use case.

In RevertSam I added SANITIZE and MAX_DISCARD_FRACTION but replace OUTPUT_MAP by just OUTPUT for the sake of being simple and generic.

Currently the inputs json uses some older b37-aligned data but I could update it to hg38 if desired. As it stands it aligns nicely with the use case so I don't really care either way.

Added a bunch of comments + a header to document usage and license terms.

Hmm test failed -- RevertSam failed with this error:

SORT_ORDER must be queryname when sanitization is enabled with SANITIZE=true.

I'm going to assume this means I should set SO in RevertSam, but then I wonder why the separate SortSam step -- or was that supposed to be changing to coordinate? There was some ambiguity in the original script: RevertSam said SORT_ORDER=queryname but filename said .coord.sorted.unmapped.bam.

Huh, the RevertSam command had a SORT_ORDER=coordinate line I hadn't noticed. Will change that. @ktibbett do you know why the script was emitting coordinate-sorted ubams but then sorting them by queryname, instead of just emitting qname-sorted from the get-go? This doesn't make a lot of sense to me... but I'm probably missing something.

[ ] Test RevertBamToUnmappedRGBamsWf with SortSam stripped out: 5175e654-0838-4cc0-b9a4-1898abbad6f5

This is just running RevertSam now.

@dshiga , can you please look at @vdauwera 's question about RevertSam outputting in coordinate-sorted order...?

Hi @vdauwera, just to give some context about the original WDL and sorting:
For our use case, we run the workflow on coordinate sorted CRAMs and so the input to RevertSam is a coordinate sorted BAM. By specifying SORT_ORDER=coordinate, we prevent RevertSam itself from trying to do any additional sorting -- by default it will sort in queryname order. (It would have been clearer to put SORT_ORDER=unsorted here instead. I didn't do that at the time because I was misled by some of the RevertSam code that makes it look like it will try to make a SortingCollection unless you exactly match the SORT_ORDER already in the input BAM header, though that's not actually the case.)
However -- we actually want the outputs to be queryname sorted, because the ubams that we generate on prem and push to the cloud are normally queryname sorted and we wanted this workflow to give us back exactly the same ubams we would have fed into the single sample pipeline to make the CRAM.
So then why not just let RevertSam do that sorting? I figured that instead of one big sort in RevertSam, which requires a lot of disk and memory and takes a long time, we would be better off sorting each of the resulting read group level ubams, which can be done in parallel on smaller machines.
This is not at all evident from the original WDL itself, though, and I intend to add some clarifying comments to it!

Oh I see, that makes way more sense now -- thanks for clarifying, @dshiga! Do you have any benchmarking numbers on the runtime of the RevertSam job if doing the sort vs. total runtime of unsorted RevertSam + separate SortSam step? We don't have a choice for the use case I'm covering because we have to use SANITIZE = true but I'd like to document this in a note on efficiency.

I can tell you that running the existing workflow on a 45 GB CRAM took ~11.5 hours, 11 hours of which was RevertSam. The sort jobs took ~30 minutes each (but ran in parallel), and the validate jobs, also in parallel, took about 5 minutes.
Unfortunately, I don't have numbers for doing the sorting inside RevertSam. I just vaguely remember it taking a long time and having trouble running real (as opposed to slimmed down) data through it, because it wanted so much memory and disk.

Ah ok, thanks for this.

This is ready for review.

Need to update the output syntax for workflow nesting.

[x] Update & test ConvertPairedFastQToUnmappedBamWf: bd54620c-89c1-44e9-929b-46427556920e
[ ] Update & test RevertBamToUnmappedRGBamsWf: 68e0d983-0bf3-44af-87f8-9a3723f5e1aa
[ ] Update & test RevertRGBamsToPairedFastQsWf: d06c9971-a5c8-43e8-9e39-25db270b2b7e

All workflows successful on Cromwell 24.


Vision dashboard backend with data characteristics

The complete vision dashboard minus compatibility with cohorts and other metadata. Includes everything included in the Vision dashboard backend without data characteristics PR but includes the data characteristics tab.

Description

Checklist

[ ] I have added screenshots above for all UI changes.
[ ] I have added e2e tests for all UI changes.
[ ] Documentation was updated if it was needed.

Codecov Report

Merging #1669 (25e2f87) into main (611ac56) will increase coverage by 7.82%.
The diff coverage is n/a.

:exclamation: Current head 25e2f87 differs from pull request most recent head 9487888. Consider uploading reports for the commit 9487888 to get more accurate results

@@            Coverage Diff             @@
##             main    #1669      +/-   ##
==========================================
+ Coverage   89.04%   96.87%   +7.82%
==========================================
  Files         105       12      -93
  Lines        5534      160    -5374
==========================================
- Hits         4928      155    -4773
+ Misses        606        5     -601

Flag
Coverage Δ

unittests
96.87% <ø> (+7.82%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

raiwidgets/raiwidgets/responsibleai_dashboard.py

...idgets/raiwidgets/responsibleai_dashboard_input.py

responsibleai/responsibleai/_interfaces.py

raiwidgets/raiwidgets/fairness_dashboard.py

responsibleai/responsibleai/_internal/__init__.py

...ai/responsibleai/rai_insights/rai_base_insights.py

...sibleai/responsibleai/rai_insights/rai_insights.py

...ponsibleai/databalanceanalysis/balance_measures.py

responsibleai/responsibleai/feature_metadata.py

raiwidgets/raiwidgets/dashboard.py

... and 81 more

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


Not useful

How is this supposed to be configured? Could a link to any documentation about the corresponding configuration be added. This by itself is pretty useless.

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

ID: e563a255-5406-284a-965b-33596e660a3c
Version Independent ID: 0ec2b3bb-8937-50be-d499-df3659fdd5ce
Content: System.Runtime.Caching.Configuration Namespace
Content Source: xml/ns-System.Runtime.Caching.Configuration.xml
Product: dotnet-api
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Thanks for your feedback, @DarthDerrr. This page describes the general functionality that the types in the namespace make available. It is intended primarily to list the types in the namespace and not to provide detailed configuration documentation.


Questionaire Responses

Describe the bug
Updated both the Fhir Engine and the Datacapture libraries to the latest versions. Upon submiting a questionaire, the app crashes with the error as shown below
Component
SDC library
To Reproduce
Steps to reproduce the behavior:

Have the latest updates on libraries. Go to patient's details, complete a survey
Click on the submit button
Scroll down to logs and see the line creating the error
See error

Expected behavior
Upon submitting the data, it was my expected to get the data saved and like the previous versions
Screenshots

Smartphone (please complete the following information):

Device: Techno LC6a
Android version: 9
Build number: LC6a
Version 28

Additional context
N/A
Would you like to work on the issue?
I am still learning the FHIR Engine and the associated libraries

Closing this issue as it's a duplicate of #1029


[Bug]: Error occurred while parsing the file using bge-m3 and qwen-7.2b deployed with Infinity and Xinference.

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

RAGFlow workspace code commit ID
v0.14.1
RAGFlow image version
v0.14.1
Other environment information
No response
Actual behavior
Error occurred while parsing the file using bge-m3 and qwen-7.2b deployed with Infinity and Xinference.
2024-12-02 15:17:24,915 INFO     1168409 HTTP Request: POST http://<IP_ADDRESS>:9997/v1/embeddings "HTTP/1.1 200 OK"
2024-12-02 15:17:25,356 INFO     1168409 set_progress(3d05036eb07d11efa36bd47c44d5570d), progress: 0.6961199294532627, progress_msg:
2024-12-02 15:17:32,213 INFO     1168409 HTTP Request: POST http://<IP_ADDRESS>:9997/v1/embeddings "HTTP/1.1 200 OK"
2024-12-02 15:17:32,819 INFO     1168409 set_progress(3d05036eb07d11efa36bd47c44d5570d), progress: 0.700352733686067, progress_msg:
2024-12-02 15:17:39,757 INFO     1168409 HTTP Request: POST http://<IP_ADDRESS>:9997/v1/embeddings "HTTP/1.1 500 Internal Server Error"
2024-12-02 15:17:39,759 INFO     1168409 Retrying request to /embeddings in 0.848969 seconds
2024-12-02 15:17:40,638 INFO     1168409 HTTP Request: POST http://<IP_ADDRESS>:9997/v1/embeddings "HTTP/1.1 400 Bad Request"
2024-12-02 15:17:40,660 INFO     1168409 set_progress(3d05036eb07d11efa36bd47c44d5570d), progress: -1, progress_msg: Page(1~100000001): [ERROR]Embedding error:Error code: 400 - {'detail': '[address=<IP_ADDRESS>:28547, pid=140] Model not found, uid: bge-m3-0'}
2024-12-02 15:17:40,672 ERROR    1168409 run_rembedding got exception
Traceback (most recent call last):
  File "/opt/PythonProjects/szzz-llm-rag/rag/svr/task_executor.py", line 403, in do_handle_task
    tk_count, vector_size = embedding(cks, embd_mdl, r["parser_config"], callback)
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/PythonProjects/szzz-llm-rag/rag/svr/task_executor.py", line 307, in embedding
    vts, c = mdl.encode(cnts[i: i + batch_size])
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/PythonProjects/szzz-llm-rag/api/db/services/llm_service.py", line 209, in encode
    emd, used_tokens = self.mdl.encode(texts, batch_size)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/PythonProjects/szzz-llm-rag/rag/llm/embedding_model.py", line 282, in encode
    res = self.client.embeddings.create(input=texts,
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/media/user/data_one/miniconda3/envs/szzz-llm-rag/lib/python3.11/site-packages/openai/resources/embeddings.py", line 125, in create
    return self._post(
           ^^^^^^^^^^^
  File "/media/user/data_one/miniconda3/envs/szzz-llm-rag/lib/python3.11/site-packages/openai/_base_client.py", line 1260, in post
    return cast(ResponseT, self.request(cast_to, opts, stream=stream, stream_cls=stream_cls))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/media/user/data_one/miniconda3/envs/szzz-llm-rag/lib/python3.11/site-packages/openai/_base_client.py", line 937, in request
    return self._request(
           ^^^^^^^^^^^^^^
  File "/media/user/data_one/miniconda3/envs/szzz-llm-rag/lib/python3.11/site-packages/openai/_base_client.py", line 1026, in _request
    return self._retry_request(
           ^^^^^^^^^^^^^^^^^^^^
  File "/media/user/data_one/miniconda3/envs/szzz-llm-rag/lib/python3.11/site-packages/openai/_base_client.py", line 1075, in _retry_request
    return self._request(
           ^^^^^^^^^^^^^^
  File "/media/user/data_one/miniconda3/envs/szzz-llm-rag/lib/python3.11/site-packages/openai/_base_client.py", line 1041, in _request
    raise self._make_status_error_from_response(err.response) from None
openai.BadRequestError: Error code: 400 - {'detail': '[address=<IP_ADDRESS>:28547, pid=140] Model not found, uid: bge-m3-0'}
2024-12-02 15:17:40,676 ERROR    1168409 handle_task got exception for task {"id": "3d05036eb07d11efa36bd47c44d5570d", "doc_id": "5b8f3452a55711ef8de0d47c44d5570d", "from_page": 0, "to_page": 100000000, "retry_count": 0, "kb_id": "4e6f8dc6a55711efa604d47c44d5570d", "parser_id": "qa", "parser_config": {"raptor": {"use_raptor": false}}, "name": "question_to_sql.csv", "type": "doc", "location": "question_to_sql.csv", "size": 926118, "tenant_id": "3c1a1b4e797b11efb0ead47c44d5570d", "language": "Chinese", "embd_id": "bge-m3@Xinference", "img2txt_id": "qwen-vl-max", "asr_id": "paraformer-realtime-8k-v1", "llm_id": "qwen2.5-instruct@Xinference", "update_date":<PHONE_NUMBER>301}

Expected behavior
No response
Steps to reproduce
The model deployed with Xinference uses a QA-based approach for knowledge base parsing, and Infinity is used as the vector database.

Additional information
No response

Obviously, the model deployed by xinference can't be accessed.

Obviously, the model deployed by xinference can't be accessed.

The error message is to use the model id: BGE-M3-0, but I have not configured BGE-m3-0, I have only configured bge-m3, I suspect that there is an extra -0 which causes the access failure. Because the first few times of embeding can be carried out normally, I do not know which step will become bge-m3-0

I see. My Batch_size is set too large, which causes the video memory to exceed. Because xinference is deployed using docker, I did not see the error message


Flutter 3.0 support

I just upgraded to the latest Flutter version and when I try to use the latest
connectycube_sdk: ^2.1.1
I get a dependency error.

Because no versions of connectycube_sdk match >2.1.1 <3.0.0 and connectycube_sdk 2.1.1 depends on xmpp_stone 0.4.3-dev.1, connectycube_sdk ^2.1.1 requires xmpp_stone 0.4.3-dev.1.

@TatankaConCube
After more investigation it seems this happens when we use latest auto_router package along with CC
Auto route wants xml version 6.0.0
However xmpp_stone which is used by CC uses xml version 5.1.0
I could not find the xmpp_stone package to open an issue. is it maintained by you people?
In the worst case can you fork the xmpp package so we can use continue using it?
Because no versions of connectycube_sdk match >2.1.1 <3.0.0 and connectycube_sdk 2.1.1 depends on xmpp_stone 0.4.3-dev.1, connectycube_sdk ^2.1.1 requires xmpp_stone 0.4.3-dev.1.
And because xmpp_stone 0.4.3-dev.1 depends on xml ^5.1.0 and auto_route_generator >=4.2.0 depends on xml ^6.0.1, connectycube_sdk ^2.1.1 is incompatible with auto_route_generator >=4.2.0.
So, because bare_bones depends on both connectycube_sdk ^2.1.1 and auto_route_generator ^4.2.0, version solving failed.
pub get failed (1; So, because bare_bones depends on both connectycube_sdk ^2.1.1 and auto_route_generator ^4.2.0, version solving failed.)
exit code 1

@aytunch the xmpp_stone is an open-source lib. The version 0.4.3-dev.1 was prepared by me with some features required for Connectycube SDK. We will try to plan to investigate and fix your issue next week.

@TatankaConCube thanks
As a temporary workaround I am using this and at least can continue debugging
dependency_overrides:
  xml: ^5.1.0

@aytunch I made the PR with the required feature, you can ping @vucoye too to speed up merging it

@TatankaConCube since your PR is merged, when can we expect to see the new CC version?
Thanks

@aytunch today we have released version 2.2.3 with required updates


Community communication channel

Jangouts development has worked so far in a impulse-driven way. We get contributions and contributors in every Hack Week, pre-GSoC, GSoC itself... But even if we have had contributions from more than 10 people in one way or another, I feel we still lack a community common vision.
There are several topics I would like to discuss with everybody interested in Jangouts. The days of @imobachgs and myself deciding on the project direction in our small office should be over. So the first question is what should be the channel for discussing those topics.
Some projects simply use issues in Github for that kind of conversations. I'm not sure I like that.
Many other projects, including Janus Gateway, use Google Groups for open general discussion (even support), keeping Github issues just for more concrete bug reports and fate requests.
Last but not least, since openSUSE already acted as some kind of patron giving us one slot for GSoC, we could maybe give another step in that direction and ask openSUSE for a mailing list<EMAIL_ADDRESS>What alternative do you prefer? Any other option?

Any mailing list is fine for me. Even github issues is something I can live with, if it comes with some kind of road map, where we wanna go and what should be included and what not.

We could also look at https://www.fossil-scm.org/xfer/doc/trunk/www/foss-cklist.wiki or http://spot.livejournal.com/308370.html for points we might be lacking for good open-source projects.
Overall, I would prefer a ML on a neutral domain (e.g<EMAIL_ADDRESS>over a openSUSE one, to not give the impression, that it only works on openSUSE or should be driven mostly by openSUSE people.

+1 on avoiding opensuse.org, since I think this would deter some people outside the openSUSE community. I think Google Groups is a pretty good option - low maintenance, neutral, good for sane people who like mailing lists and also for totally crazy people who prefer web forums ;-)
Also +1 for keeping the github issue tracker. I like the precision that that can bring to even architectural / mission discussions. Mailing list threads can sometimes go off on tangents too easily (although that's fine as long as people remember to change the Subject header ...)

+1 for avoiding opensuse.org and using jangouts.org
I  prefer jangouts.org instead feeding data trolls like google

@uhelp What's your suggestion for the technical part of jangouts.org? Buying the domain is the easy part. But if you don't want to feed data trolls I guess you are suggesting to host our own mailing list software on our own server. Or do you have any alternative in mind that is as straightforward as Groups  from the setup/maintenance point of view?

Bullshit about opensuse.org. Show some pride! Would be a really
nice. Quite some projects are hosted by fedora or debian and noone
bothers. I'd avoid opensuse.org just for the antiquated mailinglist
software and archive there.
Google groups is nice to interface with non techies as it looks like
a web forum to them but is actually a mailinglist.

Yes, I'd prefer running all of it on a root server.
Some docker containers and things are easily moveable/upgradable
.
Jangouts should also run on different distris, so tutorials for other distris and setup howtos are needed as well. Some nginx container, a framework for CMS should do the trick.
And of course a demo site as well.
Hence pride may be the wrong term here.
Nothing prevents to credit openSUSE on the jangout site.

+1 to Google Groups, like @lnussel says is actually a mailing list, and a lot of project use it so non tech users and tech people that no contribute normally to open source projects are more accustomed to use it.
If we want to get more contribution to the project, IMHO this solution will be useful for a bigger range of people.

Just in case someone needs it, there is now http://jangouts.org/cgi-bin/mailman/listinfo/devel available.
And then there was the question about the overlap with jitsi which is also opensource videophony and seems to be a rather active and mature project. Did anyone try it? Can we do things they cannot?

I like the idea of using Google Groups. Mailing lists already take a big part of my day and I would not like to overload it. I never used Google Groups, but I saw it in some projects and the fact that it looks like a forum would make it easy to catch up when threads get very big, plus it's more organised from a UX point of view :)
Github issues are also a good option to me. So, either Google Groups or Github Issues, they both look like good ideas.
What is important to me is what @jreidinger mentioned in his comment: having and preparing some sort of road map with milestones, and how we could decide on where to go, voting on issues perhaps? or do we program/design upon what we think is best for the project?

@bmwiedemann Thanks for setting up a mailing list! I'm fine with using it (but I'm also not against Google Groups, although I'm not a big fan). I would use the ML for community communication and general discussion and Github issues for specific development code and bug reporting (they look like complementary to me).
My 2 cents.
PS: I agree that we urgently need some kind of vision/roadmap for the future.

About the rest of the infrastructure, currently we have a demo server at https://jangouts.tk/. Unfortunately we're missing proper documentation.
Regarding the Docker instances I'll be happy to share them, for example, in Docker Hub. But we need some manpower to create, maintain and document them. I'm quite interested in Docker and I could try to do it but if we have some expert onboard... :)

Ok. So looks like everybody likes the combination of

Github issues to track feature requests
a non-openSUSE mailing list

The only point that is not crystal clear from the discussion is whether that list should be Google Groups or a self-hosted mailman.
For me, the self hosted solution is only an option if we have at least two volunteers that can sign with blood that they will administer that service for at least one year. Otherwise, I prefer the almost-zero setup and zero maintenance solution (Google Groups).
If we don't have such volunteers, the decision is made. If they step up, I will create a poll to decide between both possibilities.

To speed up things, no need to wait for the volunteers to pop-up in order to start voting. So...
+1 to this comment (using the "add your reaction" button in Github) if you prefer Google Groups.
-1 to this comment if you prefer the self-hosted mailman (assuming we have volunteers to maintain the service).

@bmwiedemann @aspiers @lnussel @cyntss Any vote? (see previous comments)

I don't mind either way, so I'm abstaining.

Vote given 👍

So we have a winner. I will create a Google group today or tomorrow. Thanks all.

Done. Here is the group url https://groups.google.com/forum/#!forum/jangouts and here are the instructions to join https://support.google.com/groups/answer/1067205?hl=en

I just realized the good & old mailing-list style way of joining is not described in that document.
Just send a mail to<EMAIL_ADDRESS>It simply works.


Implement named workspaces

Add workspaces feature to maintain different sets of history and variables. Allow user to save the current workspace with a name and perhaps a note. Allow user to load one of these saved workspaces. Workspaces will be represented by tabs, which the user will be able to add, delete, and name.

Implemented in 941b71f717ad5e7e2cc221fb7b91baaa5a6ac41d.


chat flow duration: replace duration with date picker

It is more intuitive for user to select an expiration date then a duration.
Instead of asking to enter weird duration code, use a nice data picker.

PR at: https://github.com/threefoldtech/jumpscaleX_threebot/pull/658 and https://github.com/threefoldtech/jumpscaleX_core/pull/801
Changelog

Add the new datetimepicker component

Add some validations to avoid empty/old dates

Updated chatflows to use the new time picker

Test some of the chat flows

As per https://github.com/threefoldtech/jumpscaleX_threebot/issues/637#issue-609955035 there was a limitation on duration to not be less than 1 hour, now I can set date After now by 1 minute, is the limitation not needed in the new date picker?

As per #637 (comment) there was a limitation on duration to not be less than 1 hour, now I can set date After now by 1 minute, is the limitation not needed in the new date picker?

set at https://github.com/threefoldtech/jumpscaleX_core/commit/f22237e5574e55473308dcbfc21279e68e0330b6

Verified
Branch: rc_10.5.3
threebot commit: 67ce0d84b2c615bf515eaa1141c0b1fcd78bbbdc
core commit: https://github.com/threefoldtech/jumpscaleX_core/commit/7d372250cb826cc070f90ac225df9b08f4810d35


hands textures can be set as wall texture

Describe the bug
hand texture can be set as a wall texture and will kinda break the programm
To Reproduce
Steps to reproduce the behavior:

set i.e images/left_hand.xpm as a wall texture
start cub3D
turn in circles
See error

Expected behavior
only textures with the size of 64 by 64 pixels should be allowed as wall texture
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

fixed by @vytkuklys few days ago


[PTX-2232] Added logic to validate applications restored by backup

@vinayakshnd this might impact other scenarios, so please run a dev-test job with a non-backup scenario these cases SetupTeardown,AppTasksDown,AppScaleUpAndDown,VolumeDriverDown,VolumeDriverAppDown,VolumeDriverDownAttachedNode,VolumeUpdate,RebootOneNode and paste the link here, you can use these apps mysql, postgres, elasticsearch, nginx-sharedv4, wordpress-sharedv4

Recent tp-dev-test job failed with PWX-13637
https://jenkins.portworx.co/job/Torpedo/job/tp-dev-test/652/console

tp-dev-test passed with VolumeUpdate,StopScheduler on elasticsearch,mysql,nginx,nginx-sharedv4,postgres,wordpress-sharedv4
https://jenkins.portworx.co/job/Torpedo/job/tp-dev-test/684/parameters/

@vinayakshnd checked the logs and RebootAllNodes is not a valid test, can you please run using RebootOneNode is the correct one, could you please run at least with this test?

@thiguetta tp-dev-test passed with RebootOneNode here: https://jenkins.portworx.co/job/Torpedo/job/tp-dev-test/686/


Ghpages and Navigo. Redirect to index.html on accessing subpath.

Accessing a subroute directly, returns to the 404.html. How can you redirect from 404.html to index.html?

GitHub pages does not allow you to control the routing. In order to have Navigo working you need to amend the http routing and point all the requests to a single html file. With GitHub pages this is not possible. The only workaround that comes to my mind is to generate all the pages as static files and those files to have the same content. But even then the 404 page may not be properly handled.

I was going through projects using this package, and found this workaround.
https://github.com/rafgraph/spa-github-pages
On the 404 page, it converts the sub route, to a query which is executed on index.html itself. Effectively redirecting properly. I would suggest, adding this to the readme for future reference.


Another attempt to fix o.o.transport.netty4.OpenSearchLoggingHandlerIT fails w/ stack overflow

Signed-off-by: Andriy Redko<EMAIL_ADDRESS>Description
This time no guesses, I was able to reproduce the issue. The Netty dumps raw messages (in hex) into logs and for some specific rare patterns (I have an example), the apprender filter blows with StrackOverflowError. The change to appender filter to watch only for single line log statements (expressed in expectations) fixed the issue.
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@nknize @andrross the StackOveflowError should be fixed now, the exact cause was found


helm chart for hubble-ui deployment removed nodeSelector and tolerations on 1.11.15 release

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
This PR removed nodeSelector and toleration settings for the hubble-ui deployment.
The current 1.11 branch (1.11.16) values.yaml seems to suggest this was a mistake, as there are defaults listed: https://github.com/cilium/cilium/blob/v1.11.16/install/kubernetes/cilium/values.yaml#L939-L946
Cilium Version
1.11.15
Kernel Version
n/a
Kubernetes Version
1.25
Sysdump
No response
Relevant log output
No response
Anything else?
Unless this was intentional, I can put a PR to revert.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

This issue has been fixed by #25182.


Disabled links in pagination still work

Right now, you need one of the Javascript plugins for the links to be disabled completely, otherwise if you just have a hash, it will take you to the top of the page. An easy way to fix this is to allow a  tag for disabled "links" with the same properties as anchors within .pagination so it doesn't break the layout.

Duplicate issue—we'll get to it when we can.