yargs.rebase function is worthless?!

As native path.relative has the same effect.
console.log(path.relative("/this/is/base", "/this/is/base/file"));  // -> file
console.log(yargs.rebase("/this/is/base", "/this/is/base/file"));   // -> ./file

console.log(path.relative("/this/is/base/file", "/this/is/base/")); // -> ..
console.log(yargs.rebase("/this/is/base/file", "/this/is/base"));   // -> ..

If only the difference between file and ./file is not critical...
And even than you can build yargs.rebase on top of path.relative with great simplification.
Moreover, currently .rebase is trailing-slash-sensitive which is generally bad at FS operations.

@ivan-kleshnin I've switched to using path.relative() in:
https://github.com/chevex/yargs/pull/82
See any problems?

No, thanks!


[18279] Check pop-up about population after click to hexagon

Added autotest of population pop-up (population density layer)  for tiny, huge, normal population and population at equator.

Changes is this branch were merged to main in scope of https://github.com/konturio/disaster-ninja-fe/pull/727
It was rebased with this branch


Allow to write "lines" directly, not just Point objects.

Please allow to write lines (strings) (as in the line protocol) directly, not just Point objects.
Especially when some of the data is coming from other systems already respecting the line protocol, it makes no sense to parse it, make Point objects so that the API makes them back strings and sends to the DB.
Thank you.

Hi @aadrian
Im happy to accept PR Requests for that.
You can start adding a new method here:
https://github.com/influxdb/influxdb-java/blob/master/src/main/java/org/influxdb/InfluxDB.java#L134
for example
public void write(final String lineprotocol);
and then add the implementation into:
https://github.com/influxdb/influxdb-java/blob/master/src/main/java/org/influxdb/impl/InfluxDBImpl.java#L171
Also add some Tests to verify your code works correct.
Greetings
Stefan

I question the value of this feature request.
@aadrian or @antjori or @slomek, could you supply a good example of where this functionality is really needed?
I just don't "get" it. In particular,

If you already have a system that creates data in the line protocol, why are you using this library?
Why not send the data directly from that system? OR
If you really need this library for some reason, why not change the existing system to NOT make line protocol strings and defer that responsibility to this library?

This library provides a pretty narrow set of features. It is pretty tightly bound to the influx DB and the features it supports; and currently I think the abstractions in the library are pretty good at doing their job.
Also, by letting the influx-java library do the translation to the line protocol you get an additional benefit: You can pick the version of the influx-java library that implements the same version of the line protocol that your influxDB is using.
As an aside, this request is basically allowing a side-door, effectively an "unsafe" mode. Before it is really considered I would like some thinking in the areas of:

Should this function validate the provided lines?

Yes -> Well then you've just moved the 'need to parse' into the library. Also, do you have to supply the version of the line protocol you are using, so that the library knows how to do the parsing?
No -> Then the library is just a pipe.

Should the lines provided in this way be batched? (if the batching is enabled)

If not, then should they have priority over records that are being batched?
If yes, how should the lines be stored in the batch processor? As strings? Or parsed and stored as Point objects?

I question the value of this feature request.

If I'm pumping millions of data lines very fast (in a few seconds), than the "Point" object creation overhead is just too huge.
Considering that data is coming from different systems, and some already have the data in the required line format, creating "Point" objects just for the OO's sake makes no sense IMHO.
At the moment this is not possible at all with the current API.

Then the library is just a pipe

What is a driver API (like the JDBC one) if not just a "smarter pipe" ?

Ok, I guess this makes sense, but it feels like you have cherry-picked the parts of my enquiry you would like to answer and ignored the rest.
Why not just send your millions of lines of data from the existing system? You must have an implementation of the line protocol in there already (which you are going to have to keep up-to-date with any changes on the InfluxDB end). The API for InfluxDB is pretty basic?
And the questions about validation and batching?

Hi @aadrian can you give some numbers how big the impact on object creation is in you use case.
I ask because especially object creation is a very fast operation in the jdk nowadays.

@majst01 The impact of creating Point objects instead of just writing the lines directly with some Java http api is ~10 bigger.

@aadrian Does that include the HTTP access? i.e. are you using the
public void write(final BatchPoints batchPoints);

interface?

@andrewdodd we are using Batching if the data  comes as batch, otherwise we pump it further right away.

@aadrian, I'm not really sure I completely understand your situation.

You have a system that produces 'write points' in the line protocol format
You send these to another system, which is using the influx-java library to send them to the actual InfluxDB
Sometimes these 'write points' are provided as a batched write, sometimes they are single points; and you use the write(BatchPoints); function or the write(Point); function accordingly
You are experiencing slow writes (I'm guessing this is with the write(Point); function if you get many in a row quickly)

Is this a correct summary?

This might be the root cause of slow writes ! I cant believe that writing a simple line from a Object with StringBuilder is 10times slower than directly writing a String.

I wouldn't be so sure @majst01. Sounds like the HTTP request might be involved here.

But sending the line protocol directly http requests are involved in the same amount.

What I mean is... we have not confirmed that the 10x slow down of "single writes" is really due to parsing/serialising the forwarded points. I believe the major factor in slowness here will be the network, not the parsing/re-serialising of the points.
I think it is highly likely that @aadrian is:

Not using the batch processor
Parsing single writes and then calling write(Point);, which results in 1 HTTP request for 1 Point written
Parsing multiple writes and then calling write(BatchPoints);, which results in 1 HTTP request for N Points written

I believe the slowness is probably due to the ratio of points to HTTP requests. I'm happy to be proven wrong, but I'd like to see a test addressing just this issue (i.e. parse->Point->serialise->write vs string->write) in the context of usual network latencies (i.e. it is probably 10x slower to do the parsing etc, but not in the context of an HTTP call).
@aadrian , if you are still with us:

Is the summary a few comments above correct?
Can you confirm the dot points in this comment are true or false?

Can you answer any of the earlier questions:

Why not send the points directly from the original system OR why not get the forwarding system to do the line protocol encoding instead?
Should there be validation on this 'raw string' write method?
Should this 'raw string' write method bypass the batch processor if it is enabled?

@majst01 If you still find this PR valuable, you can merge it as I fixed the issues you mentioned. If you don't think it's worthy, please close both this PR and issue and call it a day.

I have merged this PR, based on the discussion for some people it seems useful, the implementation does not have any side effects to the existing code.

Sorry I created such a fuss.


light/mqtt: allow inverting scale for brightness level

This is supposed to obsolete pull request 8033 (https://github.com/home-assistant/home-assistant/pull/8033)

Hi @mirko,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Why is there a need for a brightness inverse if there is already a value template that can achieve the same thing?

It felt right to me being specified in the config along with the other device specific brightness options (scale, etc.).
To me it seems I could also somehow achieve other things with templates other config options exist for.
It just looks being the same category and using a template for that kind of kludgy.

The problem with each config option added is that we have to take every permutation of config options into consideration and that's where this addition is getting into ambiguous waters. Should it run before the value template or after ?
Since this is not a common use case and we can use the value template to achieve this, I don't see a need for adding this functionality.


Error: "Only Pro users can... consume content from app workspaces"

The following snippet seems inaccurate in this page: "Only Pro users can publish to and consume content from app workspaces"
Reason: I understand that the new Viewer role in Power BI Workspaces v2 allows non-Pro users to view content in workspaces without a Pro license.  Please confirm and update.  Thanks!

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

ID: f9cf4ce3-f6b1-2c73-d0f9-44573242fb85
Version Independent ID: fc6a52fd-db96-6e9f-f89a-3dea59bff3b7
Content: Power BI licensing in your organization - Power BI
Content Source: powerbi-docs/service-admin-licensing-organization.md
Service: powerbi
Sub-service: powerbi-admin
GitHub Login: @mgblythe
Microsoft Alias: mblythe

Thanks @chrisweis, I'll take a look at this one.

Thanks @chrisweis - updating this sentence to read "Only Pro users can publish content to app workspaces".


"dead area" between radio/checkbox and label with form-check-input

currently this gives an unclickable area between the [x] and label or the (.) and label:
.form-inline .form-check-input {
...
    margin-right: 0.25rem;
...
}

I suggest removing the margin-right and applying a padding-left to the label instead:
.form-inline .form-check-input ~ .form-check-label{
	padding-left: 0.25rem;
}

No plans to change our approach to building on styling our checks—this has been asked of in the past.


No such file or directory   #include <X11/Xlib.h>

# github.com/go-vgo/robotgo
In file included from ./screen/goScreen.h:13:0,
                 from ../../../../go/src/github.com/go-vgo/robotgo/robotgo.go:44:
./screen/screengrab_c.h:11:11: fatal error: X11/Xlib.h: No such file or directory
  #include <X11/Xlib.h>
           ^~~~~~~~~~~~
compilation terminated.

Please make sure to rely on proper installation, see requirements.


Move to Quilt

For now I don't have time to work on Minecraft mods, so this summer I'll update everything to latest.

I'll do this when it's needed because of priorities.

Quilt is still in a state that doesn't satisfy my needs and it's still mostly compatible with Fabric.


When I execute publish_model.py , it prompts "model"_ pickle.UnpicklingError : invalid load key, '_ '. "

Thanks for your error report and we appreciate it a lot.
Checklist

I have searched related issues but cannot get the expected help.
I have read the FAQ documentation but cannot get the expected help.
The bug has not been fixed in the latest version.

Describe the bug
A clear and concise description of what the bug is.
Reproduction

What command or script did you run?

python tools/model_converters/publish_model.py configs/experiment_fpn/experiment_BFP_BLL.py \
data/epoch_12.pth

Did you make any modifications on the code or config? Did you understand what you have modified?
yes，I deleted the IOU balanced sampling module of Libra r-cnn and got the experiment_BFP_BLL.py  .Nothing else has been changed.
What dataset did you use?
COCO

Environment

Please run python mmdet/utils/collect_env.py to collect necessary environment information and paste it here.

TorchVision: 0.7.0
OpenCV: 4.5.1
MMCV: 1.2.7
MMCV Compiler: GCC 7.3
MMCV CUDA Compiler: 10.1
MMDetection: 2.10.0+1253742

You may add addition that may be helpful for locating the problem, such as

How you installed PyTorch [e.g., pip, conda, source]
Other environment variables that may be related (such as $PATH, $LD_LIBRARY_PATH, $PYTHONPATH, etc.)

Error traceback
If applicable, paste the error trackback here.
(base) root@b08d3225ea6e:/mmdetection# python tools/model_converters/publish_model.py configs/experiment_fpn/experiment_BFP_BLL.py data/epoch_12.pth
Traceback (most recent call last):
  File "tools/model_converters/publish_model.py", line 39, in <module>
    main()
  File "tools/model_converters/publish_model.py", line 35, in main
    process_checkpoint(args.in_file, args.out_file)
  File "tools/model_converters/publish_model.py", line 17, in process_checkpoint
    checkpoint = torch.load(in_file, map_location='cpu')
  File "/opt/conda/lib/python3.7/site-packages/torch/serialization.py", line 585, in load
    return _legacy_load(opened_file, map_location, pickle_module, **pickle_load_args)
  File "/opt/conda/lib/python3.7/site-packages/torch/serialization.py", line 755, in _legacy_load
    magic_number = pickle_module.load(f, **pickle_load_args)
_pickle.UnpicklingError: invalid load key, '_'.

Bug fix
If you have already identified the reason, you can provide the information here. If you are willing to create a PR to fix it, please also leave a comment here and that would be much appreciated!

I come across the same problem when I train FCOS. No problem when I train Faster RCNN.

This might because the model is saved and loaded by different version of pickle or pytorch.

I have the same problem using YoloX...
Pickle and pytorch versions are the exact same.
Any ideas?

I have the same problem using YoloX... Pickle and pytorch versions are the exact same. Any ideas?

DId you fix it Jaykob?

Nope :(


BUG: BrainVision reads more events than it says it does.

According to the docstring, the BrainVision reader will only read "Stimulus" events, which are typically in the shape r"(S\d{1,3})", so an S and then 1 to 3 digits. All other events will have to be specified using the event_id dictionary:
https://github.com/mne-tools/mne-python/blob/beda451422b4d8016643438ce7e998c76cbd2f59/mne/io/brainvision/brainvision.py#L233-L239
However, the BrainVision reader parses all events that end with a number, due to this regexp:
https://github.com/mne-tools/mne-python/blob/beda451422b4d8016643438ce7e998c76cbd2f59/mne/io/brainvision/brainvision.py#L325
This leads to issues when e.g., a "Comment" event is in the markers such as Mk9=Comment,Discontinuit? [B] 4156 ms,136544,1,0 as in #5356. See regexp101 to play around with it.
That comment will then be automatically added to the events. Crucially, its trigger value will be the number that was found, in this case 4156. That number originally referred to milliseconds. In this particular case the error is not too bad and will just lead to a nonsensical event value. However imagine that it was 254ms: as BrainVision uses trigger values from 0 to 255, the 254 falls in the range of sensible event values and thus has the potency to be falsely added as a "true event" when it really is just a misread comment.

do you plan to send PR?

Yes, but first we need to discuss how to fix this issue. I could replace the present r'[A-Za-z]*\s*?(\d+)' with r'S(\d{1,3})' to truly match only the S### events as advertised by the docstring. However a lot of our tests are actually working with the buggy behavior. So it would involve fixing a lot of tests as well.
I'd be up for that but perhaps somebody has objections or a better idea.

How about a new kwarg event_parsing='whatever' | 'full' where whatever is some term that accurately describes what we currently do, and full is what you propose to change it to?

@larsoner thanks for the suggestion. However, what we currently do is really not sensible and I would like to change it, I am just looking for the best way to do it.
The arguably most common event in BrainVision files next to stimulus events marked as S### are response events marked as R###. These are also the most common events in our test files. I suggest to replace the current, faulty regexp in our code with [SR]([\s\d]{2}\d{1}), which will match any S### or R###.
Then I would adjust the docstrings to explicitly mention that.
What would remain is fixing the tests, because currently, we have an "optical" event in the test files with the marker 0  1. The tests are tailored such that this event is read by default. But this event has a very idiosyncratic marker which we should not read by default (instead only when specified in event_id)

that's possible to change it if we consider a bug fix.
how does fieldtrip or eeglab or brainstorm handle?
if you tell me if makes mne behaves like them then I can live with the
bug fix option and hard API breakage.

@agramfort
fieldtrip reads

stimuli (S###)
responses (R###)
new segments (we use that only to infer the recording measurement date)
"time" (which I haven't heard of)

https://github.com/fieldtrip/fieldtrip/blob/d11daed366a426184c46bfb024a2cea7e04b1e19/fileio/private/read_brainvision_vmrk.m#L49-L77
... Brainstorm seems to read everything that is a marker by default:
https://github.com/brainstorm-tools/brainstorm3/blob/69bf5c064de3ac9864787d530d361c36546c7369/toolbox/io/in_events_brainamp.m#L32-L96

what do you suggest then?

I suggest we parse S### and R### (stimuli and responses) by default. everything else can be done with event_id

no objection.


[Draft] Disclosure View Component

Disclosure
The disclosure component already exists as part of the public-website and is used to show/hide search filters. It will also be used in the template letters.
The time has come to extract a generic component that allows us to:

provide button titles:

required closed title
optional open title (if not provided, the closed title will be used)

provide content that will appear when the disclosure is open

does your component need to be used by other products or services?

it is currently used by the search filters on the public-website and will be used by template letters

does something similar already exist in the design system

No, but it can reuse the show-hide functionality with additional js (similar to on this page component)

is there a product team that would perform the research, design, development and QA work associate with building this component?

Probably content-platform?

do you have any user stories / scenarios that describe the component?

not currently

Existing components
Code

provide a link to your component working in a dev or prod environment

https://www.citizensadvice.org.uk/s/?q=benefits&filter_by=advice

provide links to the code for this component

https://github.com/citizensadvice/public-website/blob/develop/app/components/disclosure_component.rb
https://github.com/citizensadvice/public-website/blob/develop/app/components/disclosure_component.html.haml

Usability

have you tested the component with the intended user group? Please include any links to research documentation in your proposal

TBC but the styles exist already so assume this is covered.

Accessibility

have you ensured your component meets WCAG 2.X AA guidelines? Include test protocols from external audits or notes from internal tests
have you tested your component with a screen reader?
have you tested your component by using only the keyboard to interact with it?

TBC

Quality

provide links to any appropriate automated tests you have written

unit tests

https://github.com/citizensadvice/public-website/blob/develop/spec/components/disclosure_component_spec.rb

behavioural tests
visual regression tests

this test can be modified to be more general and not search specific: https://github.com/citizensadvice/public-website/blob/develop/testing/visual-regression/scenarios/public-advice.js#L76

@davidsauntson, here are the bits I'm not sure about:

does your component need to be used by other products or services? - not sure if advisernet or intranet will use it?
do you have any user stories / scenarios that describe the component? - I couldn't find anuthing specific in the features folder but wanted to doublecheck
Usability - this one I've just copy pasted from the other component, but will be useful to know if there is a specific place I can check
Accessibility  - the other components I've been working on had reference to this accessibility review, but looking at the search page there, it looks like the component was added after the review so I'm not sure if there are other tests it was covered by

Thanks for this! My thoughts:

@davidsauntson, here are the bits I'm not sure about:

does your component need to be used by other products or services? - not sure if advisernet or intranet will use it?
I don't think either use it at the moment, but it is now in template letters (https://web.develop.content.citizensadvice.org.uk/new-platform/a-template-letter/)

do you have any user stories / scenarios that describe the component? - I couldn't find anuthing specific in the features folder but wanted to doublecheck
No, not yet

Usability - this one I've just copy pasted from the other component, but will be useful to know if there is a specific place I can check
I know @davidrapson saw some testing when the digital workplace team used in in their search page, but the context was pretty different so not how how applicable it would be

Accessibility  - the other components I've been working on had reference to this accessibility review, but looking at the search page there, it looks like the component was added after the review so I'm not sure if there are other tests it was covered by
💯  correct- it was added after the accessibility audits were done

There are some behavioural tests that cover it in the tests in advice_only_search.feature in public website - we'd want to extract these and plop them into the design system probably.

I know @davidrapson saw some testing when the digital workplace team used in in their search page, but the context was pretty different so not how how applicable it would be

Yeah we initially tested using it on equivalent for search filters on the Intranet and in a different context. Our finding there was that it made more sense to show the filters inline so we don't use the disclosure component. Once prompted folks were able to use the toggle fine though so the behaviour was OK, just not a necessary design pattern for our context.

Great, thank you both! I've now updated the issue with the comments/suggestions

Currently Casebook has a very weird disclosure design, which I do not like.
While Casebook doesn't use the design system, I would love there to be a consistent disclosure design across all products and I'd really like to get rid of the current Casebook design.

This is not a good design.  The entire "Benefits Collapse" is actually the button, but only the "Collapse" has been styled as a button.  The result is, a screen reader will read out "Benefits Collapse Expanded"
Also we've been told our arrow is upside down (see the verb / adjective thing below) and confusing on a high zoom.

I have a couple of questions.

These days, could you just use <details> / <summary>? - what about IE11 - they will just always see them fully expanded, which seems a reasonable compromise.
It is possible search engines, or even the browser search tool, will handle indexing of <details> / <summary> better, but I don't have any evidence of this.
Do you want to combine a disclosure with a heading.  The heading needs to go on the outside of the button so you can't use <details> / <summary>.  There are some disclosures on the classic Episerver that use headings.  The JS for these will open the disclosure if the url hash points to them.  Does that need to be considered?  I think it even works for nested disclosures.
The disclosure button is styled as a link.  I thought that was bad as it creates a confusing experience in Dragon where you have to specify if you want to click a button or a link.   ARIA practices has not styled them as a link, but I'm not sure it is clear they are clickable.
Is the + / - set in stone.  gov.uk is now using an arrow, which is more consistent with the native styling.  I think the question comes down to, should the button show the current state of the disclosure (an adjective eg "collapsed"), or what the button will do (a verb eg "expand").  Casebook is using verbs, and this design is using verbs in the form of symbols (+ / -) or in the template letters (+ View / - Hide).  However native uses adjectives (▶ / ▼), and so does aria (aria-expanded).  The tree widgets, eg file manager, on most operating systems also opt for arrows (▶ / ▼).
In the template letter example the label changes when it is expanded or contracted (+ Show template letter / - Hide template letter).  On Casebook, most disclosures are just a static heading (with the weird "Expand" / "Collapse" button thing), but we have a few disclosures that do this as well eg Show past addresses / Hide past addresses.  Possible on Casebook we could get away with just a ▶ Past addresses button, but on the public website I can see a floating ▶ Template letter button would be a little confusing.  Are there two use cases here?  eg, one is a more standard <details> / <summary> without a dynamic label, and the other is call to action button.

gov.uk also has an accordion.  To me an accordion is just a set of disclosures arranged vertically.  The odd thing is they've gone for the verb approach (▲/▼) on that design.  I don't like it.

From what I remember Minnie saying, this filter pattern was chosen for public site search because it makes the filters less prominent. The majority of users won't change the filter from advice content so it didn't make sense to give the filters too much space. I'm assuming this might have been the reason you chose a different approach for the intranet @davidrapson?
I think there's a case for adding this to the design system, but we need to make it clear that this pattern has a specific use case; to hide functionality that most users won't need. It should not be used just to declutter an interface. If you have functionality that a lot of users will need, the options should not be hidden as a lot of users will miss it. (For example the 'This advice applies to' switcher at the top of advice pages now lists all nations as most users missed the drop-down that was there before.)

@mrdaniellewis sorry for the delay in getting back to you! thanks for your comment - some very useful points!

on points 1 - 3 about <details>/<summary> - good shout, I think it's something we can use here. I'll have a further read myself but I can also bring it up with AbilityNet.
The example from the epi server would be using the existing Targeted content component: https://citizensadvice.github.io/design-system/?path=/story/components-targeted-content--default
4 - 5, I will check those with the designers to get their thoughts on this and see if there are potential design changes. I think that Kostas and James don't have github so I'll move the discussion to slack.
6 - I think the button text will be dependant on how the people use the component - i.e it will be easy to define it

From the screenshot of the casebook it looks like it can potentially be closer to the existing targeted content component: https://citizensadvice.github.io/design-system/?path=/story/components-targeted-content--default  (which now that I think about it is quite similar to the disclosure functionality)
Either way, I think the disclosure can be a candidate for our experimental feature and we can share with the team before making it live

@mrdaniellewis You are right about point 4 - it should ideally not use the link styling as it's not a link.
As for point 5 - I definitely see merit in moving to native (and aria) behaviour for accessibility purposes - however that would impact our targeted content component as well so that would have to be reviewed as part of this work. @JamesR-CA What are your views on this?

details / summary fails on a few accessibility points. We deliberately moved away from it for targeted content as details/summary sadly clobbers the semantics of any elements inside it. For example headings would no longer get treated as headings.
I'll see if I can dig out some more context, and I think there's a GDS design system thread about the same thing floating around.

On point 4 - the Details GDS page, research section does show that from their research it isn't necessarily a good option.

Research on this component
There is evidence that some users avoid clicking the link to show more details, as they think it will take them away from the page.
There are concerns that some users of voice assist software will not be able to interact with the component. Some software might require the user to specifically refer to the link to show more details as a button in order to interact with it.
When printing, there is currently no way to force the page to show details hidden inside a details component. This issue has been raised with the W3C.

@anneliwesterberg - worth speaking with the content team on how they are using/plan to use Targeted Content. But yes - it seems that we would need to unpack how these (targeted content and details) would be used and to see how they would provide a intuitive experience for users coming across these components.

@mrdaniellewis - what are you thoughts on the W3C aria practice examples for accordions - which use the up and down arrows. https://w3c.github.io/aria-practices/examples/accordion/accordion.html

@davidrapson  is right about the conscious decision to move away from details/summary for targeted content.  But the use case for that feels very different to me, so I don't have a problem with it having a different implementation.
The way we have used the proposed disclosure so far would not require the text on the summary element to have any semantic meaning (like being a header), so I think it's probably ok to use details/summary.  The current implementation also just accepts a string for the details part - you couldn't actually construct one with anything else at the moment.  Is there mileage in:

using details/summary
continuing to restrict what can be set as the details text to a string
making the accessibility points explicit in the docs

I have contacted Joana from Ability Net, she came back with the following advice:
From an accessibility point of view, there is not a requirement in terms of the symbol used, as long as the symbol is used consistently throughout the site. This relates to Success Criterion 3.2.4: Consistent Identification. Although this Success Criteria is more directed to the label/accessible name provided being consistent, the symbol used for disclosure components communicates the expandable state and, therefore, should be used consistently.
I would say that the chevron icon, in your Casebook example, is the most commonly used symbol to communicate an expandable section. This is commonly used not only for single disclosures, but also for accordions. An example can be found here: WAI-ARIA Practices – Accordion example.
Examples like the one that you shared (ARIA) are commonly used on FAQ pages. In terms of the symbol, the purpose is the same but instead of the down/up chevron approach, it uses chevrons pointing right/down. However, in terms of the position of the symbol, it is usually adapted to what is most convenient. For example, for small buttons the symbol is usually placed to the right of the text but for lengthy links this can be a bit challenging.
Let’s say that it is an FAQ page, where all disclosure titles have different lengths. For design consistency, the symbol is commonly aligned for all FAQs, and this may cause issues if the symbol is aligned on the right. For example, if the symbol is placed too far from the text some users may not be able to understand the visual association between them. The solution for these cases is having all chevrons aligned to the left.
Regarding the “+/-” symbols as a disclosure state indicator, although it is not as common as the chevron, it can also be used. In that case, the example on the template letter page seems to be a bit clearer, as it does not rely on the symbol alone to communicate this. Therefore, if a user is not familiar with the symbol, the text “view/hide” adds this information to the element.
In terms of the text underline, although the underline is commonly used and recommended for links, there are no requirements in terms of styling. In this case, the underline is what represents best that the element is interactive, especially for users who are not familiar with the symbols, as the button does not contain an outline.

To summarise the discussion points and suggested approach:

The design of the component will keep the current styles based on the discussion with AbilityNet
For now the component will still use <button> the reasons for moving away from <details>/<summary> are:

accessibility concerns - as outlined in GDS docs for details - voice assist software, printing
browser support - it is not being fully supported in IE11 (though it will still display the component's open state)
we will still need JS to change the text on click

Please let me know if there are any concerns, ideas or questions.


Blazing Battle not loading

Screen Recording:
https://user-images.githubusercontent.com/79750252/126849842-bd01ae97-d280-475c-bd49-16c4fbf50c77.mp4

This should be fixed, but let me know if it's still happening, along with any JS errors you see.


Why not use x ranges for c3 dependency?

I find it strange that c3 currently requires d3<=3.5.0. Why should new patch versions like 3.5.1 not work? For me it would make more sense to specify the version in package.json as <=3.5.x. This would make it easier to adopt certain fixes without waiting for a new c3 version. I use JSPM for dependency management.

Better clarification on why anything < 3.5.0 doesn't work would be very helpful. Some of the fixes in 3.5.x releases would be useful.
Is there an API change after 3.5.0? There doesn't seem to be any documentation (which i can find) which states that.

Is this issue still relevant?

No, that's fine now, thanks.


Distcp ng handle directory structure copy

also set the owner of the hive table as the flow executor

@ibuenros , @chavdar , please review it when you have time

Coverage decreased (-0.09%) to 45.091% when pulling c9d411ec310e668d42e12dbf7215af3ce3894c60 on tuGithub:distcp-ng into 9971e736a6eb3328e2375875ad362c87ff574678 on linkedin:master.

@ibuenros , updated the PR with comments

Coverage decreased (-0.2%) to 44.977% when pulling<PHONE_NUMBER>2d156a3a91c408ba28d45aac0fca6a on tuGithub:distcp-ng into 9971e736a6eb3328e2375875ad362c87ff574678 on linkedin:master.

LGTM

Coverage decreased (-0.03%) to 45.003% when pulling 17d751f62ef5b4b08a7bdab6b95870d99216c1cf on tuGithub:distcp-ng into 9abe19ab3507d3612aaf149d692f431f8b19b80c on linkedin:master.


Terminal stuck at smaller width

Does this issue occur when all extensions are disabled?: Yes/No

Version: 1.73.0-insider (Universal)
Commit: 7ea2788a43a4c35d8da63a419725ba2485de395b
Date: 2022-10-19T05:33:31.548Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 21.4.0
Sandboxed: Yes
I had my VS Code window at a smaller size and then I fullscreened the window but the terminal width didn't change. I don't have any changes in my bash profile that changes the appearance of the terminal (when I had Oh My Posh I noticed this would happen often). Usually if I reload the window it fixes this issue in the past but reloading does nothing now.

Not an issue after update


Fixed button visibility in development.html

Related Issue
Issue no #63
Description
I have fixed the issue where the button was not visible in some pages
Screenshots

Hello, please check my PR @dakshsinghrathore


sudo causes powershell error when running wsl 2

What I did to install this distro:

Removed all microsoft store distros. At this point wsl -l shows no distros.
Downloaded Ubuntu 20.04 from the tianon source.
.\LxRunOffline.exe i -n UF -d D:\WSL\UbuntuFocal -f .\focal.tar.gz -s
wsl --set-version UF 2
Run wsl and find that I'm running bash as root.
Add a user in wsl.
.\LxRunOffline.exe set-uid -n UF -v 1000

At this point, I run wsl and attempt to install wget:
finster@finster-pc:~$ sudo apt-get update
apt-get : The term 'apt-get' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ apt-get update
+ ~~~~~~~
    + CategoryInfo          : ObjectNotFound: (apt-get:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

finster@finster-pc:~$ apt-get update
Reading package lists... Done
E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
E: Unable to lock directory /var/lib/apt/lists/
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)
W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied)

As you can see, running apt-get under sudo causes a powershell error to pop up. Running without sudo uses the apt-get within the distro.
Another example:
finster@finster-pc:~$ which apt-get
/usr/bin/apt-get
finster@finster-pc:~$ sudo which apt-get
which : The term 'which' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling
of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ which apt-get
+ ~~~~~
    + CategoryInfo          : ObjectNotFound: (which:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

I should note that running any of these commands as root wsl -u root work as expected, i.e. apt-get update performs the update as expected. This is a super weird issue, and admittedly, I don't know enough about how the underlying wsl 2 system works to be able to figure this out.

Could you please check if you have anything named sudo or sudo.exe in your Windows PATH?

holy cats, Yeah that's the problem. I feel like a doof. Thanks.


647 pg conversion unit test

Pull Request submission
Added a new test case, test_pg_to_pg_mapper_with_many_to_one, to specifically examine how the function handles scenarios where multiple input values map to a single output value. This test ensures the function works correctly in these cases.
The test_pg_to_pg_mapper_success function in this pull request verifies the core functionality of the pg_to_pg_mapper function, ensuring it correctly maps input values from one product group system to another based on a provided mapping table. Uses the pd.testing.assert_frame_equal function to compare the actual output DataFrame (returned by pg_to_pg_mapper) with the expected output DataFrame. This ensures all rows and columns, including data types, match exactly.
Note: On line 141 I use  index=result_df.index in the dataframe constructor to make the test pass. Please fail this if you think it is not acceptable.
Closes or fixes

Detail the ticket(s) you are closing with this PR
Closes RDRP-647

Code

[ ] Code runs The code runs on my machine and/or CDSW
[ ] Conflicts resolved There are no conflicts (I have performed a rebase if necessary)
[ ] Requirements My/our code functions according to the requirements of the ticket
[ ] Dependencies I have updated the environment yaml so it includes any new libraries I have used
[ ] Configuration file updated any high level parameters that the user may interact with have been put into the config file (and imported to the script)
[ ] Clean Code

[ ] Code is as PEP 8 compliant as I can humanly make it
[ ] Code passess flake8 linting check
[ ] Code adheres to DRY

[ ] Type hints All new functions have type hints

Documentation
Any new code includes all the following forms of documentation:

[ ] Function Documentation Docstrings within the function(s')/methods have been created

[ ] Includes Args and returns for all major functions
[ ] The docstring details data types

[ ] Updated Documentation: User and/or developer working doc has been updated

Data

[ ] All data needed to run this script is available in Dev/Test
[ ] All data is excluded from this pull request
[ ] Secrets checker pre-commit passes

Testing

[ ] Unit tests Unit tests have been created and are passing or a new ticket to create tests has been created

Peer Review Section

[ ] All requirements install from (updated) environment.yaml
[ ] Documentation has been created and is clear - check the working document
[ ] Doctrings (Google format) have been created and accurately describe the function's functionality
[ ] Unit tests pass, or if not present a new ticket to create tests has been created
[ ] Code runs The code runs on reviewer's machine and/or CDSW

Final approval (post-review)
The author has responded to my review and made changes to my satisfaction.

[ ] I recommend merging this request.

Review comments
Insert detailed comments here!
These might include, but not exclusively:

bugs that need fixing (does it work as expected? and does it work with other code
that it is likely to interact with?)
alternative methods (could it be written more efficiently or with more clarity?)
documentation improvements (does the documentation reflect how the code actually works?)
additional tests that should be implemented (do the tests effectively assure that it
works correctly?)
code style improvements (could the code be written more clearly?)
Do the changes represent a change in functionality so the version number should increase? Start a discussion if so.
As a review you can generates the same outputs from running the code

Your suggestions should be tailored to the code that you are reviewing.
Be critical and clear, but not mean. Ask questions and set actions.

@AnneONS I think I have corrected all the problems you raised.


JDBetteridge/update build system

Amazing ! The only thing missing is my release.yml file ? Also big thank you to @stefanozampini for giving us a fix !


[issue/690] allow . and - in environment variable names.

Files touched:  schema/types/environment.go, schema/types/environment_test.go
Allow additional characters in the set considered valid in environment variable names.  Prompted by
https://github.com/appc/docker2aci/issues/244 and https://github.com/rkt/rkt/issues/3532.

@lucab PTAL, taking you up on your offer:  https://github.com/rkt/rkt/issues/3532#issuecomment-279013222

The IEEE spec from which the original conservative character set is taken, as a reference:
http://pubs.opengroup.org/onlinepubs/9699919799/

@ae6rt thanks for the PR, can you please also update SPEC.md for the new characters?

I updated spec/aci.md, and rebased.  I wanted to honor the desire to adhere to the IEEE spec, so I left the word 'solely' in, with a qualifying clause about the practical desire to allow . and -.   I hope it doesn't read strangely.

Ping @lucab knowing you are busy, but I don't want to forget about this.

LGTM, but I don't have merge powers here.


Clean leftover images

This patch temporarily handles the cleanup of any leftover images from tempest until tempest clean-up is implemented

/approve


Ignore no_cache setting for "load" command

What changes are proposed in this pull request?
Ignore no_cache setting for "load" command.
Why are the changes needed?
Currently the "load" command behaviours strangely if the corresponding node/client has the setting
alluxio.user.file.readtype.default=NO_CACHE

It reports "loaded" every time repeatedly
$ ./bin/alluxio fs load /test/file.01
/test/file.01 loaded

$ ./bin/alluxio fs load /test/file.01
/test/file.01 loaded

After applying this PR, the behaviour changes to
$ ./bin/alluxio fs load /test/file.01
/test/file.01 loaded

$ ./bin/alluxio fs load /test/file.01
/test/file.01 already in Alluxio fully

Does this PR introduce any user facing changes?
No

@jja725 PTAL, thanks

alluxio-bot, merge this please


[SPARK-42643][CONNECT][PYTHON] Register Java (aggregate) user-defined functions

What changes were proposed in this pull request?
Implement spark.udf.registerJavaFunction and spark.udf.registerJavaUDAF.
A new proto JavaUDF is introduced.
Why are the changes needed?
Parity with vanilla PySpark.
Does this PR introduce any user-facing change?
Yes. spark.udf.registerJavaFunction and spark.udf.registerJavaUDAF are supported now.
How was this patch tested?
Parity unit tests.

CC @zhengruifeng @HyukjinKwon @ueshin @hvanhovell

After double thoughts, I add spark.udf.registerJavaUDAF's implementation into this PR, since both APIs rely on the same proto message JavaUDF.

WDYT @hvanhovell ?

Merged to master and branch-3.4, thanks all!


genome overview: collection date not displayed properly

https://www.patricbrc.org/view/Genome/573.15432
The collection date looks fine in the solr, however not displayed correctly on the genome overview page.

The dates are expected to be of form MM/DD/YYYY (or MM-DD-YYYY, etc).  I'm guessing this one is DD/MM/YYYY ?   Some conversion may be needed before import?
The date picker on the genome editor saves the collection_date as a full datetime in solr, by the way.  I.e., 2017-12-14T06:00:00.000Z

this was fixed by displaying whatever is given for collection_date (unless in ISO format)


Is LocalNetworkGateway one type of Virtual Network Gateway?

It is a little bit confusing. This article is talking about Virtual network gateway configuration. It mentions ps New-AzureRmVirtualNetworkGateway to create virtual network gateway, but the last section pops up for Local Network Gateway which uses different ps cmdlet "New-AzureRmLocalNetworkGateway". I think Virtual network gateway is different from local network gateway, then why they are put in same article. Btw, I am also very interested in Local Network Gateway. I hope there could be a more detailed article just about Local Network Gateway (the description about Local network gateway in this article is way too simple).
Thanks,
martin

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

ID: e0377d24-bad6-0d7e-e5b1-0343d225d835
Version Independent ID: 163949a6-584f-9c7c-815f-ad69f09f83dd
Content: VPN gateway settings for cross-premises Azure connections
Content Source: articles/vpn-gateway/vpn-gateway-about-vpn-gateway-settings.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@cppcraze Thanks for the feedback! We are currently investigating and will update you shortly.

I've updated the headings on the article a little bit to make this more clear. Thanks for the feedback! #please-close


ExcludedTypes example?

I was looking for an example on how to use ExcludedTypes property on AdaptiveSamplingTelemetryProcessor available from 2.2 Beta1 and couldn't find any. Can you share an example and even better, update the release entry for https://github.com/Microsoft/ApplicationInsights-dotnet/releases/tag/v2.2.0-beta1 with an example on how to use ExcludedTypes property. Thanks!

I updated release notes and added xml documentation to excludedTypes.


WCT + Typescript

How could I configure WCT to work with typescript? The tester responds with a 'WCT searched for .js and .html files matching: test/' of which I could see .js is hardcoded in the error message..
If .ts test files is possible could you please share the config? Thank you

I'd second that,
I have introduced typescript into my project, only one file at this time, but WCT stopped functioning. I have a couple of ideas to solve the issue:

test the build code rather than files -> defeats the purpose of unit testing
precompile TS files to JS -> adds some noise, but doable

What I wanted to know is if there was a way to set this up in the wct.conf file, so that this problem would be abstracted away?
Thanks

@lemoustachiste 's second suggestion to precompile TS to JS is a good solution, and what I usually do. It's easy to set up and in my experience doesn't add noise in a way that is disruptive.
Also note that WCT is not in development anymore. I highly recommend starting to migrate to something like Karma. The open-wc docs at https://open-wc.org/testing/testing-karma.html are a good starting point.


Char behavior doesn't match reference docs

The reference docs are very clear that chars are signed and permit arithmetic:
https://docs.particle.io/reference/firmware/photon/#data-types
But when using the local Particle IDE and the cloud compiler, they appear to be unsigned.
Suggest update compiler commands (if possible on platform)  to reflect docs.
( Or change docs to note limitations )
More details here:
https://community.particle.io/t/chars-not-behaving-as-expected-unsigned-in-particle-dev-tool-cloud-compiler/26439
I took a bit of a stab at which repo to raise this against, sorry if I missed.

Thanks for raising this! The correct repo should be one with documentation. I'm going to close this issue but could you open it in the correct repo?


Upgrade to React Native 0.57

Based on RN 0.56 PR
Make sure to update to latest Android JDK.

@gnprice This PR is ready.

FYI: Just removed the WIP from the name of the PR.

OK. Let's focus on getting the 0.56 upgrade completely in (so #2789, and I think that means #2994 first), before turning much attention to this again -- that will help some other ongoing work, and it'll also reduce the amount of stuff for us to keep track of in this PR.

The commits here are also ready to be reviewed.
I only thing that is not working OK is the SpinningProgress component that uses the ART library from the core react-native has issues rendering on Android. Confirmed with @jainkuniya that it does not work on his machine on a pristine 0.57 project too.
I will either figure out a fix, or replace the visual with something not using the ART lib.

All unmerged commits from here were appended to the 0.56 PR. Closing this one.


Disable TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA cipher

Currently not possible with DO load balancer. See https://www.digitalocean.com/community/questions/configure-load-balancer-cipher-suites?comment=193664
Will request feature

Feature requested with Digital Ocean


'import' syntax compatible and TypeScript declaration file

Added compatibility with import syntax to jsthemis
TypeScript declaration file
Increased the version of package.json
Updated CHANGELOG.md

Checklist

[x] Change is covered by automated tests
[x] Changelog is updated (in case of notable or breaking changes)

Should we add tests for this file?

And I see, that you tried to add examples and update tests on CI but reverted changes. Did you met any problems with tests with new import syntax?

Nope, I met the issues with node >= 18. Decided to provide it later because of OpenSSL 3 issues.

Nope, I met the issues with node >= 18. Decided to provide it later because of OpenSSL 3 issues.

can we test it for openssl1.0/node <= 18?


[FLINK-31993][runtime] Initialize and pass down FailureEnrichers

https://issues.apache.org/jira/browse/FLINK-31993

Init FailureEnrichers as part of ClusterEntrypoint (to avoid performing the same task per JM initialization)

The set of Enrichers is then passed down to JM and Scheduler implementations as needed.

LGTM overall, minus a few cosmetic comments. I think the commit message is also misleading
Fail fast on bad FailureEnricher JM startup as given by the user

since we still have filterInvalidEnrichers in the codepath

Awesome! Thanks @dmvk ! Updated


Securely forget the signing key

https://github.com/input-output-hk/cardano-base/pull/140/ added forgetSignKeyKES, which we should now call in evolve.

Plan:

stateful API to the key
should be localized to individual ledgers
block production should have that stateful key object in its closure
(protocolInfo in .Cardano becomes monadic)
which means checkIsLeader needs access to it too
(i.e., BlockProduction needs a leader check function, that will then
call to the pure one in the class with the info -- see 7)
at the moment, we construct BlockProduction object (stateful) from
ConsensusProtocol/CanForge
Instead, require BlockProduction object as part of ProtocolInfo
(sensible: if you are a leader, give a BlockProduction)
[can this fix Thomas's problem? -- yes]
-- CanForge as a class goes.
The (abstract) protocol checkIsLeader takes a ChainIndepStateInfo (name?);
it will be the responsibility of the BlockProduction object to call it
-- stick with the name ChainIndepState? (state derived from the private key
is still state)
No more ForgeState/updateChainIndepState
Stateful KES wrapper offers 'sign' but no 'getPrivateKey'

OptNP BlockProduction xs -> BLockProduction (HardForkBlock)

data KESAPI m = KESAPI {
      evolve  :: Period .. -> m ()
    , getInfo :: KESInfo
    , sign    :: .. -> m Signature -- Signature in NF!
    }

newKESAPI :: m (KESAPI m)

type instance ChainIndepStateInfo (TPraos c) = KESInfo

data ProtocolInfo m b = ProtocolInfo {
        pInfoConfig      :: TopLevelConfig b
      , pInfoInitLedger  :: ExtLedgerState b -- ^ At genesis
      , pInfoLeaderCreds :: Maybe ( CanBeLeader (BlockProtocol b)
                                  , m (BlockProduction m)  -- monadic
                                  )
      }

Reducing to medium priority because we could release without it, and improve this in a future update (without breaking any kind of compatibility). It would still be really good to have it included though, so leaving it assigned to the current milestone.

Done in #2418


OpenSSL s_client not able to connect to the server with Openssl 3.0.3

We are facing a connectivity issue while connecting to the server through the s_client utility. We could see it able to connect with _-no_tls1_3 but not with tls1_3. It seems to be some connection reset happening at the server end. We could see there is no response from the server for clientHello  sent by the server. Since the same works fine with tls1_2 so it shouldn't be a problem with the server end. Kindly find the attached logs for reference.
With Default
openssl.exe s_client -connect <host_name>:<port> -CAfile <file>.pem
CONNECTED(0000010C)
write:errno=10054
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 297 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---

Works with explicitly mentioning -no_tls1_3:
openssl.exe s_client -no_tls1_3 -connect <host_name>:<port> -CAfile <file>.pem
CONNECTED(00000128)
Can't use SSL_get_servername
depth=1 DC = com, DC = cs, DC = ADserver, CN = ADserver-CSPQ202WINSQL-CA
verify return:1
depth=0 CN = CSPQ202WINSQL.ADserver.cs.com
verify return:1
---
Certificate chain
 0 s:CN = CSPQ202WINSQL.ADserver.cs.com
   i:DC = com, DC = cs, DC = ADserver, CN = ADserver-CSPQ202WINSQL-CA
   a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
   v:NotBefore: Feb  2 14:01:53 2022 GMT; NotAfter: Feb  2 14:01:53 2023 GMT
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIHQzCCBSugAwIBAgITUwAAAAPPrZAfs1y4nAAAAAAAAzANBgkqhkiG9w0BAQsF
ADBnMRMwEQYKCZImiZPyLGQBGRYDY29tMRIwEAYKCZImiZPyLGQBGRYCY3MxGDAW
BgoJkiaJk/IsZAEZFghBRHNlcnZlcjEiMCAGA1UEAxMZQURzZXJ2ZXItQ1NQUTIw
MldJTlNRTC1DQTAeFw0yMjAyMDIxNDAxNTNaFw0yMzAyMDIxNDAxNTNaMCgxJjAk
BgNVBAMTHUNTUFEyMDJXSU5TUUwuQURzZXJ2ZXIuY3MuY29tMIIBIjANBgkqhkiG
9w0BAQEFAAOCAQ8AMIIBCgKCAQEAylGvk8x4ddaJOejA8wVLOwwIRFW0KHJPjK85
hbJ7gIoeQZnRLq0GAUOcbYoJ1tFnaJ99TH2fZNqGotVoMkZAJCJz7AcfUGRtA07F
QiF9kCDjiqxR4SQ+Sk2/VKY8ZX7vGvFC2DHGKsITG5LpqyatiacAqip0Wsc+60Ev
q8PU7MccEuhrrA68+G4umO+BDly/VNT8hg8HtJa2WB4P1uVDdO7Uk1fKNxHdMpA9
+2xlsKyNQwf+Kau6jG8nW9vD9l0BwOdi603FDraWVt2ZCALFi/S8Jk9cZqC9sfua
nSXIxBUjNHi/7dqAbcgd45yv+o4MD0q+8WrFOC2znsJB9XoIyQIDAQABo4IDJTCC
AyEwLwYJKwYBBAGCNxQCBCIeIABEAG8AbQBhAGkAbgBDAG8AbgB0AHIAbwBsAGwA
ZQByMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDATAOBgNVHQ8BAf8EBAMC
BaAweAYJKoZIhvcNAQkPBGswaTAOBggqhkiG9w0DAgICAIAwDgYIKoZIhvcNAwQC
AgCAMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAS0wCwYJYIZIAWUDBAECMAsGCWCG
SAFlAwQBBTAHBgUrDgMCBzAKBggqhkiG9w0DBzBJBgNVHREEQjBAoB8GCSsGAQQB
gjcZAaASBBD2OtdvVXqlRpNynZaRdj/mgh1DU1BRMjAyV0lOU1FMLkFEc2VydmVy
LmNzLmNvbTAdBgNVHQ4EFgQUlSelO7I1GxAgbZWdrNcq4GPq8t8wHwYDVR0jBBgw
FoAUpYhQesmOm5pucV95g7JggEhab9wwgeQGA1UdHwSB3DCB2TCB1qCB06CB0IaB
zWxkYXA6Ly8vQ049QURzZXJ2ZXItQ1NQUTIwMldJTlNRTC1DQSxDTj1DU1BRMjAy
V0lOU1FMLENOPUNEUCxDTj1QdWJsaWMlMjBLZXklMjBTZXJ2aWNlcyxDTj1TZXJ2
aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPUFEc2VydmVyLERDPWNzLERDPWNvbT9j
ZXJ0aWZpY2F0ZVJldm9jYXRpb25MaXN0P2Jhc2U/b2JqZWN0Q2xhc3M9Y1JMRGlz
dHJpYnV0aW9uUG9pbnQwgdIGCCsGAQUFBwEBBIHFMIHCMIG/BggrBgEFBQcwAoaB
smxkYXA6Ly8vQ049QURzZXJ2ZXItQ1NQUTIwMldJTlNRTC1DQSxDTj1BSUEsQ049
UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJh
dGlvbixEQz1BRHNlcnZlcixEQz1jcyxEQz1jb20/Y0FDZXJ0aWZpY2F0ZT9iYXNl
P29iamVjdENsYXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkwDQYJKoZIhvcNAQEL
BQADggIBAFqf3pWsMRdm2u4mArk5CqRGsCzs0yhYb5s68wTmbR8LsxR2YBtWWPUu
CWPKn6OJKQte+bmzEkg4/J+nuzLRIooA8zJvapdXpfA3F8xLwnFnKBADKXpI3TpP
cJwM40S61uSHHtEmY3hegSA4uLzpMRReTVpKwD22WkRq29X3zWgnpKyuH82gLjIQ
szT8ac0X8OH9t1pT47j48jd7yryCDSJlXvOEzCiO6QqoUd8TZxWkxC6rQoIFbNBp
U+hZFGH14t/+f6NZY1VoeJP8nYSP+3uICZStIgdKuz40RSmLbRajfu2XbISyYHjr
oamo7Sd94UhwmznlN5MHxdpvQkZSI4TfOml227Df+PoBiOKQZZAzdPkvIL8QzTfp
/fVlINBIpMD9znM7QDgMoNr6pPGM6SyuIcs9mlLGDQu3scFooYIpTg5dNWXe1LAD
BtNqoKIGmjZZCZgcmCEVR9kDEemNKVmhmXwXmkiMt4YUKB7da1TvyJtSJazf2hQv
Q+PsS26b/Ikne7NipdZogkNqoZBbqtmVCYcuMciTTl4g8min1GQ6oCPQEk6VvB8Y
RHHzoeeKxo1yoGWgUL+zooTryYg1yyhC7Qm9Lw7VYbCAFGDz/B8u+0kPQcfcY0Mn
qig5eOVauaDbxR2LCzq5a682vnvOLKlFC6UqtzAqPingXUI9SQnp
-----END CERTIFICATE-----
subject=CN = CSPQ202WINSQL.ADserver.cs.com
issuer=DC = com, DC = cs, DC = ADserver, CN = ADserver-CSPQ202WINSQL-CA
---
No client certificate CA names sent
Client Certificate Types: RSA sign, DSA sign, ECDSA sign
Requested Signature Algorithms: RSA+SHA256:RSA+SHA384:ECDSA+SHA256:ECDSA+SHA384:RSA+SHA512:ECDSA+SHA512
Shared Requested Signature Algorithms: RSA+SHA256:RSA+SHA384:ECDSA+SHA256:ECDSA+SHA384:RSA+SHA512:ECDSA+SHA512
Peer signing digest: SHA256
Peer signature type: RSA
Server Temp Key: ECDH, secp384r1, 384 bits
---
SSL handshake has read 2407 bytes and written 358 bytes
Verification: OK
---
New, TLSv1.2, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES256-GCM-SHA384
    Session-ID: D8410000A9C94631D121E6F5915D7AB66605A651DB1DA7146EBEA2FCE3806208
    Session-ID-ctx:
    Master-Key: 598C3F9AE11B0547CD7A3F0B8D606F6164F3BAAD4DB0C64B7750BD92166AB0B2F89C77C10091F84595762CA9CDD3E0FA
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time:<PHONE_NUMBER>
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
    Extended master secret: yes
---

This issue is observed with openssl-3.0.3 specifically. @mattcaswell: Would really appreciate if you can throw some light on this?

So, to be clear, both server and client are using OpenSSL 3.0.3?

This issue is observed with openssl-3.0.3 specifically.

Which other versions have you tried it with?
Are server and client on the same machine or is there a network between them? If there is a network is there any firewall or other middlebox in between?

@mattcaswell  Please find my response inline.

So, to be clear, both server and client are using OpenSSL 3.0.3?

No. The Server and client both are not using the same version. The server is Microsoft LDAP AD.

This issue is observed with openssl-3.0.3 specifically.
Which other versions have you tried it with?

Have tried with older openssl versions like 1.0.2, and 1.1.1. Didn't encounter any issues. Even if don't exclude tls1_3, in that case, the client should be flexible enough to mutually agree on the supported version(assuming the server doesn't support tls1_3). Unfortunately, we don't see any response from the server to the clientHello but we could see the TCP connection reset.

Are the server and client on the same machine or is there a network between them? If there is a network is there any firewall or other middlebox in between?

The server and the client are not on the same machine. But they are on the same network. The utility works fine if we exclude the tls1_3 with the same server. So we can rule out it as a networking issue.

Also did you build OpenSSL yourself - and if so what Configure line did you use?

We have built the OpenSSL-3.0 ourselves with fips-capability. Since the same built utility works fine without tls1_3, so I think there shouldn't be any issue like fips enabling only at the client side. We suspect there might be some issue on the server side. Any thoughts, Something has to be taken care of explicitly for non-openssl based servers.
Please find the attached configuration below.

Command line (with current working directory = .):

    C:\Strawberry\perl\bin\perl.exe Configure --prefix=C:\openssl --openssldir=C:\openssl VC-WIN64A enable-fips

Perl information:

    C:\Strawberry\perl\bin\perl.exe
    5.32.1 for MSWin32-x64-multi-thread

Enabled features:

    acvp-tests
    aria
    asm
    async
    autoalginit
    autoerrinit
    autoload-config
    bf
    blake2
    bulk
    cached-fetch
    camellia
    capieng
    cast
    chacha
    cmac
    cmp
    cms
    comp
    ct
    deprecated
    des
    dgram
    dh
    dsa
    dso
    dtls
    dynamic-engine
    ec
    ec2m
    ecdh
    ecdsa
    engine
    err
    filenames
    fips
    fips-securitychecks
    gost
    idea
    legacy
    loadereng
    makedepend
    md4
    mdc2
    module
    multiblock
    nextprotoneg
    ocb
    ocsp
    padlockeng
    pic
    pinshared
    poly1305
    posix-io
    psk
    rc2
    rc4
    rdrand
    rfc3779
    rmd160
    scrypt
    secure-memory
    seed
    shared
    siphash
    siv
    sm2
    sm3
    sm4
    sock
    srp
    srtp
    sse2
    ssl
    ssl-trace
    static-engine
    stdio
    tests
    threads
    tls
    ts
    ui-console
    uplink
    whirlpool
    tls1
    tls1-method
    tls1_1
    tls1_1-method
    tls1_2
    tls1_2-method
    tls1_3
    dtls1
    dtls1-method
    dtls1_2
    dtls1_2-method

Disabled features:

    afalgeng            [not-linux] OPENSSL_NO_AFALGENG
    asan                [default]   OPENSSL_NO_ASAN
    buildtest-c++       [default]
    crypto-mdebug       [default]   OPENSSL_NO_CRYPTO_MDEBUG
    devcryptoeng        [default]   OPENSSL_NO_DEVCRYPTOENG
    ec_nistp_64_gcc_128 [default]   OPENSSL_NO_EC_NISTP_64_GCC_128
    egd                 [default]   OPENSSL_NO_EGD
    external-tests      [default]   OPENSSL_NO_EXTERNAL_TESTS
    fuzz-afl            [default]   OPENSSL_NO_FUZZ_AFL
    fuzz-libfuzzer      [default]   OPENSSL_NO_FUZZ_LIBFUZZER
    ktls                [default]   OPENSSL_NO_KTLS
    md2                 [default]   OPENSSL_NO_MD2 (skip crypto\md2)
    msan                [default]   OPENSSL_NO_MSAN
    rc5                 [default]   OPENSSL_NO_RC5 (skip crypto\rc5)
    sctp                [default]   OPENSSL_NO_SCTP
    trace               [default]   OPENSSL_NO_TRACE
    ubsan               [default]   OPENSSL_NO_UBSAN
    unit-test           [default]   OPENSSL_NO_UNIT_TEST
    weak-ssl-ciphers    [default]   OPENSSL_NO_WEAK_SSL_CIPHERS
    zlib                [default]
    zlib-dynamic        [default]
    ssl3                [default]   OPENSSL_NO_SSL3
    ssl3-method         [default]   OPENSSL_NO_SSL3_METHOD

Config target attributes:

    AR => "lib",
    ARFLAGS => "/nologo",
    AS => "nasm",
    ASFLAGS => "-g",
    CC => "cl",
    CFLAGS => "/W3 /wd4090 /nologo /O2",
    CPP => "\"\$(CC)\" /EP /C",
    HASHBANGPERL => "/usr/bin/env perl",
    LD => "link",
    LDFLAGS => "/nologo /debug",
    MT => "mt",
    MTFLAGS => "-nologo",
    RANLIB => "CODE(0x664af0)",
    RC => "rc",
    ar_resp_delim => "
",
    aroutflag => "/out:",
    asflags => "-Ox -f win64 -DNEAR",
    asm_arch => "x86_64",
    asoutflag => "-o ",
    bin_cflags => "/Zi /Fdapp.pdb",
    bin_lflags => "setargv.obj /subsystem:console /opt:ref",
    bn_ops => "SIXTY_FOUR_BIT",
    build_file => "makefile",
    build_scheme => [ "unified", "windows", "VC-common" ],
    cflags => "/Gs0 /GF /Gy /MD",
    coutflag => "/Fo",
    cppflags => "",
    defines => [ "OPENSSL_BUILDING_OPENSSL", "OPENSSL_SYS_WIN32", "WIN32_LEAN_AND_MEAN", "UNICODE", "_UNICODE", "_CRT_SECURE_NO_DEPRECATE", "_WINSOCK_DEPRECATED_NO_WARNINGS" ],
    disable => [  ],
    dso_cflags => "/Zi /Fddso.pdb",
    dso_scheme => "win32",
    enable => [  ],
    ex_libs => "ws2_32.lib gdi32.lib advapi32.lib crypt32.lib user32.lib",
    includes => [  ],
    ld_implib_flag => "/implib:",
    ld_resp_delim => "
",
    lddefflag => "/def:",
    ldoutflag => "/out:",
    ldpostoutflag => "",
    ldresflag => " ",
    lflags => "",
    lib_cflags => "/Zi /Fdossl_static.pdb",
    lib_cppflags => "",
    lib_defines => [ "L_ENDIAN" ],
    makedep_scheme => "VC",
    makedepcmd => "\"\$(CC)\" /Zs /showIncludes",
    module_cflags => "",
    module_cxxflags => undef,
    module_ldflags => "/dll",
    mtinflag => "-manifest ",
    mtoutflag => "-outputresource:",
    multilib => "-x64",
    perl_platform => "Windows::MSVC",
    perlasm_scheme => "auto",
    rcoutflag => "/fo",
    shared_cflag => "",
    shared_defflag => "",
    shared_defines => [  ],
    shared_ldflag => "/dll",
    shared_rcflag => "",
    shared_target => "win-shared",
    sys_id => "WIN64A",
    thread_defines => [  ],
    thread_scheme => "winthreads",
    unistd => "<unistd.h>",
    uplink_arch => "x86_64",

Recorded environment:

    AR =
    ARFLAGS =
    AS =
    ASFLAGS =
    BUILDFILE =
    CC =
    CFLAGS =
    CPP =
    CPPDEFINES =
    CPPFLAGS =
    CPPINCLUDES =
    CROSS_COMPILE =
    CXX =
    CXXFLAGS =
    HASHBANGPERL =
    LD =
    LDFLAGS =
    LDLIBS =
    MT =
    MTFLAGS =
    OPENSSL_LOCAL_CONFIG_DIR =
    PERL =
    RANLIB =
    RC =
    RCFLAGS =
    RM =
    WINDRES =
    __CNF_CFLAGS =
    __CNF_CPPDEFINES =
    __CNF_CPPFLAGS =
    __CNF_CPPINCLUDES =
    __CNF_CXXFLAGS =
    __CNF_LDFLAGS =
    __CNF_LDLIBS =

Makevars:

    AR              = lib
    ARFLAGS         = /nologo
    AS              = nasm
    ASFLAGS         = -g
    CC              = cl
    CFLAGS          = /W3 /wd4090 /nologo /O2
    CPP             = "$(CC)" /EP /C
    CPPDEFINES      =
    CPPFLAGS        =
    CPPINCLUDES     =
    CXXFLAGS        =
    HASHBANGPERL    = /usr/bin/env perl
    LD              = link
    LDFLAGS         = /nologo /debug
    LDLIBS          =
    MT              = mt
    MTFLAGS         = -nologo
    PERL            = C:\Strawberry\perl\bin\perl.exe
    RANLIB          = ranlib
    RC              = rc
    RCFLAGS         =

NOTE: These variables only represent the configuration view.  The build file
template may have processed these variables further, please have a look at the
build file for more exact data:
    makefile

build file:

    makefile

build file templates:

    Configurations\common0.tmpl
    Configurations\windows-makefile.tmpl

No. The Server and client both are not using the same version. The server is Microsoft LDAP AD running on a secure 636 port.

Do you have access to the server? If so are there any logs that might be useful there? It seems like the server is rejecting the connection but closing it down uncleanly without giving any alert. Possibly there is something in the ClientHello that it doesn't like - but there's not much to go on here.

Have tried with older openssl versions like 1.0.2, and 1.1.1. Didn't encounter any issues.

So, does attempting to connect to the server with TLSv1.3 enabled work with 1.1.1?

The server and the client are not on the same machine. But they are on the same network. The utility works fine if we exclude the tls1_3 with the same server. So we can rule out it as a networking issue.

Well, not necessarily. There are some middleboxes that inspect the TLS protocol contents, but don't understand TLSv1.3 and fail with it. However if 1.1.1 works with TLSv1.3 enabled then we probably can rule out the network.

You can also try to change the ciphersuites, supported groups, etc. on the client side to see if that helps.

It was an issue from the windows server side. Thanks, @mattcaswell for your input. Much appreciated. We can close this issue.


docs: more corrections and suggest on slugify

:tada: This PR is included in version 1.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat: add a few usability functions to the interface

feat: add a few usability functions to the interface
Issue: https://github.com/0xPolygonZero/zk_evm/issues/67

Can we update the changelog and we'll merge


Version solving fails when using newest version of build_runner and/or json_serializable

Because build_runner >=2.0.0 depends on dart_style ^2.0.0 and intl_translation >=0.17.0 depends on dart_style
^1.0.0, build_runner >=2.0.0 is incompatible with intl_translation >=0.17.0.
And because intl_translation <0.17.0 requires SDK version >=1.12.0 <2.0.0, build_runner >=2.0.0 is incompatible
with intl_translation.
So, because app depends on both intl_translation any and build_runner ^2.0.3, version solving failed.
And:
Because json_serializable >=4.1.0 depends on source_gen ^1.0.0 which depends on dart_style ^2.0.0,
json_serializable >=4.1.0 requires dart_style ^2.0.0.
And because intl_translation >=0.17.0 depends on dart_style ^1.0.0 and intl_translation <0.17.0 requires SDK
version >=1.12.0 <2.0.0, json_serializable >=4.1.0 is incompatible with intl_translation.
So, because kra_app_web depends on both intl_translation any and json_serializable ^4.1.2, version solving
failed.

Is there any update with this issue?

ditto


Add some hash algorithms

I'm sorry to tell you that, but these algorithms are very insecure. Every hash algorithm still needs a unique salt for every generation.
Furthermore some of those algorithms are way too fast that you can brute force even long password within a short time or someone else already did that (see rainbow-tables). md5 is a big example for that. That's the reason a lot of developers are removing support for md5.


Flush remote TLB

There are only two hard things in Computer Science: cache invalidation and naming things.
-- Phil Karlton

Implemented on x86_64 in c88c019.
Thanks @gjz010.


Update http4s-client, http4s-dsl, ... to 0.23.10

Updates

org.http4s:http4s-client
org.http4s:http4s-dsl
org.http4s:http4s-okhttp-client

from 0.23.3 to 0.23.10.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, early-semver-minor, semver-spec-patch, commit-count:1

Codecov Report

Merging #359 (ac572ba) into master (92c2a41) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #359   +/-   ##
=======================================
  Coverage   47.49%   47.49%
=======================================
  Files          29       29
  Lines         299      299
  Branches        6        6
=======================================
  Hits          142      142
  Misses        157      157

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 92c2a41...ac572ba. Read the comment docs.

Superseded by #365.


Added route for navigation component #25

Description
Added a new route inside Routes.js called 'dashboard'. Fixed the height of the navigation drawer.
Related Issue
Fixes #36
Type of Change:

Code

Code/Quality Assurance Only

Bug fix (non-breaking change which fixes an issue)
This change requires a documentation update (software upgrade on readme file)

How Has This Been Tested?
Tested by rendering on my local machine
Checklist:

[ ] Pull request is made against development branch.
[ ] My code follows the style guidelines of this project.
[ ] I run npm run format before creating the pull request.
[ ] I have performed a self-review of my own code.
[ ] I have updated documentation accordingly.
[ ] My changes generate no new warnings
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

[ ] My UI is responsive
[ ] UI made replicates the design provided

Screenshots (if appropriate):

Thanks @shrutigupta5555 for the PR.


Theatre mode settable params

what about add some class to body element?
For example:
body.fluid_theatre_mode .sidebar {display:none}


Tooltip doesn't show on hover

Discussed in https://github.com/carbon-design-system/carbon-components-svelte/discussions/1802

Originally posted by geoidesic September  1, 2023
https://carbon-components-svelte.onrender.com/components/Tooltip
I can appreciate that on click is useful and necessary for mobile devices but it's not useful for desktop, where the idea is that a tooltip provides information about the element you are hovering over.
The one on the IBM live demo works as expected: https://carbondesignsystem.com/components/tooltip/usage/#live-demo

carbon-components-svelte is still on v10 of the design system while the current version is v11.
Would have to dig through the history but I think this is according to specification.
In v11 Tooltip was sort of split up into two components: Tooltip, which should not contain interactive content and shows on hover and Toggletip, which can have interactive content and requires a click.
You can see a reference to this in the migration guide:

Tooltip, TooltipIcon, and TooltipDefinition are also receiving updates in v11 and mirror some of the changes seen in Notification. For example, Tooltips can now only contain interactive content. For situations that require interactive content, we are shipping a new component: Toggletip.

And the Toggletip docs:

New in v11: Toggletip should be used in place of tooltip if your content will contain interactive elements. If it does not have any interactive content, consider using Tooltip instead.

If you want a simple tooltip that appears on hover you can use TooltipIcon or TooltipDefinition.


use of defaultNumberingSystem when loading locale

In locale data provided by CLDR, there is for some language a field named "defaultNumberingSystem" in numbers, which give the numbering system that should be used by default.
Currently we are not using this and just take the first one like it's often in alphabetical order it's often the bad one. (for exemple fr locale use data of arabic numbering system instead of latin)
In this PR I check if this field is defined, and if it is i use the numberingSystem indicate in the field.

Could you add a test class for the test runner to ensure the correct result? Thank you.

Of course I can do that, however just a question what do you think is the best place to test that? Should it be in test-compiler.js

see my updated comment - the right place is probably qx.test.locale.Locale

oh thank you was looking in the qooxdoo-compiler not directly in qooxdoo, so i have to do an other PR directly in qooxdoo repo? (sorry not really familiar to work in different but linked repo)

This is compiler related - so we must test it in compiler. The old python toochain is not using defaultNumberingSystem.
@cboulanger : What do you want to test?

@rommni @hkollmann You're right. I didn't look carefully enough in which repo this PR was created! If this would break compiler builds, of course we cannot put the test in the qooxdoo framework repo (yet), altough eventually it should be part of the main test suite.
@hkollmann We should have a test to make sure the change works as intended and that there won't be a regression in the future - shouldn't this be part of any code change that affects existing behaviour? However, this is a special situation in which the behavior depends on the toolchain.

@rommni @hkollmann We don't have a place for these kind of tests yet, it seems. Tests in the compiler repo concern compilation behavior, not framework code behavior. The cleanest solution would be to add a test in the qooxdoo repo which runs it dependent on the compiler version in the environment variable "qx.compilerVersion".

@rommni @hkollmann But this can be added only after this change has been integrated and published.
@rommni  maybe you could locally add the test to qx.test.locale.Locale? Then we could integrate it later to the qooxdoo framework, using if (!qx.core.Environment.get("qx.compilerVersion"){return} to skip it in case of generator builds.

@cboulanger of course i can look at this (not today but maybe during next week), maybe i could even create a qx.test.locale.Number like we have a Date one, test the value of group & decimal sign in different locale with and without the defaultNumberingSystem field, and test the number percent format which is the other information we get from locale related to number, we can then add more test if we decide in future to get more information from locale file.

merging, thank you @rommni !


Add blurite bar to item identification

Added blurite bar into item identification

If you're adding this, you probably also want to add e.g. lunar bar and lovakite bar.

If you're adding this, you probably also want to add e.g. lunar bar and lovakite bar.
Done

@YvesW Hey, do you know what the process is to get this pull request merged? This is my first pull request for a open repository

Just wait patiently for a maintainer to review it.


Add prefix to struct member names in shader compiler

(to prevent possible conflicts with defines)

Closes https://github.com/godotengine/godot/issues/98740

Thanks!


ACC-270.1(Level A)_Kyma-dashboard_Search Field_UI not keyboard accessible.

1.1 Internal Message Details
Internal Message:
Test Plan:	ACC SAP Kyma runtime 2024
Message Priority:	Medium
Affected Check Point:	ACC-270.1
Affected UI:	Search Field
Short text:	ACC-270.1(Level A)_Kyma-dashboard_Search Field_UI not keyboard accessible.
1.2 Application Details
Application Name	Kyma-dashboard
Application URL:	https://canary.cockpit.btp.int.sap/cockpit#/globalaccount/7304343e-1ce0-412b-a955-5948bab9d2c8/subaccount/e0ec1134-2770-40a2-910b-2b8e32ec8f60/subaccountoverview
User:	SSO
Technology:	SAP UI5
UI5 Version:	1.124.1
1.3 Test Environment Details:
GitHub	https://github.com/kyma-project/busola/issues
Web browser:	Google Chrome - Version 127.0.6533.73 (Official Build) (64-bit)
Operating System:	Windows 11 Enterprise Version 22H2
Screen Reader:	JAWS 2024.2405.83 ILM 64 bit for Windows
2. Screen Flow
•	Login into the application using the URL provided.
•	URL: https://canary.cockpit.btp.int.sap/cockpit#/globalaccount/7304343e-1ce0-412b-a955-5948bab9d2c8/subaccount/e0ec1134-2770-40a2-910b-2b8e32ec8f60/subaccountoverview.
•	Activate ‘Console URL:Link to dashboard’ in overview page.
•	Activate ‘Namespaces overview’ left navigation section.
3. Issue
Synopsis: UI not keyboard accessible.
Observed Behavior:
‘Learn More’ link within ‘Overview’ page is not keyboard accessible in forward navigation.
Expected Behavior:
Each & every UI, must be accessible using the keyboard.
Keyboard is the prerequisite for support of assistive technologies to enable users with disabilities to read and operate software applications, hence all the UIs must be accessible with keyboard.

Kindly refer to attached error and issue processing document for more details.
Regards,
Huda

ACC-270.1(Level A)_Kyma-dashboard_Search Field_UI not keyboard accessible.docx
Issue processing-09.2021 (1).docx


RequestParam with a map crashes swagger-ui

When adding @RequestParam Map<String, String> params to an endpoint, swagger-ui throws: Uncaught TypeError: Cannot read property 'type' of undefined. This works in version 2.4.0

Version 2.5.0

I researched this and I've added an issue in the swagger-ui project.


kernel does not show immediately after metadata changed

Bug: Notebook Editor, Interactive Window, Editor cells

Steps to cause the bug to occur
After I inserted the kernelspec to the config file of ipynb, I have to close vscode and restart it again. Then I can see the kernel I want.
I think that it may because the notebook cache the data. And only by closing and reopening vscode can it be able to read the updated kernelspec and go effect.
By the way, I also did some workaround such as 1.close t5.ipynb window and reopen it again 2.restart kernel.3.restart my computer. Unfortunately, none of them can work for me>_<. Would you mind help us again on it? Thanks a lot!

Your Jupyter and/or Python environment
Version: 1.42.0 (user setup)
Commit: ae08d5460b5a45169385ff3fd44208f431992451
Date: 2020-02-06T10:51:34.058Z
Electron: 6.1.6
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18363
Developer Tools Console Output

Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer

@IanMatthewHuff Please feel free to let me know if more info is needed. And it would be very kind of you to take a look at it(still blocking us>_<). Thank you so much!

@zesluo  this is happening because we don't watch the notebooks on disk. Meaning if you change a file outside of VS code, you have to reload the VS code window for us to get the updates.

You should be able to switch kernels though using the VS code UI (if that's the only change you wanted to make in the notebook metadata).


Fixed RAIL window can't show again once hidden

The cause is very simple: we didn't map the xwindow on receiving
WINDOW_SHOW. but doing that causes another problem that you can't
hide a window anymore, and that is because whlie window hiding, the
_NET_WM_STATE and WM_STATE properies of the xwindow may change, in
the function xf_event_PropertyNotify we just assume that windows
not maximized, not minimized, yet not showing normally should be
corrected to be shown, we just need to consider the situation that
the window is hidden here.
fix: #5078

Wow, PRs get merged so quickly, I'm so impressed :) Good job @akallabeth @hardening


Questions about patch length and augmentation

Thank you so much for the wonderful paper! We are trying to apply your model (Timer-XL to be exact) to our large iEEG data (~100B timepoints) to create a foundation model and had a few questions if you don't mind. Your insights would be greatly helpful in applying your model to our data!

Why did you choose a patch length of 96? : Why did you choose a (quite-long) patch length of 96, and are there things we should consider when choosing the optimal patch length? (ex : should we choose length that is long enough so that next token prediction is hard?)

What do you think of patching with multiple patch lengths? :  Recent papers such as MTST , Pathformer , and Medformer seem to argue that using multiple patch sizes enables the model to learn various dynamics at different frequencies/granularities.  Given that Timer uses a single patch size, we were wondering what you think about this. (Modeling various granularities is critical for us as neural data is very multi-scale with meaningful frequencies ranging from 0.5Hz to 250Hz)

Did you pre-train a separate imputation model? : It seemed that the patch lengths for the imputation and pretraining were different (24 vs 96). Does this mean that you pre-trained a model specifically for imputation?

What do you think about augmentation? : Do you think that augmentation is unnecessary when training with lots of data like in Timer? Or do you think domain-specific augmentations could still help? Would masking several segments during pretraining help make the SSL task more difficult, and hence better (similar to how the model was pre-trained during imputation)?

Thank you in advance for you and your group's  amazing work! It's really helping us get into time-series modeling for brain data!

Hello, nice to you again!
(1) The token length is set to 96 mainly for consideration of the paper benchmark. You can try to use a longer token length based on the predicted length, which can significantly avoid the accumulation of errors.
(2) Of course. Given the prior knowledge about the frequencies in the brain data, we strongly recommend multiple patch lengths by using multiple embedding layers.
(3) Yes, but they are both pre-trained on the UTSD. Since the patch requirement for forecasting and imputation is quite different, you can also train a new embedding layer starting from the forecasting checkpoint for other tasks.
(4) I'm a little unsure about that because I am not familiar with domain-specific augmentations. If you are using a pre-trained model for tasks other than prediction (generation) (e.g., anomaly detection, classification), we think masking modeling should also be worth trying.

Thank you for your responses!

Oh I see! Makes sens to not do rolling prediction.

I see! Are you by any chance working on multi-patch size methods? I know in the appendix of your Timer-XL paper, you said your next work will be multi-resolution patches! (I feel like simply using multiple patch sizes then applying attention across them would greatly increase the memory used?)

Oh I see! Thank you

Hmmm I see. Most of the downstream-tasks in EEG is classification, so I guess we should also try masking modeling! I hope the OpenLTM is updated to also include masked pre-training! :)

Thank you!


Understanding tree structure for multiclass classification

In my problem I have 3 classes to predict and I'm trying to understand how the xgboost tree relates to the predicted probabilities:
model2=xgboost(data = as.matrix(train_set), label = output_vector, max.depth = 3,
               eta = 1, nround = 50,objective = "multi:softprob",num_class=3,
               verbose = FALSE)
names <- dimnames(train_set)[[2]][-c_set]
trees=xgb.model.dt.tree(names,model = model2)

The first few lines of the tree is as below:
    ID      Feature Split Yes  No Missing   Quality     Cover Tree Yes.Feature Yes.Cover Yes.Quality
1: 0-0 location1100   0.5 0-1 0-2     0-1 26.142200 2666.6700    0 location995   2651.56   22.050700
2: 0-1  location995   0.5 0-3 0-4     0-3 22.050700 2651.5600    0 location962   2637.33   14.790700
3: 0-2         Leaf    NA  NA  NA      NA -0.579310   15.1111    0          NA        NA          NA
4: 0-3  location962   0.5 0-5 0-6     0-5 14.790700 2637.3300    0        Leaf   2620.44    0.723138
5: 0-4         Leaf    NA  NA  NA      NA -0.503650   14.2222    0          NA        NA          NA
6: 0-5         Leaf    NA  NA  NA      NA  0.723138 2620.4400    0          NA        NA          NA
   No.Feature No.Cover No.Quality
1:       Leaf  15.1111  -0.579310
2:       Leaf  14.2222  -0.503650
3:         NA       NA         NA
4:       Leaf  16.8889  -0.204969
5:         NA       NA         NA
6:         NA       NA         NA

how would this relate to the classes as there is only a "yes" or "no" split. Even the leafs do not mention a class that they belong to nor a probability associated. I guess in some ways what I'm asking is how would I manually calculate the probabilities for a test case given the tree structure (in my case in the variables trees).

A tree always seperates only two classes. Hence, if you have 3 classes, xgb grows 3 trees per boosting round (class 1 vs rest, class 2 vs rest & class 3 vs rest).


Tuple structs cannot be deserialized

Relates to: https://github.com/torrust/torrust-serde-bencode/issues/12
It seems you can not deserialize a tuple struct like this struct Node(String, i64) from a nested list in encoded format. There are already two tests for this behavior.
   #[test]
    fn deserialization() {
        // todo: you cannot deserialize to the same struct used in serialization.
        // It does not work with a tuple struct `struct Node(String, i64)`
        // instead of a tuple `(String, i64)`.

        #[allow(dead_code)]
        #[derive(PartialEq, Debug, Serialize, Deserialize)]
        struct Torrent {
            info: Info,
            #[serde(default)]
            nodes: Option<Vec<(String, i64)>>,
        }

        #[allow(dead_code)]
        #[derive(PartialEq, Debug, Serialize, Deserialize)]
        struct Info {
            #[serde(default)]
            pub length: Option<i64>,

            #[serde(default)]
            pub name: String,

            #[serde(rename = "piece length")]
            pub piece_length: i64,

            #[serde(default)]
            pub pieces: ByteBuf,
        }

        #[derive(PartialEq, Debug, Serialize, Deserialize)]
        struct Node(String, i64);

        // cspell:disable-next-line
        let b = "d4:infod6:lengthi8e4:name11:minimal.txt12:piece lengthi1e6:pieces1:pe5:nodesll15:<IP_ADDRESS>i56711eel14:<IP_ADDRESS>i13386eeee";

        let r: Torrent = from_str(b).unwrap();

        assert_eq!(
            r,
            Torrent {
                info: Info {
                    name: "minimal.txt".to_string(),
                    pieces: ByteBuf::from(vec![b'p']),
                    piece_length: 1,
                    length: Some(8),
                },
                nodes: Some(vec![
                    ("<IP_ADDRESS>".to_string(), 56711),
                    ("<IP_ADDRESS>".to_string(), 13386),
                ]),
            }
        );
    }

Although you can serialize them:
    #[test]
    fn serialization() {
        #[allow(dead_code)]
        #[derive(PartialEq, Debug, Serialize, Deserialize)]
        struct Torrent {
            info: Info,

            #[serde(default)]
            nodes: Option<Vec<Node>>,
        }

        #[allow(dead_code)]
        #[derive(PartialEq, Debug, Serialize, Deserialize)]
        struct Info {
            #[serde(default)]
            pub length: Option<i64>,

            #[serde(default)]
            pub name: String,

            #[serde(rename = "piece length")]
            pub piece_length: i64,

            #[serde(default)]
            pub pieces: ByteBuf,
        }

        #[derive(PartialEq, Debug, Serialize, Deserialize)]
        struct Node(String, i64);

        let torrent = Torrent {
            info: Info {
                name: "minimal.txt".to_string(),
                pieces: ByteBuf::from(vec![b'p']),
                piece_length: 1,
                length: Some(8),
            },
            nodes: Some(vec![
                Node("<IP_ADDRESS>".to_string(), 56711),
                Node("<IP_ADDRESS>".to_string(), 13386),
            ]),
        };

        // cspell:disable-next-line
        assert_eq!(to_string(&torrent).unwrap(), "d4:infod6:lengthi8e4:name11:minimal.txt12:piece lengthi1e6:pieces1:pe5:nodesll15:<IP_ADDRESS>i56711eel14:<IP_ADDRESS>i13386eeee");
    }

Both options:

nodes: Option<Vec<Node>>, where Node is struct Node(String, i64)
nodes: Option<Vec<(String, i64)>>,

produce the same bencoded, but you can only deserialize the second one. The first one gives you only one item in the parent list (one node).
I am still determining if that's a bug. As bencoded format is ordered, there should be no problem assigning the values to the tuple struct fields (0 and 1). The first value should be assigned to the first element in the tuple.
Anyway, ti seems the problem is not even in this package but when the series values are mapped to the final struct (not sure).

Moved to upstream repo: https://github.com/toby/serde-bencode/issues/37


C/C++ project integrations.

This cookie cutter is great for pure Python projects, but a concern we will likely run into is how to integrate hybrid Python/C/C++ projects. Perhaps not recommended for this cookie cutter (we might consider another cookie cutter), but I think a reasonable place to open discussions.
Personally I try to adhere to the following rules:

If pure C, use Python ctypes and the wonderful numpy.ctypeslib.
If C++, use PyBind11. Note that mixing PyBind11 versions can be problematic.
If only called via Python try to use the native distutils/setuptools compilation options which work ok as long as nothing complex is used. This fails when binding complex C++/CMake ecosystems however (Psi4 as an example)
If called via Python and also linked at the shared object level write a setup.py that calls CMake. Example here.

We have a number of solutions depending on the requirements and things get quite messy depending if CMake is in the mix or not. I have tried to follow scikit-build without too much success. Opinions and discussion are most welcome.

I think its a great idea to include this info! I don't think anyone has tried to tackle this yet in cookiecutter form.
Depending on how complex we make it, we could add a cookiecutter.json boolean/dict to include C/C++ bindings and have Jinja add all the additional settings. Otherwise I think a derivative cookiecutter should be made.
I think we will need to be careful (or complex) with our Jinja templates depending on how complex we want to make a single repo.

Personally I try to adhere to the following rules...

I like these rules, but I worry about how much we want to include with with a general repo for complex CMake builds. I think starting with those 4 points in a simple fashion may be a good starting point.

Most of the choices are not terribly complex to setup and can be handled by Jinja I believe. Mostly the diversity of options make the correct choice quite difficult. I do not have simpler rules of the thumb and I think will mostly come down to how everyone uses compiled languages (worth thinking about Fortran as well).
In your experience is the largest user base:
A) Simple C programs to improve various loops (can be replaced by numba/numexpr?)
B) Relatively simple C++ programs to handle object-based loops or similar.
C) Complex C++ ecosystems such as RDKit integration or similar.

My personal experience is A and B in about equal proportions where users have somewhat simple C/C++ objects, but others may have different experiences. I would include Cython in the list of simple handlers too.
I think the audience falling in option C) category are probably not the target audience for this repo, unless you see people wanting to cross over from having complex C++ projects into the Python realm

Good point about cython, the toolchain should be pretty similar to A. For B we could perhaps simply say start with this cookie cutter and then follow the PyBind11 documentation which is fairly decent these days. I dont think we need to cookie cutter everything (especially if folks are at the level to bind C++), but simply pointing towards the desired way of performing these operations could be useful.
The C) option may natively class themselves out of cookie cutters to be honest.

simply pointing towards the desired way of performing these operations could be useful.

That is probably a good idea. We can include that information here and maybe even provide simple instructions of how to modify this cookiecutter output to get started including the PyBind11 hooks.

The gau2grid repo has some CMake integration functionality. Not entirely sure if thats the ultimate way to go.
Another approach is scikit-build which is maturing, documentation and cognitive overhead seems to be improving well over time. Last time I checked I couldn't figure out a basic example.

Closing this, I think it falls outside of the scope of the project currently.


Migrate BXML/BAML to  instead of

Testing this, BAML is producing  when it should generate
e..g http://ap.bandwidth.com/docs/xml/gather/
I ran this example
$ php sample-baml.php Gather requestUrl http://hello.com
The following BaML was generated:
example
Should be
example

Default constructor should now be


Don't retransmit handshake packets once the handshake is complete

Fixes #663.

Codecov Report

Merging #673 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #673      +/-   ##
==========================================
+ Coverage   91.34%   91.34%   +<.01%
==========================================
  Files          81       81
  Lines        5565     5567       +2
==========================================
+ Hits         5083     5085       +2
  Misses        303      303
  Partials      179      179

Impacted Files
Coverage Δ

session.go
88.45% <100%> (+0.05%)
:arrow_up:

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 7a49b06...23bad71. Read the comment docs.


Exception in KeycloakDeployment getting Client

Hi, First thanks for the hard work here giving some light on how to achieve OAuth with Alfresco
I am trying to reproduce this example. I have set everything in an Alfresco 6.2 community as it is and how it is stated in the example here but when I start alfresco I get the following exception
`
wks-docker-wks-platform-repo-acs-1        | Caused by: java.lang.NullPointerException
wks-docker-wks-platform-repo-acs-1        |     at org.keycloak.adapters.KeycloakDeployment.getClient(KeycloakDeployment.java:264)
wks-docker-wks-platform-repo-acs-1        |     ... 59 more
`
Any idea?
Thanks in advance

I think I found the issue, I thought I would have to add the public key but when I add it the issue happens...


Error: unsupported macvlan network option metric

Hello
OS: Arch Linux x86_64
Podman version: 5.1.1-1
Netavark version: 1.11.0-2
I have a container attached to multiple macvlan networks. As some of the networks block access to the internet, my container sometimes can't access the internet as all routes have a default metric of 100.
The podman documentation for podman network create (5.1.1) states that I should be able to change the metric for the network:

--opt, -o=option
Set driver specific options.
All drivers accept the mtu, metric, no_default_route and options.

However, attempting to create a macvlan network with a metric results in an error:
$ sudo podman network create --driver macvlan --interface-name=eth0 --ipam-driver=dhcp --opt=metric=50 foo

Error: unsupported macvlan network option metric

For more information on package versions and podman info please see attached.
Thanks!

This is a podman issue not netavark, podman creates the config file and validates the options not netavark.
Netavark seems to accept and use this option fine.
I move the issue to the right place.