Error: Could not parse CSS stylesheet

Error: Could not parse CSS stylesheet at exports.createStylesheet (/application/node_modules/jsdom/lib/jsdom/living/helpers/stylesheets.js:34:21) at HTMLStyleElementImpl._updateAStyleBlock (/application/node_modules/jsdom/lib/jsdom/living/nodes/HTMLStyleElement-impl.js:68:5) at HTMLStyleElementImpl._childTextContentChangeSteps (/application/node_modules/jsdom/lib/jsdom/living/nodes/HTMLStyleElement-impl.js:36:12) at TextImpl.replaceData (/application/node_modules/jsdom/lib/jsdom/living/nodes/CharacterData-impl.js:108:23) at TextImpl.set data [as data] (/application/node_modules/jsdom/lib/jsdom/living/nodes/CharacterData-impl.js:26:10) at JSDOMParse5Adapter.insertText (/application/node_modules/jsdom/lib/jsdom/browser/parser/html.js:142:22) at Parser._insertCharacters (/application/node_modules/jsdom/node_modules/parse5/lib/parser/index.js:600:30) at Object.insertCharacters (/application/node_modules/jsdom/node_modules/parse5/lib/parser/index.js:1062:7) at Parser._processToken (/application/node_modules/jsdom/node_modules/parse5/lib/parser/index.js:657:55) at Parser._processInputToken (/application/node_modules/jsdom/node_modules/parse5/lib/parser/index.js:684:18) at Parser._runParsingLoop (/application/node_modules/jsdom/node_modules/parse5/lib/parser/index.js:440:18) at Parser.parse (/application/node_modules/jsdom/node_modules/parse5/lib/parser/index.js:344:14) at Object.parse (/application/node_modules/jsdom/node_modules/parse5/lib/index.js:10:19) at parseIntoDocument (/application/node_modules/jsdom/lib/jsdom/browser/parser/html.js:202:17) at parseIntoDocument (/application/node_modules/jsdom/lib/jsdom/browser/parser/index.js:31:10) at new JSDOM (/application/node_modules/jsdom/lib/api.js:42:5)
This error occurs after trying to generate a transcript, the transcript is generated normally, but then this error occurs.

Doesn't seem to be occurring for me. Are you running the latest version of discord-html-transcripts?

I was using 2.5.8, just upgraded to 2.6.0 to test if it might be fixing the bug, but it didn't.

Can you run npm list jsdom and send the output?

D:\Programação\Colorado-Bot>npm list jsdom npm WARN config global --global, --localare deprecated. Use--location=globalinstead<EMAIL_ADDRESS>D:\Programação\Colorado-Bot +--<EMAIL_ADDRESS>|--<EMAIL_ADDRESS>--<EMAIL_ADDRESS> --<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>D:\Programação\Colorado-Bot>`

I was looking here too, and this error only appeared on the linux system on windows is normal

re-open if issue still exists


block certifier: fix certifier concurrent map access

Motivation
race condition, added test that failed with -race -count 5 and pass after the fix

bors merge


[WIP] React 0.14

This PR updates react-test-tree to support React 0.14. This will be a breaking update for anyone using React 0.13 or lower, so I propose we release it as v0.3.0. I also propose that we release when 0.14 is also officially released.

Split tree nodes into two types: TestNode and TestClassNode
TestNodes represent plain HTML elements, whereas TestClassNodes represent instances of React components
Only TestClassNodes have the code for handling refs/refCollections and their associated logic
getDOMNode is abstracted into a separate utility method in order to handle different types of element
The ref tree walk has now been updated to handle React's new ref structure. Unfortunately this is not very clean

Still to do:

[x] Add HOC support
[x] Pull in changes to README
[x] Handle ref name clashes
[x] Decide on value prop
[x] Simulate library tests
[x] refCollections should work on composites
[x] Document breaking changes and how to migrate
[x] Release rc1
[x] Complete empty tests, add additional tests
[x] Add support for stateless components
[x] Always wrap input with additional component so we can hijack render
[x] Refactor to use testRef and testRefCollection instead of ref and refCollection
[x] Update docs to reflect new API changes
[x] Document how state changes are async
[x] Children should retain their type; don't always convert them to an array
[ ] Investigate HoC/stubbing issue (add more tests on it)

Closes #30 #47 #43 #39 #24 #48

Need to resolve #36 before this can be merged

Just checking… is there still a plan to merge this?

Hi - yeah there's still a bit more work to be done, but I'm hoping to do it
this week.
On 16 Oct 2015 8:55 p.m., "Joey Baker"<EMAIL_ADDRESS>wrote:

Just checking… is there still a plan to merge this?
—
Reply to this email directly or view it on GitHub
https://github.com/QubitProducts/react-test-tree/pull/31#issuecomment-148819126
.

@joeybaker @aguestuser @doctyper this has been released as 1.0.0-rc1. Please install like so:
npm install<EMAIL_ADDRESS>Could you give it a whirl for me? Thanks! Check out the README and CHANGELOG to see what has changed.

I likely won't have time to look at this until Friday, but I will, and thank you for the work!!

Yay! Such great news! Happy to take a look and will likely have time to do so somewhere in the Thur/Fri range.

I gave this a quick tryout today. Unfortunately, I'm getting an error. Here's a repo. You can run the tests with npm test

@joeybaker thanks for trying it out. Did you forget to put a link in?

Whoops! Sorry about that. Here's the repo https://github.com/joeybaker/react-element-query/tree/react-0-14?files=1 relevant code is in the react-0-14 branch

Ok this happens because we now always need to wrap the component's render function before rendering it. This doesn't work in your case because you are passing a  as the top level component. I should be able to fix this by always wrapping the testTree input in a proper component.

:+1: thanks!

@joeybaker rc2 has been released, please give it a whirl it should fix your issue!

@joeybaker just released rc3 which fixes rc2 - please try that out :)

@oliverwoodings my day became very crazy. Will look tomorrow. Sorry for the delay!

@oliverwoodings Okay, I tried rc3, and I'm seeing a new error:

Relevant bit of the code:
  const smallTree = testTree((

    <ElementQuery sizes={sizes}>

hi

    </ElementQuery>

), {mount: true})
  const smallEl = smallTree.container[0].element

@joeybaker your refCollection prop there is not contained inside a component so it doesn't belong to anything. If you want to render it like that you need to set the wrap config option to true.
<EMAIL_ADDRESS>has been released with support for the new testRef and testRefCollection support.

@oliverwoodings: Just tried out rc4, the new testRef and testRefCollection API works great.
Question, in rc3 it was possible to add a ref to a child and have that ref be accessible from react-test-tree. E.g.:
const someElementTree = testTree(
    <SomeElement>

Test Child

    </SomeElement>
);

const testChildRef = someElementTree.get("testChild");
expect(testChildRef).to.exist; // passes rc3, fails rc4

This no longer works in rc4 (I also tried changing ref -> testRef. No joy.)
Is this by design or a bug?

Hmm, I upgraded all my dependencies today, and my application works fine. Now I'm working on getting the tests up and running as well, and I see this error:
Error: Invariant Violation: onlyChild must be passed a children with exactly one child.
    at invariant (base/test/all-tests.js:15071:16)
    at Object.onlyChild [as only] (base/test/all-tests.js:33443:85)
    at Transition.render [as __rttOldRender] (base/test/all-tests.js:57454:46)
    at Transition.renderProxy [as render] (base/test/all-tests.js:35497:51)
    at ReactCompositeComponentMixin._renderValidatedComponentWithoutOwnerOrContext (base/test/all-tests.js:21530:35)
    at ReactCompositeComponentMixin._renderValidatedComponent (base/test/all-tests.js:21550:33)
    at ReactPerf.measure.wrapper (base/test/all-tests.js:15345:22)
    at ReactCompositeComponentMixin.mountComponent (base/test/all-tests.js:21163:31)
    at ReactPerf.measure.wrapper [as mountComponent] (base/test/all-tests.js:15345:22)
    at Object.ReactReconciler.mountComponent (base/test/all-tests.js:19473:36)

Running on rc4.
I'm not doing anything special, just rendering this in a ES6 class extending React.Component:

(From react-bootstrap) (I usually have stuff inside the Nav element, but for the sake of testing I removed it).
I debugged the code, and this.props.children is provided as an array with length = 1, while the React.Children.only expects a object.

I ran into that too. It was my assumption that react 0.14 changed the behavior of children to always be an array, but I didn't consider that test tree might be at fault.

@oliverwoodings got it thanks! I missed that wrap was added in 1.0.
I just gave rc4 a shot, and everything looks good!

A suggestion: it might be worth adding a migration-guide doc for 1.0.
Based on the changelog and my own notes, I think these are the main points:
* `.get` && `getIn` instead of direct property access
* `wrap` option to use refs on an element passed directly to test tree
* `testRef` and `testRefCollection` instead of just `ref` and `refCollection`

Would you accept a PR that created this doc?

Hmm...I can't get a decorated component to properly work...

The component has a ref which is supposed to be stubbed out, that part seems to be broken because of reassignment bug here: https://github.com/QubitProducts/react-test-tree/blob/react0.14/lib/testTree.js#L73-L79 (const ftw!)

I have declared innerComponentRef and innerTestRef, and the fields inside the component I have put in testRef, as it should be. But I can't get it to work.

FWIW I use react-bootstrap. The component works fine in the app, but breaks in tests... Please try reproducing, and if unable I can try creating a test case.

@Blystad I'm having the same issue. test-tree seems to lose refs when components get HoC wrapped / decorated.

@doctyper you need to use the new wrap option for that scenario to work. As with the old ref syntax, testRefs and testRefCollections have to 'belong' to a composite component (i.e. they need to be returned from the render function of a component class). In your example there you are calling testTree with elements that aren't contained inside a component class. Specifying wrap: true in the testTree options will cause testTree to wrap it for you :)
@joeybaker check out the readme on the react0.14 branch, there is a section in there on migrating to 1.0. Feel free to add to it!
@Blystad @joeybaker regarding children being an array, this is a bug in test-tree that I need to address. For some reason I assumed making children always an array wouldn't be a problem, but I now see the issue with that! https://github.com/QubitProducts/react-test-tree/blob/react0.14/lib/testTree.js#L151
@Blystad not sure I follow you about the stubbing out part - what is the reassignment bug?
I'll check out the HoC issues, see if I can reproduce anything.

@oliverwoodings I'm not sure the re-assignment is a bug, but it certainly looks strange to reassign a function argument multiple places.
Any chance you can look into the HOC and React.Children issue soon? 2/3 of my tests are currently broken :(
Thanks for your hard work!

Yep planning to look into those today. Been a bit hectic here, sorry I haven't got round to it sooner!

@Blystad @joeybaker the children issue is fixed on the react0.14 branch. Working on the HoC/stubbing issue now

@Blystad @doctyper i'm not able to replicate the HoC issue, and all the tests are passing for stubbing/HoC. Could you make a test case please?

Alright, will do.

https://github.com/Blystad/issue-RTT-31
Here you go. I stripped away as much as I feel confident about removing.
What I'm doing (and which worked great on 0.13), is inspired by redux-form.
I have a decorator which accepts some options:
{
    form: <formName>,
    fields: ['fieldA', 'fieldB', 'fieldC'],
    validator: function,
}

The decorator then passes on a datastructure in the fields prop, which contains the properties I want to assign to each input field:
          onChange: this.onChange.bind(this),
          name: fieldName,
          testRef: fieldName,
          value: this.props.values[fieldName],
          checked: this.props.values[fieldName],

I test this using both autogenerated and written tests. The auto generated ones are there to ensure that the form is hooked up correctly, and the written tests to ensure special form behaviour.

@Blystad i'm not able to install your test setup i'm afraid, get this error:

(i've checked, that file isn't there before i run npm install)

Try using a newer version of Node. I use 4 I think.

Ok will do

Ok got it running, but it's proving quite hard to debug. Will update you as I go.

Great, thanks
On Fri, 20 Nov 2015, 18:19 Oliver Woodings<EMAIL_ADDRESS>wrote:

Ok got it running, but it's proving quite hard to debug. Will update you
as I go.
—
Reply to this email directly or view it on GitHub
https://github.com/QubitProducts/react-test-tree/pull/31#issuecomment-158464503
.

@Blystad worked it out! Here: https://github.com/Blystad/issue-RTT-31/blob/master/src/main/js/policy/PolicyDecorator.jsx#L63 you are setting the testRef, then spreading the props onto the component. Props actually contains { testRef: undefined }, which overrides the previous testRef you set. If you move the testRef to after you spread the props it will work.
The reason this happens is because we have to 'delete' the testRefs from parents so they don't accidentally propagate to children. I'm currently doing this by setting testRef to be undefined when cloning, which is what is causing this adverse behavior. We have to set it to undefined because react does a shallow merge when using React.cloneElement. I'm going to have to find another way to 'remove' the prop (probably by manually recreating the element instead of cloning it).

Aha, great, I'll test that tomorrow :) Thanks
On Fri, 20 Nov 2015, 18:46 Oliver Woodings<EMAIL_ADDRESS>wrote:

@Blystad https://github.com/Blystad worked it out! Here:
https://github.com/Blystad/issue-RTT-31/blob/master/src/main/js/policy/PolicyDecorator.jsx#L63
you are setting the testRef, then spreading the props onto the component.
Props actually contains { testRef: undefined }, which overrides the
previous testRef you set. If you move the testRef to after you spread the
props it will work.
The reason this happens is because we have to 'delete' the testRefs from
parents so they don't accidentally propagate to children. I'm currently
doing this by setting testRef to be undefined when cloning, which is what
is causing this adverse behavior. We have to set it to undefined because
react does a shallow merge when using React.cloneElement. I'm going to have
to find another way to 'remove' the prop (probably by manually recreating
the element instead of cloning it).
—
Reply to this email directly or view it on GitHub
https://github.com/QubitProducts/react-test-tree/pull/31#issuecomment-158471563
.

Tested it, and you were right.
However, the onChange tests still fail. If I change the inputs to normal HTML inputs, it's fine. Bootstrap Input however, does not work.

@Blystad this is not directly a problem with RTT. You are calling simulate on react-bootstrap's <Input /> component - this is not actually an input DOM node, hence why it doesn't work. See this thread: https://github.com/react-bootstrap/react-bootstrap/issues/297 - to simulate changes on a react-bootstrap component you have to call it's getInputDOMNode() method. We used to invisibly support this quirk in RTT by checking if an element had the getInputDOMNode method, but I removed it in the new version since I want to try and keep RTT as pure and unbiased as possible. Maybe I should add it back, though...

Hey Oli - it's also a similar issue with Material UI -
http://material-ui.com. It's a pain - not sure how to fix it, as those
components get quite complicated. I'm testing the onChange prop which is
passed in, but would be nice if there were a common way to handle these
things..
On Sun, Nov 22, 2015 at 11:41 AM, Oliver Woodings<EMAIL_ADDRESS>wrote:

@Blystad https://github.com/Blystad this is not directly a problem with
RTT. You are calling simulate on react-bootstrap's  component -
this is not actually an input DOM node, hence why it doesn't work. See this
thread: react-bootstrap/react-bootstrap#297
https://github.com/react-bootstrap/react-bootstrap/issues/297 - to
simulate changes on a react-bootstrap component you have to call it's
getInputDOMNode() method. We used to invisibly support this quirk in RTT
by checking if an element had the getInputDOMNode method, but I removed
it in the new version since I want to try and keep RTT as pure and unbiased
as possible. Maybe I should add it back, though...
—
Reply to this email directly or view it on GitHub
https://github.com/QubitProducts/react-test-tree/pull/31#issuecomment-158752038
.

@wbecker does material-ui expose similar kinds of methods?

No, it's pretty black box. I would have thought though that the point of
RTT with regards to 3rd party libraries should be to make it easy to ensure
that callbacks happen, not that some action on the DOM triggers a callback.
Like if have a thing like  what I would want to test is that
changeCallback gets called (with the expected arguments).
From a Unit test PoV you shouldn't care under what circumstances it gets
called - just that your component that uses it handles the onChange event.
From an Integration test PoV you do care about this, and if the underlying
component changes from one version to another (eg it provides different
arguments) then you will have some issues. I'm not sure how to test this
though, because this implies that you can create the right scenario for
that callback to be triggered in the test... This is obvs tricky - it might
be simple if your component if just wrapping a Select or something, but
will get a lot more complicated as the complexity of the 3rd party
component changes. In these cases, what can you do? So in the general case
maybe its best to focus on allowing the Unit test use case?
On Sun, Nov 22, 2015 at 12:58 PM, Oliver Woodings<EMAIL_ADDRESS>wrote:

@wbecker https://github.com/wbecker does material-ui expose similar
kinds of methods?
—
Reply to this email directly or view it on GitHub
https://github.com/QubitProducts/react-test-tree/pull/31#issuecomment-158758370
.

No, it's pretty black box. I would have thought though that the point of
RTT with regards to 3rd party libraries should be to make it easy to ensure
that callbacks happen, not that some action on the DOM triggers a callback.

How is RTT meant to know what a callback is meant to be called with? We can't assume that just because a component has a prop called onChange that it is expecting to be invoked like a native JavaScript onChange handler.

Like if have a thing like  what I would want to test is that
changeCallback gets called (with the expected arguments).

Again - how is RTT meant to know what 'expected' arguments are? I would also argue that if you are testing for expected arguments then you are doing an integration test, not a unit test. By testing the arguments you are testing the third party component.

From a Unit test PoV you shouldn't care under what circumstances it gets
called - just that your component that uses it handles the onChange event.

I agree, but if that is the case then maybe you should just be stubbing out the third party component and triggering the onChange yourself. If you just want to make sure that changeCallback is invoked, can't you just manually invoke the prop yourself:
var tree = testTree(<FooComponent />);
var spy = sinon.spy(tree.element, "changeCallback");
tree.get("thirdPartyComponent").getProp("onChange")("foo");
expect(spy).to.have.been.calledWith("foo");

And perhaps combine this with stubbing to make some kind of generic replacement component?

I quickly checked the source and I guess this is what you're looking for @oliverwoodings
  getInputNode() {
    return ReactDOM.findDOMNode(this.refs.input);
  },

https://github.com/callemall/material-ui/blob/master/src/enhanced-textarea.jsx#L122

How is RTT meant to know what a callback is meant to be called with?

Exactly! That's what I was trying to differentiate between unit and
integration tests. You have to provide that yourself which is all pretty
lame.
It would be nice if there were a common way to get things triggered, to
make things like this easier... Like a HoC or something, kind of needs to
be a Lower order Component that lives inside that allows you to trigger
things as needed, so that it provides the right arguments. But that's not a
thing, but maybe there needs to be some common API that React components
can use so that you can do integration tests in a similar way all the time?
(I can't see it really picking up much steam though...)
That code is pretty much what I do. It's not fantastic but it allows you to
do some kind of TDD.
On Sun, Nov 22, 2015 at 1:24 PM, Oliver Woodings<EMAIL_ADDRESS>wrote:

No, it's pretty black box. I would have thought though that the point of
RTT with regards to 3rd party libraries should be to make it easy to ensure
that callbacks happen, not that some action on the DOM triggers a callback.
How is RTT meant to know what a callback is meant to be called with? We
can't assume that just because a component has a prop called onChange
that it is expecting to be invoked like a native JavaScript onChange
handler.
Like if have a thing like
onChange={this.changeCallback} />
what I would want to test is that
changeCallback gets called (with the expected arguments).
Again - how is RTT meant to know what 'expected' arguments are? I would
also argue that if you are testing for expected arguments then you are
doing an integration test, not a unit test. By testing the arguments you
are testing the third party component.
From a Unit test PoV you shouldn't care under what circumstances it gets
called - just that your component that uses it handles the onChange event.
I agree, but if that is the case then maybe you should just be stubbing
out the third party component and triggering the onChange yourself. If you
just want to make sure that changeCallback is invoked, can't you just
manually invoke the prop yourself:
var tree = testTree();var spy = sinon.spy(tree.element, "changeCallback");tree.get("thirdPartyComponent").getProp("onChange")("foo");expect(spy).to.have.been.calledWith("foo");
And perhaps combine this with stubbing to make some kind of generic
replacement component?
—
Reply to this email directly or view it on GitHub
https://github.com/QubitProducts/react-test-tree/pull/31#issuecomment-158759282
.

On another note, I'm trying this:
const inputDOMNode = root().get(item).element.getInputDOMNode();
expect(inputDOMNode, 'inputDOMNode').to.exist;

but, while I'm able to call getInputDOMNode the return value is undefined. I tried checking root().get(item).element.refs but that was an empty object.
Ideas?

@wbecker interesting stuff, although I can't really see how RTT can solve what you want.
@Blystad I'll check it out

@Blystad try installing directly from the react0.14 branch. I've pushed the updates for react-bootstrap integration, all your tests pass now:

Will hopefully have this released as an RC today.

@Blystad 1.0.0-rc5 has been released, please give it a whirl. I'm hoping this is our final rc needed before I can finally merge this!

:disappointed: I wish I could just put forth the :+1: and say shipit :shipit: but I found another, (damn) bootstrap related, bug:
When adding wrapperClassName and labelClassName to a Input component, the test fails. See updated test-case @ https://github.com/Blystad/issue-RTT-31/commit/b57beb53341f7b5510107cc0707e98e7a473a2d7

Wow how odd! I'll check it out

I've narrowed the issue down to the wrapperClassName prop which causes react-bootstrap to wrap the input children in a div. It is definitely caused by rtt somehow, just tring to work out why.

Worked out why. I switched to manually cloning the element using React.createElement with the old element type and new props/children (to fix the issue of testRef propagating as undefined) however this had the adverse affect of changing the owner of the elements, resulting in refs being assigned incorrectly. I've come up with a hacky fix for now, will release as an rc.

@Blystad 1.0.0-rc6 released, should solve your issues

Released 1.0.0-rc7 which fixes stubbing refs being passed through

Ok I'm going to merge and release this. I'm confident now that all the core issues are resolved and anything else will just be edge cases that can be fixed with small patches.

Thanks for all the hard work @oliverwoodings!

Awesome, great work, thanks :)

This is working great on my side! Thank you!


[ENHANCEMENT] Bump Harvester OS to SLE-Micro 5.5

Is your enhancement related to a problem? Please describe.
We should use the newer OS for v1.4.0
Describe the solution you'd like
Bump OS with SLE-Micro 5.5
Describe alternatives you've considered
None
Additional context
None

Have we considered bumping to SLE-Micro 5.6

Have we considered bumping to SLE-Micro 5.6?

The next release of SLE-Micro 5.5 is SLE-Micro 6.0
(Ref: https://www.suse.com/lifecycle/#suse-linux-enterprise-micro)
IIUR, there are some major changes (like moving to btrfs instead image-based immutable OS) on SLE-Micro 6.0.
So, I thought we should use SLE-Micro 5.5 instead SLE-MIcro 6.0. (6.0 will bring too many potential risks)
Also, the EoL of SLE-Micro 5.5 is' 31 Oct 2027`. It's long enough for us to move on to the next.

Thanks for this @Vicente-Cheng  - this looks good on Harvester Version: master-9c0a3a1-head
With:
<EMAIL_ADDRESS>Password:
Last login: Wed Jul  3 19:35:38 2024 from <IP_ADDRESS>
rancher@test-node-8:~> sudo cat /etc/os-release
NAME="SLE Micro"
VERSION="5.5"
VERSION_ID="5.5"
PRETTY_NAME="Harvester master"
ID="sle-micro-rancher"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sle-micro-rancher:5.5"
IMAGE_REPO="registry.suse.com/suse/sle-micro/base-5.5"
IMAGE_TAG="2.0.4-5.8.31"
IMAGE="registry.suse.com/suse/sle-micro/base-5.5:2.0.4-5.8.31"
TIMESTAMP=20240626110458
GRUB_ENTRY_NAME="SLE Micro"
VARIANT="Harvester"
VARIANT_ID="Harvester-20240703-785f4dd"
GRUB_ENTRY_NAME="Harvester master"
rancher@test-node-8:~>

I'll go ahead and close this out :+1: :smile:


Remove some C style casts

My project uses GCC and has -Werror and -Wold-style-cast compiler options set to catch bad pointer casting practices. While the lines I've changed aren't necessarily bad usage of the old style cast, the are collateral damage in the war against bugs.  I'm only using dragonbox.h in my project so other files haven't been changed.
Thanks for a great library.

Looks good, thanks. The only problem is that now the code style is a bit inconsistent, but I think I will at some point overhaul cast and literal constant usages so it should be no problem.


various fix and improvements

Codecov Report

Merging #79 into master will decrease coverage by 0.37%.
The diff coverage is 44.44%.

@@            Coverage Diff             @@
##           master      #79      +/-   ##
==========================================
- Coverage   98.47%   98.10%   -0.38%
==========================================
  Files          18       18
  Lines        1311     1318       +7
==========================================
+ Hits         1291     1293       +2
- Misses         20       25       +5

Impacted Files
Coverage Δ

pyriemann/utils/tangentspace.py
85.29% <28.57%> (-14.71%)
:arrow_down:

pyriemann/__init__.py
100.00% <100.00%> (ø)

pyriemann/clustering.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Images not rendering (solution)

Need close "img" tag on this part:

return <img src="${data.file.url}" alt="${caption}">;

@Havaria Thank you for letting me know.

This have been fixed along with many other major changes.

In addition to this, I would like you to know that, you can override default parser function in the same manner, as you would write a custom function. So, that can help you to define your own personal HTML Markup or make some temporary fixes for yourself.


Cifar100 dataset question

First of all, this is an excellent job, I want cifar100 as a dataset to run this code, but I found that the base of cifar100 is provided in configs/distillers, but in the resnet folder, I can't find the corresponding  file，I hope you can clear my doubts, thanks

I have updated and added the cofing. Thanks for reminding.

I have updated and added the cofing. Thanks for reminding.
I'm sorry that there is a new question here. May I ask where did you download the model here? I'm sorry for causing you so much trouble in a short period of time.

MMClassification doesn't provide the config or weight. So you need to train a teacher first.

I really like your work, I have an idea, I don't know if it is feasible, I would like to ask you to send me the teacher model file by email, so as to avoid other problems when the teacher model I trained is substituted into the existing code and lead to numerical deviations in the results. Thank you very much if you can 👍 💯

In fact, I cannot find the weight now. It's easy to train a teacher. For NKD, I use ResNet-34 as the teacher and the Top-1 Acc of the teacher is 79.3. Or you can reproduce other methods using the teacher you train. It donesn't need much time for training on Cifra-100.

Okay!!!thanks! You have solved a lot of my doubts, I will continue to support your work, thank you!


Switch to new provisioning process

This switches us to using the new provisioner, as documented by https://confluence.puppetlabs.com/display/EDU/(ALPHA)+Self-provisioned+training+VMs
It means that if we want to release another old style VM that we'll have to build from the legacy branch. Going forward, we'll need to build the master VM by executing the boostrap.sh provisioning script in a first-boot task.
The training VM should be more or less unchanged, though it's reaching time to deprecate it and the legacy ILT workflow anyway.

There are a few documentation files still to be updated, but otherwise ready for fingerpokin

@binford2k There are a couple of changes to profiles shared with the learning vm build. I'd like to have some time for testing before these changes are merged so I don't end up in a situation where I'm rushing to clean stuff up before a release. Just let me know when this is 'rc' level and I can run acceptance tests against the Learning VM.
The require bootstrap::profile::pe_master line in manifests/profile/cache_gems.pp might cause problems. Could you set up a parameter and/or conditional to manage that? Also, it looks like the gems are now kept in /var/cache/rubygems/gems instead of /var/cache/rubygems. Shouldn't be a big problem, but I'll have to double check that the configuration file on the Learning VM and nodes still points to the right place.
There are also some changes to manifests/profile/cache_rpms.pp, but on first glance it looks like the end-result should still be fine for the Learning VM. Does that sound right?

@kjhenner  $cache_dir should be unchanged. I tried to change as little that wasn't necessary: https://github.com/puppetlabs/pltraining-bootstrap/pull/312/files#diff-937f336be1cd572a7ee82ca62954ac5bL6
What's the concern with bootstrap::profile::pe_master? You're installing PE on the learning VM, right? (although, the student VM also includes that profile, so we don't want to install PE there either)

@kjhenner check the last commit. That should drop the PE dependency. I think the only reason it was in there is that Josh was piggybacking off the PE install.

@kjhenner what do we need to do in order to test this with the LVM?

ping @kjhenner

@kjhenner can you switch the Jenkins build pipelines to use the legacy branch so we can get this merged while you determine how to validate it with the LVM?

@binford2k Sorry, I didn't see this! I'll have to check my notification preferences. We can go ahead and merge when you're ready, and I can run the builds against the legacy branch if needed.

It's ready. (Not marked WIP).


Google login

@Alex-D @Grafikart
An usage of Google Bookmarks is planned ? In sync ?
Because it currently works well : the big difference with Collect.io is that bookmarks will be entirely under control, alright ?
I had already tried to develop a similar application 4 years ago, but without success.
I wish you courage and strength with this project !

Collect is not the same as Google Bookmarks since we store all things in files.
Also, design/UI/UX are optimized for visual things, not juste links. So if you want save an image, we can copy this image to your storage and a thumbnail should be displayed in the interface. Moreover, we keep some ideas for future around team work/share.


Fix typos and replace one E.Mul by E.Div

Should also be fixed in WebLab!

Thanks, fixed on WebLab too


Validator Scripts

Script Description -
Validator Scripts deal with the validation of string based data. Inspired by validator.js, it will support validation of IDs (such as Adhaar, PAN or other international identification numbers) and a few other simpler ones to validate usernames, passwords, phone numbers (with support for country-based locales).
what will change -
Addition of a new script library
Instructions

Create a new folder for your script and file/folder name should be appropriate.
Create a README.md in your folder for program Instructions
add requirements.txt if needed
add pytest/unittest if possible

Please add/delete options that are not relevant.

[x] Adding New Code
[x] Improving Documentation

Programming Language

[x] Python

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server  - https://discord.gg/FXyh2S3
Happy Coding,

We can have validator function for adhaar card called isAdhaar(string).
According to UIDAI, the adhaar must have

It should have 12 digits.
It should not start with 0 and 1.
It should not contain any alphabet and special characters.
It should have white space after every 4 digits.

For instance, if we have the adhaar number "3675 9834 6012", then the function isAdhaar("3675 9834 6012") returns true, as all the conditions are satisfied. If any of the given conditions fail, then the function returns false.

@Akshat-Mishra101 you can check similar project at
https://github.com/py-contributors/sanatio


Distributed Logging

Logging in distributed Dask environments presents unique challenges due to each worker spinning up a new Python environment, leading to the loss of any logging mechanisms established in the master node.
To address this, we're considering several approaches:
Centralized Logging with AWS CloudWatch: This is the simplest solution that would allow us to centralize all logs for easy access and analysis.
Utilizing Dask Worker Streams for Echoflow Logs: If maintaining the exact order of logs from workers is not crucial, configuring dask worker streams to handle Echoflow logs can be a straightforward fix.
Advanced Logging with Kafka and Elastic Stack: For those with the infrastructure to support it, leveraging Kafka for log aggregation and Elastic Stack for log analysis and visualization offers a robust solution.
Each of these solutions has its own set of trade-offs in terms of complexity, infrastructure requirements, and the precision of log ordering. We're exploring these options to improve our logging framework in distributed Dask setups.

Resolved with #51


armv8 not supported

BoringSSL supports arm64 android, but doesn't seem to support arm v8 for general purpose machines, which also means that clash-rs can't compile programs for arm v8 for general purpose machines because clash-rs uses BoringSSL, is that right?

Hey thanks for looking into this.
you are probably right however there seems to be certain level of support discussed in this post, not sure if that helps. https://www.amongbytes.com/post/201804-comparing-mbedtls-to-boringssl/
while I'm not an expert of this, what would be the main devices that run on arm v8 ? if that's so widely used I'm happy to consider other SSL implementations that supports more plats

Actually, I have a FriendlyELEC's CPU board, such as NanoPi R2S, where you can see its CPU and other related parameters. I want use clash-rs on it.
I usually apply it on OpenWrt, which are now common on many ARM CPU machines equipped with them. If you are willing to provide support, it would be appreciated!

i think i managed to build it on arm https://github.com/Watfaq/clash-rs/releases/tag/v0.1.8 if you want to try it out

I try v0.1.8
cannot run
on OpenWrt 23.05.0-rc3 armv8
root@OpenWrt:~# ./clash-armv7-unknown-linux-gnueabihf
./clash-armv7-unknown-linux-gnueabihf: line 1: syntax error: unexpected word (expecting ")")
root@OpenWrt:~# ./clash-armv7-unknown-linux-gnueabi
./clash-armv7-unknown-linux-gnueabi: line 1: syntax error: unexpected word (expecting ")")
root@OpenWrt:~# ./clash-aarch64-unknown-linux-gnu
-ash: ./clash-aarch64-unknown-linux-gnu: not found

on Armbian (22.08.0-trunk) aarch64
root@armbian:~# ./clash-aarch64-unknown-linux-gnu
./clash-aarch64-unknown-linux-gnu: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./clash-aarch64-unknown-linux-gnu)
./clash-aarch64-unknown-linux-gnu: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./clash-aarch64-unknown-linux-gnu)
./clash-aarch64-unknown-linux-gnu: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./clash-aarch64-unknown-linux-gnu)
root@armbian:~# ./clash-armv7-unknown-linux-gnueabi
-bash: ./clash-armv7-unknown-linux-gnueabi: No such file or directory
root@armbian:~# ./clash-armv7-unknown-linux-gnueabihf
-bash: ./clash-armv7-unknown-linux-gnueabihf: No such file or directory

Alright. I think that's back to this https://github.com/Watfaq/clash-rs/issues/90
The build is off a much newer glibc on the GitHub actions image Ubuntu 22.
Need to figure it out to support older versions.

root@OpenWrt:~# ./clash-aarch64-unknown-linux-gnu
-ash: ./clash-aarch64-unknown-linux-gnu: not found
This one does look like the file was not downloaded or something though.

root@OpenWrt:~# ./clash-aarch64-unknown-linux-gnu -ash: ./clash-aarch64-unknown-linux-gnu: not found
This one does look like the file was not downloaded or something though.

It might be a musl built system issue, ref: https://stackoverflow.com/questions/66963068/docker-alpine-executable-binary-not-found-even-if-in-path
in most of case, OpenWRTis built with musl .
# ldd
musl libc (x86_64)
Version 1.2.4
Dynamic Program Loader
Usage: ldd [options] [--] pathname

I tested it in AWS ARM64 Server, the arm8, aka aarch64, is work as expected.

@Nelocompne This is a dev build via RUSTFLAGS='-C target-feature=+crt-static' ./scripts/build.sh aarch64-unknown-linux-gnu. clash-aarch64-unknown-linux-gnu.zip
Please have a try to test whether it can run in your platfrom. thx

thank you build, it work on my openwrt :
root@OpenWrt:~/greenhat616# ./clash-aarch64-unknown-linux-gnu -h
Usage: clash-aarch64-unknown-linux-gnu [OPTIONS]

Options:
  -d, --directory <DIRECTORY>
  -c, --config <FILE>          [default: config.yaml]
  -h, --help                   Print help
  -V, --version                Print version
root@OpenWrt:~/greenhat616# ./clash-aarch64-unknown-linux-gnu -V
clash 0.1.8
root@OpenWrt:~/greenhat616# ./clash-aarch64-unknown-linux-gnu
  2023-11-24T20:14:32.269247Z  INFO clash_lib::app::inbound::network_listener: HTTP TCP listening at: <IP_ADDRESS>:8888
    at clash_lib/src/app/inbound/network_listener.rs:118

  2023-11-24T20:14:32.269400Z  INFO clash_lib: receive shutdown signal
    at clash_lib/src/lib.rs:269

root@OpenWrt:~/greenhat616# curl -x <IP_ADDRESS>:8888 https://www.bilibili.com -I
HTTP/1.1 200 OK
date: Fri, 24 Nov 2023 20:17:18 GMT

HTTP/2 200
date: Fri, 24 Nov 2023 20:17:19 GMT
content-type: text/html; charset=utf-8
support: nantianmen
vary: Origin,Accept-Encoding
expires: Fri, 24 Nov 2023 20:17:18 GMT
cache-control: no-cache
x-cache-webcdn: MISS from blzone02
x-cache-time: 0
x-save-date: Fri, 24 Nov 2023 20:17:19 GMT

i think we have found the good to build.

the static build has been attached to releases https://github.com/Watfaq/clash-rs/releases/tag/v0.1.9

new releases v0.1.9 static-crt can work on my openwrt.
so arm8 is already supported i will close this issue.


[Feature] Disable/hide numeric fields

Just as you have the "disableAlpha" property to remove alpha, I think it would be good to have a "disableFields" property to remove the fields, e.g.  <div class="vc-chrome-fields-wrap" v-if="!disableFields">
For many users, they are not geeks and don't care about numeric values of the color!
Great work, very useful, thanks!

@derekphilipau  Thanks for your feedback. I think it's resonable, and we will put it into our todo list and implement it maybe in the next version.
Of cource, contribution is welcome!  😄😄😄

My use case is probably too specific, I just want simplest RGB value possible.  Just in case someone is interested I modified the Chrome component to: a) not show an "active-color" swatch, b) not show alpha, c) button on parent controls show/hide of color component, d) button background/text color dependent upon color value.  vue-color is really nice and easy to customize, thanks!

@derekphilipau   In your case, I think using Saturation and Hue direactly to compose your component would be a better option.
And we released 2.4.3 just now. In this new release we added disableFields props to help hide the numberic fields.  Check this pr for more info.
Thanks for your feedback!


Implement relevant dialogue from all Warcraft 3 campaign missions

Night Elves: Frozen Throne

[ ] S01
[ ] S02
[ ] S03
[ ] S04
[x] S05
[ ] S06
[ ] S07
[ ] S08

what about this one

Arthas: You waste your breath, Mal'Ganis.  I heed only the voice of Frostmourne
now.
Mal'Ganis: You hear the voice of the Dark Lord.  He whispers to you through the
blade you wield.  What does he say, young human?  What dose the Dark Lord of
the Dead tell you now?
Arthas: He tells me that the time for my vengeance has come.
from human Chapter Seven: The Shores of Northrend


Explosions Destroy Aghost Items

Description

Specifically things that are given the item component that don't start out as handheld ex: piano. Everything else isn't affected.

ghosts should be immune to explosions very sus


Division by Zero in LocalOutlierFactor

The LocalOutlierFactor anomaly detector sometimes sets the k-distance to INF at https://github.com/RubixML/ML/blob/master/src/AnomalyDetectors/LocalOutlierFactor.php#L215.
Then, when using contamination and running localReachabilityDensity we take a max of the k-distances https://github.com/RubixML/ML/blob/master/src/AnomalyDetectors/LocalOutlierFactor.php#L317 and divide 1 by it, giving zero.
Lastly, this zero is used for division at https://github.com/RubixML/ML/blob/master/src/AnomalyDetectors/LocalOutlierFactor.php#L295 which gives a division by zero error.
I'm struggling to understand why I ended up with the infinite k-distance, and if it is a problem (or a peculiarity) with my data, but I keep running into this issue.

Changing to use an EPSILON if the local reachability density is zero, seems to give sensible results. I'll raise a PR in case that's an approach you'd like to take.

Thank you!


Fixed: 'Event loop is closed' while calling status from API more than once

Related Issue: https://github.com/packit-service/packit/issues/570
Description:
In the first call of the status API, the global event loop was fetched and later it was closed. The second attempt to get an event loop failed as that had been closed already which resulted in the error.
I considered two ways to fix that:
Option 1: Set a new event loop using asyncio.set_event_loop(asyncio.new_event_loop()) and then use asyncio.get_event_loop again.
Option 2: Use asyncio.run() which essentially does the same thing as option 1, but it's already available in the library for consumption.
I propose Option 2, as run is a high level call providing the exact functionality thereby saving us the trouble of managing event loops directly in our code. Also, because of the fact that it makes the code neater and more maintainable.
cc: @dhodovsk @eliskasl @lachmanfrantisek

LGTM.
I tried it and it works. Thank you!

/packit copr-build

/packit copr-build

The zuul is complaining about rebase-check. Can you please rebase?
Zuul merged the master, which means your branch is not up to date with upstream/master.
Please, rebase!

@lachmanfrantisek  Rebased

Sorry for nitpicking, but there are two more problems (I missed them in the previous CI logs):

The code format does not match the black style. (You need to run black on top of the file or use our pre-commit setup to do it for you.

reformatted /home/zuul-worker/src/github.com/packit-service/packit/packit/api.py
All done! ✨ 🍰 ✨
1 file reformatted, 79 files left unchanged.

The mypy (another check from pre-commit complains about two lines. Please, fix the typing or mark those lines with # type: ignore, if you think the types are OK.

packit/api.py:572: error: Incompatible return value type (got "Tuple[List[Tuple[int, str, str]], Dict[Any, Any], List[Any], Dict[Any, Any], List[Any]]", expected "List[Any]")
packit/api.py:583: error: Argument 1 to "run_until_complete" of "AbstractEventLoop" has incompatible type "Future[Tuple[List[Tuple[int, str, str]], Dict[Any, Any], List[Any], Dict[Any, Any], List[Any]]]"; expected "Awaitable[List[Any]]"

Thanks @lachmanfrantisek  Learnt how to use pre-commit before committing  :-)
Next commit incoming.

/packit copr-build

Thanks @lachmanfrantisek Learnt how to use pre-commit before committing :-)
Next commit incoming.

Thanks. All those checks can be misleading for newcomers, but are quite handy.

Thanks @lachmanfrantisek Learnt how to use pre-commit before committing :-)
Next commit incoming.

Thanks. All those checks can be misleading for newcomers, but are quite handy.

I have used  pydocstyle and pycodestyle for checking docstyle and linter errors. pre-commit is new to me :-)


Fixed tab icons

Fixes #1228. Also fixes the incorrect styling of the bot explorer.
===

Pull Request Test Coverage Report for Build 2387

5 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 55.489%

Totals

Change from base Build 2383:
0.03%

Covered Lines:
4899

Relevant Lines:
8322

💛  - Coveralls


[ML-Commons]

This pull request is from MICRO2023 Artifact, ID 85.

Thank you. Your CM interface is fine but I simplified it and moved your scripts and Docker file to script::reproduce-paper-m2023-85 . Please, check it out if you have time! But it's already enough for the pilot project!

Thank you. Your CM interface is fine but I simplified it and moved your scripts and Docker file to script::reproduce-paper-m2023-85 . Please, check it out if you have time! But it's already enough for the pilot project!

I checked it. Everything is fine. Thanks for your help.


Refactor rewards calculation and payment to be done in batches

Issue To Be Solved
The rewards payment transaction currently is a very long and costly transaction and should be made more efficient.
Suggest A Solution
And ideal solution would dynamically split up the rewards payments into batches that are a reasonable size based on number of delegators, expected gas usage, etc.
The FlowEpoch.EpochMetadata.rewardAmounts still needs to be stored in the current epoch's metadata every time in the same format as usual.
In FlowEpoch.heartbeat(), pay these batches over the course of successive blocks.
Open questions
Specifics about how and where to split these up most efficiently.
How do we determine the ideal size for a batch of rewards payments?
Can we make the batch size dynamically determined so we don't have to update it as the network grows and shrinks?

In this PR, , I moved the rewards calculation to the beginning of the epoch commit phase so that it freed up some computation at the end of the epoch, but haven't done it in batches yet


Pending checks aren't being labelled

Repro

Create a PR
Click show pending checks

Ext v2021.2.36004
Version: 1.54.0-insider (user setup)
Commit: 3290f9a73ba6fc3b1063ea32476067434ee91b1d
Date: 2021-02-26T05:13:29.656Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

This has since been fixed.


Introduce a context menu -> copy JSON in the JSON inspector

With the collapsible JSON extension, users lost the ability to easily copy the payload. We'll introduce functionality for them to get the JSON data on their clipboard.

Right clicking on the activity in the chat control
A button in the inspector itself allowing the user to copy the raw data
a context-menu somewhere inside the extension with the option to copy

see #1694

@mewa1024 can you comment on one of the three options we have available to us above?

I like option 2. The button should say "Copy" and have no icon (to avoid a proliferation of icons when in sidecar mode).
Longterm, can w consider another Pivot that says "RAW JSON", which allows the user switch between views, similar to this view in Firefox?

mockup:
![image](https://user-images.githubusercontent.com/39317542/61979361-7b544e80-afa8-11e9-

Note to fixer (@denscollo ):
It looks like this is already implemented for all activity types -- Activity, Trace, Command -- when the livechat session is in debug (inspector) mode:

However, it is disabled for livechat sessions in default mode. @cwhitten do you happen to know if that was an intentional design decision for inspector mode only?
If not, I don't see any harm in enabling the same context menu for activities in default mode;
The function responsible for initiating the context menu in chat.tsx can be found here and the chat saga that eventually contacts the main process to show the menu can be found here.

Let's go ahead and wire up the Copy button as @mewa1024 suggests, and show the Copy json menu item on all activity types regardless of connection mode.

Addressed in #1801


Fix field initializers not being extracted due to multiple constructors

Should resolve #32.
1.13.1 Diff

What about cases like in World?
Seems like
        this.eventListeners = Lists.newArrayList(this.pathListener);
        this.calendar = Calendar.getInstance();
        this.worldScoreboard = new Scoreboard();
        this.spawnHostileMobs = true;
        this.spawnPeacefulMobs = true;
        this.lightUpdateBlockList = new int[32768];

should be extracted too?

You are correct, and those cases should be fixed now as well. Also, while taking a closer look, I did notice that some initializers that should have not been extracted. Like field_195842_d in LibraryLWJGL3 . This should be fixed now too, and the diff has been updated to reflect the changes.

Having a look through the current diff, are IntHashMap and FoodStats correct?

Yes. I may be doing something wrong, but from what I can tell, extracting those initializers produces different bytecode. Comparing to the original indicates that they should not be extracted.
Original vs FF before

Original vs FF after


Feature/geode 6536 1: modify borrowConnection singleHop solution

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[*] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[*] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[*] Is your initial contribution a single, squashed commit?

[*] Does gradlew build run cleanly?

[*] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

The most recent change resolves the issue we were seeing in internal tests that would cause a hang. Thank you for your patience with this; it's been extremely difficult to try and reproduce the failure in a DUnit environment to allow for debugging, and I wish I had been able to provide you with a test that could help get to the root cause of the issue.


Wokspace folder was removed requires restart -> cancel leaves in strange state

Refs: #30722

Remove the first root folder
Get the Ben vacation dialog -> say cancel
The folder still gets removed and me as the user I am puzzled why was the reload even needed.

Expected -> if I press cancel the folder does not get removed

@isidorn how did you remove the first root folder?

Oh I see. The dialog is actually asking to reload the window because we need to reload the extension host (we use the first root folder as legacy root path). If you cancel that you just cancel the window reload, but not the removal of the first folder.

@bpasero yes

Wording will be improved via https://github.com/Microsoft/vscode/issues/31014


Added CNH Validation (Brazilian License Driver)

Description

Thank you!

Thanks for your contribution! I'll triage and take a look at it as soon as possible!

Closed in favor of #2234


不能在vue3上使用

@aliang888 Please use english for issues.
This library isn't prepared for Vue 3. If you'd like to implement support for Vue 3, we're open pull requests. :)


Merge origin/master onto feature/GraphingCalculator

Description of the changes:

Merge origin/master onto feature/GraphingCalculator

The number of files changed is because we used git pull instead of git merge in the past.
How changes were validated:

Manually checked each file
Verified if all changes/new files in Features/GraphingCalculator have been retained

also used the following commands to double-check:

git diff upstream/feature/graphingcalculator -- *Graph*.*
git diff upstream/feature/graphingcalculator -- *Equ*.*
git diff upstream/feature/graphingcalculator -- src/Calculator\Resources\en-US

Verified if all changes in origin/master have been retained

The simplest way to check is it create a Pull Request of this branch and select origin/master as the target.

origin/master uses winUI 2.2, while feature/GraphingCalculator used winUI 2.1. No bugs detected.

/azp run

/azp run

/azp run


Improve global container overview of the service

Here's a screenshot of the service with (only) three k8s worker nodes and not even a probe in the master node (because #1030 ):

As you can see, the edges are really tangled, plus the uncontained nodes don't tell us anything in the top-level view.
Report: service_report.json.gz
We should try to improve the rendering (yes, the never-ending problem, I wish I could provide specific suggestions).
I am not sure what we could do about the  Uncontained nodes. I think I'd rather see them expanded into process nodes with names even if it's the container view.
I think the container view makes the assumption that all your services/infrastructure is containerized, which may not be the case (like in kubernetes).
For instance, in the case of k8s, all connections go through the kube-proxy. Seeing kube-proxy instead of Uncontained would be better (at least you see what's that Unconnected node)/ However, it's not good enough because  kube-proxy handles all the connections to services, which would result in a node like:
                  _______________________
container x ---> |                      | ---> container a
container y ---> |                      | ---> container b
container z ---> |      kube_proxy      | ---> container c
        ... ---> |                      | ---> ...
                  ----------------------

In which you have no idea where an origin connection is leading. We could make use of the kubernetes information (the service IPs and to what containers they map) to improve the view to something like this:
                        /---------> container a
conteainer x ---->service1 -------> container b
                        \---------> container c

                       /----------> container a
container y ---->service2 --------> container d
                       \----------> container e

(I didn't draw a single acontainer because it's complicated with ascii art). Or even:
_____________
             |---------> container a
container x  |----------> container b
             |---------> container c
-------------

_____________
             |---------> container a
container y  |----------> container d
             |---------> container e
-------------

(if we don't want to show services), which would be much more useful from the application's perspective.
But it would be good to be able to still see the infrastructural view (i.e. the kubelet_node) if wanted.
So to summarize I think we should:

Improve rendering of crossed edges
Show information about uncontained nodes at the top level
Use semantic information to improve the view of the connections from and to the kube-proxy.

Thoughts?

The kube-proxy work is something we will need for flux too.

Related: https://github.com/weaveworks/scope/issues/606

Seems like we should treat the k8s processes as special system nodes, like we do with weave stuff.

Related: #538

I've been doing some more research and it seems that the kube-proxy spaghetti ball will be no more after kubernetes 1.2, when kube-proxy will start using the iptables mode by default (see https://github.com/kubernetes/kubernetes/blob/master/docs/user-guide/services.md#virtual-ips-and-service-proxies )
My tests (in a 1-node cluster so far) show that the iptables mode plays well with conntrack.
Kubernetes 1.2 will be released sometime in March (see https://github.com/kubernetes/kubernetes/wiki/Release-1.2). This makes eliding kube-proxy in userspace mode a much lower priority.
Our cluster service is running kubernetes 1.1.8, with kube-proxy running in userspace mode (resulting in the picture above). In order to elide kube-proxy accurately when running in userspace mode, we would need kube-proxy's port mapping information (i.e. the information printed at here https://github.com/kubernetes/kubernetes/blob/v1.1.1/pkg/proxy/userspace/proxysocket.go#L15 ) which is not publicly exposed. But, again, I am not sure this should be a priority anymore.
For reference here's my local cluster with kube-proxy running in userspace mode:

and in iptables mode:

I still need to make a test with a multinode cluster but I think Scope will work just fine with k8s>1.2

CC @monadic
@pidster @rade  Thoughts? Should we bite the bullet and make Scope work with kube-proxy in userspace mode too?

Should we still bite the bullet and make Scope work with kube-proxy in userspace mode too?

As I mentioned on slack, we need figure out how to deal with proxies in general. There are plenty of other proxies around that people use, and some of them are in userspace by necessity, i.e. the kernel does not speak HTTP.
But there seems little point in investing in scoping userspace kube-proxy, if that is not what most people will be running soon.

As I mentioned on slack, we need figure out how to deal with proxies in general. There are plenty of other proxies around that people use, and some of them are in userspace by necessity, i.e. the kernel does not speak HTTP.

I think that eliding users-pace proxies should be fairly easy once we have access to all the proxy's 4-tuples: in.RemoteAddr(), in.LocalAddr(), out.LocalAddr(), out.RemoteAddr()
The bigger problem will be getting that information.

Related #552

Related #361

+1, no point in investing in the user-space proxy.

+1, no point in investing in the user-space proxy.

Uhm, maybe not specifically on userspace kube-proxy but this is a problem we are going to face in many other scenarios (flux, nginx, custom proxies ...).
With flux (and even kube-proxy), we can add introspection APIs which tell us to what backend(s) each proxy client specifically talking to. However that doesn't scale: we cannot modify every single userspace proxy solution out there (think nginx, custom user proxies we can't control etc ...) plus it goes against Weave's philosophy of no instrumentation.
I am thinking this could be a perfect opportunity to try to use the techniques in https://github.com/weaveworks/scope/tree/master/experimental/tracer driven by a specific usecase (trying to get an ingress->egress correlation in proxies without instrumentation).
Getting this to work will be hard (if not impossible) but, if we get it right, it would be a key differentiator with other monitoring solutions out there.
Thoughts? (CC @tomwilkie )

Id say almost all decent proxies will use asynchronous io and make the
techniques in tracer useless.
If been keen to see if the layer 3 iptables based load balancing can be
intospected by scope. I can't see a way of doing the layer 7 work without
instrumentation. But in the whole one weave vein, this is definitely
something flux should do.
On Saturday, 5 March 2016, Alfonso Acosta<EMAIL_ADDRESS>wrote:

+1, no point in investing in the user-space proxy.
Uhm, maybe not specifically on userspace kube-proxy but this is a problem
we are going to face in many other scenarios (flux, nginx, custom proxies
...).
With flux (and even kube-proxy), we can add introspection APIs which tell
us to what backend(s) each proxy client specifically talking to. However
that doesn't scale: we cannot modify every single userspace proxy solution
out there (think nginx, custom user proxies we can't control etc ...) plus
it goes against Weave's philosophy of no instrumentation.
I am thinking this could be a perfect opportunity to try to use the
techniques in
https://github.com/weaveworks/scope/tree/master/experimental/tracer
driven by a specific usecase (trying to get an ingress->egress correlation
in proxies without instrumentation).
Getting this to work will be hard (if not impossible) but, if we get it
right, it would be a key differentiator with other monitoring solutions out
there.
Thoughts? (CC @tomwilkie https://github.com/tomwilkie )
—
Reply to this email directly or view it on GitHub
https://github.com/weaveworks/scope/issues/1032#issuecomment-192626936.


Tests for php artisan adminlte:username

This tests could no be executed always only after correctly executing:
php artisan adminlte:username
but this command requires interaction!

I will close this issue because is related with:
https://github.com/acacha/adminlte-laravel/issues/248
There are no test for this feature so the problem is not detected!


Browser Toolbar Technology Icon Not Displaying

Chrome Extension
Since the last update the icon in the toolbar no longer displays a technology icon, it's just the purple Wappalyzer logo.
Tech icons do show and are being properly detected when you expand the extension.
I inspected the html/background view and across multiple pages it didn't throw any errors.
Not a huge problem, but it's throwing off my 'at a glance what is this site using' flow :)

Please see #3249. You can enable the dynamic icon in the extension settings.


Case insensitive matching

When searching it should be a case sensitive match.
Question: is it faster to lowercase both and indexof? or regex with i flag?

Regex is faster.
http://fiddle.jshell.net/ptw4npuz/

Fixed in 6b44ba061cfe065df30b7e477561e6a6dd37ddad


mv on node-webgl

I would like to see mv running on WebGL canvas obtained from node-webgl module. RPGMakerMV has terrible performance when using Canvas renderer. At the same time Chrome has black listed some graphic cards/drivers. I wish to ensure that the game engine always uses WebGLRenderer. I am willing to try to port pixi.js myself (at least those features that are used by mv) to use webgl context provided by node-webl module. However, I need some help. If somebody can point me to the right direction it would be really a big help. Is it possible at all? What pixi.js requires/uses from WebGL context? How to find what is missing from context obtained through node-webgl comparing Chrome's WebGL context? Maybe it would be possible to make a thin layer - adapter that would transform a context obtained through node-webgl to something that pixi.js expects.

Hello! Sorry for late answer. Yeah, I can help with that, definitely. Can you please create issue at github.com/pixijs/pixi.js ?

Ok. I have created issue there https://github.com/pixijs/pixi.js/issues/2271


Merge linux patch

Ups, sorry... wanted to merge into my own repository

Not sure why you don't just use powershell, it works on linux

Bruh I'm dumb


Visual Studio SDK how to access commit message text box

Hi,
I was told to ask this here:
I wanted to develop an extension like this: https://marketplace.visualstudio.com/items?itemName=emilianox.flow-jira-commit-prefix but for Visual Studio 2022.
I have trouble finding out how to get access to the commit message textbox under the "Git changes" tab. The visual studio sdk documentation isn't very helpful either.
Does someone know how to go about implementing this extension?
Thanks!

@jarosal -- thank you for your feedback and question, and apologies for the late reply.
This repo is solely for documentation issues, and this seems implementation-related.  Please consider these resources:
Please consider these resources:

Ask a question or find an answer on the Microsoft Q&A page for Visual Studio.
Check the Visual Studio MSDN Forum.
Stack Overflow
Reddit

I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.


The previous focused resource group displays shortly in the FOCUSED RESOURCES view when focusing a resource group

OS: Win10/M1
Build Version: 20230727.1
Regression: Not a regression
Repro Steps:

Click "Focus Group" icon to focus a resource group -> Unfocus it.
Click "Focus Group" icon to focus another resource group.
Check whether the previous focused resource group doesn't display in the FOCUSED RESOURCES view.

Expect:
The previous focused resource group doesn't display in the FOCUSED RESOURCES view.
Actual:
The previous focused resource group displays in the FOCUSED RESOURCES view.

It's a good catch, but probably not worth the amount of time and effort required to make this fix, closing by design


remove rule react/jsx-no-target-blank the majority are internal links

As stated in eslint-plugin-react

If you do not have any external links, you can disable this rule

This rule has become more of a burden than helpful - and we're losing link attribution to our own sites.

I suppose I'm okay with removing this, but why are we using target='blank' on internal links?

Because it's a nicer experience to open a link to a new tab. They're not internal per se, but linking to a peer domain of ours. It's generally from the test runner or dashboard opening a link to the docs, so we don't want to navigate them away from the current page.

bah, did I mess up the release? forgot to use semantic release, so tried commiting a semantic msg directly to master :/

Released in 2.1.0


Merge prTesting_202011111945 branch to master branch

Docs Build status updates of commit c0d671a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Magento 2 deployed_version with Deployer Recipe

I'm running into Magento 2 problems. I'm trying to release a new version, and the deploy is completed without any errors.
I have a perfect running version 1 installed and working.
Once I do a deploy for a new version, everything is going successfully.
A directory releases/2 is created, all tasks are completed succesfully and current gets a new symlink to releases/2
Everything SEEMS well.
However, inside releases/2/pub/static/deployed_version.txt there is a NEW deployed version available, but the installation keeps referring to the old version of releases/1.
I've tried to empty cache, flush cache, chmod directories, manually emptying the directories, run setup:upgrade, setup:di:compile, new deploy of static.
Nothing happens, literally NOTHING. It keeps referring to the static files set of releases/1.
My last resort is that the problem is with deployer, but even I doubt it.
Maybe I am overlooking something, and is there someone that can help me.
`<?php
namespace Deployer;

require 'recipe/common.php';

// Project name
set('application', 'mywebsite.com');
set('default_timeout', 1800);
// Project repository
set('repository', '*GITHUB REPO*');

// [Optional] Allocate tty for git clone. Default value is false.
set('writable_use_sudo', false); // Using sudo in writable commands?
set('writable_mode', 'chmod'); // chmod, chown, chgrp or acl.
set('clear_use_sudo', false);    // Using sudo in clean commands?
set('cleanup_use_sudo', false); // Using sudo in cleanup commands?
// Configuration
set('shared_files', [
    'app/etc/env.php',
    'var/.maintenance.ip',
]);
set('shared_dirs', [
    'var/log',
    'var/backups',
    'pub/media',
]);
set('writable_dirs', [
    'var',
    'pub/static',
    'pub/media',
]);
set('clear_paths', [
    'var/generation/*',
    'var/cache/*',
    'var/page_cache/*',
    'var/composer_home/*',
    'var/di/*',
    'var/view_preprocessed/*'
]);

set('allow_anonymous_stats', false);

// Hosts - Now also includes host staging
host('production')
  ->stage('production')
  ->hostname('*HOST*')
  ->set('branch', 'master')
  ->user('*USER*')
  ->set('phpv', '/usr/local/php71/bin/php')
  ->set('deploy_path', '*PATH');

host('staging')
  ->stage('staging')
  ->hostname('*HOST*')
  ->set('branch', 'master')
  ->user('*USER*')
  ->set('phpv', 'php')
  ->set('deploy_path', '*PATH');

// Tasks
desc('Enable all modules');
task('magento:enable', function () {
    run("{{phpv}} {{release_path}}/bin/magento module:enable --all");
});
desc('Compile magento di');
task('magento:compile', function () {
    run("{{phpv}} {{release_path}}/bin/magento setup:di:compile");
    run('cd {{release_path}} && {{bin/composer}} dump-autoload -o');
});
desc('Deploy assets');
task('magento:deploy:assets', function () {
    run("{{phpv}} {{release_path}}/bin/magento setup:static-content:deploy en_US nl_NL");
})->onStage('production');
desc('Enable maintenance mode');
task('magento:maintenance:enable', function () {
    run("if [ -d $(echo {{deploy_path}}/current) ]; then {{phpv}} {{deploy_path}}/current/bin/magento maintenance:enable; fi");
});
desc('Disable maintenance mode');
task('magento:maintenance:disable', function () {
    run("if [ -d $(echo {{deploy_path}}/current) ]; then {{phpv}} {{deploy_path}}/current/bin/magento maintenance:disable; fi");
});
desc('Upgrade magento database');
task('magento:upgrade:db', function () {
    run("{{phpv}} {{release_path}}/bin/magento setup:db-schema:upgrade");
    run("{{phpv}} {{release_path}}/bin/magento setup:db-data:upgrade");
});
desc('Flush Magento Cache');
task('magento:cache:flush', function () {
    run("{{phpv}} {{release_path}}/bin/magento cache:flush");
});
desc('Reindex Magento');
task('magento:reindex', function () {
    run("{{phpv}} {{release_path}}/bin/magento cache:flush");
});

desc('Magento2 deployment operations');
task('deploy:magento', [
    'magento:enable',
    'magento:compile',
    'magento:deploy:assets',
    'magento:maintenance:enable',
    'magento:upgrade:db',
    'magento:cache:flush',
    'magento:reindex',
    'magento:maintenance:disable'
]);
desc('Deploy Magento2 project');
task('deploy', [
    'deploy:info',
    'deploy:prepare',
    'deploy:lock',
    'deploy:release',
    'deploy:update_code',
    'deploy:shared',
    'deploy:writable',
    'deploy:vendors',
    'deploy:clear_paths',
    'deploy:magento',
    'deploy:symlink',
    'deploy:unlock',
    'cleanup',
    'success'
]);
after('deploy:failed', 'magento:maintenance:disable');
`

Maybe you should reset opcache after each deploy?

Also try making sure that opcache is being cleared out, either via restarting the PHP service or using CURL to call a script.

Not an answer but I'd strongly suggest looking into https://github.com/jalogut/magento2-deployer-plus
It's a great recipe for Magento, and I've been using it for nearly two years with no major woes on its part.
You can choose to cherry-pick from there what you like or just use it as is.

I am cleaning up on issues. Fill free to reopen if needed.
Also, we have a new section available: discussions.


Good job!

Great job on the project! I've included promised-handlebars in my cms enduro.js.
No issue, just saying thank you ;-)

Thanks


etcd backup fails after fixing the invalid credentials provided for S3 and fails on local backup when two nodes are powered OFF

Rancher server: Master build from Feb 28
OS : Ubuntu
Docker: 18.09.3
Steps:

Create a single node cluster with all roles and S3 backup configured.
Create few workloads
Perform a backup(B1)
Edit the cluster and provide invalid secret key
Perform backup, it fails as expected.
Perform a restore, this also fails as S3 creds are invalid.
Edit the cluster again and provide valid credentials.
Wait for the cluster to become active.
Perform a backup.
Backup fails with the below error:

2019/02/28 19:56:14 [INFO] kontainerdriver rancherkubernetesengine stopped
2019/02/28 19:56:14 [ERROR] EtcdBackupController c-pwll6/c-pwll6-4h4fr [etcdbackup-controller] failed with : [etcd-backup] failed to perform etcd backup: Failed to start [etcd-snapshot-once] container on host [a.b.c.d]: Error response from daemon: No such container: f3b1e0fbc285d71843c58f2c706582772f293895202b7bf740e1cb386a20535b
2019/02/28 19:56:15 [INFO] [etcd] Successfully updated [etcd-snapshot-once] container on host [a.b.c.d]
2019/02/28 19:56:15 [INFO] kontainerdriver rancherkubernetesengine stopped
2019/02/28 19:56:15 [ERROR] EtcdBackupController c-pwll6/c-pwll6-bn4rv [etcdbackup-controller] failed with : [etcd-backup] failed to perform etcd backup: Can't remove Docker container [old-etcd-snapshot-once] for host [a.b.c.d]: Error: No such container: old-etcd-snapshot-once
2019/02/28 19:56:18 [INFO] kontainerdriver rancherkubernetesengine listening on address <IP_ADDRESS>:10849
2019/02/28 19:56:18 [INFO] Starting saving snapshot on etcd hosts
2019/02/28 19:56:18 [INFO] [dialer] Setup tunnel for host [a.b.c.d]
2019/02/28 19:56:18 [INFO] [etcd] Saving snapshot [c-pwll6-zpzdh] on host [a.b.c.d]
2019/02/28 19:56:19 [INFO] kontainerdriver rancherkubernetesengine listening on address <IP_ADDRESS>:10787
2019/02/28 19:56:19 [INFO] Starting saving snapshot on etcd hosts
2019/02/28 19:56:19 [INFO] [dialer] Setup tunnel for host [a.b.c.d]
2019/02/28 19:56:19 [INFO] [etcd] Successfully updated [etcd-snapshot-once] container on host [a.b.c.d]
2019/02/28 19:56:19 [INFO] kontainerdriver rancherkubernetesengine listening on address <IP_ADDRESS>:10801
2019/02/28 19:56:19 [INFO] Starting saving snapshot on etcd hosts
2019/02/28 19:56:19 [INFO] [dialer] Setup tunnel for host [a.b.c.d]
2019/02/28 19:56:19 [INFO] [etcd] Saving snapshot [c-pwll6-rqgqr] on host [a.b.c.d]
2019/02/28 19:56:19 [INFO] [etcd] Saving snapshot [c-pwll6-4h4fr] on host [a.b.c.d]
2019/02/28 19:56:20 [INFO] kontainerdriver rancherkubernetesengine stopped
2019/02/28 19:56:20 [ERROR] EtcdBackupController c-pwll6/c-pwll6-zpzdh [etcdbackup-controller] failed with : [etcd-backup] failed to perform etcd backup: Failed to take one-time snapshot, exit code [2]: time="2019-02-28T19:56:20Z" level=info msg="invoking set s3 service client"

2019/02/28 19:56:21 [INFO] kontainerdriver rancherkubernetesengine stopped
2019/02/28 19:56:21 [ERROR] EtcdBackupController c-pwll6/c-pwll6-rqgqr [etcdbackup-controller] failed with : [etcd-backup] failed to perform etcd backup: Can't rename Docker container [etcd-snapshot-once] for host [a.b.c.d]: Error response from daemon: No such container: etcd-snapshot-once
2019/02/28 19:56:21 [INFO] kontainerdriver rancherkubernetesengine stopped
2019/02/28 19:56:21 [ERROR] EtcdBackupController c-pwll6/c-pwll6-4h4fr [etcdbackup-controller] failed with : [etcd-backup] failed to perform etcd backup: Can't stop Docker container [etcd-snapshot-once] for host [a.b.c.d]: Error response from daemon: No such container: etcd-snapshot-once
2019/02/28 19:56:25 [INFO] kontainerdriver rancherkubernetesengine listening on address <IP_ADDRESS>:10947
2019/02/28 19:56:26 [INFO] Starting saving snapshot on etcd hosts
2019/02/28 19:56:26 [INFO] [dialer] Setup tunnel for host [a.b.c.d]
2019/02/28 19:56:26 [INFO] kontainerdriver rancherkubernetesengine listening on address <IP_ADDRESS>:10602
2019/02/28 19:56:26 [INFO] Starting saving snapshot on etcd hosts
2019/02/28 19:56:26 [INFO] [dialer] Setup tunnel for host [a.b.c.d]
2019/02/28 19:56:26 [INFO] [etcd] Saving snapshot [c-pwll6-zpzdh] on host [a.b.c.d]
2019/02/28 19:56:26 [INFO] [etcd] Saving snapshot [c-pwll6-rqgqr] on host [a.b.c.d]
2019/02/28 19:56:26 [INFO] kontainerdriver rancherkubernetesengine listening on address <IP_ADDRESS>:10121
2019/02/28 19:56:26 [INFO] Starting saving snapshot on etcd hosts
2019/02/28 19:56:26 [INFO] [dialer] Setup tunnel for host [a.b.c.d]
2019/02/28 19:56:26 [INFO] [etcd] Saving snapshot [c-pwll6-4h4fr] on host [a.b.c.d]
2019/02/28 19:56:26 [INFO] kontainerdriver rancherkubernetesengine stopped
2019/02/28 19:56:26 [ERROR] EtcdBackupController c-pwll6/c-pwll6-rqgqr [etcdbackup-controller] failed with : [etcd-backup] failed to perform etcd backup: Failed to create [etcd-snapshot-once] container on host [a.b.c.d]: Error response from daemon: Conflict. The container name "/etcd-snapshot-once" is already in use by container "f07ef05a4cfafdbf83b4b2826e3317ca1bca43b8beea1f2da54affc8959a78bc". You have to remove (or rename) that container to be able to reuse that name.
2019/02/28 19:56:26 [INFO] [etcd] Successfully started [etcd-snapshot-once] container on host [a.b.c.d]
2019/02/28 19:56:26 [INFO] [etcd] Successfully started [etcd-snapshot-once] container on host [a.b.c.d]
2019/02/28 19:56:27 [WARNING] Failed to remove container [Can't remove Docker container [etcd-snapshot-once] for host [a.b.c.d]: Error response from daemon: removal of container etcd-snapshot-once is already in progress]: %!!(MISSING)v(MISSING)

Local backup failure happens in the below case too:

Create a 3 node setup with all three roles in each of them
Power OFF two nodes
Perform a backup
Backup is stuck in activating state.
Server logs below:

root@soumyaupgtestserver:~# cat test.txt
2019/02/28 22:01:40 [INFO] kontainerdriver rancherkubernetesengine listening on address <IP_ADDRESS>:10584
2019/02/28 22:01:40 [INFO] Starting saving snapshot on etcd hosts
2019/02/28 22:01:40 [INFO] [dialer] Setup tunnel for host [a.b.c.d]
2019/02/28 22:01:40 [INFO] [dialer] Setup tunnel for host [d.e.f.g]
2019/02/28 22:01:40 [INFO] [dialer] Setup tunnel for host [z.x.y.a]
2019/02/28 22:01:40 [WARNING] Failed to set up SSH tunneling for host [d.e.f.g]: Can't establish dialer connection: can not build dialer to c-5bm56:m-j5wpj
2019/02/28 22:01:40 [WARNING] Failed to set up SSH tunneling for host [a.b.c.d]: Can't establish dialer connection: can not build dialer to c-5bm56:m-rz6zj
2019/02/28 22:01:40 [WARNING] Removing host [d.e.f.g] from node lists
2019/02/28 22:01:40 [WARNING] Removing host [a.b.c.d] from node lists
2019/02/28 22:01:40 [INFO] [etcd] Saving snapshot [c-5bm56-h42z9] on host [z.x.y.a]
E0228 22:01:40.736556      10 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1.ConfigMap: Get https://d.e.f.g:6443/api/v1/namespaces/cattle-system/configmaps?limit=500&resourceVersion=0&timeout=30s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
2019/02/28 22:01:40 [INFO] kontainerdriver rancherkubernetesengine stopped
2019/02/28 22:01:40 [ERROR] EtcdBackupController c-5bm56/c-5bm56-h42z9 [etcdbackup-controller] failed with : [etcd-backup] failed to perform etcd backup: Failed to create [etcd-snapshot-once] container on host [z.x.y.a]: Error response from daemon: Conflict. The container name "/etcd-snapshot-once" is already in use by container "760d055e852b63aa9f659f1a1b9ebaf7d2f480a920177a8d4f82bbbe38548cee". You have to remove (or rename) that container to be able to reuse that name.
E0228 22:01:41.675058      10 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1beta2.StatefulSet: Get https://d.e.f.g:6443/apis/apps/v1beta2/statefulsets?limit=500&resourceVersion=0&timeout=30s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
E0228 22:01:42.670670      10 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1.Pod: Get https://d.e.f.g:6443/api/v1/pods?limit=500&resourceVersion=0&timeout=30s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
E0228 22:01:42.714819      10 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1beta1.PodSecurityPolicy: Get https://d.e.f.g:6443/apis/extensions/v1beta1/podsecuritypolicies?limit=500&resourceVersion=0&timeout=30s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
E0228 22:01:42.759018      10 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1.Service: Get https://d.e.f.g:6443/api/v1/services?limit=500&resourceVersion=0&timeout=30s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
E0228 22:01:44.743911      10 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1.Job: Get https://d.e.f.g:6443/apis/batch/v1/jobs?limit=500&resourceVersion=0&timeout=30s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
E0228 22:01:45.677665      10 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1beta2.ReplicaSet: Get https://d.e.f.g:6443/apis/apps/v1beta2/replicasets?limit=500&resourceVersion=0&timeout=30s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
E0228 22:01:45.680839      10 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1.RoleBinding: Get https://d.e.f.g:6443/apis/rbac.authorization.k8s.io/v1/rolebindings?limit=500&resourceVersion=0&timeout=30s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
E0228 22:01:45.743711      10 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1.LimitRange: Get https://d.e.f.g:6443/api/v1/limitranges?limit=500&resourceVersion=0&timeout=30s: context deadline exceeded

@moelsayed : When i perform the use case,
Create a 3 node setup with all three roles in each of them
Power OFF two nodes
Perform a backup
I still see backup is stuck in activating state and backup fails
Is this fixed here ?

That test case would break the cluster. Rancher connects to the cluster nodes using the node agent.. it's how the dialer is established. In this case when the cluster got broken, the node agent died, and rancher can no longer connect to the cluster nodes.. and can't run backups..
Error waiting for container [etcd-snapshot-once] on host [x.x.x.x]: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"

So, no, you shouldn't be able to complete backups in this case since rancher will not be able to connect to the nodes.

Tested with master build from March 5th
Use case below succeeded:
Steps:
Create a single node cluster with all roles and S3 backup configured.
Create few workloads
Perform a backup(B1)
Edit the cluster and provide invalid secret key
Perform backup, it fails as expected.
Perform a restore, this also fails as S3 creds are invalid.
Edit the cluster again and provide valid credentials.
Wait for the cluster to become active.
Perform a backup.
Backup fails with the below error:


Add overlay attribute

Add overlay attribute to auto-complete directive so that if inside a container (like, for example, table) the suggestion list is outside the container and not inside. Also keep the auto-complete height to 0 as it gives unnecessary scroll when inside a container.

Coverage decreased (-0.4%) to 99.407% when pulling 799235ca7c2704b2e31c3cf63eb248f238d1d6d9 on SamarRizvi:SamarRizvi-patch-overlay into 87d0e6b695fd53d21f73357a1d3377ab569a78d0 on mbenford:master.

Coverage decreased (-0.4%) to 99.407% when pulling 267898ef2cf9949b495b651c232cd4d951a2927b on SamarRizvi:SamarRizvi-patch-overlay into 87d0e6b695fd53d21f73357a1d3377ab569a78d0 on mbenford:master.

Coverage decreased (-0.6%) to 99.211% when pulling 916c3711d58d29b69860f472c7a586794ed34c64 on SamarRizvi:SamarRizvi-patch-overlay into 87d0e6b695fd53d21f73357a1d3377ab569a78d0 on mbenford:master.

Coverage decreased (-0.6%) to 99.211% when pulling 916c3711d58d29b69860f472c7a586794ed34c64 on SamarRizvi:SamarRizvi-patch-overlay into 87d0e6b695fd53d21f73357a1d3377ab569a78d0 on mbenford:master.


Not work for app without storyboard/xib

The -[UIApplication nextResponder] will not see an available window before didFinishLaunch if you start an app with manually window setup

The fix is to add a storyboard/xib to your project.


XIONE-3594: Build breaks at VNC_FRAMEBUFFER_LIBRARIES

Risks: Low
Reason for change: Builds fail if it didnt find VNC_FRAMEBUFFER_LIBRARIES
Test Procedure: Builds are okay.
Signed-off-by: Rohith Damodaran<EMAIL_ADDRESS>

Build is verified against https://jenkins.ccp.xcal.tv/jenkins/job/SKYXIONE-Yocto-Build/45615/console
for https://gerrit.teamccp.com/#/c/502779/.
The one commit is a cherry pick of merged commit from main branch. The other two is screen capture build fix.


add_to_blacklist(): explicitly push to master

This attempts to work around the "git push.default simple" symptom.
See also http://stackoverflow.com/questions/21772279/why-is-pushing-to-matching-the-default-in-git/21772695#21772695
Example transcript:
http://chat.stackexchange.com/transcript/message/36096835#36096835

It should work, according to the sh docs: http://amoffat.github.io/sh/sections/passing_arguments.html#passing-arguments
I'm going to merge, and if it breaks something, we're in no worse of a situation than we were beforehand


Remove leading backslashes from XML formats

@ben-thul : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

thanks @ben-thul ! #sign-off


Add option to hide the group card switch

Description:
Adds an option to hide the group card switch as described in the following feature request:
https://community.home-assistant.io/t/add-option-to-hide-the-group-card-master-switch/2824
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io/pull/1516
Pull request in home-assistant-polymer (if applicable): home-assistant/home-assistant-polymer/pull/159
Example entry for configuration.yaml (if applicable):
hombot:
  name: "Hom-Bot"
  hide_switch: yes
  entities:
    - sensor.hombot_status
    - sensor.hombot_battery
    - script.hombot_clean
    - script.hombot_pause
    - script.hombot_home
    - sensor.hombot_last_clean

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

The fact that it's a switch is an implementation detail of the UI. I wonder if we want to hide control or even disallow control (so it won't respond to services either)

I don't know if this is the best solution to disalow control?

I don't like this. I love the amazing feature that we can use a group for i.e. turn_on/turn_off services.

@pvizeli how would you suggest hiding the functionality?

@pvizeli it would be configurable, so user picks it.
What about a config option called control. For now we will only support hidden but maybe in the future it can control other entities (something that @technicalpickles mentioned in that topic too)

Instead of hide_switch: yes, a show_switch key with a default to yes would probably feel more natural to new users.

@balloob yeah, 'control' is a great idea.
I don't like line 149-150. I think the attribute ATTR_CONTROL should be pass to UI and handle that only in the UI.

So 'control' instead of 'hide_switch'?

Yeah, let's stick with control and have it be set to hidden to hide it.

Top

@teodoc am I missing something or this is not working (yet) ?
I've tried to test it and it by using the below config
ha:
  name: Home Assistant
  control: hidden
  entities:
    - input_boolean.restart_hass
    - input_boolean.reboot

I've looked also on your commits and the "hidden" value of the control is only handled in your unit tests; isn't the UI also supposed to handle this hidden value and prevent the group card switch to be actually hidden ?

Config is correct. The ui part is not merged yet.
https://github.com/home-assistant/home-assistant-polymer/pull/159

K, thanks for the confirmation

Just merged it, will put out a new frontend when I get home.

Will you be able to customize the group.all_automations and group.all_scripts, group.all_xxxx to hide the "control"


New maintainers?

Hey @hallelujah, do you still need new maintainers for this project? We'd be happy to take over it @vaporware. Thanks!

@toobulkeh and @vaporware
Yes I need maintainers.
I add you and  but if you do not want to just tell me


How do I use this?

I installed the typescript-to-proptypes package as the readme explains, but do I not need to configure anything? Its not working for me by just installing the package.

Duplicate of #19


separator in legacy GO file

https://curation.pombase.org/dumps/latest_build/logs/log.2023-04-13-21-43-31.legacy_go_from_contigs
ignoring IC from value containing a pipe ("|") at line 11: GO:0006281|GO:0005739
not urgent but IC-from filed "|" separator should be allowed

We added that warning on purpose.  Does this comment still apply?: https://github.com/pombase/website/issues/1855#issuecomment-1104998992

No I need to change it to a comma, it used to be a pipe!


Fix driver loading

Making the same fix to driver loading that was applied to the JDBC
input in https://github.com/logstash-plugins/logstash-input-jdbc/pull/356
This commit also reworks the test to force driver loading in the
integration tests by removing the postgres gem as a dependency and
doing all the database setup work in an external sql script)
This fixes #34 (the fix previously applied in #31 did not work correctly)

LGTM


Managed engine SQL database with replication

Restored failed. I've been trying to restore sql database from prod to non-prod environments. Both source and destination are managed instance. In prod, I've configured Transactional replication from Managed instance database as publisher and azure SQL database as a subscriber. The issue is I cannot able to restore QA database with prod backup. It has been failing. I had to remove replication, take a backup and restore to QA.
Error:
Msg 208, Level 16, State 1, Line 48
Invalid object name 'dbo.sysextendedarticlesview'.
Cannot drop the table 'dbo.MSpeer_lsns' because it is being used for replication.
Database '29db7953-014e-XXXXX-a41d-XXXXXXXXXXXX' was restored, however an error was encountered while replication was being restored/removed. The database has been left offline. See the topic MSSQL_ENG003165 in SQL Server Books Online.
RESTORE DATABASE is terminating abnormally.
Msg 3013, Level 16, State 1, Line 48
RESTORE DATABASE is terminating abnormally.
I dont see the database offline at the destination.  Any inputs will be appreciated.

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

ID: bf165912-1223-f858-f9a5-9ff835e35da7
Version Independent ID: e376568f-5539-fee6-a91d-7eb8422f286b
Content: MSSQL_ENG003165 - SQL Server
Content Source: docs/relational-databases/replication/mssql-eng003165.md
Product: sql
Technology: replication
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

Correction: Managed Instance

Hi @SQLDBA346 , thank you for contacting Microsoft! I'm so sorry to hear you're running into issues! I really wish I could help but unfortunately this forum is intended for feedback on the documentation, and not with the product.
To get further assistance with your issue, we'd recommend engaging the community, or opening a ticket with Microsoft Support. More information can be found here: https://docs.microsoft.com/sql/sql-server/sql-server-get-help.
If you're looking to provide suggestions or ideas for improvement for the product,  you can do so at https://aka.ms/sqlfeedback.
Our apologies that the SQL Docs team was unable to assist you further with your issue, but we appreciate you reaching out. Please let us know if there's anything more we can do for you.
Thanks again and hope you have a wonderful rest of your day!
Masha from SQL Docs team


June 2024 Steering and Technical Committee (STC) meeting

Date: Wed June 19th 2024 @ 10:00pm PST (Pacific),  June 20th 2023 @ 6:00am UK @ 2:00pm China
Attendees
@msfussell (Diagrid)
@yaron2 (Diagrid)
@daixiang0 (Intel)
@paulyuk (Microsoft)
Decline/Not present
@halspang (Microsoft)
@olitomlinson (Dotmatics)
@jackzhao (Alibaba)
Action items and notes from previous meetings
May 2023 Steering and Technical Committee (STC) meeting
Add agenda items in the comments below
Agenda and Notes

Update on Dapr Graduation ToC submission. See https://github.com/cncf/toc/issues/1354
Any other topics

Completed


panic: (*zed.TypeError) with Go v1.21

I happened to let brew on my Macbook update Go to the latest version v1.21. When I later compiled my Zed binaries, one of the mdtests started failing due to what I can repro here:
$ go version
go version go1.21.0 darwin/amd64

$ zq -version
Version: v1.9.0-10-g08fc271c

$ echo '0' | zq -z 'yield error(this)' -
panic: (*zed.TypeError) 0xc0000d6ba0

goroutine 1 [running]:
github.com/brimdata/zed.(*Value).Bytes(0xc0005cf050)
	/Users/runner/zed/value.go:152 +0x1f8
github.com/brimdata/zed/zson.(*Formatter).FormatRecord(0xc0004a4990, 0xc0005cf050)
	/Users/runner/zed/zson/formatter.go:75 +0x96
github.com/brimdata/zed/zio/zsonio.(*Writer).Write(0xc0000d69a8, 0xc00041faa8?)
	/Users/runner/zed/zio/zsonio/writer.go:33 +0x25
github.com/brimdata/zed/zbuf.WriteBatch({0xbb59518, 0xc0000d69a8}, {0x28624d0?, 0xc0005cf0b0?})
	/Users/runner/zed/zbuf/batch.go:41 +0x6d
github.com/brimdata/zed/zbuf.CopyPuller({0xbb59518, 0xc0000d69a8}, {0x284d9a0, 0xc0005cf020})
	/Users/runner/zed/zbuf/batch.go:166 +0x76
github.com/brimdata/zed/cli/zq.(*Command).Run(0xc0004fe380, {0xc000112060, 0x2, 0x2})
	/Users/runner/zed/cli/zq/command.go:162 +0x76b
github.com/brimdata/zed/pkg/charm.path.run({0xc00006c238?, 0x1, 0x1}, {0xc000112060?, 0x2, 0x0?})
	/Users/runner/zed/pkg/charm/path.go:11 +0x79
github.com/brimdata/zed/pkg/charm.(*Spec).ExecRoot(0x100874b?, {0xc000112050, 0x3, 0x3})
	/Users/runner/zed/pkg/charm/charm.go:63 +0x3f
main.main()
	/Users/runner/zed/cmd/zq/main.go:11 +0x5b

However, if I stay behind on the prior Go release, it runs fine.
$ go version
go version go1.20.7 darwin/amd64

$ zq -version
Version: v1.9.0-10-g08fc271c

$ echo '0' | zq -z 'yield error(this)' -
error(0)

I know our go.mod specifies 1.20 so this was ultimately my mistake and we've done nothing yet to set incorrect expectations with users. However, I know we tend to try moving up to newer versions of tooling shortly after they're released, so I figured I'd give an early heads-up about this one.

Verified in Zed commit d55ca74.
Repeating the original repro steps, the crash no longer occurs.
$ go version
go version go1.21.1 darwin/amd64

$ zq -version
Version: v1.9.0-25-gd55ca742

$ echo '0' | zq -z 'yield error(this)' -
error(0)

However, for the moment our go.mod is still pointing at 1.20. In a group discussion @nwt explained that after he completed the fix in the linked PR he discovered that some of the Parquet boomerang tests are now failing for reasons we don't yet understand. Once that's addressed, we should be clear to go ahead and start using the latest, since we've tended to move to the latest as soon as at least one bug fix release has gone out and indeed Go 1.21.1 is now available.
Thanks @nwt!


Configure codegen

https://www.graphql-code-generator.com/docs/config-reference/codegen-config

command to run code-gen

$ yarn generate:gql

# OR

$ npm run generate:gql


Implement Raise in python

Our meeting minutes notes say:

raise: Extends the throw to have a parent expression.

However, I fail to find a throw or similar node in the CPG. What's the CPG node for this construct? Do we have something? @oxisto @konradweiss