0153-WebUI-dynamic-resizing

Description
Remove dynamic resizing from the WebUI. This PR is meant to be a starting point for this kind of improvements. Low hanging fruits are e.g. login and logout pages.
Related Issue
See discussion here
Types of changes

[x] Docs change / refactoring / dependency upgrade
[x] New feature (non-breaking change which adds functionality)

Verification Process

[x] Spot checks it in my local dev environment

Release Notes

login.htm and logout.htm now resize without extra javascript function calls
reworked webui.js to move from setStyle function calls over to CSS styles.css

Contributing checklist

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING and LICENSE document.
[x] I fully agree to distribute my changes under Apache 2.0 license.

@ptweety Ok, I have tested your proposed WebUI patch now and to me this looks good so far. The only missing things for the current state of affairs I have commented/reviewed above. Please revise.
In addition, would you like to add your main webui.js modifications here right away? Because it would be great to have these major modifications to improve the dynamic resizing of the WebUI using CSS methods in the same PR.

@jens-maus Sure, I'm still working on the patch and will come up with some more commits soonish.

Ok, patch has been renamed and improved. Please also check the updates made to 0039-patchset.
What I have not replicated from the onResize() function into css  is a check against min-width and min-height of the WebUI. Is this a must or should we leave it?

Ok, patch has been renamed and improved. Please also check the updates made to 0039-patchset.

To me they are looking fine. However, what's with the mentioned removal of cellpadding and cellspacing?

What I have not replicated from the onResize() function into css is a check against min-width and min-height of the WebUI. Is this a must or should we leave it?

Which check do you mean exactly? Please point your finger at it ;)

To me they are looking fine. However, what's with the mentioned removal of cellpadding and cellspacing?

It's included now.

What I have not replicated from the onResize() function into css is a check against min-width and min-height of the WebUI. Is this a must or should we leave it?

Which check do you mean exactly? Please point your finger at it ;)

See here:
  MIN_WIDTH: 750,
  MIN_HEIGHT: 400,

...

  if (width  < this.MIN_WIDTH)  { width  = this.MIN_WIDTH;  bodyOverflow = "auto"; }
  if (height < this.MIN_HEIGHT) { height = this.MIN_HEIGHT; bodyOverflow = "auto"; }

We could set these minimum values also in the css. But I wonder why.

It's included now.

Perhaps! Thanks.

Which check do you mean exactly? Please point your finger at it ;)

See here:
  MIN_WIDTH: 750,
  MIN_HEIGHT: 400,

...

  if (width  < this.MIN_WIDTH)  { width  = this.MIN_WIDTH;  bodyOverflow = "auto"; }
  if (height < this.MIN_HEIGHT) { height = this.MIN_HEIGHT; bodyOverflow = "auto"; }

We could set these minimum values also in the css. But I wonder why.

I dunno. I would say, remove them for the time being and finish your dynamic resizing changes in this PR so that we can test it altogether. My guess is, that the original eQ3 author thought about there have to be a minimum size so that WebUI elements won't start overlapping.

I dunno. I would say, remove them for the time being and finish your dynamic resizing changes in this PR so that we can test it altogether.

This PR should now be done.

I dunno. I would say, remove them for the time being and finish your dynamic resizing changes in this PR so that we can test it altogether.

This PR should now be done.

Ok, I will have a deeper look at it tomorrow. But what about all these FIX: and commented out things in the patch?

@ptweety Ok, I have tested your final PR now and was even able to remove the rest of the onResize() and resize() functions in webui.js so that we show have complete dynamic resizing now. However, have you had a look also at the m_resize() functionality in webui.js? Where no dynamic resizing is still used for some dialogs. Perhaps you can rework this part in webui.js as well.

@ptweety Ok, I have tested your final PR now and was even able to remove the rest of the onResize() and resize() functions in webui.js so that we show have complete dynamic resizing now.

Nice 👍

However, have you had a look also at the m_resize() functionality in webui.js? Where no dynamic resizing is still used for some dialogs. Perhaps you can rework this part in webui.js as well.

Yes, I had a look. There is almost everything hardcoded - all the sizes of the elements in the dialogs (including margin, padding, borders, ...) and then there are some sprinkles of CSS ... I ... looked away.

However, have you had a look also at the m_resize() functionality in webui.js? Where no dynamic resizing is still used for some dialogs. Perhaps you can rework this part in webui.js as well.

Yes, I had a look. There is almost everything hardcoded - all the sizes of the elements in the dialogs (including margin, padding, borders, ...) and then there are some sprinkles of CSS ... I ... looked away.

Ok, would be great to have that replaced by pure CSS as well if possible.

Ok, would be great to have that replaced by pure CSS as well if possible.

It is possible, of course, but it is a huge effort.
Let me give you a simple example by analyzing the MessageBox. To paint this simple component we call the .show() function of this class with some text, a given width and height and some other parameters (which may influence the layout and sizing as well). It consists of:

a UIFrame derived from UIContainer (which is derived from UIComponent)

a UIFrameTitle
a UIFrameContent

a UIText
a UIButton

a UIButtonText

all of which have position: absolute and individually calculated top, left, width and height. The later happens not only in one place. It' spread around all of the different components and obviously also in the constructor (initialize) and other functions of the MessageBox as well.
If we now want to at least get rid of the calculated top and left attributes we can introduce a new function
setPosition into the UIFrame to overload the original function from UIComponent as such:
  setPosition: function() {
    Element.setStyle(this.m_element, {
      //top : parseInt(y) + "px",
      //left: parseInt(x) + "px"
      top      : "50%",
      left     : "50%",
      transform: "translate(-50%, -50%)"
    });
    return this;
  },

That fixes one thing only.
But wait ... the MessageBox is also draggable. Guess what happens when a user grabs the UITitle of this MessageBox? Yes, all of the above was for nothing. We have again dynamically calculated top and left.
BTW: I wonder why the hell are these components draggable in the first place? I don't understand this feature ...
As a helpful reading regarding modal dialogs let me reference this article

Ok, would be great to have that replaced by pure CSS as well if possible.

It is possible, of course, but it is a huge effort.

Ok, I understand. Then I think we are done here as my own tests look quite good here and you at least managed to get rid of this strange manual resizing chain in onResize() which also puzzled me a while ago. Now this looks way cleaner and AFAICS also speeded up resize operations a bit in the WebUI. So I think it is time to merge this on the master and get some feedback from the snapshot testers around here. Thanks again and please continue sending in such great PRs for improving the WebUI even on a level that is not immediately visible to the end user!

It looks good with Chromium based Browsers.
But with Firefox (94.0.2 (64-Bit) ) there are resizing problems on every page except "Einstellungen > Systemsteuerung".
Examples:

@Baxxy13 Please see if adding width: 100% to .Layer0 in the CSS also solves these issues for you?

after adding width: 100% to .Layer0 everything looks correct now

@Baxxy13 : thanks for testing. login.htm and logout.htm also need some fix for Firefox browser

after adding width: 100% to .Layer0 everything looks correct now

Unfortunately I have to use width: -moz-available in .Layer0 instead because otherweise Safari has horizontal resizing issues of large tables, as it seems. @ptweety perhaps you can test all this throughout all major browsers again? would be great.

@jens-maus: I checked with Safari, Chrome and Firefox (no Edge here). Your fix seems to work fine.
However, for login.htm and logout.htm we also need to extend the existing style as follows:
#maintable #content {
  height: 100%;
  width: 100%;
  display: inline-table;
  background-repeat: no-repeat;
  background-position: 480px center;
}

login.htm and logout.htm also need some fix for Firefox browser

i saw that too, therefore i wrote...

on every page except...

login.htm and logout.htm also need some fix for Firefox browser

i saw that too, therefore i wrote...

on every page except...

That was to unspecific ;)

@jens-maus will you make a commit with the style updates for login.htm and logout.htm or shall I create a PR?

Ah, forget it. I was to late to the party (outdated browser window...)

scrolling the WebUI page doesn't seem to work properly either, the right side doesn't fit

scrolling the WebUI page doesn't seem to work properly either, the right side doesn't fit

This seems to be yet-another-firefox only problem as it seems. Neither Chrome nor Safari seem to show this behaviour and the contentLeft can be independently scrolled from the content in contentRight. But perhaps @ptweety has some idea where this comes from or how to fix it for firefox.

Yes, let's start with a small analysis.
The HTML of the WebUI has several sections. One being the #content. Many pages directly inject their data inside this container, hence also rely on the behavior of the same. This includes the scrolling (implemented with overflow: auto.
But in some cases the container is not filled with a simple table that needs to be scrolled, but instead is again divided in subsections like contentLeft or contentRight which need individual scrolling. In this cases #content should not do any scrolling. As a consequence the container may not have any overflow by it's own.
Unfortunately different browsers implement different behavior if it comes to the overflow in such sections. Chrome and others reduce the dimensions, but Firefox expands to the max (height).
Lets go more visual:

You can see the differences in the calculated height in both browsers (top: Chrome, bottom: Firefox)
To fix this we maybe need to rework the affected pages and greatly reduce their complexity of the HTML. In particular the deep nesting of tables inside tables which have again tables inside ... needs to be brought back to one simple layer.

Now, let's compare with a working example (startpage):

Here the HTML is much simpler without deep nesting. You may also find that the structure is build with <div> instead of <table>.

Is there a solution in sight?

Unfortunately different browsers implement different behavior if it comes to the overflow in such sections. Chrome and others reduce the dimensions, but Firefox expands to the max (height).

Isn't there a css statement for firefox to prevent it from explicitly using the #content container for scrolling and just rely on contentLeft and contentRight?

To fix this we maybe need to rework the affected pages and greatly reduce their complexity of the HTML. In particular the deep nesting of tables inside tables which have again tables inside ... needs to be brought back to one simple layer.

I am all for it. However, we have to be careful that this doesn't end up in a complete rewrite of the WebUI which would mean we are completly off to future changes eQ3 might introduce in future versions. And what about our mid-term plan to better push the bootstrap.css integration for a new WebUIv2 development? I really fear we are splitting our resources here by trying to improve the existing WebUI on one hand and trying to get WebUIv2 development going as we already discussed/decided.

Well, I think that the fix is quite simple and does not introduce to much of a change. For devices the idea is something like that:

But to provide a fix, I need some more time (after work).

Hmm, ok. If this would only mean to replace this CLASS03900 table and their contentLeft and contentRight <td> entries with simple <div> statements, I am all for it! So please submit a new PR on it ASAP ;-)

OK, here is started to prepare a PR: https://github.com/jens-maus/RaspberryMatic/compare/master...ptweety:fix-dynamic-resizing
I have not yet build a new image to test it locally, but maybe it already shows off what needs to be fixed.

create a PR out of it and we can work it out that way.


Link to issues which form Roadmap page is wrong

Describe the bug
On the roadmap page (https://www.asyncapi.com/roadmap) at the bottom there's an explanation that the list is linked to GitHub issues in the shape-up repo. The link uses a specific tag of "Key Results", but this no longer exists.
How to Reproduce
Click the link at the bottom of the page of https://www.asyncapi.com/roadmap
Expected behavior
I believe the link just needs to be updated to use the "Outcome" label.
https://github.com/asyncapi/shape-up-process/issues?q=is%3Aopen+is%3Aissue+label%3AOutcome

@derberg Let me know if that is the expected URL and I will make a quick fix PR :)


Update install scripts

Issues:

we currently guess the version of installed components but looking at github repo, but we actually want to get a known repeatable version
we use konveyor repo, we should update to kubev2v repo

Solution:

Set pre defined versions of kubevirt and forklift
Use kubev2v repo

All the scripts are looking nice. For this set, do the version you have set static correlate to a specific openshift version?

no, just took the latest as for this PR

If yes, then maybe a comment in script saying as much. Maybe a few words in README docs about what to tweak if targeting a newer openshift?

@rokkbert hi, what versions will https://github.com/kubev2v/forkliftci use ?
hmm, maybe we can just use the scripts from https://github.com/kubev2v/forkliftci, @sjd78 @rszwajko WDYT ?

Added a Readme file as suggested in https://github.com/konveyor/forklift-console-plugin/pull/40#issuecomment-1248179744
Added a link to HCO versioning file https://github.com/kubevirt/hyperconverged-cluster-operator/blob/main/hack/config and matched the versions used in kubevirt deploy script to HCO versions

@sjd78 @rszwajko please re-review

@sjd78 @mnecas thanks for the reviews :white_flower: , please re-revire


[gstreamer] disable "nvcodec" of "plugins-bad"

Changes
Resolve #34109
nvcodec is enabled since https://github.com/microsoft/vcpkg/pull/30689
Disable it to fix build error...
I found the error while trying to add libonnxruntime support for the port.
Checklist

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Thanks for the fix!


Update dependencies to latest version

I upgraded the dependencies to their latest versions.
I also needed to make some changes for next.js 13.

Thank you for creating this template. Very useful and helpful.
I am having problems for React 18 is not available. I hope this issue will be resolved.

I somehow missed the first notification. I'll see if I can update that to use the modern link component tonight. 👍

I fixed the navbar link and updated the dependencies to be up to date as of today. Did a quick check and everything looks good.

@FTheron Thank you for taking the take to update the PR and your help!


Fix test errors and warnings

I was unable to run the tests:

methods.navigate failed due to the method requiring a DOM event as a second parameter
Many tests showed the duplicate key warning warning which is also visible in the browser console
Nuxt failed with TypeError: Cannot read property 'emit' of undefined due to<EMAIL_ADDRESS>not locking down dependencies and accidentally requiring some non-compatible<EMAIL_ADDRESS>packages

Resolves #31
DCO 1.1 Signed-off-by: Thomas Jaggi<EMAIL_ADDRESS>

@Snugug, since you have been merging the last few PRs: Would you be willing to review this one? Thanks in advance!


Chapter 6 - can't load map

I installed the code for chapter 5-6.  I get the following error:
could not load TileJSON at http://a.tiles.mapbox.com/v4/mapbox.streets.json?access_token=pk.eyJ1IjoibWFya3RoZXRob21hcyIsImEiOiJHa3JyZFFjIn0.MwCj8OA5q4dqdll1s2kMiw util.js:19:12
log
util.js:19:12
_loadTileJSON/<
load_tilejson.js:13:20
r
request.js:28:8
e
corslite.js:46:13

I am also getting this error and unable to display in the map in my application.

I'm also unable to load map to coming back 401 error, tiles and image files
I think, this problem because token.

Changing the development.json and production.json MAPBOX_API_TOKEN setting to our own key does not fix it either.

Changing the development.json and production.json MAPBOX_API_TOKEN setting to our own key does not fix it either.

You said My account personality token right?

Changing the development.json and production.json MAPBOX_API_TOKEN setting to our own key does not fix it either.

I was changed MAPBOX_API_TOKEN but Can't read property mabox is undefined in vendor.js Why?

same problem

Facing the same problem here. The solution is pretty simple:

Create a account in Mapbox (or Sign In)
Go to "Account" (https://account.mapbox.com/) find a part with "Access tokens"

Copy your default public token (or create a new token, and use him)
Go to file development.json (directory: ..../letters-social/config/development.json)
Relace MAPBOX_API_TOKEN with your own (that will help you fix problem that will appear on Listing 6.6. in book [in "generateStaticMapImage" method])

Go to file vendors.js (directory: ..../letters-social/src/shared/vendors.js)
Replace accessToken with your own (that will fix problems that your facing in this issue)

Thats it! :)

@Askiater it's helped, thank you! =)

It's great @Askiater , it solved my problem, once i did not find the 3th place to set my new key in the  vendor js file
your were helpful

@Askiater  Thank u so much :)

It says that Classic styles are no longer supported and linked me to this webpage to change come configuration. In which file should I change the configuration?????

It says that Classic styles are no longer supported and linked me to this webpage to change come configuration. In which file should I change the configuration?????

This is still a problem.

I just followed official mapbox Migrating to the modern Static Tiles API  guide and made few updates in the DisplayMap.js component:

generateStaticMapImage:

    generateStaticMapImage(lat, lng) {
        return `https://api.mapbox.com/styles/v1/mapbox/streets-v11/static/${lat},${lng},12.0,0/600x175?access_token=${process.env.MAPBOX_API_TOKEN}`;
    }

ensureMapExists:

     ensureMapExists() {
        if (this.state.mapLoaded) return;
        this.map = this.L.mapbox.map(this.mapNode);
        this.map.setView(
            [this.state.location.lat, this.state.location.lng],
            12
        );
        this.map.addLayer(
            this.L.mapbox.styleLayer("mapbox://styles/mapbox/streets-v11")
        );
        this.map.scrollWheelZoom.disable();
        this.map.zoomControl.disable();
        this.addMarker(this.state.location.lat, this.state.location.lng);
        this.setState(() => ({ mapLoaded: true }));
    }

It should looks like:


child exited with status 1

Latest update including the update to 0.8.4 makes st crash on start for me with 'child exited with status 1'.
I have reverted to 73c034ba05101e2fc337183af1cdec5bfe318b99,

Do you have git installed? I can't think of what else would cause the issue.
Are you using an AUR helper or manually compiling or what?

The AUR build is bulidng fine with the new version as well for me.

The update runs fine, I even merged it on top of my build(which has very few additional patches).
However, I have another issue: some terminals with neovim open in them "freeze", and I have to close them with Super+q. I don't think it's the additional patches, so it's either some nvim plugin I have (although it's unlikely imo that it would conflict with the st update), or it's an issue for others as well?
It does not seem to happen with terminals without nvim in them.

I think I've run into that issue once or twice in testing. Not sure what the issue is because it hasn't happened too much to test. Probably something with scroll though.

Are you using an AUR helper or manually compiling or what?

I am manually compiling the source in ~/.local/src/st, provided by the LARBS install.

What are the contents of the scroll/ directory inside?
You might want to run git submodule init and git submodule update manually and see if that adds the repo if not their already.

I found the issue. The problem is running 'sudo make install' in the st directory, which installs scroll to /usr/local/bin with permissions 700, id:gid 0:0. This obviously won't execute as user and st silently fails.
I think it would be better to use install(1) with an appropriate permission mode, something like 755 in scroll/Makefile line 14-15.

I think that should do it.
I might just merge these two repositories in the future because I don't see scroll being used aside from st. We'll see.


rename BlockHeight .nullProgress to .nilProgress

rename BlockHeight .nullProgress to .nilProgress
see comment from @adamstener in https://github.com/zcash/ZcashLightClientKit/pull/347

My suggestion would be to factor this out completely and remove it, as having it is a code smell.
If there is no way around having this zero based initializer, the proper name would be .zero.


Android app converts help URL to all lowercase

Summary
In the Android app, Mattermost converts help URLs to all lowercase.
Environment Information

Device Name: Huawei Honor 10
OS Version: Android
Mattermost App Version: 1.32.0
Mattermost Server Version: 5.23.0

Steps to reproduce
Set the help URL in a Mattermost instance to include upper and lower case characters. Visit the URL from android.
Expected behavior
The URL should not be converted to all lower case.
Observed behavior
User is sent to a lowercase version of the URL.

It's probably https://github.com/mattermost/mattermost-mobile/blob/master/app/screens/settings/general/settings.js#L153
const link = config.HelpLink ? config.HelpLink.toLowerCase() : '';

I don't want to argue, just trying to understand why one would expect uppercase URLs?
RFC2396 states that

For example, the host names used in URL are
actually case insensitive, and the URL http://www.XEROX.com
is equivalent to http://www.xerox.com.

(see Page 22, section 6.)

That's for host names / site names. So http://www.xerox.com/MyPage vs. http://www.xerox.com/mypage.

I don't want to argue, just trying to understand why one would expect uppercase URLs?

One example is that URLs with MoinMoin Wiki engine are case-sensitive.
http://moinmo.in/MoinMoinWiki -> ok
vs
http://moinmo.in/moinmoinwiki -> "This page does not exist yet."

@hloeung @nobuto-m thanks to both of you, totally forgot about these cases! makes a lot more sense now :)


Add open in background file buffer

Hi,
First, thanks for making this plugin! It is such a nice lua version of fzf.vim :)
I'm interested in opening selections in "the background", i.e. just adding them to the buffer list but not switching to them. What are your thoughts about adding it to such an action? I didn't add them any default keybindings since if someone wants to use this they can create keybinding in their user config.

I think it’s great, I surely wouldn’t mind adding this, can we make the function name a bit more self explanatory though? Perhaps file_open_in_ background or something similar?

Yes, of course! I've changed it to file_open_in_background.

Merged, ty!

Thank you!


Add curl and jq to Frequency Docker images

As someone using a Frequency Docker image, I want to be able to implement specific heathchecks. To do so using the docker healthcheck system, the tools of curl and jq, while not absolute, are most common and easy to use.
Note this could be done in conjunction with #1390, although this would be good for others to implement stronger or different health checks than the default.

q: @wilwade how much longer do we plan to maintain the instant-seal image now that we have the standalone-node image?

Good question. I've added it to https://github.com/LibertyDSNP/frequency/issues/1799 which should be happening over the next month


build: bump to latest sass version

Updates us to Sass version 1.41.0, because it includes some potentially breaking changes related to calc.

Looks like this reveals an error in MDC. Blocking this for now until it's resolved.

Looks like MDC merged in a fix yesterday. Unblocking.


KAFKA-14869: Ignore unknown record types for coordinators (KIP-915, P…

…art-1) (#13511)
This patch implemented the first part of KIP-915. It updates the group coordinator and the transaction coordinator to ignores unknown record types while loading their respective state from the partitions. This allows downgrades from future versions that will include new record types.
Reviewers: Alexandre Dupriez<EMAIL_ADDRESS>David Jacot<EMAIL_ADDRESS>More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

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

@jeffkbkim This PR has failures related to the change. Could you take a look?
Build / JDK 11 and Scala 2.13 / testLoadGroupsAndOffsetsWillIgnoreUnknownMessage() – kafka.coordinator.group.GroupMetadataManagerTest
<1s
Build / JDK 11 and Scala 2.13 / testLoadGroupsAndOffsetsWillIgnoreUnknownMessage() – kafka.coordinator.group.GroupMetadataManagerTest
<1s
Build / JDK 16 and Scala 2.13 / testLoadGroupsAndOffsetsWillIgnoreUnknownMessage() – kafka.coordinator.group.GroupMetadataManagerTest
<1s
Build / JDK 16 and Scala 2.13 / testLoadGroupsAndOffsetsWillIgnoreUnknownMessage() – kafka.coordinator.group.GroupMetadataManagerTest
<1s
Build / JDK 8 and Scala 2.12 / testLoadGroupsAndOffsetsWillIgnoreUnknownMessage() – kafka.coordinator.group.GroupMetadataManagerTest
<1s
Build / JDK 8 and Scala 2.12 / testLoadGroupsAndOffsetsWillIgnoreUnknownMessage() – kafka.coordinator.group.GroupMetadataManagerTest


Ffm 939

This pull request contains support for cluster identifier for all API calls.

@rushabh-harness Cluster use is now consistent and Android SDK works properly with freemium and non-freemium production accounts.


Rename parameterless From method

As @thomaslevesque notes, Make.A<Thing>().From() reads a little weird.
Alternatives we've been kicking around:

Make.A<Pizza>().Please() (Please was part of @blairconrad's original API, and he's partial to it)
Make.A<Pizza>().WithDefaults()
Make.Any<Pizza>() (but what if it has neither ham nor pineapple?)
Make.ASimple<Pizza>()
Make.A<Pizza>().FromNothing()
Make.A<Pizza>().OutOfTheFormlessVoidThroughSheerForceOfWill()

We could always leave the parameterless From and just add an alternative, of course.

I think my favorite options are .FromNothing() (for consistency with From) and .WithDefaults() (because it best describes what it does). But if you decide to go with .Please(), that's fine too!


Highlight & mark code in web worker

Highlight code & add markers in a web worker. Would likely require using something like worker-dom or undom to do dom manipulations.

Once we use Vite for bundling, check out vite's support for loading files as workers: https://vitejs.dev/guide/assets.html#importing-script-as-a-worker


Filtering tests by name does not work for multiple values

./bin/reframe --system=daint -C config/cscs.py -c cscs-checks/ -n  LAMMPSCPUCheck@1 -l  -n AlltoallvTest@0

The above will result in 0 tests found, while passing each name separately, works fine.

Ah I had also seen this and I thought it was on purpose.. It's because we make one big regex in cli https://github.com/eth-cscs/reframe/blob/master/reframe/frontend/cli.py#L924 but then, if the expression contains the @ we check for exact match here https://github.com/eth-cscs/reframe/blob/master/reframe/frontend/filters.py#L31

I think this is indeed a bug because chaining the -n option should be equivalent of ORing their requirements.


Automatically sign the number of each image (figure)

I have a  Markdown file. It has images like this:
![ Some Title](/img/exmpl.png " Some Title")`
Will be great if Hugo can automatically number images using hugo so that I get output like example on bellow.

Fig1. Some Title

Why not just use CSS Counter, and ::before Selector to add content?
https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Lists_and_Counters/Using_CSS_counters

Why not just use CSS Counter, and ::before Selector to add content?
https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Lists_and_Counters/Using_CSS_counters

excellent! Thanks! I did not know that it was possible.


Feature Charts: Add Longhorn 1.5.5 Chart in 2.7

Longhorn has an upcoming release 1.5.5 so we need to add this new release in the feature charts along with Rancher 2.7. We will probably need to make this OOB.
Add 1.5.5 LH chart in feature chart 2.7 - Cluster Manager/Rancher Marketplace
Cc: @cchien816 @recena @innobead @khushboo-rancher @yangchiu @PhanLe1010 @mantissahz @lucasmlp
Related issue: https://github.com/rancher/rancher/issues/44761

The chart was released on May 1st, 2024.


Inconsistency between ASDF standard and the implementation

(I am working on an ASDF reader in Go)
According to the definition of extension_metadata,
any object of that type must contain two properties:

extension_class
package of type software

However, this is what I get with the following code:
asdf.AsdfFile().write_to("test.asdf")

history:
  extensions:
  - !core/extension_metadata-1.0.0
    extension_class: asdf.extension.BuiltinExtension
    software: {name: asdf, version: 2.4.2}

The property is named "software" instead of "package" and does not contain a tag.

Thanks for noticing this. This certainly needs to be corrected. I'll see if it can't be done in the next couple of weeks.

This has been fixed in master.  The software property has been renamed to "package" (and tagged) in accordance with the standard.


Initial thoughts on features Transpower might like in OpenSCD

Some initial thoughts.

This has served it's purpose. Closing.


.qtz file extension

All quartz composer files in this project are not accounted for https://github.com/ideo/avocado

@ankurp .qtz extension isn't support by Linguist. Please see the requirements and steps to add support for a new language ;)


⚠ Processors has degraded performance

In 48294fc, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 176 ms

Resolved: Processors performance has improved in 7bb8c53.


Collab-cafe-link

:white_check_mark: Checklist

[ ] This pull request has a meaningful title.
[ ] If your changes are not yet ready to merge, you have marked this pull request as a draft pull request.

:ballot_box_with_check: Maintainers' checklist

[ ] This pull request has had the appropriate labels assigned
[ ] This pull request has been added to the SATRE backlog project board
[ ] This pull request has been assigned to one or more maintainers

:arrow_heading_up: Summary

:closed_umbrella: Related issues

:raising_hand: Acknowledging contributors

[ ] All contributors to this pull request are already named in the table of contributors in the README file.
[ ] The following people should be added to the table of contributors in the README file:

thanks @JimMadge 👍. Have reverted the CONTRIBUTING.md change.


[Spectrum Editor] Add ability to import from mobile-spectrum-data package

Ref: https://github.com/davwheat/mobile-spectrum-data/issues/5

Deployed to production
https://github.com/davwheat/mastdatabase.co.uk/commit/6e55d510a2a7f722ac9a4c2316d19ac92a660f0d


Needs documentation for the sdk

There is no documentation whatsoever. The developer wouldn't possibly know how to use it unless he goes checks the source code.

Hello, thank you for reaching out.
Amazon Halo has ability to allow customers to share data with 3Ps (e.g. WeightWatchers). At the moment, this SDK is only for 3Ps that have partnered with Amazon Halo. Once Amazon Halo has decided to partner with a 3P, we will send the 3P documentation on how to use this SDK.
If you or a 3P is interested in partnering with Amazon Halo, please email<EMAIL_ADDRESS>Thank you.


cf push should allow me to set a health-check

On Diego, workers that do not listen on a port need to be run with cf set-health-check APP none
It would be vastly more convenient if the health check could be set on push:
cf push APP --health-check=none --no-routes

/cc @ematpl @jfmyers9

As of v6.13.0, the CLI has the --health-check-type flag, or -u for short:
$ cf help push
<snip />
OPTIONS:
   -i                           Number of instances
   --docker-image, -o           docker-image to be used (e.g. user/docker-image-name)
   --health-check-type, -u      Application health check type (e.g. port or none)

oh hai.  that was easy! :grinning:


Use multiple PublicAPI.Shipped.txt files

A recent update to the PublicAPI allows to merge multiple files into a single data source. Since the majority of the APIs in the SDK are shared, with only a few different due to framework issues, this greatly simplifies API management.

This is blocked by the library not being on NuGet


Code coverage by each file

Request code coverage by each file name , this will help a lot

Request code coverage by each file name , this will help a lot

Do you mean file filter like ExcludeByFile but for inclusion?

Can you show code coverage by file like NPM or yarn does please.

Ah ok now I understand what you mean, coverlet goal is to generate a coverage file is not a coverage report tool for that functionality there are better tool for instance:
ReportGenerator(my choice) https://github.com/danielpalme/ReportGenerator
https://coveralls.io/
https://codecov.io/
and other.


First Android app: Android Basics with Compose

URL of codelab

In which task and step of the codelab can this issue be found?
third，create first android app，second step
Describe the problem
video missing
Steps to reproduce?

Go to...
Click on...
See error...

Versions
Android Studio version:
API version of the emulator:
Additional information
Include screenshots if they would be useful in clarifying the problem.
!

Hi @kokodayo000
Thank you for writing in and bringing this to our attention.
It has been reported to our localization team so it can be addressed.
Hope you are enjoying the course!
Regards.


Changed ordering of parameters to Hasher create.

From what I can tell these parameters are ordered incorrectly the Hasher constructor is invoked.

nice find. thanks!


Quick start needs to be updated

The old Quick Start (https://fybrik.io/v0.1/get-started/quickstart) still shows:
helm repo add m4d-charts https://mesh-for-data.github.io/charts
helm repo update
helm install m4d-crd m4d-charts/m4d-crd -n m4d-system --wait
helm install m4d m4d-charts/m4d -n m4d-system --wait
Maybe this webpage should be dropped...

We are not maintaining old snapshots of the website.

Maybe this webpage should be dropped...

In this specific case due to the rename I think it's a good suggestion. If others agree I think a PR would be appreciated.

hi @elsalant , do you have any updates about the issue?

Probably not relevant anymore


Fix rubocop warnings

Goal
Fix rubocop warnings.
Approach

Bumped rubocop.
Added recommended gems:

rubocop-rake
rubocop-rspec

rubocop -A

Coverage remained the same at 100.0% when pulling a2c4ef3e3377cced9d1e59582dd56b65f500fdf4 on fix-rubocop-warnings into 01c5892b5ad094b82e00b74198af050732f9acdc on master.


pub invocations failing in tech debt and package autoroller shards

The engine roll here https://github.com/flutter/flutter/pull/112895
Included a Dart roll here: https://github.com/flutter/engine/pull/36601
Which included a pub roll https://dart.googlesource.com/sdk.git/+/4f4f446e228a0fb67195aa384c843dc1cf21e0bb
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux technical_debt__cost/8557/overview
I'm not sure that the pub roll is the issue, but I'm going to try to get the Engine -> Framework roller going again by reverting the Dart rolls into the Engine.

The Engine -> Framework roll succeeded after the Dart rolls above were reverted.
cc @sigurdm @a-siva

The failure happens when running flutter update-packages --transitive-closure
This can be fixed by patching https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/commands/update_packages.dart#L412 and moving the temporaryFlutterSdk?.deleteSync call to the finally clause.
flutter update-packages is creating various packages including a simulated Flutter SDK package.  It then deletes the SDK package and runs dart __deprecated_pub deps.
For some reason __deprecated_pub deps is now expecting the SDK package contents to be available.  Not sure what specifically changed in pub and whether it was intentional.

The change in behavior started with https://dart.googlesource.com/pub/+/b0ba5cc63bcc8c93922e3ea0ee9e303c4b279b5e
The .dart_tool/package_config.json file generated by earlier parts of flutter update-packages contains references to the fake SDK package path.  So it seems reasonable that later invocations of pub could assume that the fake SDK directory still exists.