[FLINK-2480][test]add a test for Print Sink with prefix

I check the coverage of sink and add a test for sink to print with prefix.

Looks good to me.

@mxm
Thank you!
BTW:can you take a look about this PR:https://github.com/apache/flink/pull/992?
I add a new test in that PR and I`m not sure is it you need?

@HuangWHWHW
I think this test and also the class PrintSinkFunctionTest needs some more improvement. Here are a few comments:

Exception during open() should not be caught, but should fail the test. This happens at multiple points in the code.
The test contains a class that starts with a lower case letter, which is against the Java style rules.
The test as a whole extends RichSinkFunction which is not necessary and seems strange.
The mock print stream overwrites only one println() function, which makes it susceptible to changes in the sink. It is better to use a regular PrintStream that prints to a StringWriter to collect all contents.

@StephanEwen
Yes, thank you for the comments very much.
I`ll take the fix.
BTW:There are two PRs of mine that need someone to give some comments:
https://github.com/apache/flink/pull/1030
https://github.com/apache/flink/pull/992
Could you take a look?
Very sorry if it will spend your time.
Thanks a lot!

·The mock print stream overwrites only one println() function, which makes it susceptible to changes in the sink. It is better to use a regular PrintStream that prints to a StringWriter to collect all contents.·
Hi @StephanEwen
If I change this how can I get the printed message?
Since I use System.setOut(stream); to solve this before.

@StephanEwen
Hi, I take changes for all of your comments but this following:
"The mock print stream overwrites only one println() function, which makes it susceptible to changes in the sink. It is better to use a regular PrintStream that prints to a StringWriter to collect all contents."
I have no ideas to assert the print is correct.
So can you tell me in detail?
Thank you very much!

@HuangWHWHW Stephan is talking about something like this instead of the PrintStreamMock:
ByteArrayOutputStream baos = new ByteArrayOutputStream();
PrintStream captureStream = new PrintStream(baos);
PrintStream original = System.out;
System.setOut(captureStream);

System.out.println("Printing one line");
System.out.println("Another line");

System.setOut(original);
captureStream.close();

Assert.equals("Printing one line\nAnotherline\n", baos.toString());

You can see that we're using a PrintStream with a ByteArrayOutputStream here to capture the contents that are being printed to standard out.

@mxm
Much thanks!
I`ll take a fix.

@mxm @StephanEwen
Hi, I fix the PrintStream.
And if I use the ByteArrayOutputStream baos = new ByteArrayOutputStream();, it will append "\r\n" in the end of print.
Does it matter?

@mxm
@StephanEwen
Hi,I squashed commits into one but it seems that the CI doesn't run.
Any other way to do?

@mxm
Hi,
I change the "\r\n" to "\n" since it use println in PrintSinkFunction.invoke();

@HuangWHWHW You can use System.lineSeparator() to get the either \n or \r\n depending on the operating system.

Ah, smart!
Didn't notice it before.
I'll change.

@mxm
Hi, added the System.lineSeparator().

Looks good. Will merge this later on.

Many thanks for your time!

@mxm
Hi, can you see why the CI failed?
I build success in local.

The test failures are unrelated to your changes.

Ah, thank you.
I'll force push again.
Sorry for making you wait again.


Feature/relative panel

What does the pull request do?

Port of RelativePanel from
https://github.com/dotMorten/UniversalWPF
RelativePanel is a UWP panel that is becoming quite popular.
Its fully ported except for...
https://raw.githubusercontent.com/dotnet/wpf/master/src/Microsoft.DotNet.Wpf/src/System.Xaml/System/Xaml/NameReferenceConverter.cs
@kekekeks probably it can do something with XamlIL to resolve names?
TODO:

[ ] Port tests.

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Avaloniaui.net with user documentation

Breaking changes

Fixed issues

@danwalmsley to resolve names you need to get INameScope from the service provider.
Note that some names might be not registered yet when converter is called, so you need to use FindAsync and await it.
Not sure how it would work with converters though. We might need to add support for IProvideValueTarget for converters too.


feat(obstacle_cruise_planner): add velocity_threshold to outside obstacle

PR Type

New Feature

Related Links
https://github.com/autowarefoundation/autoware.universe/pull/1646

Description
Add min velocity threshold parameter for ignoring slow obstacles outside the trajectory.
This parameter is useful, for example, for filtering slow vehicles on non-priority opossite lanes.

Review Procedure
See https://github.com/autowarefoundation/autoware.universe/pull/1646

Remarks

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[ ] Code follows coding guidelines
[ ] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code follows coding guidelines
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets
[ ] Write release notes

CI Checks

Build and test for PR: Required to pass before the merge.
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

@tkimura4 Rebase please.

No obstacle stop wall for 2.0m/s object

Obstacle stop wall for 3.1m/s object


Updated guidance on web part properties with image source

Q
A

content fix?
yes

New article?
no

Related issues?
n/a

What's in this Pull Request?
Updated guidance on web part properties with image source

thx Waldek, appreciated.


When local data volume is created, VM ID should be provided

There are 2 storage types (local, shared). The type of data disk is local or shared as well (depending on the disk offering that user chooses during volume creation). When local data volume is created, it should be attached to VM.
Acceptance criteria:

Volume creation

Add a "select VM" drop-down in volume creation
If a chosen disk offering is local - choosing VM has to be required, a mandatory field
If a chosen disk offering is shared - choosing VM is not necessary, an optional field

Storage section

Remove "State:[Ready]/[Allocated]" from volume card
Add to Storage sidebar (section "General information")

"State:[Ready]/[Allocated]"
"VM name:[VM name]/[Not attached]"

Add "VM name:[VM name]/[Not attached]" to volume card

Connected feature ID: storage_disk_create, storage_card, storage_geninfo_display

@bwsw For now, we do not show VMs, to which volumes are attached, in Storage section.
Should we add a separate section to Storage details sidebar (volume tab) "VM name" where VM will be displayed? If the volume is not attached to any VM we can hide this section.

@ershovaelena @HeyRoach @tamazlykar
Ticket declined.


can't install nor uninstall

Microsoft PowerToys version
0.56.1
Running as admin

[X] Yes

Area(s) with issue?
Installer
Steps to reproduce
attempting to install powertoys results in the following:
a prompt to find 51.1's MSI installer. said installer does not exist.

followed by this message.

which ends with this:

i downloaded 51.1 and tried to install it to uninstall it again but it instantly fails with this error.
clicking cancel causes the following error:

✔ Expected Behavior
the program should install correctly with no errors. if a older version is detected, it should remove it.
❌ Actual Behavior
the installer tries to find a MSI file that doesn't exist. clicking OK causes a file not found error, clicking cancel causes the installer to fail. running the older installer causes it to instantly fail.
Other Software
windows 10 version 21H2 (build 19044.1566)

right, i think i fixed it.
here's what i did.

i ran CMD as admin, went to the folder and then extracted the MSI version older version of powertoys by adding the parameter of --extract_msi.
i then ran the msi. the "network file not found" prompt appeared. i selected the msi for the older version and selected ok.
then i clicked remove. typed in the admin password and eventually it "removed" itself.
then i reinstalled the new version of powertoys. aside from some messages about not being able to setup the task to run on startup, it ran just fine.

hope this helps.


add versions.Date

motivations
during #968, doing
- name: dcp_zoningdistricts:
   version_env_var: VERSION_PREV`

in zoningtaxlots/recipe.yml fails with
❯ python3 -m dcpy.lifecycle.builds.plan recipe --recipe-path recipe.yml
INFO:dcpy:Planning recipe from recipe.yml
INFO:dcpy:published_version_strings=['latest', '2024-05-01', '2024-04-01', '2023-12-01', '2023-10-01', '2023-08-01', '2023-07-01', '2023-06-01', '2023-05-01', '2023-04-01', '2023-02-01', '2023-01-01', '2022-12-01', '2022-11-01', '2022-10-01', '2022-09-01', '2022-08-01', '2022-07-01', '2022-06-01', '2022-05-01', '2022-04-01', '2022-03-01', '2022-02-01', '2022-01-01', '2021-11-01', '2021-10-01', '2021-09-01', '2021-08-01', '2021-07-01', '2021-06-01', '2021-05-01', '2021-04-01', '2021-03-01', '2021-02-01', '2021-01-01', '2020-12-01', '2020-11-01', '2020-10-01', '2020-09-01', '2020-08-01', '2020-06-01', '2020-05-01', '2020-04-01', '2020-03-13', '2020-03-10', '2020-03-09', '2020-03-02', '2020-03-01', '2020-02-22', '2020-02-18']
ERROR:dcpy:Error: Tried to parse version 2020-03-13 but it did not match the expected format
INFO:dcpy:previous_recipe=None
INFO:dcpy:Export envars: {'VERSION': '2024-07-01'}

this is because published versions of ZTL are not only the first day of the month, some are just normal dates like 2020-03-13. and in versions.py we don't have a model for this simpler "date" format
changes

add Date to utils.versions and add tests for it
ensure get_previous_version in connectors.edm.publishing can handle a mix of version types
improve logging

tests
PR tests passing and (using temporary changes to ZTL's recipe.yml) I ran builds.plan locally and got:

thoughts
There are risks in having both FirstOfMonth and Date. For example, if we publish a dataset on 5/1, does that mean we always publish on the first of a month?
I think we should eventually drop FirstOfMonth and either replace it with Month or use Date with a dataset-specific bump number.

We should scrap first of month, though it is the current convention for ZTL. The reason for having it as a specific type was to be able to programmatically determine the "previous" version (2024-06-01 has 2024-05-01 as prev)
But version types should definitely be fully distinguishable. I'd be happy to make a "month" version type and move to that moving forwards with ZTL. The "publish" versions are just for us anyways, but it's also a good chance to align ZTL versions with what GIS actually publishes, in general I think our "2024-06-01" gets published as "May 2024" (NOT June 2024) (link address in bytes for this version is https://s-media.nyc.gov/agencies/dcp/assets/files/zip/data-tools/bytes/nyczoningtaxlotdb_20240531.zip - not sure if that date has some sort of convention or if it just happens to have been published then)

made requested changes!
gonna hold off on scrapping FirstOfMonth fromverisons.py and first_of_month version strategy from recipes so we can make that change as part of bigger discussion about these versions, bumping them, etc.

Looks good. I do wonder about our abstraction for these date'ish version types in general... We've got Quarter, FirstOfMonth, and now Date. It seems like these are all actually just Date types, with a a different minimum duration between them. E.g. Date = 1 day FirstOfMonth = 1 month Quarter = 3 months.
So if we just treat these types as (our implementation of) Date, with a duration, we could bypass any custom sorting. Definitely a rabbit hole to go down, here.

This really does seem like the way to go longer term - all dates under the hood, with different conventions for formatting.
Main exception would be CPDB - we have "{year}{stage of ccp}".
And I guess pluto? Majors are meant to be quarterly... but aren't entirely (or necessarily)


Rename LPOT to INC, ONSAM-1443

Existing Sample Changes
Description
Fixes Issue#ONSAM-1443

Change the test env setup script, follow the python version in oneAPI.
Change for LPOT is renamed to INC in text and code.

External Dependencies
List any external dependencies created as a result of this change.
Type of change
Please delete options that are not relevant. Add a 'X' to the one that is applicable.

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Implement fixes for ONSAM Jiras

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[X] Command Line
[ ] oneapi-cli
[ ] Visual Studio
[ ] Eclipse IDE
[ ] VSCode
[ ] When compiling the compliler flag "-Wall -Wformat-security -Werror=format-security" was used

Delete this line and everything below if this is not a PR for a new code sample
Delete this line and all above it if this PR is for a new code sample
Adding a New Sample(s)
Description
Please include a description of the sample
Checklist
Administrative

[ ] Review sample design with the appropriate Domain Expert:
[ ] If you have any new dependencies/binaries, inform the oneAPI Code Samples Project Manager: @JoeOster

Code Development

[ ] Implement coding guidelines and ensure code quality. see wiki for details
[ ] Adhere to readme template
[ ] Enforce format via clang-format config file
[ ] Adhere to sample.json specification. https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-specification
[ ] Ensure/create CI test configurations for sample (ciTests field) https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-ci-test-object
[ ] Run jsonlint on sample.json to verify json syntax. www.jsonlint.com

Security and Legal

[ ] OSPDT Approval (see @JoeOster for assistance)
[ ] Compile using the following compiler flags and fix any warnings, the falgs are: "/Wall -Wformat-security -Werror=format-security"
[ ] Bandit Scans (Python only)
[ ] Virus scan

Review

[ ] Review DPC++ code with Paul Peterseon. (GitHub User: pmpeter1)
[ ] Review readme with Tom Lenth(@tomlenth) and/or Joe Oster(@JoeOster)
[ ] Tested using Dev Cloud when applicable

Include other folder code change, cancel it


Mining Stacks Guide

Introduction to Stacks mining. Running a miner (own page for this section)

Create “Mainnet” version, put in “Stacks Tokens” section
Running on testnet before running on Mainnet

Have top-level node for mining (call out testnet use case as well). Hank is the SME.

this could include machine requirements to run a miner and/or to run a full node

closing in favor of https://github.com/blockstack/docs/issues/824


multlyering is white above continents

when doing an overlay of a color contour plot (1)  and a line contour overlay (2), the area over the continents of (1) is not displayed anymore. This should be corrected.
Contour Plot (1):

Overlay Contour (2):

Multilayering Result:

This is not an issue with multilayering, but with transparency.
For some reason on your server the area over continents has the colour #FAFAFA instead of #FFFFFF, over the ocean the colour is correct.
Only #FFFFFF gets turned transparent which is why the continents aren't affected by it.

Ok, then this is maybe not in the mss code but in the server config. The overlay is defined in
(FZJ) mss-cirrus-hl@icg1318:~/INSTANCE/config/plots3.py
Does it have to do with "alpha=0.8" or with the line "countries = False" = I don't see it.

Strange, that this worked once. I will have a look.

Fixed. My bad. My "hot patch" on the server was not aligned with the "clean patch" to MSS main branch.

This was a mis-configuration of the production server.


document is null when running Jest test with Create React App

I'm running a Jest test, which is erroring out when I set state due to react-dom not finding document.  I put a log statement in react-dom and I see that document is populated initially
  console.log node_modules/react-dom/cjs/react-dom.development.js:5066
    !!!! Document {
      location: [Getter/Setter],
      _reactListenersID0002526682692260973: 0 }

but later in the test execution it's null and that's the error I encounter in my Jest test.
  console.log node_modules/react-dom/cjs/react-dom.development.js:5066
    !!!! null

Error Message:
  console.log src/containers/App.js:266
    handleError TypeError: Cannot read property 'body' of null
        at getActiveElement (/home/jc/projects/grip/grip-client/node_modules/react-dom/cjs/react-dom.development.js:5069:16)
        at getActiveElementDeep (/home/jc/projects/grip/grip-client/node_modules/react-dom/cjs/react-dom.development.js:5334:17)
        at getSelectionInformation (/home/jc/projects/grip/grip-client/node_modules/react-dom/cjs/react-dom.development.js:5366:21)
        at prepareForCommit (/home/jc/projects/grip/grip-client/node_modules/react-dom/cjs/react-dom.development.js:8689:26)
        at commitRoot (/home/jc/projects/grip/grip-client/node_modules/react-dom/cjs/react-dom.development.js:17711:3)
        at completeRoot (/home/jc/projects/grip/grip-client/node_modules/react-dom/cjs/react-dom.development.js:19239:3)
        at performWorkOnRoot (/home/jc/projects/grip/grip-client/node_modules/react-dom/cjs/react-dom.development.js:19168:9)
        at performWork (/home/jc/projects/grip/grip-client/node_modules/react-dom/cjs/react-dom.development.js:19076:7)
        at performSyncWork (/home/jc/projects/grip/grip-client/node_modules/react-dom/cjs/react-dom.development.js:19050:3)
        at requestWork (/home/jc/projects/grip/grip-client/node_modules/react-dom/cjs/react-dom.development.js:18919:5)
        at scheduleWork (/home/jc/projects/grip/grip-client/node_modules/react-dom/cjs/react-dom.development.js:18728:5)
        at Object.enqueueSetState (/home/jc/projects/grip/grip-client/node_modules/react-dom/cjs/react-dom.development.js:12456:5)
        at App.Object.<anonymous>.Component.setState (/home/jc/projects/grip/grip-client/node_modules/react/cjs/react.development.js:375:16)
        at setState (/home/jc/projects/grip/grip-client/src/containers/App.js:250:14)
        at tryCatcher (/home/jc/projects/grip/grip-client/node_modules/bluebird/js/release/util.js:16:23)
        at Promise._settlePromiseFromHandler (/home/jc/projects/grip/grip-client/node_modules/bluebird/js/release/promise.js:512:31)
        at Promise._settlePromise (/home/jc/projects/grip/grip-client/node_modules/bluebird/js/release/promise.js:569:18)
        at Promise._settlePromiseCtx (/home/jc/projects/grip/grip-client/node_modules/bluebird/js/release/promise.js:606:10)
        at _drainQueueStep (/home/jc/projects/grip/grip-client/node_modules/bluebird/js/release/async.js:142:12)
        at _drainQueue (/home/jc/projects/grip/grip-client/node_modules/bluebird/js/release/async.js:131:9)
        at Async.Object.<anonymous>.Async._drainQueues (/home/jc/projects/grip/grip-client/node_modules/bluebird/js/release/async.js:147:5)
        at Immediate.Async.drainQueues [as _onImmediate] (/home/jc/projects/grip/grip-client/node_modules/bluebird/js/release/async.js:17:14)
        at runCallback (timers.js:705:18)
        at tryOnImmediate (timers.js:676:5)
        at processImmediate (timers.js:658:5)

App.test.js
import React from 'react';
import ReactDOM from 'react-dom';
import { Provider } from 'react-redux';
import { shallow, mount } from 'enzyme';
import { BrowserRouter as Router, Route } from 'react-router-dom';

import { JSDOM } from 'jsdom';

import configureStore from '../../store/configureStore';

global.Promise = require('bluebird');
const util = require('util');

jest.mock('../../actions/simulationRuns');
let App;

describe('App', () => {
  beforeEach(() => {
    // Set up some mocked out file info before each test
    App = require('../App').default;
  });

  it('renders without crashing - mount', () => {
    const div = document.createElement('div');
    ReactDOM.render(
      <Router>
        <Provider store={configureStore()}>
          <Route path="/">
            <App />
          </Route>
        </Provider>
      </Router>,
      div
    );
  });
});

setupTests.js
import { configure } from 'enzyme';
import Adapter from 'enzyme-adapter-react-16';

configure({ adapter: new Adapter() });

I also tried adding
    Object.defineProperty(document, 'currentScript', {
      value: document.createElement('script')
    });

to setupTests.js and beforeEach.

Do you have a repro? It's hard to tell what's wrong without it

@thymikee , sure, here you go: https://github.com/jcald1/grip-client/tree/feature/258.  Just need to copy .env.development to .env first.

I'm seeing this exact error as well. React Dom can't find the document in the Jest environment.

Please follow the issue template which includes asking for a reproduction

you know what's annoying when there is a valid issue that multiple people are experiencing and some dogmatic busybody comes in and squashes conversation because it doesn't abide by "the rules"...
More helpful would be some input into this. It's not always easy to reproduce bugs when you have a substantially large codebase and bad error reporting.
I will try and do that as soon as I can.
I too am experiencing this issue but am getting the following error message:
 RUNS  src/core/flow-engine.test.tsx
/home/trpgb21/develop/updated-nasu/nasu-ae/node_modules/react-dom/cjs/react-dom.development.js:302
      var evt = document.createEvent('Event'); // Keeps track of whether the user-provided callback threw an error. We
                         ^

TypeError: Cannot read property 'createEvent' of null

I had the same issuen after upgrading from node 8.10.0 to 11.5.0.

/home/trpgb21/develop/updated-nasu/nasu-ae/node_modules/react-dom/cjs/react-dom.development.js:302
var evt = document.createEvent('Event'); // Keeps track of whether the user-provided callback threw an error. We
^
TypeError: Cannot read property 'createEvent' of null

I had the same issue


Docs build broken with newest Sphinx release

Problem Description
Currently Documentation build is broken since Sphinx update 7.3.x
Sphinx PR: https://github.com/sphinx-doc/sphinx/pull/12298
Breathe issue: https://github.com/breathe-doc/breathe/issues/981
Potentially downgrade Sphinx to < 7.3.0. until issue is fixed.
master: #1541
5.13:
5.12:

We should be able to remove the restriction again.


essential mod support?

could you guys add essential mod support? or fix the way the menu works on mouse and keyboard

just use e4mc mod to play with friends without server. it's also compatible with latest java edition versions, and plus using that mod, people doesn't even have to have the mod.

@RedPCat Essential is closed source; compatibility cannot be worked on
Don't agree with it all you want; compatibility just.. cant be done because we have no source to work with
There are also better alternatives to Essential (ie: e4mc)

better alternative if you can port forward - i can port forward fine but my internets the worst in the group but im one of the only ones who can port forward on their router

Don't agree with it all you want; compatibility just.. cant be done because we have no source to work with

@FlashlightET As omo said, its the better alternative that anyone has access to. If you can't port forward you can TRY to handle with essential mod breaking things. Rather than that there's nothing to be done.

Any possibilities of this being re-opened now that Essential is open sourced?

nope, use World Host or E4MC


add docker compose and simple nginx config for it

Details
Issues
Resolves #
Testing
Documentation

Moved compose to separate folder with README


Try overlay conversion with a flat preimage file

This is a self-reminder for me to get back to this after EthCC: the current overlay method uses ReadPreimage, which we know has a heavy impact on performance since the preimages are stored in a different order than the snapshot iterates.
We have worked around this problem by dumping the images in a flat file, this method should be tried with the overlay approach as well, in order to check if the performance improves.

done, it works


added some quarter wavelength cavity designs and added floorplans to …

…some previous designs

not sure why it says all checks have failed, I manually checked all my files, the only one that has errors is from cosmetic features in ELEC413_GreyPoupon_2.oas which I didn't even modify for this pull request

Fixed error


Brace inner formatting

Description
guide:

Inside curly braces, separate tokens by single spaces, except for around the . for attribute access and the | for a filter.

This needs an extra level of parsing compared to what we're doing right now. Django does it with extra regexes, which we should copy in.

Woops, not done. #39 should have said “For”. Still need to do expressions, e.g. in {% if x == y %}.

Block tags were done in #47.
Turns out that filters there aren't allowed spaces by Django, e.g. {% if name | upper == "EGBERT" %} is not allowed anyway.


[WFCORE-6722] Standardize the error message shown when the server is launched with an valid but empty option

Hello,
This PR is fixing the following issue:
https://issues.redhat.com/browse/WFCORE-6722
It is trying to unify error messages when no value was specified for an option.

Hello, arsenalzp. I'm waiting for one of the admins to verify this patch with /ok-to-test in a comment.

/ok-to-test

@arsenalzp merged, thanks for contributing to WildFly Core!


JSON schema files are invalid

The JSON schema files are invalid and therefore need a fix.

some $refs are unknown.
e.g. #/definitions/tool in JSON schema 1.2a
some $ids are duplicate
e.g. #/properties/services in JSON schema 1.2a

as reported by https://www.json-schema-linter.com/

According to OxygenXML, IntelliJ IDEA, and https://jsonschemalint.com/, the v1.2a and 1.3 schemas are perfectly valid. CycloneDX Core Java also includes https://github.com/networknt/json-schema-validator and runs over 131 unit tests against the schemas (including JSON strict) without issues.
What I have found are large variances in support for various parts of JSON Schema.  For example, some validators do not support iri-reference whereas others do.
https://www.json-schema-linter.com/ seems to be complaining about references that are easily resolvable. For example, it complains that it cannot find the reference to organizationalEntity. It is literally here: https://github.com/CycloneDX/specification/blob/master/schema/bom-1.2.schema.json#L154
I think https://www.json-schema-linter.com/ is likely broken and its analysis should not be trusted.

yes,  https://www.json-schema-linter.com/ seams to be kind of an over-achiever. to picky.
but the issue with the duplicate ids is still relevant.
tried to solve it via #84

@jkowalleck We are currently working on v1.4 of the spec and will likely merge the PR in one it goes through the documented standardization process.

would it be possible to write a test/tool that goes trough the JSON and grabs all the $id and finds duplicates and $ids that would override existing json-pointers? this could be part of the current test suite "JsonSchemaVerificationTest".
it also should grab all the $ref and check if they exist. be aware: if a ref is not a known $id it might be a valid json-pointer.

Furthermore i would suggest to not use $id for elements that don't need one.
If the element's $id is just a "#' followed by the elment's json-pointer, then $id is not needed and should be omitted.

@stevespringett @coderpatros @DarthHater
As https://github.com/CycloneDX/specification/tree/v1.4-dev is ready for final bugfixes,
I would like to take the opportunity to come back to the topic of broken/wrong $ref and duplicate/shadowing $id.

Sounds good @jkowalleck. Can you submit a PR to the v1.4-dev branch?

BTW, the vendor of https://www.json-schema-linter.com/ has a Windows tool that has a full blown linter included, however, it's only compiled for x86 and cannot run on Windows 11 arm, which is what I'm running on Parallels.
The vendor also has an API, which I submitted the 1.4 schema to. This is what was returned:
{
 "file": {
  "path": "wwwroot/uploads/X69FN58JA34R.json",
  "done": true,
  "general": "",
  "is_schema": true,
  "schema_dtd_ref": false,
  "valid": true,
  "time": "2021-12-22T00:25:27",
  "results": [
   {
    "type": "message",
    "description": "Recursive reference #/definitions/component",
    "jsonpointerInstance": "/definitions/component/properties/pedigree/properties/ancestors/items/$ref"
   },
   {
    "type": "message",
    "description": "Recursive reference #/definitions/component",
    "jsonpointerInstance": "/definitions/component/properties/pedigree/properties/descendants/items/$ref"
   },
   {
    "type": "message",
    "description": "Recursive reference #/definitions/component",
    "jsonpointerInstance": "/definitions/component/properties/pedigree/properties/variants/items/$ref"
   },
   {
    "type": "message",
    "description": "Recursive reference #/definitions/component",
    "jsonpointerInstance": "/definitions/component/properties/components/items/$ref"
   },
   {
    "type": "warning",
    "description": "No type specified for schema level and no \"enum\" or \"default\" keyword is found.",
    "jsonpointerInstance": "/definitions/publicKey/allOf/0/if/properties/kty"
   },
   {
    "type": "warning",
    "description": "No type specified for schema level and no \"enum\" or \"default\" keyword is found.",
    "jsonpointerInstance": "/definitions/publicKey/allOf/0/if"
   },
   {
    "type": "warning",
    "description": "No type specified for schema level and no \"enum\" or \"default\" keyword is found.",
    "jsonpointerInstance": "/definitions/publicKey/allOf/0/then"
   },
   {
    "type": "warning",
    "description": "No type specified for schema level and no \"enum\" or \"default\" keyword is found.",
    "jsonpointerInstance": "/definitions/publicKey/allOf/1/if/properties/kty"
   },
   {
    "type": "warning",
    "description": "No type specified for schema level and no \"enum\" or \"default\" keyword is found.",
    "jsonpointerInstance": "/definitions/publicKey/allOf/1/if"
   },
   {
    "type": "warning",
    "description": "No type specified for schema level and no \"enum\" or \"default\" keyword is found.",
    "jsonpointerInstance": "/definitions/publicKey/allOf/1/then"
   },
   {
    "type": "warning",
    "description": "No type specified for schema level and no \"enum\" or \"default\" keyword is found.",
    "jsonpointerInstance": "/definitions/publicKey/allOf/2/if/properties/kty"
   },
   {
    "type": "warning",
    "description": "No type specified for schema level and no \"enum\" or \"default\" keyword is found.",
    "jsonpointerInstance": "/definitions/publicKey/allOf/2/if"
   },
   {
    "type": "warning",
    "description": "No type specified for schema level and no \"enum\" or \"default\" keyword is found.",
    "jsonpointerInstance": "/definitions/publicKey/allOf/2/then"
   },
   {
    "type": "message",
    "description": "Recursive reference #/definitions/service",
    "jsonpointerInstance": "/definitions/service/properties/services/items/$ref"
   },
   {
    "type": "warning",
    "description": "No type specified for schema level and no \"enum\" or \"default\" keyword is found.",
    "jsonpointerInstance": "/definitions/vulnerability/properties/references/items"
   },
   {
    "type": "warning",
    "description": "No type specified for schema level and no \"enum\" or \"default\" keyword is found.",
    "jsonpointerInstance": "/definitions/vulnerability/properties/affects/items/properties/versions/items/oneOf/0"
   },
   {
    "type": "warning",
    "description": "No type specified for schema level and no \"enum\" or \"default\" keyword is found.",
    "jsonpointerInstance": "/definitions/vulnerability/properties/affects/items/properties/versions/items/oneOf/1"
   },
   {
    "type": "message",
    "description": "Definition never used in local schema.",
    "jsonpointerInstance": "/definitions/range"
   }
  ]
 }
}

Sounds good @jkowalleck. Can you submit a PR to the v1.4-dev branch?

working on it.

@stevespringett my original finding of duplicate ids was with a json schema validator i intended to use,
that found the CDX json schema invalid. it was https://opis.io/json-schema/2.x/php-validator.html
just for completeness, i've added a test setup to reproduce my initial findings:
https://github.com/jkowalleck/specification/tree/schema-lint-opis/_TESTS/schema-lint-opis
not sure if we like a php test for the schema, but, well, here it is ....

Thanks @jkowalleck for the tests. They've been incorporated into the specification repo.
The issues with 1.4 schema have been resolved. However, I'm not in favor of modifying the existing 1.2 and 1.3 schemas. The correct thing to do would be to version them, which would end up being 1.2b and 1.3a. Given the fact this is so close to the release of v1.4, I'm on the fence about performing updates to older specs. @coderpatros, @DarthHater : what are your thoughts?

my changes to 1,2 and 1,3 do not change content. they do not change values. it is just another form of writing the same content, the correct one.
everything that was available as #/foo/bar is still available with the exact name.

most ids were shadowing themselfs.
one id was not shadowing itself - so i kept it as is
the duplicates i removed were identical duplicates - the content of one of the identical twins stayed untouched -  one id stayed so access is still possible.

things i found lately, that i'd love to change in v1.4 JSON schema

add php json schema linter to gh-workflow
remove properties/vulnerabilities.$id - it shadows itself
remove properties/signature.$id - it shadows itself

will prepare a PR for this, targeting v4-dev branch

@jkowalleck I had to revert your changes. They broke the JSON Schema documentation generator resulting in an endless loop. I will add the docgen to the GH Action so you'll know when something breaks.

ow, what is this JSON Schema documentation generator that broke, @stevespringett ?
give me a hint what was reverted and when the generator is in place, so i can PR the changes and see if the generator breaks and if it can be fixed.

Reverted in 36fcc240f3b16583cc05cf8f168b5a1591b52088
The Maven action has been updates to include JSON and XML schema doc generation and the action has been renamed CI Build.
At the conclusion of the build, there will be two artifacts that are saved with the build. One for JSON doc, the other for XML docs.

i found https://github.com/CycloneDX/specification/commit/4d3184295dc8ae6be5fb7a53caa11a9ea43de0e2
and https://github.com/CycloneDX/specification/commit/33d9445d25e043fe3b70e5c472515fca6e5f94d9
reverted in https://github.com/CycloneDX/specification/commits/v1.4-dev
this were the ones where duplicate and selfshadowing $id were removed.
will prepare them again. hopefully the doc-tools will pick them up.
if the doc tools dont, then they are not good. :-/

found the issue.  working on a fix.
FYI: JSON schema doc tool is capable of recursions - it writes "Same definition as ..." and links to it.


The PAGE CRASHES when you add I18nProviderClient and write in input control

Describe the bug
When you interact with an input in a client component wrapped by an I18nProviderClient before the dictionary has finished loading, the page crashes
To Reproduce
Steps to reproduce the behavior:
Use the project in codesandbox that provides the documentation, add an input control in the client component
https://codesandbox.io/p/sandbox/jovial-paper-skkprk?file=%2Fapp%2F%5Blocale%5D%2Fpage.tsx%3A1%2C1
1.- add <input autoFocus /> to the client component
2.- Reload the page and write immediately
Expected behavior
the page should not crash.
Screenshots

About (please complete the following information):

next-international version 1.1.3
Next.js version 14 and 13.5

Additional context
If you wait for the dictionary to finish loading completely, everything works perfectly.

🤯 I have no idea where this is coming from. Might not even be related to next-international, but Next.js / React itself?

I think that if it has to do with next-international, if you do not wrap the components with the I18nProviderClient the page will not crash 😢

Even it's not great, you can use :
    {
      en: async () => {
        await new Promise(resolve => setTimeout(resolve, 100));
        return import('./en');
      },
      fr: async () => {
        await new Promise(resolve => setTimeout(resolve, 100));
        return import('./fr');
      },
    },
``` in `locales/client.ts`

Even it's not great, you can use :
    {
      en: async () => {
        await new Promise(resolve => setTimeout(resolve, 100));
        return import('./en');
      },
      fr: async () => {
        await new Promise(resolve => setTimeout(resolve, 100));
        return import('./fr');
      },
    },

in locales/client.ts

This change works to not block the page, but the javascript that loads later is blocked

The use hook seems to crash the browser (cf. https://github.com/QuiiBz/next-international/blob/main/packages/next-international/src/app/client/create-i18n-provider-client.tsx#L35) if we interact with the page before the locale is loaded
I tried to remove it and use it in a useMemo hook to call but I've an error despite this (from the React doc, https://react.dev/reference/react/use#caveats)

The use Hook must be called inside a Component or a Hook.

Thanks for the investigation @Yovach, I'll take a look this weekend. But this is honestly a very strange behavior...

If you want to reproduce it easily:

add a <input autoFocus/> in a Client Component that calls useI18n
hold a key like A on your keyboard
click on the refresh button
Then, your CPU should get 100% of usage (wtf?)


[BUG]: Have stable diffifusion model train support tensor or pipeline parallel?

🐛 Describe the bug
when I read colosalAI parallel doc，it say：

we need modify torch.nn.Linear to col_nn.Linear. But In stable diffusion model code, I found model use torch.nn.Linear now

So have stable diffusion model train supported tensor or pipeline parallel now?
Environment
No response

No, our implementation now only supports ZeRO3 or GeminiDDP.


gnome3.mutter: 3.36.4 -> 3.36.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for gnome3.mutter is: "A window manager for GNOME"
meta.homepage for gnome3.mutter is: "https://gitlab.gnome.org/GNOME/mutter"
meta.changelog for gnome3.mutter is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 3.36.5 with grep in /nix/store/j7j4gaj1hll48w9np946in2x6vz8h3h8-mutter-3.36.5

directory tree listing: https://gist.github.com/a9e96576c1991121932d0dc1115eaa6b

du listing: https://gist.github.com/d051a41970ae4e382f0c222116d67fae

Rebuild report (if merged into master) (click to expand)

52 total rebuild path(s)

18 package rebuild(s)

18 x86_64-linux rebuild(s)
17 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
17 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
adapta-gtk-theme
chrome-gnome-shell
gnome3.gnome-control-center
gnome3.gnome-session
gnome3.gnome-shell
gnome3.gnome-terminal
gnome3.gnome-tweak-tool
gnome3.gnome-tweaks
gnome3.gnome_control_center
gnome3.gnome_session
gnome3.gnome_shell
gnome3.gnome_terminal
gnome3.gpaste
gnome3.mutter
gnome3.pomodoro
gnomeExtensions.gsconnect
gnomeExtensions.system-monitor
pantheon.elementary-session-settings

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/j7j4gaj1hll48w9np946in2x6vz8h3h8-mutter-3.36.5 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gnome3.mutter https://github.com/r-ryantm/nixpkgs/archive/31c71dd805dfd7d5926eb2db0577487c59df2291.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/j7j4gaj1hll48w9np946in2x6vz8h3h8-mutter-3.36.5
ls -la /nix/store/j7j4gaj1hll48w9np946in2x6vz8h3h8-mutter-3.36.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

13 packages built:

adapta-gtk-theme
chrome-gnome-shell
gnome3.gnome-control-center
gnome3.gnome-session
gnome3.gnome-shell
gnome3.gnome-terminal
gnome3.gnome-tweak-tool
gnome3.gpaste
gnome3.mutter
gnome3.pomodoro
gnomeExtensions.gsconnect
gnomeExtensions.system-monitor
pantheon.elementary-session-settings

Maintainer pings
cc @hedning @jtojnar @worldofpeace @dasj19 for testing.

@GrahamcOfBorg build gnome3 gnome3-xorg

Test failed but it is not clear to me why. Trying again.
@GrahamcOfBorg test gnome3

Maybe we need to update gnome-shell as well... there is a release ready for that package as well... I'll do a separate PR for that.

The test succeeded now so merging.

The test seems to be blocking unstable channel now, even though it passed here.
https://hydra.nixos.org/build/125573530
I can also reproduce the failure locally using nix-build -A nixosTests.gnome3. And when I revert 496818, it seems to work again. Consistently.
I tried bisecting mutter itself but it does not seem to make much sense:
# bad: [7d061a06dec02278bef1054e502cae8837c39f2f] Bump version to 3.36.5
# good: [d03deb006c4154232ee257a8a16fee4ea61f3286] Bump version to 3.36.4
git bisect start '3.36.5' '3.36.4'
# bad: [ef3dac70648196de8e291708eaa1cf68dc2eec28] Update Brazilian Portuguese translation
git bisect bad ef3dac70648196de8e291708eaa1cf68dc2eec28
# bad: [2d899596e21d43ab241d0ba37c0a9f90c2e610be] screen-cast/src: Make record functions return an error when failing
git bisect bad 2d899596e21d43ab241d0ba37c0a9f90c2e610be
# bad: [b1d45820efc5c9136f12d8a3b97a573a2eede9e7] screen-cast/window-stream-src: Fix indentation
git bisect bad b1d45820efc5c9136f12d8a3b97a573a2eede9e7
# bad: [d07335cd4ca094d790eac75e75cff01a28fda827] screen-cast-src: Make the two record vfuncs more similarly named
git bisect bad d07335cd4ca094d790eac75e75cff01a28fda827
# first bad commit: [d07335cd4ca094d790eac75e75cff01a28fda827] screen-cast-src: Make the two record vfuncs more similarly named

Tried reverting it on master but it does not seem to fix it there :confused:

I am now consistently getting the Failed to parse arguments: Cannot open display error even on channels/nixos-unstable :scream_cat:

The test is probably just a bit flaky (IIRC that's been an issue a while). Tested on channels/nixos-unstable and have gotten failures and success.
The failure on hydra indicates that the dbus session might not be up yet? We probably need a better way to wait for gnome-shell to be properly set up.
Doing some digging now.

The failure on hydra indicates that the dbus session might not be up yet? We probably need a better way to wait for gnome-shell to be properly set up.

Yep, that is entirely the problem. The only thing better would be to actually extend the testing driver.


bug(mat-chip): overflow of container element

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
Mat-Chips overflow it's containing block:

Reproduction
StackBlitz link: https://stackblitz.com/edit/qw8gjm?file=src%2Fexample%2Fchips-overview-example.html
Expected Behavior
The accent fish chip should be either:

shown with clipped ellipsis style
wrap overflowing text content to next line

Actual Behavior
The accent fish chip overflows/breaks the containing block.
Environment

Angular:17.3.1
CDK/Material: 17.3.1
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows

Duplicate of https://github.com/angular/components/issues/26584.


u-boot-ts: Integrate SPI delay patch for TS4900

connect https://github.com/resin-os/resinos/issues/91

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@agherzan @floion


Add filesystem lock indicator component

Use :focus-within pseudo-class to show a popover.

This change is

Reviewed 3 of 4 files at r1, 1 of 1 files at r2.
Reviewable status: all files reviewed, 4 unresolved discussions (waiting on @ip1981 and @jgrund)

iml-gui/crate/src/components/lock_indicator.rs, line 15 at r2 (raw file):
Previously, jgrund (Joe Grund) wrote…
I'd rename also lcks to locks:
if let Some(locks) = locks.get(&x.composite_id().to_string()) { ... }

There is no need to mangle the name since the only inner locks is used inside if body.
The similar code seems to be used in std, e.g. https://github.com/rust-lang/rust/blob/master/src/librustc/traits/select.rs#L2850-L2859

No, in that code there are simple ifs, not if letss. But I renamed to all_locks and locks :)

It seems you find shadowing to be dangerous

I don't like my mental cache reset ;)


Windows VM VMSS issues with CNI

Is this a request for help?: Help
What version of acs-engine?:  master - commit 28eb1d106e17281eab2753464a60ceafa1b85ea1

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
k8s - 1.10.2
What happened:
For the most part the Windows VMSS seem to work, the kublet comes up it starts, it even registers with the master as healthy, however it seems as though there is something wrong with the CNI and how it gets installed or configured. I have tried nuking all of the nodes and bringing up new with the scale set to try to somehow redeploy, but the kubelet does not seem happy with the CNI nor am I able to get any windows containers to standup on the nodes. I am using whatever the default network plugin is I do not modify that at all so this is all standard CNI for ACS-Engine deploy on windows.
What you expected to happen:
What I expected to happen was to start my pod and get a Windows SQL container running (running sql:1709)
How to reproduce it (as minimally and precisely as possible):
{
    "apiVersion": "vlabs",
    "properties": {
      "orchestratorProfile": {
        "orchestratorType": "Kubernetes",
        "orchestratorRelease": "1.10",
        "kubernetesConfig": {
          "enableRbac": true,
          "apiServerConfig" : {
            "--feature-gates": "HyperVContainer=true"
          },
          "kubeletConfig" : {
            "--feature-gates": "HyperVContainer=true"
           }
        }
      },
      "aadProfile": {
        "serverAppID":  "",
        "clientAppID":  "",
        "tenantID":  "",
        "adminGroupID":  ""
      },
      "masterProfile": {
        "count": 1,
        "dnsPrefix": "ebk8s",
        "vmSize": "Standard_F2s_v2"
      },
      "agentPoolProfiles": [
        {
          "name": "linuxpool1",
          "count": 2,
          "vmSize": "Standard_F4s_v2",
          "availabilityProfile": "VirtualMachineScaleSets",
          "storageProfile": "ManagedDisks",
          "OSDiskSizeGB": 256
        },
        {
          "name": "windowspool2",
          "count": 2,
          "vmSize": "Standard_F4s_v2",
          "availabilityProfile": "VirtualMachineScaleSets",
          "storageProfile": "ManagedDisks",
          "OSDiskSizeGB": 256,
          "osType": "Windows"
        }
      ],
      "windowsProfile": {
        "adminUsername": "",
        "adminPassword": ""      },
      "linuxProfile": {
        "adminUsername": "",
        "ssh": {
          "publicKeys": [
            {
              "keyData":  ""
            }
          ]
        }
      },
      "servicePrincipalProfile": {
        "clientId":  "",
        "secret":  ""
      }
    }
  }

Anything else we need to know:
some logs from my kubelet to help
goroutine 1 [running]:
visualstudio.com/containernetworking/cni/cni.(*NetworkConfig).GetNetworkInfo(0xc042046140, 0x29)
	/home/madhanm/repo/gopath/src/visualstudio.com/containernetworking/cni/cni/cni.go:175 +0x70e
visualstudio.com/containernetworking/cni/cni/network.(*netPlugin).Add(0xc042002540, 0xc042080070, 0x1, 0x0)
	/home/madhanm/repo/gopath/src/visualstudio.com/containernetworking/cni/cni/network/network.go:108 +0x35b
visualstudio.com/containernetworking/cni/cni.(PluginApi).Add-fm(0xc042080070, 0xc04201fbc8, 0x5)
	/home/madhanm/repo/gopath/src/visualstudio.com/containernetworking/cni/cni/plugin.go:49 +0x40
github.com/containernetworking/cni/pkg/skel.(*dispatcher).checkVersionAndCall(0xc042036280, 0xc042080070, 0x6311a0, 0xc0420b01e0, 0xc04205fe78, 0x0, 0x41055f)
	/home/madhanm/repo/gopath/src/github.com/containernetworking/cni/pkg/skel/skel.go:162 +0x1a6
github.com/containernetworking/cni/pkg/skel.(*dispatcher).pluginMain(0xc042036280, 0xc04205fe78, 0xc04205fe90, 0x6311a0, 0xc0420b01e0, 0xc0420b01e0)
	/home/madhanm/repo/gopath/src/github.com/containernetworking/cni/pkg/skel/skel.go:173 +0x2a9
github.com/containernetworking/cni/pkg/skel.PluginMainWithError(0xc04205fe78, 0xc04205fe90, 0x6311a0, 0xc0420b01e0, 0xc0420b01e0)
	/home/madhanm/repo/gopath/src/github.com/containernetworking/cni/pkg/skel/skel.go:210 +0xf4
visualstudio.com/containernetworking/cni/cni.(*Plugin).Execute(0xc042004038, 0x631520, 0xc042002540, 0x0, 0xc042071c20)
	/home/madhanm/repo/gopath/src/visualstudio.com/containernetworking/cni/cni/plugin.go:49 +0xf9
main.main()
	/home/madhanm/repo/gopath/src/visualstudio.com/containernetworking/cni/cni/network/plugin/main.go:43 +0x35c
E0510 15:54:30.397865    4684 cni.go:259] Error adding network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
E0510 15:54:30.397865    4684 cni.go:227] Error while adding to cni network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
E0510 15:54:30.744409    4684 remote_runtime.go:92] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "msftdb_default" network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
E0510 15:54:30.744409    4684 kuberuntime_sandbox.go:54] CreatePodSandbox for pod "msftdb_default(cdf7e940-5466-11e8-b6dc-000d3a066105)" failed: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "msftdb_default" network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
E0510 15:54:30.744409    4684 kuberuntime_manager.go:646] createPodSandbox for pod "msftdb_default(cdf7e940-5466-11e8-b6dc-000d3a066105)" failed: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "msftdb_default" network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
E0510 15:54:30.745431    4684 pod_workers.go:186] Error syncing pod cdf7e940-5466-11e8-b6dc-000d3a066105 ("msftdb_default(cdf7e940-5466-11e8-b6dc-000d3a066105)"), skipping: failed to "CreatePodSandbox" for "msftdb_default(cdf7e940-5466-11e8-b6dc-000d3a066105)" with CreatePodSandboxError: "CreatePodSandbox for pod \"msftdb_default(cdf7e940-5466-11e8-b6dc-000d3a066105)\" failed: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod \"msftdb_default\" network: netplugin failed but error parsing its diagnostic message \"\": unexpected end of JSON input"
I0510 15:54:31.341582    4684 kubelet.go:1901] SyncLoop (PLEG): "msftdb_default(cdf7e940-5466-11e8-b6dc-000d3a066105)", event: &pleg.PodLifecycleEvent{ID:"cdf7e940-5466-11e8-b6dc-000d3a066105", Type:"ContainerDied", Data:"5c100367f279f32adb2c862099dadc2a9c27ebae5f877940f3bde631cd158b15"}
W0510 15:54:31.341582    4684 pod_container_deletor.go:77] Container "5c100367f279f32adb2c862099dadc2a9c27ebae5f877940f3bde631cd158b15" not found in pod's containers
I0510 15:54:31.642578    4684 kuberuntime_manager.go:403] No ready sandbox for pod "msftdb_default(cdf7e940-5466-11e8-b6dc-000d3a066105)" can be found. Need to start a new one
E0510 15:54:32.460642    4684 docker_sandbox.go:657] ResolvConfPath is empty.
I0510 15:54:32.482637    4684 kubelet.go:1901] SyncLoop (PLEG): "msftdb_default(cdf7e940-5466-11e8-b6dc-000d3a066105)", event: &pleg.PodLifecycleEvent{ID:"cdf7e940-5466-11e8-b6dc-000d3a066105", Type:"ContainerStarted", Data:"8b0938b6c6be120ff58729d4020e9b3a08a1108c8dbf0851630b898dc8bf9d30"}
{"level":"debug","msg":"[cni-net] Plugin wcn-net version b9c3a1d-dirty.","time":"2018-05-10T15:54:32Z"}
{"level":"debug","msg":"[net] Network interface: {Index:13 MTU:1500 Name:vEthernet (Ethernet 3) HardwareAddr:00:0d:3a:06:6b:a2 Flags:up|broadcast|multicast} with IP addresses: [fe80::857d:1b6a:9a42:f58/64 <IP_ADDRESS>/12]","time":"2018-05-10T15:54:32Z"}
{"level":"debug","msg":"[net] Network interface: {Index:4 MTU:1500 Name:vEthernet (nat) HardwareAddr:00:15:5d:71:de:a1 Flags:up|broadcast|multicast} with IP addresses: [fe80::7574:3878:b12d:80ec/64 <IP_ADDRESS>/20]","time":"2018-05-10T15:54:32Z"}
{"level":"debug","msg":"[net] Network interface: {Index:1 MTU:-1 Name:Loopback Pseudo-Interface 1 HardwareAddr: Flags:up|loopback|multicast} with IP addresses: [::1/128 <IP_ADDRESS>/8]","time":"2018-05-10T15:54:32Z"}
{"level":"debug","msg":"[cni-net] Plugin started.","time":"2018-05-10T15:54:32Z"}
{"level":"debug","msg":"[cni-net] Processing ADD command with args {ContainerID:8b0938b6c6be120ff58729d4020e9b3a08a1108c8dbf0851630b898dc8bf9d30 Netns:none IfName:eth0 Args:IgnoreUnknown=1;K8S_POD_NAMESPACE=default;K8S_POD_NAME=msftdb;K8S_POD_INFRA_CONTAINER_ID=8b0938b6c6be120ff58729d4020e9b3a08a1108c8dbf0851630b898dc8bf9d30 Path:/opt/wincni.exe/bin;c:\\k\\cni}.","time":"2018-05-10T15:54:32Z"}
{"level":"debug","msg":"[cni-net] Read network configuration \u0026{CniVersion:0.2.0 Name:l2bridge Type:wincni.exe Ipam:{Type: Environment:azure AddrSpace: Subnet:\u003cnone\u003e Address: QueryInterval: Routes:[{Dst:{IP:\u003cnil\u003e Mask:\u003cnil\u003e} GW:<IP_ADDRESS>}]} DNS:{Nameservers:[<IP_ADDRESS>] Domain: Search:[svc.cluster.local] Options:[]} RuntimeConfig:{PortMappings:[]} AdditionalArgs:[{Name:EndpointPolicy Value:[123 34 69 120 99 101 112 116 105 111 110 76 105 115 116 34 58 91 34 49 48 46 50 52 48 46 48 46 48 47 49 50 34 44 34 49 48 46 50 52 48 46 48 46 48 47 49 50 34 93 44 34 84 121 112 101 34 58 34 79 117 116 66 111 117 110 100 78 65 84 34 125]} {Name:EndpointPolicy Value:[123 34 68 101 115 116 105 110 97 116 105 111 110 80 114 101 102 105 120 34 58 34 49 48 46 48 46 48 46 48 47 49 54 34 44 34 78 101 101 100 69 110 99 97 112 34 58 116 114 117 101 44 34 84 121 112 101 34 58 34 82 79 85 84 69 34 125]}]}.","time":"2018-05-10T15:54:32Z"}
panic: runtime error: index out of range

Invoke-HNSRequest : @{Error=The parameter is incorrect. ; Success=False}
At C:\k\hns.psm1:204 char:16
+ ...      return Invoke-HNSRequest -Method POST -Type networks -Data $Json ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorExcep
   tion
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio
   n,Invoke-HNSRequest

Also noticed this popped up when the kubelet tried to start ☝

Forgot to show pod logs
`
~ $ kubectl describe pods msftdb
Name:         msftdb
Namespace:    default
Node:         28006acs000005/<IP_ADDRESS>
Start Time:   Thu, 10 May 2018 11:28:35 -0400
Labels:       name=msftdb
Annotations:
Status:       Pending
IP:
Containers:
msftdb:
Container ID:
Image:          microsoft/mssql-server-windows-express:1709
Image ID:
Port:           1433/TCP
State:          Waiting
Reason:       ContainerCreating
Ready:          False
Restart Count:  0
Environment:
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-fghmv (ro)
Conditions:
Type           Status
Initialized    True
Ready          False
PodScheduled   True
Volumes:
default-token-fghmv:
Type:        Secret (a volume populated by a Secret)
SecretName:  default-token-fghmv
Optional:    false
QoS Class:       BestEffort
Node-Selectors:  beta.kubernetes.io/os=windows
Tolerations:
Events:
Type     Reason                  Age                From                     Message

Normal   Scheduled               7m                 default-scheduler        Successfully assigned msftdb to 28006acs000005
Normal   SuccessfulMountVolume   7m                 kubelet, 28006acs000005  MountVolume.SetUp succeeded for volume "default-token-fghmv"
Normal   SandboxChanged          6m (x12 over 7m)   kubelet, 28006acs000005  Pod sandbox changed, it will be killed and re-created.
Warning  FailedCreatePodSandBox  2m (x138 over 7m)  kubelet, 28006acs000005  Failed create pod sandbox: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "msftdb_default" network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
`
Also did see the pause image is being accessed from the master

I got the exact same issue

Seems this is a Azure CNI plugin setup issue? Could you show the cni configure file? I'm using none network policy, which runs smoothly.

I'm having incredible difficulty with CNI issues on my nodes. It seems that everything works fine for a bit, and then all of the sudden, I can't start any pods because of CNI issues.

It seems that everything works fine for a bit, and then all of the sudden, I can't start any pods because of CNI issues.

@BuairtRi  Have you done something between? Could you show the cni configure file?

+1
I'm experiencing the same behavior: at start everything works and then the internal kubernetes network isn't available from the windows node. any workaround this?

@ariellapinin Could you elaborate the Kubernetes network issues?       : No
   Autoconfiguration Enabled . . . .  : Disabled

this is version from the current master. It seems like the problem isn't related to dns, because when trying to resolve to any kubernetes network ip, I'm getting timeout

@ariellapinin Could you check whether steps at here help for your issue?

Not meeting this issue for a long time. It should have been resolved.
@beaudryj Feel free to open a new issue if you still have problems with new aks-engine.
/close


Create a new release for PyPI that captures the sql repo changes

I would like to have another tagged release before we merge in the Protobuf code. I don't have a firm date for the Protobuf code but I am hoping it can be reviewed for merge by May 13, 2016.

Completely agree @kozbo, it should be a strong priority to make a solid release before we take on the protobuf transition pain. Some points to note:

I think we should decide on our nomenclature (#1217), and improve our administration documentation (#1205, #1206) before we release. These are critical for our admin user experience.
Do we need updated ontology handling (#1147) for a new release? In either case, we need to think about the admin user experience for dealing with variant and sequence annotations, which is not entirely smooth right now.
We should think about the forward compatibility issues that we are taking on. Specifically, our planned updated ID scheme (#1119) will require new IDs to be created for all objects in the DB, as well as a schema change if we change the type from string to int (not sure if this is worth the trouble, though). We will need to create an upgrade program to help admins upgrade their DB to the new version. I don't think we can avoid this, given the strong requirement to deploy now and the need to incorporate protobuf as quickly as possible, but I thought I should raise the point so we have visibility on this issue.

Do we want to deal with the larger problem of upgrading as part of this issue? To quote @diekhans, we don't have to worry about upgrade/backwards compatibility until we get out of Alpha. That said, I think we need a thought-out plan for how we will handle it once we do get to beta.

No, I don't think we need to worry about upgrading in any formal sense, just keep this issue in the back of our minds as we're releasing.

Given the additions to the administration documentation and ontologies PR awaiting merge, is there anything else blocking a release?

No, I don't think so. Lets try and get them in and push the button!

OK, I think we're ready to tag 0.3.0 once #1236 has been merged. Over to you @kozbo, @david4096!

Ugh, just realised we need release notes... Can't tag quite yet.

@jeromekelleher Would you like me to draft up some release notes for 0.3.0?

Yes please @kozbo! We need a PR on docs/status.rst with the notes before we can tag.

Here is a documentation only PR that you may want to include as well: https://github.com/ga4gh/server/pull/1239.

Version 0.3.0 released and pushed to pypi.

Awesome @jeromekelleher


⚠ Mobitopup has degraded performance

In 09c3e8a, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 3314 ms

Resolved: Mobitopup performance has improved in e431866 after 16 minutes.


Notify of Pokémon suddenly empty

Two times i had the problem that after a restart the List of Pokemons to Notify was empty.

Happened again after Update to newest Version.
This is very annoying as it takes ages to add all filters again.

In the new Version is is even harder to add and check notification pokemons. With the numbers every pokemon takes up one line and it is only possible to see 4 lines of names.
The field should be much bigger and also have an option to copy the content so it is possible to paste a whole set of pokemons.

And empty again!!!!
The last version is broken!

It appears to be broken in 0.1.5 as well. Filter/notification preferences as well as toggles for pokestops/ scannedlocations/etc. do not save between sessions.

yeah my software auto-updated and cleared the list for me again.  It's definitely a pain to set up that list again.


Adapt catalog builder and photo processor to use the (asynch…

…ronous) kinesis handler
I used the asynchronous version of the Kinesis handler, because the two uses in this PR appear either not to depend on order or to check for itself if the event was already processed.
This closes the hello-retail part of ENG-2170, the ticket to convert all existing event consumers to use the new module, kinesis-handler.

was this deployed for the workshop today?

Excellent! Thank you, @laurwang.


Problem with alpine branch

Hi!
I use your image to install and build npm packages
docker run -it --rm -v $(pwd):/data mkenney/npm npm install --prefix /data
before switch to alpine, it works fine (currently all works with debian branch).
In alpine branch case i have error:
gyp WARN EACCES user "undefined" does not have permission to access the dev dir "/root/.node-gyp/6.2.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/data/node_modules/bufferutil/.node-gyp"
gyp ERR! build error
gyp ERR! stack Error: not found: make
gyp ERR! stack     at getNotFoundError (/usr/local/lib/node_modules/npm/node_modules/which/which.js:14:12)
gyp ERR! stack     at F (/usr/local/lib/node_modules/npm/node_modules/which/which.js:69:19)
gyp ERR! stack     at E (/usr/local/lib/node_modules/npm/node_modules/which/which.js:81:29)
gyp ERR! stack     at /usr/local/lib/node_modules/npm/node_modules/which/which.js:90:16
gyp ERR! stack     at /usr/local/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
gyp ERR! stack     at /usr/local/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:117:15)
gyp ERR! System Linux 3.13.0-83-generic
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /data/node_modules/bufferutil
gyp ERR! node -v v6.2.2
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
...
...
npm ERR! Linux 3.13.0-83-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--prefix" "/data"
npm ERR! node v6.2.2
npm ERR! npm  v3.10.8
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the bufferutil package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs bufferutil
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls bufferutil
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /src/npm-debug.log

My package.json
  "dependencies": {
    "bootstrap-less": "3.3.8",
    "flux": "3.1.0",
    "react": "15.3.2",
    "react-dom": "15.3.2",
    "react-router": "2.8.1",
    "material-ui": "0.16.1",
    "less": "2.7.1",
    "font-awesome": "4.6.3",
    "react-tap-event-plugin": "1.0.0",
    "classnames": "2.2.5",
    "query-string": "4.2.3",
    "react-paginate": "2.2.3",
    "moment": "2.14.1",
    "react-intl":"2.1.5",
    "autobahn-react":"0.3.1",
    "jwt-payload-decoder":"1.2.4",
    "react-count-to": "0.5.1",
    "mime-types": "2.1.12",
    "promise-polyfill": "6.0.2"
  },
  "devDependencies": {
    "babelify": "7.3.0",
    "browser-sync": "2.17.5",
    "browserify": "13.1.0",
    "eslint": "3.8.1",
    "nodemon": "1.11.0",
    "rework": "1.0.1",
    "rework-npm": "1.0.0",
    "rework-npm-cli": "0.1.1",
    "serve": "1.4.0",
    "uglify-js": "2.7.3",
    "watchify": "3.7.0",
    "bufferutil": "1.2.1",
    "utf-8-validate": "1.2.1"
  }

Hi @NewOldMax
The reason it fails is because the Alpine image doesn't include any build tools (gcc, make, etc.). Those are left out intentionally because they increase the image size by about 100MB, which kind of defeats the purpose of the alpine image (keeping it small).
For tools that require compilation tasks you're going to need to use the Debian image (mkenney/npm:debian), I'm not worried about that image's size and it includes build tools for various compilation tasks (node-sass, node-gyp, etc.). Let me know if that doesn't meet your needs, thanks!


Fix for #784 edge case in comment handling

The case where line_start == snippet.len() wasn't handled so we had a missing newline.
Since we can't get the next char after line_start in this case I handle the None implicitly with the match.

Thanks for the fix!


Resolve all warnings in the FVM branch.

Issue summary

Moving to FVM made a lot of code obsolete. This code should be deleted.
Other information and links

All warnings resolved!


Fix 9 Duplication issues in multiple files

CodeFactor found multiple issues last seen at 9074bb91c51dc6ba56ea2cd01fb419bc4a047ebe:
Duplicate Code
JavaScript-Files\begin_round.js:133-143
begin_round_number_two.js:132-142
begin_round_four.js:130-140
begin_round_for_3_players.js:130-140
begin_round_number_two.js:146-158
JavaScript-Files\begin_round.js:147-159
begin_round_for_3_players.js:144-156
begin_round_four.js:144-156
JavaScript-Files\begin_round.js:102-126
begin_round_number_two.js:102-126
begin_round_for_3_players.js:100-124
begin_round_four.js:100-124
JavaScript-Files\begin_round.js:165-191
begin_round_number_two.js:164-190
begin_round_four.js:162-188
begin_round_for_3_players.js:162-188
begin_round_for_3_players.js:4-35
begin_round_four.js:4-35
begin_round_number_two.js:4-35
JavaScript-Files\begin_round.js:4-35
begin_round_for_3_players.js:99-128
begin_round_number_two.js:101-131
begin_round_for_3_players.js:4-56
begin_round_four.js:4-56
begin_round_number_two.js:4-56
begin_round_for_3_players.js:143-159
begin_round_four.js:143-159
begin_round_number_two.js:145-161
begin_round_number_two.js:164-200
begin_round_for_3_players.js:162-198
begin_round_four.js:162-198

I have now fixed these bugs.


[OT] Possible improvement: PAGER function.

Sorry to bother, just a thought.
By removing the timing for the decoded DTMF string displayed on the display (the decoded DTMF string is displayed for an indefinite time until a subsequent decoding is successfully completed), it would be possible to obtain a simple PAGER function.
Doing the same thing with DTMF Decoding Response, it would be possible to obtain an advanced PAGER function.
Doing the same thing with DTMF Contact List, it would allow the sending of preconfigured PAGER messages up 8 characters max, like the Yaesu VX-3 Messages function (up 16 characters max), without losing the original DTMF Contact List functionality.

The DTMF decoder just isn't that good to be honest, it detects characters that weren't sent all the time. That's why I use a timeout on it so to remove the many erroneous detections.
Much better off using the FSK modem in the radio.

The radios do have a basic pager function in them already, although not with any message sending capability.
Receiving radio ..

Set "D DCD" to ON
Set "D RSP" to RING (or BOTH)
Set "D HOLD" to time you want on-screen msg to remain

Transmitting radio ..

Press the '*****' key to start the DTMF entry
Enter the receiving radios "ANI ID" number, ie "102"
Press the PTT to send it

The receiving radio should start to ring (beeping) and also display a 'called' message for however long "D HOLD" is set too.
It doesn't do message sending, but it does do basic paging.

Hi OneOfEleven,
thanks for your kind reply.
I agree, the DTMF decoder detects characters that were not sent all the time and so it would be much better to use the FSK modem on the radio.
However, it may also be enough to have any decoded DTMF string, not necessarily agreed, which acts as a call warning if the operator is far from the radio when the message is received.
The operation can be improved by programming a specific tone to limit false positives, so that when the user sees a decoded DTMF string on the display, he reasonably knows that someone has called him.
Basically the Simple Pager/Pocket Beep function of Kenwood, Icom, Alinco, Yaesu and so on, works with that scheme.
The user who sends the message cannot be sure that it has been received by the recipient user and this latter can not be sure that the possible call warning is not the result of a false positive.

The radios do have a basic pager function in them already, although not with any message sending capability.
Receiving radio ..
* Set "**D DCD**" to **ON** .. enables DTMF decoding

* Set "**D RSP**" to **RING** (or **BOTH**) .. enable beeping/ringing when DTMF call received

* Set "**D HOLD**" .. sets the 'call from' message on-screen time

Yes, I know, that is exactly what I already do.
The limit of this is in the 60 maximum seconds that D HOLD allows at the call warning to remain visible on the display.
The use of D RSP makes it similar to the operation of the Enhanced Pager function provided by Yaesu.

So it doesn't do message sending (at the moment), but it does do basic paging.

Actually, as I wrote, already now your firmware, but also the original one from Quansheng, allows the sending of messages.
The limits are in the 8 maximum characters for the text and 60 seconds maximum for their viewing on the display.
Of course, as happens for example with the Yaesu VX-3, transceivers must all be programmed with the same messages.
A further limit is that it is not possible to write messages on the fly nor from the scratch, as it could be done with very old Kenwood, ICOM, Yaesu, Standard and so on (normally up  6 characters maximum), but there is the advantage that the messages cannot be decoded by third parties who do not know their programming code.
Be seeing you.
U.Sb

The "D HOLD" menu setting does have a "STAY ON SCREEN" option. So you can set it to remain in screen until you next press a key.

Hi OneOfEleven,
thanks, you are really great and very kind, the best!
Thanks a lot!
Be seeing you.
U.Sb

Hi OneOfEleven,
as reference:
D HOLD set to STAY ON SCREEN works as expected for DTMF Decoding Response, while timing for the decoded DTMF string is not affected, it is always 5 seconds regardless D HOLD setting (5 seconds - STAY ON SCREEN).
Text "CALL FRM:" into DTMF Decoding Response prevents use of callsigns/messages 8 characters long, because the whole text exceeds the width of the display and so the last character start a new line generating artifacts.
Thanks a lot for your tireless and priceless work!
Be seeing you.
U.Sb

Seems OK in this firmware.
I guess whatever QS is doing is also inverting the sub-audible up into the HF audio range.

@OneOfEleven
Hi OneOfEleven,
first, good to see you back.
I was sure you would have managed to fix things.

Sorry for the bad picture.
Text is "CALL FRM : UV-5K(8)"
Since the problem with CALLSIGNS/MESSAGES 8 characters long is only cosmetic and it can be easily arranged, for instance by removing colon from the text "CALL FRM:" to make it become "CALL FRM", thus saving a character on the total shown on the single line of the display and the possible modification is within the reach of all while it is building the firmware from themselves, in my opinion the issue can be closed.
Thanks a lot for your tireless support and great patience.
Be seeing you.
U.Sb

No it's OK, I leave issues open so that I don't forget to sort them out, that's why I left yours open. I was going to get to it, just haven't got there yet.

Hi OneOfEleven,
thanks for fixing the matter, you are really very kind.
Now it is gone.
Thanks a lot for your priceless support and great patience.
Be seeing you.
U.Sb

You're welcome


Does this supports kotlin version 2.4.0 of the readium library

Not yet.

@amalStorilabs I just released a new version v2.0.0-rc.0 that is upgraded to<EMAIL_ADDRESS>


deps(mac/js): update WebExtension, omit injectProcessEnv from TokenSigning backwards compatibility code

WE2-907

Signed-off-by: Mart Somermaa<EMAIL_ADDRESS>

Merged within #316


[SPARK-9591][CORE]Job may  fail for exception during getting remote block

SPARK-9591
When we getting the broadcast variable, we can fetch the block form several location,but now when connecting the lost blockmanager(idle for enough time removed by driver when using dynamic resource allocate and so on) will cause task fail,and the worse case will cause the job fail.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

thanks for updating @jeanlyn .  Sorry that I didn't fully understand the issue earlier and for potentially changing the desired outcome on you.

Thanks everyone for the review! I updated the code, and now doGetRemote will accept exception when we still have location to fetch the block avoiding the work flow being broken, and the BlockFetchException(this is the behavior of doGetRemote, so i use a new exception and wrap the last exception,any suggestions?) will throw when there is no location.

ok to test

Merged build triggered.

Merged build started.

Test build #41899 has started for   PR 7927 at commit 75db334.

@jeanlyn can you rename the title of this patch and the issue to remove references to "broadcast"? I believe this is applicable to all blocks in general.

Test build #41899 has finished for   PR 7927 at commit 75db334.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class BlockFetchException(messages: String, throwable: Throwable)

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41899/
Test PASSed.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #41907 has started for   PR 7927 at commit 6c6d53d.

Test build #41907 has finished for   PR 7927 at commit 6c6d53d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class BlockFetchException(messages: String, throwable: Throwable)

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41907/
Test FAILed.

It seems that the failure not related.

retest this please

Merged build triggered.

Merged build started.

Test build #41960 has started for   PR 7927 at commit 6c6d53d.

Test build #41960 has finished for   PR 7927 at commit 6c6d53d.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class BlockFetchException(messages: String, throwable: Throwable)

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41960/
Test PASSed.

LGTM merging into master, thanks everyone.

i have this problem in spark1.3.0, is there any other solutions? i can't update spark to 1.6

@sprite331. According to my understanding, this patch tries to catch certain exceptions when the user introducing dynamic allocation. One quick solution is to disable dynamic allocation if possible, which can avoid certain exception (negative part is to miss that new function introduced since 1.3). Another one, you can try to catch that exception by yourself (if you upgrade your 1.3 deployments).  I am not sure if either solutions work to you or not.


Use hashing to compare SideCondition

We should investigate using Hashed to compare SideConditions because that is heavily used.

After fixing #2102, this is not really performance-limiting anymore.


Create a form so the user can write his/her initials , and a function to store the initial and the score.

User Story
AS A coding boot camp student
I WANT to take a timed quiz on JavaScript fundamentals that stores high scores
SO THAT I can gauge my progress compared to my peers

Acceptance Criteria
GIVEN I am taking a code quiz
WHEN the game is over
THEN I can save my initials and my score

Created a form so the user can input his/her initial and used the local storage to save the initials and the score of the users.


Ass 3 feedback

Ass 3 feedback

although there are some places need improvements, overall you've got a good submission, well done!

Thank you for taking your time for the review. I will improve it


Fix upgrade TestMain since it is breaking post submit tests  (#6096)

Fix upgrade TestMain since it is breaking tests.
Also add helm installer to SimpleTests.

Fix errors

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: rkpagadala
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: yutongz
Assign the PR to them by writing /assign @yutongz in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

prow/OWNERS [rkpagadala]
tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hklai, rkpagadala
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

prow/OWNERS [hklai,rkpagadala]
tests/OWNERS [hklai]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Incompatible with Anonymized DNSCrypt

I use dnswarden-uncensor-sg1-dc in dnscrypt-proxy with anonymized dnscrypt, in dnscrypt-proxy.toml I set skip_incompatible = true, but dnswarden-uncensor-sg1-dc not in used (incompatilbe with the settings). Any plan to make it compatible?

Looks like it is failing on certain relays and working on some relays, for example it worked on anon-cs-montreal relay. I've no idea what is causing to fail on some relays.

Closing this, the older dnscrypt servers will cease to exist in few days/weeks as i've moved my entire dns setup to new platform. Stamps for new servers can be found here.


Storybook 8 compatibility

Hey @yuqu! I’m reaching out from the core SB team :)
Storybook 8 (our next major release) is coming soon, and it introduces some breaking changes that your addon might need to account for.
We’ve listed all the key changes in a new Storybook 8 migration guide, and we’d encourage you to check it out and see if your addon is impacted.
We also have an addons channel in our Discord community, which we’d like to use to better communicate with addon authors in the future. If you’re not part of the server, consider joining here and message me (@joevaugh4n) so that I can give you the addon creator role! If you’re already in the server, please just ping me and I’ll respond to you there.
Thanks for being a part of our addon community!
Joe

To resolve the dependency issue, we should replace the dependency @storybook/addons and @storybook/api with @storybook/preview-api and @storybook/manager-api.
@storybook/addons
https://www.npmjs.com/package/@storybook/addons

The contents of this package have moved to @storybook/preview-api and @storybook/manager-api. Please update your import depending on where are using this API.
This package will no longer be released as part of the 8.0 release of storybook.

@storybook/api
https://www.npmjs.com/package/@storybook/api

The contents of this package have moved to @storybook/manager-api. Please update your import.
This package will no longer be released as part of the 8.0 release of storybook.

@joevaugh4n @mmuenker Thanks for reaching out.
We've just updated our addon to v3.0 to be compatible with Storybook v8.


Added framework_version

Issue: https://linear.app/netlify/issue/COM-75/add-framework-version-parameter-to-open-api-deployfiles
The new field it's added to the deploy files. The framework is added here as well, but I think that's just for deploy creation? And we will be updating the deploy

Force pushed with a changed commit message for the conventional commits check

https://linear.app/netlify/issue/COM-75/add-framework-version-parameter-to-open-api-deployfiles


WIP: add UseCompatibleTypes Rule, including related resources.  Refactor UseCompatibleCmdlets Rule.

PR Summary
Add UseCompatibleTypes rule which checks for compatibility with a specified version of PowerShell on a specified platform.  Refactor UseCompatibleCmdlets to be similar since both use the same resources.
Need:
updated type/cmdlet dictionaries for Core 6.0.2
rule documentation
PR Checklist
Note: Tick the boxes below that apply to this pull request by putting an x between the square brackets. Please mark anything not applicable to this PR NA.

[x] PR has a meaningful title

[x] Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] User facing documentation needed
[x] Change is not breaking
[x] Make sure you've added a new test if existing tests do not effectively test the code changed
[ ] This PR is ready to merge and is not work in progress

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready

The command data files are of version 6.0.1 and not 6.0.2 (a rename should be sufficient). The osx file should use the word macos instead of osx, see recently merged PR 947 for why.

@MiaRomero Please update your branch and resolve merge conflicts

@rjmholt All the added/removed/renamed JSON files should probably be reverted as this PR was created before I added the proper ones for 6.0.2. The ones for 6.1 should only be added once 6.1 goes GA

I'm closing this now as #1133 was taken


request.params missing in the docs. Issue#1683.

Fixes https://github.com/koajs/koa/issues/1683
request.params documentation was missing. I have included it with suitable example.

There is no request.params in Koa. I assume you are using @koa/router, in which case this should be moved to that repo.


Create test cases for tests without test case id in testrail

My test rail project has around 100 test cases. Half of them are automated by Cypress. So I can match only 50% of the test cases to cypress tests (by setting testcase id). The results are reported to testrail if I execute cypress, but only testcases which are marked with a testcase number are generated. I would like to generate the other non automated test cases too so we can see what we should test manually. Is that possible?

Ok, just noticed I can achieve wanted behavior by using "runIncludeAll": true,

Hi
ok great
thank you for clearing things up
have a wonderful weekend


Few issues during setup

Disclaimer: aint so good at this coding thing :)
I got a few errors while testing this. Not sure if I'm following the steps as intended. Here's what I did:

Created a new folder pluginTest, not in the sketch plugins folder
Ran skpm init
Ran skpm build, and got this error:

Error: ENOENT: no such file or directory, mkdir '/Users/aminnassiri/Projects/pluginTest/plugin.sketchplugin/Contents/Sketch'

Added the folders manually and ran skpm build again. Got this error:

error Error while building ./my-command.js
{ SyntaxError: /Users/aminnassiri/Projects/pluginTest/src/my-command.js: Unterminated string constant (2:31)
1 | export default function (context) {
2 |   context.document.showMessage('It's alive 🙌')

Changed the string and ran skpm build again. Worked this time.
Installed the plugin and tested it. Works!
Ran the skpm link and got this error:

Amins-MBP:pluginTest aminnassiri$ skpm link /Users/aminnassiri/Library/Application\ Support/com.bohemiancoding.sketch3/Plugins
error Error while reading the package.json file
{ Error: Cannot find module '/Users/aminnassiri/Projects/pluginTest/Users/aminnassiri/Library/Application Support/com.bohemiancoding.sketch3/Plugins/package.json'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/usr/local/lib/node_modules/skpm/lib/skpm-link.js:24:17)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3) code: 'MODULE_NOT_FOUND' }

Thanks for the report!

Error: ENOENT: no such file or directory, mkdir '/Users/aminnassiri/Projects/pluginTest/plugin.sketchplugin/Contents/Sketch'

I'll fix that thanks

error Error while building ./my-command.js
{ SyntaxError: /Users/aminnassiri/Projects/pluginTest/src/my-command.js: Unterminated string constant (2:31)
1 | export default function (context) {
2 | context.document.showMessage('It's alive 🙌')

That should be fix in the version 0.4.7 (https://github.com/sketch-pm/skpm/pull/10)

Ran the skpm link and got this error:

skpm link should be called with the path to your new folder (here: /Users/aminnassiri/Projects/pluginTest)
I could probably check that the path given is not the path to the com.bohemiancoding.sketch3/Plugins folder

should be fixed in 0.4.8
Feel free to come back with any feedback and suggestions that you have, I'd love to see if it meets other use cases than mine


⚠ Mobitopup has degraded performance

In da5f830, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 4595 ms

Resolved: Mobitopup performance has improved in 11c32a8.


Issue after upgrading to fw CC2652RB_20210128

Hi,
I did upgrade a CC2652RB from slae.sh tonight from version CC2652RB_20201026 to version CC2652RB_20210128 and the dongle was then unable to communicate properly after the upgrade with zigpy. After a downgrade it's working again.
Upgrade was first successfully performed with Jelmer's script then with SmartRF Flash Programmer 2.
More details in the issue initially opened with zigpy-znp: https://github.com/zigpy/zigpy-znp/issues/63
Any help would be greatly appreciated =)

My bad, I did use the router image instead of the coordinator by mistake.
I checked this morning again the last version for CC2652RB as a coordinator and it's CC2652RB_2021010 so I definitely did not download the correct fw. This couldn't have work.


Add property for retrieving raw bytes of scan record

adding scan record byte support,
https://github.com/JuulLabs/kable/issues/356

@kemalfaust you'll need to run:
./gradlew apiDump

And commit the changes.

@twyatt sorry my first pull request, I think now its ready

Look like your API dump is for an outdated commit.
Try going a git pull and then running the ./gradlew apiDump again?

@kemalfaust everything looks good, I'll merge (and release) shortly after I get another review approval.

Nice, thank you @twyatt I'll wait new Release 🎉


fix: Allow pip requirements in specific dependencies

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

GitHub release
PyPI release
Conda release

Your semantic-release bot :package::rocket:


#1349 Improve CLI error message when API connection fails

This PR adds the functionality to improve the CLI error message when no API connection can be made.
It adds a generic utility function in the cli/cmd/check_endpoint_status.go which pings the API using the HEAD request method and checks whether it's active. This allows for handling these kind of errors more elegantly and also makes provision to suggest remedial measures.

Thank you for your contribution. It looks like some of the unit tests of the CLI are breaking in our CI:
?   	github.com/keptn/keptn/cli	[no test files]

=== RUN   TestAddResourceToProjectStageService

--- FAIL: TestAddResourceToProjectStageService (0.00s)

    add_resource_test.go:47: unexpected error, got 'Resource testResource.txt could not be uploaded: Head configuration-service: unsupported protocol scheme ""

        Possible reasons:

        * The Keptn API server is currently not available. Check if your Kubernetes cluster is available.

        * Your Keptn CLI points to the wrong API server (verify using 'keptn status')'

=== RUN   TestAddResourceToProjectStage

--- FAIL: TestAddResourceToProjectStage (0.00s)

    add_resource_test.go:63: unexpected error, got 'Resource testResource.txt could not be uploaded: Head configuration-service: unsupported protocol scheme ""

        Possible reasons:

        * The Keptn API server is currently not available. Check if your Kubernetes cluster is available.

        * Your Keptn CLI points to the wrong API server (verify using 'keptn status')'

=== RUN   TestAddResourceToProject

--- FAIL: TestAddResourceToProject (0.00s)

    add_resource_test.go:79: unexpected error, got 'Resource testResource.txt could not be uploaded: Head configuration-service: unsupported protocol scheme ""

        Possible reasons:

        * The Keptn API server is currently not available. Check if your Kubernetes cluster is available.

        * Your Keptn CLI points to the wrong API server (verify using 'keptn status')'

=== RUN   TestAddResourceToProjectService

--- FAIL: TestAddResourceToProjectService (0.00s)

    add_resource_test.go:97: unexpected error, got 'Resource testResource.txt could not be uploaded: Head configuration-service: unsupported protocol scheme ""

        Possible reasons:

        * The Keptn API server is currently not available. Check if your Kubernetes cluster is available.

        * Your Keptn CLI points to the wrong API server (verify using 'keptn status')'

Yeah was looking into them. Need to cover the new function.


Validate the 'token/ticket' header for SSO Authentication

From what I can see in the code examples, this library can produce the token or tickets:
      service_fqdn: 'm01.krb.local'
    }, function (err, token) {
      if (err) {
        console.log(err)
      } else {
        console.log('SPNEGO token :', token)
      } })

I would like to validate the 'token/ticket'. Not sure if this library supports that. Is it the case?

I don't remember that we have a validation function.


Infer working with Bazel would be nifty.

Bazel is a pretty nifty build tool. It'd be even niftier if you could use it with Infer. Any chance of adding some support for it? I notice that there's a way of getting the clang database out now....

That would be the niftiest! Please discuss in #457


Add a flag for input redis username

Description
We need to use the Redis username to connect to our Redis, but it seems there is no this flag to start asynqmon.
I tried to use the redis-url to start it, but there are some special characters in our password (e.g. @, % etc...) so the parser will parse our password in the wrong way.
Solution
Can I submit a PR to add a flag for --redis-username?

Sure, please feel free to open a PR

Thanks, I've created a PR for this issue.


Update how-to-install-iot-edge-ubuntuvm.md

Fixed typo, 'azure' should be 'az'

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

The fix looks correct; merging.
Thanks @jantielens.


Allow arangodump to backup _jobs and _queues

My Environment

ArangoDB Version:        3.5.2
Storage Engine:             RocksDB
Deployment Mode:       Single Server
Deployment Strategy:   Manual Start
Configuration:               N/A
Infrastructure:               Own
Operating System:        Ubuntu 18.04
Total RAM in your machine:        12GB
Disks in use:        HDD
Used Package:              Ubuntu .deb

Component, Query & Data
Affected feature:  arangodump
Problem: When arangodump is run with --include-system-collections, _analyzers, _appbundles, _apps, _aqlfunctions, _graphs, _modules are dumped, but not _jobs or _queues. We would like to be able to back them up for logging purposes.
Expected result: Include _jobs and _queues to dump in --include-system-collections or as another cli option.

Hi @monotykamary,
Version 3.5.5, which includes a fix for this issue, has been released.
From the Changelog:

Include collections "_queues" and "_jobs" in dumps created by arangodump
in case the option --include-system-collections was set to true. Previously
these collections were always excluded from dumps.

Please find the latest release in the download section.


Flutter package example specification

Seems like example folder for Flutter package does not meet Dart package specification
Steps to reproduce
cd /tmp
flutter create --template package abc
cd abc
mkdir example
flutter pub get

Throws an error:
/tmp/abc/example: no pubspec.yaml found
After creating README.md or main.dart in the example folder, the same error is thrown.
Seems like, it requires an entire Flutter app here instead of some code snippets.
It there any documentation for that? Thanks!

Hello @pd4d10 !
Thank you for posting.
Can you please also post an output of the flutter doctor -v command?
This seems to be a similar issue to the one discussed here: #19973
Thank you.

Thanks for the quick response!

flutter doctor -v
[✓] Flutter (Channel dev, v1.10.5, on Mac OS X 10.14.5 18F203, locale zh-Hans-CN)
    • Flutter version 1.10.5 at /Users/z/github/flutter
    • Framework revision 3cf88fed6d (4 天前), 2019-09-18 23:09:41 -0400
    • Engine revision 33ad6757e8
    • Dart version 2.6.0 (build 2.6.0-dev.0.0 cb80ea7ba9)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/z/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.0, Build version 11A420a
    • CocoaPods version 1.7.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] VS Code (version 1.38.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.4.1

[✓] Connected device (3 available)
    • Chrome        • chrome                               • web-javascript • Google Chrome 76.0.3809.132
    • Server        • web                                  • web-javascript • Flutter Tools

I tried to using flutter create to create an app in the example folder and it works now. Just wondering it is different from Dart package.

Flutter needs an existing pubspec.yaml in the example folder.