feat(chat): change sorting of applications alphabetically (Issue #2285)

Description:
Models. assistants, applications should be ordered alphabetically
Issues:

Issue #2285

UI changes

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review


Overhaul the top sections of the class reference (GUI classes)

The top sections of classes are often one of the first things users read about them, so they are important to get right.
Part of a series; this is the one dedicated to the GUI & Text team. Here are the others so far: #76526 (core), #76549 (animation), #76600 (physics)
I mostly touched up the short descriptions and occasionally the full descriptions and the tutorials sections. I also tweaked a little bit of documentation to the side and added a few missing descriptions.
I also added TextServerDummy documentation, but split that off to a different PR: #76699

Rules for brief descriptions
I'm abiding by a set of rules for consistency. I had them in mind when writing all descriptions, but violated them intentionally sometimes.

Use the articles "a" and "an". This is helpful for words that can be multiple things, i.e. "light" which can be a noun, an adjective, and a verb. This, and the fact it's grammatically correct, helps with reading comprehension in many cases.

Use a single sentence with punctuation. If two sentences are needed, don't use newline.

Never use text formatting (i.e. italics) or external links.

Don't use capitalization for normal words. If referring to a class, use a reference.

For nodes, always answer "What is this?". For non-node objects, it's also OK to answer "What does this do?"

Avoid self-referencing, such as "Popup: Popup is a [...]"

Avoid circular reasoning such as "CanvasLayer: Canvas drawing layer."

Exception 1: It's something common folk are familiar with, i.e. "Timer: A countdown timer."
Exception 2: The class can't be used by people who don't know the term, i.e. it's okay to say "XML" in XMLParser.

When a class is abstract, start with "Abstract base class for [...]".

I often used "Holds X" and "Stores X" to replace "Contains X" - I think it improves clarity that X is the main thing, not just one of the things the resource holds.

Try to stay under 120 characters without compromising the quality of writing. (Sometimes it's impossible, in that case, go on for a bit longer)

Thanks a ton to everyone who participated in a 3+ hour long discussion about how to describe Viewport!

I noticed an annoying tendency of repeating brief description in description, and even worse, you changed some descriptions that at least tried to be different. I think repeating should be avoided, because it's redundant.

Ok finished reviewing. GitHub started to lag near the end 😬
I really think that you should remove all description sentences that repeat brief description. idk if we have any official policy against that tho.

It's a common pattern that I also hated, but occasionally I felt like I had to do it... @KoBeWi since I was behind your tail fixing up and commenting on your review this whole time, could you address some of my comments?

p.s. I educated myself on the difference between input fields and editors. I think TextEdit, CodeEdit, and GraphEdit easily pass the bar needed to count something as an editor.

could you go back and address some of my comments?

Will do. Not now, but surely tomorrow.

Timezone buddies! :3

Thanks for the review! I feel good about these changes once more.

Thanks!

Cherry-picked for 4.0.4. ViewportTexture changes depend on another PR, so I skipped those.


Examples don't work with Direct3D 11 backend (DXGI_SWAP_EFFECT_FLIP_DISCARD problem)

When I run any example program with D3D11 backend I just get white window. What happens is every frame  m_swapChain->Present(syncInterval, 0) gets hung up for two seconds or so and then returns  DXGI_ERROR_WAS_STILL_DRAWING. Bgfx doesn't output any errors.
RenderDoc can capture frames and they are rendered correctly, it's just that the window never gets updated to show them. D3D9, D3D12, OpenGL, Vulkan backends all work without a problem.
I'm building on Windows 10 64 bit with vs2019. GPU is GTX 760 with latest drivers.

Looking into it again, changing swap effect to DXGI_SWAP_EFFECT_DISCARD instead of DXGI_SWAP_EFFECT_FLIP_DISCARD fixes the problem. My system should support it and the swapchain is created successfully, but the described above happens. Why could this be?
I tried other swap effects and non-FLIP ones work while FLIP ones do not.


Remove role_tags from cisagov/terraform-state-read-role-tf-module configuration

🗣 Description
This pull request modifies the Terraform code to remove role_tags from the cisagov/terraform-state-read-role-tf-module configuration.
💭 Motivation and context
This is in accordance with the changes in cisagov/terraform-state-read-role-tf-module#5.
Note that var.tags is passed in via the provider's default tags, so there is no need to use additional_role_tags here.
🧪 Testing
I applied these changes to our COOL production and staging environments and verified that the only change that terraform apply wanted to apply was to add some tags to an extant IAM policy resource.
✅ Checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All new and existing tests pass.

Are we not updating the provisionterraform provider to exclude the Workspace tag? We're doing similar in other PRs to remove the role_tag key.

See commit e69e239.

Do we want to also add the Workspace-exclusion foo here like we have elsewhere (e.g. cisagov/cool-userservices-dns@b86b715?)

See commit e69e239.


Adapt to CachingConnectionFactory customizations when running on CF

As a continuation of spring-cloud/spring-cloud-stream-binder-rabbit#115, we would have to handle situations where people have configured arbitrary CCF properties via the connector javabean properties mapping.
Refer to this comment for background.

PullRequest has been merged and cherry-picked to 1.3.x


Does it work with AspNetCore 2.0 ?

I'm migrating an application from katana to aspnetcore 2.0.
Given https://github.com/aspnet/Security/issues/1310 i do not understand if i have to bring everything is this new services.AddAuthentication world or not, i see that IdentityServer4.AccessTokenValidation still use a classic middle-ware approach.
Do you have any guidance ?
Thanks

No. Use the MS JwtBearer middleware instead.


Map/3 Highlighting of buildings

As a user I want to differentiate between buildings of the HPI, UP and other unrelated ones easily. They should be highlighted or otherwise marked brightly. (maybe kill in the analog plans all around campus.)

The HPI buildings have to marked (preferably in orange, to avoid confusion)

Planning Poker (just edit this):
Nikkel: S

Closed with #84


testutil: set test title

Sometimes, notably in evp_test, it may be useful for the subtests to be able to set their own title.  In the case of evp_test, the test file name is a nice possiblity.
Checklist

[x] tests are added or updated

Merged.  b73c5e054a9211fb493b2733baa678c71750fe51 and 46fcbf77bc6f2a287cb7266c58c204aa3960e456
Thanks!


Create button component

In order to reach linked content on the careers page, we will create a button component
Acceptance criteria

Component should be able to handle both a single button and group multiple buttons together
Buttons can act as a link to internal and external page

Sub-tasks

[ ] Create button group component in Storybook
[ ] Make button component available to web
[ ] Add button array to page schema

Discovery: should buttons be able to link to downloadable content such as PDF, Excel, etc?
In order to ensure good quality we should (Keep the ones we need for this US)

[ ] Perform integration testing
[ ] Perform functional testing
[ ] Extra focus on usability
[ ] Test for portability
[ ] Test for accessibility
[ ] Create automated acceptance test/smoke test
[ ] Perform performance and load test
[ ] Perform user testing
[ ] Perform security testing

Things to figure out:

Do the EDS buttons cover all use cases here https://eds.equinor.com/components/buttons/
Should we allow for different variations. If so, how?
Should we have an option for both buttons with and without icons - if with, then how do we select the icon to use?
Do buttons that are used as links (to internal or external pages) go against the design language/accessibility? (a button is a button, not a link)

If the publisher adds one link, display as a outline button (but still as an )
If the publisher adds more than one link, display as content links

We decided to add the c2a to the text block component.

@nilsml @BirteThornquist  What do you think, should we do all the work related to the use of the EDS button on coloured backgrounds as a part of this task or create a separate one?
We'll probably need (at least)

Better contrasts, Birte has suggested to use a white background on the button for Envis
Another hover colour as the baby blue from EDS looks strange on e.g. spruce wood

Ready for testing / verification @petterwildhagen  As mentioned, this is no longer a separate component in the content list, but one field in the text block component.
The idea we are testing is to render one c2a as a outlined EDS button and > 1 as a list of content links like we do in related content. Se /careers/figma-example for some examples.

[ ] Component should be able to handle both a single button and group multiple buttons together
[ ] Buttons can act as a link to internal and external page

@SvSven @BirteThornquist @wenche
We are able to add both a single button and multiple buttons - but nothing is visible in the preview or published page
Internal/external links are added, but not tested du to the above
Question: could the component have an optional title, ore should we add a textcomponent with one word for e.g. Downloads etc, see e.g. this page with buttons: https://www.equinor.com/en/investors/quarterly-results.html
@petterwildhagen

@meols
I can see in the Studio that the links you have added are created by using the first variant of the buttons, before we decided to move this into the Text block component. (And this was obviously still available when you started to test because of the issues with the production environment :/ )
So to test this, you should add links with the Text block component
I have created several on https://energyvision.app.radix.equinor.com/careers
Question: could the component have an optional title, ore should we add a textcomponent with one word for e.g. We haven't actually discussed this, we have titles for the related content component in the News articles, but in this case it's already inside a text block. But one of those things we can easily tune later when more content is added.
Downloads etc, see e.g. this page with buttons: https://www.equinor.com/en/investors/quarterly-results.html I don't think this example has been taken into consideration at this point by Birte, I would say we can look at this while we are creating more components, and probably solve it in a better way. :)


docs: Document use of the DCO which is now required for all PRs

Merging without review because it was already approved by TSC and enabled, and this is merely documenting what contributors need to do to affix the DCOs to their commits.


[Feature] Integration with baserow

Summary
Provide integration with Baserow. The implementation may follow the same integration template as the other databases integration.
Motivation
Baserow is under development means to be to Airtable.com and Google Sheets what Appsmith is to AppSheet and other no-code platforms.
Additional Context
I opened a similar issue in the Baserow issue manager https://github.com/bram2w/baserow/issues/8
 Front conversations

@jibe-b thank you for the feature request! Baserow looks interesting. Do you have open APIs for the platform yet? What type of authentication do you plan to support?

@jibe-b thank you for the feature request! Baserow looks interesting. Do you have open APIs for the platform yet? What type of authentication do you plan to support?

This will be worked as part of this action https://github.com/appsmithorg/appsmith/issues/4518

Use case is to have a self hosted baserow with a self hosted appsmith.

I definitely second this - It seems that Baserow and Appsmith are a match made in heaven! That integration would be awesome

I third this and think that this integration would be amazing.
A senior developer advocate at AppSmith also agrees: https://www.linkedin.com/posts/joseph-appsmith_baserow-activity-7213895815851900929-E2Io?utm_source=share&utm_medium=member_desktop

Hello guys, I want to express my complete support to this request, It would be an excellent Datasource integration, that will help not only Appsmith itself but the community of users.
Besides, I've seen this integration already working in another low Code platform, so I don't see why it can't be possible in our beloved Appsmith. Thanks a lot!


Welcome/Intro Copy

Was looking for some sort of intro copy to the site from the start

Intro copy is currently disabled for focus testing.


Datalead AI rebrand

We rebrand Datalead AI is to TheWebCo.

Hello!
Thanks for your contribution.
Looking forward to more contributions from you.
Have a good day!


Passing Cookies onto the ViewController

If i have cookies already available in my cordova app, how can i ensure they are passed onto the SafariViewController?
Currently InAppBrowser seems to do this by default

SafariVC uses the cookies of the system browser..

@EddyVerbruggen  Is there no way to have these passed on?


Break-up Leeds, closing #444

Not tested but hoping this works!

Not tested but hoping this works!

Note: I've kept the entire Leeds area as it may be interesting for people who want an overview of the city and works fine, even in browser (tested yesterday).

Note: I've kept the entire Leeds area as it may be interesting for people who want an overview of the city and works fine, even in browser (tested yesterday).

Thanks for the PR! I made a few adjustments (renaming the polygons mostly) and will push that + upload the data in a followup commit. Then if you do cargo run --bin updater with "leeds" listed in runtime for data/player/data.json, you'll get the new maps.
I had to slightly stretch the southern border of the central polygon, because the boundary managed to just barely clip https://www.openstreetmap.org/way/511767781 in some bizarre way that crashes. It's a bug in the clipping logic that I ought to fix, but not right now. :)

Thanks for the PR! I made a few adjustments (renaming the polygons mostly) and will push that + upload the data in a followup commit. Then if you do cargo run --bin updater with "leeds" listed in runtime for data/player/data.json, you'll get the new maps.
I had to slightly stretch the southern border of the central polygon, because the boundary managed to just barely clip https://www.openstreetmap.org/way/511767781 in some bizarre way that crashes. It's a bug in the clipping logic that I ought to fix, but not right now. :)

Oh yeah, and the generated city overview:

It looks suspiciously like a leopard mid-run.

Oh yeah, and the generated city overview:

It looks suspiciously like a leopard mid-run.


Move XSpec to GitHub

I suggest that XSpec should move from GoogleCode to GitHub before GoogleCode
closes:
http://google-opensource.blogspot.ie/2015/03/farewell-to-google-code.html

There's already two copies of XSpec on GitHub:
https://github.com/search?utf8=%E2%9C%93&q=code.google.com%2Fp%2Fxspec&type=Repo
sitories&ref=searchresults

I suggest that we make an 'XSpec' Organization on GitHub and migrate the code
there.  The low overhead of accepting pull requests on GitHub may also mean
that we get more fixes from current non-committers for some of the outstanding
XSpec issues.

Regards,

Tony.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 6 Jun 2015 at 4:47

Source code, wiki, and issues migrated.

The only link from Google Code that is not redirected is https://code.google.com/p/xspec/adminAdvanced.  A bit harsh, but I guess the point is to force people to change.


Rename pos/rot/loc/scl

Renames pos to positon, rot to rotation, loc to location and scl to scale.
See #11119.

Good idea, but could you merge these commits into one commit? "Clarify button labels" or something similar?

Sure I can squash them, I just felt it was cleaner to have them separated. It's all methods, properties and signals though, no button labels so don't see why you'd want that named "button labels".
Well almost. There's 3 button labels that change. BTW I think we should have icons instead of labels for those, since they're not menus.

Skimming through the diff, your changes are okay. However, it puts files with clang-format errors up for checking so it fails the check. Would be nice to fix those errors too.

@Noshyaar Yeah, my bad, I didn't run clang-format, I just assumed the files would already be compliant. LMK if there's anything else.

I only looked at two of the commits when I suggested the title. If everyone is happy with four commits it's really not a big deal.
LGTM

@hpvb Ah! Yes, scale is just one Button indeed! Thing is, I hadn't discussed nor planned on doing loc, rot or scl, so I wanted it to be front and clear for @Noshyaar to review, and easy for me to drop those commits in case they weren't wanted. I'm totally fine with a squash before merge.

I'd suggest renaming the real method names too, to fix some inconsistencies.
https://github.com/letheed/godot/blob/b8ccb621988b1d7da93b72da3eda5d8d412116be/scene/2d/canvas_item.cpp#L999-L1000
ClassDB::bind_method(D_METHOD("get_local_mouse_position"), &CanvasItem::get_local_mouse_pos);
ClassDB::bind_method(D_METHOD("get_global_mouse_position"), &CanvasItem::get_global_mouse_position);

I did spend a minute thinking at bezier_len, couldn't think of positive. -__-
There's a couple other that I wasn't sure about and didn't touch, and would like your input on: pos_sec and _track_pos_draw.

pos_sec maybe position in seconds. I'd change it to just sec or seconds.
I guess _track_pos_draw draws a current time indicator on a track. I'd suggest _track_bar_draw and rename the Control name to track_bar, or leave it as is.

We discussed the PR in the PR monday.
Could you also rename the corresponding cpp functions when feasible ?

Yeah, I'll see what I can do.

Should be good. Renamed only exposed methods. (+1 variable target_pos that shadowed a method, I left it in the commit.) For reference:

List of functions still using `pos` but not exposed.

cpos
cursor_set_pos
_find_canvas_items_at_pos
_find_control_at_pos
_find_item_at_pos
_find_items_at_pos
_find_next_visible_control_at_pos
get_click_pos
get_constant_pos
get_drop_section_at_pos
get_handle_pos
get_history_pos
_get_mouse_pos
get_name_map_pos
_get_point_from_pos
get_point_view_pos
_get_ray_pos
_get_slot_pos
get_tangent_view_pos
_get_tkpos
get_view_pos
get_word_at_pos
get_world_pos
_gui_find_control_at_pos
_insert_pos
last_pos
mbpos
mouse_to_local_pos
mpos
popup_pos
pos
rpos
seek_pos
set_anim_pos
set_cursor_at_pixel_pos
_set_tkpos
set_window_pos
text_pos
_update_history_pos
video_frames_pos
video_pos
_connpos_update
get_char_pos_for
_get_column_pos_of_word
is_pos_at_end_of_items
make_canvas_pos_local
pos_warped
set_pos_a
set_pos_b

Apart from a couple issues, look good. A rebase to fix merge conflicts + squash the commits would be good, then we can review it a last time and merge.

Renamed _track_pos_draw to _track_position_draw in both the C++ method and the binding, for consistency. Didn't touch the variables since I didn't anywhere else.
Renamed get_drop_section_at_pos since it's exposed now.
Dropped button changes. They'll get icons anyway.
Re-did the class documentations.

Replaced "transform/pos" by "transform/origin" in the Tween.xml example, since I'm guessing those are the member variables. I'd like a confirmation or a correction though.

Can I ask you to rebase a last time to fix the merge conflict, and maybe check that no pos/rot/loc/scl calls were added in the meantime? Then I'll merge it, pinky promise :o)

Should be good. Aside from conflicts, I only had to touch a handful of class doc files.


Feature request: DllPlugin is not compatible with tree shaking

Feature request

What is the expected behavior?
Bundles built using DllPlugin should take advantage of tree shaking: module concatenation (scope hoisting) and dead code removal.
What is motivation or use case for adding/changing the behavior?
Currently ModuleConcatenationPlugin bails out on any optimizations when DllPlugin is being used, because all the modules are being flagged as "used" even if they are not entry points:

ModuleConcatenation bailout: Module is referenced by: DllPlugin

Here's a trivial example:
/** @file src/dep.js */

export function foo() { // this export is never used and should be removed
    console.log('foo');
}

export const bar = 'bar';

/** @file src/index.js */

import {bar} from './dep'; // only `bar` export is being used

console.log(bar);

When webpack runs in production mode the modules are correctly concatenated and the unused export is successfully removed. But when DllPlugin is added to the list, none of the optimizations are taking place.
How should this be implemented in your opinion?
There should be a way to indicate in DllPlugin options which modules (exports) are actually being exposed in the public contract/manifest (i.e. "used"), so that ModuleConcatenationPlugin can do its work. Alternatively there could be a new plugin that would introduce the new semantics and the existing DllPlugin would maintain the existing behavior.
Are you willing to work on this yourself?
maybe

Yep send a PR adding an option to the plugin which only exposes modules mentioned in the entrypoint

Done: #7344

Merged in 8af0320c3ea18cabc4ca62585fc98815f128f09d


Refactor URL builder

Some functionality is implemented. Validate and refactor.

The original URL builder code was not functional anymore and thus removed.
A successor of the URL builder could implement a snapshot feature such that the current state is copied as JSON into the clipboard .
Later on this clipboard entry should be validated and then used to recover the previously copied state.

Continue after refactoring of rendering


Values for market and benchmark other than  CSI300 and SH000300

❓ Questions and Help
I would like to know which values are available right now for "market" and "benchmark" when using qrun. I am trying to test qlib for bitcoin price evolution and also for the French Stock Market. How can I create my own benchmarks?
Johnny

@johnnytorresm Hi,
The "market" is a collection of symbols (a collection of stocks) and the "benchmark" is the benchmark data for this "collection".
"market" is the name of the stock market index (CAC40) and "benchmark" is the code corresponding to the index (FCHI)
"benchmark" is used to calculate the excess return, so the "benchmark" can be chosen according to the specific market; for example, the average value of the "market" can be used as the "benchmark"

Dear Sir,
I appreciate your reply.
best regards,

Johnny Torres
<EMAIL_ADDRESS>Mobile: +33 (0) 6 14 35 45 83
Skype : johnnytorresm
CyberSysNet - True Business Intelligence
<EMAIL_ADDRESS>
From: Pengrong Zhu @.>
Sent: Monday, February 28, 2022 2:12 PM
To: microsoft/qlib @.>
Cc: johnnytorresm @.>; Mention @.>
Subject: Re: [microsoft/qlib] Values for market and benchmark other than CSI300 and SH000300 (Issue #929)
@johnnytorresmhttps://github.com/johnnytorresm Hi,
The "market" is a collection of symbols (a collection of stocks) and the "benchmark" is the benchmark data for this "collection".
"market" is the name of the stock market index (CAC40) and "benchmark" is the code corresponding to the index (FCHI)
"benchmark" is used to calculate the excess return, so the "benchmark" can be chosen according to the specific market; for example, the average value of the "market" can be used as the "benchmark"
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/qlib/issues/929#issuecomment-1054242846, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APJZO2N4M3BMRFLCHWOVKZLU5NYENANCNFSM5PHCRWXA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>


QRCode file fix

Codecov Report

Merging #657 into release-2.3.5 will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             release-2.3.5     #657   +/-   ##
================================================
  Coverage            32.66%   32.66%
  Complexity            1232     1232
================================================
  Files                  170      170
  Lines                14981    14981
  Branches              2371     2371
================================================
  Hits                  4893     4893
  Misses                9363     9363
  Partials               725      725

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e34ad6d...3dfdb5a. Read the comment docs.


Incorrect client defined property resolver should cause failure

If a jasypt.encryptor.property.resolver-bean is specified, but the bean is not found, Spring jasypt falls back to the default property descriptor with an info log (in DefaultLazyPropertyResolver).
I think a failure is a better response, as the bean has been explicitly specified by the client code.

I hear ya, lemme se what I can do...

Great, thank you!

will be in next release


Bug: meta { count } returns too many results when updates were performed

Bug description and how to reproduce
This is best reproduced by a private, non-public dataset. @etiennedi and @michaverhagen have the details on which dataset is best used to reproduce.
In this dataset there are frequent updates due to setting a lot of cross-references. The dataset contains 400 items which should have 0 refs for the specified prop. However, the Aggregate function returns far more than that:

Related
This might be a cascading failure due to #1355

As suspected, this is related to #1355. bc518c3 adds a new integration test which is green with the 1355 fix, but red without it.


pretrain model can not be downloaded

awesome work！！but the pretrain model can not  be downloaded

changed the download procedure, check the README for updated instructions


Add particle property to face the direction of movement

It's weird that there's still no option to make a particle face the direction of movement. You can get an idea of what I'm talking about here http://www.badlogicgames.com/forum/viewtopic.php?f=11&t=20383&p=84813

From that forum thread it looks like you resolved this using the "align" property. Perhaps this issue should be closed then?


Autotag puzzles as lo-pri if their metas get solved

I like this idea a lot. We'll just need to be a little careful on the implementation details since puzzles can have multiple metas & can have several levels of nesting (if my metameta gets solved i should be low pri too even if my meta is still unsolved), and I guess we'll want to un-tag things if meta relationships change (maybe we discover a new meta that this puzzle feeds into) or the meta becomes unsolved (eg someone entered the answer for the wrong puzzle and corrects it).

I like this idea a lot. We'll just need to be a little careful on the implementation details since puzzles can have multiple metas & can have several levels of nesting (if my metameta gets solved i should be low pri too even if my meta is still unsolved), and I guess we'll want to un-tag things if meta relationships change (maybe we discover a new meta that this puzzle feeds into) or the meta becomes unsolved (eg someone entered the answer for the wrong puzzle and corrects it).

Hmm you're right that there are a bunch of edge cases to consider with multiple meta support.
More generically, I think the following invariant must be true: puzzle should be auto-tagged as lo-pri if and only if ALL of its metas have been solved, OR if all of its metametas have been solved, etc.
Any operation that makes that statement newly true should auto-tag. Inversely, any operation that makes that statement newly false should untag.
This could make implementation a bit tricky -- especially when adding new meta relationships or "unsolving" a meta, you'd have to check all the way down the feeder tree to see if things should be untagged.
Alternatively, we could limit the scope of this feature to just a single level (i.e. just check the meta and ignore metametas) and it'd make the implementation way simpler.
Let me know if you disagree.

Hmm you're right that there are a bunch of edge cases to consider with multiple meta support.
More generically, I think the following invariant must be true: puzzle should be auto-tagged as lo-pri if and only if ALL of its metas have been solved, OR if all of its metametas have been solved, etc.
Any operation that makes that statement newly true should auto-tag. Inversely, any operation that makes that statement newly false should untag.
This could make implementation a bit tricky -- especially when adding new meta relationships or "unsolving" a meta, you'd have to check all the way down the feeder tree to see if things should be untagged.
Alternatively, we could limit the scope of this feature to just a single level (i.e. just check the meta and ignore metametas) and it'd make the implementation way simpler.
Let me know if you disagree.

I think it's reasonable to just check a single level (so mark as lo-pri if all of a puzzle's direct metas have been solved). I think the check to decide whether to autotag could be done whenever a meta is marked as solved: For each feeder, check if all of its direct metas are solved, and if so, autotag the feeder as lo-pri.
But if someone then manually deletes the lo-pri tag, I don't think it should automatically be reapplied because we may suspect a puzzle might feed into another meta but we haven't unlocked that meta or aren't sure which meta it is.

I think it's reasonable to just check a single level (so mark as lo-pri if all of a puzzle's direct metas have been solved). I think the check to decide whether to autotag could be done whenever a meta is marked as solved: For each feeder, check if all of its direct metas are solved, and if so, autotag the feeder as lo-pri.
But if someone then manually deletes the lo-pri tag, I don't think it should automatically be reapplied because we may suspect a puzzle might feed into another meta but we haven't unlocked that meta or aren't sure which meta it is.

I think for modeling multiple levels of the relationship it's actually a
straightforward condition: a puzzle should be low pri if all its parents
are either solved or low pri. I'm not sure how that's best computed but it
translates directly to a recursive CTE in SQL I think.
Supporting manually overriding the priority is probably a good idea too.
On Sat, Jan 9, 2021, 13:07 Anthony Hsu<EMAIL_ADDRESS>wrote:

I think it's reasonable to just check a single level (so mark as lo-pri if
all of a puzzle's direct metas have been solved). I think the check to
decide whether to autotag could be done whenever a meta is marked as
solved: For each feeder, check if all of its direct metas are solved, and
if so, autotag the feeder as lo-pri.
But if someone then manually deletes the lo-pri tag, I don't think it
should automatically be reapplied because we may suspect a puzzle might
feed into another meta but we haven't unlocked that meta or aren't sure
which meta it is.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cardinalitypuzzles/smallboard/issues/322#issuecomment-757367203,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2QQNJDP3WMZN5MB3IXSMLSZDAQ7ANCNFSM4V3KZDLA
.

I think for modeling multiple levels of the relationship it's actually a
straightforward condition: a puzzle should be low pri if all its parents
are either solved or low pri. I'm not sure how that's best computed but it
translates directly to a recursive CTE in SQL I think.
Supporting manually overriding the priority is probably a good idea too.
On Sat, Jan 9, 2021, 13:07 Anthony Hsu<EMAIL_ADDRESS>wrote:

I think it's reasonable to just check a single level (so mark as lo-pri if
all of a puzzle's direct metas have been solved). I think the check to
decide whether to autotag could be done whenever a meta is marked as
solved: For each feeder, check if all of its direct metas are solved, and
if so, autotag the feeder as lo-pri.
But if someone then manually deletes the lo-pri tag, I don't think it
should automatically be reapplied because we may suspect a puzzle might
feed into another meta but we haven't unlocked that meta or aren't sure
which meta it is.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cardinalitypuzzles/smallboard/issues/322#issuecomment-757367203,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2QQNJDP3WMZN5MB3IXSMLSZDAQ7ANCNFSM4V3KZDLA
.


Fix incompatibility w/astropy-dev

This change enables different imports.
It was incorrect to use a private function in the first place, but that's
partly on astropy-core for making this code private.
https://github.com/astropy/astropy/pull/10775 solves the issue moving forward.

This solution is not acceptable.  #471 is the right solution.


⚠ Bofrost.at has degraded performance

In 3266361, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1292 ms

Resolved: Bofrost.at performance has improved in ea49a22 after 6 minutes.


Added cuBlas code compilation support

What's the purpose of this change  - to be able have this library target NVIDIA GPUs?  If so, why, given that the existing ROCm hipBLAS implementation can already do this?
Assuming @Kerilk wants this library to target NVIDIA GPUs, can this be implemented to download the cuBLAS header rather than store a replica of it in this repository,  like the library does w/ the ROCm hipblas implementation in order to get the hipblas.h header?

Hi @rothpc
What's the purpose of this change - to be able have this library target NVIDIA GPUs? If so, why, given that the existing ROCm hipBLAS implementation can already do this?

Purpose of this change is to build cuBLAS code as it is for hipblas. But ROCm hipBLAS allows hip code to compile and run on Nvidia/CUDA hence it is not same.
Since CHIP-SPV supports cuda code compilation hence there was an ask if hipBLAS can also support that hence the PR.

I will leave it to you and @Kerilk to take a call where to have the header file.

Since this file is not existing anywhere else, let's have it here for now. In the future, we may want to have a H4I-CuBLAS repo that would depend on this one and provide CMake integration for cuBLAS.


Indexer-Dashboard testing under OpenSearch 2.16.0

Description
We need to ensure our components work under the new version of OpenSearch. The goal of this issue is to test our packages, their lifecycle and the main correct communication of Indexer and Dashboard.
For that, we need to:

[x] (Prerequisite) https://github.com/wazuh/wazuh-indexer/issues/336
[x] (Prerequisite) https://github.com/wazuh/wazuh-dashboard/issues/265
[x] Verify the packages installs
[x] Verify the package upgrades: 4.9.0(1) ⇾ 4.10.0
[ ] Indexer-Dashboard communication works

Tests must be performed following the official documentation under RHEL 9 and Ubuntu 22.04 operating systems, or newer versions if available and supported.
Issues

List here the detected issues

wazuh-indexer
RPM
Package: https://github.com/wazuh/wazuh-indexer/actions/runs/11010695262

[ ] Package installs
[ ] Package upgrades

DEB
Package: https://github.com/wazuh/wazuh-indexer/actions/runs/11011659482

[ ] Package installs
[ ] Package upgrades

Potential issue during wazuh-indexer DEB package upgrade
During the upgrade, I was prompted for which services to restart. There were a lot of services that are not related to the wazuh-indexer service. I chose the default option, which is to restart the services.
Restarting services...
 systemctl restart cron.service haveged.service ifplugd.service irqbalance.service multipathd.service packagekit.service polkit.service rsyslog.service snapd.service ssh.service systemd-journald.service systemd-networkd.service systemd-resolved.service systemd-timesyncd.service systemd-udevd.service udisks2.service
Service restarts being deferred:
 systemctl restart ModemManager.service
 /etc/needrestart/restart.d/dbus.service
 systemctl restart<EMAIL_ADDRESS> systemctl restart networkd-dispatcher.service
 systemctl restart systemd-logind.service
 systemctl restart<EMAIL_ADDRESS>

Potential issue during wazuh-dashboard DEB package upgrade
Looks like the paths to the certificates are wrong.
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]: {"type":"log","@timestamp":"2024-10-04T16:27:00Z","tags":["info","plugins-service"],"pid":4168,"message":"Plugin \"applicationConfig\" is disabled."}
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]: {"type":"log","@timestamp":"2024-10-04T16:27:00Z","tags":["info","plugins-service"],"pid":4168,"message":"Plugin \"cspHandler\" is disabled."}
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]: {"type":"log","@timestamp":"2024-10-04T16:27:00Z","tags":["info","plugins-service"],"pid":4168,"message":"Plugin \"dataSource\" is disabled."}
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]: {"type":"log","@timestamp":"2024-10-04T16:27:00Z","tags":["info","plugins-service"],"pid":4168,"message":"Plugin \"visTypeXy\" is disabled."}
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]: {"type":"log","@timestamp":"2024-10-04T16:27:00Z","tags":["info","plugins-service"],"pid":4168,"message":"Plugin \"workspace\" is disabled."}
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]: {"type":"log","@timestamp":"2024-10-04T16:27:00Z","tags":["fatal","root"],"pid":4168,"message":"Error: ENOENT: no such file or directory, open '/etc/wazuh-dashboard/certs/dashboard-key.pem'\n    at Object.openSync (node:fs:596:3)\n    at readFileSync (node:fs:464:35)\n    at readFile (/usr/share/wazuh-dashboard/src/core/server/http/ssl_config.js:170:31)\n    at new SslConfig (/usr/share/wazuh-dashboard/src/core/server/http/ssl_config.js:130:18)\n    at new HttpConfig (/usr/share/wazuh-dashboard/src/core/server/http/http_config.js:174:16)\n    at MapSubscriber.project (/usr/share/wazuh-dashboard/src/core/server/http/http_service.js:67:177)\n    at MapSubscriber._next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/operators/map.js:49:35)\n    at MapSubscriber.Subscriber.next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Subscriber.js:66:18)\n    at CombineLatestSubscriber.notifyNext (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/observable/combineLatest.js:97:34)\n    at InnerSubscriber._next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/InnerSubscriber.js:28:21)\n    at InnerSubscriber.Subscriber.next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Subscriber.js:66:18)\n    at MapSubscriber._next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/operators/map.js:55:26)\n    at MapSubscriber.Subscriber.next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Subscriber.js:66:18)\n    at DistinctUntilChangedSubscriber._next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/operators/distinctUntilChanged.js:69:30)\n    at DistinctUntilChangedSubscriber.Subscriber.next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Subscriber.js:66:18)\n    at MapSubscriber._next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/operators/map.js:55:26)\n    at MapSubscriber.Subscriber.next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Subscriber.js:66:18)\n    at ReplaySubject._subscribe (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/ReplaySubject.js:80:28)\n    at ReplaySubject.Observable._trySubscribe (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Observable.js:44:25)\n    at ReplaySubject.Subject._trySubscribe (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Subject.js:102:51)\n    at ReplaySubject.Observable.subscribe (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Observable.js:30:22)\n    at MapSubscriber.shareReplayOperation (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/operators/shareReplay.js:53:32) {\n  errno: -2,\n  syscall: 'open',\n  code: 'ENOENT',\n  path: '/etc/wazuh-dashboard/certs/dashboard-key.pem'\n}"}
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]: Error: ENOENT: no such file or directory, open '/etc/wazuh-dashboard/certs/dashboard-key.pem'
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at Object.openSync (node:fs:596:3)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at readFileSync (node:fs:464:35)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at readFile (/usr/share/wazuh-dashboard/src/core/server/http/ssl_config.js:170:31)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at new SslConfig (/usr/share/wazuh-dashboard/src/core/server/http/ssl_config.js:130:18)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at new HttpConfig (/usr/share/wazuh-dashboard/src/core/server/http/http_config.js:174:16)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at MapSubscriber.project (/usr/share/wazuh-dashboard/src/core/server/http/http_service.js:67:177)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at MapSubscriber._next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/operators/map.js:49:35)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at MapSubscriber.Subscriber.next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Subscriber.js:66:18)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at CombineLatestSubscriber.notifyNext (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/observable/combineLatest.js:97:34)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at InnerSubscriber._next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/InnerSubscriber.js:28:21)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at InnerSubscriber.Subscriber.next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Subscriber.js:66:18)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at MapSubscriber._next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/operators/map.js:55:26)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at MapSubscriber.Subscriber.next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Subscriber.js:66:18)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at DistinctUntilChangedSubscriber._next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/operators/distinctUntilChanged.js:69:30)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at DistinctUntilChangedSubscriber.Subscriber.next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Subscriber.js:66:18)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at MapSubscriber._next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/operators/map.js:55:26)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at MapSubscriber.Subscriber.next (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Subscriber.js:66:18)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at ReplaySubject._subscribe (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/ReplaySubject.js:80:28)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at ReplaySubject.Observable._trySubscribe (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Observable.js:44:25)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at ReplaySubject.Subject._trySubscribe (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Subject.js:102:51)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at ReplaySubject.Observable.subscribe (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/Observable.js:30:22)
Oct 04 16:27:00 ubuntu2204.localdomain opensearch-dashboards[4168]:     at MapSubscriber.shareReplayOperation (/usr/share/wazuh-dashboard/node_modules/rxjs/internal/operators/shareReplay.js:53:32)
Oct 04 16:27:00 ubuntu2204.localdomain systemd[1]: wazuh-dashboard.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit wazuh-dashboard.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Oct 04 16:27:00 ubuntu2204.localdomain systemd[1]: wazuh-dashboard.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit wazuh-dashboard.service has entered the 'failed' state with result 'exit-code'.
Oct 04 16:27:00 ubuntu2204.localdomain systemd[1]: wazuh-dashboard.service: Consumed 5.033s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit wazuh-dashboard.service completed and consumed the indicated resources.

LGTM

Potential issue during wazuh-indexer DEB package upgrade
During the upgrade, I was prompted for which services to restart. There were a lot of services that are not related to the wazuh-indexer service. I chose the default option, which is to restart the services.
Restarting services...
 systemctl restart cron.service haveged.service ifplugd.service irqbalance.service multipathd.service packagekit.service polkit.service rsyslog.service snapd.service ssh.service systemd-journald.service systemd-networkd.service systemd-resolved.service systemd-timesyncd.service systemd-udevd.service udisks2.service
Service restarts being deferred:
 systemctl restart ModemManager.service
 /etc/needrestart/restart.d/dbus.service
 systemctl restart<EMAIL_ADDRESS> systemctl restart networkd-dispatcher.service
 systemctl restart systemd-logind.service
 systemctl restart<EMAIL_ADDRESS>

I could replicate this behavior on previous versions too. Looks like it's a common thing in Ubuntu 22.04.


Accounts created via miden-client cannot consume p2id notes

Accounts created via miden-client account new basic-immutable are unable to consume p2id notes created by genesis account.
Steps to reproduce:

Import genesis accounts
Mint assets to the regular account (account-1)
Consume the mint note by regular account (account-1)
Create a new account with miden-client account new (account-2)
Create a p2id note using  miden-client transaction new p2id <account-1> <account-2> <faucet-acc> 50
Sync the client
Consume the p2id note by account-2

The expected result here is a successful transaction and assets moving from the note vault to the account vault. However, I am getting this error when trying to consume the note by account-2
miden-client transaction new consume-note 0x53022a16d1c3b720 0xd26fcc2644850cf86974068973af4f79f8a7a562538f4d88f19e57e078ee9bdc
rpc api error: rpc request failed for submit_proven_transaction: status: InvalidArgument, message: "VerificationFailed(IncorrectAccountInitialHash { tx_initial_account_hash: RpoDigest([12638004671345914736,<PHONE_NUMBER>6625982358,<PHONE_NUMBER>2251791824,<PHONE_NUMBER>7796117166]), store_account_hash: Some(RpoDigest([0, 0, 0, 0])) })", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "content-length": "0", "date": "Fri, 02 Feb 2024 11:21:05 GMT"} }

Hi @daedlock, thanks for raising the issue! This is a known issue with the node that should be fixed soon as @phklive's last comment suggests.

This should be working now - but I'm re-opening until we actually verify this.

I can confirm this works from the client side - but it brings the node into a failure state.
Opened this issue: https://github.com/0xPolygonMiden/miden-node/issues/211 cc @phklive @bobbinth

We have indeed fixed this error.
The error that we are now facing is the opposite:
rpc api error: rpc request failed for submit_proven_transaction: status: InvalidArgument, message: "VerificationFailed(IncorrectAccountInitialHash { tx_initial_account_hash: RpoDigest([0, 0, 0, 0]), store_account_hash: Some(RpoDigest([2194417484513961168,<PHONE_NUMBER>887968501,<PHONE_NUMBER>818268576,<PHONE_NUMBER>5696479504])) })", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "content-length": "0", "date": "Tue, 13 Feb 2024 10:00:16 GMT"} }

It is specific to how we create accounts at genesis. It is now erroring out because genesis accounts are already stored in the store even though they have not interacted with the rollup yet.
We need to update the make_genesis functionality.

Thanks @daedlock, I close this issue, the problem you described has been solved by this PR: https://github.com/0xPolygonMiden/miden-node/pull/200
The new error that is arising has been document here and I am looking into it: https://github.com/0xPolygonMiden/miden-node/issues/223

Thanks!


speed up and improve stable paa

Speed up ~ 30% fitting gmm
Avoid falling in case of all gts have no at least two assigned anchors
Speed up loss calculate in case of no positive anchors

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.d.rybalchenko seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

In my dataset, code works fine, but whet I try to mix ideas from GFL head (when target for cls loss is iou) and PAA sometimes (rarely) gmm.fit falls.
For me I fix this as bellow:
gmm = skm.GaussianMixture(
  2,
  weights_init=weights_init,
  means_init=means_init,
  precisions_init=precisions_init,
  covariance_type='diag',
  reg_covar=1e-5)
try:
  gmm.fit(pos_loss_gmm)
except ValueError:
  precisions_init = [[[1.0]], [[1.0]]]
  gmm = skm.GaussianMixture(
    2,
    weights_init=weights_init,
    means_init=means_init,
    precisions_init=precisions_init)
  gmm.fit(pos_loss_gmm)

Should I include this improvement of stability to the pull request?

The main code seems okay to me. If there are some failed cases when covariance_type='diag', I recommend adding an init argument in PAA head and letting the users determine the covariance type. The advantage and possible risks about difference choices should be described in the docstring then.

@rydenisbak any comments on this suggestion?

@hellock, excuse me, I was in vacation)
I will implement suggestion tomorrow

@hellock, excuse me, I was in vacation)
I will implement the suggestion tomorrow

Hi @rydenisbak, any progress now?

Modifications in this PR hava been merged in #3985


OSS Gadget Releases aren't being published as single files.

Lots of files in the linux release.

https://docs.microsoft.com/en-us/dotnet/core/deploying/single-file
-p:PublishSingleFile=true --self-contained true

Current plan is to remove the Shared library from the release bundle and convert the tools to Single-File. Will be resolved after or alongside #213.

Publishing using the PublishSingleFile property is increasing the total unpacked size of a release by 4.5-5x (from ~100 MB to ~500 MB). I believe this is because the .NET runtime is again being bundled with each project built by the solution. Reconsideration would likely require a revised project structure or build/release strategy.

Makes sense that single file would do that.  Overlooked that when I added that.

Won't fix.


perf: Switch to a cached LINDAS endpoint (PROD)

Closes #1369.

@bprusinowski for some odd reason this endpoint breaks ...  I'll keep you updated on how to proceed

@Rdataflow yup, we won't merge this now – thanks for asking Zazuko, let's see what happens there 👍

FTR: with the new version of trifid on PROD the cached endpoint works like a charm now - we keep monitoring the situation 👀

@Rdataflow the preview is being re-deployed with latest changes from main, should be up in ~5 mins.

@claudiodigallo just give your green light directly to ITX once the situation on your side is ready 👍
cc @sosiology

@CDiGallo thanks for the green light! In that case, we can merge this PR after the release tomorrow, is that okay or is the expectation that this is part of the Release to PROD?
Cc: @Rdataflow @bprusinowski

No, this is only for visualize test

@CDiGallo perfect! We will merge to test.


feature: button with fullwidth option

Feature request
Is your feature request related to a problem? Please describe.

I need the button to fill the width and center label.
Describe the solution you'd like

@phamhieu use the block prop
<Button block>I am full width</Button>

I'll close this for now. just reopen it if it doesn't work

@phamhieu use the block prop
<Button block>I am full width</Button>

I'll close this for now. just reopen it if it doesn't work


compare icon should classify the total compare product added in the comparison page

Bug report
Title
compare icon should classify the total compare product added in the comparison page
Issue Description
compare icon should classify the total compare product added in the comparison page
Preconditions
1. framework Version- master

Steps to reproduce
1. step1- add a product to compare list
2. step2- Now check the compare icon in the header, will not show the no of products added in the list likewise cart.

Expected result

comparison icon should show the total counts

Actual result

Fixed


Can't hook DraggableListener

Hello, i'm using DraggablePanel but can't hook draggablelistener.. was there something wrong with my simple code:
DraggablePanel draggablePanel;
Fragment_Top Frag_Top;
Fragment_Bot Frag_Bot;
@Override
protected void onCreate(Bundle savedInstanceState) {
	super.onCreate(savedInstanceState);
	setContentView(R.layout.activity_main);

	draggablePanel = (DraggablePanel) findViewById(R.id.draggable_panel);
	Frag_Top = new Fragment_Top();
	Frag_Bot = new Fragment_Bot();

	initializeDraggablePanel();

	hookDraggableListener();
}

private void hookDraggableListener() {
	// TODO Auto-generated method stub
	draggablePanel.setDraggableListener(new DraggableListener() {

		@Override
		public void onMinimized() {
			// TODO Auto-generated method stub
			Toast.makeText(MainActivity.this, "Minimized", Toast.LENGTH_SHORT).show();
		}

		@Override
		public void onMaximized() {
			// TODO Auto-generated method stub
			Toast.makeText(MainActivity.this, "Maximized", Toast.LENGTH_SHORT).show();
		}

		@Override
		public void onClosedToRight() {
			// TODO Auto-generated method stub
			Toast.makeText(MainActivity.this, "Closed to Right", Toast.LENGTH_SHORT).show();
		}

		@Override
		public void onClosedToLeft() {
			// TODO Auto-generated method stub
			Toast.makeText(MainActivity.this, "Closed to Left", Toast.LENGTH_SHORT).show();
		}
	});
}

private void initializeDraggablePanel() throws Resources.NotFoundException {
      draggablePanel.setFragmentManager(getSupportFragmentManager());
      draggablePanel.setTopFragment(Frag_Top);
      draggablePanel.setBottomFragment(Frag_Bot);
      draggablePanel.initializeView();
}

Please help me !
Thank you !

Hi @ChunJR
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
draggablePanel = (DraggablePanel) findViewById(R.id.draggable_panel);
Frag_Top = new Fragment_Top();
Frag_Bot = new Fragment_Bot();
//init hookDraggableListener() first.
hookDraggableListener();
initializeDraggablePanel();
}
Change order code like that. it will work.

Thank you @Nguyenduylinh1402  ^^, it's work perfectly !

As @Nguyenduylinh1402 you have to change the order :)


Use Capybara assertions

Related issue: #199
This PR introduces support for the existing Rails DOM assertions one might expect to work out of the box.

This PR introduces support for the existing Rails DOM assertions

This seems like a bit of a misnomer. Rails' assert_select is different than Capybara's assert_selector, and this PR is introducing support for the latter. (I'm not saying using Capybara's assertions is the wrong way to go, though - but it's different than what the PR description claims and what's in https://github.com/github/actionview-component/issues/199#issue-558410314.)

@rmacklin good point.
I ended up using Capybara as I found myself wanting assert_text. I do think it's worth noting that this is mimicking what Rails uses for system tests: https://github.com/rails/rails/blob/786ece692cb71703241a1059e982add5605b67b3/actionpack/lib/action_dispatch/system_test_case.rb#L3
Do you think it's OK to go with the Capybara assertions?

I don't feel to strongly either way, and since most rails app's will probably already have a capybara dependency, it seems okay to make it a dependency of this gem 👍


Eloop termination

New future to terminate eloop:

Add eventfd https://man7.org/linux/man-pages/man2/eventfd.2.html
Add mutex

We can't use eventfd since it's Linux only, and won't be supported on FreeBSD.
If we do add mutex/locks, I'd recommend using standard C threads.h locks, instead of using pthreads (pthreads is supported on both FreeBSD and Linux, but both might have some non-POSIX extensions)


Use 999-SNAPSHOT artifact version for a development

Summary
I'd like to use 999-SNAPSHOT version for a development as it's super annoying to build FW twice (once for development and once for TS development). Quarkus QE TS daily's fails over missing 999-SNAPSHOT https://github.com/quarkus-qe/quarkus-test-suite/actions/runs/12227655427/job/34105123719, I expect this could help, but I didn't look further if it doesn't, I'll find why daily build deploy doesn't work.
Please check the relevant options

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Dependency update
[x] Refactoring
[ ] Release (follows conventions described in the RELEASE.md)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] This change requires a documentation update
[ ] This change requires execution against OCP (use run tests phrase in comment)

Checklist:

[x] Example scenarios has been updated / added
[x] Methods and classes used in PR scenarios are meaningful
[x] Commits are well encapsulated and follow the best practices

LGTM.

Thanks for the review.

But what about next-version in https://github.com/quarkus-qe/quarkus-test-framework/blob/main/.github/project.yml?
.github/workflows/check-release-version.yml checks it, but we do not really need it with main. But nor sure how about it when branch is created. Some sanity checks could be needed.

We still need to release snapshots, so we need to keep track of the current version (although we could infer it from the next version I guess). There can be other consumers of our FW so with Michal we only discussed changing current development version to 999-SNAPSHOT. Feel free to fight back if I am missing something.

Branches could also switch to 999-SNAPSHOT based versioning, e.g. 1.5.999-SNAPSHOT. Wdyt?

Absolutely, I'll follow with it.

hey @rsvoboda can you check today? I can also ask for another review if your schedule is tight today. I'd like to deal with it so that I can check dailys with this change. Thanks

After the struggle with 999-SNAPSHOT release workflow, I don't plan to make same changes in 1.5.z. We can do that later.

Let's gain some experience on the main first before battling on many fronts 😇.


TKK generated

Hey.
Did you manage to figure out how TKK is generated?
var code = res.body.match(/TKK='.*?';/g);
TKK= not found in HTML https://translate.google.com

Where does TKK come from?
Maybe this: tkk:'434303.3040823967'

TKK= not found in HTML https://translate.google.com

Even if the regex is not able to find it, it doesn't actually matter because:
https://github.com/k3rn31p4nic/google-translate-api/blob/411112851b27c6bd5698f6344a65f367e5dbc87a/src/tokenGenerator.js#L92-L93

Where does TKK come from?
Did you manage to figure out how TKK is generated?

TKK is a global variable that's used as a seed by the token generator to generate the token. And as it's a global variable available across the page, either there might be some other script that generates it or it's being generated server side. So, currently, TKK is being scraped from their site.

seems this is being cared in https://github.com/k3rn31p4nic/google-translate-api/pull/10


Update stylx creation process to use Pro 2.0

Background
The stylx creation process has changed since Pro 1.2.
At Pro 2 support was added for

Directly add SVG to styles
Mobile Styles that are supported both in Pro and Runtime

The old process at: https://github.com/Esri/military-features-data/tree/dev/military-symbology-styles/utils-and-source-data/style-creation-utilities
is no longer necessary (in addition to being overly complex and error-prone).
Current State
The currently documented style creation process should be updated to use Pro 2
Steps to Reproduce / Requirement / Workflow
Use Pro 2 to create Mobile Style(stylx) from metadata and SVG icons
Expected Results / Behavior

An Style Creation app to create a Mobile Style (stylx) from metadata and SVG icons
A documented process/updates to repo readme for using the Style Creation App
A  Mobile Style created from the app

Version
The app / stylx will target:
Pro 2.1
Runtime 100.1
Server 10.?

@dfoll @topowright - a quick app to create a new Pro Style from SVGs is now available to test at: https://esri.box.com/s/s042ujvrzrhtx7kufz6o8srxcweibeaq
This App takes as input:

The SVGs provided to us by the symbol committee - available at: https://github.com/Esri/military-features-data/tree/csm/app6d-dev/military-symbology-styles/utils-and-source-data/svg
A CSV file that matches the desired style specification available at:
https://github.com/Esri/military-features-data/tree/csm/app6d-dev/military-symbology-styles/utils-and-source-data/style-source-files/app6d/imagefile_name_category_tags

IMPORTANT: this file must be edited (IMPORTANT2: NOT in Excel, because this changes some of the data) to change the string "{Symbols_Root}" to the local location of the SVGs

@topowright @dfoll
Updated addin app is now available to test at: https://esri.box.com/s/s042ujvrzrhtx7kufz6o8srxcweibeaq
Should look like this now and eliminate the edit-csv step (I crossed out above):

The style creation addin app has been updated to add the step of merging the lines-area-labels style and point style:
This eliminates this step in the old process:  Merge - part of Overall Process

Updated app at: https://esri.box.com/s/s042ujvrzrhtx7kufz6o8srxcweibeaq
I believe the only remaining steps for this task are:

Update the process to set the LabelRules for the Unit frames
Update the current docs/readmes
Test the new process for creating mil2525d / app6d styles

I looked at some different approaches to setting the LabelRules in the stylx (and see if these are exposed in any way in Pro):
That is - this column is the style that is not exposed:

That associates a style item with this table/entry:

And I think the most flexible way to do this until it is exposed by Pro is to keep this as a sql script that gets executed as part of the new process/addin.  Currently working on adding this step to the addin

Added a step to addin to update/add the label rules to the style:

2 icons are failing to import into the style - these 2 should be investigated further and reported to Core as an issue (we may also try to remove the unsupported SVG)
Update the current docs/readmes
Test the new process for creating mil2525d / app6d styles
Test the created style in Runtime+Pro

PE

[ ] Identify labels for each symbol set

I hit a snag on this task L24 when testing the final/resulting style in Runtime/Pro - the final style was not compatible with runtime (i.e. crashed Pro / doesn't draw in Runtime) - I just need make a few changes to ensure each step of the process is working with a mobile style.
Also the 2 bad icons mentioned above were actually repeated unique keys, so this was an input data problem.
I'll update once I have a fully working style and have tested in Runtime/Pro

This task is impeded due to the issue reported in last comment - opened new issue #324 that should be reported to Core. @topowright @ACueva @dfoll

The steps to use the app have been updated in branch: https://github.com/Esri/military-features-data/tree/csm/%23296-update-stylx-creation-process
At:
https://github.com/Esri/military-features-data/tree/csm/%23296-update-stylx-creation-process/military-symbology-styles/utils-and-source-data/style-creation-utilities

Created PR: #335 to address the original issue and some recommended enhancements/feedback this week:

Add Addin source+prebuilt app to the repo
Move documentation on using the app to the wiki ( https://github.com/Esri/military-features-data/wiki/Creating-Dictionary-Renderer-Style-Files )

The only 2 issues I have noticed using this app/process/stylx-created are noted in:

#324 - Runtime 100.3 is not displaying the text from these styles (but Pro 2.2 is so they can be tested)
#334 - A dozen of the SVGs are failing to import at Pro 2.2 - just hit "OK" when you recieve the warning for these on the app (vs. "Cancel" which will abort the app)

This issue was moved to Esri/military-symbology#287


Amend Pay tech docs navigation

Context
The current Pay tech docs navigation has a few characteristics that are not line with content best practice. Specifically:

an "Optional features" section that does not tell users skimming the left hand nav what the section contains
some of the titles are not active and verb-based
the API reference section could be closer to the bottom of the navigation as it is supporting information
the different types of payment (e.g. direct debit, moto) could have their own section

Changes proposed in this pull request

move content from "Optional features" section into new section "Customise your payment pages"
create new section "Take different kinds of payment" with digital wallet, moto, and direct debit payments
make titles more active and verb-based

Guidance to review

check that new navigation makes sense and content is in a logical position
check that amended titles are ok

https://payments-platform.atlassian.net/browse/PP-6721

thanks @sfount for the github help and the approving review - much appreciated!


ocp-dasd.sh fails from time-to-time

There is a very tight time window between when SMAPI has completely finished starting and when the ocp-dasd service tries to run (initiated in ipconf.sh).  The SMAPI test at the start of ocp-dasd.sh is ineffective, in that it doesn't wait long enough after VSMREQIN becomes active before firing commands, and the rest of the API servers seem to not yet be up.
Note that the way ocp-dasd runs is up for change due to deferring the allocation of DASD to closer to cluster deploy-time.  But at least for now we have a race condition.
I did build a systemd service that polls for SMAPI and can be used as a dependency manager -- the expandfs service uses this.  Anything that depends on SMAPI -- especially ocp-dasd, needs to be dependent on this service.

For the A/NZ demos, add a workaround to the setup-demo-system Ansible playbook to run the ocp-dasd service again.

I forgot I had a smcli systemd service that runs a reliable poll-for-SMAPI action, and can be used as a dependency for any service requiring SMAPI.  I updated the demo ocp-dasd service to have a Requires on smapi.service.


Update aks-vmware-system-requirements.md

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

#sign-off


Remove Debug Message when Delivering Timers

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @dhalperi

LGTM, thanks. Will merge once green.


Error: 4: The user must be signed in to make this API call. getSleepSamples()

Hi I encounter this error 'The user must be signed in to make this API call', using the given sample regarding with the sleep method . However, the authResult is {"success":true}, not sure why it says the user is not logged in.  but when I use the other function it returns ok.
`const options = {
scopes: [
Scopes.FITNESS_ACTIVITY_READ,
Scopes.FITNESS_ACTIVITY_WRITE,
Scopes.FITNESS_BODY_READ,
Scopes.FITNESS_BODY_WRITE,
Scopes.FITNESS_SLEEP_READ,
],
}
GoogleFit.authorize(options)
.then(authResult => {
if (authResult.success) {
const opt = {
startDate: '2020-01-01T12:33:18.873Z', // required, timestamp or ISO8601 string
endDate: new Date().toISOString(), // required, timestamp or ISO8601 string
};
  GoogleFit.getSleepSamples(opt).then((res) => {
    console.log(res)
  });
} else {
    console.log(authResult.message);
}

})
.catch(() => {
console.log("AUTH_ERROR");
})`
thanks for updates

@Ransoy  Can you test this merge with only fitness and sleep scope to see if it works?

@aboveyunhai ok  thanks for the updates, will test

@aboveyunhai  thank you for the updates the issue is now fix, it works without the nutrition scope, but I have another concerned, the result of granulity is empty .

but when I tested it to oauth playground i got this result.it display the sleep stages

granulity should be empty as expect because it can be added via addSleep() function which it's not implemented currently. It is just a reserved field for the future,

i see currently the implementation by default the granulity is empty for now.
@aboveyunhai from the example above I'm using Sleep as Android app for data simulation but you can added manually using there rest api.
https://developers.google.com/fit/scenarios/write-sleep-data

@Ransoy  I just successfully implement the saveSleep() function and able to get data from granulity with the current function. It's a little bit weird for me that you can get the start and end date but empty for granulity.

cool can you commit the changes so I can implement on my end.
I using this https://developers.google.com/oauthplayground/ to verify data.
thanks

I was able to read the data from the playground after data sync. So you are probably missing something.

hi @aboveyunhai  I  was able to use the saveSleep() and get Data from granulity,Yeah I probably missed something using there rest api. but I wonder why there is no granulity data using the actual app like Sleep as Android but I was able to read the data from the playround after I sync it from the app.

You need to read google fit doc by yourself, it's just a trivial option even Google does not include that data in its own fit app.
I just included it in case if someone needs it as I rewrote the sleep function.

Hello @aboveyunhai I'm using in my react-native app this library. When I request data from GoogleFit.getDailyStepCountSamples(opt)
.then((res) => {
console.log('Daily steps >>> ', res)
}). In the then part nothing is executed. Basically the promise is not reacting anyway

and also for GoogleFit.getSleepSamples(opt).then((res) => {
console.log(res)
});

Hello @aboveyunhai I'm using in my react-native app this library. When I request data from GoogleFit.getDailyStepCountSamples(opt)
.then((res) => {
console.log('Daily steps >>> ', res)
}). In the then part nothing is executed. Basically the promise is not reacting anyway

@danutz30
Me also facing same issue with below warning.
Possible Unhandled Promise Rejection (id: 2):
Error: 4: The user must be signed in to make this API call.
Error: 4: The user must be signed in to make this API call.
at Object.promiseMethodWrapper [as getSleepSamples] (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:2255:36)
at _callee15$ (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:383003:61)
at tryCatch (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:43186:19)
at Generator.invoke [as _invoke] (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:43359:24)
at Generator.next (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:43229:23)
at tryCatch (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:43186:19)
at invoke (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:43259:22)
at http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:43289:13
at tryCallTwo (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:27071:7)
at doResolve (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:27235:15)

and also for GoogleFit.getSleepSamples(opt).then((res) => {
console.log(res)
});

@danutz30
Me also facing same issue with below warning. Please update here if there any fix, i am stuck at here since 3 days.
Possible Unhandled Promise Rejection (id: 2):
Error: 4: The user must be signed in to make this API call.
Error: 4: The user must be signed in to make this API call.
at Object.promiseMethodWrapper [as getSleepSamples] (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:2255:36)
at _callee15$ (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:383003:61)
at tryCatch (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:43186:19)
at Generator.invoke [as _invoke] (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:43359:24)
at Generator.next (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:43229:23)
at tryCatch (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:43186:19)
at invoke (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:43259:22)
at http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:43289:13
at tryCallTwo (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:27071:7)
at doResolve (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:27235:15)

and also for GoogleFit.getSleepSamples(opt).then((res) => {
console.log(res)
});

@danutz30
I followed the provided documentation and now i am able to retrieve the steps, just posting logs for your reference. refer last object to get steps value.
Daily steps >>>
(3) [{…}, {…}, {…}]
0:
source: "com.google.android.gms:merge_step_deltas"
steps: Array(0)
length: 0
proto: Array(0)
rawSteps: []
proto: Object
1:
source: "com.xiaomi.hm.health"
steps: Array(0)
length: 0
proto: Array(0)
rawSteps: []
proto: Object
2:
source: "com.google.android.gms:estimated_steps"
steps: Array(1)
0: {date: "2020-11-21", value: 66}
length: 1
proto: Array(0)
rawSteps: [{…}]
proto: Object
length: 3
proto: Array(0)

@sudheer-autumn npm package does not include the latest fix for sleep. The temporary fix is to add nutrition scope when you call sleep function, or you can just directly install the package from github.

@aboveyunhai when do you think the sleep part will be fixed with the right scope ?
also I've encountered an issue with infinite loading indicator dialog  when requesting access to fit data in release mode apk
Do you know something about this ?


Bug in skip login option

Summary:
1- Open app without logged in
2- Click on login from navbar
3- Click back button in login activity
4- You will see nav bar as in you are logged in, while you are not.

This is fixed now @nes

Solved.


HDDS-10174. Enable Surefire process checker

What changes were proposed in this pull request?
Ozone build configures 20 minutes fork timeout:
https://github.com/apache/ozone/blob/73e6f90aae4dc22a265361b9a63ccb25a5e6919a/pom.xml#L286
but it's not applied, because the facility to check the fork is disabled by default:

Since 3.0.0-M4 the process checkers are disabled (source)

So instead of killing the fork after 20 minutes, any runaway test is caught only by the Github job timeout, 2.5 hours for integration tests.  The problem is even worse for the flaky-test-check, which gives more time (6 hours) to jobs.
This change enables the process checkers.
However, current version of Surefire doesn't seem to kill the fork after timeout even with process checkers enabled.  Thus we need to downgrade to 3.0.0-M5.
https://issues.apache.org/jira/browse/HDDS-10174
How was this patch tested?
Tested with a simple repro:
package com.example;

import org.junit.jupiter.api.Test;

class ForkTest {
  @Test
  void sleeps() throws Exception {
    Thread.sleep(300_000);
  }
}

and this command, using various versions of Surefire (including latest 3.2.5):
$ mvn -B clean test -Dsurefire.timeout=60 -Dmaven-surefire-plugin.version="${v}"

3.0.0-M6 and newer run for 5 minutes:
12:37:58,056 [INFO] --- maven-surefire-plugin:3.0.0-M6:test (default-test) @ surefire-fork-timeout ---
12:37:58,164 [INFO] Using auto detected provider org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
12:37:58,746 [INFO]
12:37:58,747 [INFO] -------------------------------------------------------
12:37:58,747 [INFO]  T E S T S
12:37:58,747 [INFO] -------------------------------------------------------
12:37:59,084 [INFO] Running com.example.ForkTest
12:42:59,111 [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 300.021 s - in com.example.ForkTest
12:42:59,120 [INFO]
12:42:59,120 [INFO] Results:
12:42:59,120 [INFO]
12:42:59,120 [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
12:42:59,120 [INFO]
12:42:59,122 [INFO] ------------------------------------------------------------------------
12:42:59,122 [INFO] BUILD FAILURE
12:42:59,122 [INFO] ------------------------------------------------------------------------
12:42:59,123 [INFO] Total time:  05:01 min
12:42:59,123 [INFO] Finished at: 2024-01-23T12:42:59+01:00
12:42:59,123 [INFO] ------------------------------------------------------------------------
12:42:59,123 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (default-test) on project surefire-fork-timeout: There was a timeout in the fork -> [Help 1]

3.0.0-M5 and earlier timeout after 1 minute as requested:
12:36:56,575 [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @ surefire-fork-timeout ---
12:36:56,781 [INFO]
12:36:56,781 [INFO] -------------------------------------------------------
12:36:56,781 [INFO]  T E S T S
12:36:56,781 [INFO] -------------------------------------------------------
12:36:57,094 [INFO] Running com.example.ForkTest
12:37:57,146 [INFO]
12:37:57,146 [INFO] Results:
12:37:57,146 [INFO]
12:37:57,147 [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
12:37:57,147 [INFO]
12:37:57,150 [INFO] ------------------------------------------------------------------------
12:37:57,150 [INFO] BUILD FAILURE
12:37:57,150 [INFO] ------------------------------------------------------------------------
12:37:57,151 [INFO] Total time:  01:00 min
12:37:57,151 [INFO] Finished at: 2024-01-23T12:37:57+01:00
12:37:57,151 [INFO] ------------------------------------------------------------------------
12:37:57,152 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) on project surefire-fork-timeout: There was a timeout in the fork -> [Help 1]

CI:
https://github.com/adoroszlai/ozone/actions/runs/7625431710

Thanks @aswinshakil, @hemantk-12 for the review.


Replace Kafka with the newest

Hi,
What do you think of replacing Kafka to the latest (2.12-2.1.0)? Alternative is to put it aside and choose the needed version in the template or from firecamp-service-cli (I personally don't like this approach).

Meaning, I can do that and send you a PR. Just would like to know your opinion

We understand that latest kakfa version 2.1 is available which was committed on 1st feb 19.
We built kafka with firecamp cli on 6th Mar 2019 but still its running with old version. please help.

I'm also facing same issue. We created the new kafka cluster today only but still it's taking old kafka version 1.0. I can see two dockerfile 1.0 and 2.1 for kafka catalog. I feel it's picking still default dockerfile 1.0 to build the new image. Can you please help here? How to upgrade to kafka version 2.x ?

Did you update the firecamp-cli tool?

can you share the latest firecamp cli tool?

just checked - unfortunately, that won't help you. @JuniusLuo has to build docker images and push them to his dockerhub repo. that means the new firecamp release.

When can we expect new firecamp release with updated Kafka version 2.x ?


Question about tax ID generation

Hello! I'm having a little bit of trouble understanding how the tax IDs are generated from taxonomic data in gtdb-taxdump. I don't have any prior experience with hashing, and I'm having a little trouble finding documentation explaining how xxhash works. Could you expand a little bit on the steps for using it to generate tax IDs from taxonomy data? Thank you!

Hi Daniel, xxhash is one of hash functions which converts text (NCBI assembly accession) or byte array (the low-level storage form of text and numbers) to 32-bit or 64-bit unassigned integers, called hashes or hash values. Here we hash the taxon name (in lower case) of each taxon node to uint64 using xxhash and convert it to uint32.
A hash function is stable, which means the same texts always return the same hash values. So in different GTDB versions, the TaxId of a taxon node will keep the same if the name is not changed.
Note that different keys may get the same hash value, this is called a collision. The chance is very low but we detect it and assign a different value in taxonkit create-taxdump.


use custom fetch for uploads

upload was not using custom fetch when it was provided

:tada: This PR is included in version 1.5.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Keyboard short cut for switching between Integrated terminals

Issue Type: Feature Request
Keyboard short cut for switching between Integrated terminals is required
VS Code version: Code 1.53.2 (622cb03f7e070a9670c94bae1a45d78d7181fbd4, 2021-02-11T11:48:04.245Z)
OS version: Windows_NT x64 10.0.19042

set a keybinding for workbench.action.terminal.focusNext also known as Terminal: Focus Next Terminal

for example:
{ "key": "ctrl+shift+j", "command": "workbench.action.terminal.focusNext" }

What if we provide a key binding by default for this?


Improves code quality and add AndroidDatabase tests

This PR gives more code quality and add tests for AndroidDatabase
Please @juanpedromoreno could you review? Thanks

LGTM!


Handle Touch Cancel events on iOS and Android

libGDX currently doesn't handle properly "Touch Cancelled" events generated on touch screen devices (iOS and Android backends affected).
On iOS they are treated as a touch up event which means that, if the user is touching the screen and there is an interruption (such as touching the Lock button or doing the the Home gesture), a touch up will be performed, causing unwanted clicks or unexpected behaviour on resume. On Android we have a bit of a mess and even if the touch up doesn't occur, we have other issues due to how we handle this (see https://github.com/libgdx/libgdx/issues/4866).
There's been a couple of attempts of improving the situation (https://github.com/libgdx/libgdx/pull/6783 and https://github.com/libgdx/libgdx/pull/6353) but they didn't deal with the origin of the issue that is our current inability to handle the CANCEL events.
The proposed solution adds a new touchCancelled method to InputProcessor that is only called by the Android and iOS backends when a CANCEL event is received.
To avoid changing Scene2D behaviour that deals with event cancellations by sending a touch up event with stage coordinates set to Integer.MIN_VALUE, the Stage implementation of touchCancelled calls Stage.cancelTouchFocus () which then generates the custom touch up events as usual.
This solution allows users to handle Touch Cancels on their own InputProcessor implementations, doesn't change Scene2D behaviour and cleans up the hacky onPause() code plus should fix the issues on the Android backend.
I've done some testing but some more is required, that's why I'll set it as draft.

Ran some more tests on iOS and Android and haven't found any issue and behaviour is now the expected. Changing to Ready for review.
@NathanSweet It'd be great if you could have a look.

The scene2d way of handling this is a bit of a hack. A lot of code looks at the distance from touch down to touch up, so it doesn't have to worry whether a touch up is a cancel or a touch up that is very far away. It is convenient not to need extra code for every touch down to handle touch cancel, which is relatively rare. The same could be done for InputProcessor, but it isn't terribly elegant. In some cases when it does matter then you get very strange behavior until you check if it is a cancel.
I'm not sure we want to document that it is limited to iOS and Android. It could make sense to generate a touch cancel on the desktop, even if we don't do it yet. I suppose we could remember to change the comments if we do.
The PR looks good to me. Having an explicit touch cancel event seems good and is probably not much of burden for implementations, which probably use InputAdapter. Transforming it into the scene2d touch cancel is good. Very minor style nitpicks: I tend to add public even for interfaces and I'm not a fan of @Override for library code. I think it's good to merge either way.

Thanks @NathanSweet.
Thanks for pointing out the code style inconsistencies, I've made changes to match the code style on the class. Much worse than the dislike that having public on interface methods or not or having @Override annotations or not may cause is to have some methods with and some without.


TestAccTeamDeleteOnAPIBeforeApply no longer passes

The code now contained in TestAccTeamDeleteOnAPIBeforeApply used to pass reliably.  Now, however, it does not pass.  Why?

Disabling this test caused a decrease in coverage: https://coveralls.io/builds/35531461
The original purpose of this test was indeed to cover handleErrNotFound().  And it used to work.  Again bringing us to the puzzling question: why does it no longer work?

During testing I have uncovered similar bugs when reading a deleted project or a deleted project access token.  Terraform should recognize that the resource has been deleted from the server and re-create it.  Instead, Terraform fails.
Maybe, before recent changes, Rollbar API allowed "deleted" teams to be read if requested by ID, even tho the "deleted" teams were not included in the list of teams?


Server: Add a processing queue

For some requests, we do not need to wait for. We can add a queue with a channel like in peer.go, to process these asynchronously.

Can you please bring some light here? Since I found using peers with channel for connections in dev branch.

Channels can be blocking or non-blocking. For the items that we do not need to wait for, non-blocking, you can use a queuing system to give back control to the caller.

Closing as obsolete, see #283 and #307.


Data set dashboard tables

Proposed Changes

Update dataset tables data and styles

Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests
[x] Build locally
[ ] Code format / lint
[ ] Docs have been reviewed and added

Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Fixes #67
Does this introduce a breaking change?

[ ] Yes
[x] No

Merging!


Rcpp-generated functions should be internal

While looking at this project today, I noticed that these functions are all currently exported in the package namespace:
export(GetRdConsumer)
export(GetRdProducer)
export(KafkaConsume)
export(KafkaProduce)
export(RdSubscribe)

From the example in the README, it seems to me that you want the main interface people use to be the R6 classes KafkaBroker, KafkaConsumer, and KafkaProducer. Given that, I think you should bring all of these functions inside the package namespace to reduce your possible maintenance burden and to be sure people use the main pattern you're encouraging.

great catch! I'm all for consolidating our interface.


RDKDEV-988 - Upstream PlayerInfo dolby audio mode changes

Reason for change: Added missing audio modes for dolby_audiomodechanged event in PlayerInfo plugin.
otherwise 'client.events.1.dolby_audiomodechanged' event will return with unknown for DOLBYDIGITAL and DOLBYDIGITALPLUS audio modes.
Risks: Low
Test Procedure:
TDK PlayerInfo test cases: Check_Dolby_AudioMode_Changed_Event

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

Internal ticket created for tracking https://ccp.sys.comcast.net/browse/RDKCOM-4632

Sprint branch is changed to "sprint/24Q2". So, i am closing this PR to create New one.


Fontawesome classes are purged when using @nuxtjs/tailwindcss

I would love to use Fontawesome 6 with Nuxt and Tailwind. I followed the instructions provided at https://fontawesome.com/v6.0/docs/web/use-with/vue/use-with, but in production the Fontawesome classes still are purged.
I created a repo to reproduce the error.
https://github.com/rw-simon/test-nuxt-tailwind-fontawesome.git
Also tried:

Purging in tailwind.config.js
Purging specific class names rather than regex

Where did I go wrong?
Thanks in advance for any help you can provide 😉
Cheers
Simon
Version
@nuxtjs/tailwindcss: 4.2.0
nuxt: 2.15.7
Reproduction Link
https://github.com/rw-simon/test-nuxt-tailwind-fontawesome.git
Steps to reproduce

Install with npm install
Run npm run dev -> it works fine in dev enviroment
Run npm run build & npm run start -> does not work in production enviroment

What is Expected?
It is expected that the Fontawesome classes (e.x. "fa-lg" or "svg-inline--fa") are not purged, since they are excluded in the nuxt.config.js.
What is actually happening?
All Fontawesome classes are purged.

I'm also experiencing this problem, in my case it happens only after upgrading @nuxtjs/tailwindcss to version 5.0.0, with version 4.2.1 everything was working as expected

This also happened to me when upgrading to 5.0.0 and FA ^3. This feels quite hacky, but I was able to get this working by explicitly importing the font awesome css in my nuxt.config.js. e.g.
// nuxt.config.js
export default {
    // ...

    css: [
        // ...
        '<EMAIL_ADDRESS>    ],

    // ...
}
``

None of the suggested solutions work. Is there any other way?

I'd say this is about configuring the CSS.
Either you can put it in nuxt.options.css and it's not related to Tailwind, and it ships like a normal CSS file.
Or if you do include it with Tailwind, you will need to also configure JIT appropriately.
If an updated replication could be provided, I'll be very happy to help. If a solution has been found by now, please do share here.

Not really a proper solution, but the Nuxt Icon module works like a charm without any problems and provides many more sources for icons beyond Font Awesome

Closing this issue.. but please feel free to report any issues you face related to it 🙂


ELECTRA-base fine tuned on MNLI

Could you please release the ELECTRA-base fine tuned on MNLI or post it on Huggingface's Transformers?

If you want to compute an semantic embedding and use cos. similarity -> maybe you want to have a look at this: https://huggingface.co/T-Systems-onsite/cross-en-de-roberta-sentence-transformer
It is very good for English and German. More languages here: https://github.com/German-NLP-Group/xlsr#models