Accessibility Standards

Accessibility Standards
User Story
AS A marketing agency
I WANT a codebase that satisfies accessibility standards
SO THAT our site is efficiently optimized for search engines
Acceptance Criteria
GIVEN a webpage meets accessibility standards
WHEN I view the source code
THEN I find semantic HTML elements
WHEN I inspect images
THEN I find alternative definitions
WHEN I view the HTML5 Outline
THEN I view the proper HTML hierarchy structure

Notes

Multiple elements (large-banner, section, navigator, footer) were added in place of divider elements to promote better accessibility
Added alternative attributes to  for screen readers for better accessibility and search engine optimization purposes
Rearranged <h(1-6)> elements to elicit a semantic structured codebase


Controlled TextField with required enabled initially renders invalid

Package Versions
react: ^16.4.2
rmwc: ^1.9.4
material-components-web: ^0.39.1

From https://github.com/jamesmfriedman/rmwc/issues/280

If you have a controlled TextField with required set it will initially render as invalid due to the initial syncing of the React component props to the MDC component internal state. However, required fields should not render as invalid until they lose focus or the form is submitted.

Example:
import * as React from 'react'

// Components
import { TextField, TextFieldIcon } from 'rmwc/TextField'

// Types
export interface Props {
  value: string
  onChange: (username: string) => void
}

export default class UsernameInput extends React.PureComponent<Props> {
  public render() {
    return (
      <TextField
        outlined
        required
        label={"Username"}
        value={this.props.value}
        onChange={this.onChange}
        withLeadingIcon={<TextFieldIcon icon='person' />}
      />
    )
  }

  // Event handlers
  private onChange = (evt: React.FormEvent<HTMLInputElement>) =>
    this.props.onChange(evt.currentTarget.value)
}

This was fixed with the release of 1.9 since MDC overhauled their internal validation checks. Please reopen if you are still seeing issues.

@jamesmfriedman

Re-opened as I am still encountering this issue.

As a workaround, you can set the text field to valid after mounting. I created a code sandbox:
https://codesandbox.io/s/j239839xy

@rjdestigter every once in a while I comb through the mat-web-react issues and I found the same one. Looks like this is upstream. I'll still look to see if I can patch the adapter / foundation which I've done in a few other cases to hack around the problem.

Verified this will be fixed with the release of MDC 40 and RMWC 3.0.0

This bug is back.
https://codesandbox.io/s/ypvmprv6n9

Thanks for reporting. Experiencing a few regressions with 3.0.7. I’d recommend downgrading to the previous version for the time being.

I just had a crack at fixing it.

I've gone back a few releases but it's still not working. I think my fix isn't going to hack it without access to the previous props in the sync method so you can choose to only call setValue if the value has actually changed (so the first sync won't call it, and the invalid classes won't be applied.)

This fixes the issue:
class Text extends TextField {
  sync() {}

  componentDidUpdate(prevProps) {
    if (prevProps.value !== this.props.value) {
      super.sync(this.props);
    }
  }
}

Thank you!

Should be out with todays patch. Added a test case to make sure this doesn't regress again, although due to having to patch native input validity onto JSDOM, I can't seem to get the full test case to work which would be render valid -> focus -> blur -> invalid.

JSDOM still doesn't do validity? Ugh.

It kind of does with a polyfill I added in, but it’s more of an issue of JSDOM not mimicking the exact same validity behavior when you focus and then blur a required field (which should set it as invalid)


ioPay Desktop supports custom endpoint

https://community.iotex.io/t/how-can-i-connect-iopay-to-a-custom-rpc/1511/6

I have tried it. This rpc url is not available. The testnet, https://babel-api.testnet.iotex.io, is available.


[TabView] Fix wrong visual state of selected item in reenabled TabView

    <StackPanel Spacing="8" HorizontalAlignment="Left">
        <muxc:TabView IsEnabled="{Binding IsChecked, ElementName=chk}">
            <muxc:TabView.TabItems>
                <muxc:TabViewItem Header="Document 1"/>
                <muxc:TabViewItem Header="Document 2"/>
                <muxc:TabViewItem Header="Document 3"/>
            </muxc:TabView.TabItems>
        </muxc:TabView>
        <CheckBox Content="TabView.IsEnabled" IsChecked="True" x:Name="chk"/>
    </StackPanel>

The reason is obvious - two visual state groups inside TabViewItem style are trying to modify the same set of properties.
CommonStates: Normal, PointerOver, Pressed, Selected, PointerOverSelected, PressedSelected
DisabledStates: Enabled, Disabled
Current PR fixes this issue by clearing Disabled visual state.
More exhaustive fix should probably add SelectedDisabled and UnselectedDisabled visual states into CommonStates group, and modify TabViewItem behavior to go to those states as appropriate. Situation is complicated as visual states in both CommonStates and DisabledStates visual groups are managed by ListViewItem that knows nothing about SelectedDisabled (tested on Win11), but we can potentially subscribe to VisualStateGroup::CurrentStateChanged for CommonStates group and to IsEnabledChanged, and switch between Normal <=> UnselectedDisabled and Selected <=> SelectedDisabled using info from VisualStateChangedEventArgs.NewState.Name and IsEnabled properties
@StephenLPeters @teaP FYI
Note: TreeViewItem is also derived from ListViewItem and defines Disabled and SelectedDisabled visual states inside CommonStates group - those are probably not activated too, but at least TreeViewItem is not corrupted by disabling and reenabling.
@jevansaks FYI
Win11, WinUI2.7
P.S. It is so easy to modify the same property from different visual state groups, so unit test to check for such error in all styles defined in MUX would be very helpful.

/azp run

@eugenegff could you please post after screenshots in the PR description as well :)

@StephenLPeters

It is fixed after hover over - I suspect it is the same bug as with Buttons foreground, but need to check it further.

@StephenLPeters
Do you know what happend to the foreground color of the second tab?

ContentPresenter.Foreground is touched by both common visual states and visual state group

<VisualState.Setters>

</VisualState.Setters>

@StephenLPeters I made the same screenshots without fix from current PR - foreground of the second tab is not a regression

@StephenLPeters As I said before,

It is so easy to modify the same property from different visual state groups, so unit test to check for such error in all styles defined in MUX would be very helpful.


ref(Makefile): add auto gen packs bindata condition

@michelleN,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


use webxdc types package

[ ] needs to be tested if it still works

note that there are some ts errors with solids stuff that were there before already (on master).

Did you mean to simply rename the old file instead of deleting it?

the types package is now at @webxdc/types

superseded by #61


Drag tab outside window to create new window (ala chrome/firefox)

Description of the new feature/enhancement
I really enjoy the feature in browsers where I can easily create a new window that holds the current tab by dragging it outside the current window. It would be nice if terminal allowed the same functionality, where dragging a tab outside of the open terminal window creates a new terminal instance with the selected tab. GIF below demonstrates what I mean

@jwlodek - this looks as a duplicate of https://github.com/microsoft/terminal/issues/1256 which is handled as a part of https://github.com/microsoft/terminal/issues/5000

Sure is, thanks @Don-Vito
/dup #1256


Add link to EOS in grid storage section

Summary

Related issue :

@gwarf has the linter changed? i got errors from other pages already pushed

@gwarf has the linter changed? i got errors from other pages already pushed

I'm not sure if something changed, but the errors that are reported seems valid, so I'm fixing them, and we will merge once all is good.

So the remaining error on github.com is a known error due to their server configuration. I will enable PR preview to confirm all links/changes are fine and then we can merge.

thanks a lot!


Changes to incorporate latest version of broccoli-filter

This is done to take advantage of caching introduced in latest broccoli-filter.

:clap: Thanks for the great contribution, @msranade!
Which SemVer level should I update the npm package with, patch, minor or major? I haven't tracked the recent updates of broccoli-filter.

This change doesn't introduce any API changes so minor version bump should be fine.


Add a subtle background and border to unselected tabs in the editor

Some users have complained about unselected tabs being difficult to notice. This adds a subtle background that should make them easier to see.
It's not very noticeable, but I don't think it can be made much lighter without decreasing the contrast between the selected tab and unselected tabs too much.
Preview:

Thanks!

This happens when there are more tabs open than there is space.


[overlay] overlay module improvements

TBD:

[x] add when kwarg to support conditional actions?

will help improve: https://github.com/cloudfoundry/cf-for-k8s/blob/6c9f5cd30acbfe0644bc323da73444b9c41e4617/config-optional/remove-resource-requirements.yml -> https://gist.github.com/cppforlife/7a5f061a184e09a33f2cab2ee433795c

[ ] traverse value for merge/replace/append/insert (since they may include overlay directives) when short circuiting
[ ] change default array match matcher to not_op(all) which would result in appending?
[ ] match child defaults needs to better merge if node specific rules

node specific rules should take precedence
this ends up to be if any missing_ok/expects/when is specified on node, we should throw away defaults for that node

[ ] rename expects to expect kwarg?
[ ] docs: add table to docs describing overlay actions behaviors
[ ] docs: how to add overlay annotation on a first map item within an array item

notes from the plane: https://gist.github.com/cppforlife/f5eddb3f7dd73239144fb0c148d8f9f2

when= included in https://github.com/k14s/ytt/releases/tag/v0.28.0


Modify source time tuple so that it stays within bounds before sampling from distribution

Previously, if the sampled source_time + event_duration exceeded source_duration, the new source_time would simply be source_duration - event_duration (e.g. the last event_duration seconds of the audio file). While this is somewhat okay and unnoticeable for shorter audio files, it works poorly for longer audio files (e.g. music  stems).
Additionally if a user specifies a distribution like uniform, normal, or trunc_norm, but sets the max or the mean such that it exceeds the duration of the file, the returned sampled source_time becomes a const (of source_duration - event_time). This change makes it so that they are still sampling from the requested distribution but now within safe bounds.
The bulk of this change is in a new function called _modify_source_time in core.py.

This change is

Coverage decreased (-3.1%) to 96.885% when pulling f55fe254ff4b153e2dc142c9ecbc09477591dece on pseeth:source_time_resampling into 3c83bba96c146025119516b4e1a6f3ef7ff5bfad on justinsalamon:master.

source_time tuples should also be modified if the minimum is out of bounds as well. For lack of a better  idea, if the minimum + event_duration > source_duration, then the min is set to 0. So if both the minimum and maximum are out of bounds, then the source_time is sampled between 0 and source_duration - event_duration.
Finally for the normal and truncnorm distributions, the result can still be out of bounds if you set mean to source_duration - event_duration. In these cases, the code at the moment just falls back to the old method of simply setting source_time = source_duration - event_duration.

I'm more or less following, but it would be good to get some clarifications:
Right now, if you ask for an event_duration such that that source_time + event_duration > source_duration, source_time is set to source_duration - event_duration. The logic behind this is as follows:

event_duration always takes top priority. I.e. we always try to accommodate the user specified event duration, even at the cost of modifying source_time.
If source_time is too large to satisfy event_duration, we move it backwards in time under the assumption that we want to keep the modified source_time as close as possible to the specified source_time.
If source_duration - event_duration is negative, it means there is no way to satisfy event_duration. Only in this case do we set source_time to 0 and event_duration to source_duration.

If I understanding correctly, the problem you are encountering is that under the current implementation, you often end up with the same source_time = source_duration - event_duration which is undesired.
As such, what you are proposing is to first calculate the valid range for source_time such that event_time is respected, and then sample from this valid range. That is, first compute the valid range and then sample, instead of first sampling and then checking if the result is valid.
Is this correct?

@pseeth I had a quick look at your changes and I think they're fine, but it seems to me like there's a bigger discussion to be had first about the behavior on scaper when faced with a combination of event_duration, source_time and source_duration that can't be satisfied.
Right now the behavior is:

Prioritize event_duration, at the cost of source_time

But, other options are possible, such as:
2. Prioritize source_time, at the cost of event_duration.
My inclination is to stick with (1), but I wanted to run it by you first.
A related issue is how we prioritize event_time versus event_duration. Right now event_duration is prioritized such that if event_time + event_duration > soundscape_duration, event_time get modified to soundscape_duration - event_duration.  But I wonder if that's the right play here? Perhaps it would make more sense to prioritize event_time over event_duration? This would mean the event_time would be chosen sampled from the specified distribution, no issues, and then if it ends up going over the soundscape duration it would just be trimmed. Thoughts?
Would like to get your take on these 2 issues:

event_duration vs source_time
event_duration vs soundscape_duration.

My inclination with (1) is to keep it as is right now, i.e. prioritize event_duration. I'm less clear about (2).

Hey @justinsalamon, yeah your initial comment  was correct and that's how I've implemented it. The reasoning is that I don't know (or particularly care) the lengths of all of the audio files in my dataset. The more important thing (at least for my purposes) is that what is generated by Scaper is sufficiently random while still sampling from all the possible data. I agree that event_duration should be prioritized over source_time. I think prioritizing event_time over event_duration could result in clipped or cut-off audio towards the end of soundscapes.

Just wanted to elaborate slightly.
Say a user requests ('uniform', 0, 300) for source_time. The source audio files are all of varying length, some are around 10 seconds and some are around 300 seconds and some exceed 300 seconds. Say the requested event duration is 1 second. Here's what currently happens:

10 second source file. The source time is sampled from (0, 300) uniformly, but the probability of getting 10 - 1 = 9 for the start time outweighs any other start time as when sampling from (0,300), getting a number in (10, 300) results in that happening. I think it's reasonable to assume that the user is valuing the distribution over source_time (e.g. they want to draw uniformly from each audio file).
300 second source file, the current behavior is unchanged.

300 second source file, the current behavior is unchanged.

If a user knows the duration of all of their source files, they can fix it on their end when making an event.

I think prioritizing event_time over event_duration could result in clipped or cut-off audio towards the end of soundscapes.

It definitely would.
Basically there's no way to satisfy both the desired distribution of start times and the desired distribution of event durations because the end of the soundscape forces you to prioritize one over the other: either respect event durations (as it is now) at the expense of the start time distribution, or prioritize the distribution of start times at the cost of even durations, as some events will get clipped if they're toward the end of soundscape.
If you think it makes sense to keep the current priorities (event duration > event time) I'm fine with that.

Made some edits if you can review @justinsalamon. I added a test case for _ensure_valid_source_time_tuple_bounds (a name I just picked, easy to change if you have objections!). I used your review to make the test case, hopefully it's doing what we want now!

@pseeth let's be sure to discuss "open questions" (e.g. naming functions) before they're implemented to avoid redundant code review cycles :)

Will do. For some reason, can't comment directly but the list(set(source_times)) fix isn't as straightforward as I thought. Picture that a user wants to actually weight the draw and puts in [0, 0, 2, 2, 2, 10] or something, to give a 3/5s chance of getting 2 and a 2/5s chance of getting 0, and then 10 would be out of bounds, say. The set solution would get rid of this and not warn them.

Had a bit of time so I just went ahead and addressed the comments. Instead of using list(set(...)), I wrote something that instead prevents duplicate times being added for out of bounds items in choose. Also renamed the function as requested.

Instead of using list(set(...)), I wrote something that instead prevents duplicate times being added for out of bounds items in choose.

This workaround has an issue: say the user wants to weight the list as you say, and they provide [0, 1, 2, 3, 3, 3] but the value 3 is out of bounds. Then all the 3s would get adjusted but duplicates would be removed, so now the bias towards 3 is gone. Worse still, you end up with mixed semantics where values below the upper boundary can have duplicates and values above it cannot.
I think it might be cleaner to just specify that any duplicates in "choose" will be automatically removed (and we move the duplicate removal code somewhere upstream) such that all values are sampled uniformly. We could then, if there's need for it, introduce a new distribution tuple (e.g. "discrete") where the user can provide a discrete list of values and corresponding weights (e.g. [("a", 1), ("b", 1), ("c", 10)]).

For example we could change https://github.com/justinsalamon/scaper/blob/master/scaper/core.py#L27 from:
"choose": lambda x: random.choice(x),
to:
"choose": lambda x: random.choice(np.unique(x)),

Bump, if you have time, @justinsalamon.


Improvements to analysis server closing labels

@bwilkerson Here's some tweaks to the closing labels as a result of testing on a larger codebase, inc:

Fix misleading comment after moving the _compareLabels method to unit tests (it takes arguments now instead of using class variables)
Track the ending line of closing labels and include labels that would normally be filtered (only spanning 1-2 lines) if they end on the same line as another label (> 2 lines)
Revert line checking to use argument lists node instead of invocation node to avoid showing labels on expressions that span multiple lines when the arguments are only on 1-2 (and apply same to constructors)
Don't show closing labels for code inside interpolated strings

Depending on feedback, we might want to tweak some of these (eg. I think 2 is a good improvement, but haven't had much feedback yet) but I think these generally improve what's there so far.
I don't know whether the way I'm handling the grouping of lines (using a map with a new private class to add the line number) or interpolated strings (counting nest levels) are best; I'm open to suggestions to improve them.
I don't know what the release schedule is, but it might be useful to bump the server version and get this in a dev SDK release and then let people play around with it properly (I'll need to push a Dart Code update, but that's mostly complete). WDYT?

... handling the grouping of lines ...

Seems reasonable to me. We should do some performance testing at some point, but I think the structure you have now is easy enough to maintain.

I don't know what the release schedule is ...

We'll release it as soon as we think it's ready, so it's pretty much up to us. The code will be in the next dev build, but that doesn't necessarily correspond to the update of the spec version.
I think you and I are reasonably happy with the API, but it would be worthwhile looping Alex in before we finalize it (to ensure that IntelliJ doesn't need something different). I'll send out an e-mail this morning.

@bwilkerson I've pushed changes for the things you commented on. Merging is fine by me if you're happy with it. Let me know if anything comes out of your discussion with Alex.

@bwilkerson I've run Sort members on the two test files plus the computer file (apologies - you had mentioned this, I just forgot it.. I should have an option to run during formats!).
I believe everything should've been formatted correctly (I do format-on-save) but lmk if you think anything is still wonky and I'll fix. Don't worry about refusing to merge over things some might picky; I'm more than happy to ensure my code is up to scratch (it's totally reasonable to expect you don't end up with some huge diff after making a trivial change because someone didn't format/sort correctly).

(Oops, I'll sort the merge, seems Devon made an edit because I left an unused var).

I'm a bit of a Git noob.. I merged this (since I presumed rebase would confuse discussions above, since the commits would be replaced with new IDs), but not sure if that complicates anything (it looks good on GH because it says it shows a condensed view of the merge commit). LMK if rebasing would be better and I'll redo.

@bwilkerson I had an email from a buildbot saying a build failed and I'm the only name on the blamelist...
https://build.chromium.org/p/client.dart/builders/vm-precomp-win-simarm64-1-4-be/builds/2313
I'm not totally sure I understand why it's failed.. I'm assuming it's just flakey, but if you think it's something of mine, please let me know!

There's nothing to worry about.
For future reference, I arrived at that conclusion by the following steps.

Open the build result page and look in the section titled Steps and Logfiles:.
Ignore steps and Failure reason because they rarely (never?) have information that isn't in the other steps.
The only other step that's red is test vm. It's unlikely that your code could have caused the VM to fail, but I'll look a little deeper just to be sure.
Click on stdio (under test vm) to open the log file and scroll to the end.
Look for a section labeled === Failure summary:.
Under that there are two sections that start like this:

FAILED: precompiler-dart_precompiled release_simarm64 language/regress_26543_2_test
Expected: Pass
Actual: Timeout

That tells me that the test took longer than normal to run for some reason. I don't believe there's anything you wrote that could have caused the VM to run slower when executing code in the set of language tests, so you're off the hook.

Great, thanks for the info 🙂


NIC dialog doesn't filter nicProfiles by permissions

Follow-up for https://github.com/oVirt/ovirt-web-ui/pull/517

see #542 for screenshot

cc @lizsurette

I'm hoping for network card to be done in 1.4.3 or 1.4.4.

Same as #738


Fix wrong filename and format

This command does not work, the processed import file always gets an ID generated and prepended to the file and needs to be specified for the import process command. Additionally, JSONL Files cannot be uploaded directly, only ZIP files are supported.
The preview didn't work for me here, so I'm not 100% sure I got it right as far as formatting is concerned, sorry.

Summary

Ticket Link

Hello @anx-ag,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.


minimum version of go not documented

At least, not in README or CONTRIBUTING, as far as I can see.
Its newer than 1.6, which doesn't have 'context', as examples/hotrod required that to build.

It's 1.7 now, I will soon upgrade to 1.9 and add to the docs.

Thank you.


Update CHANGELOG.md after recent merge

Pull Request (PR) description

Update CHANGELOG.md after recent merge

This Pull Request (PR) fixes the following issues
None
Task list

[x] Added an entry under the Unreleased section of the change log in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md.
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[ ] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #508 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #508   +/-   ##
=======================================
  Coverage   91.39%   91.39%
=======================================
  Files          17       17
  Lines        2661     2661
=======================================
  Hits         2432     2432
  Misses        229      229

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 a20eef2...8370794. Read the comment docs.

Labeling this as 'invalid' temporarily so it doesn't count against my personal hacktoberfest count. I don't want to cheat. 🙂


Activities disordered

We had ordered activities by popularity, with the exception of American Gut / GoViral / PGP as leading at the list. It looks like refactoring accidentally reorganized it so those three are at the end of the list.

now fixed :)


Pr 816 additions

This fixes up the run() documentation for PR #816

Codecov Report

Merging #818 into master will increase coverage by 2.05%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master     #818      +/-   ##
==========================================
+ Coverage   60.19%   62.24%   +2.05%
==========================================
  Files          71       71
  Lines       12108    13645    +1537
  Branches     1914     2428     +514
==========================================
+ Hits         7289     8494    +1205
- Misses       4190     4428     +238
- Partials      629      723      +94

Impacted Files
Coverage Δ

autobahn/asyncio/wamp.py
74.72% <50%> (ø)
:arrow_up:

autobahn/wamp/interfaces.py
100% <0%> (ø)
:arrow_up:

autobahn/util.py
49.78% <0%> (+0.42%)
:arrow_up:

autobahn/wamp/exception.py
96.1% <0%> (+0.79%)
:arrow_up:

autobahn/wamp/types.py
78.36% <0%> (+5.88%)
:arrow_up:

autobahn/wamp/message.py
68.46% <0%> (+5.93%)
:arrow_up:

autobahn/wamp/cryptobox.py
6.62% <0%> (+6.62%)
:arrow_up:

autobahn/wamp/protocol.py
59.67% <0%> (+7.34%)
: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 b1e3fc7...9c2aadb. Read the comment docs.

Codecov Report

Merging #818 into master will increase coverage by 2.05%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master     #818      +/-   ##
==========================================
+ Coverage   60.19%   62.24%   +2.05%
==========================================
  Files          71       71
  Lines       12108    13645    +1537
  Branches     1914     2428     +514
==========================================
+ Hits         7289     8494    +1205
- Misses       4190     4428     +238
- Partials      629      723      +94

Impacted Files
Coverage Δ

autobahn/asyncio/wamp.py
74.72% <50%> (ø)
:arrow_up:

autobahn/wamp/interfaces.py
100% <0%> (ø)
:arrow_up:

autobahn/util.py
49.78% <0%> (+0.42%)
:arrow_up:

autobahn/wamp/exception.py
96.1% <0%> (+0.79%)
:arrow_up:

autobahn/wamp/types.py
78.36% <0%> (+5.88%)
:arrow_up:

autobahn/wamp/message.py
68.46% <0%> (+5.93%)
:arrow_up:

autobahn/wamp/cryptobox.py
6.62% <0%> (+6.62%)
:arrow_up:

autobahn/wamp/protocol.py
59.67% <0%> (+7.34%)
: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 b1e3fc7...9c2aadb. Read the comment docs.


Forking an child process throws an eaddrinuse exception when in debug mode

When running an nodejs app in debug mode and i want to fork an childprocess (child_process.fork(...)), i get an eaddrinuse exception.
I guess this happens because VS tries to attach the debugger to child process on the same port, which is currently in use by the main process.

Did you try running node --debug app.js in the command line? If you get the same result, the issue is with the code or node itself.

For the sake of need-more-info, I ran into the exact same issue when forking. I also ran node --debug app.js from CMD and received the same EADDRINUSE exception. This is as simple as it gets:
app.js
var fork = require('child_process').fork;
var forked = fork('./fork.js');

setTimeout(function () {
    console.log('finished');
}, 10000);

fork.js
console.log("test");

Hi,
i run the nodejs app from visual studio in debug mode. And when the run the forked child process i get the error.
regard Michael

Still trying to understand. If this happens regardless of whether you are running ntvs... Is there a reason to believe this is ntvs-related?

Closing this as external since it appears to be a node issue, but let me know if you think otherwise.


Failing processing image - V4

Hey, i have a issue with v4 gatsby-source-prismic. When i input "gatsby develop" or "gatsby build" i see this error
Unexpected error value: "failed to process https://images.prismic.io/my-reponame/db9757c5-4ce1-46e9-8834-ead4d9cbbca8_default_a1f5f3dfbc.png?auto=compress,format\nRequestError: connect    ETIMEDOUT xxx.xxx.xx.xxx:443".
I know it is coming from beta version because when i use my current version which work with v3 prismic, everything work correctly, the error only shows while using v4 version.
Best Regards! Zilib

Hey @newadbie / Zilib,
This error displays when gatsby-source-filesystem cannot download the file in time. There are many reasons this could happen (Imgix timing out, local network issues, etc.). Note that using the Imgix fields (i.e. not localFile) will prevent this issue.
One solution may be to reduce the number of concurrent downloads gatsby-source-filesystem is performing. By default, it downloads up to 200 files at once.
Could you try setting this environment variable when running gatsby develop or gatsby build and let me know if it works?
GATSBY_CONCURRENT_DOWNLOAD=1 gatsby develop

# or

GATSBY_CONCURRENT_DOWNLOAD=1 gatsby build

This will increase the download time as it will only download one image at a time. You can adjust this number higher if you find it works for you.

I'm also getting image issues locally, but the URLs from graphwl don't seem correct...
https://images.prismic.io/juniper-studio/992354f7-58ef-4c4a-962f-494df444c922_mockup-braun.jpg%3Fauto=compress%252Cformat?ixlib=gatsbyFP&auto=compress%2Cformat&fit=max&q=50&w=116&h=77
removing the %3Fauto=compress%252Cformat before the ? seems to fix it.

Hey @jodiedoubleday, can you update to the latest gatsby-source-prismic and gatsby-plugin-prismic-previews and let me know if that's fixed?
Imgix pushed out an update to their Gatsby plugin which changed the way it processed URLs so I had to change some of the logic here.

@angeloashmore works a treat ✅

I'm also getting issues with localFile{ChildImageSharp{gatsbyImageData}}} with V4:

"Unexpected error value: "failed to process https://images.prismic.io/testelohn/cc1e4a16-7b2e-47ff-aac8-c135904ec0f3_testeheader2.png?auto=compress,format\nFailed to download https://images.prismic.io/testelohn/cc1e4a16-7b2e-47ff-aac8-c135904ec0f3_testeheader2.png?auto=compress,format after 3 attempts""

This happens with all my localFile gatsbyImage queries. Although all the error message URLs - such as the above - work fine and I had no issues with gatsby-prismic-source V3.
Currently trying to upgrade to V4 with the following:

"gatsby": "^3.10.2",
"gatsby-plugin-image": "^1.10.1",
"gatsby-plugin-prismic-previews": "^4.0.3",
"gatsby-plugin-sharp": "^3.10.2",
"gatsby-source-filesystem": "^3.10.0",
"gatsby-source-prismic": "^4.0.2",
"gatsby-transformer-sharp": "^3.10.0",

As a follow-up, I could swear I made it work once when I updated to " gatsby": "^3.11.0",. But it stopped working and I am back to the same error.  I am using macOS Big Sur and my colleague with the same OS has the same error. But my colleague using Linux can run this exact branch with no errors whatsoever! We are all using Node v16.6.0.
I did try GATSBY_CONCURRENT_DOWNLOAD=1 gatsby develop. with no success.

Workaround found! Turns out that if we use npm instead of yarn it works as expected.

That's strange! I'm glad you found a workaround!
For context, the error comes from gatsby-source-filesystem, not gatsby-source-prismic. It is, however, a result of using the localFile field within a Prismic document's Image or Link to Media field.
Are you able to open an issue in the Gatsby repository for gatsby-source-filesystem? I'm not familiar enough with the internal workings of gatsby-source-filesystem to debug the issue.

I'll look into it. But, meanwhile, I see that @jodiedoubleday used to have issues with the image path ending in (for example) ?auto=compress,format. How can I force remove it from the URL to see if it fixes the issue? Maybe it helps...

@rafalohn You can customize the Imgix URL parameters using the imageImgixParams plugin option.
See: https://prismic.io/docs/technologies/install-the-plugin-gatsby#3.-configure-the-plugin

options.imageImgixParams: Provide a default set of Imgix image transformations to your images. These options will override the default Imgix transformations set by Prismic.

If you are downloading the images locally with the localFile field, then removing auto=compress,format is okay. gatsby-transformer-sharp will compress them instead.
If you are using Imgix URLs with gatsby-plugin-image, removing auto=compress,format is not recommended since images will not be properly optimized.
It sounds like you're using localFile so you can set imageImgixParams to {} to remove all default Imgix URL parameters.

Adding imageImgixParams: {} did not remove the parameters from the URL path. I still got the same

Error: Unexpected error value: "failed to process https://images.prismic.io/testelohn/cc1e4a16-7b2e-47ff-aac8-c135904ec0f3_testeheader2.png?auto=compress,format\nFailed to download https://images.prismic.io/testelohn/cc1e4a16-7b2e-47ff-aac8-c135904ec0f3_testeheader2.png?auto=compress,format after 3 attempts"

To be clear, I have components such as
import { GatsbyImage, getImage } from "gatsby-plugin-image"
(...)
<GatsbyImage image={getImage(image.localFile)} />

using something like
import { graphql, useStaticQuery } from "gatsby"
(...)
graphql`
(...)
localFile {
  childImageSharp {
        gatsbyImageData(
          layout: FULL_WIDTH
          placeholder: BLURRED
        )
      }
    }
(...)

This works in gatsby-source-prismic V3 and now works in V4 with npm. But with yarn I got the error above.

@rafalohn I might have misremembered. Can you try imageImgixParams: { auto: undefined }? Or set auto to an empty string?
The params are basically is spread over the existing params.

Both imageImgixParams: { auto: undefined }  and imageImgixParams: { auto: "" }   kept ?auto=compress,format on my image URLs.

Thinking more about this, that makes sense. The imageImgixParams option only applies to the Imgix fields (fluid, fixed, and gatsbyImageData). Note that these are the image-level fields, not the fields within localFile.childImageSharp.
The localFile field downloads the original URL given directly from Prismic.
Should the localFile field apply the provided imageImgixParams to the locally downloaded file? Since localFile can also contain non-image files (think: a Link to Media field linked to a PDF), it would only apply to image URLs.

I guess imageImgixParams should be ignored if I am aiming for local gatsbyImageData.
I can't help the feeling that there is some sub-dependency somewhere that npm install differently than yarn and that's why one works and the other doesn't. And, since I have this problem with gatsby-source-prismic V4 but not V3, it probably is some new dependency or a newer version of a previously used one. Does that make sense? Any possible suspects?

Happy to share that today I updated to "gatsby": "^3.12.0", (and likewise to the #.12.0 for the gatsby-plugin-## family) and now I can use yarn and no longer have the

Error: Unexpected error value: "failed to process URL...

errors I had before. Looks like it is working as expected for me and my colleagues. Thank you for your support and great work @angeloashmore

That's great to hear! Sorry I wasn't able to provide more support here. I'm still not sure what the underlying issue is causing that error.
I'm going to close this issue as it sounds like using the latest version of Gatsby and its plugins will fix the issue. If it comes back, we can reopen and investigate. Thanks!


Make busty retry on "busy rn"

Make busty try one more time when she gets a timeout from openai before resorting to "busy rn"

OpenAI seems to have gotten their act together and this hardly happens anymore, so I'm just gonna close this as it would probably add needless bloat to the already chaotic LLM module. If it starts happening again we can reconsider.


How can I use RxLifecycle Without appcompact V

When I try to use RxLifecycle in my project, it always prompt error for not find appcompact-v7:23.3.0, I have a version of appcompact-v7:23.0.2, it is useless. See picture below.
If I can use RxLifecycle without import  appcompact-v7:23.3.0 ?
Thanks.

You need to update your Android SDK repositories with the latest app compat/support annotations libraries.


Workaround for gadt bug in merlin destruct

See https://github.com/janestreet/merlin-jst/pull/36 for the original bug report. This PR is not a principled fix, it's just a better user experience: report an error message (that still admits that merlin just hasn't done a very good job here) rather than a stack trace.

Closing in favor of #103


Implement Wasm SIMD absolute value instructions for x86

This adds single-instruction encodings (PABSB, PABSW, PABSD) for the Wasm SIMD absolute value instructions.

I'm not really familiar enough with the meta crate to be comfortable being the one to rubber stamp this. Maybe @bnjbvr (when he is feeling better) or @sunfishcode would be better picks?


Config allowing remote access from Portainer

Hi,
Could you please advise how to configure Sherpa in order to access Docker running on Raspi from Portainer running on another server?
For security reasons I don't want to grant full access.
Thanks for your support!

Hi @74cmonty, was there specific API commands you want to provide access to via Sherpa? The README covers implementing such commands. Was there something in the README that was misleading or confusing?


Hi, I'm not actively working on this anymore, feel free to fork it


[app] Improve Plugin Instaces Toolbar

This commit improves the toolbar for the plugin instaces page, by moving
the toolbar to a seperate component and by relecting the selected
filters in the url, so that the filter is the same if a user selects a
plugin and then goaes back to the plugin instances page.

[x] I added a CHANGELOG entry for this change.
[ ] I adjusted the corresponding documentation for this change.
[ ] I adjusted the values.yaml file and the documentation for all values.

Codecov Report

Merging #409 (715fd37) into main (1cacace) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #409   +/-   ##
=======================================
  Coverage   47.29%   47.29%
=======================================
  Files         138      138
  Lines       11443    11443
=======================================
  Hits         5412     5412
  Misses       5892     5892
  Partials      139      139

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Catch up to main

Coverage increased (+0.3%) to 93.831% when pulling b00403fa8a8ae20f01562211f080a56f0e7a08bc on master into<PHONE_NUMBER>160df2c6c0f248e9ec55a45b663288 on v3.


Adjust cursor position on new line or don't emit empty spaces

VSCode Version: Code - Insiders 1.6.0-insider (67a46126c83aac8c715d4c318fcfd18a183658bf, 2016-09-13T11:09:28.863Z)
OS Version: Darwin x64 15.6.0

Steps to Reproduce:
TypeScript code
class Test {

    test() {

    }
}

Put cursor on line 2:0
Hit enter

Initial:

User presses Enter:

Notice how cursor is at 3:0 but there are spaces in front of cursor
Natural thing is to use tab to get to proper indent location which will leave empty spaces in front:

(Users might not be aware there are extra whitespaces if they dont have renderWhitespace)
So seems like it should put cursor at the end of that whitespaces or not append whitespaces
FYI - Both Atom and Sublime - do not append whitespaces

It seems like option editor.trimAutoWhitespace should do this automatically (unless I misunderstand what this option does). As a workaround you can use command editor.action.trimTrailingWhitespace (default ctrl+k ctrl+x) to do it manually. You could also try the option files.trimTrailingWhitespace that is supposed to automatically remove trailing whitespace when writing a file.

Thanks @Bill-Stewart
I do have "editor.trimAutoWhitespace": true and it does not affect it
files.trimTrailingWhitespace and editor.action.trimTrailingWhitespace do help - but still - it seems like an issue that should be addressed

Agree, it seems editor.trimAutoWhitespace should address this, unless (as I said) I don't understand what it does.

See #8145 (https://github.com/Microsoft/vscode/issues/8145) - "The editor.trimAutoWhitespace trims automatic whitespace inserted by the editor when you press Enter or Tab."

Wow, so it should work then but it doesn't. Thanks for finding that

I just tested your use case on the Windows platform and can't reproduce it.

Please try with editor.formatOnType: true - seems like the issue is related to that

Enabled editor.formatOnType in my settings. Still can't repro.

Thanks - maybe OSX issue - would appreciate if someone could test on OSX - both insiders and stable are having this issue with editor.formatOnType: true

It appears to be caused by the format on type TS language provider.

Migrated to TS repo. https://github.com/Microsoft/TypeScript/issues/11074


Seqr BQ billing data should use prop map by usage_end_time

This is a reasonably appropriate fix for the problem, it's a max 24 hour difference, and our timing for updating analysis is basically within that tolerance.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@638a2fc). Click here to learn what that means.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #176   +/-   ##
=======================================
  Coverage        ?   88.04%
=======================================
  Files           ?        4
  Lines           ?      393
  Branches        ?        0
=======================================
  Hits            ?      346
  Misses          ?       47
  Partials        ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add .bmp image file support

Adds .bmp image support. Useful for training with uncompressed data, such as spectrograms.

yassss, text to sound!


.NET version

Can win-acme be updated to use a newer .NET version, as 7.0 is now unsupported?

This will happen in due time, probably combined with some other (minor) breaking changes in a 2.3 release.

OK great - will be important to maintain Cyber Security compliance.

@WouterTinus Considering .NET 6 is out of support soon (https://dotnet.microsoft.com/en-us/download/dotnet/6.0) and there seems to be a PR for .NET 8 (https://github.com/win-acme/win-acme/pull/2641), are we likely to see a new version soon?

Yes.

Yes.

Great, thanks.


could not find service natural-language-classifier-standard to bind to app

Hi, when I tried to cf push, then it shown failed, could not find service natural-language-classifier-standard to bind to app.
Is there anyone know this trouble? Thank you.

You need to create the service and bind it to the app. Take a look at the Getting Started section.


Update PR Template

Remove checkboxes for stylish-haskell and purty since both are being taken care off through the git pre-commit hooks (and later through CI).
@michaelpj does this make sense to you? I think if something is fully automatically taken care of then there is no need for an added manual step of clicking a checkbox in the GitHub UI?

Pre-submit checklist:

Branch

[x] Commit sequence broadly makes sense
[x] Key commits have useful messages
[x] Relevant tickets are mentioned in commit messages

PR

[x] Self-reviewed the diff
[x] Useful pull request description
[x] Reviewer requested

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

Actually @shmish111 suggested this, so i'll mention you here David :)

Not everyone will use the pre-commit hooks, I expect. Maybe we should just change the precondition to "and not using pre-commit hooks"?
TBH, since it's checked by CI I guess it's arguably redundant anyway. What I was trying to avoid was that I commonly see people having to do one cycle of "CI failed"->"oops fix formatting". But perhaps we have a better solution to that now, which is "use the pre-commit hooks!".

@michaelpj @gilligan do you want to rebase this or close it?


"Gaussian Elimination" Implementation in C++

Added an implementation for the Gaussian Elimination algorithm in C++, and encapsulating it in a C++ class so as to make it user-friendly, and used some of recent C++ features such as multi-dimensional vector to create matrix. Any advice for changes or such is appreciated.

In my second commit, I just changed it so as to make sure that the row with highest absolute pivot moves up.

Unfortunately, we have a PR for gaussian elimination in C++ (#258). I'll see what the status is on that PR and get back to you. Sorry it's taking so long.

The other pull request is closed, so this is the main one for Gaussian elimination.

I looks better now. But why is it so different from the C version? Gaussian elimination is not a complex algorithm. I expected it to be the C code with C++ features like std::vector.


Conversion between CGmodel representation and PyRosetta Pose

We were working on getting the conversion between CG PyRosetta objects (Poses) and CGOpenMM/Foldamers (CGModel). This is important for being able to compare structures and energies from both codebases.
Garrett started this process in this branch of CG PyRosetta:
https://github.com/shirtsgroup/cg_pyrosetta/tree/cgopenmm_comparison/cg_pyrosetta

The difficulty here is the moving target of the PyRosetta representation of parameters.
Structures should be easy to port over, since the Pose object stores coordinates of a model. There was a question of consistency between atom names and residue names between both codebases. This was complicated by the CG11x3 residue needed to have torsions and bond angles apply correctly to the 1-1 model.
Where ideally each 1 bead/1 backbone residue would have the names of each atom in them (say BB1 and SC1), the current representation has 3 BB and 3 SC atoms per residue. This is different than the current representation of the 1-1 model in OpenMM.
The porting over of the energy functions would also be a bit weird. CG OpenMM has all the parameters defined at the beginning of a given simulation, where the goal with CG PyRosetta is to have parameters be in files and be read in from the command line when PyRosetta is run.  Generating the correct energy parameter files for PyRosetta representation of the CGmodel seems straight forward, but would need some work.
Just my current thoughts on the matter, we can discuss more on the differences between model representations below.


Fatal error during import

Symphony: 2.7.10
PHP: 7.3.28
When I select a file to import and then click on "Next step", the following error message appears:
03.08.2021 15:16 > Warning: GenericErrorHandler 2: count(): Parameter must be an array or an object that implements Countable on line 158 of file /home/webptifvz/html/example.org/extensions/importcsv/lib/parsecsv-0.3.2/parsecsv.lib.php
03.08.2021 15:16 > Fatal Error: ErrorException 0 - count(): Parameter must be an array or an object that implements Countable on line 158 of /home/webptifvz/html/example.org/extensions/importcsv/lib/parsecsv-0.3.2/parsecsv.lib.php

The error can be solved by commenting out the line in the file parsecsv.lib.php.

@tiloschroeder errors with count() turned up in quite a few extensions. We could try and update parsecsv from 0.3.2 to current version 1.3.1, but I wonder if that might lead to other problems with the extension. The function seems to be totally different in the current version.
A quick fix for PHP 7.3+ to this line is:
	if ( count((is_countable($conditions)?$conditions:[])) > 0 ) $this->conditions = $conditions;


Add Multi-App Run for Kubernetes to the Pub/Sub Tutorial

Adding example for the Multi-App Run for Kubernetes in the v1.12 release to the Pub/Sub Tutorial
This one https://github.com/dapr/quickstarts/tree/master/tutorials/pub-sub

A potential template to use for this:
Present in tutorials/pub-sub/dapr.yaml
version: 1
apps:
  - appDirPath: ./node-subscriber
    appPort: 3000
    command: ["node", "app.js"]
    containerImage: ghcr.io/dapr/samples/pubsub-node-subscriber:latest
  - appDirPath: ./python-subscriber
    appPort: 5001
    command: ["python3", "app.py"]
    containerImage: ghcr.io/dapr/samples/pubsub-python-subscriber:latest
  - appDirPath: ./csharp-subscriber
    appPort: 5009
    command: ["dotnet", "run", "csharp-subscriber.csproj"]
    containerImage: ghcr.io/dapr/samples/pubsub-csharp-subscriber:latest
  - appDirPath: ./react-form
    appPort: 8080
    command: ["npm", "run", "start"]
    containerImage: ghcr.io/dapr/samples/pubsub-react-form:latest
    createService: true


manually import seeds for www

already imported for dev

@lukashartl please document in infrastructure repo how this would be done


FCM does not pass on data fields to Android

If the a notification message is received while the app is in the background any accompanying data payload is never passed on to the application when the user taps on the notification.

https://github.com/flutter/plugins/pull/672 seems to address that

@kroikie this has landed. Is this still an issue?

No longer an issue.

@kroikie
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/695. Any further collaboration will be done there.


add coverage

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@80aa3c6). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master      #3   +/-   ##
========================================
  Coverage          ?   0.00%
========================================
  Files             ?       1
  Lines             ?       1
  Branches          ?       0
========================================
  Hits              ?       0
  Misses            ?       1
  Partials          ?       0

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 80aa3c6...ba7815c. Read the comment docs.


Fix typo in individual-accounts-in-web-api

Fixes minor typo in aspnet/web-api/overview/security/individual-accounts-in-web-api.md.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@stannedelchev Thank you for taking the time to fix this, and congratulations on your 1st docs contribution!


Adding Integration test

Adds a test that runs the XTT handshake and ensures that current and future implementations run correctly. Fixes #34

Seeing actual tests being run (and passing) in Travis feels good!!!
Some functional comments:

The asserts should be replaced by TEST_ASSERT (or EXPECT_EQ or EXPECT_NE if you're doing == or !=) from the test-utils.h header. This is because assert only exists for DEBUG builds (if you're not building DEBUG, the entire assert, including everything in its arguments, just doesn't even exist).
Since we're making the if(BUILD_TESTING) check in the top-level CMakeLists.txt (which I think is a good idea), we can remove the same check that's being done in tests/CMakeLists.txt
Remove any headers you don't need (for example, the ../src/internal/message_utils.h in server_setup.h.
We're missing an assert after the first read_from_network on line 118 (just like the one we have for the server on line 141).
The exit(1)-checks in network_array.h should be replaced by TEST_ASSERTs, so we can get at least some context on what failed if things go wrong. For example, on line 47 (notice that we have to reverse the condition, since we're making sure it is true now):

TEST_ASSERT(network->filled >= numbytes);

Some extra checks to make:

We can compare the claimed_root_out, after xtt_handshake_client_preparse_serverattest returns, to client.roots_id:

EXPECT_EQ(client.rc, XTT_RETURN_WANT_BUILDIDCLIENTATTEST);
TEST_ASSERT(0 == memcmp(client.roots_id.data, claimed_root_out.data, sizeof(xtt_certificate_root_id));

After xtt_handshake_server_preparse_idclientattest returns, we can compare requested_client_id_out to xtt_client_id_null (since that's what we told the client to request), and claimed_group_id_out to client.gid.
The client_id (which goes into xtt_handshake_server_build_idserverfinished) should be set to something. It can be anything, doesn't matter. But then, at the end of the handshake, we can make sure that the client gets the same ID as what the server assigned it (client_id is what the server is assigning):

xtt_identity_type client_id {.data={1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16}};
....
printf("Passes all of client step 3);
xtt_identity_type assigned_id;
client.rc = xtt_get_my_identity(&assigned_id, &client.ctx);
EXPECT_EQ(XTT_RETURN_SUCCESS, client.rc);
TEST_ASSERT(0 == memcmp(assigned_id.data, client_id.data, sizeof(xtt_identity_type));

We can do a similar check, after the handshake, comparing the results of xtt_get_clients_identity to xtt_get_my_identity, and xtt_get_clients_longterm_key_ed25519 to xtt_get_my_longterm_key_ed25519. For example:

xtt_ed25519_pub_key clients_longterm_key;
server.rc = get_clients_longterm_key_ed25519(&clients_longterm_key, &server.ctx);
EXPECT_EQ(XTT_RETURN_SUCCESS, server.rc);
xtt_ed25519_pub_key my_longterm_key;
client.rc = get_my_longterm_key_ed25519(&my_longterm_key, &client.ctx);
EXPECT_EQ(XTT_RETURN_SUCCESS, client.rc);
TEST_ASSERT(0 == memcmp(my_longterm_key.data, clients_longterm_key.data, sizeof(xtt_ed25519_pub_key));

Also at the end, compare the output of xtt_get_version and xtt_get_suite_spec to the values we set at the top.
Also, at the end, run xtt_get_clients_pseudonym_lrsw and xtt_get_my_longterm_private_key_ed25519 and just check that the return codes are XTT_RETURN_SUCCESS (we don't have anything to compare those to, but it's still nice to make sure we can run them)

Some formatting/style comments:

Remove the commented-out junk that we no longer need, and any extra blank lines we don't need (for example, on line 66 in server_setup.h)
We no longer need the explicit setting of bytes_requested on lines 40 and 41, right?
I would move all the hard-coded stuff into server_setup.h and client_setup.h, even if we end up repeating (e.g. for the GPK)
I think I would also put all the contexts into the ctxhelpers.

For example, put the server_root_cert, intended_server_id, and group_ctx into the xtt_client_ctxhelper (since you're calling the corresponding initialization functions within setup_client_input, which I think is a good idea)
Similarly, the xtt_initialize_[client,server]_handshake_context should go in the setup_[client,server]_input
Similarly for the server and its cert_ctx_s and group_pub_key_ctx

Each step can go in its own function, e.g. client_step_one. Not only is that self-documenting, but it also limits the scope of any variables, so we can try to make sure we're not accidentally communicating from client-to-server other than via the fake-network

Looks great! Sorry for the delay in responding.
I've got a few more quick requests. Once you're done with these, would you rebase this branch onto the most-up-to-date master and clean-up the branch (we can talk about how to do that)?

In main, loop over suite_spec options, so we're testing all four. Something like:

client.version = XTT_VERSION_ONE;
xtt_suite_spec suite_specs[] = {XTT_X25519_LRSW_ED25519_CHACHA20POLY1305_SHA512, XTT_X25519_LRSW_ED25519_CHACHA20POLY1305_BLAKE2B, XTT_X25519_LRSW_ED25519_AES256GCM_SHA512, XTT_X25519_LRSW_ED25519_AES256GCM_BLAKE2B};
for (size_t i=0; i<sizeof(suite_specs); ++i) {
    client.suite_spec = suite_specs[i];
    setup_server_input
    ...
    handshake_checks
}

Would you remove the semicolons after the while(0)s in test-utils, the ones I mistakenly had in there?
In the check at the top of write_bytes, it's safer to check that it's <= sizeof(network->array) (just in case we change the size of that array)
Similarly, use basename_length = sizeof(basename) in client_setup.h and server_setup.h.
Why specify roots_id differently from the other hard-coded data?
The call to xtt_handshake_server_preparse_idclientattest should use &server->bytes_requested, right? Not client?

Relatedly, can server_step_two just take the client's gid as a parameter, rather than the whole client helper context? This way, we're sure we're only using what we really need from the client.

In handshake_checks, compare the version and suite_spec we get from the server context to the ones we set at the beginning.

We don't need to define a new suite_specs array if we're passing the suite_spec as a CLI param. I'd say let's just use the existing definitions of xtt_suite_spec, so the test could be run as integration_test 2 to run it using XTT_X25519_LRSW_ED25519_CHACHA20POLY1305_BLAKE2B, for example. That way, our suite_specs array in the test doesn't have to be updated if we add/delete suite_specs (but the CMakeLists.txt will, see below). This means we have to set the suite_spec like:

client.suite_spec = (xtt_suite_spec)atoi(argv[1]);

It would also be nice to dump which suite_spec we're using to stdout, just so we know. Something like printf("Using suite_spec '%d'\n", client.suite_spec);
Just make the TEST_ASSERT on line 22 TEST_ASSERT(argc == 2) since we know what it should be.
For adding multiple CTest tests, the current approach adds a test for the integration_test 0 case twice. A more-flexible approach would be to allow the add_test_case macro (actually, we should change this to a function, not a macro) to take an optional argument that it passes to the test command. Something like this (@drbild I'd be interested in your take on this):

function(add_test_case case_file test_args)
  ...
  <existing add_test_case stuff>
  ...
  if(test_args)
    foreach(test_arg ${test_args})
      add_test(NAME "${case_name}_${test_arg}"
        COMMAND "${CURRENT_TEST_BINARY_DIR}/${case_name}" ${test_arg}
      )
    endforeach()
  else()
    add_test(NAME ${case_name}
      COMMAND ${CURRENT_TEST_BINARY_DIR}/${case_name}
    )
  endif()
endfunction()

add_test_case("wrapper_sanity-test.c")
add_test_case("integration_test.c" "1;2;3;4")

Notice this also does away with the file(GLOB stuff, which should probably go away; with this approach, we'll have to manually add each new test.

Watch the spacing in test/CMakeLists.txt. It looks like some of the lines at the bottom got an extra space at the beginning of their lines.
Regarding my earlier question about setting the client->roots_id, you may want to look into C99's "compound literal" syntax (Dr. Dobbs has a good article on it here). Using that syntax, you can set the roots_id like this:

client->roots_id = (xtt_certificate_root_id){.data={0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x31}};

In this case, this is just a formatting thing, but it can make working with structs nicer.

We can remove the TODO comment in the top-level CMakeLists.txt on line 192. We're running the tests now!

Looks good! I'll merge it now.
Thanks!


Small Text update

@adamssusie : Thanks for your contribution! The author, @dlapiduz, has been notified to review your proposed change.

#sign-off


iOS add ACRTextField to bridging header

Platform
What platform is your issue or question related to? (Delete other platforms).

iOS

Author or host
Host
If you're an author, who are you sending cards to?
Version of SDK
Latest master
Issue
ACRTextField is not in the ACFramework.h file, making it inaccessible to Swift developers. We added this in our own bridging header, but wanted to bring up this issue with the team.

Thank you, I will check it out. this must have been oversight! Sorry for the trouble.

@nesalang to confirm if this is fixed or not. Thanks

closes it as the header is included.


add sync file to GA module

Add sync file for GA to persist the measurement ID

This is ready for review


Applying Swin UNETR to a new segmentation task

Hi,
Thank you for the great work and open source code!
I am trying to use the Swin UNETR for my own segmentation task consisting of T2 brain images for segmentation into 9 labels. I would like to train a Swin UNETR on my own data and then infer on my test data. I am working with the BTCV repository as it seemed to have the structure that is required for running such a training and inference.
I put my training/validation/test data in the same folder structure as is required by the decathlon dataset with a dataset.json file describing the data (imagesTr, imagesTs, labelsTr, labelsTs consisting of .nii.gz files). I then launch python main.py --data_dir DATA_DIR --json_list dataset.json --roi_x 32 --roi_y  32 --roi_z 32 --batch_size 2 and get the following error which I do not quite understand how to fix.

ValueError: Expected more than 1 spatial element when training, got input size torch.Size([8, 768, 1, 1, 1])
My data ran perfectly with nnUNet (https://github.com/MIC-DKFZ/nnUNet) for comparison, and it is to be noted that some of my nifti images have different sizes.

Hi I am not expert and just a random user of this like you -- but I was attempting something similar, so maybe this helps.
The script is adapted specifically to the BTCV dataset so it is different from nnUNet.
I can recommend you check out the BTCV tutorial.
Here it is clear, that the train_trainforms and val_transforms are adapted to the BTCV dataset.
That means you have to adapt these for your dataset specifically.
For example, I have 3d dataset with 2 channels. I changed my nifti files to have the following dimentions, (output of fslinfo):

dim1            2
dim2            512
dim3            512
dim4            175

I now remove the line
AddChanneld(keys=["image", "label"])
from
train_transforms = Compose( ...'
For my case I also did normalization beforehand and wrote my own script to check orientations are all the same, so I also removed the transforms. Of course, what you should do depends on your data. :)
Since I already have dimentions as my first channel.
After these changes, I got the expected dimensions while running the scripts on my data.
If you are in doubt what dimensions to expect, I can recommend that you download the BTCV dataset online and make a print of the tensor shapes fx under "Check data shape and visualize" in the turorial. You should then be able to deduce what the corresponding dimensions should be for your specific case.
Note that if you use the test.py script later on, this uses transforms from get_loader in data_utils.
So changes you make in your transforms during training should also be matched in the get_loader of data_utils, so you continue to load the data as expected.

Hi @davidkvcs , thanks for the question and interest of the work. The problem should be related to the patch size. The original configuration used 96x96x96 as the sub-volume for all experiments. The SwinUNETR model contains several downsampling operation. Not sure this is the best solution, but using 64 for each dimension is the minimum requirement for Training SwinUNETR. Hope this can help you re-design your data.


ECMAscript - static properties

class FakeMath {
  // `PI` is a static public property.
  static PI = 22 / 7; // Close enough.

…
Public and private static properties

Available via MDN now: https://caniuse.com/?search=javascript+static


Fix SHOW CREATE TABLE for Elasticsearch

Fixes #3385

Ready.

CI failed -- https://github.com/prestosql/presto/issues/2428 (not the last run)

CI failed -- https://github.com/prestosql/presto/issues/3474

@martint i know column handle -> metadata isn't perfect (fwiw that's also what we do in JDBC connectors)
I can revert to the previous approach, if we're OK to hide hidden properties in SHOW queries
(Ignoring unrecognized properties is not an option IMO, as it would mask bugs in metadata reporting from the connector)
-- i'd like to have agreement on this before changing the code.

Is there an example failure somewhere? The linked issue doesn't have any details, so I don't understand the discussion around properties without metadata.
In general, the connector APIs are difficult to implement efficiently. The engine asks for a table handle, so the connector will look up information about the table. It then uses the handle to ask for metadata. There are basically three choices for a connector:

Look up the information again. This has the downside of extra latency and load on the source.
Store the information in the handle.
Implement it the "right" way by doing some sort of caching. It can either do it per transaction, which is complicated to implement, or use a fixed size cache and pay the cost of extra memory (likely not a practical issue).

Is there an example failure somewhere? The linked issue doesn't have any details, so I don't understand the discussion around properties without metadata.

https://github.com/prestosql/presto/blob/1c71e2ebacb9180de2c4615296e934f6c86e5558/presto-elasticsearch/src/test/java/io/prestosql/elasticsearch/BaseElasticsearchSmokeTest.java#L105-L112

The issue here seems to be that the connector is abusing the properties map in ColumnMetadata to include properties that are not returned from Connector.getColumnProperties() -- in other words, they are not actually column properties.
We can change the private getTableMetadata method to return an internal data structure that can be converted to both ColumnHandle and ColumnMetdata.

We can change the private getTableMetadata method to return an internal data structure that can be converted to both ColumnHandle and ColumnMetdata.

That's exactly what @martint and I have come to as well.


images: FIXES change image name when updating.

Description
The current implementation is allowing to change the image name when updating an image via API, this should not be allowed as image names are refs.
This PR fixes this behavior by:

if the update image name is empty, set it to previous image name.
if the update image name is not empty and different from the previous image name return error.

FIXES: THEEDGE-2128
Type of change
What is it?

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[X] Tests update
[ ] Refactor

Checklist:

[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] I run make pre-commit to check fmt/vet/lint/test-no-fdo

/retest

@tomershinhar , this will need automation tests to be updated :smiley:

Codecov Report
Base: 51.81% // Head: 51.83% // Increases project coverage by +0.01% :tada:

Coverage data is based on head (7883cc2) compared to base (39fd4a7).
Patch coverage: 87.50% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1851      +/-   ##
==========================================
+ Coverage   51.81%   51.83%   +0.01%
==========================================
  Files          70       70
  Lines        9839     9853      +14
==========================================
+ Hits         5098     5107       +9
- Misses       4273     4277       +4
- Partials      468      469       +1

Impacted Files
Coverage Δ

pkg/services/errors.go
95.78% <0.00%> (-2.06%)
:arrow_down:

pkg/routes/images.go
63.36% <100.00%> (+0.39%)
:arrow_up:

pkg/services/images.go
32.99% <100.00%> (+0.29%)
:arrow_up:

pkg/services/devices.go
50.79% <0.00%> (-0.32%)
:arrow_down:

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

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

/retest

Many thanks @tomershinhar for updating the automation tests.

@de1987 that's what we have in this particular case , unittests + automation tests

we discussed it and we are good to go!


pkg/trace/event: fix flaky TestMaxEPSSampler

What does this PR do?
Double the max EPS delta in TestMaxEPSSampler

Motivation
Reduce flakiness in TestMaxEPSSampler - similar to https://github.com/DataDog/datadog-agent/pull/2946

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

@ahmed-mez Is this increase something that may flake in the future or it was simply not well adjusted?

It may flake in the future since the test itself is non-deterministic. I'm happy to consider alternatives!


Is there only decimal masks?

It would be nice for me, in my actual project to use mask in this SpreadSheet but i need mask 2 columns with "00000" (if i have a number the value would be "00012" or "00862", etc), but everything i searched leads to using this mask with currency values

Hi,
Sorry mask on jSuites can't make that. And in jSpreadsheet you can't use mask for this.
2 solutions possibles :

improve jSuites mask to accept this format 00000 (i think is better)
create a custom editor for show value in this format 00000

Have good day


Release @google-cloud/logging v4.5.0

This pull request was generated using releasetool.

@ofrobots so chances are this is just race conditions with the system tests, since they're getting run twice.  That having been said - we need to get this green before we ship :( Will make this a priority tomorrow.

Currently blocked on #424

Release is at https://github.com/googleapis/nodejs-logging/releases/tag/v4.5.0

The release build has started, the log can be viewed here. :sunflower:

:egg: You hatched a release! The release build finished successfully! :purple_heart:


presence: Work toward id vs. email

prep commits

Merged these prep commits.  I'm not sure slim_presence is the name we'll end up with the way to request this behavior via the API, but it'll be easy to rename once we know what we want.


Don't attempt to minify script/style tags with no content

This is more common with script tags, where most uses will reference external script files than inline scripts.
Skipping this, even when JS / CSS minification is enabled avoids the need to spin up the minification libraries entirly.
I've intentionally made the code change here, rather than where ScriptOrStyleContent is determined, as the code change was significantly smaller with the same effect.

Thanks!


Add BucketOwnerEnforced to s3_object_ownership doc

what

BucketOwnerEnforced support was added to Terraform

why

Bring the docs up to date for a great new AWS s3 feature

references

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket_ownership_controls#object_ownership
https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html
https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-s3-object-ownership-simplify-access-management-data-s3/

@mwarkentin
My apologies! I totally missed this PR and already merged in this update #127

@korenyoni no worries!


metal ip request should support metro flag

The metal ip request command supports --facility but not --metro.

Additionally, --quantity should offer better help to explain the limitations on valid address sizes.

Additionally, the Address field response is an arbitrary member of the pool. The CIDR should be returned.


No match for argument: python3-setuptools Error: Unable to find a match

i get this error
repo: using cache for: oe-repo
not found other for:
not found modules for:
not found deltainfo for:
not found updateinfo for:
oe-repo: using metadata from Mon 07 Nov 2022 04:58:03 PM UTC.
Last metadata expiration check: 0:00:04 ago on Mon 07 Nov 2022 04:58:04 PM UTC.
No module defaults found
No match for argument: python3-setuptools
Error: Unable to find a match
and my python3-setuptools_65.5.1.bb is
SUMMARY = "Easily download, build, install, upgrade, and uninstall Python packages"
HOMEPAGE = "https://github.com/pypa/setuptools"
AUTHOR = "Python Packaging Authority<EMAIL_ADDRESS>LICENSE = "MIT License (MIT)"
LIC_FILES_CHKSUM = "file://LICENSE;md5=7a7126e068206290f3fe9f8d6c713ea6"
SRC_URI = "https://files.pythonhosted.org/packages/c5/41/247814d8b7a044717164c74080725a6c8f3d2b5fc82b34bd825b617df663/setuptools-65.5.0.tar.gz"
SRC_URI[md5sum] = "9018a18990e7c16159ec3972affba76c"
SRC_URI[sha256sum] = "512e5536220e38146176efb833d4a62aa726b7bbff82cfbc8ba9eaa3996e0b17"
S = "${WORKDIR}/setuptools-65.5.0"
RDEPENDS_${PN} = ""

Hi,
what is the branch you are working on?
What are you trying to build?

dunfell

i am trying to build image for raspberry pi4 and want to to auto boot device with PyQt5 application

for PyQt5 application i need screeninfo and some other modules available in below list
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-screeninfo
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-apscheduler
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-tzlocal
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-pytz
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-sseclient
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-gcloud
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-firebase-admin
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-requests
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-charset-normalizer
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-idna
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-urllib3
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-certifi
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-api-python-client
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-httplib2
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-auth
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-cachetools
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-pyasn1-modules
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-pyasn1
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-auth-httplib2
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-api-core
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-googleapis-common-protos
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-protobuf
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-uritemplate
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-cloud-storage
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-cloud-core
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-resumable-media
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-crc32c
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-pyjwt
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-onglass
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-setuptools
"

when i try
IMAGE_INSTALL_append = " python3-screeninfo"
i get this error
No match for argument: python3-screeninfo
Error: Unable to find a match
After some research i get this point to remove this error i add  "inherit setuptools"  and i get this error
Could not inherit file classes/setuptools.bbclass
to remove this error i try to install steptools but get same error for steptools

@thomas-roos  and my local.conf file looks like this

This file is your local configuration file and is where all local user settings
are placed. The comments in this file give some guide to the options a new user
to the system might want to change but pretty much any configuration option can
be set in this file. More adventurous users can look at local.conf.extended
which contains other examples of configuration which can be placed in this file
but new users likely won't need any of them initially.

Lines starting with the '#' character are commented out and in some cases the
default values are provided as comments to show people example syntax. Enabling
the option is a question of removing the # character and making any change to the
variable as required.

Machine Selection

You need to select a specific machine to target the build with. There are a selection
of emulated machines available which can boot and run in the QEMU emulator:

#MACHINE ?= "qemuarm"
#MACHINE ?= "qemuarm64"
#MACHINE ?= "qemumips"
#MACHINE ?= "qemumips64"
#MACHINE ?= "qemuppc"
#MACHINE ?= "qemux86"
#MACHINE ?= "qemux86-64"

There are also the following hardware board target machines included for
demonstration purposes:

#MACHINE ?= "beaglebone-yocto"
#MACHINE ?= "genericx86"
#MACHINE ?= "genericx86-64"
#MACHINE ?= "edgerouter"

This sets the default machine to be qemux86-64 if no other machine is selected:
MACHINE ??= "raspberrypi4"
LICENSE_FLAGS_WHITELIST="commercial"
IMAGE_INSTALL_append = " util-linux-agetty"
IMAGE_INSTALL_append = " python3-tkinter"
IMAGE_INSTALL_append = " python3-pip"
IMAGE_INSTALL_append = " python3-pyqt5"
IMAGE_INSTALL_append = " python3-pyqt5"
IMAGE_INSTALL_append = " python3-pycrypto"
IMAGE_INSTALL_append = " python3-iniparse"
IMAGE_INSTALL_append = " python3-cryptography"
IMAGE_INSTALL_append = " python3-six"
IMAGE_INSTALL_append = " python3-setuptools"
IMAGE_INSTALL_append = " python3-click"
IMAGE_INSTALL_append = " python3-cachecontrol"
IMAGE_INSTALL_append = " python3-screeninfo"
IMAGE_FSTYPES = "tar.xz ext3 rpi-sdimg"
Where to place downloads

During a first build the system will download many different source code tarballs
from various upstream projects. This can take a while, particularly if your network
connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
can preserve this directory to speed up this part of subsequent builds. This directory
is safe to share between multiple builds on the same machine too.

The default is a downloads directory under TOPDIR which is the build directory.

#DL_DIR ?= "${TOPDIR}/downloads"

Where to place shared-state files

BitBake has the capability to accelerate builds based on previously built output.
This is done using "shared state" files which can be thought of as cache objects
and this option determines where those files are placed.

You can wipe out TMPDIR leaving this directory intact and the build would regenerate
from these files if no changes were made to the configuration. If changes were made
to the configuration, only shared state files where the state was still valid would
be used (done using checksums).

The default is a sstate-cache directory under TOPDIR.

#SSTATE_DIR ?= "${TOPDIR}/sstate-cache"

Where to place the build output

This option specifies where the bulk of the building work should be done and
where BitBake should place its temporary files and output. Keep in mind that
this includes the extraction and compilation of many applications and the toolchain
which can use Gigabytes of hard disk space.

The default is a tmp directory under TOPDIR.

#TMPDIR = "${TOPDIR}/tmp"

Default policy config

The distribution setting controls which policy settings are used as defaults.
The default value is fine for general Yocto project use, at least initially.
Ultimately when creating custom policy, people will likely end up subclassing
these defaults.

DISTRO ?= "poky"
As an example of a subclass there is a "bleeding" edge policy configuration
where many versions are set to the absolute latest code from the upstream
source control systems. This is just mentioned here as an example, its not
useful to most new users.
DISTRO ?= "poky-bleeding"

Package Management configuration

This variable lists which packaging formats to enable. Multiple package backends
can be enabled at once and the first item listed in the variable will be used
to generate the root filesystems.
Options are:
- 'package_deb' for debian style deb files
- 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
- 'package_rpm' for rpm style packages
E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
We default to rpm:
PACKAGE_CLASSES ?= "package_rpm"

SDK target architecture

This variable specifies the architecture to build SDK items for and means
you can build the SDK packages for architectures other than the machine you are
running the build on (i.e. building i686 packages on an x86_64 host).
Supported values are i686 and x86_64
#SDKMACHINE ?= "i686"

Extra image configuration defaults

The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
images. Some of these options are added to certain image types automatically. The
variable can contain the following options:
"dbg-pkgs"       - add -dbg packages for all installed packages
(adds symbol information for debugging/profiling)
"src-pkgs"       - add -src packages for all installed packages
(adds source code for debugging)
"dev-pkgs"       - add -dev packages for all installed packages
(useful if you want to develop against libs in the image)
"ptest-pkgs"     - add -ptest packages for all ptest-enabled packages
(useful if you want to run the package test suites)
"tools-sdk"      - add development tools (gcc, make, pkgconfig etc.)
"tools-debug"    - add debugging tools (gdb, strace)
"eclipse-debug"  - add Eclipse remote debugging support
"tools-profile"  - add profiling tools (oprofile, lttng, valgrind)
"tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
"debug-tweaks"   - make an image suitable for development
e.g. ssh root access has a blank password
There are other application targets that can be used here too, see
meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
We default to enabling the debugging tweaks.
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"

Additional image features

The following is a list of additional classes to use when building images which
enable extra features. Some available options which can be included in this variable
are:
- 'buildstats' collect build statistics
- 'image-mklibs' to reduce shared library files size for an image
- 'image-prelink' in order to prelink the filesystem image
NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
USER_CLASSES ?= "buildstats image-mklibs image-prelink"

Runtime testing of images

The build system can test booting virtual machine images under qemu (an emulator)
after any root filesystems are created and run tests against those images. It can also
run tests against any SDK that are built. To enable this uncomment these lines.
See classes/test{image,sdk}.bbclass for further details.
#IMAGE_CLASSES += "testimage testsdk"
#TESTIMAGE_AUTO_qemuall = "1"

Interactive shell configuration

Under certain circumstances the system may need input from you and to do this it
can launch an interactive shell. It needs to do this since the build is
multithreaded and needs to be able to handle the case where more than one parallel
process may require the user's attention. The default is iterate over the available
terminal types to find one that works.

Examples of the occasions this may happen are when resolving patches which cannot
be applied, to use the devshell or the kernel menuconfig

Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
Note: currently, Konsole support only works for KDE 3.x due to the way
newer Konsole versions behave
#OE_TERMINAL = "auto"
By default disable interactive patch resolution (tasks will just fail instead):
PATCHRESOLVE = "noop"

Disk Space Monitoring during the build

Monitor the disk space during the build. If there is less that 1GB of space or less
than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
of the build. The reason for this is that running completely out of space can corrupt
files and damages the build in ways which may not be easily recoverable.
It's necesary to monitor /tmp, if there is no space left the build will fail
with very exotic errors.
BB_DISKMON_DIRS ??= "
STOPTASKS,${TMPDIR},1G,100K
STOPTASKS,${DL_DIR},1G,100K
STOPTASKS,${SSTATE_DIR},1G,100K
STOPTASKS,/tmp,100M,100K
ABORT,${TMPDIR},100M,1K
ABORT,${DL_DIR},100M,1K
ABORT,${SSTATE_DIR},100M,1K
ABORT,/tmp,10M,1K"

Shared-state files from other locations

As mentioned above, shared state files are prebuilt cache data objects which can
used to accelerate build time. This variable can be used to configure the system
to search other mirror locations for these objects before it builds the data itself.

This can be a filesystem directory, or a remote url such as http or ftp. These
would contain the sstate-cache results from previous builds (possibly from other
machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
cache locations to check for the shared objects.
NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
at the end as shown in the examples below. This will be substituted with the
correct path within the directory structure.
#SSTATE_MIRRORS ?= "
#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n
#file://.* file:///some/local/dir/sstate/PATH"

Yocto Project SState Mirror

The Yocto Project has prebuilt artefacts available for its releases, you can enable
use of these by uncommenting the following line. This will mean the build uses
the network to check for artefacts at the start of builds, which does slow it down
equally, it will also speed up the builds by not having to build things if they are
present in the cache. It assumes you can download something faster than you can build it
which will depend on your network.

#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/all/PATH;downloadfilename=PATH"

Qemu configuration

By default native qemu will build with a builtin VNC server where graphical output can be
seen. The line below enables the SDL UI frontend too.
PACKAGECONFIG_append_pn-qemu-system-native = " sdl"
By default libsdl2-native will be built, if you want to use your host's libSDL instead of
the minimal libsdl built by libsdl2-native then uncomment the ASSUME_PROVIDED line below.
#ASSUME_PROVIDED += "libsdl2-native"
You can also enable the Gtk UI frontend, which takes somewhat longer to build, but adds
a handy set of menus for controlling the emulator.
#PACKAGECONFIG_append_pn-qemu-system-native = " gtk+"

Hash Equivalence

Enable support for automatically running a local hash equivalence server and
instruct bitbake to use a hash equivalence aware signature generator. Hash
equivalence improves reuse of sstate by detecting when a given sstate
artifact can be reused as equivalent, even if the current task hash doesn't
match the one that generated the artifact.

A shared hash equivalent server can be set with ":" format

#BB_HASHSERVE = "auto"
#BB_SIGNATURE_HANDLER = "OEEquivHash"
CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
track the version of this file when it was generated. This can safely be ignored if
this doesn't mean anything to you.
CONF_VERSION = "1"
systemd settings
DISTRO_FEATURES:append = " systemd"
VIRTUAL-RUNTIME:init_manager = "systemd"
VIRTUAL-RUNTIME:initscripts = ""
IMX_DEFAULT_DISTRO_FEATURES:append = " systemd"
enable some hardware
ENABLE_I2C = "1"
ENABLE_UART = "1"
DISABLE_SPLASH = "1"
DISABLE_RPI_BOOT_LOGO = "1"
IMAGE_INSTALL:append = " psplash"
IMAGE_FEATURES += " splash "

please share your bblayers.conf and your bitbake command

@thomas-roos
bitbake command :
source ./oe-init-build-env smartGlass/build
bitbake qt5-image
My   bblayers.conf  file
POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= "
${TOPDIR}/../../meta
${TOPDIR}/../../meta-poky
${TOPDIR}/../../meta-yocto-bsp
${TOPDIR}/../../../meta-raspberrypi
${TOPDIR}/../../../meta-openembedded/meta-oe
${TOPDIR}/../../../meta-openembedded/meta-multimedia
${TOPDIR}/../../../meta-openembedded/meta-networking
${TOPDIR}/../../../meta-openembedded/meta-python
${TOPDIR}/../../../meta-openembedded/meta-perl
${TOPDIR}/../../../meta-qt5
${TOPDIR}/../../../meta-security
${TOPDIR}/../meta-rpi
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-screeninfo
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-apscheduler
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-tzlocal
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-pytz
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-sseclient
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-gcloud
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-firebase-admin
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-requests
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-charset-normalizer
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-idna
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-urllib3
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-certifi
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-api-python-client
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-httplib2
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-auth
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-cachetools
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-pyasn1-modules
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-pyasn1
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-auth-httplib2
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-api-core
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-googleapis-common-protos
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-protobuf
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-uritemplate
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-cloud-storage
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-cloud-core
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-resumable-media
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-google-crc32c
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-pyjwt
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-onglass
/home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-setuptools
"

and setuptools.bbclass looks like this :
inherit distutils
DEPENDS += "python-setuptools-native"

When i remove " inherit setuptools " from " python3-screeninfo_0.8.1.bb " then i get this error
ERROR: qt5-image-1.0-r0 do_rootfs: No manifest generated from: python3-setuptools

and also remove from local.conf

i am not using meta-aws

ERROR: ParseError at /home/smart/Desktop/smart_glass/poky/smartGlass/sources/meta-screeninfo/recipes-devtools/python/python3-screeninfo_0.8.1.bb:16: Could not inherit file classes/setuptools.bbclass

this is the main error that we need to handle

how can i inherit      "inherit file classes/setuptools.bbclass"

Hi, sorry to say this, but this is all about meta-aws. May ask your questions here: https://www.yoctoproject.org/community/mailing-lists/ or if the problem is Raspberry Pi related here: https://github.com/agherzan/meta-raspberrypi
Btw. setuptools does not exsist in dunfell use setuptools3 -> https://git.yoctoproject.org/poky/tree/meta/classes/setuptools3.bbclass?h=dunfell
good luck!

@thomas-roos thanks for you help i get the point i need to use setuptools3