It's not working - how to implement highcharts?

Sory for no description but I've double click enter :/

Whats not working and what have you tried?

Please, can you provide more info about your issue: browser, version of react, version of react-highcharts and a stack trace you have.

I've made npm install react-highcharts --save into my reactJS project and after that I'm trying to implement it.
I have index.html file in which i display app.js. Inside app.js I render my Main component. My Main component look like this:
var React = require('react');
var Highcharts = require('react-highcharts');
var config = {
/* HighchartsConfig */
};
var Main = React.createClass({
getInitialState: function() {
return {
config: {}
};
},
componentDidMount: function() {
var config = {
    xAxis: {
        categories: ['Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec']
    },

    series: [{
        data: [29.9, 71.5, 106.4, 129.2, 144.0, 176.0, 135.6, 148.5, 216.4, 194.1, 95.6, 54.4]
    }]

};
this.setState({
   'config':config,
});

render: function() {
return (

);
}
});
module.exports = Main;

On console I get this error:
"Uncaught Error: Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs. This usually means that you're trying to add a ref to a component that doesn't have an owner (that is, was not created inside of another component's `render` method). Try rendering this component inside of a new top-level component which will hold the ref."

Hi Sebastian,
I tried to run the example you provided, and was having a hard time of reproducing the error, several things here:

You have a file called Main.js, but I don't see where you actually require it
There are several syntactic errors, e.g.  render: function() { seems to be in the body of componentDidMount function.

Could you please take a look at the code, and update the example once you have a second?

I have large app and wanted to give an example, sory for mistakes. Here are files after corrections. What is interesting - I've implemented it on other app using import/export not require and I had no problem with that.
Here are my files
// App.js
var React = require('react');
var Highcharts = require('react-highcharts');

var config = {
  /* HighchartsConfig */
};
var App = React.createClass({
  getInitialState: function() {
    return {
        config: {}
    };
  },
  componentDidMount: function() {
    var config = {

        xAxis: {
            categories: ['Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec']
        },

        series: [{
            data: [29.9, 71.5, 106.4, 129.2, 144.0, 176.0, 135.6, 148.5, 216.4, 194.1, 95.6, 54.4]
        }]

    };
    this.setState({
       'config':config,
    });
	},
  render: function() {
        return (

              <Highcharts config = {this.state.config} />

        );
    }
});

module.exports = App;

// app.js
var React = require('react');
var App = require('./components/App');

React.render(
  <App />,
  document.getElementById('main')
);

// index.html
<!DOCTYPE html>

    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
		<title>MyApp</title>
		<link href="node_modules/bootstrap/dist/css/bootstrap.css" type="text/css" rel="stylesheet" />
		<link href="src/css/styles.css" type="text/css" rel="stylesheet" />

I'm using
  "dependencies": {
    "griddle-react": "^0.2.13",
    "jquery": "^1.11.3",
    "react": "^0.13.2",
    "react-highcharts": "^1.0.2",
    "underscore": "^1.8.3"
  },
  "devDependencies": {
    "bootstrap": "^3.3.5",
    "browserify": "^6.2.0",
    "browserify-shim": "^3.2.0",
    "http-server": "^0.6.1",
    "reactify": "^0.15.2",
    "uglify-js": "^2.4.20",
    "watchify": "^2.1.1"
  },

I found the problem however I'm not able to call component inside of another component which in this case is useless.
var React = require('react/addons');

instead of
var React = require('react');

and then I'm able to call
React.render(<Highcharts config = {config}></Highcharts>, document.body);

but only from app.js
When I'm trying to call Highcharts component from my own component I still get this error
"Uncaught Error: Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs.
This usually means that you're trying to add a ref to a component that doesn't have an owner (that is,
was not created inside of another component's `render` method). Try rendering this component inside
of a new top-level component which will hold the ref."

Hello,
I tried to reproduce it again, but everything worked for me.
2 things I did differently:

I did not include react in the html file, as it's already included in JS.
I used webpack as I'm not familiar with your browserify setup, you can try using browserify to see if that's what's causing the issue.

I created a separate branch you could play with:
https://github.com/kirjs/react-highcharts/commit/12c280d0abefaf943641beaefb11a573fec180a6

It can be useful:
"I encountered this error when a component module I was using had it's own react dependency installed. So I was using multiple versions of React.
Make sure NOT to list react under dependencies in your package.json. This is why we have peerDependencies ;-)"
http://stackoverflow.com/questions/28519287/what-does-only-a-reactowner-can-have-refs-mean

Closing, feel free to reopen if needed


Having trouble getting typing/pressing to work

I'm not sure what I'm doing wrong, I even tried to add logging in up() in lib/Input.js to see if my commands end up in there (they do).
I tried using page.keyboard.down/page.keyboard.up and page.press, while having an input/textarea element focused. But nothing got typed in the input.
I used something like: page.press("keyA")
Is there a special trick for getting these to work? Anything I can do to debug?
Thanks

did you try page.type("some text")?

I saw it, but haven't tried that or sendCharacter because I'm working from keycodes.
I tried it now and it does work.

why close? page.type() is not what I need.

page.type() sends the proper keycodes. If you aren't trying to do something fancy, page.type("a") is probably what you want. See https://github.com/GoogleChrome/puppeteer/blob/master/docs/api.md#class-keyboard

I actually am trying to do something fancy, like holding keys :)
I thought I was supposed to send the "code" you get from a keyboard event (MetaLeft, keyA, keyS).
I tried sending just "Meta" and "a" instead, tried with press/up/down and none of them work for me.

@Madd0g if you want to down "A", do
page.keyboard.down('A');

If you want to down "meta", do
page.keyboard.down('meta');

Same for up/press. Is this what you need?
We also have a lot of tests to check that keyboard works as expected. Tests run many different scenarios, you might find some of them useful.
Also, the full list of keys could be found on MDN: key values.

From reading the tests, it seems I have misunderstood press(key, [options]), I thought it was a combination of down/up (down holds a key and up releases it which causes a character to appear), but it only actually sends if text is passed as part of the options?
I see this in the tests, what does 'a' do here? The test only expects 'f' to appear.
await page.press('a', {text: 'f'});
expect(await page.evaluate(() => document.querySelector('textarea').value)).toBe('f');

Maybe I'm misunderstanding down/up as well - should the following commands result in "abc" being typed? if not - why not?
await page.down('a');
await page.up('a');
await page.down('b');
await page.up('b');
await page.down('c');
await page.up('c');

by default, down just sends a keydown, but not a corresponding input/keypress
consider
await page.keyboard.down('1', {text: '!'});

this sends the key 1, but inputs the text ! if the keydown was not canceled. Key presses and text input are related, but they aren't the same thing. Depending on your keyboard layout, stranger things could happen.

Maybe I'm misunderstanding down/up as well - should the following commands result in "abc" being typed? if not - why not?

You don't misunderstand anything, this will produce "abc".
Note though: you should use page.keyboard.down and page.keyboard.up methods, there are no page.down and page.up.  The page.press is just a shortcut for page.keyboard.down and page.keyboard.up (check out implementation).
So your snippet is equivalent to this:
await page.press('a');
await page.press('b');
await page.press('c');

Let me know if it doesn't work for you.

I see this in the tests, what does 'a' do here? The test only expects 'f' to appear.

Like you noticed, the following code snippet indeed yields "f" as a text:
await page.press('a', {text: 'f'});

Keyboard might have different functional layouts, making the same key on the keyboard produce different text. For example, consider pressing ; in two keyboard layouts: English and Spanich

in English layout, ; key yields ; (naturally)
in Spanish layout, ; key yields ñ

Consider the following example:
// Press key in english layout
await page.press(';');
// Pretend to press key in spanish layout
await page.press(';', {text: 'ñ'});

Thank you for the detailed explanations.

Note though: you should use page.keyboard.down and page.keyboard.up methods, there are no page.down and page.up. The page.press is just a shortcut for page.keyboard.down and page.keyboard.up (check out implementation).

Sorry, I have been using the correct page.press and page.keyboard.down (and up), I just messed them up in that "abc" example.

So your snippet is equivalent to this:

await page.press('a');
await page.press('b');
await page.press('c');

Let me know if it doesn't work for you.

It doesn't work. I couldn't get any press/up/down command to go through.
I was passing my own keypresses to puppeteer (at first I was passing event.code, like "MetaLeft/keyA", then I switched to event.key, which looks like "Meta" and "a").
I tried with keydown/keyup listeners (sending two commands) and with a keypress listener (sending only one) and neither approach worked. I tried sending with page.type() per Joel's suggestion and that did work, but I want to support holding modifier keys.

@Madd0g could you please share the exact script that fails to do what you want? This will help a lot with debugging.

I actually dug deeper now to see why the page.type() works while other methods don't. It uses this:
this.press(char, {text: char, delay});

It also passes the {text: char} for every keypress.
So I tried that and now press() works for me! Now my keypress (one message) does go through and gets typed, but it only works for letters, not any special keys.

Aha, new discovery! Arrows work! If I press ArrowLeft, the keyboard down/up thing works. It doesn't work with letters or modifier keys (I tried Shift/Meta). So Shift+ArrowLeft does not select text like expected, but it does move one character to the left.

I having some issues when trying to hold the Shift key and type. Ofcourse I may be doing it wrong.
  const browser = await puppeteer.launch({ headless: false })
  const page = await browser.newPage()

  await page.goto('http://localhost:4000')
  await page.focus('[name="username"]')
  await page.keyboard.down('Shift', { text: 'hello' })
  await browser.close()

Sorry it took so long, my isolated test case shows the same problems:
const puppeteer = require('puppeteer');
const assert = require('assert');

(async () => {
    let browser = await puppeteer.launch({
        headless: false, // default is true
    });

    let page = await browser.newPage();
    await page.evaluate(() => {
        let el = document.createElement('textarea');
        document.body.appendChild(el);

        el.focus();
    });
    let myValue = 'abc';
    // THIS WORKS
    // await page.type('abc');

    // THIS DOESN'T
    // await page.press('a');
    // await page.press('b');
    // await page.press('c');

    //THIS DOESN'T
    await page.keyboard.down('a');
    await page.keyboard.up('a');
    await page.keyboard.down('b');
    await page.keyboard.up('b');
    await page.keyboard.down('c');
    await page.keyboard.up('c');

    let value = await page.evaluate(() => {
        return document.getElementsByTagName('textarea')[0].value;
    });
    console.log('value is', value);
    assert.equal(value, myValue);
})();

@thetutlage Shift doesn't actually cause letters to be uppercase (sounds crazy, I know). Consider if the user had capslock pressed on their keyboard.
@Madd0g you have to specify the text that should be generated for the keypress. By default, page.press does not send an input event.
await page.press('a', {text: 'a'});

Thank you, I understand, you said it before but I did not really understand, now I do.

For the record: filed https://github.com/GoogleChrome/puppeteer/issues/723 to address keyboard API confusion.

I am also having troubles with key presses. For example, I've typed some text with type, then I want to press "Enter" in order to search for some term. However, nothing happens.

Same problem with @elenaoat .
I test page.keyboard.press() at key-event-viewer, found there is no keypress event but just only keydown and keyup event.

while press enter manually, there exist keypress event.

So anyone can tell me how can i trigger keypress event with Enter by puppeteer ?


Implement Java TestPrismRunner and PrismRunner

This PR closes https://github.com/apache/beam/issues/31967, closes https://github.com/apache/beam/issues/31935, and closes https://github.com/apache/beam/issues/31935 with a Java Prism Runner.

Resolves, downloads and executes Prism via PrismLocator/Executor
Wraps PipelineResult methods delegating to the portability module's JobServicePipelineResult

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @lostluck


Browser Hijack?

This unexpected Chrome Browser Hijack will confuse and disappoint my end users and create extra helpdesk calls for my org.  Please don't do this.
Reddit thread where I heard about this change:  https://www.reddit.com/r/sysadmin/comments/es6xp5/office_365_proplus_to_change_chromes_default/

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

 We'll update the article to make that clearer.


rest.py

Hello, if I want to try your backborn on other visual tasks, can I call rest.py directly?

No, the usage and pre-trained weights of ResT on downstream tasks, such as object detection, instance segmentation will be available on Monday.

The code and pre-trained weights of ResT on downstream tasks have been released.

OK，thanks for your reply！！！


Fix links.

Fix links to documentation that changed links.

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

#sign-off


Use speedy XOR from pion/transport

Now that we have a speedy version of xorBytes in pion/transport, we might as well use it.  Benchmarks indicate an improvement of 10% to 20% in CTR encryption speed for large blocks, depending on the architecture.
The semantics of xor.XorBytes is a little bit different from the previous version — it panics if the destination is too short, while the previous version used to truncate the output.  As far as I can tell, we never call it with a too small destination, we always use GrowBuffer beforehand.  I've removed XorTestBufferSize, which was testing this behaviour; if any further tests are necessary, they should go into the xor package.

I've now pushed the v0.13.1 tag to pion/transport. Can you try fixing up go.mod
accordingly and we'll see if that works?

Done.


Thumbnail sidebar has background with text and shapes instead of solid color

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version: Safari 15.4
Operating system and its version: Mac OS X Monterey 12.0.1
PDF.js version: 2.14.305
Is a browser extension: No

Steps to reproduce the problem:

Open this URL: https://www.usmanafzali.com/cv

What is the expected behavior? (add screenshot)
PDF sidebar has gray background.
Screenshot from Chrome 102.0.5005.61 (Mac OS X Big Sur 11.6.5)

What went wrong? (add screenshot)
PDF sidebar has text ("Title:", "Author:") and graphics (shapes and lines) in the background.

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
https://mozilla.github.io/pdf.js/legacy/web/viewer.html

Additional examples:
Steps to reproduce the problem:

Open this URL: https://muriliis.owlstown.net/cv

What went wrong? (add screenshot)
Left side of PDF has text (Pe, Au, Te) and graphics (shapes and lines) in the background.

Last example:
Steps to reproduce the problem:

Open this URL: https://www.kalinaslavkova.com/cv

What went wrong? (add screenshot)
Viewer doesn't show PDF. Instead, it shows text (File name:, File size:, Author:) and graphics (shapes and lines) in the background.

PDF.js version: 2.14.305
[...]
Open this URL: https://www.usmanafzali.com/cv
[...]
Open this URL: https://muriliis.owlstown.net/cv
[...]
Open this URL: https://www.kalinaslavkova.com/cv

Either of those URLs trigger the built-in browser PDF Viewer in both Firefox and Chrome in my testing, since an <embed>-element is being used to provide the PDF document. Hence the quoted PDF.js version number doesn't really make sense here.

Can you reproduce this with https://github.com/mozilla/pdf.js#online-demo, since I'd have hoped that PR #14984 should prevent older browsers from having trouble with <dialog>-elements?

PDF.js version: 2.14.305
[...]
Open this URL: https://www.usmanafzali.com/cv
[...]
Open this URL: https://muriliis.owlstown.net/cv
[...]
Open this URL: https://www.kalinaslavkova.com/cv

Either of those URLs trigger the built-in browser PDF Viewer in both Firefox and Chrome in my testing, since an <embed>-element is being used to provide the PDF document. Hence the quoted PDF.js version number doesn't really make sense here.

Can you reproduce this with https://github.com/mozilla/pdf.js#online-demo, since I'd have hoped that PR #14984 should prevent older browsers from having trouble with <dialog>-elements?

I also can't reproduce any of this. All links indeed trigger the built-in viewer. Closing until more information is provided (see above).


Fix bug add to structs

@yosida95 this PR fixes a bug in my previous commit. I prematurely implemented a change... "jenkins instead of Jenkins" that I will propose in a later PR. The additional changes are to add more to the existing build structs. Specifically, to allow you to inspect a build and when it is an upstream triggered build, get the relevant upstream information.

I reverted your previous PR #23 , so please do git rebase onto my master and meld all relative commits into single commit with suitable message?

Rebased on the upstream master!

Closing this, replaced with #26


Const connection config

The postgres connection does not change the connection_config thus passing it as const.
Implies 'thread safety' when using the same config for multiple connections

Looks good to me, thanks for the cleanup!


PR for Release

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

npm package (@latest dist-tag)
GitHub release
v1.3.0
v1.3.0

Your semantic-release bot :package::rocket:


[Bug] Fix prop validation warning

Context
When running the main branch, a warning shows in the console [Vue warn]: Invalid prop: custom validator check failed for prop "spokenLanguages".
Requirements

[ ] Fix it!

Dependencies

None

I no longer see this warning in the console when running the local dev environment. Considering this resolved!


Allow Domain Name creation with CertificateID

Allow API::DomainName to be created without providing CertificateBody and CertificateChain but rather a IAM CertificateID that can be used to look up the certificate in IAM. Private key still has to be provided.
Both variants must be supported.

Added in version 1.3.0


contentTemplate not working on ModalBox

//when you try to use contentTemplate the modalbox won't open.
$scope.openModalBox = function () {
var modalBoxOptions = {
//content: 'I am a modalbox created from service...',
size: 'lg',
theme: 'danger',
boxType: 'confirm',
confirmTemplate: '/app/partials/modal/add-project.html',
afterConfirm: function () {
}
}
$modalBox(modalBoxOptions);
};

contentTemplate call content would be appeded to master template. If you want to use contentTemplate, you should not set one of 'confirmTemplate', 'alertTemplate' , 'promptTemplate' or , 'template' options or if you want to set, your master template should have standart modal shell(look at template codes top of the modal.js file) and it shoul have ng-bind="content" attribute on one element.

Great! That was it, but I think I'll have to go back and try to get the regular modal to work again. Modal box, doesn't seem to support functions on the parent scope, or specifying its own controller.
Regular modal doesn't seem to support call back when modal closes (similar to afterConfirm). Doesn't seem to have access to scope or have way to pass scope in. I like how the ui-bootstrap modal works, but your looks nicer if it would just work. bummer..

$scope of modal or modalbox are child of $scope in option if defined or $rootScope you can access it easly when you manage it by js coding.
Like
...
var myModalBox = $modalBox(modalBoxOptions); //this return modalbox factory, you can access all methods and options;
var myModalScope = myModalBox.$scope;

Also, afterCustom is return the modalbox scope when you have a custom template.


intial commit

[ ] Project URL:
[ ] Update contents.json instead of README
[ ] One project per pull request
[ ] Screenshot included
[ ] Avoid iOS or open-source in description as it is assumed
[ ] Use this commit title format if applicable: Add app-name by @github-username
[ ] Use approved format for your entry

Was this a mistake?
Closing.


EE-1142: Refund percentage

Ref: https://casperlabs.atlassian.net/browse/EE-1142

First this refactors bunch of tests that used assumption that the gas refund is always 100% (i.e. after = before - gas_cost) that now does assertion based on the "transaction fee" which is the amount paid out to the proposer. This way we can in future change the gas refund % without changing tests again
Changes the finalization mechanism to use gas percentage currently hardcoded at 0%.
Note that "gas cost" of the execution result is still the amount of gas spent during execution, while we charge the user for payment code's amount

bors r+

bors r+


add changelog for the new release SSDT for VS15.8.2

First time to add changelog for the new release. A double check will be appreciated. Thanks~

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

#sign-off


Run PINOCCHIO on CSCS

Collaborate with Victor Holanda to get the PINOCCHIO workflow run properly on CSCS.

request with a working pipeline went out :)


feat(datasets): Added the Experimental SafetensorsDataset

Description
This PR adds the SafetensorsDataset to support interactions with tensors stored in files in the Safetensors format.
Fixes https://github.com/kedro-org/kedro-plugins/issues/221
Development notes
I have used the PickleDataset as a base for the implementation of this dataset (as it goes about the same manner to access files).
These changes have been tested,

Manually, by running the code locally to load and save tensors from and to Safetensors files.
Via the existing and newly added unit tests.

Checklist

[X] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[x] Updated the documentation to reflect the code changes
[ ] Added a description of this change in the relevant RELEASE.md file
[X] Added tests to cover my changes
[ ] Received approvals from at least half of the TSC (required for adding a new, non-experimental dataset)

Hey @astrojuanlu,
This is my implementation of the SafetensorsDataset. I would appreciate a review.

Thank you for the PR, @MinuraPunchihewa! It looks great to me. I tested it manually, and everything works perfectly!

Thank you, @DimedS. I appreciate it. I just updated the release notes as well.

This is going in, thanks @MinuraPunchihewa again!


elm-repl derps in read-only directories

A demonstration:
$ cd /
$ elm-repl
---- elm-repl 0.18.0 -----------------------------------------------------------
 :help for help, :exit to exit, more at <https://github.com/elm-lang/elm-repl>
--------------------------------------------------------------------------------
> 1
elm-repl: repl-temp-000.elm: openFile: permission denied (Permission denied)

If this were a bash script, I'd use one of ${TMPDIR:-/tmp} or $(mktemp -d).
Surely there's a haskell package that gives you a cross-platform tmpdir.

I think this is what you want:
https://hackage.haskell.org/package/temporary-<IP_ADDRESS>/docs/System-IO-Temp.html#v:withSystemTempDirectory


Acknowledge CRLF as possible EOL sequence for codefence

The back-end uses CRLF (\r\n) as EOL sequence for task description (reference here). In our parser, we only acknowledge LF (\n) as a possible EOL after 3 backticks fence, if it's not there, we'll append new line, this leads to a new line being added each time we edit task description.
Fixed Issues
$ https://github.com/Expensify/App/issues/38001
Tests
1. What unit/integration tests cover your change? What autoQA tests cover your change?
The ExpensiMark-HTML-test.js is updated to include the new test cases.
2. What tests did you perform that validates your changed worked?

Run the unit test.
Test in Expensify App follow these steps:

Edit a task description with code fence without line break

```task description```

Save the description
Open task descrition edit page again
Repeat step 2 and 3 several times
Verify that no extra line break is added each time saving the description

QA
1. What does QA need to do to validate your changes?
Test in Expensify App follow these steps:

Edit a task description with code fence without line break

```task description```

Save the description
Open task descrition edit page again
Repeat step 2 and 3 several times
Verify that no new description is saved

2. What areas to they need to test for regressions?
NA
Screenshots
https://github.com/Expensify/expensify-common/assets/113963320/8733ce95-7225-4918-88a7-f400dfe97201

@tienifr Seems like we have ESLint error. Pls fix it

@tienifr I mean ESLint error here. These tests above don't cover ESLint error

That line is unrelated to the code changes made in this PR, is it not?

Alright, @johnmlee101 Can you help review this PR? Thanks

Hmm? What's the issue?

Can't merge @tienifr


page reloads unmounts old components but they are destroyed in the server and still try push data

step to reproduce:

run server with 1 or more components (like clock one which updates via server events)
reload the page
see the warning  WRN handle ws request: unexpected connection close
start seeing errors every timestep the clock old clock component was updating

Error logs below
 ┌───────────────────────────────────────────────────┐
 │                    Fiber v2.2.3                   │
 │               http://<IP_ADDRESS>:9000               │
 │                                                   │
 │ Handlers ............. 4  Processes ........... 1 │
 │ Prefork .......  In components with asynchronous behavior they must contain a check for whether the component is in the exited state
func (c *Clock) Mounted(l *golive.LiveComponent) {
	go func() {
		for {
			if l.Exited {
				return
			}
			c.ActualTime = formattedActualTime()
			time.Sleep(time.Second)
			c.Commit()
		}
	}()
}

This is the code part responsible for killing components along with children: https://github.com/brendonmatos/golive/blob/d475256504d0b9d0ef9d431c3d885c40261c8363/server.go#L200

thanks @brendonmatos will see if i can help make it easy with a fix


protection50 bots

plz tell me how i make my persnal bot

Hi @muna09! Can you tell me a little more about what you're trying to achieve? What do you want your personal bot to do?

Closing due to lack of information. Feel free to comment in here with more info!


Add access-token option

Description
Add --access-token option to provide directly an access token.
Related Issue

See #63
See also #64:

After an internal discussion on your proposed change, we'd prefer to accept the --access-token as a raw string value
— comment of Brent Hosie

Motivation and Context
Provide the access-token directly is a requirement to use OAuth Server-to-Server credential, since Service Account (JWT) credentials have been deprecated.
How Has This Been Tested?

Tested with unit test

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

@mems npm install @adobe/auth-token@next has support for the new oauth-server-to-server standard. Does that meet your need?

Thank you for your contribution. Handled by #66

When we are trying to use v6.0.0-beta.11 or v6.0.0-beta.12 or v6.0.0-beta.13...
we are getting below Error :


Add module xSQLServer.Helper.psm1 in xSQLServer.psd1

Fixes #199
Add module xSQLServer.Helper.psm1 in xSQLServer.psd1
Thanks to that, no need to import this module in each resource.

This change is

Bad idea with xPDT module, revert commit.

@luigilink I will fix the tests tomorrow.

I put this PR on-hold until you have fixed the PR according to issue #199

@johlju When can we work on this PR ?
Maybe we have to focus on the remove of xPDT.psm1 first ?

I really would like to have unit testing on all resources first.
And yes, xPDT.psm1 would be good to remove as well. I'm hoping that is close though. As soon as xSQLServerSetup is working with installing SSAS into a cluster, then we can remove xSQLServerFailoverClusterSetup  When that is removed, we can change the way xSQLServerSetup is starting setup process (currently in PR). When all that is done we can remove all code in xPDT.psm1. And code coverage should increase significantly then as well.
I'm planning on testing SSAS functionality this weekend.

We need to https://github.com/PowerShell/xStorage/issues/93 into account. So we do not create the same issue with this one.

Closing this as per comment in issue https://github.com/PowerShell/xSQLServer/issues/199.


fix ffmpeg filter drawtext on the containers

Fix summary
resolves: #412
Problems Before Change
### Summary of current problems

Image
Current state

jrottenberg/ffmpeg:7.1-ubuntu2404
Filter not found

jrottenberg/ffmpeg:7.1-ubuntu2404-edge
Filter not found

jrottenberg/ffmpeg:6.1.2-ubuntu2404
Filter not found

jrottenberg/ffmpeg:6.1.2-ubuntu2404-edge
Filter not found

jrottenberg/ffmpeg-7.1-nvidi2404
Cannot find a valid font for the family Sans

jrottenberg/ffmpeg:7.1-alpine320
Filter not found

jrottenberg/ffmpeg:7.1-scratch320
Filter not found

jrottenberg/ffmpeg:7.1-vaapi2404
Filter not found

added enable-libharfbuzz, enable-libfontconfig, enable-libfribidi to ffmpeg build conf.

added COPY /usr/share/fonts,  /usr/share/fontconfig, /usr/bin/fc-* the final docker stage for fontconfig support.

added fontconfig to the packages. ( for completeness )

Os flavors:

[x]  <ffmpeg-ver>-ubuntu2404
[x] <ffmpeg-ver>-ubuntu2404-edge
<ffmpeg-ver>-vaapi2404  ( does not work here 🤷♂ , may need to be a separate PR )
[x] <ffmpeg-ver>-nvidia2404
[x] <ffmpeg-ver>-alpine320
[x] <ffmpeg-ver>-scratch320

https://github.com/user-attachments/assets/7f66444a-c9bc-4909-8c51-0fe2ab28a0ab
Convert video to smaller video
docker run --rm -v $(pwd):$(pwd) -w $(pwd) --platform="linux/amd64" ffmpeg-7.1-ubuntu2404-desktop-build:latest -i IMG_5428.MOV -ss 00:00:02 -t 00:00:01.5 -vf scale=iw/2:-2 -c:v libx264 -c:a copy outfile/solo_stove_slow_mo.mp4

Now add some text
docker run --rm -v $(pwd):$(pwd) -w $(pwd) --platform="linux/amd64" ffmpeg-7.1-ubuntu2404-desktop-build:latest -i outfile/solo_stove_slow_mo.mp4 -vf "drawtext=text='Fire !':fontcolor=orange:fontsize=48:x=(w-text_w)/2:y=(h-text_h)/4" outfile/solo_stove_slow_mo_w_text.mp4

additional details are here: https://github.com/jrottenberg/ffmpeg/issues/412#issuecomment-2466497544

@jrottenberg @Gwemox @thiagoTeams This PR is ready-for-review and  fixes the drawtext problem for

ffmpeg versions: 7.1, 7.02, 6.1.2
Os flavors:

[x]  <ffmpeg-ver>-ubuntu2404
[x] <ffmpeg-ver>-ubuntu2404-edge
[ ] <ffmpeg-ver>-vaapi2404 ( does not work here 🤷♂ , may need to be a separate PR )
[x] <ffmpeg-ver>-nvidia2404
[x] <ffmpeg-ver>-alpine320
[x] <ffmpeg-ver>-scratch320

that failed build on scratch320 for 7.0.2 should build just fine ( I suspect this was just a azure hickup )
It built successful before... must be close to the build timeout max of an hour...

@jrottenberg I stimulated a new build. They all built now.
Note: They had all built before,  but then I got the scratch320 timeout on a build.
Might need to look into making the scratch build quicker in the future,
if this build problem persists... my gut says it was a builder hickup. ( that made it slow )

Thank you again !

Thank you @jsheffie !
I'll be testing these new images soon.


Make the array buttons customizable

I would like to change the add/remove/move up/move down button widgets of an array type form. Please add this feature.

Change them how? You can turn them off using ui:options -- see the example in the Playground. Otherwise, could you please explain what kind of change you'd like to see?


Provide a more robust solution for getting the current time

The current implementations for getting the time (since boot?) are:

https://github.com/esp-rs/esp-hal/blob/v0.19.0/esp-hal/src/time.rs
https://github.com/esp-rs/esp-hal/blob/v0.19.0/esp-hal/src/timer/systimer.rs#L139-L152

These implementations unfortunately have a couple issues:

They unsafely (and unsoundly I guess) acquire access to the TIMG0/SYSTIMER peripherals to read the counters in them.
They do so assuming the peripherals have been enabled and pulled out of reset.
They also assume that the user won't reset them (again) by recreating the driver (See https://github.com/esp-rs/esp-hal/pull/1893#issuecomment-2273769315).
They also assume that the user won't change the counter values in the peripherals (which is a perfectly legitimate thing to do).

I'm not sure what the solution is yet besides simply removing these APIs, but if getting the time without direct access to a timer peripheral is that desirable, then the hal user needs to explicitly create a timer driver and give up access to one of its counters somehow, something along the lines of esp_hal_embassy::init.
Perhaps this feature doesn't belong directly in hals and should be exposed by 3rd party libraries similar to embassy_time_driver and critical_section.
Or maybe this could be like the esp_hal_embassy feature where SoftwareInterrupt<3> is inaccessible. Though this doesn't solve the enable/reset problem.

There are definitely things to improve here.

... if getting the time without direct access to a timer peripheral is that desirable ...

I think it is

They do so assuming the peripherals have been enabled and pulled out of reset.

The HAL should/could (and currently does?) guarantee that (ok - we don't enable them on boot if they are not, yet)

They also assume that the user won't reset them (again) by recreating the driver

I guess that is something the drivers need to take care of. If we really need to reset those, the driver should take care to save and restore the counters

They also assume that the user won't change the counter values in the peripherals

I think we don't offer an API for that? - if a user uses direct register manipulation for that, all our assumptions are invalid, I guess (in general true for all drivers)

They also assume that the user won't change the counter values in the peripherals

I think we don't offer an API for that? - if a user uses direct register manipulation for that, all our assumptions are invalid, I guess (in general true for all drivers)

I guess this is the main issue. As far as the user is concerned, if they have access to the TIMG0 or SYSTIMER peripheral via peripherals.TIMG0 or peripherals.SYSTIMER, then they have full ownership of the peripheral and are free to tinker with registers. The hal breaks this rule in these APIs to get the current time.

... if getting the time without direct access to a timer peripheral is that desirable ...

I think it is

Yeah I figured. Short term, it's probably best to have a esp_hal::time::init(....) that just takes an erased timer. This solves all the problems I mentioned.

In addition to the global time setup, it'd be a good idea to setup an interrupt to keep track of the timer wrapping around as well (Both SYSTIMER and TIMG can do this at least), the we can have a current time that only increments forward and doesn't wrap around.

it'd be a good idea to setup an interrupt to keep track of the timer wrapping around as well (Both SYSTIMER and TIMG can do this at least)

Unless I'm misunderstanding what part is wrapping around here, the smallest wrap around possible is ~7years, the highest being 36558 years on the esp32 - is this something real world applications really have to consider?

it'd be a good idea to setup an interrupt to keep track of the timer wrapping around as well (Both SYSTIMER and TIMG can do this at least)

Unless I'm misunderstanding what part is wrapping around here, the smallest wrap around possible is ~7years, the highest being 36558 years on the esp32 - is this something real world applications really have to consider?

Ah, I was under the impression that the wrap around number was much smaller for some reason. 36558 years is plenty.

I think the only remaining point to address here is

They do so assuming the peripherals have been enabled and pulled out of reset.

For systimer especially, it's assumed it's running


[5.4] Added "contains" operator to where clause in collections

The operator "contains" is added to \Illuminate\Support\Collection class in operatorForWhere method, so that we can search for string.

Hmm, GitHub seems to be having some issues affecting CI services.

No plans on adding this to core.


Flow Direction Raster format

The documentation in the input files mentions that we can generate flow direction from ArcMap and QGIS.
I am using QGIS and GRASS's r.fill.dir, the issue I am facing is that the coding of (agnps) mode is different to the one required in GIStoSWMM.

1 in agnps is north
1 required in GIStoSWMM is northeast

so,
Could you please share with us how you generated the raster?
as a temporary solution, I am writing a quick script to fix my coding. but curious about how to do it because it will simplify the workflow.
Thanks,
Faris

it also seems like ArcGIS pro uses a different encoding for direction.

Leaving this here in case someone needs it,
`
import rasterio
import numpy as np
with rasterio.open("flow_direction_raster.tiff") as flow:
flow_arr = flow.read(1).copy() # one here means band number 1 (the only band)
#now we define the encoding needed by GIStoSWMMM
GIStoSWMM_mapping = {
1:2,
2:3,
3:4,
4:5,
5:6,
6:7,
7:8,
8:1,
255:255 #nodata
}
# now iterate over matrix and replace values with GIStoSWMM encoding
for cell in np.nditer(flow_arr, op_flags=['readwrite']):
cell[...] = GIStoSWMM_mapping[cell.item()]
# saving the changed array into a raster
with rasterio.open("flow_direction_raster_GIStoSWMM.tif", 'w+', **flow.profile) as out:
    out.write_band(1,flow_arr)

`

Hi @schoeller,
First, I could not run this project using my data as I kept hitting a "segmentation error" that I could not figure out.
Second, it is okay to get the no slope error if you have no_data values in your raster.
Third, double-check the mapping. I think you should have 128:1 rather than 128:2 and so on.
Finally, Best of luck!
Please let me know if you succeed with running this (If you do, I will give it another try with my dataset)
I hope @tjniemi has time to review all this, as I like the idea of this project.

@FarisCS
I altered
    GIStoSWMM_mapping = {
        16:5,
        8:6,
        4:7,
        32:4,
        0:9,
        2:8,
        64:3,
        128:2,
        1:1,
        247:255 #nodata

to
        32:3,
        16:4,
        8:5,
        4:6,
        2:7,
        1:8,
        128:1,
        64:2,
        0:9,
        247:255 #nodata

Then I had to set NODATA_valueto 0 within landuse. I did likely to dem and flowdir. I then ran a modified batch and received
Report:
-> Running time: 0.0876675 minutes
-> Total number of cells: 146
-> Number of active cells: 146
-> Catchment area: 5.6865 ha
-> Catchment average elevation: 0 m
-> Catchment average slope: 0
-> Landuse information (code, number of cells, area in ha, % of catchment):
        10      54      2.3597  41.4965
        12      51      1.9333  33.9981
        14      41      1.3935  24.5054
        20      0       0       0
        30      0       0       0
        32      0       0       0
        34      0       0       0
        60      0       0       0
        62      0       0       0
        64      0       0       0

I expect non-zero average catchment elevation and suspect an error in my input ASC files. If @tjniemi  could throw an eye I be more than glad.

Excellent work!

I expect non-zero average catchment elevation and suspect an error in my input ASC files. If @tjniemi could throw an eye I be more than glad.

As for the zero here, it makes sense. since in the line linked. it checks before committing the addition for two things

that the cell's landuse value is larger than BUILT_AREA. judging from the report you posted it is not the case for all cells you have. unless the report is also incorrect?
that it is larger than no_data which assigned from the DEM,
relevant lines:

reading the noData from the raster as string
converting noValueData from Raster to double then assigning it to each cell

I did not catch that during my time with this project so good job.
I think the second check should be equality because zero or minus values are valid as an elevation value.

@schoeller
Have a good day
I am working with GisToSWMM5 and somehow new in. During my SWMM set up I got a report which is very similar to yours in terms of non-zero average catchment elevation and recognizing the landuse classes. I also guess that there is something wrong with my ASC files. I received the following report:
Report:
-> Running time: 21.4897 minutes
-> Total number of cells: 2494
-> Number of active cells: 2494
-> Catchment area: 32.9963 ha
-> Catchment average elevation: 0 m
-> Catchment average slope: 0
-> Landuse information (code, number of cells, area in ha, % of catchment):
31      0       0       0
34      0       0       0
30      0       0       0
10      2494    32.9963 100
33      0       0       0
32      0       0       0
60      0       0       0
61      0       0       0
As can be seen, only building with code 10 is recognized by the tool as sub-catchments. Additionally, catchment average elevation and slope are 0 which made me suspicious about the ASC files.
Would you let me know how you did overcome with these issues in your project?
Thank you in advance


Add credit card card holder name on create profile

@schwartzdev I will prepare an update to Gemfile.lock in dotandbo-spree now.


Markdown text in ticket does not look right when ticket is minimized on board.

Product: Contriboard
Build Version: v1.2.7
Description: Markdown text in ticket does not look right properly when not in ticket.
Reported By: Mikko Kemppinen
Steps:
1.
2.
3.
4.
Expected result:

Moved to trello . closed now


Migrate to os_log for reading iOS simulator logs

As of iOS 11 / Xcode 9, Flutter engine logs are no longer recorded in the
simulator's syslog file, which we previously read using tail -f. Instead
they're now accessible through Apple's new macOS/iOS os_log facility,
via /usr/bin/log, which supports a relatively flexible query language.
When run in non-interactive mode, /usr/bin/log buffers its output in 4k
chunks, which is significantly smaller than what's emitted up to the
point where the observatory/diagnostics port information is logged. As a
workaround we force it to run in interactive mode via the script tool.

Fixes #12085


[Feat]: Latest News on Wildlife animal

i can add section for latest news related to wildlife animal , which can dynamicly load from api

Thanks for creating the issue in WildGuard! The issue has been assigned to you.
Before you start working on your PR, please make sure to:

⭐ Star the repository if you haven't already.
Pull the latest changes to avoid any merge conflicts.
Attach before & after screenshots in your PR for clarity.

We're excited to see your contribution as part of Hacktoberfest 2024! 🎉
Don't forget to follow me on GitHub for more updates.
Happy open-source contributing! 🚀


Lots of new connection + COMMAND to slaves in Redis Cluster

Bug Report
Current Behavior
In the current Redis Cluster setup with 3 masters and 3 slaves, my java daemon is reconnecting to one of the slaves continuously. When performing a tcpdump, I constantly see a new connection being opened, a COMMAND being sent, then the connection closes again (the TCP FIN is initiated by the client).
Input Code
We're just using Spring Boot 2.0.0 with Lettuce to connect to Redis. This seems to be done by the library, since I don't have specific code here. Just using the RedisTemplates in a few places.
Expected behavior/code
I expected that the slaves are connected to once to get the cluster information and maybe a single connection to keep checking the status. I have no idea why it keeps opening and closing connections.
Environment

Lettuce version(s): 5.0.2
Redis version: 3.2.10

Additional context
We are using a lot of connections on a busy server. I'm not able to reproduce it locally when not performing a lot of actions.

I found this issue, which sound like a similar problem: https://github.com/lettuce-io/lettuce-core/issues/808
The issue is that we haven't done much configuring, just added the 3 master IP addresses to the configuration.

Possibly a duplicate of #808, depends on the actual configuration, so there can be two issues:

Lettuce periodically connects to cluster nodes to determine whether they are alive. In any case, connecting to any Redis server initiates a connection sequence which consists of a series of commands that need to be sent to determine the server's capabilities.

When you use Redis through Spring Data Redis with Cluster, then you might find that Redis Cluster connections are not shared. Please use either a connection pool as a temporary workaround or upgrade to Spring Data Redis 2.1M1 or later as Spring Data fixed a connection sharing issue with DATAREDIS-731. Without connection sharing, cluster connections are created on each command that is invoked on RedisTemplate.

Thank you for the quick response. I'll go upgrade the libraries and test this.

Just upgrading to 2.1M3 didn't work for me, it didn't change anything. Adding an explicit pool configuration did fix it though! I'm left with a question though: are the connection numbers in the config (minIdle, maxIdle and maxActive) for each node, or cumulative?
Other than that, I would say this is an improvement:

minIdle, maxIdle and maxActive are the numbers of logical connections. A Lettuce Cluster connection consists itself then of multiple physical connections:
Consider:
(number of nodes n x 2) + 1
That's the total maximum of physical connections that are bundled under a logical connection.
Closing this ticket as the issue is solved externally.

hi @marcdejonge what config did you use to get around of this issue? We have seen the same problem now and updating versions doesn't help either.


Implement local dumping

This PR brings local dumping - as in just dump from a burrow directory rather than starting a chain and dumping over GRPC. It makes things a bit less fiddly and avoids extra pointless CPU usage on a sometimes CPU-bound task (dumping).
The refactor also enable dumping from a particular height which opens the way for resumption #1142
There is also some misc house-keeping in here:

Avoiding panics by always checking for tx exceptions in burrow deploy
Fix vent options to make --txs and --blocks have an effect

CI is playing up in strange ways - we'll merge this regardless if I can get a second confirmation that make test_integration passes locally


Best way o check if item exist

Hi all,
Nice library, thanks!
I want to check if an Item with a specific ItemCode exists in SAP B1.
I do https://[servicelayer]/b1s/v1/Items('12345')?$select=ItemCode. When ItemCode 12345 exists, I will get a successful response. But when it does not exist I get an unhandled exception. Of course I can resolve this with a try-catch, but that doesn't sound like the most smooth way to check if a specific item exists. What is your advise?

Hey @CribAd how's it going? Hope well!
Actually you problably got a 404 status codes, which will thrown an exception. If you like you can modify this behavior during the request using the extension method called .AllowHttpStatus(statusCode), in your case 404.
cs       public static SLRequest AllowHttpStatus(this SLRequest request, params HttpStatusCode[] statusCodes)

Thanks, that works.

Thanks for your help, @jmartins-sh.


SPFx 1.91, office-ui-fabric-react and sp-property-pane

Category

[x] Question
[ ] Typo
[ ] Bug
[ ] Additional article idea

Hi,
I initialized a new webpart with the SPFx 1.91, and i remarked two problem in package.json :
Presence of "office-ui-fabric-react". Normaly just "sp-office-ui-fabric-core" is used on others version of SPFx, it's normal?
"sp-property-pane" isn't initialised and not used instead of "sp-webpart-base" obsolete property pane's controls.
Thanks.

Starting in v1.8.2, the SPFx solution uses Office UI Fabric React V6, which is why you see the office-ui-fabric-react in your package.json.
Also, the changes to the property pane also occurred during the 1.8 release. sp-webpart-base is deprecated in 1.8 and removed from 1.9. See release notes

Thanks.
I thinks the SPFx 1.9.1 have a little error on the Hello World initialised by Yo, the import of the sass file is 'office-ui-fabric-react/dist/sass/References.scss', not 'sp-office-ui-fabric-core/dist/sass/SPFabricCore.scss'.
With 'office-ui-fabric-react/dist/sass/References.scss' the tokens for SP theme don't work. (ex : for $ms-color-themePrimary, it's always the default blue)

Ah, now I see what you mean. I have confirmed the tokens aren't working in 1.9.1 solution.
This isn't an area of expertise for me, but it looks like the References sass file doesn't include the imports for the tokens.  I have confirmed that the themes work if you do it without the tokens.
background-color: "[theme: themePrimary, default: #0078d7]";
I've also confirmed in my testing, that by adding the import for the theme tokens into References, they will work (avoid doing this).
@StfBauer do you have any thoughts on this? Looks like a bug to me, but figured I'd ask someone more knowledgeable :)

Yes that's right. background-color: "[theme: themePrimary, default: #0078d7]" token work, but References.scss don't include this SP token and others. I thinks it's not a bug just a forgets ^^

Unclear... what's the repro?

Create a new 1.9.1 Hello World Project
Use the hosted workbench in SharePoint
Change the theme in your SharePoint site, the web part background will not change even though it's using the defaulted css
background-color: $ms-color-themePrimary;

This token worked previously when sp-office-ui-fabric-core was the default import, instead of ~office-ui-fabric-react/dist/sass/References.scss
Notes

Using themes without tokens like [theme: themePrimary, default: #0078d7] works
Including @import '~office-ui-fabric-react/dist/sass/themeOverrides.scss'; into HelloWorld.module.scss works (Seems to not be included in the default OUIFR scss module)

Expected Behavior
Given the default scss file with a SPFx project includes theme tokens such as $ms-color-themePrimary... the themes should work.

Confirmed... looks like problem is what you say, References.scss doesn't contain the theme override... but when you change your SCSS from this:
@import '~office-ui-fabric-react/dist/sass/References.scss';

to this...
@import '~office-ui-fabric-react/dist/sass/References.scss';
@import '~office-ui-fabric-react/dist/sass/themeOverrides.scss';

It works as expected...

Great!
It would be nice if that import was included in the default scaffolding. As from a documentation perspective, we wouldn't have to update a lot of the docs around theming.
However, if that's not the route to be taken, I'd be willing to do a PR for the docs affected.
Thanks for all the help!

Agreed... I've raised it internally... will see if they think it's something that should be (1) guidance & doc issue, (2) in the default project scaffolding or (3) in the references.scss file which I think would mean it would be the responsibility of the OUIFR folks since those are their packages.
I'm inclined to think it should be the last option, as it's not really SharePoint specific...

The correct file to make the theme override is:
@import '~office-ui-fabric-react/dist/sass/ThemingSass';

_reference.scss is just a partial file and shouldn't be used in your code. With this Reference, the theming worked for me.

@StfBauer So based on that, would you say the default scaffolding is wrong as it's including the reference.scss by default?

@bcameron1231 Well, it seems to be wrong in case of Scaffolding of SPO projects. You have to keep in mind that for the old projects still, the previous version (built by the SPFx team) still needs to be included.
I did a quick check in the PnP/SPFx generator:
Onprem-SPFx/SPO (not React Projects) includes still the following link:
@import<EMAIL_ADDRESS>
SPO/React now includes the following which is wrong cause like mentioned before it should be ThemingSass - Which only contains the theme slots, animations and text styles.
@import '~office-ui-fabric-react/dist/sass/References.scss';

So for SPFx projects on SPO should only use 'ThemingSass' link and not the old one for all projects. Theme slot on Office 365 are universal in SASS even if the come directly out of the 'office-ui-fabric-react' package for React.
Hope this makes sense to you.

@StfBauer : @import '~ office-ui-fabric-react / dist / sass / Theming Sass'; is not enough, it lacks variables for fonts or variables for responsive (ex: $ ms-font-size-m / $ ms-screen-max-md).
In this case, you must also add @import '~ office-ui-fabric-react / dist / sass / Fabric.scss'; but it is not a good method, this sends back full of warnings.

@PooLP You are right. I haven't checked for font styles and media queries. Last I don't use the media queries because the do not work for web parts but is a complete other story.
@import<EMAIL_ADDRESS>@import '~office-ui-fabric-react/dist/sass/ThemingSass';

When you include the 'Fabric.scss' you end up on compile 254KB ‼ Into each of your web part.
I think it is a multi-level issue. One is that we do not have any SASS / Theming variable version only anymore, similar to what we had in the 'sp-office-ui-fabric-core' package that you still get when you create an on-premises web part. This issue can be solved by just using an old version of that package.
Second, font-sizes has changed according to the Office UI Fabric 6 documentation nowadays. So the variables you mentioned are in there for legacy support reasons as it seems.
The third issue IMO we do not know when there is any change to the theming in SPO.
We currently don't have an index of all theme slots and theming variables available. (I created one in my SPFx-uifabric-themes package documentation.

Yes, for now I'm using @import<EMAIL_ADDRESS>while waiting for the problem to be solved.
The example I gave comes from a webpart that I'm updating, I still have old references for fonts.
I use UI Fabric Media Queries when I create an APP Pages or Teams Tab.
Thanks for your time and I hope that the problem will be solved in the next versions ;).

So, the new templates are available in the 1.14 beta. These templates don't use OUIFR color variables.
And for that reason the import shouldn't be changed (we could do that but as @StfBauer mentioned - it would lead to additional unnecessary 200K in each web part).


feat: unique link stores

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


boxes AssertionError

python train_net.py --num-gpus 1   --config-file configs/HICO-DET/interaction_R_50_FPN.yaml OUTPUT_DIR ./output/HICO_interaction
ERROR [09/08 16:54:57 d2.engine.train_loop]: Exception during training:
Traceback (most recent call last):
File "/opt/data/private/Code/detectron2/detectron2/engine/train_loop.py", line 141, in train
self.run_step()
File "/opt/data/private/Code/detectron2/detectron2/engine/train_loop.py", line 227, in run_step
loss_dict = self.model(data)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/opt/data/private/Code/zero_shot_hoi/lib/arch.py", line 127, in forward
proposals, proposal_losses = self.proposal_generator(images, features, gt_instances)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/opt/data/private/Code/zero_shot_hoi/lib/modeling/horpn.py", line 369, in forward
losses = {k: v * self.loss_weight for k, v in outputs.losses().items()}
File "/opt/data/private/Code/zero_shot_hoi/lib/modeling/horpn_outputs.py", line 509, in losses
gts = self._get_ground_truth()
File "/opt/data/private/Code/zero_shot_hoi/lib/modeling/horpn_outputs.py", line 389, in _get_ground_truth
anchors = [Boxes.cat(anchors_i) for anchors_i in self.anchors]
File "/opt/data/private/Code/zero_shot_hoi/lib/modeling/horpn_outputs.py", line 389, in
anchors = [Boxes.cat(anchors_i) for anchors_i in self.anchors]
File "/opt/data/private/Code/detectron2/detectron2/structures/boxes.py", line 291, in cat
assert isinstance(boxes_list, (list, tuple))
AssertionError

Have you solved this problem?


kubevirtci: Wait for cluster and calico

What this PR does / why we need it:
Some guards are missing from kubevirtci script, this change add them:

Wait for cluster readiness after creation
Wait for vms readiness
Wait for calico node pod readiness
Wait for tenant node readiness

Special notes for your reviewer:
Copied from https://github.com/kubevirt/cloud-provider-kubevirt/pull/113
It may help with e2e flakiness
Release notes:

NONE

/lgtm
/approve

/lgtm


Add more labels to issues

This change adds a hard coded list of candidate labels that can be taken
from the labels field of a ticket and added as a label to the generated
gh issue.
The list is hard coded because so many tickets have duplicate or
borderline meaningless labels that you wouldn't want to add to a
gh issue. So we hard code the list of candidate labels.

The list of additional labels is small right now of course, but as you see labels that you would like to be able to add from the ticket you can just add them to the array at the top of the file.

why you do that bot?

I saw the bot close it and I was just like "umm, ok." Hahaha


Fix issue in helm install v3

Signed-off-by: Fabian Kramm<EMAIL_ADDRESS>What this PR does / why we need it:
It is currently not possible anymore to install any remote charts in helm v3.
How to reproduce:

Run helm install any-chart https://test.com/test.tgz --debug
Produces the following output:

$ ./bin/helm install cert-manger https://test.com/test.tgz --debug
install.go:158: [debug] Original chart version: ""
Error: couldn't load repositories file (): open : no such file or directory
helm.go:81: [debug] open : no such file or directory
couldn't load repositories file ()
helm.sh/helm/pkg/repo.LoadFile
        /Users/fabiankramm/Programmieren/go-workspace/src/helm.sh/helm/pkg/repo/repo.go:52
helm.sh/helm/pkg/downloader.(*ChartDownloader).ResolveChartVersion
        /Users/fabiankramm/Programmieren/go-workspace/src/helm.sh/helm/pkg/downloader/chart_downloader.go:157
helm.sh/helm/pkg/downloader.(*ChartDownloader).DownloadTo
        /Users/fabiankramm/Programmieren/go-workspace/src/helm.sh/helm/pkg/downloader/chart_downloader.go:87
helm.sh/helm/pkg/action.(*ChartPathOptions).LocateChart
        /Users/fabiankramm/Programmieren/go-workspace/src/helm.sh/helm/pkg/action/install.go:610
main.runInstall
        /Users/fabiankramm/Programmieren/go-workspace/src/helm.sh/helm/cmd/helm/install.go:170
main.newInstallCmd.func1
        /Users/fabiankramm/Programmieren/go-workspace/src/helm.sh/helm/cmd/helm/install.go:109
helm.sh/helm/vendor/github.com/spf13/cobra.(*Command).execute
        /Users/fabiankramm/Programmieren/go-workspace/src/helm.sh/helm/vendor/github.com/spf13/cobra/command.go:762
helm.sh/helm/vendor/github.com/spf13/cobra.(*Command).ExecuteC
        /Users/fabiankramm/Programmieren/go-workspace/src/helm.sh/helm/vendor/github.com/spf13/cobra/command.go:850
helm.sh/helm/vendor/github.com/spf13/cobra.(*Command).Execute
        /Users/fabiankramm/Programmieren/go-workspace/src/helm.sh/helm/vendor/github.com/spf13/cobra/command.go:800
main.main
        /Users/fabiankramm/Programmieren/go-workspace/src/helm.sh/helm/cmd/helm/helm.go:80
runtime.main
        /usr/local/go/src/runtime/proc.go:200
runtime.goexit
        /usr/local/go/src/runtime/asm_amd64.s:1337

The problem here is that the RepositoryConfig is an empty string instead of the default location:
$ helm install --help
Global Flags:
...
      --registry-config string           path to the registry config file (default "/Users/fabiankramm/Library/Preferences/helm/registry.json")
      --repository-cache string          path to the repositories config file (default "/Users/fabiankramm/Library/Caches/helm/repository")
      --repository-config string         path to the repositories config file (default "/Users/fabiankramm/Library/Preferences/helm/repositories.yaml")
...

This PR fixes this issue by setting the RepositoryConfig and RepositoryCache fields correctly in the creation of the chartdownloader.
Special notes for your reviewer:
Helm is great, keep up the good work :)
If applicable:

[ ] this PR contains documentation
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

@FabianKramm Sorry but handled PR #6300 before your PR. Missed it somehow. Thanks for pushing the PR.
Closing as duplicate of #6300 .

@hickeyma @marckhouzam no worries, I'm just glad this issue got fixed!


Added deployment in hindi md

Added a hindi readme

any issues with the pr?

any issues with this?


List potentially missing some cool host stars

There are a few cool host stars that I would expect to be in the long list that are missing, such as LP 890-9 (T_eff = 2850 ± 75 K) and LP 791-18 (T_eff = 2960 ± 55 K). It would be good to understand what cut is excluding these targets.

This is a good question! Upon deeper investigation, it looks like both of these targets are being cut due to their J magnitudes. Currently, the long list excludes stars with Jmag > 11.5. LP 890-9 and LP 791-18 have Jmag values of 12.258 and 11.559, respectively. This is likely what is occurring for other cool hosts that may be missing from the list.
I believe that these magnitude cuts are not hard and fast rules, but were guidelines meant to encapsulate the most likely range of Pandora's capability. I would imagine that these thresholds would change over time and indeed as the instrument performance is characterized on-sky, so I'm happy to adjust these magnitude cuts, but perhaps this is worth discussing with the larger SWG.


draft documentation for Apps 0.8.0

multi-deployment manifest format
OpenFaaS support
hello-serverless quick guide
restructured the taxonomy

@justinegeffen this is now ready for your review

@aaronrothschild this is now ready for your review

@aaronrothschild @justinegeffen @hanzei ping? This is for 0.8.0.
@DHaussermann you can find the docs here for 0.8.0 testing.

@levb Is there anything blocking this PR?

I've resolved most of the open discussions on this PR. The only outstanding one is the self-managed vs. self-hosted discussion  which I'm inclined to leave to another PR as the term self-managed` is used consistently at the moment.
@levb @justinegeffen What do you think about merging the PR as it is?


Alex Kidd in the Enchanted Castle (USA).md graphic glitch

when you go in the first door the rock paper scissors game the hands are glitchy
happens in the Europe version aswell

This worked correctly in earlier versions but has been broken since v0.6.1, specifically because of this changeset: 01db12653529a86ca71c0cc82716bd5cd1db96c7
That change introduced an off-by-one error related to the sprite overflow flag in the VDP status register. In H40 mode, it's supposed to get set whenever a line contains more than 20 sprites or more than 320 sprite pixels (before accounting for overlap or whether sprites are horizontally onscreen). After that change, the sprite pixel overflow check was setting the flag at >=320 pixels instead of >320 pixels.
Alex Kidd is sensitive to this because it renders lines with exactly 320 sprite pixels and it has some logic that uses the sprite overflow flag (which is kind of unusual, most games seem to ignore it).


Ansible: Remove freetype from windows playbook

Having updated our build scripts (with #1015 and #1025) to download freetype on demand and to build during the configure phase, we no longer need freetype as an explicit dependency on windows.
This PR removes it from the playbook. Supersedes #747.

By removing this role OpenJ9 will not be able to use the windows playbooks as is for our machines setups.  Nor will any individual be able use the playbook or guide to setup a windows system.  Could the main.yml not have been modified to not call the role?

@jdekonin Apologies we weren't aware of how these were used in downstream projects.   Hmm, looks like that might need to a review step going forward.

@ali-ince Can you create a reverse PR for this?  We'll then think about how to do this with less negative impact.


Convert ExaCA to use Mist files for material properties

Currently, ExaCA has a set of material files that it pulls from in order to set material properties (resources/ExaCA/materials). To be consistent with other applications, it should ultimately use Mist files for updating material settings.
However, this depends on the ability of Mist to output ExaCA-compatible input files, so that capability needs to be implemented first. The related issue on Mist is https://github.com/ORNL-MDF/mist/issues/27.

Opened a PR on the Mist repo to add ExaCA material file generation: https://github.com/ORNL-MDF/mist/pull/30


ISPN-7073 XSD Documentation improvements

https://issues.jboss.org/browse/ISPN-7073
ISPN-7073 Update XSDoc tool
- support complexTypes with choice children
- update the Google Analytics tracking code
- generate docs only for the latest version of each namespace
- output using html format instead of XML to avoid corruption of empty tags
Also

Remove unused server schemas
Generate the html reference for server schemas

If you want to test this:
mvn clean install -DskipTests
mvn install -Pdistribution distribution

Then check in distribution/target/site/configdocs and distribution/target/site/serverconfigdocs

I've rebased this after the merge of the javadoc PR

Looking...

Looks good, let's try the new "rebase and merge button" :D

Integrated, thanks Tristan!


feat: add publish job

Added two jobs to publish to Hub and Hub Dev.
After verification on other connectors, these jobs will be moved to Fluvio repo as reusable workflows.
For cross-compilation https://github.com/cross-rs/cross is used.
Fixes #10

Should we consider publish to dev hub on any push to master, and maybe publish to prod hub on a version tag?

Should we consider publish to dev hub on any push to master, and maybe publish to prod hub on a version tag?

I wouldn't publish to dev hub on every push to master because it would produce many versions that we will need to garbage-collect. It would make our life easier if versions on dev and prod hubs were made from the same code version.
For continuous dev work, the job might be run from a branch we the package is private and versions are custom.
Allowing prod publishing only from tags is good idea, but I don't know how to actually do that on a workflow inputs level.

Should we consider publish to dev hub on any push to master, and maybe publish to prod hub on a version tag?

I wouldn't publish to dev hub on every push to master because it would produce many versions that we will need to garbage-collect. It would make our life easier if versions on dev and prod hubs were made from the same code version.
For continuous dev work, the job might be run from a branch we the package is private and versions are custom.
Allowing prod publishing only from tags is good idea, but I don't know how to actually do that on a workflow inputs level.

We can follow Fluvio repo model.  For every commit to main, we can create pre-release where artifacts will be stored in the GitHub release.   So most of steps will be similar to publish except it will be published into GitHub

Allowing prod publishing only from tags is good idea, but I don't know how to actually do that on a workflow inputs level.

on:
  push:
    tags:
      - v2
      - v1.*

To run based on a tag, it's an additional config block under "on:" triggers.  You can list patterns to match - which might be convenient to limit exactly what tags trigger the workflow.


the oauth2-integration sample of release 0.0.1 seems to be unworkable

For example, in the client module of the sample, looks like there's no request mapping for the redirect url (http://localhost:8080/authorized) defined in the below code
RegisteredClient registeredClient = RegisteredClient.withId(UUID.randomUUID().toString())
.clientId("messaging-client")
.clientSecret("secret")
.clientAuthenticationMethod(ClientAuthenticationMethod.BASIC)
.authorizationGrantType(AuthorizationGrantType.AUTHORIZATION_CODE)
.authorizationGrantType(AuthorizationGrantType.CLIENT_CREDENTIALS)
.redirectUri("http://localhost:8080/authorized")
.scope("message.read")
.scope("message.write")
.build();
spring:
thymeleaf:
cache: false
security:
oauth2:
client:
registration:
messaging-client-authorization-code:
provider: spring
client-id: messaging-client
client-secret: secret
authorization-grant-type: authorization_code
redirect-uri: "{baseUrl}/authorized"
scope: message.read,message.write
This redirect url is likely handled by the application code instead of the spring security framework, right? Not sure if I understand it correctly. Could you please have a look? Thanks!

english:
The redirect URI has returned the code to you. You can write an authorized method later
1 Exchange code post for accesstoken
2 Request with accesstoken http://localhost:8090/messages
中文：
redirect-uri 已经给你返回code 了，在client自己写一个authorized 方法就可以了
(1) 用code  post换取accesstoken
(2) 用accesstoken 请求http://localhost:8090/messages 就可以了

english:
The redirect URI has returned the code to you. You can write an authorized method later
1 Exchange code post for accesstoken
2 Request with accesstoken http://localhost:8090/messages
中文：
redirect-uri 已经给你返回code 了，在client自己写一个authorized 方法就可以了
(1) 用code post换取accesstoken
(2) 用accesstoken 请求http://localhost:8090/messages 就可以了

Thanks! But this is not what I'm looking for. Acutally I know how oauth2 works, and I just  want to see the supposed best practices in spring security and spring authorization server. It would be great if the spring team could complete the sample if it's incomplete for now, so that we can quickly evalute the server in our use cases and eventually switch to it when it becomes more mature.

@yaozou
As stated by @liangyangtao

The redirect URI has returned the code to you. You can write an authorized method later

This is correct.
The authorization code is returned to the client via the registered redirect_uri {baseUrl}/authorized, which in turn exchanges it for an access token. At the end of the authorization_code grant flow, the client will redirect to either the registered redirect_uri {baseUrl}/authorized OR the last saved request (which is what happens in the sample). See OAuth2AuthorizationCodeGrantFilter.
Closing as this sample works as expected.


feat: Support textarea

I just want to support also textarea so that I add inputType to support it.
It should be one of the input or textarea.

@yanggun7201 thanks for your contribution, could you make the changes and also add spec for this change

Can I just change README.md file? or more files?
Could you please let me know about it?
Thanks.

@yanggun7201 thanks for your contribution, could you make the changes and also add spec for this change

Can I just change README.md file? or more files?
Could you please let me know about it?
Thanks.

@yanggun7201 can you add a spec for this in ReactTags.spec.js file


Create an Animal records

Create record

{
  name: {String},
  dateAdmitted: {Date},
  condition: {String},
}

As a doctor I should be able to add nee Animals

@Sukhamjot-Singh This is a backend application. I need to create an API endpoint that accepts these details as the payload and create a record on the DB.

Okay then, my bad.
I have no experience of express.


Add codecov badge

Do you want to add travis and gitlab badges, while you are at it?

@junghans Maybe in a separate pull request. This one has been annoying. The auto correct features for .md files are not exhaustive in their formatting corrections.

Markdown has this weird rule that all list items must be tight unless any one item extends beyond 80 characters and wraps onto the next line than all items in the list must be loose. Super annoying... and kind of ugly.

Can you shorten the long ones?

I'm actually wondering if there is a way to ignore that particular rule.


Fix: empty routees cause panic  #264

when we use
	rootContext := actor.EmptyRootContext
	pid, _ := rootContext.SpawnNamed(
			router.NewRoundRobinGroup(),
			"redisRouter")
	rootContext.Send(pid, &hello{Who: "Roger"})

or
	pid, _ := rootContext.SpawnNamed(
			router.NewRandomGroup(),
			"redisRouter")
	rootContext.Send(pid, &hello{Who: "Roger"})

its cause panic, because router not check the length of routees, after repaired, it will print a log and ignore message.

@Qiaojiawei Hi sorry but it seems a quite legit fix! Just merged it, thank you very much! = )


nis code

OP-1634

I fixed it quickly @nbittich to be able to release it tonight, sorry :sweat_smile:


fix(runtime-core): withDefaults & union types

Improves typing of props when using union types in combination with withDefaults.
Fixes

https://github.com/vuejs/core/issues/11758
https://github.com/vuejs/core/issues/8952

Affects
https://github.com/vuejs/core/issues/9125
Explanation
We can skip the Omit<T, Defaults> in
Readonly<Omit<T, keyof Defaults>>

because we're overloading the omitted keys with key/value of Defaults and the mapped type modifier anyways:
  & {
    readonly [K in keyof Defaults as K extends keyof T ? K : never]-?: ...

/ecosystem-ci run

#9125, #11758, and #8952 are all runtime issues. This PR doesn't really solve them.

@edison1105 what's the runtime issue of https://github.com/vuejs/core/issues/11758 and https://github.com/vuejs/core/issues/8952?

@davidmatter

#11758, on the surface, seems to address a type hint issue, but at the runtime will still validate the required props. see playground, it will still show the warning Missing required prop: 'sum' because both quantity and sum are required. #9125 has the same problem.
#8952 expects appearance to be required and limited to outline when color: 'white', but in the compiled code, appearance: { type: String, required: false }, appearance is not required. This feature might be achievable in language-tools, but for users not using TypeScript, generating a validation method would be a better solution. like:

  color:{
    type:String,
    validator:(value, props)=>{
      if(value==='white'){
        return props.appearance === 'outline'
      }else{
        //...
      }
    }
  },

Ah, yes. Thanks for the clarification. I think I will use this PR to add the needed runtime changes. Btw: My assumption is that changing the props options interface to allow computed required would be even better than "misusing" prop validators for this. With computed require we could just generate simple logic based on the TS union type definition.
...
  required?: boolean | ((props: Data) => boolean)
...

The following behavior in the compiler will need to be changed as well.
 case 'TSUnionType':
 case 'TSIntersectionType':
      return mergeElements(
        node.types.map(t => resolveTypeElements(ctx, t, scope, typeParameters)),
        node.type,
      )


Can't figure out how to auth

Hi,
I'm trying to authenticate my Twitch application which I made through https://dev.twitch.tv/console/apps by adding its client ID as clientId and client secret as token in options but it returns "AuthenticationError [TwitchJSAuthenticationError]: Login authentication failed". Am I misunderstanding the process?
Kind regards

The client secret is not the token. To obtain a token, please read this.

Thank you, I got a better hang of it now.
While attempting to connect to the chat using the following, I get a "Promise timed out after 5000 milliseconds error".
const chat = twitchClient.chat;
await chat.connect(); // error triggers here
await chat.join(channelName);


Support Kubernetes deployment

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
As a user, I'd like to deploy Toolpad on Kubernetes.
Examples 🌈
Here is an example of how Toolpad could be deployed on Kubernetes:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: toolpad
spec:
  replicas: 1
  selector:
    matchLabels:
      app: toolpad
  template:
    metadata:
      labels:
        app: toolpad
    spec:
      containers:
      - name: toolpad
        image: muicom/toolpad:latest
        env:
        - name: TOOLPAD_DATABASE_URL
          value: postgresql://toolpad-app:secretpw@postgres:5432/postgres?connect_timeout=10
        - name: PORT
          value: '3000'
        - name: TOOLPAD_EXTERNAL_URL
          value: http://localhost:3000/
        ports:
        - containerPort: 3000
          name: toolpad

Motivation 🔦
Kubernetes is a popular container orchestration platform that is widely used in production environments. It would be useful to have support for deploying Toolpad on Kubernetes, so that users can try it on that platform.

@chanwit First of all, my apologies for waiting so long to get back to you. Over the past weeks we've been reflecting on the future of Toolpad and decided to make some changes on the product level. Toolpad wants to be closer integrated in your existing codebases, therefore it will be distributed as a npm package instead and support loading parts of your existing codebase.
If you're still using Toolpad, or consider using it in the future, @prakhargupta1 and I would love to have a chat with you about your use-cases.

Closing this issue as we've stopped building docker images by default as part of https://github.com/mui/mui-toolpad/discussions/1748


Usage of this work

Thank you for your excellent work! I'm wondering how to use this work to combine with a Faster R-CNN object detection network based on detectron2?

@CtCCtV you can reference maskrcnn https://github.com/facebookresearch/detectron2/blob/main/configs/common/models/mask_rcnn_fpn.py


GCM MAC computation for AES-GCM

Hi,
I would like to use OpenSSH in FIPS mode with FIPS capable OpenSSL. I saw #3216 and #4157 and i have some questions.
In #4157, @srahul123 explains that aes256-gcm is affected by this issue but he tried to solve it modifying gcm128.c file. Are aes128-gcm and aes256-gcm both affected?
If I configure OpenSSH adding<EMAIL_ADDRESS>in the "Ciphers" option, do you know i am concerned by this issue? Are GCM MAC computed anyway?

It is likely that AES128-GCM is also affected.  We are not supporting the current FIPS code, it is "frozen"  We are working on a new FIPS version for the next release.  If you modify the current code in any way, you cannot claim to be FIPS compliant, sorry.


docs: update startup instructions

This PR updates the LNDK startup instructions to note two things:

LND v0.18.0 is required.
The dev flag is no longer required.

Closes #135 and #108


not found weight file

Build the image according to the dockerfile file, then run the container. Error: IsADirectoryError: [Errno 21] Is a directory: '/tmp/ckpt', it should be that there is no weight file in the directory '/tmp/ckpt'. Did not a weight file be generated when building the image? How to solve this problem?

[root@iZwz9fjpavyfd2ybhfxx1lZ gemma_pytorch]# docker run -t --rm \

-v /tmp/ckpt:/tmp/ckpt \
gemma:pytorch \
python scripts/run.py \
--ckpt=/tmp/ckpt \
--variant="2b" \
--prompt="The meaning of life is"

Traceback (most recent call last):
File "/workspace/gemma/scripts/run.py", line 79, in
main(args)
File "/workspace/gemma/scripts/run.py", line 48, in main
model.load_weights(args.ckpt)
File "/workspace/gemma/gemma/model.py", line 562, in load_weights
torch.load(
File "/opt/conda/lib/python3.10/site-packages/torch/serialization.py", line 986, in load
with _open_file_like(f, 'rb') as opened_file:
File "/opt/conda/lib/python3.10/site-packages/torch/serialization.py", line 435, in _open_file_like
return _open_file(name_or_buffer, mode)
File "/opt/conda/lib/python3.10/site-packages/torch/serialization.py", line 416, in init
super().init(open(name, mode))
IsADirectoryError: [Errno 21] Is a directory: '/tmp/ckpt'

Hi @Cguanqin, have you downloaded the checkpoint from Kaggle or HuggingFace Hub before running the docker?
You can follow the instruction here to get the checkpoint. https://www.kaggle.com/models/google/gemma/frameworks/pyTorch

I have confirmed that I have downloaded the model, but I am still encountering this error regardless of whether I specify the path where the model was downloaded or the path to the model file itself.

Hi @Cguanqin,
Could you please confirm if this issue is resolved for you with the above comment ? Please feel free to close the issue if it is resolved ?
Thank you.

Hi @Cguanqin,
Closing this issue due to lack of recent activity,  Please feel free reopen if this is still a valid request.
Thank you!


Grpc Async Client Call

This PR tries to address the following:

Change the GRPC client call from ACA from synchronous to asynchronous, by using different threads to call NCM and process GoalState(s) returned from NCM, in order to make ACA's on-demand functionality un-blocking.
Modified GRPC client test code from sync to async, to test && prove the feasibility of async calls.

Current results:
ACA is able to call NCM asynchronously, and so far it looks like that the on-demand workflow goes as usual.

The above screenshot shows port_1, which is on host_one and has an IP of <IP_ADDRESS>, was able to ping <IP_ADDRESS>, which is another port inside of another host, after ACA on host_one requested the needed GoalStates from the NCM.
Next:
Need to test scenarios in which multiple ports are involved, to see if the change really works.

Update where on-demand-engine sleeps, so it can wait until goalstates are updated before processing the packet.
Updated ping test speed, notice that the first ping packet went through much faster than the first picture:

Unit tests passed:
root@dcf1e7a6a94b:/mnt/host/code# ./build/tests/aca_tests
Trying to init a new sub to connect to the NCM
[==========] Running 51 tests from 10 test suites.
[----------] Global test environment set-up.
[----------] 5 tests from dhcp_config_test_cases
[ RUN      ] dhcp_config_test_cases.add_dhcp_entry_valid
****** a lot of outputs that were deleted as length of content is limited******
[       OK ] zeta_programming_test_cases.delete_zeta_config_valid (8 ms)
[----------] 2 tests from zeta_programming_test_cases (21 ms total)

[----------] 5 tests from arp_config_test_cases
[ RUN      ] arp_config_test_cases.add_arp_entry_valid
Arp Entry with ip: <IP_ADDRESS> and vlan id 1201 added
[       OK ] arp_config_test_cases.add_arp_entry_valid (0 ms)
[ RUN      ] arp_config_test_cases.add_arp_entry_invalid
Arp Entry with ip: <IP_ADDRESS> and vlan id 1201 added
Entry already existed! (ip = <IP_ADDRESS> and vlan id = 1201)
[       OK ] arp_config_test_cases.add_arp_entry_invalid (0 ms)
[ RUN      ] arp_config_test_cases.delete_arp_entry_valid
Entry already existed! (ip = <IP_ADDRESS> and vlan id = 1201)
[       OK ] arp_config_test_cases.delete_arp_entry_valid (0 ms)
[ RUN      ] arp_config_test_cases.update_arp_entry_valid
Arp Entry with ip: <IP_ADDRESS> and vlan id 1201 added
[       OK ] arp_config_test_cases.update_arp_entry_valid (0 ms)
[ RUN      ] arp_config_test_cases.update_arp_entry_invalid
Entry not exist! (ip = <IP_ADDRESS> and vlan id = 1201)
Arp Entry with ip: <IP_ADDRESS> and vlan id 1201 added
[       OK ] arp_config_test_cases.update_arp_entry_invalid (0 ms)
[----------] 5 tests from arp_config_test_cases (0 ms total)

[----------] 1 test from arp_request_test_cases
[ RUN      ] arp_request_test_cases.arps_recv_valid
[       OK ] arp_request_test_cases.arps_recv_valid (0 ms)
[----------] 1 test from arp_request_test_cases (0 ms total)

[----------] Global test environment tear-down
[==========] 51 tests from 10 test suites ran. (4190 ms total)
[  PASSED  ] 51 tests.

  YOU HAVE 21 DISABLED TESTS

==========INIT TIMES:==========
g_initialize_execute_system_time = 192704 microseconds or 192 milliseconds
g_initialize_execute_ovsdb_time = 136118 microseconds or 136 milliseconds
g_initialize_execute_openflow_time = 49656 microseconds or 49 milliseconds
==========EXECUTION TIMES:==========
g_total_execute_system_time = 827784 microseconds or 827 milliseconds
g_total_execute_ovsdb_time = 366614 microseconds or 366 milliseconds
g_total_execute_openflow_time = 263328 microseconds or 263 milliseconds
==========UPDATE GS TIMES:==========
g_total_update_GS_time = 680836 microseconds or 680 milliseconds
Program exiting, cleaning up...
ACA_Zeta_Programming::clear_all_data ---> Entering
ACA_Zeta_Programming::clear_all_data <--- Exiting
ACA_OVS_L2_Programmer::execute_openflow_command ---> Entering
Executing command: ovs-ofctl del-flows br-tun "arp,arp_op=1"
Command succeeded!
 Elapsed time for system command took: 3202 microseconds or 3 milliseconds.
Elapsed time for openflow client call took: 3295 microseconds or 3 milliseconds. rc: 0
ACA_OVS_L2_Programmer::execute_openflow_command <--- Exiting, rc = 0
ACA_OVS_L2_Programmer::execute_openflow_command ---> Entering
Executing command: ovs-ofctl del-flows br-int "udp,udp_src=68,udp_dst=67"
Command succeeded!
 Elapsed time for system command took: 3203 microseconds or 3 milliseconds.
Elapsed time for openflow client call took: 3299 microseconds or 3 milliseconds. rc: 0
ACA_OVS_L2_Programmer::execute_openflow_command <--- Exiting, rc = 0

DISABLED_grpc_client_connectivity_test result:
/zzxgzgz/alcor-control-agent# ./build/tests/aca_tests --gtest_also_run_disabled_tests --gtest_filter=*DISABLED_grpc_client_connectivity_test -a <IP_ADDRESS> -p 54321
Trying to init a new sub to connect to the NCM
Note: Google Test filter = *DISABLED_grpc_client_connectivity_test
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from aca_on_demand_testcases
[ RUN      ] aca_on_demand_testcases.DISABLED_grpc_client_connectivity_test
After initing a new sub to connect to the NCM
Streaming capable GRPC server listening on <IP_ADDRESS>:
Start of DISABLED_grpc_client_connectivity_test
Made sure that g_grpc_server is not null
Channel state: 0
Request one's request ID: 12345
Request two's request ID: 54321
Beginning of process_async_grpc_replies
Inside the while loop, counter: 1
This call is OK
Static cast done successfully
Got an GRPC reply that is OK, need to process it.
This reply has request ID: 54321
Return from NCM - Reply Status: 1
Inside the while loop, counter: 2
This call is OK
Static cast done successfully
Got an GRPC reply that is OK, need to process it.
This reply has request ID: 12345
Return from NCM - Reply Status: 0
[       OK ] aca_on_demand_testcases.DISABLED_grpc_client_connectivity_test (10002 ms)
[----------] 1 test from aca_on_demand_testcases (10002 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (10002 ms total)
[  PASSED  ] 1 test.
==========INIT TIMES:==========
g_initialize_execute_system_time = 0 microseconds or 0 milliseconds
g_initialize_execute_ovsdb_time = 0 microseconds or 0 milliseconds
g_initialize_execute_openflow_time = 0 microseconds or 0 milliseconds
==========EXECUTION TIMES:==========
g_total_execute_system_time = 0 microseconds or 0 milliseconds
g_total_execute_ovsdb_time = 0 microseconds or 0 milliseconds
g_total_execute_openflow_time = 0 microseconds or 0 milliseconds
==========UPDATE GS TIMES:==========
g_total_update_GS_time = 0 microseconds or 0 milliseconds
Program exiting, cleaning up...

Future improvement:
Right now, the on-demand engine, after receiving the operation status from NCM, sleeps for a period of time, with the hope of it waking up with the needed goalstate(s) received and applied.
This leads to, in many cases, a long time for the first packet to go out(around 1000ms). In some cases, when only sending 1 packet to the destination, the packet got timed out eventually; in other lucky case, all first packets were sent out in less than 2 ms (https://github.com/futurewei-cloud/alcor/pull/560#issuecomment-827190398).
I believe this highly depends on the connection between ACAs and the NCM, and how fast NCM sends back data. If it is fast enough, then on-demand engine wakes up with needed goalstates, it sends out the packet really quickly; otherwise, it is slow.
Possible solutions:

Change the reply message from the NCM, to include the goalstates needed, but it will break out intent to let only one thread to take care of the goalstates.
Find out a way to let the on-deand engine know that the goalstate has been received and applied, and it can go ahead and let the packet out.

Added time measurement for request_uuid_on_demand_payload_map, below are some example outputs:
Cleaned up [0] entries in the map, which took [9]us, which is [0]ms

Inserting one entry into request_uuid_on_demand_payload_map took [3]us, which is [0]ms

Erasing one entry into request_uuid_on_demand_payload_map took [3]us, which is [0]ms

Also, a new variable called REQUEST_UUID_ON_DEMAND_PAYLOAD_MAP_MAX_SIZE can be found in include/aca_config.h. This variable defines the maximum size of request_uuid_on_demand_payload_map. Before an entry is inserted into request_uuid_on_demand_payload_map, the on-demand engine checks its current size, and waits until the size is less than the max size.


cpma.log.json is not a valid json

Example:
{
  "level": "error",
  "msg": "Unable to read private key: ",
  "time": "2019-06-06T16:31:59+02:00"
}
{
  "level": "error",
  "msg": "Unable to read private key: ",
  "time": "2019-06-06T16:31:59+02:00"
}
{
  "level": "error",
  "msg": "Unable to read private key: ",
  "time": "2019-06-06T16:31:59+02:00"
}
{
  "level": "error",
  "msg": "Unable to read private key: ",
  "time": "2019-06-06T16:31:59+02:00"
}

We need to wrap these objects with array [{...},{...}] or change format of this file

Should we care about this? Although, when/if someone decide to fix it, please also pay attention to the fact that we may want to send json log messages to some recipient, such as UI.

From what I saw reading through some logrus docs is that the messages were put in JSON format to make log parsing by splunk, etc. easier. I don't know that the intention was ever to make the entire log proper json

Yeah, exactly.


Readme Improvements by adding gifs and an open-source section that this project is a  part of

let me know if this needs to be done

Similar work is going on in this thread #5 so will wait for his reply,,,if he doesnt...will assign it to u

Similar work is going on in this thread #5 so will wait for his reply,,,if he doesnt...will assign it to u


Provide a Mixin as an alternative to the Plugin

Versions:

VueJs: 2.*
Vee-Validate: 2.*

Description:
I could be off track here, but a plugin feels quite invasive, for what should be a component-by-component choice.
Having every single component contain errors and fields computed properties doesn't feel right.
Using the example outlined in the docs I'm now using a Mixin for certain components, and I expect it would be even easier to do this for forms.
Should this not be provided by the core package?

well there is the inject option which would only add the errors and fields on the components that actually need it.
take a look at injections:
http://vee-validate.logaretm.com/advanced#injection
Now if you would like to selective and import the mixin then apply it to certain components this is relatively simple to do, as we would just expose the mixin make function as a property.


Add supports RA80V2

Check list:

xqsystem/login: 🟢
xqsystem/init_info: 🟢
misystem/status: 🟢
xqnetwork/mode: 🔴
xqsystem/vpn_status: 🟢
misystem/topo_graph: 🟢
xqsystem/check_rom_update: 🟢
xqnetwork/wan_info: 🟢
misystem/led: 🟢
xqnetwork/wifi_detail_all: 🟢
xqnetwork/wifi_diag_detail_all: 🟢
xqnetwork/avaliable_channels: 🟢
xqnetwork/wifi_connect_devices: 🟢
misystem/devicelist: 🟢
xqnetwork/wifiap_signal: 🟢
misystem/newstatus: 🟢
xqsystem/reboot: ⚪
xqsystem/upgrade_rom: ⚪
xqsystem/flash_permission: ⚪
xqnetwork/set_wifi: ⚪
xqnetwork/set_wifi_without_restart: ⚪

I managed to make it work with some workaround.
I tried to find the proper "xqnetwork/mode" for this version of AX3000 v2, but no success. So I decided to check my v1 AX3000 response for this method and I applied a workaround.
Am I proud of it? No
Am I happy with it? Definitely yes!
enum.py - add the following at line 258
    RA80V2 = "ra80v2"  # 2024.10.20
luci.py - modify the mode method like following
`    async def mode(self) -> dict:
"""xqnetwork/mode method.
    :return dict: dict with api data.
    """
    try:
        return await self.get("xqnetwork/mode")
    except:
        return "{\"mode\":0,\"code\":0}"`

updater.py - modify the line 601 to add a try/except
                try:                     data[ATTR_SENSOR_MODE] = Mode(int(response["mode"]))                 except:                     data[ATTR_SENSOR_MODE] = Mode(0)

Hi
I don't see where to enter the code

Hi I don't see where to enter the code

You have to update the indicated lines in the files I mentioned: enum.py, luci.py and updater.py


[SPARK-17505][MLLIB]Add setBins for BinaryClassificationMetrics

What changes were proposed in this pull request?
Add a setBins method for BinaryClassificationMetrics.
BinaryClassificationMetrics is a class in mllib/Evaluation.  numBins is a key attribute of it.   If numBins greater than 0, then the curves (ROC curve, PR curve) computed internally will be down-sampled to this many "bins".
It is useful to let the user set the numBins.
How was this patch tested?
ut cases were changed to test this PR.
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

Test build #65255 has started for PR 15058 at commit d06b2b1.

Test build #65255 has finished for PR 15058 at commit d06b2b1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test PASSed.

I feel strongly enough about it that I'd request we close this PR

sure, I close it now


Any ideas on how to unit test the result?

For example, a test case from: delaunay-triangulation/tests/tests.cpp:
TEST_CASE("Delaunay triangulation should be able to handle 10000 points as float", "[DelaunayTest]") {
    std::vector<Vector2<float> > points(1e4);
    srand(666);
    for (size_t i=0; i < 1e4; ++i)
    {
        float x = (float)rand() / (float)RAND_MAX;
        float y = (double)rand() / (float)RAND_MAX;
        points.at(i) = Vector2<float>(x, y);
    }
    REQUIRE(10000 == points.size());
    Delaunay<float> triangulation;
    const std::vector<Triangle<float> > triangles = triangulation.triangulate(points);
}

Why not test the result, including const std::vector<Triangle<float> > triangles? The test case only guarantees that there is no run-time error but not the correctness of the triangulation result.

With a sample of data of that size, it would be hard and complex to test it properly. This is more of a "performance" test, to see if the implementation can process 1000 points without crashing or going out of memory.
Accuracy test against data from other implementations could be useful, but it would require a lot of time to setup.


Create a snapshot of "sigma-containter"

The problem with taking a screenshot is that the canvas is divided into several sections:

I am using Angular and I don't see a way to capture it, I have tried to create a single canvan combining the existing ones but the styles are not maintained in the new one.

Until we release a proper @sigma/snapshot package, fully featured and with the proper options, there is an example on how to snapshot a sigma instance here.
The code is there. Don't hesitate to come back to this ticket if you have trouble making it work.