Different resource name in preview plan and after deployment

How to reproduce:

Simple resource group definition

var resourceGroup = new ResourceGroup("foobar");

Run pulumi up with details and then select yes to deploy

$ pup
Please choose a stack, or create a new one: dev
Previewing update (dev)

View Live:

     Type                         Name           Plan
 +   pulumi:pulumi:Stack          pws-lab01-dev  create
 +   └─ azure:core:ResourceGroup  foobar         create

Resources:
    + 2 to create

Do you want to perform this update? details
+ pulumi:pulumi:Stack: (create)
    [urn=urn:pulumi:dev::pws-lab01::pulumi:pulumi:Stack::pws-lab01-dev]
    + azure:core/resourceGroup:ResourceGroup: (create)
        [urn=urn:pulumi:dev::pws-lab01::azure:core/resourceGroup:ResourceGroup::foobar]
        [provider=urn:pulumi:dev::pws-lab01::pulumi:providers:azure::default_3_24_0::04da6b54-80e4-46f7-96ec-b56ff0331ba9]
        location  : "westeurope"
        name      : "foobar8c6de1f5"

Do you want to perform this update? yes
Updating (dev)

View Live:

     Type                         Name           Status
 +   pulumi:pulumi:Stack          pws-lab01-dev  created
 +   └─ azure:core:ResourceGroup  foobar         created

Resources:
    + 2 created

Duration: 50s

Run pulumi stack -i

$ pulumi stack -i
Current stack is dev:
    Owner: evgenyb
    Last updated: 46 seconds ago (2020-10-06 13:36:33.0312218 +0200 CEST)
    Pulumi version: v2.11.2
Current stack resources (3):
    TYPE                                           NAME
    pulumi:pulumi:Stack                            pws-lab01-dev
    ├─ azure:core/resourceGroup:ResourceGroup      foobar
    │     ID: /subscriptions/.../resourceGroups/foobar2ae87716
    └─ pulumi:providers:azure                      default_3_24_0
          ID: a6ce109d-5aa0-4385-8472-d68ac3dc63ca

Current stack outputs (0):
    No output values currently in this stack

More information at: https://app.pulumi.com/evgenyb/pws-lab01/dev

Use `pulumi stack select` to change stack; `pulumi stack ls` lists known ones

As you can see, the name of the resource shown at the plan is foobar8c6de1f5, but the actual resource group name is foobar2ae87716

Hi @evgenyb
Please can you tell me what version of pulumi and pulumi-azure you are using for this?
Paul

Hi @stack72,
Pulumi version: v2.11.2
pulumi-azure: 3.24.0

Thanks @evgenyb
I am seeing the sae behaviour
We can look into this
Paul

Hi @evgenyb
So I discussed this with the team internally - this is actually intended behaviour as there is no state being saved between a preview and an apply
There is an issue open in pulumi/pulumi to allow applies of a preview plan which would solve the issue
I hope this answers your question - sorry that it may not be what you were hoping :/
P.

Hi Paul,
I am fine with this behavior. I normally don't use autonamibg anyways, but during the workshop me and other attendee noticed that behavior and it looked a bit suspicious, so, I just wanted your team to know in case it's actually a bug :) Feel free to close this issue.
Thanks
Evgeny

Thanks @evgenyb for being in contact about this!


reports: add type statistics to report file

Proposed changes
Mutant type statistics are added in the root of the file. zero values are omitted
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[ ] I have read the CONTRIBUTING doc
[ ] Lint and unit tests pass locally with my changes (make all)
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments

Closed #134


Update README.md for today's v2.1 release

CBOR Tags, Duplicate Map Key detection, 26% faster CBOR decoding, 57% fewer allocs, etc.  Add "Quick Start" section. Too many other changes to list.

@fxamacker, this will close #156.  I'll start drafting release notes while you review this.


System.Threading.ThreadPool Downgrade?

I upgraded this package to the latest stable while cleaning up unused references in older project.
I removed the MySQL.Data package to let Nuget implicitly decide on the version.
Now I have this:
  Shoko.Server.csproj: [NU1605] Detected package downgrade: System.Threading.ThreadPool from 4.3.0 to 4.0.10. Reference the package directly from the project to select a different version.
 Shoko.Server -> MySqlBackup.NET 2.3.1 -> MySql.Data 8.0.17 -> SSH.NET 2016.1.0 -> System.Net.Sockets 4.1.0 -> runtime.unix.System.Net.Sockets 4.3.0 -> System.Threading.ThreadPool (>= 4.3.0)
 Shoko.Server -> MySqlBackup.NET 2.3.1 -> MySql.Data 8.0.17 -> SSH.NET 2016.1.0 -> System.Threading.ThreadPool (>= 4.0.10)

I obviously plan to do what it says, but the fact that this happens is annoying. As far as I can tell, it's not actually the fault of this project, but MySQL,Data. Unfortunately, I think that's closed source, so I can't do anything about it. If you explicitly reference the version, it should cascade and prevent the need for users to do it, though...I think.

During compilation of the DLL, this project was bound with specific version of MySql.Data. I still unsure how to unbound with specific version MySql.Data, so that MySqlBackup.NET can freely work with any version of MySql.Data.
So, in order to keep up the new releases of MySql.Data, this project need to be continuously re-released even without any major changes.
I believe there should be a workaround for this problem, but I'm unable to find one at the moment.
If you do find the solution, you may reply at the post. Thanks.

I will release a new nuget package later today.

Hi, new version of nuget package is released.

Thanks


Adding cleaned up dosomething_campaign module POT file.

Fixes #5222
What's this PR do?
This PR adds the extracted POT file for the dosomething_campaign module that has been edited to only add strings immediately needed for translation.
Where should the reviewer start?
Just review the strings to make sure all seems well.
Any background context you want to provide?
Strings relating to the CMS admin interface have been pulled out for the time being since we do not require them to be translated.
What are the relevant tickets?
#5147
#5222

@angaither

:+1:


Potential Sites For Displacement Camps

https://nsec.esri.com/arcgis/home/item.html?id=e38ef635741b4ca793d35935f1666667

[x] Title?
[x] Description?
[x] No Access and Use Constraints
[x] No Credits
[x] Delete Protection Disabled

[ ] Description and Summary are the same

Verified


Incompatibility with new mongodb driver?

Hi,
The driver works fine with the legacy pecl mongodb driver: https://pecl.php.net/package/mongo
However, it looks like there is incompatibility with the new driver: https://pecl.php.net/package/mongodb
More info about the two drivers here: https://docs.mongodb.org/ecosystem/drivers/php/
Any pointers?
Thank you

I confirm this. I installed only the new mongodb pecl driver and laravel-mongodb, and it returns Class 'MongoClient' not found
I have installed and successfully enabled the extension in both cli and fpm .ini file
Both phpinfo() to fpm and php -i confirm the correct installation:
mongodb

mongodb support => enabled
mongodb version => 1.0.0
mongodb stability => stable
libmongoc version => 1.2.0
libbson version => 1.2.0

Lavarel MongoDB only works with deprecated mongo driver at the moment.

@jenssegers do you have any plan to support new mongodb driver?

I should check out what the differences are between the old and new version. Is there a changelog or something we can check with differences between the two?

This is the new version of mongodb driver:
http://mongodb.github.io/mongo-php-driver/

Since Laravel MongoDB doesn't play well with deprecated mongo driver in HHVM, implementing the new driver mongodb would enable everyone that runs HHVM to use Laravel with MongoDB
The issue with Laravel MongoDB and HHVM is explained here and it seems unfixable for this reason.

I am getting 'SASL Authentication failed on database' error when attempting to connect to a remote database. No error when using the latest driver?!
Any pointers to integrate this driver to the library Jens?

Also with php7.

I forked this repo yesterday to see how easy it would be to implement the new driver. It's very different to the 'legacy' one and even with the userland library, there is a lot of work to be done. I like the new driver and library but some things are trickier. For instance (and I could very well be mistaken here) but the new driver doesn't seem to expose MongoDB's cursor methods like the old library.

@syntheticminds Do you know if there's already a homebrew version of the new mongodb ext?

I wouldn't know; I use Homestead. If you provision a box with the following in ~/.homestead/after.sh, you'll be running the new driver.
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 7F0CEB10
echo "deb http://repo.mongodb.org/apt/ubuntu trusty/mongodb-org/3.0 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-3.0.list

sudo apt-get update
sudo apt-get install mongodb-org pkg-config libsasl2-dev -y

sudo pecl install mongodb

echo 'extension=mongodb.so' | sudo tee /etc/php5/mods-available/mongodb.ini
sudo ln -s /etc/php5/mods-available/mongodb.ini /etc/php5/fpm/conf.d/mongodb.ini
sudo ln -s /etc/php5/mods-available/mongodb.ini /etc/php5/cli/conf.d/mongodb.ini

sudo service php5-fpm restart

I guess there are two approaches to get PHP 7 and HHVM support:

Use the mongodb/mongo-php-library. It does take a lot of the heavy lifting out and then cursor opperations can be performed as options on the queries themselves.
Use mongofill/mongofill so the MongoDB extension isn't even needed. Not sure what the performance hit is and the repo looks a bit quiet.

Has there been any updates to when mongodb will be considered as the driver for this package?

I'm working on a new version, but a lot of stuff has changed.

Thanks! That is good to know!

I currently pushed my "work in progress" changes to this branch: https://github.com/jenssegers/laravel-mongodb/tree/pecl-mongodb
Tests are still failing, would be great to have some pull requests so that we can release this faster!

I only see 1 failed test in travis , is there more that need to be tested ? I can possibly work on this later tomorrow

@lukepolo No there are still more tests failing, check my last push.

Hi, I just ran the tests on the pecl-mongodb branch and everythings seems to work properly with the new driver and PHP 7 (on ArchLinux)
I just ran into one issue with the whereIn function that doesn't match anymore the Laravel Collection whereIn signature…

Hi, I have installed mongo-hhvm driver with php version of 5.6. I have connected the mongo database while executing hhvm filename.php. I got an error as
"Uncaught exception: Could not open extension /usr/lib/x86_64-linux-gnu/hhvm/extensions/20150212/mongo.so: /usr/lib/x86_64-linux-gnu/hhvm/extensions/20150212/mongo.so: cannot open shared object file: No such file or directory" .
In php.ini file , i have specified extensions as,
hhvm.dynamic_extension_path=/usr/lib/x86_64-linux-gnu/hhvm/extensions/20150212,
hhvm.dynamic_extensions[mongodb]=mongodb.so .
kindly provide me solution to proceed further.

What you get with phpinfo()? Can you paste the mongodb part in your results?

@paulocoghi  Thanks for your response ,also i have changed the hhvm.dynamic_extension_path to "/usr/lib/php/20131226/mongo.so"  and restarted the apache server. But it dint work it out, Can you please suggest to continue the process .

Now I see that you are trying to use the old mongo driver. Unfortunately laravel-mongodb doesn't play well with it in hhvm as I explained before.
You have two options:
1 - Use the new mongodb driver, available and stable in both HHVM and PHP7 along with laravel-mongodb version 3.x
2 - Use the old mongo driver with PHP 5.6, instead of HHVM

How do you install an earlier version like 3.0.x or 3.1.x?


Add list cell struct

Add a struct for a cell in the list output, so we can organize the list method in a more modular way. This will be followed by a list row struct.
Relates to #123
ps-id: 371dd7cb-b4bd-49b9-b9f5-bd743575dfe9

@drewdeponte yes that's the plan. The cell struct is created (alongside with the row struct in the next PR) to make the public list method a bit more maintainable and to allow conditionally adding and formatting the cells that make up a row.


Loss function - How can I use L1 loss train the network?

Hello @tarashakhurana ,
I want to use L1 loss to train the network as your mentioned in your paper. But in this repo, L1 loss is not used.
Could you provide the code for using L1 loss for training?

Hi, I'm not sure I understand your question. We do use L1 loss for training, as specified here. One potential confusion to clarify is that we manually compute the gradient of the loss function with respect to the density grid. You can find that implemented here. With the current code, only L1, L2 and AbsRel losses can be used to train the model. If you need to train with any other loss, I can provide a Differentiable Voxel Rendering layer in PyTorch that does not require manual gradient computation but takes up a huge memory.

Hi, thanks for the explanation.
I want a Differential Voxel Rendering layer in PyTorch to try it more flexibly. Could you please share it?

@tarashakhurana When can you provide the code of the Differential Voxel Rendering layer in PyTorch?
I am blocked by this part for a long time and expect your feedback. Many thanks.

Thanks for the reminder! I have added it now: https://github.com/tarashakhurana/4d-occ-forecasting/tree/main#new-differentiable-voxel-rendering-implemented-as-a-layer-in-pytorch

It worked. Thanks a lot.


Where ExchangeServiceBase.preAuthenticate is used?

I think this field comes from C# code, and could not found it's usage.

it´s being set but never used with the HttpWebRequest

@evpaassen's last change touched on this.  I also just sent him a question about whether there is a reason why we wouldn't drop it since it is dead code.

In #22, I enabled preemptive authentication, but this has been removed (unintendedly) when migrating to HttpClient 4 in #113, #126. My implementation in #22 should have used this preAuthenticate field to disable preemptive authentication when performing a plain HTTP autodiscover request, but it didn't.
So currently, it is dead code indeed. But preemptive authentication should be re-implemented in the correct way and the preAuthenticate field of HttpWebRequest should be used to determine whether preemptive auth should be enabled for that single request.
It's not a big deal, but it would save some overhead. I could try to reimplement it correctly when I have some time. I'd suggest leaving this code in place until then. I already added comments about this on the getter and setter of preAuthenticate in HttpWebRequest.


patch redash

id - this field has been removed
object_id - can be string OR int
created_at - does not conform to valid date-time

@alexanderdean @chuwy sorry for missing your last comment - yes happy for this to be released!  Have also checked and it validates against the latest redash still (v5.0.2).
Do you want me to re-generate the SQL and JsonPaths?  Considering this schema is totally broken without this patch not sure there is any harm in force updating those assets as well.

Force regenerated everything @chuwy !

Closing in favor of https://github.com/snowplow/iglu-central/pull/860. Thanks.


Handle an empty .gitmodules in a submodule

This should fix #18

Thanks, Ivan.

No, thank you!  This script saved me a lot of work and heartache!


Why an internal slot and not a symbol?

Minor question, but it seems like if the [[Metadata]] internal slot were instead a Symbol.metadata ordinary property, then this proposal could be implemented 100% in an ordinary JS library as a decorator. Is that right? What's the reasoning for going down the path of making it more built-in in this way?

In particular, rather than making these new MOP operations, the semantics can be simply, "get the Symbol.metadata, and then get/set the metadata property there; or, create a new empty object and put it in Symbol.metadata if needed".

Primarily, it is to allow metadata mutation on a frozen object. This helps avoid issues with decorator execution order if one decorator freezes the class before another can apply metadata. It also enforces a structure on the data that is consistent that you cannot guarantee if it is a symbol-named property.

I am considering adding a compatibility mode to read metadata from Symbol.metadata if it is present, but that is fairly low on my list of priorities at the moment. I will revisit this when I have more time available.


Adding the new note for quota expiry in 30 days.

@jjaygbay1 - can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

merged


added invert-matrix to /science/mathematics/linear_algebra

part of #450

Awesome. Got pulled away mid review but hope to finish that today.
On Thu, Dec 27, 2018, 8:49 AM Stefan Mesken<EMAIL_ADDRESS>wrote:

@KappaDistributive commented on this pull request.
In src/science/mathematics/linear_algebra/invert-matrix.md
https://github.com/rust-lang-nursery/rust-cookbook/pull/508#discussion_r244188454
:

+fn main() {

let m1 = Matrix3::new(2.0, 1.0, 1.0, 3.0, 2.0, 1.0, 2.0, 1.0, 2.0);
println!("m1 = {}", m1);
match m1.try_inverse() {

   Some(inv) => {

       println!("The inverse of m1 is: {}", inv);

   }

   None => {

       println!("m1 is not invertible!");

   }

}
+}
+```

+[nalgebra::Matrix3]: https://docs.rs/nalgebra/0.10.1/nalgebra/struct.Matrix3.html
Thanks for catching that mistake! I've fixed it in the recent commit.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang-nursery/rust-cookbook/pull/508#discussion_r244188454,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGOQ3s2HiU1ahG8-ngLRN4OmnJ2_UfNCks5u9Po0gaJpZM4ZhUY9
.


ft: azure list parts

Adds listParts API for Azure data backend. No calls actually need to be made to Azure since the part metadata is stored in Scality S3, so only tests included.

@ironman-machine try

Hello @dora-korpar
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/14915' with the following env. args:
{
    "SCALITY_INTEGRATION_BRANCH": "ultron/master",
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "master",
    "SCALITY_S3_BRANCH": "ft/azure-listparts"
}

@ironman-machine r+

:hourglass: PR is now pending. CI build url: http://ci.ironmann.io/gh/scality/Integration/14936

Hello @dora-korpar
"r+": Success

:sunny: :+1: circleCI test succeeded!


socket2 fails to build

Hi,
I'm not sure if this is an issue with me or with the socket2 library, but it seemed to appear out of the blue.  That is, there is no clear event between before (when my project was building) and after (when my project was failing to build) to which I can attribute this breakage.  socket2 is buried deep within my dependency tree -- it is not in my project's Cargo.toml.
The error
error[E0583]: file not found for module `sys`
  --> /home/me/.cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.3.8/src/lib.rs:72:5
   |
72 | mod sys;
   |     ^^^
   |
   = help: name the file either sys.rs or sys/mod.rs inside the directory "/home/me/.cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.3.8/src"
error: aborting due to previous error

rustc --version
rustc 1.30.0-nightly (3bc2ca7e4 2018-09-20)

The dependency chain (as near as I can tell)
actix v0.7.4 -> trust-dns-resolver v0.9.1 -> trust-dns-proto v0.4.0 -> socket2 v0.3.8

If this is not actually a problem with the library, could someone please explain to me how to resolve it on my end?  Thank you.

 Apologies.

@wayeast Can you elaborate on how you got this error? Seems to have come up for me out of the blue as well.


Cannot quit fzf early with --exit-0 or --select-1

Category

[X] fzf binary
[ ] fzf-tmux script
[ ] Key bindings
[ ] Completion
[ ] Vim
[ ] Neovim
[ ] Etc.

OS

[X] Linux
[ ] Mac OS X
[ ] Windows
[ ] Windows Subsystem for Linux
[ ] Etc.

Shell

[X] bash
[X] zsh
[ ] fish

Running the following (in bash or zsh) and pressing escape or enter immediately causes fzf to quit with the appropriate exit code.
fzf < <(sleep 10; echo 123; sleep 10; echo 456)

Running with the --exit-0 or --select-1 flag, however, pressing escape/enter has no effect until the sleep 10 has finished.
fzf --exit-0 < <(sleep 10; echo 123; sleep 10; echo 456) # stall for 10s
fzf --select-1 < <(sleep 10; echo 123; sleep 10; echo 456) # stall for 20s

(Note this is different from (sleep 10; echo 123) | fzf which is the shell stalling, not fzf.)

Well, they are designed to work that way. The purpose of the options is not to start the interactive finder when it's not needed, not to cause unnecessary flickering of the screen while running your script. See #27 and #36 for the background.


#186 manual secret entry (2)

Hi,
Thank you very much for the pull request @igor2890 , I appreciate your willingness to contribute to the project.
I have not tested the functionality yet, but first let me add some comments about the UI.
I am recently working on adding manual secret entry to FreeOTP Android, for uniformity across platforms could you please match this UI as closely as possible ? Digits can remain 6 through 9 unlike in the screenshot.

Please also change "Enter OTP" to "Manual Add".
Instead of "Some problems", please use the alert dialog box messages as below:
	Token is invalid!

	The token you are attempting to add is invalid. Please check that each field is valid following the OTP Key Uri Format.

You may also want to add a 'Lock' checkbox which can be enabled. It should warn that locked tokens will not be included in backups.
It would be great to add a UITest for this also.
It looks like the git commit history needs to be cleaned up also.

Hello @justin-stephenson !
Thanks for your feedback. Of course, I will consider all your comments.
About the "Lock" checkbox - I used an already existing screen URILockViewController for this purpose.

Hello @justin-stephenson ! Thanks for your feedback. Of course, I will consider all your comments. About the "Lock" checkbox - I used an already existing screen URILockViewController for this purpose.

Okay great, that works also.
If you have any questions just let me know.

Replaced by https://github.com/freeotp/freeotp-ios/pull/281


Adding React-Toolbox to the feature/postcss-sass branch.

Looking to integrate the react-toolbox for Material Design UI elements.
https://github.com/react-toolbox/react-toolbox
There seems to be some issues with the webpack/postcss/sass-loader processing. For example the below after using import { Button } from 'react-toolbox/lib/button';
==> SERVER -> Error in server execution, check the console for more info.
/Users/corey/Projects/coreygo/coreygo/node_modules/react-toolbox/lib/ripple/theme.scss:1
(function (exports, require, module, __filename, __dirname) { @import "../colors";
                                                              ^
SyntaxError: Invalid or unexpected token
    at Object.exports.runInThisContext (vm.js:76:16)
    at Module._compile (module.js:542:28)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/corey/Projects/coreygo/coreygo/node_modules/react-toolbox/lib/ripple/index.js:13:14)
    at Module._compile (module.js:570:32)

I've never been able to get react-toolbox to work with any universal webpack configurations. That being said, you'll need to add configuration to sass-loader.
  sassLoader: {
    data: '@import "theme/_config.scss";',  // the sass file where you import react toolbox
    includePaths: __Shared_Folder_Path__
  },

Seems they've switched from SASS to PostCSS, using "react-toolbox": "^2.0.0-beta.4", still seems to have issues with or without the sass-loader.
Was able to basically rewrite the components and get them to work but that's a rather dumb workaround :)

I'll see about digging into this some more this afternoon. Its always something I'd like to use, but never actually do because of this very issue.

Cool. The readme.md for "react-toolbox": "^2.0.0-beta.4" isn't up to date :)
Here's what my fork of react-universally currently includes, sort of combining flow, postcss-sass, and apollo feature branches, also added bluebird and redux-saga:
package.json
  "dependencies": {
    "apollo-client": "^0.7.1",
    "apollo-server": "^0.3.3",
    "app-root-dir": "1.0.2",
    "bluebird": "^3.4.7",
    "body-parser": "^1.15.2",
    "code-split-component": "2.0.0-alpha.5",
    "colors": "1.1.2",
    "compression": "1.6.2",
    "dotenv": "4.0.0",
    "express": "4.14.0",
    "graphql": "^0.8.2",
    "graphql-tag": "^1.2.2",
    "graphql-tools": "^0.9.0",
    "helmet": "3.3.0",
    "hpp": "0.2.1",
    "normalize.css": "5.0.0",
    "offline-plugin": "4.5.4",
    "react": "15.4.2",
    "react-addons-css-transition-group": "^15.4.2",
    "react-apollo": "^0.8.1",
    "react-dom": "15.4.2",
    "react-helmet": "3.3.0",
    "react-jobs": "^0.5.0",
    "react-redux": "^5.0.2",
    "react-router": "4.0.0-alpha.6",
    "react-toolbox": "^2.0.0-beta.4",
    "redux": "^3.6.0",
    "redux-saga": "^0.14.2",
    "serialize-javascript": "1.3.0",
    "user-home": "2.0.0",
    "uuid": "3.0.1"
  },
  "devDependencies": {
    "assets-webpack-plugin": "3.5.0",
    "babel-cli": "6.18.0",
    "babel-core": "6.21.0",
    "babel-eslint": "7.1.1",
    "babel-jest": "18.0.0",
    "babel-loader": "6.2.10",
    "babel-plugin-syntax-flow": "^6.18.0",
    "babel-plugin-transform-flow-strip-types": "^6.21.0",
    "babel-plugin-transform-react-jsx-self": "6.11.0",
    "babel-plugin-transform-react-jsx-source": "6.9.0",
    "babel-polyfill": "6.20.0",
    "babel-preset-env": "1.1.8",
    "babel-preset-latest": "6.16.0",
    "babel-preset-react": "6.16.0",
    "babel-preset-stage-3": "6.17.0",
    "babel-template": "6.16.0",
    "chokidar": "1.6.1",
    "cross-env": "3.1.4",
    "css-loader": "0.26.1",
    "enzyme": "2.7.0",
    "enzyme-to-json": "1.4.5",
    "eslint": "3.13.1",
    "eslint-config-airbnb": "14.0.0",
    "eslint-plugin-flowtype": "2.29.2",
    "eslint-plugin-import": "2.2.0",
    "eslint-plugin-jsx-a11y": "3.0.2",
    "eslint-plugin-react": "6.9.0",
    "extract-text-webpack-plugin": "^2.0.0-beta.5",
    "file-loader": "0.9.0",
    "flow-bin": "^0.37.4",
    "flow-coverage-report": "^0.2.0",
    "flow-typed": "^2.0.0",
    "glob": "7.1.1",
    "happypack": "3.0.2",
    "html-webpack-plugin": "2.26.0",
    "isomorphic-fetch": "^2.2.1",
    "jest": "18.1.0",
    "md5": "2.2.1",
    "node-notifier": "4.6.1",
    "node-sass": "^4.3.0",
    "postcss": "^5.2.10",
    "postcss-cssnext": "^2.9.0",
    "postcss-import": "^9.1.0",
    "postcss-loader": "^1.2.2",
    "postcss-simple-vars": "^3.0.0",
    "react-addons-test-utils": "15.4.2",
    "react-hot-loader": "3.0.0-beta.6",
    "regenerator-runtime": "0.10.1",
    "rimraf": "2.5.4",
    "sass-loader": "^4.1.1",
    "semver": "5.3.0",
    "source-map-support": "0.4.8",
    "style-loader": "0.13.1",
    "webpack": "2.2.0-rc.3",
    "webpack-bundle-analyzer": "2.2.1",
    "webpack-dev-middleware": "1.9.0",
    "webpack-hot-middleware": "2.15.0",
    "webpack-md5-hash": "0.0.5",
    "webpack-node-externals": "1.5.4"
  }

@coreygo I would look into this https://github.com/react-toolbox/react-toolbox-themr
I'll be trying it later this afternoon, but it should solve the problem.

Was there a solution to this? Other libraries aside from react-toolbox also run into this issue.

@RishabhJain96 please look into my setup in my branch of feature/react-toolbox-sass, I've been able to make<EMAIL_ADDRESS>running without problem so far.
I will make a PR for this branch anyway. Cheers.

@diondirza your diff worked against my fork. So<EMAIL_ADDRESS>is working well now. I was hoping to get it sorted with<EMAIL_ADDRESS>but for now it probably makes more sense to stick with the former version.
Thanks for sorting that.

@diondirza could you clarify something for me? toolbox.theme.scss seems to have no effect over the input color styling. Am I missing something about how it is being used? Clearing the file makes no difference.

@coreygo If you look at their documentation there are two ways to theming react-toolbox. By using sass loader configuration in data prop to override some of their global variables or specifically per component you want. Like the way I put it on Home.js
configFactory.js line 410 & 417
{
  path: 'sass-loader',
  options: {
    sourceMap: true,
    sourceMapContents: true,
    outputStyle: 'expanded',
    data: `@import "${path.resolve(appRootDir.get(), './src/shared/components/DemoApp/toolbox.theme.scss')}";`,
  },
},

In that branch I used both of them so someone could pick what way they want. There is some glitch while you theming globally using file toolbox.theme.scss, if you run your app in development env it won't be applied, yet if in production env it will run properly. There must be something not right with how inline css loaded with webpack. Yet I don't know until now how to fix it.

Closing this for now.

Anyone ever get react-toolbox ver2 (with postcss instead of sass) to work with server rendering? It's rendering alright on the client but postcss seems not to run on the server for some reason. No matter what I do, I keep getting the unexpected token : when it tries to process css vars. At one point I had it loading fine in the browser (but still getting the server error), but now I just get a white page with ERR connection refused as soon as I import anything from RT. I'm using the same config as before, so I guess a package update must be responsible for the change in behavior. Either way, something's not right. It's strange, because postcss (at least autoprefixer) and css modules are running without issue for my custom SASS.
Anyhoo, in case anyone has any insight here's my config. Would love to get this running without having to resort to the themr tool. Note that I've made an explicit config for RT, and have explicitly excluded it from the general css configs.
        ifElse(isClient || isServer)(
          mergeDeep(
            {
              test: /\.css$/,
              include: path.join(appRootDir.get(), 'node_modules', 'react-toolbox'),
            },

            ifDevClient({
              use: [
                'style-loader',
                {
                  loader: 'css-loader',
                  options: {
                    modules: true,
                    sourceMap: true,
                    importLoaders: 1,
                    localIdentName,
                  },
                },
                'postcss-loader',
              ],
            }),

            ifProdClient(() => ({
              use: [
                ...ExtractTextPlugin.extract({
                  fallback: 'style-loader',
                  use: [
                    `css-loader?modules=1&importLoaders=1&localIdentName=${localIdentName}`,
                  ],
                }),
              ],
            })),

            ifNode({
              use: [
                'classnames-loader',
                `css-loader/locals?modules=1&importLoaders=1&localIdentName=${localIdentName}`,
                'postcss-loader',
              ],
            }),
          ),
        ),

Got it working by cloning react toolbox out of node_modules and into my project. It now works perfectly. So there's definitely something in the Webpack config that is excluding (or not including) the node_modules path from being processed on the server. The problem isn't the loader config from the repo that targets node_modules as I commented it out for testing. I also tried adding the React Toolbox path to JS/Babel processing in Values but that didn't do it either.
It's not an ideal situation, but for now I'm stumped trying to get React Toolbox to work if it lives where it should be in node_modules. I'm sure I'm missing something obvious, but if anyone has a hint it would be appreciated.

@unleashit I have made react-toolbox v2 working properly several months ago, now I have updated with latest master today. Maybe you could take a look at my branch here

@diondirza actually your repo was a big help but it wasn't my loader configs.  It was as I suspected... something to do with the careful (in a good way) security measures of RU. After diffing your values.js, I could see you added /node_modules/ to  nodeExternalsFileTypeWhitelist.
As soon as I did that, the lights went on in the room! Thanks very much for your help.


Update index.md

Add theprimeagen

Is he really an infosec hacker tho? He seems more like a loud obnoxious hype-train kinda dude...

Did you even read the title of where I added this person? Under coders

Yup, read it loud and clear -- that's not a persuasive way to get someone to merge your PR by the way.
So he's an infosec coder? Don't think so ...I've seen his stream before he's obnoxious and toxic.

Then you should remove some of the other streamers from the list. I've never seen, for example, cmgriffing do security coding or anything related. You just don't want to add someone "toxic" to the list.

You make a very good point -- I will look into all those since the list was
made as a direct copy from an original list:
https://docs.google.com/document/d/e/2PACX-1vR_h7BQvuL0cTfTBPA3ATwv8JZP4_YBsudR_FYoEtcxMD9q0x3KrF_WiHHT6UhzdaXhFt-ZkJ1qHbKZ/pub
On Sun, Mar 28, 2021 at 12:32 PM TheJoker @.***> wrote:

Then you should remove some of the other streamers from the list. I've
never seen, for example, cmgriffing do security coding or anything related.
You just don't want to add someone "toxic" to the list.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/infosecstreams/infosecstreams.github.io/pull/14#issuecomment-808947290,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQKI22IAZ6G3BSQOXSF7MVTTF6G6BANCNFSM4Z56244Q
.


Support for Data in JSON type #283

An attempt to add data property to JSON type (suggestion number two for possible solutions in #283) without the inefficiency of having to convert JSON back to data type

thanks for this, i was 10 minutes away of making the same improvement

thanks for this, i was 10 minutes away of making the same improvement

Thank you, works great


[KYUUBI #1039] Kill yarn job when engine initialize timeout and yarnApplicationState is ACCEPTED

kill yarn job when engine initialize timeout and yarnApplicationState is ACCEPTED
#1039
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #1119 (9eaeb16) into master (cbe5bee) will decrease coverage by 0.16%.
The diff coverage is 42.10%.

:exclamation: Current head 9eaeb16 differs from pull request most recent head 43a95c1. Consider uploading reports for the commit 43a95c1 to get more accurate results

@@             Coverage Diff              @@
##             master    #1119      +/-   ##
============================================
- Coverage     79.24%   79.07%   -0.17%
  Complexity       90       90
============================================
  Files           177      177
  Lines          6620     6639      +19
  Branches        783      784       +1
============================================
+ Hits           5246     5250       +4
- Misses          920      934      +14
- Partials        454      455       +1

Impacted Files
Coverage Δ

...n/scala/org/apache/kyuubi/engine/ProcBuilder.scala
81.05% <38.88%> (-9.86%)
:arrow_down:

...ain/scala/org/apache/kyuubi/engine/EngineRef.scala
79.22% <100.00%> (+0.27%)
:arrow_up:

.../org/apache/kyuubi/operation/KyuubiOperation.scala
50.00% <0.00%> (-5.36%)
:arrow_down:

...pache/kyuubi/sql/KyuubiQueryStagePreparation.scala
80.39% <0.00%> (-0.99%)
:arrow_down:

Continue to review full report at Codecov.

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

Option 1 requires the user to set up Hadoop client on the Kyuubi server node(s), and also set HADOOP_HOME, suppose that the user usually should deploy Kyuubi on the Hadoop node, it's acceptabe.
If we choose option 3, we need to test with different versions of Yarn cluster to ensure that the compatibility between Kyuubi server bundled Hadoop client jars and Yarn cluster.
Seems that option 2 has less dependencies and good compatibility.
@timothy65535 @simon824 @zhouyifan279 @yaooqinn WDYT?

Use Yarn RestFul API

we often use option-2 to get some data from hadoop...
this method i think it's better. we only need core-site.xml and some files about kerberos.
this method is independent of hadoop_version.

YARN REST API supports killing apps since 2.5.0. That should be enough to cover most YARN versions used in production.

 We will not kill application by shell script or yarn api.
REFER TO:
https://github.com/apache/spark/blob/9d8ac7c8e90c1c2a6060e8f1e8f2f21e19622567/resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala#L137-L145
cc @simon824 @pan3793 @yaooqinn

The issue seems to be caused by the improper usage of process.destory which will not invoke the shutdown hooks of the spark/engine app.
Instead of calling process.destory, it looks like we'd better notify the engine to shutdown itself

it looks like we'd better notify the engine to shutdown itself

When app in ACCEPTED status, the engine has not initialized, so it can not shutdown itself. LauncherProtocol can work.

it looks like we'd better notify the engine to shutdown itself

When app in ACCEPTED status, the engine has not initialized, so it can not shutdown itself. LauncherProtocol can work.

I don't know what you mean

hi @yaooqinn, when in ACCEPTED state, means that the spark driver hasn't been inited.

I know the final step is using yarnClient to kill the application if the cluster manager is yarn in this case. But do we have any higher-level API or actions that we can take to make this happen?  e.g. by calling SparkContext.stop
we are not a yarn-specific platform, right?

I know the final step is using yarnClient to kill the application if the cluster manager is yarn in this case. But do we have any higher-level API or actions that we can take to make this happen? e.g. by calling SparkContext.stop
we are not a yarn-specific platform, right?

Right.

The spark internal launcher already expose the interface to comminicate with resource manager client.

YARN: implemented.
Meson: implemented.
K8s: seems has not implemented.

https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/launcher/LauncherBackend.scala

The spark internal launcher already expose the interface to comminicate with resource manager client.

YARN: implemented.
Meson: implemented.
K8s: seems has not implemented.

[spark core]
https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/launcher/LauncherBackend.scala
  def connect(): Unit = {
    val port = conf.getOption(LauncherProtocol.CONF_LAUNCHER_PORT)
      .orElse(sys.env.get(LauncherProtocol.ENV_LAUNCHER_PORT))
      .map(_.toInt)
    val secret = conf.getOption(LauncherProtocol.CONF_LAUNCHER_SECRET)
      .orElse(sys.env.get(LauncherProtocol.ENV_LAUNCHER_SECRET))
    if (port.isDefined && secret.isDefined) {
      val s = new Socket(InetAddress.getLoopbackAddress(), port.get)
      connection = new BackendConnection(s)
      connection.send(new Hello(secret.get, SPARK_VERSION))
      clientThread = LauncherBackend.threadFactory.newThread(connection)
      clientThread.start()
      _isConnected = true
    }
  }

Is it common use in different hadoop versions？
Mesos and k8s also support restful api.

Is it common use in different hadoop versions？

Right.

Restful API

If use restful api, and contains some auth properties(e.g kerberos), we can not call the restful api directly.

Option 1 requires the user to set up Hadoop client on the Kyuubi server node(s), and also set HADOOP_HOME, suppose that the user usually should deploy Kyuubi on the Hadoop node, it's acceptabe.
If we choose option 3, we need to test with different versions of Yarn cluster to ensure that the compatibility between Kyuubi server bundled Hadoop client jars and Yarn cluster.
Seems that option 2 has less dependencies and good compatibility.
@timothy65535 @simon824 @zhouyifan279 @yaooqinn WDYT?

Now we have a new option:
4. Use SparkLauncher
It requires initializing SparkLauncher Object instead of building  spark-submit command ,  then  get appId and killApp by SparkAppHandle.
And it is independent of hadoop_version.
@zhang1002 @zhouyifan279 @pan3793 WDYT?

+1, use SparkLauncher may be the best way to solve this problem, it contains LauncherProtocol

+1, use SparkLauncher may be the best way to solve this problem, it contains LauncherProtocol

Have you achieved it by SparkLauncher before? I just did a test and found that if job state is RUNNING, SparkAppHandle can stop/kill application. But if SparkAppHandle.State is SUBMITTED  (yarn state is ACCEPTED) , it was failed.

if sparklaunch can not stop it, yarn rest api will also can not kill it. Need to check it why it can not kill the app.

关于及时停止超时应用:
层级一: 应用一直处于ACCEPT，但是提交程序已经超时

可以通过REST API或者SHELL方式停止，这两种方式存在兼容性或者是认证方面的问题，尤其是使用了kerberos认证，这种调用一定失败
通过上层进程与子进程交互来停止，也就是一直提到的LauncherProtocol，这个接口已经被用在Spark Core模块里面了，每个资源框架各自实现如何通过api方式来停止任务。比如yarn，它就是利用yarn clint去停止任务。不管是第一点提到的SHELL还是REST，底层肯定是yarn client来停止。所以说如果这种方式都停不了，那就是yarn本身就停不掉

层级二: 每次提交spark任务都会提前创建好zk上的space，如果层级一没有做到，在engine启动的时候可以检测一下space是否存在，不存在及时退出即可
层级三: 每个engine自己会有默认30分钟的检测时间，即没有session，engine也会自己退出
关于层级一，yarn client api是可以做到停掉处于accwpt的任务。如果spark launch没有做到，可以debug下。

Now we have differences. I think we need to fully discuss the implement of this problem before coding.

Now we have differences. I think we need to fully discuss the implement of this problem before coding.

Or we provide a develop-oriented post executed script if timeout. we pass some application details, such as user/applicaiontId to it and the script can contain something like yarn kill ... or spark-submit --kill ...

ok.
at first, we only consider app running in yarn. This is problematic because we also can run them in k8s or others...

Now we have differences. I think we need to fully discuss the implement of this problem before coding.

Or we provide a develop-oriented post executed script if timeout. we pass some application details, such as user/applicaiontId to it and the script can contain something like yarn kill ... or spark-submit --kill ...

It means that kyuubi doesn't actually execute the script, just generates it?

Maybe we considered too much, we don’t have to find a unified method to stop application in different resource managers and different compute engines, we can implement stop() in different child class and then make some conditional judgments.


Spark batch jobs are not terminating

Recently after cluster upgrade, spark jobs were not starting because of the issue:
https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/issues/591
I have changed the kubernetes-client jar from 3.0.0 to 4.4.2 in the docker image as mentioned in the comments. Now spark batch jobs are not terminating after it's execution. Both driver and executor are stuck in running state.
Sparkoperator version: 2.4.0

You probably need to look into your executor/driver logs to figure out why.

Closing this. Feel free to reopen if needed.

@suvashishtha
私も同じ問題に直面しました
何か進捗はありましたか？

@liyinan926  I am facing the same problem. Executor logs shows the job as finished. I tried to explicitly kill the application using sys.exit(0) still the driver and the executor are in running state. Any pointers ? I am using v2.4.4 of the operator.

@liyinan926 I am having this issue when running k8s operator, writing as a delta table, and using Ozone. The logs are fine nothing there to raise suspicion. The executor sent all information back to the driver. When I describe the app, the status is running but the message below has them in a pending state.

@dustinTDG / @rkautoid Can you grab thread dumps from the executors page of the Spark UI?
I'm wondering if this is related to the problem fixed [1] in 3.0 branch of Spark but not yet back ported to the 2.4 branch?
That was SPARK-24266 [2] which fixed a loss of an HTTP_GONE event from the k8s control plane.
[1] https://github.com/apache/spark/pull/28423
[2] https://issues.apache.org/jira/browse/SPARK-24266

I see this error a lot in the batch jobs:
{"level":"WARN","timestamp":"2020-08-10 19:17:35,985","thread":"OkHttp https://kubernetes.default.svc/...","source":"io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager", "line":"209","message":"Exec Failure"}
java.io.EOFException
	at okio.RealBufferedSource.require(RealBufferedSource.java:61)
	at okio.RealBufferedSource.readByte(RealBufferedSource.java:74)
	at okhttp3.internal.ws.WebSocketReader.readHeader(WebSocketReader.java:117)
	at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:101)
	at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:274)
	at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:214)
	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:206)
	at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
^C

I do think its related to the above issue. The batch job starts, Driver is able to spin up new executors, communicate with them and get the job done, but cannot clean them up.

It looks a bit different from what I see.  For me, it appears to get stuck at the very end of writing data to Bigtable in the very last task of a job.  Our partner is working to back port the fix I mentioned and I will let you know if that addresses the hang.


Mutual TLS for internode communication

Can we have secure setup between containerised pods of vespa cluster?
http pods connection works, but will https work?

Yes, see https://docs.vespa.ai/en/securing-your-vespa-installation.html#securing-the-application-container

Can't find jdisc_container folder in /path/to/vespa/home/conf/ even after adding -
<server id="server1" port="8080">
  <config name="jdisc.http.connector">
    <idleTimeout>90</idleTimeout>
  </config>
</server>

Will it work if I just add the certificates and the private key that I've generated?

Yes, you can just create the path and add certs there.

Hi,
Wanted to check if mTLS is working between config(server-2) and container(server-1) after configuring TLS as follows. Tried to ping container through config, but it didn't work. How do I test it out? Is the below configuration correct?  Also will this configuration work for content nodes communication as well, from the looks of it, it seems as if it will work only for container given it's under container element.
Testing:
bash-4.2$ kubectl exec vespa-0 -- bash -c 'curl -iv https://vespa-container:8080'
* About to connect() to vespa-container port 8080 (#0)
*   Trying <IP_ADDRESS>...
* Connection refused
* Failed connect to vespa-container:8080; Connection refused
* Closing connection 0
curl: (7) Failed connect to vespa-container:8080; Connection refused

TLS configuration:
<container id="default" version="1.0">
        <http>
            <server id="server-1" port="8080">
                <ssl>
                    <private-key-file>/opt/vespa/conf/jdisc_container/vespa-certs.key</private-key-file>
                    <certificate-file>/opt/vespa/conf/jdisc_container/vespa-certs.cer</certificate-file>
                    <ca-certificates-file>/opt/vespa/conf/jdisc_container/vespa-certs.p12</ca-certificates-file>
                    <client-authentication>want</client-authentication>
                    <cipher-suites>
                    TLS_AES_128_GCM_SHA256,
                    TLS_AES_256_GCM_SHA384,
                    TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
                    TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
                    </cipher-suites>
                    <protocols>TLSv1.2,TLSv1.3</protocols>
                </ssl>
            </server>
            <server id="server-2" port="19071">
                <ssl>
                    <private-key-file>/opt/vespa/conf/jdisc_container/vespa-certs.key</private-key-file>
                    <certificate-file>/opt/vespa/conf/jdisc_container/vespa-certs.cer</certificate-file>
                    <ca-certificates-file>/opt/vespa/conf/jdisc_container/vespa-certs.p12</ca-certificates-file>
                    <client-authentication>want</client-authentication>
                    <cipher-suites>
                    TLS_AES_128_GCM_SHA256,
                    TLS_AES_256_GCM_SHA384,
                    TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
                    TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
                    </cipher-suites>
                    <protocols>TLSv1.2,TLSv1.3</protocols>
                </ssl>
            </server>
        </http>
        <document-api/>
        <search/>
        <nodes>
            <node hostalias="node-1" />
        </nodes>
    </container>

Above I answered how to configure mTLS for traffic to/from a Vespa instance.
mTLS for internal traffic between nodes is also possible, but more complicated, as there are multiple processes and protocols. We haven't yet gotten around to document this but i will happen in the not too far future.
I should also mention that this is provided for you by default when you deploy to the Vespa Cloud.

Open source Vespa now officially supports mTLS across all internal services and endpoints. As mentioned, if you use Vespa Cloud this is—and always has been—enabled without any setup required.
See our mTLS blogpost for an introduction and our mTLS reference documentation for setup instructions.
Please let us know if you have any follow-up questions!


Remove version: RoyQu.RedPanda-C++ version 2.25

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/redpanda-cpp/files/2.25/RedPanda.C++.2.25.1.win32.MinGW-w64 i686 GCC 8.1.Setup.exe/download
OK
(Automated message - build 923)

Close with reason: Duplicate;


Focusing on facets

[x] When a facet is focused (on page load, clicking a chiclet, returning from find more with selected values), it should have it's border highlighted.
[ ] focusing on top opened facet on page load is buggy and shifts to the middle of the facet panel

I can't reproduce this issue in Chrome, Mozilla FF, or Safari.


Battery is force charged after being below minimum

System was reaching its lower bound (notstrom dose) with 7% and stopped using the battery.
I started batcontrol ( 0.2.10 preview with the different charge calculation) afterwards and batcontrol wants to recharge.  But it makes no sense, because price target (0.18 Cent) is not met.
2024-11-13 18:35:28 DEBUG [FC Cons] predicting consumption: [433.9 335.7 339.4 305.6 258.  288.5 244.5 212.2 236.1 236.1 369.6 329.9
 326.1 318.2 327.8 345.1 349.3 337.4 449.9 431.4 430.  366.5 385.9]
2024-11-13 18:35:28 DEBUG [BatCTRL] Production FCST: [  0.   0.   0.   0.   0.   0.   0.   0.   0.   0.   0.   0.   0.  22.
  Available in Battery: -7.7 Wh
2024-11-13 18:35:29 DEBUG [BatCTRL] Discharging is NOT allowed
2024-11-13 18:35:29 DEBUG [BatCTRL] Charging allowed: True
2024-11-13 18:35:29 DEBUG [BatCTRL] Additional Energy required: 7.7 Wh
2024-11-13 18:35:29 DEBUG [BatCTRL] Mode: grid charging. Charge rate : 18 W

beside of that, it seems the Fronius does not charge from the grid 👎 : , might be another issue

Yeah, this is the reason why we see some flattering on some users.
We should add a margin on min_battery level, that we are not fighting against fronius min value.

Merged into Release-0.2.11 branch for testing

I'm on the %buffer side above the MIN_SOC delivered by Fronius. It also keeps the system more away from a "forced recharge" by the internal inverter logic.
But to implement this, we should a config parameter MIN_SOC-Margin or something. If we hide that in the code, more questions will rise.

Hey,
I am not sure if staying at MIN_SOC is something we should do.
My case yesterday: the produced energy did not lift the battery by 1%. So the battery hovered around 6% (7% is backup up). During the evening, it dropped down to 5% due to self discharge. In the night the battery was forced charged to 7% again by Fronius.

Sure, it is a new minimum, which is true.
My main goal is to avoid the internal forced recharge during high prices.
Currently, im losing 2-3% while staying at batcontrol Minimum...
I can create an external logic which schedules a forced recharge, or increase the backup power threshold to have a higher margin.

Makes sense! So basically we want to shift the forced recharge from a random time to a controlled time at the cost of having a little less capacity available.

So, we will add a % margin above the MIN_SOC reported by Fronius.
I had another "incident" today, while the battery was hovering around our minimum, was released and dropped below MIN_SOC - was recharged by the inverter immediately.

I think this comment was for #68


Quest change

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


fix: allow reusability of Server Variable Objects

Refs #775

Answering your comment in the #775 issue:

I've issued a https://github.com/asyncapi/spec/pull/776 that remedies the situation and would probably suggest to go for 2.4.1 as soon as possible.

Yeah, I think it's a pretty good use case for a patch version.

/dnm

Do we really have to do 2.4.1? In my opinion, it's more of an oversight and that doesn't change the structure of the specification at all. When OpenAPI 3.1.0 came out, people were still making small improvements to the spec without releasing 3.1.1.

Do we really have to do 2.4.1? In my opinion

No, it's not really necessary, I've just suggested it given the quick cadence of release process for the spec.

it's more of an oversight and that doesn't change the structure of the specification at all.

IMHO it does change the capabilities of the specification; strictly speaking it extends the capabilities, so feat would be more appropriate, but given the context and the fact that this is oversight I went with fix.

When OpenAPI 3.1.0 came out, people were still making small improvements to the spec without releasing 3.1.1.

Not sure this is correct observation (but I might be mistaken). OAS is considered immutable and the last commit to the 3.1.0 version is actually the release commit. No commits after that.
Commit history for the 3.1.0 spec: https://github.com/OAI/OpenAPI-Specification/commits/main/versions/3.1.0.md

For me it looks also good. Thanks @char0n for extending the idea of reusability.

@dalelane @fmvilas your review is needed here. Thanks!

Given we've discontinued effort with 2.4.1 release and are going directly for 2.5.0, this PR needs to be send against next-spec and the title needs to changeto feat: allow re-usability of Server Variable Objects

@char0n yup, I think you should be able to change the base branch

Right, I'll do it right after https://github.com/asyncapi/spec/pull/831 is merged.

Base branch changed for next-spec.

/ready-to-merge

Changed title from fix: allow re-usability of Server Variable Objects to feat: allow re-usability of Server Variable Objects. Can I ask somebody to to remove do-not-merge label or merge this PR? Thanks!

/rtm


Added type="button" to 'set privacy button'

Added type="button" to 'set privacy button'  to fix the opening of page privacy menu on hitting enter in a char block in edit stream-page page.
Closes #6592

Merged in 400bc57536729edec8a6b71468c60ddd19282e74


Fix NGen command in appveyor build script

Fixes #207

LGTM

I'll merge this one since it is a reviewed infrastructure improvement


refs

refs
https://www.cnblogs.com/xgqfrms/p/16636559.html
Software Engineering at Google
https://abseil.io/resources/swe-book
https://github.com/abseil/abseil.github.io/tree/master/resources/swe-book/html

https://item.jd.com/13119039.html

https://kaopubear.top/blog/2022-07-16-book-software-engineering-at-google/


List Module parameter interpreted as napari layer

Trying to run the op morphology.dilate(img "out"?, img "in1", list "in2", boolean "isFull"?) -> (img "out"?) yields a widget that provides a layer selector for in2.

Unfortunately, this will probably be a tricky issue to fix, because we are dealing with java generics, and we already have a complicated widget for dealing with Shapes.

I suggest to encapsulate all the various places you call ModuleItem.getType() throughout the codebase into a single utility function that computes the Pythonic type hint from the ModuleItem. Then, you can refactor to call getGenericType() instead of (or in addition to) getType(), and have some case logic around "easy" cases like ParameterizedType of collections.

I suggest to encapsulate all the various places you call ModuleItem.getType() throughout the codebase into a single utility function that computes the Pythonic type hint from the ModuleItem.

Yup, the function is type_hint_for

I looked a little more into why this is failing. Here's what's happening:

The OpListing reduces ListDilate's parameters down to their raw types, via the default type reducer. Therefore, the List<Shape> parameter becomes a List parameter
napari-imagej, in the attempt to find a suitable type hint, finds that ImageDisplays can be converted to a List, and recommends the corresponding python type, a napari Image layer, as the input type.

As a result, I think that the OpSearcher needs to have a bit more intelligence in creating the OpListings, especially w.r.t. type parameters. Iirc this change was made to avoid the distinction between, for example, Img<IntegerType> and Img<RealType> showing up as two separate signatures, and I still think that's nice.
We could also make some changes in napari-imagej to solve this, but I'm guessing Fiji will see similar issues, so maybe we should just fix it in Ops?


[Question] Should updated MTU apply on existed VM network?

During verifying #4353, we found that existed VM network will not affect by MTU update.
Should convert to BUG if this is NOT expected behavior
Environment

Harvester

Version: v1.2.0-rc5
Profile: QEMU/KVM, single node (8C/16G/250G)
ui-source: Auto

Test Cases

Note Click "►" to expand details.

Create cluster network nonmgmt with MTU 6666

Create VM network vlan1-before

Update cluster network's MTU to 7777

Create VM network untagged-after

Create a VM with these 2 VM networks

One network w/ MTU 6666, the other w/ 7777

vlan1-before

untagged-after

cc. @yaocw2020

Yes, it's the expected result. I have filed an enhancement issue https://github.com/harvester/harvester/issues/4355, and we'll  completely solve the MTU problem.

@yaocw2020, thanks for the comment.
Close ticket as by design.


Last character in note of txn cut off

When signing a payment txn with a note attached the last character is being cut off. The string is shown correctly in the signing window.
This happens when using new Uint8Array(Buffer.from(NOTE, "base64")). It seems to work without the second argument.

Hello @gidonkatten . Can you provide me an example transaction? . Does the last character is =?


Remove duplicate .jars from the accountrecoveryendpoint

Describe the issue:
In IS-5.10.0, repository/deployment/server/webapps/accountrecoveryendpoint/WEB-INF/lib/ has following .jar files which are also available in repository/components/plugins also.
How to reproduce:
Open repository/deployment/server/webapps/accountrecoveryendpoint/WEB-INF/lib/, you can observe 5.16.73 version of following jars.

org.wso2.carbon.identity.mgt.endpoint.util-5.x.x.jar
org.wso2.carbon.idp.mgt.stub-5.x.x.jar

Open repository/deployment/server/webapps/accountrecoveryendpoint/WEB-INF/lib/, you can observe 5.17.5 version of following jars.

org.wso2.carbon.identity.mgt.endpoint.util-5.x.x.jar
org.wso2.carbon.idp.mgt.stub-5.x.x.jar

Expected behavior:
These .jar files do not need to be available in the reapplication. Dependencies can be resolved from the plugins folder.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Canisters

About the PR
Added 5 gas tanks (Hydrogen, Ammonia, Methane, Polyt. Acid, Oxygen), MiniTank and Pressurized Reagent Canister.
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Test fail is real for once
  Failed FillLevelSpritesExist [83 ms]
  Error Message:
     CMPressurizedCanister has SolutionContainerVisualsComponent with
                            MaxFillLevels = 6, but /Textures/_CM14/Objects/Tanks/pressurized_reagent_container.rsi doesn't have state beaker1!

Test fail is real for once

i have literally zero idea how to fix that...


Make projects display uniformly

Dimensions are uniform in desktop viewport but height is still slightly off in mobile view. Closing this issue and making an updated one.


Fix VA: Find out the meaning of address fields

Ask VA ppl the difference between:
-"Location/City" and "Location State" fields
(seems to be associated with the business, and all but like one entry are in Virginia. Why do they have a Washington, DC entry??)
-"Company Address 1", "Company Address 2", and "City/Town".
(seems to be associated with the HQ of the business, and many of these list different states. probably not useful for our purposes but it would be good to ask clarification about what these exist for.)
See the data interview document in the BLN-onboarding repo about reaching out to an agency for information.

DC borders VA. The company addresses are HQs. The Locations are the sites where the jobs are lost.


New version: BrainFlow v5.0.0

Registering package: BrainFlow
Repository: https://github.com/brainflow-dev/brainflow
Created by: @Andrey1994
Version: v5.0.0
Commit: 1f89540a6663bc68dc8da0a2ef8d8e313afd1622
Reviewed by: @Andrey1994
Reference: https://github.com/brainflow-dev/brainflow/commit/1f89540a6663bc68dc8da0a2ef8d8e313afd1622#commitcomment-75760533
Description: BrainFlow is a library intended to obtain, parse and analyze EEG, EMG, ECG and other kinds of data from biosensors

I will not fix the automerge issue, and dont understand how I am supposed to fix this "This PR is allowed to modify at most 3 files, but it actually modified 4 files."

I will not fix the automerge issue,

Nice attitude, thanks.

and dont understand how I am supposed to fix this "This PR is allowed to modify at most 3 files, but it actually modified 4 files."

It looks like you changed the directory where the package is?
[noblock]

Yes, you are right

The fact is that it wasn't anticipated the possibility of renaming the directory, which caused editing the Project.toml file in this pull request, which is what upset the bot.
I asked Pkg developers, they said it should be OK to merge this pull request. The directory was renamed already in the repository, so at least new versions should work fine.  I can confirm I was able to install v4.9.2, which is a good sign, I guess.


glossary: no tooltip when there's break lines in  tags

For example the lines
- `etag`: strong ETag response header (only HTTP external
  dependencies created with `dvc import-url`)

won't produce a glossary tooltip. But they should.
If we require  terms to be in a single line, then maybe the automatic linter (pretty-quick) that runs on a Git pre-commit hook should enforce that format, like it enforces quoted text to be in a single line?

What do you think @algomaster99? Thanks

@jorgeorpinel prettier and Rewraps plugin both take care of it. They put ... in one line.

Not when there's a space in the term e.g. data artifact.

@jorgeorpinel
One solution I have thought for this is to add 'external\ndependencies' to the match array. Notice that I added a new-line character between the words.

@algomaster99 I think we can "normalize" the term before trying to match it in JS itself. Remove extra spaces, convert \n to space, tabs to spaces, etc.

@shcheklein I don't get what you mean by normalize? Can you explain?

@algomaster99:
} else if (props.tag === 'abbr') {
    const text = props.children[0]
    return <Tooltip text={text} />
  }

you can do something like:
const text = normalize_space(props.children[0])

It's either that or making prettier force those tags into a single line, if that's possible. But I'm guessing that's not possible to do with prettier, so I second normalizing 🙂

@algomaster99 I thought of another improvement.

[ ] The match terms should be case insensitive so that for example, both Workspace and workspace match workspace (without having to also specify Worspace in the match array.

What do you guys think?

It would also be nice to have a Glossary menu item on the nav bar that opens a page in the docs where all these terms are listed (with  anchors. This is mainly to link from glossary descriptions (because we can't have tooltips inside tooltips) but may be useful in other cases perhaps? And to read the full list in case anyone is curious. What do you think?

@jorgeorpinel I think it deserves it's own issue. Not a top priority, but let's create an issue for sure.


Various fixes

Various fixes

moved the GIF video tutorial into Github images hosting, to make the repository less heavy
fixed coords typo in readme
reorganized code
fixed rendering of vanilla armors if the custom armors have a different texture resolution
fixed emissivity texture not rendered at all when the animation has a specific amount of frames / with some particular atlas size

This needs testing.
I tested it with vanilla armor, leather armors, custom armors and didn't find any side effect of my changes, but surely you know the project better than me and you can check if this fix is correct or would introduce any problem.
I contacted you on Discord providing multiple example resourcepacks to show the emissivity map bug in action.
I think it's stable enough to be merged! :D

Bless open-source. Thank you so very much for this

I've tested this and from what I can see it's stable! Thank you for giving this project attention! When I started fancy pants I didn't expect it to get this much attention and I am glad others are also contributing.


🚧Fix security issue with exception serialization

Complete The Item Below

[X] I have updated the title without removing the 🚧 emoji.

Description
Fix a security issue with deserialization of the BufferNotInitializedException.  More info on this can be found with the sonar cloud scan in the link below.
Sonar Scan Security Hotspot
Acceptance Criteria

[ ] Security issue fixed with BufferNotInitializedException class.

ToDo Items

[X] Change type labels added to this issue.  Refer to the Change Type Labels section below.
[X] Priority label added to this issue.  Refer to the Priority Type Labels section below.
[X] Issue linked to the correct project (if applicable).
[X] Issue linked to the correct milestone (if applicable).
[x] Draft pull request created and linked to this issue (only required with code changes).

Issue Dependencies
No response
Related Work
No response
Additional Information:
Change Type Labels

Change Type
Label

Bug Fixes
🐛bug

Breaking Changes
🧨breaking changes

New Feature
✨new feature

CICD Changes
♻cicd

Code Doc Changes
🗒documentation/code

Product Doc Changes
📝documentation/product

Priority Type Labels

Priority Type
Label

Low Priority
low priority

Medium Priority
medium priority

High Priority
high priority

Code of Conduct

[X] I agree to follow this project's Code of Conduct.

Issue Closed without changes.
Reason: After further investigation, it was decided that this is not a security risk.  This is due to the fact that the exception does not contain any additional properties outside of the usual Exception properties.  Due to this, no security risk is imposed on the consumer side due to properties available to build custom logic around to give the attacker an advantage.


feat: refetch user LP data on wallet switch

Description

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

High Risk PRs Require 2 approvals

What protocols, transaction types or contract interactions might be affected by this PR?

Testing

Engineering

Operations

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #6158   👈

This stack of pull requests is managed by Graphite.


Creating a Tic-Tac-Toe Game in Python

Description:
Creating a Tic-Tac-Toe game in Python using Object-Oriented Programming (OOP) concepts is an excellent way to demonstrate the principles of OOP and develop a fun and interactive game. This classic game involves two players taking turns to mark X and O on a 3x3 grid, with the objective of getting three of their marks in a row, column, or diagonal. Here, we'll outline the key features and technologies used to develop a Tic-Tac-Toe game in Python with an OOP approach.
Features:

Game Board: The game board is represented as a 3x3 grid, which is essential for displaying the current state of the game. This grid can be implemented as a 2D list or a custom class to track the positions of X and O.

Players: The game should support two players, typically referred to as Player X and Player O. In OOP, each player can be represented as a separate object with attributes like their name and symbol (X or O).

Game Logic: Implement the game logic to manage the flow of the game, including taking turns, checking for a win or a draw, and updating the game board.

User Input: Allow players to input their moves through the command line or a graphical interface. This input can be validated to ensure it's a valid move.

Win Condition: Detect when a player has won by checking for three of their symbols in a row, column, or diagonal. This requires a method to check for a winning condition after each move.

Draw Condition: Check for a draw when the board is full and there is no winner. This helps in determining the end of the game.

User Interface: Implement a user-friendly interface for displaying the game board and guiding players through the game. This can be done using simple text-based UI or a graphical interface library such as Tkinter.

Replay Option: Allow players to start a new game after one has concluded.

Technologies and Concepts:

Python: Python is the programming language used to create the game. It offers a clean and readable syntax, making it a popular choice for beginner and advanced developers alike.

Object-Oriented Programming (OOP): Utilize OOP principles such as classes and objects to represent the game board, players, and game logic. This approach promotes code organization and encapsulation.

Data Structures: Use data structures like lists or dictionaries to represent the game board and track game state. Object-oriented programming can help encapsulate these data structures within classes.

User Input and Output: Incorporate input and output mechanisms to handle player moves and display the game's current state. The input() function can be used to gather player input, and print() for displaying the game board.

Conditional Statements: Utilize conditional statements to check for winning and draw conditions, making decisions based on the state of the game.

Loops: Implement loops to manage the flow of the game, allowing players to take turns and replay the game.

Error Handling: Include error handling to handle invalid user input, ensuring a smooth gameplay experience.

Graphical Libraries (Optional): If you choose to develop a graphical user interface, you can utilize libraries like Tkinter or Pygame to create a more visually appealing version of the game.

By combining these features and technologies with sound OOP principles, you can create an engaging and well-structured Tic-Tac-Toe game in Python that not only entertains but also serves as a learning tool for OOP concepts.

I will like to contribute , can you please assign it to me!!


fix HoodieLogFileReader

fs.open(logFile.getPath(), bufferSize).getWrappedStream()  may not be a FSInputStream.
When use s3 in aws emr, it's  a BufferedFSInputStream

@bvaradar I think we can squash . and merge?  (I started doing that) . anyways, CI seems have errors.? Something related to HBase that I have not seen before.. have restarted the job.


Expand DFDSServiceAPI to make use of OAuth on its controllers

[ ] Protect the controllers by adding [authorise] to each and every controller
[ ] Configure Msal in startup.cs

See Capability-Service, https://github.com/dfds/cost-janitor-2 for inspiration on how to do this

No.


navigation in useRadioGroup using keyboard arrows break if there is another focusable element withing the group

🐛 Bug Report
Hi,
I had to create this pattern in one project: https://design-system.service.gov.uk/components/radios/conditional-reveal/index.html. But when I tried to navigate between the radios using arrow keys the focus was last and value of the radio group was set to null. This is because the getFocusableTreeWalker select any focusable element, even in this case it should really select only radio buttons.
🤔 Expected Behavior
After pressing arrow key, if the radio button is focused, I would expect the next radio to be selected and focused, even if there is some other focusable element. in between those two radio buttons.
😯 Current Behavior
Focus is removed from the radio group, because it is trying to focus non-radio element which is removed from the dom.
💁 Possible Solution
I have add another option to the getFocusableTreeWalker using patch-package. Which is a callback used to modify default selectors. Whatever is returned from this callback will be used as a new selector for tree walker.
export function getFocusableTreeWalker(root, opts, scope) {
  let selector = opts?.tabbable ? TABBABLE_ELEMENT_SELECTOR : FOCUSABLE_ELEMENT_SELECTOR;
  if (opts.selectorModifier) {
    selector = opts.selectorModifier(selector)
  }
  let walker = document.createTreeWalker(root, NodeFilter.SHOW_ELEMENT, {
    acceptNode(node) {
      ...

// Then in the useRadioGroup function in the onKeyDown method

let walker = getFocusableTreeWalker(e.currentTarget, {
      from: e.target,
      selectorModifier: function( selector ) {
        return "input[type=radio]:not([disabled]):not([type=hidden]):not([hidden])"
      }
    });

🔦 Context
This is one of the issues I have faced when trying to create conditional reveal from the example above. I had to use patch-package to make this work as intended. But I would like to be this fixed in the library.
💻 Code Sample
https://codesandbox.io/s/silly-violet-ow97m?file=/src/App.js:674-693
🌍 Your Environment

Software
Version(s)

react-spectrum
3.4.1

Browser
Chrome 93

Operating System
macOS

Hmm that's interesting. The pattern makes sense, but I'm pretty sure the radiogroup role can only have radio children according to the ARIA spec (see "Required owned elements"). It is possible to have radios outside a radio group though. I will need to check with our accessibility experts and do some research and get back to you.


combining de aerial imagery into one file, within editing section

German section only - wait until all done before merging.
This combines 2 files into one.

Ready to merge now - waiting until after comments & approval / rejection of /hotosm/learnosm/issues/413


Enable MINC ITK Support

This PR enables MINC IO support in the Superbuild

Thank you for initiating this pull request.
The default configuration of SimpleITK, including which modules are enabled, generally follows that from ITK. There are a variety of reasons and constraints for this. However, I believe that the MINIC module has matured nicely in ITK. I ran valgrind on the modules [1], and it appears to be free from memory defects now.  Can you begin the discussion in the ITK community to enable these modules by default?
Any ITK modules can easily be enable in the SimpleITK superbuild simply by adding a CMake variable on the command like. i.e. cmake -DModule_ITKIOMINC:BOOL=ON . would enable that ImageIO module for a customized version of SimpleITK.
[1] https://open.cdash.org/viewDynamicAnalysis.php?buildid=4914374

Hi @blowekamp, where do I go to begin such a discussion?

The ITK mailing list:
https://itk.org/ITK/help/mailing.html
Or you can just submit a patch with itks Gerrrit.


iPhone HTML5 export never loading

I have looked for similar issues, but the question wasnt' the same, doesn't seem to be answered, or the issues were either closed or changed to discussion.
Godot version:
I am using the 3.1 stable version released today.
OS/device including version:
desktop mac, android mobile device, and iphone
Issue description:
When exporting my game with the HTML5 template using GLES2, I can view and play my game on all the desktop browsers I have as well as on my Android phone default browser. However, it never completes loading on my iphone or ipad.
HelloWorld3.1.zip

iPhone and iPad models and iOS versions?
Also try the demo on https://webassembly.org/

iPhone X - ios 12.1.4
iPad 3rd generation - ios 10.3.3
iPad - the webassembly.org demo shows up on the ipad in Safari.
iPhone - the webassembly.org demo never loads in Safari or in Chrome.

there is a custom version of the engine that takes acare of ios safari support for html5. It works without major hiccups. https://github.com/dotdigitalgroup/godot/tree/asmjs-support
This issue is the same as https://github.com/godotengine/godot/issues/26554

Great. Can't wait to check it out. But, what is it exactly that is at that link? I don't see a way to start the engine. Is it a build for export?

I don't understand your comment, I linked the repository for the custom build of Godot. Download the source code and follow the guide in the docs for compiling the engine and export templates from source. All the best.

@awindahl is this making its way into official Godot?

This is just a custom version, I have no idea what the plans are.

Ok Thanks a lot.

Manually merged into my code, confirming it works great with mp3 sounds.
However, for some reason the html template on export is empty

Duplicate of #26554.


Clarify that the Command function works in Microsoft Access.

The Command function works in Microsoft Access, but not in other Microsoft Office applications (such as Word and Excel).

Docs Build status updates of commit 99c8305:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Language/Reference/User-Interface-Help/command-function.md
:white_check_mark:Succeeded
View

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


Refunds

I want to merge this change because... it creates new refunds:

Miscellaneous Refunds
Product Refunds

It replaces the previous dialog, where it was possible to apply a refund with a single amount.
https://app.clickup.com/2549495/v/l/6-21582465-1

PR intended to be tested with API branch:  SALEOR-1723/4-refund-order-lines
https://github.com/mirumee/saleor/pull/6530
Screenshots

Pull Request Checklist

[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Translated strings are extracted.
[ ] Number of API calls is optimized.
[ ] The changes are tested.
[ ] Data-test are added for new elements.
[ ] Type definitions are up to date.
[ ] Changes are mentioned in the changelog.

Test environment config

API_URI=https://master.staging.saleor.rocks/graphql/

Task linked: SALEOR-1723 resolver for available lines to refund


store/java: whitelisting is slow

Typically the whitelist calls in java take 50-70s from their installed state. I'm not sure if keytool offers anything we could do better.
Perhaps build a new trustStore (rather than modify) if the whitelist only allowes at most half of certs through?

I think #163 is a better factor which has been improved a bit. I'm not super worried about this now.


Errors with Get/Set-PSRepository on Windows Subsystem for Linux (WSL)

Expected Behavior
Getting / setting PowerShell repositories should behave the same in WSL as they do in Windows.
Current Behavior
We're getting odd errors getting and setting PowerShell repositories here https://github.com/psake/psake/issues/237 where we are setting the PSGallery repository installation policy to Trusted if needed. This works fine on Windows but in WSL (Ubuntu) it is throwing errors.
In WSL, run Get-PSRepository with no parameters. Works as expected.
PS /> Get-PSRepository
Name                      InstallationPolicy   SourceLocation
----                      ------------------   --------------
PSGallery                 Untrusted            https://www.powershellgallery.com/api/v2/

Run Get-PSRepostory -Name PSGallery throws an error.
PS /> Get-PSRepository -Name PSGallery                                                                                Exception calling "GetIsNetworkAvailable" with "0" argument(s): "An error was encountered while querying information from the operating system."
At /opt/microsoft/powershell/6.0.0-rc/Modules/PowerShellGet/<IP_ADDRESS>/PSModule.psm1:6264 char:9
+         $connected = [System.Net.NetworkInformation.NetworkInterface] ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : NetworkInformationException

Running Set-PSRepository throws an error but still appears to set the repository to trusted.
PS /> Set-PSRepository -Name PSGallery -InstallationPolicy Trusted                                                                                Exception calling "GetIsNetworkAvailable" with "0" argument(s): "An error was encountered while querying information from the operating system."
At /opt/microsoft/powershell/6.0.0-rc/Modules/PowerShellGet/<IP_ADDRESS>/PSModule.psm1:6264 char:9
+         $connected = [System.Net.NetworkInformation.NetworkInterface] ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : NetworkInformationException

PS /> Get-PSRepository

Name                      InstallationPolicy   SourceLocation
----                      ------------------   --------------
PSGallery                 Trusted              https://www.powershellgallery.com/api/v2/

Possible Solution
Steps to Reproduce (for bugs)

Setup WSL and install PowerShell 6.0.0-rc.
Run Get-PSRepository with no parameters. Works as expected
Run Get-PSRepository -Name PSGallery. Observe errors
Run Set-PSRepository -Name PSGallery -InstallationPolicy Trusted. Observe errors

Context
As part of developing and testing the psake project, it would be great if this process worked in WSL as well.
Your Environment
> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.0.0-rc
PSEdition                      Core
GitCommitId                    v6.0.0-rc
OS                             Linux 4.4.0-43-Microsoft #1-Microsoft Wed Dec 31 14:42:53 PST 2014
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

> Get-Module -ListAvailable PowerShellGet,PackageManagement
ModuleType Version Name
---------- ------- ----
    Script <IP_ADDRESS> PackageManagement
    Script <IP_ADDRESS> PowerShellGet

> Get-PackageProvider
Name          Version
----          -------
NuGet         <IP_ADDRESS>
PowerShellGet <IP_ADDRESS>

> Get-PackageProvider -ListAvailable
Name          Version
----          -------
NuGet         <IP_ADDRESS>
PowerShellGet <IP_ADDRESS>

@devblackops  - whilst I understand what the issue that you've raised is, I am struggling to understand (through looking at the code) why this error comes up, let alone exactly why there is a requirement to check for network access at all (a PSRepository can be a Local folder afterall)
However I now understand the flow and required fix here.
Thanks for reporting!

This issue is fixed by the changes made to simplify the connectivity checks powershellget does.


BUG: white/black_tophat behavior fixes

closes #9553
When the name of input parameter and output parameter is same in ndimage.white_tophat()/ndimage.black_tophat(), they gives zero.
I have designed the solution by comparing input and output.

This fix is wrong in several ways. array_equal compares values, while what you care about here is whether input and output are the same object. Then, you can't just ignore output by setting it to None. Finally, the tests are wrong - the output isn't changed by the application of the filter.

@rgommers
I was mistake for a moment. I am so imprudent.
I will re-work this feature.

array_equal compares values, while what you care about here is whether input and output are the same object.

Yes, it is right. This feature is target to resolve the case of a=ndi.balck_tophat(a, size=3, output=3).
That case is all of variables(output, return value, input) are same. In this situation, results is always zero.
Because of below part
    tmp = grey_erosion(tmp, size, footprint, structure, output, mode,
                                   cval, origin)
...
...
    if input.dtype == numpy.bool_ and tmp.dtype == numpy.bool_:
        numpy.bitwise_xor(tmp, input, out=tmp)
    else:
        numpy.subtract(tmp, input, out=tmp)

    return tmp

After grey_erosion calculation, tmp value is alway same for intput. so result is zero value.
but in this case, when I remove output variable from grey_erosion, tmp is not input.
so result is normally processed.
My mistake was final value(output=tmp) is ignored.

Thanks, but this seems to be the wrong approach. I left a comment in https://github.com/scipy/scipy/issues/9553#issuecomment-519231669 on how the issue should be fixed.


Barebone .xcodeproj having an error on vim startup

I'm getting started in iOS development (was following this).
I've created the project in Xcode and went into neovim as now .xcodeproj should be supported.
Project structure is as follows:
Landmarks/
├─ Landmarks/
│  ├─ Assets.xcassets/
│  ├─ ContentView.swift
│  ├─ LandmarksApp.swift
│  ├─ Preview Content/
├─ Landmarks.xcodeproj/
│  ├─ project.pbxproj
│  ├─ project.xcworkspace/
│  ├─ xcuserdata/
├─ LandmarksTests/
│  ├─ LandmarksTests.swift
├─ LandmarksUITests/
│  ├─ LandmarksUITests.swift
│  ├─ LandmarksUITestsLaunchTests.swift

But when I go into neovim this appears on top:

Project builds fine on Xcode.
I tried debugging and trying with xcodegen but since I don't really know how an iOS project works I'm a bit lost.

hey @rubenmate, this an issue resulting from the pbxproj file, could you attach the xcodeproj/project.pbxproj file here.


Support for JS SDK v3.0.0 -> Adding to develop branch

Now supporting JS SDK v3.0.0:
Currently in develop  branch

There is a jssdk dependency conflict since ringcentral-helpers#0.1.0 requires jssdk 2.0.0 per the following:
Unable to find a suitable version for ringcentral, please choose one by typing one of the numbers below:
    1) ringcentral#develop which resolved to 065cefcc1c and is required by ringcentral-cti-demo-js
    2) ringcentral#^2.0.0 which resolved to 2.0.6 and is required by ringcentral-helpers#0.1.0


feat(ci): add test action, codecov

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Refactor and add llama.cpp support

This needs a bit more work before it would be ready to merge but would you be interested in something like this?
This pull:

Refactors the story generation functions into a class with methods. I made wrapper functions to preserve the existing API.
Allows performing generation with llama.cpp's server example as a backend.
Provides a way to pass in extra parameters to the backend and also makes the max tokens configurable (for example, llama.cpp's rope scaling stuff basically lets you double or triple context for free so doing generations with 8192 or so as a limit is practical).
When using HF as a backend, uses GOAT's own HF repo for the tokenizer so authentication is not necessary.
Other misc fixes/cleanups.

Example of use with llama.cpp:
from goat_storytelling_agent import storytelling_agent as goat

def main():
    agent = goat.StoryAgent('In a world where humans never existed, animals struggle survive. These animals walk on all fours but their lifespan and intelligence is about the same as humans and they can speak. The main character is a very unusual fox.',
        form='short story', backend="llama.cpp",
        extra_options=dict(top_k=0, top_p=1.0, min_p=0.2, stop=["### USER", "### ASSISTANT"]))
    novel_scenes = agent.generate_story()
    print()
    print(novel_scenes)

if __name__ == "__main__":
    main()

Thanks for your PR, I have made some changes and merged everything. I have kept most of the things, removed some redundant functions in the end of storytelling_agent.py. I am keeping the prompts.py mostly without the "assistant" message in the end, but added prompt_engine as an argument to StoryAgent so that users can inherit create their own prompt versions and then supply them to the agent.

Glad you found the pull useful! I actually was planning to clean it up some more, I was actually just checking to see if you were interested before I went ahead and did that. :) I don't mind that you merged it of course, just wanted to say usually my pulls are cleaner than that when I'm proposing to have them merged!

I am keeping the prompts.py mostly without the "assistant" message in the end,

My reason for doing that was there are some cases where you want the model to generate exactly a certain format or item. For example, if you want it to stick to the format
Chapter 1:
Scene 1:

And you know you want it to write Chapter 1, Scene 1 then you can eliminate the possibility of it going off course and writing some other chapter, using a different format, etc. This also makes inference a little faster because prompt ingestion is a lot faster than generating tokens.
Anyway, up to you whether you find that approach useful. I just thought I'd explain my reasoning.

@Green-Sky

For me this does not work,

Actually this pull does work. :) You can verify that it's {backend}tokenize in the changed files.
I think something got broken in the subsequent changes after it was merged.

@KerfuffleV2 oh, right. on master then :)

Hey @KerfuffleV2

just wanted to say usually my pulls are cleaner than that when I'm proposing to have them merged!
The cleanliness of code is on point for all practical purposes, no worries.
My reason for doing that was there are some cases where you want the model to generate exactly a certain format or item.
I totally get the reasoning and agree with it. I just didn't want to complicate maintainability even further by adding another thing to account for when extending. So, this is more for a future vision thing. Anyway, I think giving the ability to use custom prompt engines is a win-win and good foundation for future to make working with prompts a breeze.

@Green-Sky, fixed the two bugs in the latest commit to main in the parent repo, thanks for pointing that out. Now it is slash agnostic and consistent - strips it when working with urls in any case.

Anyway, I think giving the ability to use custom prompt engines is a win-win and good foundation for future to make working with prompts a breeze.

I agree that's a good chance. It also should be possible to use that to add the assistant response shortcut stuff back in. I see you kept this part: https://github.com/GOAT-AI-lab/GOAT-Storytelling-Agent/blob/6d315078e14e0825071b01749bd24ae96b8cca11/goat_storytelling_agent/storytelling_agent.py#L94
That was the main actual code change necessary to support that behavior (if the last prompt item was from assistant, add the content like it was part of the response).


Allow filtering on the settings view

Lapce is growing, and so is the number of configurable settings it has.
It would be great to have a way to filter the setting to help the user find what they're looking for, instead of having to scroll and jump between different sections.
For example, if I need to change the font size, I could type "font" in a "Filter" text field, and only relevant options will be shown.
Like this :

Cheers

Closing as this has been merged.
Thank you @tk103331


Images for stages

There are some stages missing images.

[ ] Great Ravine (st106, st107)
[ ] The Guiding Lands (st109)
[x] Introduction (st401)
[ ] Everstream (st403)
[ ] Confluence of Fates (st405)
[x] Ancient Forest (intro) (st406)
[x] Caverns of El Dorado (st409)
[x] Chamber of Five (st505)

The Guiding Lands (st109)
I did not have my graphics settings maxed though (other than HD textures), hope it's good enough.

Thanks, I'll add it to the rich presence assets.

Here's one of the Everstream I took a few days ago but forgot to upload

until now.


Ensure newly-created pending invitation is displayed on invitations page

fixes #224

agreed, and added. merging


Include reverse direction of user inputted transmission lines

If a user inputs a transmission line where (region_from, region_to) is not in alphanumeric order, the indexing will not line up for tc_table and reverse_tc. This can be solved by duplicating and reversing the inputted transmission lines, and then appending those reversed tx lines to the transmission_constraints_table.

Looks good. I wrote a test for user constraints that I'll add to develop.


How to I can Increase APN  Expiry time one week set?

Already Documentation gave one hr().But I want set time at one week. I'm try to apply many javascript functions (one week= note.expiry = Math.floor(Date.now() / 1000) + 3600; // Expires 1 hour from now.     ). But I had error for "bad expiration".  How I can set one week.

3600 are seconds (60 seconds * 60 minutes = 3600 seconds = 1 hour). You can set to
note.expiry = Math.floor(Date.now() / 1000) + (60 * 60 * 24 * 7); (60 seconds * 60 minutes * 24 hours * 7 days)
APNS Expiration: A UNIX epoch date expressed in seconds (UTC). This header identifies the date when the notification is no longer valid and can be discarded.
If this value is nonzero, APNs stores the notification and tries to deliver it at least once, repeating the attempt as needed if it is unable to deliver the notification the first time. If the value is 0, APNs treats the notification as if it expires immediately and does not store the notification or attempt to redeliver it.
In 2009 PC World stated that max expiration is 28 days ... but the documentation does not say anything about this.

@mihai-iorga  Thanks man.. !  I get it more info ..


Fix crash of SettingsActivity on resume

SettingsActivity#populateSettingsList listens for changes in accounts using observeNotNull that throws when a null value is assigned.
This change uses an empty list as a null object instead of the literal null value.
An alternative approach would be checking for null in all observers (currently only SettingsViewModel) but using an empty list avoids building this checking logic in each observer (cf. null object pattern).

Follows our existing codestyle. :heavy_check_mark:
Does not break any unit tests. :heavy_check_mark:
Contains a reference to the issue that it fixes. :x:
For cosmetic changes add one or multiple images, if possible. N/A

@Valodim and I talked about this today. Changing the value in onInactive() will cause the observer to be updated with that empty list placeholder value the next time it becomes active. If loading the account list takes some time this will first show an empty account list, then the actual list of accounts. It doesn't make for a nice user experience (I tested this with an artificial delay).
My suggestion is to not set the value in onInactive(). This will keep the old list of accounts in AccountsLiveData. Resuming the activity won't update the list right away (because it hasn't changed). Only after the "refresh load" has completed the list of accounts is updated. Most of the time the list stays the same, so there won't be any visual disruption (list disappearing, then reappearing). And if an account is added or removed we might see the old state for a bit, then the new state. I think this makes for a nicer user experience.
In practice it hardly matters, because accounts are cached in memory and "account loading" is really fast. The way I suggest doesn't change the UI as often and has less potential to be visually disruptive. Removing the list has the advantage of not holding on to an account that might be deleted. But since we're not doing anything critical with the Account instance I see no harm in potentially holding on to it beyond the lifetime of an account.
And while we're at it, we can remove the init block. Right now we load the account list twice when first observing AccountsLiveData. Once triggered by the constructor and once by onActive().

Adjusted according to your suggestions @cketti.