Is it possible to translate BREAD BROWSE columns?

Laravel version
9
PHP version
7.4
Voyager version
1.4.3
Description of problem
Is it possible to translate BREAD BROWSE columns when user changed his/her language in profile? So how to do it?
For example:
English -> Mongolia:
Order - Дараалал
Name - Нэр
Slug - Слаг

Proposed solution
Is it possible to translate BREAD BROWSE columns when user changed his/her language in profile? So how to do it?
Alternatives considered
Is it possible to translate BREAD BROWSE columns when user changed his/her language in profile? So how to do it?
Additional context
Is it possible to translate BREAD BROWSE columns when user changed his/her language in profile? So how to do it?

I think so, appears to look that way anyways.
https://voyager-docs.devdojo.com/core-concepts/multilanguage
You can also add bread to the translations table pretty easily by using "TCG\Voyager\Models\Translation" as a model, or build your own that extends it. If you search the repo here for getTranslatedAttribute
The browse blade takes a datatype, which has datarows.
Datatype and DataRows have the translator trait applied.
Type uses "display_name_singular, display_name_plural" and Row uses "display_name"
https://github.com/thedevdojo/voyager/blob/7866a2d287c72b2682322d84f691974eb68c9331/resources/views/bread/browse.blade.php#L91
So you should just be able to make translation entries for your table.
The tricky part is that Voyager hides the DataTypes and Rows Tables.
You can use tinker or debug another way.
For example
Run php artisan tinker and then type
TCG\Voyager\Models\DataType::where('name','categories')->first()->rows->pluck('display_name','id')

This will give you a list of data rows with their display_name and corresponding id.  You can use 'name' if you don't want the case confusion.
Now go into the Bread for translations that you just made and add a new entry.
Set the fields as follows:
Table Name : data_rows
Column Name: display_name
Foreign Key: [ID VALUE FROM QUEURY FOR COLUMN]
Locale: [WANTED LOCAL]
Value: [TRANSLATED VALUE]
Now when your user changes their local, that data_row will get translated.

Notice the first column is now translated.

@Emerica Thank you so much. 🙇🏻♂🙇🏻♂🙇🏻♂

@Emerica how to create PR for new unsupported locale?
I have already translated. When i try to push then it says:
git push --set-upstream origin adding-a-new-unsupported-locale-mongolia-mn
remote: Permission to thedevdojo/voyager.git denied to enkhtulga-gantsagaan.
fatal: unable to access 'https://github.com/thedevdojo/voyager.git/': The requested URL returned error: 403

I think you have to commit to your own fork vs master and then submit the pull in github from your fork.


Enh/move templates to helper

Move some hardcoded strings around in tests so that it's easier to change when manually testing non-master branches

looks good except the tests don't run in gh actions

need to fix the test files - might move the generated test code into a gitignored folder so it's clear they're just temp files

Ah, I see what's going on here - tests are running against old templates and not fetching from git.
I'm leaving this for another day - I just wanted to clean up some duplication but maybe it's better to not touch any of these for now

We will likely revist the tests at a later time - and if necessary refactor then


IE 11 autoprefixer for css grid not working

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
gridTemplateColumns is not being prefixed into -ms-grid-columns. It stays as gridTemplateColumns in IE 11. Same with gridColumn

Expected Behavior 🤔
gridTemplateColumns should be transformed into -ms-grid-columns while gridColumn into -ms-grid-column when viewed in IE11

Steps to Reproduce 🕹
use gridTemplateColumns in your styles and view in IE11

Tech
Version

Material-UI
v4.7.0

React
16.12.0

Browser
IE11

IE11 uses an older version of the Grid specification.
The properties you are using don't exist in the older grid spec. Using prefixes makes no difference.

https://medium.com/@elad/supporting-css-grid-in-internet-explorer-b38669e75d66
https://stackoverflow.com/questions/45786788/css-grid-layout-not-working-in-ie11-even-with-prefixes

I have tried with styled-components, the support seems to be a bit worse:
compare
import React from 'react';
import PropTypes from 'prop-types';
import { withStyles } from '@material-ui/core/styles';
import styled from 'styled-components';

const Div = styled('div')({
  display: 'grid',
  gridTemplateColumns: '40px 50px auto 50px 40px',
  gridTemplateRows: '25% 100px auto',
  '& > *': {
    background: 'red',
  },
});

function SimpleTabs(props) {
  return (

1

2

3

4

5

6

  );
}

export default SimpleTabs;

with
import React from 'react';
import PropTypes from 'prop-types';
import { withStyles } from '@material-ui/core/styles';

const styles = theme => ({
  root: {
    display: 'grid',
    gridTemplateColumns: '40px 50px auto 50px 40px',
    gridTemplateRows: '25% 100px auto',
    '& > *': {
      background: 'red',
    },
  },
});

function SimpleTabs(props) {
  const { classes } = props;

  return (

1

2

3

4

5

6

  );
}

SimpleTabs.propTypes = {
  classes: PropTypes.object.isRequired,
};

export default withStyles(styles)(SimpleTabs);

Can someone please give me clear instructions on how to enable autoprefixing for the grid attributes? Because it does not seem to work at all. The second example from @oliviertassinari generates nothing.
I was hoping that running your npm script with cross-env AUTOPREFIXER_GRID=autoplace ... would enable grid support but again.. nothing. I'm running latest "@material-ui/core": "^4.9.7"
@nino-moreton Did you solve this somehow?


Functions in tables

Is it not possible to have a function as an element of a table?
I.E
intro = {
say = 'Hello I am the Helper NPC',
choices = {
choice1 = 'HELP ME',
choice2 = "LEAVE ME ALONE"
},
f = function done() return 1 end
}

Could you provide a full example, the one listed here should work with no concerns.
Also, please see Mastering Markdown to aid in formatting.

I thought so too, this is the full example really, I can not get the script to work with the function as part of the table.
intro = {
	say = 'Hello I am the Helper NPC',
	choices = {
                 choice1 = 'HELP ME',
                 choice2 = "LEAVE ME ALONE"
    },
	onSelection = function selected(  )
	-- do stuff
        end
}

You mean you can't execute the function?

The script was throwing an error on load. Not sure if it was line endings or some voodoo, but after a reboot, clean and rebuild, the code above no longer errors ...

As a side note, your syntax was wrong. You can't give a function a name and also set it inside of a table. The error I receive when I run your code is this: sol: syntax error: [string "..."]:8: '(' expected near 'selected'
What that means is this
	onSelection = function selected(  )
	-- do stuff
        end

is illegal, because you are giving a name to the function when you're just trying to make a regular function object that gets set into onSelection. In the future, remove the name of the function if you're going to put it into a table. Please also read the free-to-find Programming In Lua book that's available online to familiarize yourself with Lua concepts, and be sure to read the errors sol2 provides you with.


[Question]: "The total size of the files uploaded at once is too large." error while uploading a file.

Describe your problem
I have added to the docker env MAX_CONTENT_LENGTH=100000000000 and also added to the nginx.conf this line - client_max_body_size 100M. still i am facing the issue when i upload a file more than 1 mb.

Please refer to this.


Couchbackup returns empty file

I created a tool in March that fetches all the name of the databases and writing its content to a file. This has been working until now, where i tried to run the application again.
This is the function for backing up:
export function couchBackup() {
    initDB().then((result) => {
        for (const item of result) {
            couchbackup.backup(dbUrl + '/' + item, fs.createWriteStream(item + '.json'),
                { parallelism: 2 },
                (err, data) => {
                    if (err) {
                        console.log('failed!', err);
                    } else {
                        console.log('GREAT successs! ', data);
                    }
                });
        }
    });
}

I am still able to go into the cloudant service and i am getting the names of the databases. It is also downloading 1 file for each db as expected, but this time this is empty. It doesn't look like it is going further to the parralelism:2 line. I don't even get Great success!

couchbackup version
2.5.2
Node.js version
10.0.0

So i got the application working now with running the app via git bash. It didn't work with WSL.

If I understand correctly, the issue is gone now. I'm about to close this ticket.

Should it be any difference between "win32" vs "linux" platform when running couchbackup?

There should be no such platform-dependent pieces in the code. If you manage to find any, @BennyHoang , please let us know.

Will keep you updated!
So where i am currently:
export function couchBackup() {
    initDB().then((result) => {
        for (const item of result) {
            couchbackup.backup(dbUrl + '/' + item, fs.createWriteStream(item + '.json'),
                //nothinig happens here
                { parallelism: 2 },
                (err, data) => {
                    if (err) {
                        //does not log anything in here
                        console.log('failed!', err);
                    } else {
                        //does not log anything in here
                        console.log('GREAT successs! ', data);
                    }
                });
        }
    });
}

So it looks like the application is restarting before it can write the content of the db to thie files.


[CWE-89] POST based SQL Injection in submit.php, Line 16

Hello,
Issue
There is a clear SQL injection in file submit.php, line 16, due to an improper validation of the post variable "email", who is passed directly to the SQL command line.
Remediation
I would recommend you to globally stop the insecure way of doing SQL connexion **_query and migrate over a PDO connexion. Those are way more secure and made to avoid any SQL injection as they handle the construction of the SQL request in a per-design safe way.
The hot-fix (that shouldn't be considered as definitive fix but that can fix the issue right now) would be to validate the content of the "email" post variable, in this case you could just check if the email parameter match a regex that can confirm it's a syntax-valid email that respect the corresponding RFC's (cf: https://datatracker.ietf.org/doc/html/rfc2822), and not using it if it doesn't match the regex.

To add on @March-M's comment, another temporary fix could be to use pg_query_params rather than pg_query. Doc here.

Thanks for the help


A way to ommit prefix class for component status

I want to folllow the CSS style guide that Medium has: https://gist.github.com/cuibonobo/16f555c0047ab80044cf, with:
.componentName
  background blue

.componentName.is-stateOfComponent
  background red

And then compile them with gulp-stylus and this config:
gulp
  .src('./src/component.styl')
  .pipe(
    stylus({
      prefix: 'foo-',
      include: [
        ...
      ]
    })
  )....

Resulting in:
.foo-componentName
  background: blue;

.foo-componentName.is-stateOfComponent
  background: red;

Now it's:
.foo-componentName
  background: blue;

.foo-componentName.foo-is-stateOfComponent
  background: red;

Resulting in a lot of extra bytes..
Is this possible? I have hundreds of selectors, so the prefix option is nice to have, but I want to ommit class states/or other helper classes from the compiler.
ref: https://github.com/stylus/stylus/issues/2406#issuecomment-409109935

Not in gulp-stylus, maybe if they answer the question in that issue on stylus


Full use/aim animation premultiply blend

This PR makes the aim and use animations premultiply against the current animation, with idle base inverted.
All bones are unlocked, but all of the use animations need to be fixed as a result.

This PR already looks far superior to master with no real drawbacks that I could find, so let's merge it as a checkpoint. The attack animations will be bad especially when running, but it's still better than what we had before.


Replace the Patient DB excel link with a new page in the website

Is your feature request related to a problem? Please describe.
The patient DB is currently a link to a published Google Sheet. It is not very useful without any filtering or sorting functionality and also, it takes the user out of the website. There is no way to download the excel either.
Describe the solution you'd like
Add a page in the website which will show the patient DB as a HTML table with sorting and pagination which will allow the users to browse the DB directly in the website. Ability to download this data as CSV would be helpful too.

Additional context
Example of the table that was provided by the portal

Dunzo!


Internationalization with rust-i18n

Using the https://crates.io/crates/r_i18n crate

https://crates.io/crates/rust-i18n is a better choice, I think


Life360 integration

Description:
Life360 integration.

Note: This is "take 2." The original proposal can be found in #23405.

Related issue (if applicable): N/A
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#9539
Example entry for configuration.yaml (if applicable):
life360:
  - username: LIFE360_USERNAME
    password: LIFE360_PASSWORD

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

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

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

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[x] Untested files have been added to .coveragerc.

I realized, for multiple Life360 accounts, only one device_tracker scanner should be created which iterates over the accounts (and circles and members) so that each unique member is only updated once, no matter what circles and accounts it is accessible from. Also, it's still unclear whether or not config flow should be used.

I did end up using config entries and adding config flow. Life360 accounts can now be entered either via the configuration, the UI, or both. CONFIG_SCHEMA now accepts a single dictionary as opposed to a list so that there is only one configuration that affects all accounts instead of allowing each account to have a different config. (Which makes sense since there is now only one scanner that processes all accounts.) Also added a new 'accounts' key which is optional and can have a list of username/password pairs. Doc PR updated accordingly.
Should now be ready for review.
FYI, after a discussion with balloob, I will look into converting to the new device_tracker entity scheme in a follow-up PR.

This looks great, great work ! Thanks. 🐬

@pnbrunker thanks so much for working towards integration with release 0.95.0.    I've assumed it's going to be released and jumped onto 0.95.0b1 with no sucess.
I've read everything I can find Is there more documentation available other than that contained above - my configuration is throwing errors.
configuration .yaml
life360:
  - username: LIFE360_USERNAME
    password: LIFE360_PASSWORD

log error
Invalid config for [life360]: expected a dictionary for dictionary value @ data['life360']. Got [OrderedDict([('username', '<redacted>'), ('password', '<redacted>')])]. (See /config/configuration.yaml, line 115). Please check the docs at https://home-assistant.io/components/life360/

Please open an issue if you suspect a bug. If you need help please use our help channels:
https://home-assistant.io/help/#communication-channels
Merged PRs should not be used for support or bug reports. Thanks!


deploygate--upload-app-bitrise-step 1.1.1

What to do if the build fails?
At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.
New Pull Request Checklist
Please mark the points which you did / accept.

[x] I will not move an already shared step version's tag to another commit
[x] I read the Step Development Guideline
[x] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[x] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[x] I read and accept the Abandoned Step policy

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I'd like to change the employer email to<EMAIL_ADDRESS>due to my fault, sorry.

I'd like to change the employer email in the CLA due to my fault, sorry. How can I do it?

@jmatsu Thanks for signing the CLA!
We investigated the case, and unfortunately, there's currently no easy way to change the email address with an existing signing.
For now, could you please let us know what's the data that you'd like to change? We'll store this data, and fix it as soon as we find a valid solution. I just got in touch with you via email.

@Janos-vrancsik
I replied to your email so could you please check it? Thanks in advance.


Add validation scripts for pipeline integrity checks

Hi @ahernank, here's a set of validation scripts developed to ensure that each step of the pipeline functions as intended. We take a modular approach, tracking through each task while making use of scripts by a more appropriate scripting language for each module. Specifically, the validation process includes checks for input file accessibility, integrity, and format, as well as output file format and association. This enhancement aims to improve the reliability and accuracy of our data processing pipeline.
Details of Changes:

Input file accessibility: The scripts include functions to verify that all required input files are present and accessible.
Input file integrity and format: The scripts perform checks to ensure that input files are complete, uncorrupted, and in the correct format.
Output file format and association: The scripts validate that the output files are correctly formatted and properly associated with their respective input files.

Modes of Operation:
Interactive mode: Users can run each module validation individually. This mode is useful for debugging and verifying specific parts of the pipeline.
Non-Interactive mode: Users can run all module validations in a batch using the all_in_one_validation script. This mode is efficient for full pipeline checks
We aim to catch and address data processing potential issues in the workflow to improve the overall robustness of our pipeline.
Resolves #11

Validation report:
In addition to performing the checks, the all_in_one_validation script generate a report in a text format (validation_report.txt). This report provides the status of each module validation, including hint about an issue where any is encountered. See sample validation report below:
Validation Checklist Report
Validate Input Manifest: Success
Validate SelectVariants Output: Success
Validate Bgzip and Tabix: Success
Validate WhatsHap Phase: Success
Validate WhatsHap Stats: Success
Validate MergeVcfs: Failed
Details: Missing file: merged.vcf.gz
Validate BgzipAndTabixII: Success
Validate SHAPEIT: Success
Validate TabixII: Success
Validate LigateRegions: Success
Validate cohortVcfToZarr: Success


Update maven site model

This updates the maven site model to the new structure

Seems that the <project> structure is good as-is


Can't set nextPathname in location descriptor for replace() method on onEnter()

This used to work just fine.  Then someone went and changed the api without documenting any breaking changes.   Extremely frustrating.
I have a route checking for authentication onEnter:
const requireAuth = (nextState, replace) => {

	console.log(nextState.location);

	if(!isLoggedIn()) {
		replace({ pathname: '/login', nextPathname: nextState.location.pathname });
	}

	if(isLoggedIn() && !userHasAccess()) {
		replace({ pathname: '/forgot-password', nextPathname: nextState.location.pathname });
		Store.dispatch(updateIceCream('error', 'You must verify your account.  Enter your email above if you need a new code.'));
	}

}

And at the end of my login action creator:
 let state = getState(),
      routeState = state.route.location.state;

dispatch(replace(routeState ? routeState.nextPathname : '/'));

First thing I'm noticing is that it's no longer getState().route.location it's now getState().route.locationBeforeTransitions.  This is not documented anywhere.
Second thing I'm noticing is that getState.route.locationBeforeTransitions.state is null always.  Where am I supposed to pick up the nextPathname prop I'm attempting to supply to the replace methods location argument?

Is it a leftpad bug? :laughing:

First thing I'm noticing is that it's no longer getState().route.location it's now getState().route.locationBeforeTransitions. This is not documented anywhere.

Because that state isn't reliable to listen to (as the name implies, it's not the fully-resolved location state). Instead, use the history singleton to read from.

Where am I supposed to pick up the nextPathname prop I'm attempting to supply to the replace methods location argument?

browserHistory.listen(location => currentLocation = location) This is a synchronous call.


Wagtail 6.2 testing

This updates the tox testing to include Wagtail 6.2
It builds on: https://github.com/torchbox/wagtail-makeup/pull/26

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

Project coverage is 73.68%. Comparing base (bce562a) to head (3056a91).
Report is 21 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #27      +/-   ##
==========================================
+ Coverage   73.33%   73.68%   +0.35%
==========================================
  Files           5        5
  Lines          75       76       +1
==========================================
+ Hits           55       56       +1
  Misses         20       20

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

Closing to use https://github.com/torchbox/wagtail-makeup/pull/28


RCP has disconnected from a network and now fails to connect to that network

Description
I have a RCP + SBC device operating as a Border Router (OTBR) in a network of 18 devices. This network has been stable since the past 3 weeks. Since this morning, the Border Router device has been disconnected from the network. I can see all 17 devices on scan.
I have rebuilt otbr-posix on the SBC and done several resets and factory resets on the RCP through CLI (ot-ctl) but nothing seems to let the RCP attach to the established network of the 17 other devices. I have also seen messages related to different partitionid in the logs, but cannot find how I can change the partitionid of this RCP.
syslog output for otbr-agent shows something peculiar, as follows:
Received IPv6 UDP msg, len:84, chksum:f984, from:d64989268897f84b, sec:no, prio:net, rss:-29.0
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----:     src:[fe80:0:0:0:d449:8926:8897:f84b]:19788
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----:     dst:[ff02:0:0:0:0:0:0:2]:19788
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-PLAT----: processReceive: OK
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MLE-----: Receive Parent Request (fe80:0:0:0:d449:8926:8897:f84b)
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [WARN]-MLE-----: Failed to process Parent Request: Drop
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----: Received IPv6 UDP msg, len:84, chksum:8c80, from:e617a18459bb1d24, sec:no, prio:net, rss:-38.0
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----:     src:[fe80:0:0:0:e417:a184:59bb:1d24]:19788
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----:     dst:[ff02:0:0:0:0:0:0:2]:19788
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-PLAT----: processReceive: OK
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MLE-----: Receive Parent Request (fe80:0:0:0:e417:a184:59bb:1d24)
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [WARN]-MLE-----: Failed to process Parent Request: Drop
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----: Received IPv6 UDP msg, len:84, chksum:127d, from:a26714800096071c, sec:no, prio:net, rss:-35.0
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----:     src:[fe80:0:0:0:a067:1480:96:71c]:19788
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----:     dst:[ff02:0:0:0:0:0:0:2]:19788
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-PLAT----: processReceive: OK
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MLE-----: Receive Parent Request (fe80:0:0:0:a067:1480:96:71c)
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [WARN]-MLE-----: Failed to process Parent Request: Drop
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----: Received IPv6 UDP msg, len:84, chksum:62dc, from:9e4b67dc05de22fe, sec:no, prio:net, rss:-42.0
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----:     src:[fe80:0:0:0:9c4b:67dc:5de:22fe]:19788
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----:     dst:[ff02:0:0:0:0:0:0:2]:19788
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-PLAT----: processReceive: OK
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MLE-----: Receive Parent Request (fe80:0:0:0:9c4b:67dc:5de:22fe)
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [WARN]-MLE-----: Failed to process Parent Request: Drop
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----: Received IPv6 UDP msg, len:84, chksum:960d, from:439e4f5342c78c94, sec:no, prio:net, rss:-34.0
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----:     src:[fe80:0:0:0:419e:4f53:42c7:8c94]:19788
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----:     dst:[ff02:0:0:0:0:0:0:2]:19788
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-PLAT----: processReceive: OK
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MLE-----: Receive Parent Request (fe80:0:0:0:419e:4f53:42c7:8c94)
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [WARN]-MLE-----: Failed to process Parent Request: Drop
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----: Received IPv6 UDP msg, len:84, chksum:81c0, from:1ec6cca2bd84157c, sec:no, prio:net, rss:-46.0
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----:     src:[fe80:0:0:0:1cc6:cca2:bd84:157c]:19788
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MAC-----:     dst:[ff02:0:0:0:0:0:0:2]:19788
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-PLAT----: processReceive: OK
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [INFO]-MLE-----: Receive Parent Request (fe80:0:0:0:1cc6:cca2:bd84:157c)
May 19 22:53:13 NPT-gateway-8 otbr-agent[533]: [WARN]-MLE-----: Failed to process Parent Request: Drop

To Reproduce
I have not seen this issue previously and do not know how to reproduce this situation.
IEEE 802.15.4 hardware platform: Silicon Labs MGM12P SoC
Network topology: Mesh - All devices are currently mounted on a wall like framework to test functionality.
Expected behavior
In the past 3 weeks, the Border Router has been functioning fine. And this operation is expected to continue.
Console/log output
Console log output is attached above.

@vijayrao1988 , can you provide more detail on your setup?
Are the other devices Full Thread Devices (FTDs) or Minimal Thread Devices (MTDs)?
I would look into MleRouter::HandleParentRequest() to see which of the conditions that result in kErrorDrop are occuring.

The setup consists of 18 devices: 17 Full Thread Devices running a Thread stack off a Silicon Labs SDK and 1 RCP running a OpenThread Thread stack.
Physically, they are put on frame with 4 rows of 4 devices each and a 5th row with 1 device. The OpenThread RCP sits below this frame. The txpower on the devices is 0dBm as is the case with the RCP.
They were working fine for 3 weeks.
I must add that initially there were 20 devices and 3 were physically removed from the setup leaving the rest in tact. It was almost immediately after removing those 3 devices that we saw the connection drop off.
I have reinstalled otbr-posix, done resets and factory resets on the RCP through ot-ctl and rebooted the SBC a few times.
Is it possible that these devices have been put in some sort of a blocked list?

How do I look for more details from MleRouter::HandleParentRequest() in the logs?

You would either need to add additional logging or use a debugger to inspect which condition is failing.
If all the devices are FTDs, then I'm surprised as to why devices would be sending Parent Request messages to the RCP? The FTDs should already have formed a network among themselves and the RCP should be joining that network.

Fair point. I think the devices entered some sort of an error state, in this case, where they weren't joining a network with matching parameters nor letting any other device join their network.
Update: We introduced 2 new devices to the network; 1 device running the same firmware as the Silicon Labs FTDs and another OpenThread RCP. This seemed to cause some sort of a brokering which unblocked the standoff. We now have a network of 20 devices. I still do not understand what caused the erroneous non-communicative state and how introducing 2 new devices resolved it. Could this some sort of blocked-list?
I think the problem is because of an old Thread stack in our firmware that Silicon Labs hasn't updated in a long time and don't maintain any more as they have moved to OpenThread. As a solution to avoid this situation in the future, we will move our device firmware out of Silicons Labs Thread stack in the coming few months.

The error has reoccured. I'm attaching the syslog output for otbr. Any observations that can help to resolve this issue?
In this log file, the initial part shows the presence of the devices through a scan. There are several Frame RX errors as well in the log. Could this be the problem?
syslog-IsolatedBorderRouter.txt

From the logs, it appears that OTBR is not able to join the existing partition. It sends MLE Parent Request messages, without receiving any MLE Parent Response.
From the logs, it's not clear why the other nodes are not responding to OTBR's MLE Parent Request message. Perhaps this is an issue with the legacy Thread implementation that you are using on the other devices?

Could someone help me with this please?
May 21 16:49:03 NPT-gateway-8 otbr-agent[155571]: [INFO]-MAC-----: Frame rx failed, error:UnknownNeighbor, len:100, seqnum:173, type:Data, src:0xf400, dst:0xffff, sec:yes, ackreq:no
May 21 16:49:03 NPT-gateway-8 otbr-agent[155571]: [INFO]-MAC-----: Frame rx failed, error:UnknownNeighbor, len:100, seqnum:174, type:Data, src:0xf400, dst:0xffff, sec:yes, ackreq:no
May 21 16:49:03 NPT-gateway-8 otbr-agent[155571]: [INFO]-MAC-----: Frame rx failed, error:UnknownNeighbor, len:100, seqnum:175, type:Data, src:0xf400, dst:0xffff, sec:yes, ackreq:no
May 21 16:49:03 NPT-gateway-8 otbr-agent[155571]: [INFO]-MAC-----: Frame rx failed, error:UnknownNeighbor, len:100, seqnum:137, type:Data, src:0x2400, dst:0xffff, sec:yes, ackreq:no
May 21 16:49:03 NPT-gateway-8 otbr-agent[155571]: [INFO]-MAC-----: Frame rx failed, error:UnknownNeighbor, len:100, seqnum:114, type:Data, src:0x0000, dst:0xffff, sec:yes, ackreq:no
May 21 16:49:03 NPT-gateway-8 otbr-agent[155571]: [INFO]-MAC-----: Frame rx failed, error:UnknownNeighbor, len:100, seqnum:249, type:Data, src:0xb000, dst:0xffff, sec:yes, ackreq:no
May 21 16:49:03 NPT-gateway-8 otbr-agent[155571]: [INFO]-MAC-----: Frame rx failed, error:UnknownNeighbor, len:100, seqnum:115, type:Data, src:0x0000, dst:0xffff, sec:yes, ackreq:no
May 21 16:49:03 NPT-gateway-8 otbr-agent[155571]: [INFO]-MAC-----: Frame rx failed, error:UnknownNeighbor, len:100, seqnum:138, type:Data, src:0x2400, dst:0xffff, sec:yes, ackreq:no
May 21 16:49:03 NPT-gateway-8 otbr-agent[155571]: [INFO]-MAC-----: Frame rx failed, error:UnknownNeighbor, len:100, seqnum:195, type:Data, src:0xcc00, dst:0xffff, sec:yes, ackreq:no
May 21 16:49:03 NPT-gateway-8 otbr-agent[155571]: [INFO]-MAC-----: Frame rx failed, error:UnknownNeighbor, len:100, seqnum:250, type:Data, src:0xb000, dst:0xffff, sec:yes, ackreq:no
May 21 16:49:03 NPT-gateway-8 otbr-agent[155571]: [INFO]-MAC-----: Frame rx failed, error:UnknownNeighbor, len:100, seqnum:196, type:Data, src:0xcc00, dst:0xffff, sec:yes, ackreq:no
May 21 16:49:03 NPT-gateway-8 otbr-agent[155571]: [INFO]-MAC-----: Frame rx failed, error:UnknownNeighbor, len:100, seqnum:116, type:Data, src:0x0000, dst:0xffff, sec:yes, ackreq:no
May 21 16:49:03 NPT-gateway-8 otbr-agent[155571]: [INFO]-MAC-----: Frame rx failed, error:UnknownNeighbor, len:100, seqnum:251, type:Data, src:0xb000, dst:0xffff, sec:yes, ackreq:no
May 21 16:49:03 NPT-gateway-8 otbr-agent[155571]: [INFO]-MAC-----: Frame rx failed, error:UnknownNeighbor, len:100, seqnum:139, type:Data, src:0x2400, dst:0xffff, sec:yes, ackreq:no

@vijayrao1988 the log line Frame rx failed, error:UnknownNeighbor, ... simply shows that device received a secure frame from an unknown neighbor/device (a device not yet in neighbor table) and therefore it is dropping it. This log line itself is not bad and not necessarily a bug or issue. It's just a notification to show what's happening. That's expected when you have devices/neighbors in another partition.
As @jwhui mentioned, the logs indicate that other devices continue to try to attach and not be able to process the "Parent Response" from the OTBR.

Closing stale issue.


Tweak Tween cheatsheet link formatting to avoid rST conversion bug

reStructuredText doesn't allow embedding links in bold/italic text.
See https://github.com/godotengine/godot-docs/issues/3474.

Thanks!

Cherry-picked for 3.2.2.


Bitget_perpetual connector does not get ready for scripts

Describe the bug
Since 2023/03/31, when running a script using the bitget_perpetual connector, the script throws the following message continously:
script_strategy_base - bitget_perpetual is not ready. Please wait...
Steps To Reproduce
Here are the steps to reproduce the issue:

Modify one simple script to use bitget_perpetual. For example, modify log_price_example.py "binance_paper_trade" market with "bitget_perpetual"
Start HummingBot
Configure the bitget_perpetual connector adding the API key, secret key and passphase
Executing "balance" commands here works nice.
Start the bot using this command: start --script mod_log_price_example.py

Release version
The problem appears at least in:

1.13 source install.
1.14 source install.
1.14 docker install.

Attachments
Trying to debug the connection status, I arrived to perpetual_derivative_py_base.py:status_dict():

I am new to hummingbot, python, and bitget connector, so take my comment with caution.
Not sure about the implications, but seems that https://api.bitget.com/api/mix/v1/ is not avaiable at this moment to get the server time. Checking https://api.bitget.com/api/spot/v1/ seems to work, so I tried to modify the constant SERVER_TIME_PATH_URL to "/api/spot/v1" and seems to improve the situation.
But some breakpoints trigger on 400 error in rest_assistant.py::execute_request(), not sure why.


NAT classication server doesn't actually need two public IPs

The docs state that the server requires two public IPs but that isn't true -- the field public_ip2 is never read:
https://github.com/uProxy/uproxy-probe/blob/master/server.py
Also, why does the server code need to know its IP? Seems like the only config should be the ports. Think there's a bunch of cleanup we can do here.

Are you sure?  I see it referenced at
https://github.com/uProxy/uproxy-probe/blob/master/server.py#L105

Oh yeah :-) Well, public_ip1 isn't referenced -- I guess there is some link between private and public IPs so it ends up being implicitly bound.
In that case it seems weird to worry about the private IPs. Maybe they can be referenced by interface name?

Yes, 2 public ips are needed, but the client will only need to know one IPs. The 2nd ip will be passed to client through the connection established between client and first public ip.

OK! Thanks for the update. Closing this.


Multiple reboot after a graceful shutdown

Describe the Bug
Multiple reboot after a graceful shutdown. After 3 reboot, the server starts without issues
Fresh World on 1.0.
Your Runtime Command or Docker Compose File
services:
    satisfactory-server:
        container_name: 'satisfactory-server'
        image: 'wolveix/satisfactory-server:latest'
        network_mode: host
        ports:
            - '7777:7777/udp'
            - '7777:7777/tcp'
        volumes:
            - '/mnt/giorgio/satisfactory-server:/config'
        environment:
            MAXPLAYERS: 4
            PGID: 1000
            PUID: 1000
            ROOTLESS: false
            STEAMBETA: false
            AUTOPAUSE: true
        restart: unless-stopped
        deploy:
          resources:
            limits:
              memory: 6G
            reservations:
              memory: 4G

System Specs (please complete the following information):
If you're on Linux, just paste the following block as a single command, and paste the output here.
===== START ISSUE REPORT =====
OS:  Linux marco-ArchServer 6.4.12-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 24 Aug 2023 00:38:14 +0000 x86_64 GNU/Linux
CPU: AMD Ryzen 5 2600 Six-Core Processor
RAM: 23GB/32GB
HDD: 69GB/100GB (73% used)
ZFS 1: 4GB/899GB (1% used) (Where the volume is mount)
===== END ISSUE REPORT =====

Additional Context
issue.log

Hey! This sounds like a game bug. Are you saying that the container reboots 3 times after launch, and then works fine?

Hey! This sounds like a game bug. Are you saying that the container reboots 3 times after launch, and then works fine?

Yep, i wanted to report it to make sure is not a container problem

I don't believe so! Could you see if the issue persists for you without your volume mount? Could you also double check that you're running the latest image? The image hash should be b02914a46b1d

Feel free to re-open if the issue persists, and you believe it to be a container issue :)


Mouse scroll down in chat message input goes to last line

v2.0.11 Win 7 64 bits
In a chat message with multiple lines, if user scroll down with mouse middle button (scroll), it always goes to the last (bottom) line. If user wants to edit line 3, he must use up arrow on keyboard to navigate.

It worked for me. I tested with both a touchpad and with a mouse and I could scroll through each line.

I can't reproduce this on OSX. I'm going to close this one as super low priority. It may only be a Windows issue (or a Win 7 issue) and it doesn't seem super common that a user would be using the scroll wheel to navigate through a chat message.


Update stubs/erlang-* to the new calling convention

This pull request updates the Erlang stubs to the new v0.2.0 calling convention where VERIFY SUCCESS is replaced by ACCEPT and VERIFY FAILURE is replaced by REJECT.

I'll take the liberty to merge this.


BUG: stats: Fix formula in the stats method of the ARGUS distribution.

Replace np.exp(-chi2/4) * sc.iv(1, chi2/4) with sc.ive(1, chi2/4).
This is exactly what ive is for.
Before:
>>> argus.mean(60)
[...]/_continuous_distns.py:8542: RuntimeWarning: invalid value encountered in multiply
  m = np.sqrt(np.pi/8) * chi * np.exp(-chi2/4) * sc.iv(1, chi2/4) / phi
nan

After:
>>> argus.mean(60)
0.99958318851653

The one test failure on Travis CI is an unrelated recurring failure in scipy.sparse.


Add Ombi support

Ombi allows for users to request movies, TV show, albums, etc.
Their releases only come in zip format, so the download script uses wget/unzip using a temporary folder rather than piping curl to tar. It may be able to cleaned up some.

Hi Mathew,
I Couldnt tell you how pleased I was when saw someone had added a pull request this morning let alone a new application! I've been helping out for a few months now and this is the first time anyone has added anything other then me and Anand (he runs the site)!
I've looked at what you've added and am 99% happy with everything you've done. Honestly great effort and really really appreciated. However there is a couple of tiny things that need fixing if you have the time to quickly adjust them which i've hightlighted.
Just out of interest does the access details work?
PORTSEARCH='' appears to be the same as the Radarr setting i'm guessing you used as a template to get this working. It also reads from whatever you have the APPSETTINGS set to to find it.
Also did you want to add your name instead of mine to the script author?
Thanks again!!
Tom

Glad I could help! Love the script and use it all the time to run updates, etc. I did in fact use Radarr as a template (they both use Mono). The port search function works fine, but grabbing the username doesn't - both Radarr Sonarr and this new app use sqlite for their settings. I could write a query for them eventually but if you're okay with leaving it as is for now I think I'll just leave it.
I'll get those minor changes done shortly.

Yep, Just leave it for now that's fine. If you want to write something to query that file for those apps it would be fantastic. I'm currently putting the finishing touches to Subsonic and Madsonic. I also keep finding little niggles I want to fix\improve all over the place!
Thanks again for your time to add this.
Tom

Those changes should be good to go, but check that line in ombi/ombi-init-update.sh. I believe it's  correct.

Perfect! As you can see i've merged it up.
If you did want to continue to help and wanted to add anything else just give me a shout. I've started adding feature requests to the main issue log with what i'm looking at. So if you did want to add anything  then you could just do that as well so i don't end up potentially duplicating your work!!!
Thanks again.
Glad you find the tool useful as well.
Tom

Glad I could help. I added an issue for the db query on apps that use sql or sqlite, and I've made a branch on my fork to experiment with that a bit.

If you want, you could update the project description to include Ombi.

There appears to be an issue with detecting the systemd file in the access details "grep: : No such file or directory" not checked whats causing it but complete guess is missing constant not set?


First argument to new HDWalletProvider() must be a mnemonic phrase, a single private key, or a list of private keys

Using the latest "@truffle/hdwallet-provider": "^2.1.12",, when I tried to run truffle migrate --reset --compile-all --network moonbase it gave me an error First argument to new HDWalletProvider() must be a mnemonic phrase, a single private key, or a list of private keys., it now expects the private key is a Uint8Array with length 32 to be provided as an array.
so provide a parameter privateKeys and type string[] as mentioned here https://github.com/trufflesuite/truffle/tree/develop/packages/hdwallet-provider
so i change it to
let args = {
   privateKeys: [privateKeyDev],
   providerOrUrl: 'http://localhost:9944/',
};
return new HDWalletProvider(args);

...

let args = {
   privateKeys: [privateKeyMoonbase],
   providerOrUrl: 'https://rpc.api.moonbase.moonbeam.network',
};
return new HDWalletProvider(args);

hello! even with  ^2.1.12 the private key as a string should work as it is a legacy parameter, but this raises a good point that we should update to the current accepted parameters (which also apply to the current version ^2.0.8).
I'll submit a PR for it. thanks for bringing this up!


A question about lr_decay_epoch

Hi, thanks for your great work and code release.
I have a question about training.
It is noticed that in train.ipynb
lr_decay-epoch is set to 100, but max epoch is 30.
In paper, 'note that such a decaying learning rate is not used when ti combined with the Stochastic weights averaging technique'
It means that: if we use SWA(stochastic weights averaging), we use constant lr (0.004) during training.
if we not use SWA,  we need to decay lr to 0.004*0.1=0.0004 after epoch 24.
Am I right ?
Another question is :
the results of these 2 settings differ a lot ?
Thanks for your help.

Hi, @SakurajimaMaiii !

It means that: if we use SWA(stochastic weights averaging), we use constant lr (0.004) during training.

Yes, you're right.
If you don't want to use SWA, you should set lr_decay_epoch to 24 and modify some codes about SWA (i.e. swa_model, best_model_wts ... in utils.py) properly.
As I remember, w/ SWA setting is higher about 0.3% on average.
Thank you for your interest in our research.

Hi, I have another problem.
In single source domain experiment,
the hyperparameters are same ?
i.e.  learning rate, batch size , epoch.
Thanks for your help.

Yep @SakurajimaMaiii , All hyperparameters are the same.

Yep @SakurajimaMaiii , All hyperparameters are the same.

Wai,  so quick . Thanks for your reply.


Implement okapi_version() check everywhere

Implement the okapi version function as implemented here: https://github.com/trinsic-id/okapi/pull/422
Languages:

[ ] .NET
[ ] Go
[ ] Java
[ ] Node
[x] Python
[ ] Ruby
[ ] Swift
[ ] Wasm

My plan is to have this for better debugging support. We can ensure customers are using the native binary version that we think they are using. Mostly this applies to mobile, where you can't pull the native binary metadata to determine version number.
I'd rather get this out with the 1.6 release so that we can start using it if necessary. It's a trivial change, separate from the discussion surrounding how to version the wrapper libraries (which can be done close-to or post GA).


Plugin overwrites source maps generated by other plugins

I am using ts-loader and it generates the correct source maps. But when I add ExtractTextPlugin as a plugin somthing goes horribly wrong with the creation of the source maps.
Here is the relevant part of my setup:
module: {
    loaders: [

        // Support for Typescript
        { test: /\.ts$/, loader: 'ts' },

        // Support for Styles (CSS/Sass)
        {
            test:   /\.s(c|a)ss$/,
            loader: ExtractTextPlugin.extract(
                'style',
                `css?sourceMap!sass?sourceMap&includePaths[]=${bourbon.includePaths}`
            )
        }
    ]
},

plugins: [
    new ExtractTextPlugin('style.css', {
        allChunks: true
    })
]

With the ExtraTextPlugin enabled I get links to the TypeScript source like test.scss:7. Which is obviously not really the correct file ;-D If I disable the plugin (via disable: true) everything works fine (as long as I am using the source-map option).
I also removed the sourceMap param from the css and sass loader. But even then the source files are broken. With this setting they link to the compiled JS instead to the TypeScript files.
Did anyone encounter the same problem?

I check the generated code and there is actually no TypeScript source map anymore. But Chrome seems to find one!?

I have the same problem using stylus for css and babel with es6.
When I have a js error, it shows that it's in app.styl:10
When looking at the map file, the whole chunk referencing the javascript is not there anymore.
Everything's fine if I disable the plugin.

Same issue with babel-loader and ExtractTextPlugin. Enabling extract-text outputs this as the sourcemap:
{"version":3,"sources":[],"names":[],"mappings":"","file":"styles.css","sourceRoot":""}

+1

+1

+1

+1

Could you please create a small repro repo so I can test it?

@paulshen and I just did this and discovered that it was our use of sourceMapFilename which was the culprit. Makes sense that the CSS source map overwrites the JS one when sourceMapFilename doesn't include [file] or something to generate a dynamic output name.

@elsigh - confirmed that was my issue too. Thanks for posting that :+1:

Thanks @elsigh, this fixed it for me as well.. I changed sourceMapFilename: '[name].[chunkhash].map' to sourceMapFilename: '[file].map' and it sorted the problem out.

+1

+1  confusing!

This one is so hard to track down on a big webpack config.
I just made an empty repo to isolate the plugin and I was ready to create an issue :/
It should be big over the README.md

Thank you so much @jamesthurley && @elsigh ! this was indeed the issue and the shared fix worked perfectly for me. Cheers! 🍻

omg thank you!!!!!!

wasted few hours on this. Thanks @elsigh

More kudos to @elsigh -- that was our issue too!

I still have this issue and none of the above solutions work for me

ok so i fixed it by adding:
...
output: {
    sourceMapFilename: '[file].map'
}
...

now it outputs bundle.js.map and index.css.map

The same behavior with empty css source map:
{"version":3,"sources":[],"names":[],"mappings":"","file":"styles.css","sourceRoot":""}
Happens because of purifycss-webpack plugin, spent about 30 mins demystifying. Hope it helps someone.

Thanks @dvakatsiienko, I have the same problem and after omitting purifycss-webpack (move to  production), problem solved.

The same behavior with empty css source map:
{"version":3,"sources":[],"names":[],"mappings":"","file":"styles-less.css","sourceRoot":"webpack:///"}
/# sourceMappingURL=styles-less.css.map/
Happens because of angular-router-loader  plugin.

DEPRECATED
Please use: https://github.com/webpack-contrib/mini-css-extract-plugin


COMP: Make sure GIT_DIR is set in pre-commit

@SimonRit This is updating the hooks branch for #342 to work


load state_dict

Thank you for your code.
I want to use MobileNet2. I trained it (with e.g 10 epochs)  and I save state_dict, but when I use it, I have an error.
Error is:
RuntimeError: Error(s) in loading state_dict for MobileNetV2:
Missing key(s) in state_dict: "conv1.weight", ...
Unexpected key(s) in state_dict: "module.conv1.weight", ....
Please help me.
Thanks in advance.

I found a solution. I use
torch.save(net.module.state_dict(), PATH)
instead of
torch.save(net.state_dict(), PATH)


Finalize annotation selector format

Selector format needs:

Role information (also needs to be available for AdobeDC formats)
Block vs inline context and fragment location

Removed the usage of textValue and extended the definitions to include body content for both the HTML comment and Ripple thread (or reply) metadata. This is where I'm packing all the state information (deleted, resolved, etc) as well as role info.
Note that there's no guarantee of order for items in the annotation body array.


adding working vsphere cloud provider config to existing cluster doesn't work

What kind of request is this (question/bug/enhancement/feature request):
Bug?
Steps to reproduce (least amount of steps as possible):
Create a vsphere cluster without a cloud provider config for vcenter
Once the cluster has completed, edit the cluster YAML using the rancher UI adding in a known working vsphere cloud provider config
Once the cluster has updated, define a vsphere storage class and set as default
Using the Wordpress Helm chart in the Rancher Apps library attempt to deploy with persistent storage for both Wordpress and the DB, leave as use default storage class
Result:
Volumes stuck in pending with the error message;

Warning
ProvisioningFailed
Failed to provision volume with StorageClass "sphere": No VM found
a few seconds ago

Other details that may be helpful:
If I create a cluster using the exact same config but with the cloud provider in it from the beginning it works perfectly and as expected
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.2.4
Installation option (single install/HA): single node and HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): vSphere/VMware
Machine type (cloud/VM/metal) and specifications (CPU/memory): VM
Kubernetes version (use kubectl version): 1.13.5

Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.7", GitCommit:"6f482974b76db3f1e0f5d24605a9d1d38fad9a2b", GitTreeState:"clean", BuildDate:"2019-03-25T02:52:13Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):
17.3.2 Rancher OS on VMware

I managed to make this work by individually deleting the nodes in the node view so that rancher automatically recreates them. After the cluster has come back up entirely and all nodes were rebuilt, it works as expected.
This doesn't seem like its right...

We see the same issue. When a cluster has been provisioned and is up and running with etcd/control members, it fails hard when adding the Vsphere cloud provisioner. When adding the provisioner beore adding the nodes, all goes well.
Are there any specific log files that need to be captured for this to be investigated?


Create Linux PostgresSQL Recipe

Documentation:  https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list/postgresql-monitoring-integration
Output to user:
Note:In order for this integration to function you need to either create or have an existing user with READ Permissions on pg_stat_database, pg_stat_database_conflicts and pg_stat_bgwriter.
If you'd like to create a new user with these permissions please follow these steps within your PostgresSQL Instance:
CREATE USER new_relic WITH PASSWORD 'PASSWORD';
GRANT SELECT ON pg_stat_database TO new_relic;
GRANT SELECT ON pg_stat_database_conflicts TO new_relic;
GRANT SELECT ON pg_stat_bgwriter TO new_relic;
Required Configuration:

Username: Prompt User, assume no default value is provided
Password: Prompt User, assume no default value is provided
Port: Have user confirm the default port of 5432, or allow change . Note: In the recipe the default will still require a change to the config file. The downloaded config file contains a different port.
Database: Have user confirm default of postgres or allow change
SSL : Would you like to configure SSL? Y/N IF YES

Please provide the path of the client certificate file :
Please provide the path of the client key file:
Trust the server certificate? Y/N IF NO
Please provide the path for the root certificate file:

Set collections_list to ALL in recipe (no user prompting required)
Set pgbouncer to true (no user prompting required)

For Logging: Ensure that common log file directories/patterns & process name for Postgres SQL are populated in the beginning of the recipe.
Aha! Link: https://newrelic.aha.io/features/VIRTUOSO-60

Closed by https://github.com/newrelic/open-install-library/commit/d63fd9d5bf907b78dc49b92571aeca8084e52462 and https://github.com/newrelic/open-install-library/commit/07c3e30492a84317fd8407adc3eb1e35476ae8fc


Fix bug preventing onPosition callback from firing

The switch from findDOMNode to ref callbacks introduced a bug preventing the target node rect from being detected when only the onPosition callback was supplied.

Thanks for the quick turn around here neal!


Specify which binary to select in installation command

Installing cargo-component now gives this error:
cargo install --git https://github.com/bytecodealliance/cargo-component

    Updating git repository `https://github.com/bytecodealliance/cargo-component`
error: multiple packages with binaries found: cargo-component, wit. When installing a git repository, cargo will always search the entire repo for any Cargo.toml.
Please specify a package, e.g. `cargo install --git https://github.com/bytecodealliance/cargo-component cargo-component`.

So we need to specify which "crate" to install.
Interestingly, I was getting the same error with the wit command that contained --bin wit, so I added the wit package there too. I am not sure what the --bin wit flag is doing.
I am on Windows 10, using Git Bash, if that's relevant.

@kajacx thanks again for the fix!


An exception occurred while trying to process the frame: list index out of range

I got this error when creating vid2vid "IndexError: list index out of range". Can anybody help me to fix this error

@click2balaji Have you tried method to fix this issue described in the readme file?

I tried uninstalling the sckit-image as mentioned in the readme file, but got this response

Let me know if I am doing this wrong @volotat

Tried installing this in this path:

This was the error i got, let me know if iam doing this in the right path and how to fix this @volotat

This were the settings i used

Let me know what can be done pls

It seems that something is not compiling properly while scikit-image installing. No idea what can help in this situation, I think it's better to look up similar problems at the scikit issues.

@volotat will there a chance if i reinstall this extension/automatic1111/python?

You tried to uninstall the SYSTEM component not the VENV one.
When you enter your StableDiffusion Folder from CMD, go to "../venv/scripts/" then type in CMD: activate
now you should have something like below:
(venv) C:\Users\Trixmaster\StableDiffusion\venv\scripts\
Here you type in your PiP commands like: "pip install scikit-image==0.19.2 --no-cache-dir"
That way it gets installed into your VENV (Virtual Environment) inside the StableDiffusion Folder.
When you just open the cmd without activating the VENV first, then you install the component into your SYSTEM instead, and not just into the VENV.


chore: fix typo from adit to edit

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


Formatting trigger in code

 i have seen several users copy the trigger with ` so maybe removing that or using a more elegant way mighz be better.
In this example i used the -be cc

Yeah sounds fair to me tbh, would require us to change basically every file though 🤔

Yea thsts why i didn't pr xd

This would probably be solved by having a website for documentation / using markdown for the command descriptions, which is being worked on.
Removing the ` works as a band-aid solution. Happy to accept a PR.

I'll speak to Esen, so we document that appropiately then. Appreciate any feedback regarding additional information to be included in the website!


Missing generated class or incorrect reference

using Nswag.ApiDescriptionClient 13.10.1 on .Net Core 5.0.2
I'm having several issues generating a client from the public openApi: https://bag.basisregistraties.overheid.nl/api/v1
One issue is:
The generated c# contains quite a few references to one schema class which is not included in the generation.
As example, the following yml:
    Intersects:
      type: "object"
      description: "'overlapt' en 'raakt' vallen hieronder"
      properties:
        intersects:
          $ref: "#/components/schemas/GeoJSONGeometry"

generates
        [Newtonsoft.Json.JsonProperty("geometrie", Required = Newtonsoft.Json.Required.Always)]
        [System.ComponentModel.DataAnnotations.Required]
        public Intersects1 Geometrie { get; set; } = new Intersects1();

which results in a compile error as the class Intersects1 is nowhere to be found.
For completeness, the entire yml (which is public domain) and .cs are attached: bag.v1.zip

I cannot speak for NSwag or the errors it produces as it's a completely separate project. If there's something in the Swagger/OpenAPI JSON, which is generated by Swashbuckle, that looks incorrect to you please start by running it through a validator (e.g. https://editor.swagger.io/). If it's showing errors then please post them here and I'd be happy to investigate further.

Terribly sorry. Clicked a ref link on their issuetracker and didn't notice it took me here. My bad!


TSS-1583-dmas-migrate-market-access-public-frontend-docker-file-away-from-rockylinux-8

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

Project coverage is 87.71%. Comparing base (0869e79) to head (5aeddde).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #153   +/-   ##
=======================================
  Coverage   87.71%   87.71%
=======================================
  Files          72       72
  Lines        2116     2116
=======================================
  Hits         1856     1856
  Misses        260      260

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


Extract audio only when mosaic is set to have audio support

Currently, every mosaic configuration is retrieved from the following struct:
Mosaic struct {
	Name      string  `json:"name"`
	Medias    []Media `json:"medias"`
	WithAudio bool    `json:"with_audio"`
}

WithAudio field should be respected while firing the ffmpeg command.

WithAudio field should be respected while firing the ffmpeg command.

is this relate dto ffmpeg -an flag?
ref: https://superuser.com/a/268986
PS. sry I haven't use ffmpeg before

@rafiramadhana I think the part of the command you are talking about is another option. For the command we are currently using, I guess we need to remove the "-map", "1:a",


Allow specifying a callback

Made it so that you can specify a callback and you get a stacktrace in it. You can then write to the file yourself if you want or do anything else (write to the database).

I really like this feature but this pull is not compatible with the updates since.
@raymondfeng if this was redone to be compatible would you be in agreement with taking it in?


Fix RenderPointerListener so that callbacks aren't called at the wrong time.

Description
I recently added some code to keep hover events from being propagated when a mouse wasn't attached.  While that works, there are times when it can fire callbacks during the building of other components, since they can now be called from detach/attach.  This is not ideal, since it will assert then.  This changes the code so that it won't update the annotations during attach/detach, but also won't push the annotation layer unless a mouse is connected, achieving the same result as before, but with better semantics.
The basic problem is that in the detach for RenderPointerListener, it would detach the annotation, which could cause onExit to be called on the annotation, since the widget was disappearing under the mouse, and thus needs to receive an onExit, but that onExit might be (and probably will be) calling setState, which marks the owning widget as needing to be built, sometimes when it already has been.
The fix creates a new _ListenerElement that overrides activate and deactivate in order to tell the render object ahead of the detach that it might be detached, and so the onExit gets called before the detach instead of during it.
In addition, I now avoid scheduling more than one check for mouse positions per frame.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[X] I signed the CLA.
[X] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[X] I updated/added relevant documentation (doc comments with ///).
[X] All existing and new tests are passing.
[X] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[X] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] No, this is not a breaking change.

This is not ideal, since it will assert

Can you add a test case for this so we never switch it back?

Actually, in writing the test case, I found that I didn't always fix it, so I learned (again) the value of testing!
In any case, I was able to fix the underlying problem, but the fix is a bit esoteric. The basic problem is that in the detach for RenderPointerListener, it would detach the annotation, which could cause onExit to be called on the annotation, since the widget was disappearing under the mouse, and thus needs to receive an onExit, but that onExit might be (and probably will be) calling setState, which marks the owning widget as needing to be built, sometimes when it already has been.
The fix creates a new _ListenerElement that overrides activate and deactivate in order to tell the render object ahead of the detach that it might be detached, and so the onExit gets called before the detach instead of during it.
I did write some tests...

@goderbauer could you please take another look?

I am hoping that this will fix the test failures I am seeing in https://github.com/flutter/flutter/pull/32192.

No, those failures (at least the one I saw) were because the callback was null, but _onPointerHoverInternal wasn't checking for a null callback before trying to call it.


Make AzureError ObjC compatible

Is your feature request related to a problem? Please describe.
AzureError is not ObjC compatible.
Describe the solution you'd like
If AzureError was ObjC compatible, we could use it in our Communication package, keeping it consistent with the rest of the codebase.
Describe alternatives you've considered
Right now we're using the Error base class instead.
Additional context
It is a requirement for the Communication package to support ObjC for our internal ObjC libraries.

This is going to have to be addressed as part of a larger effort to bridge our Swift-based Core library with ObjectiveC-based client libraries. Closing this issue but we will cover it as part of this much larger effort.


Remove unused variable: until

The variable until was unused so I removed it

Thank you so much for the effort you have put into this PR!
However, since we completely re-worked the entire codebase of Now CLI, I'm not closing your Pull Request. Feel free to re-open it based on the new code, though!
You can read more about our biggest release yet here: https://zeit.co/blog/now-2


SR-1511: Handle out-of-range projection inputs

A comprehensive solution to @mattieudv's problems...
The new katpoint.OutOfRange class handles out-of-range values in the spherical projection routines. Inspired by NumPy's seterr machinery, it maintains a global treatment option (using class attributes) that can be changed permanently or temporarily using a with-statement like so:
with OutOfRange.set_treatment('clip'):
    ...

The following treatment options are available:

'raise': raise katpoint.OutOfRangeError (default)
'nan': replace out-of-range values with NaNs
'clip': replace out-of-range values with nearest valid values

The new exception is more specific but still derives from ValueError to maintain backwards compatibility. The default treatment is 'raise' for the same reason.
I will port this to ska-katpoint as well in due time.

A nice picture of the SSN valid region in the plane for a source at 60 degrees elevation, produced like this:
import numpy as np
import matplotlib.pyplot as plt
import katpoint

phi = np.linspace(0, 2 * np.pi, 200)
x0, y0 = np.cos(phi), np.sin(phi)
with katpoint.OutOfRange.set_treatment('clip'):
    az, el = katpoint.plane_to_sphere['SSN'](0.0, np.radians(60), x0, y0)
    x1, y1 = katpoint.sphere_to_plane['SSN'](0.0, np.radians(60), az, el)

fig, ax = plt.subplots()
ax.plot(x0, y0)
ax.plot(np.r_[x1, x1[0]], np.r_[y1, y1[0]])
ax.axis('equal')

There's a lot of code here so I'll only get stuck into the details next week, but my first reaction is that it would be better to make this context-local state (using the contextvars package; there is a backport for older Python versions).

Thanks, that's exactly why I put your name on the list :-) I was also wondering if I could tie it into the Astropy ScienceState object used to override eg the Solar System ephemeris.

I was wondering about thread-safety and future locking requirements as I wrote this, but contextvars is a much better idea!

Another general idea: a fourth treatment which behaves the same as clip but emits a warning (with warnings.warn). That could be useful for automatic pipelines where it's desirable not to crash but clipping needs to be investigated.

A slight problem: contextvars is only backported as far as Python 3.5, and I probably want to keep the 2.7 support for katpoint  v0.x. I'll definitely switch to it in katpoint v1.x but are there any alternatives for now?

The closest then is probably Threading.local, which will keep state
thread-local but not async-task-local.
On Mon, 7 Dec 2020 at 00:31, Ludwig Schwardt<EMAIL_ADDRESS>wrote:

A slight problem: contextvars is only backported as far as Python 3.5, and
I probably want to keep the 2.7 support for katpoint v0.x. I'll definitely
switch to it in katpoint v1.x but are there any alternatives for now?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/ska-sa/katpoint/pull/67#issuecomment-739575912, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAO7PKAFXYAQUAJAUDQAYVDSTQA2JANCNFSM4UNFS4JQ
.

--
Bruce Merry
Senior Science Processing Developer
SARAO

There is no ignore option - I'll have to add one quickly :-)
The clip option finds the closest valid point to the backside of the beam, typically on the unit circle for SIN projections. So your points will be squashed onto the boundary, but at least will be valid. This is good for treating slews when the target suddenly jumps elsewhere.

The most immediate problem is where a single az/el value in a scan is corrupted by the katdal interpolation without employing unwrapping, resulting in a spurious out of range value (where katpoint then raises an exception). I guess clip will fix this in the interim. My code will anyways detect that the single sample value is far off from where it is supposed to be and discard it.

OK, I've addressed 95% of @bmerry's concerns, I think. @mattieudv, please have another look.


[Service Bus] Control number of msgs that should be processed concurrently

The following is the result of investigating #1314
Previously, we depended on the credit_window property of the rhea receiver link to provide the feature of concurrent message processing to the user.
While credit_window does indeed control the max number of messages received by rhea buffer, it does not guarantee the number of messages being processed by our streaming receiver. If the user's onMessage handler does any async work, then the event loop is free to call the same handler for the next message.
To control the number of messages that the user's message handler is called for at a given time, we need to do the credit management ourselves.
In this PR,

we disable automatic credit management by setting credit_window to 0 when creating rhea receiver links
manual credit management is done by adding single credit each time the user's message handler completes processing a message
by adding the number of credits as configured in maxConcurrentCalls, we ensure that rhea sends the message` event a max of those many times
renaming maxConcurrentCallsPerSession to maxConcurrentCalls to reduce confusion for the user. This distinction matters only for session manager which we do not expose yet.
expose the maxConcurrentCalls option to the user when they use the streaming receiver
test behavior when maxConcurrentCalls is not passed, when value of 1 is passed and when value of more than 1 is passed

I like it. Default 1 for maxCurrentCalls makes sense (unlike what I said earlier).
Does anyone like calling the option concurrency? It's a bit shorter, not sure if it loses any meaning.


Remove "Upgrade Policy" link for device Supervisor

Removed this link because it's been superseded by https://github.com/balena-io/docs/blob/master/pages/reference/supervisor/supervisor-upgrades.md#upgrade-paths

@balena-ci I self-certify!


Concatenating arrays from different devices results in a CUDARuntimeError

Conditions (you can just paste the output of python -c 'import cupy; cupy.show_config()')

CuPy Version          : 7.3.0
CUDA Root             : /usr/local/cuda
CUDA Build Version    : 10010
CUDA Driver Version   : 10010
CUDA Runtime Version  : 10010
cuBLAS Version        : CUBLASError('CUBLAS_STATUS_NOT_INITIALIZED')
cuFFT Version         : 10101
cuRAND Version        : 10101
cuSOLVER Version      : (10, 2, 0)
cuSPARSE Version      : 10300
NVRTC Version         : (10, 1)
cuDNN Build Version   : 7605
cuDNN Version         : 7605
NCCL Build Version    : 2506
NCCL Runtime Version  : 2506

Code to reproduce

import cupy
print(cupy.__version__)

arrs = []
rng = cupy.random.RandomState(1994)

for i in range(100):
    cupy.cuda.runtime.setDevice(i % 2)
    a = rng.randn(1000, 100)
    arrs.append(a)

cat = cupy.concatenate(arrs, axis=0)

Error messages, stack traces, or logs

Traceback (most recent call last):
  File "with-cupy.py", line 14, in <module>
    cat = cupy.concatenate(arrs, axis=0)
  File "/home/fis/Workspace/XGBoost/lib/python3.7/site-packages/cupy/manipulation/join.py", line 54, in concatenate
    return core.concatenate_method(tup, axis)
  File "cupy/core/_routines_manipulation.pyx", line 577, in cupy.core._routines_manipulation.concatenate_method
  File "cupy/core/_routines_manipulation.pyx", line 623, in cupy.core._routines_manipulation.concatenate_method
  File "cupy/core/_routines_manipulation.pyx", line 649, in cupy.core._routines_manipulation._concatenate
  File "cupy/core/_routines_manipulation.pyx", line 770, in cupy.core._routines_manipulation._concatenate_single_kernel
  File "cupy/core/core.pyx", line 134, in cupy.core.core.ndarray.__init__
  File "cupy/cuda/memory.pyx", line 544, in cupy.cuda.memory.alloc
  File "cupy/cuda/memory.pyx", line 1243, in cupy.cuda.memory.MemoryPool.malloc
  File "cupy/cuda/memory.pyx", line 1264, in cupy.cuda.memory.MemoryPool.malloc
  File "cupy/cuda/memory.pyx", line 1042, in cupy.cuda.memory.SingleDeviceMemoryPool.malloc
  File "cupy/cuda/memory.pyx", line 1062, in cupy.cuda.memory.SingleDeviceMemoryPool._malloc
  File "cupy/cuda/memory.pyx", line 764, in cupy.cuda.memory._try_malloc
  File "cupy/cuda/memory.pyx", line 761, in cupy.cuda.memory._try_malloc
  File "cupy/cuda/memory.pyx", line 1011, in cupy.cuda.memory.SingleDeviceMemoryPool._alloc
  File "cupy/cuda/memory.pyx", line 499, in cupy.cuda.memory._malloc
  File "cupy/cuda/memory.pyx", line 500, in cupy.cuda.memory._malloc
  File "cupy/cuda/memory.pyx", line 99, in cupy.cuda.memory.Memory.__init__
  File "cupy/cuda/runtime.pyx", line 296, in cupy.cuda.runtime.malloc
  File "cupy/cuda/runtime.pyx", line 201, in cupy.cuda.runtime.check_status
cupy.cuda.runtime.CUDARuntimeError: cudaErrorIllegalAddress: an illegal memory access was encountered

I'm using cupy with dask on multiple GPUs.  If the operation is not supported, a more friendly error message for further debugging would be appreciated. ;-)

Thanks for the report.
The array should be explicitly moved to the device before doing the concatenation, but I believe that there should be an assertion that prints a friendly error message.

might be relevant: https://github.com/dask/dask/issues/5992

@trivialfis  How many GPUs your environment has?

2 GPUs for reproducing the issue.

Sorry, I completely saw wrong.


Upgraded cedar to 4.2.0

Description of changes
Issue #, if available
Checklist for requesting a review
The change in this PR is (choose one, and delete the other options):

[ ] A breaking change requiring a major version bump to cedar-local-agent (e.g., changes to the signature of an
existing API).
[ ] A backwards-compatible change requiring a minor version bump to cedar-local-agent (e.g., addition of a new API).
[ ] A bug fix or other functionality change requiring a patch to cedar-local-agent.
[ ] A change "invisible" to users (e.g., documentation, changes to "internal" crates, etc.)
[ ] A change (breaking or otherwise) that only impacts unreleased or experimental code.

I confirm that this PR (choose one, and delete the other options):

[ ] Updates the "Unreleased" section of the CHANGELOG with a description of my change (required for major/minor
version bumps).
[ ] Does not update the CHANGELOG because my change does not significantly impact released code.

Testing
Add a description on how the code changes were tested, if applicable.
Hint: run ./scripts/build_and_test.sh script to validate your changes locally before submitting a PR.

Thanks for opening this @l-kli – I'm looking forward to being able to upgrade to Cedar 4.


Keey history of "Find All References"

I'm just trying to make another attempt to collect votes for this important productivity feature. The way it works currently is rather inefficient and inferior to how other IDEs do it. For example, IntelliJ has an option to open each references search in a new tab.
For full description, please see #176586.

Closed as duplicate (which was accidentially locked)