support for per-chunk compression

Is it possible to have different compressors, e.g. lossy and lossless for individual chunks?
In a scenario, where you have a mask of importance, where you want to keep signal with lossless compression or even with no compression, but have other parts of the signal with lossy compression for efficiency and space.
For example we have:

import zarr
A = zarr.zeros((32, 32), chunks=(4, 4))

important region that I want to keep is A(4:11,4:11), where we want to go lossless, e.g. zlib, then for the rest I want to use quantize from numcodecs for lossy compression. This way, will have high precision for interesting parts within mask and have lossy compression for out of mask and have two different compressor for different parts of a single array at chunk level.

Hi Erhan, thanks for getting in touch. That's not currently possible I'm
afraid, the compressor is configured for an entire array, so all chunks are
processed via the same encoding pipeline.
There is a possible workaround, where you create two arrays with the same
shape, one with lossy and the other with lossless compression. You then
choose which regions to put data in, based on your mask. Under the hood,
chunks only get materialised when written, so each array would have an
empty region with zero storage cost corresponding to the region containing
data in the other. Not sure this is a solution as you'd still need some
logic on your side to read data from the appropriate array based on the
mask, but thought I'd mention the idea.
On Tue, 20 Nov 2018, 16:00 Erhan Bas<EMAIL_ADDRESS>wrote:

Is it possible to have different compressors, e.g. lossy and lossless for
individual chunks?
In a scenario, where you have a mask of importance, where you want to keep
signal with lossless compression or even with no compression, but have
other parts of the signal with lossy compression for efficiency and space.
For example we have:
import zarr
A = zarr.zeros((32, 32), chunks=(4, 4))
important region that I want to keep is A(4:11,4:11), where we want to go
lossless, e.g. zlib, then for the rest I want to use quantize from
numcodecs for lossy compression. This way, will have high precision for
interesting parts within mask and have lossy compression for out of mask
and have two different compressor for different parts of a single array at
chunk level.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zarr-developers/zarr/issues/341, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAq8QkGn1uZeYabGmjnM_IzHcxTuA8dVks5uxCcIgaJpZM4YraMo
.

Thanks, it is a good starting point for me.


Lasso effect on top of react virtualized

Hi,
I'm looking for examples on how to create "Lasso" effect (a box for range selection) on top of react virtualized grid. I don't care about the selection itself, a callback for a cell being hovered should be enough.
I know there is a react-selectable out there and also some forks, but none of them actually works well with react virtualized.
any ideas?
Thanks

Hello! 😄
For this type of question, I suggest using Stack Overflow with a #react-virtualized tag or asking in the react-virtualized Slack channel. Issues are reserved for bug reports and feature-requests.
This helps keep the project somewhat more maintainable for me and hopefully gets you an answer faster (since more people check those places than monitor GitHub issues). 😄


BitFinex order id overflow

BitFinex raw code uses int for storing order id's. E.g. BitfinexOrderStatusResponse
Order ID's for BTCUSD on BitFinex have recently gone above max value for java int 2,147,483,647.
com.xeiam.xchange.bitfinex.v1.service.polling.BitfinexTradeServiceRaw.getBitfinexOpenOrders therefore now throws a "Numeric value (2149xxxxxx) out of range of int" exception when returning any open orders for a user.
Potentially same issue for other Bitfinex_...._Response DTO classes. E.g. BitfinexOfferStatusResponse

@Panchen believe this has already been fixed, could you check with latest develop branch?
https://github.com/timmolter/XChange/pull/1409

@jheusser thanks. Tested latest dev branch vs BitFinex this am and confirmed fixed.
Couldn't find an issue for above and missed #1409


Update Supporting-Multiple-Target-Frameworks.md

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/Supporting-Multiple-Target-Frameworks.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


RuntimeError: PyNaCl library needed in order to use voice

Everytime I start up the bot it always says that it needs PyNaCl Library needed in order to use voice and  I don't see why it would be doing this as I started completely new with the bot through the .zip and I'm getting this issue. How would I fix this problem

Update your dependencies.


Cleanup

Coverage remained the same at 98.17% when pulling 978053fc257e0b6cbfa00e1f670f815ace78007e on feature/solr_weights into 3cd751c2ecb2afdc5d1bbccfa600b512af224bb8 on development.

Coverage remained the same at 98.17% when pulling 978053fc257e0b6cbfa00e1f670f815ace78007e on feature/solr_weights into 3cd751c2ecb2afdc5d1bbccfa600b512af224bb8 on development.

Coverage remained the same at 98.17% when pulling fc4a7010b91880b7c6121d6603bc816ce8578901 on feature/solr_weights into 3cd751c2ecb2afdc5d1bbccfa600b512af224bb8 on development.

Coverage remained the same at 98.17% when pulling fc4a7010b91880b7c6121d6603bc816ce8578901 on feature/solr_weights into 3cd751c2ecb2afdc5d1bbccfa600b512af224bb8 on development.

Coverage remained the same at 98.17% when pulling fc4a7010b91880b7c6121d6603bc816ce8578901 on feature/solr_weights into 3cd751c2ecb2afdc5d1bbccfa600b512af224bb8 on development.

Coverage remained the same at 98.17% when pulling 7d591622ac58a79e7b7f4ceafc44444f95fa3d66 on feature/solr_weights into 3cd751c2ecb2afdc5d1bbccfa600b512af224bb8 on development.


[Bug]: Remix on Cloudflare Worker - Cannot use 'import.meta' outside a module

Which packages are impacted?

[X] remix-validated-form
[ ] @remix-validated-form/with-zod
[ ] @remix-validated-form/with-yup
[ ] zod-form-data

What version of these packages are you using?

remix-validated-form: ^4.1.9
@remix-validated-form/with-zod: ^2.0.1

Please provide a link to a minimal reproduction of the issue.
https://github.com/omarkhatibco/remix-cf-remix-validated-form
Steps to Reproduce the Bug or Issue
just run yarn dev
Expected behavior
should work fine.
Screenshots or Videos
No response
Platform

OS: mac
Browser: chrome
Version: 100

Additional context
this Problem is not related directly to remix-validated-form it's related more to Jotai, but since I could not find anyway to fix Jotai, I had to report it.
the possible solution is just change the import from
- import { useUpdateAtom } from 'jotai/utils'
+ import { useUpdateAtom } from 'jotai/utils.cjs'

reference for the Issue

Thanks for bringing this up! I think this would be good to fix.

Hello @airjp73,
it seems that v1.3.5 is breaking ESM in Remix, let's wait till v1.3.6 and check it again.

@aiji42 and @omarkhatibco thanks for debugging this! your comments and links allowed me to understand / track down what was going on for me. i’m using jotai with remix and cloudflare-workers and ran into the same problem, but i couldn’t find any open issues related to it in remix-run/remix or pmndrs/jotai, though there is a closed issue in the jotai repo: https://github.com/pmndrs/jotai/issues/1094
do either of you know where i can look to follow along with potential future progress with this?
also, as an aside, i was able to get things working for myself by pinning jotai to v1.5.3 (v1.6.0 introduced the import.meta.env checks via the rollup.config.js).

Is this still an issue in the latest version? I migrated all the state management to zustand awhile back -- does it have the same problem?

Going to close this. Please feel free to re-open or write a new issue if the problem persists with the latest version.

This is still an issue with
remix-validated-form 4.6.9
@remix-validated-form/with-zod 2.0.5
@remix-run/cloudflare 1.13.0
@remix-run/cloudflare-pages 1.13.0
@remix-run/server-runtime 1.13.0

but only with "target": "ES2019" in tsconfig.json. That's the default for the Remix-Cloudflare template.


Add options to specify the database host and port

Add options to specify the database host and port if they are not default.
Postgresql 9.5 sets the default to allow peer access via sockets, which doesn't work because both the bacula services run as root.
Setting the db host to 'localhost' (and being able to set the port if necessary) allows it to work over tcp/ip rather than sockets which means it can use a password.
They are both set to undef by default to retain current behaviour and try to use a socket connection instead.

With some recent updates to the structure of this module, I now set the following hiera data to achieve the desire from this pr.
bacula::director::manage_db: false
bacula::director::db_type: 'pgsql'
bacula::director::db_address: 'mydb.example.com'
bacula::director::db_port: '5432'
bacula::director::db_pw: '123456'

Let me know if there are issues with this approach, but its been working for me in the last few months.  Cheers.

Awesome, that'll work nicely - thanks!


some question about activitynet dataset

I found that about 400+ video features were missing from the uploaded new activitynet (link: https://app.box.com/s/h0sxa5klco6qve5ahnz50ly2nksmuedw/folder/138579301343) , resulting in the absence of many samples from the test set. This will lead to inaccurate performance under the evaluation. May I ask on which data set will the performance test of the follow-up work be conducted ?

I found that about 400+ video features were missing from the uploaded new activitynet (link: https://app.box.com/s/h0sxa5klco6qve5ahnz50ly2nksmuedw/folder/138579301343) , resulting in the absence of many samples from the test set. This will lead to inaccurate performance under the evaluation. May I ask on which data set will the performance test of the follow-up work be conducted ?

Hello! Can you share the code on your ActivityNet dataset with me? The author was not released


Only building docker images in prow presubmit

Since circle CI is doing most of the unit testing anyway.

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

Needs approval from an approver in each of these files:

prow/OWNERS

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

@sebastienvas: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
e477e1f7eb93e4833cf69d8d03312fbb1f1baaea
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

closing as this does not improve much anyways.


npm install -g yarn

For new people to react it would be better to add to the readme the step of installing yarn (npm install -g yarn)

Good idea, Will add it in the next iteration of the docs.


Suggestion: Add detailed blog on how to use the plugin in README

I have written a blog post on how to add subscriptions in-app purchases in Flutter using this plugin.
How to Implement Subscriptions In-App Purchase in Flutter
For many people who wants to use this plugin this post will be very helpful to them to start with.
I wrote this blog after implementing the same approach in my Flutter app.
I know the doubts I faced while implementing the in-app purchase feature in my app.
Please do correct me if any information is wrong or needs improvement in the blog.
Thanks!

Hey @varunkamani ,
I read your blog. It's awesome, great work.
But I am seeing that you are calling finishTransaction when the transaction state is deferred, you should NOT do that.
Deferred state may arise when the billing api is asking the user for his payment details. But that does NOT mean that the transaction is finished.
Finish transaction should only be called when the transaction state is either purchased, failed or restored.
Read more here: https://developer.apple.com/documentation/storekit/skpaymentqueue/1506003-finishtransaction

Hi @dipinarora9
Thanks for the response.
What action should I take in the case of a Deferred state? Should I do nothing just like the Purchasing state?
This will help me to correct the blog and my existing app.
Is there any other thing that I'm doing wrong?
Thanks.

Yes, leaving it to nothing just like purchasing state would be ok.
And no, there is no other mistake.

Thanks.

@dipinarora9 Thanks for the feedback. I have fixed the bug. Please verify.

#264

That was very helpful, thanks. I wish I'd seen this earlier! You have this block in _getPastPurchases():
    for (var purchasedItem in purchasedItems) {
      bool isValid = false;

      if (Platform.isAndroid) {
        Map map = json.decode(purchasedItem.transactionReceipt);
          // if your app missed finishTransaction due to network or crash issue
          // finish transactins
        if (!map['acknowledged']) {
          isValid = await _verifyPurchase(purchasedItem);
          if (isValid) {
            FlutterInappPurchase.instance.finishTransaction(purchasedItem);
            _isProUser = true;
            _callProStatusChangedListeners();
          }
        } else {
          _isProUser = true;
          _callProStatusChangedListeners();
        }
      }
    }

I wasn't doing this, but was just checking isAcknowledgedAndroid. This was crashing my app, because it is null for subscriptions, apparently. It is set for non-consumable purchases. You can see that this is apparently by design, as it is set here.
Is that expected behavior for some reason that I am missing? It surprises me. Very helpful that the plugin provides that data as a workaround, but I'm wondering if I'm missing something about subscriptions...


Fix VS Project References

Hiya,
Was updating my clone of this library and I noticed several different references broken in the VS Solution. Hopefully this should add most of them back. Also ignore the appveyor stuff, I was messing around with that build process; feel free to squash all of my commits.
Thanks!

Looks good! We just merged a massive branch of changes so there's going to small issues.
Thanks!


some integration tests checks

we need to check integration tests for:

qsfs
wg
k8s with modules

integrated with another issue


Feature request: sort_key(&self) -> usize for lock ordering

Start by reading this thread.
I know that the idea is incomplete, and as such it isn't ready for either an RFC or inclusion in the standard library.  So my question is, would you be willing to help design a better API, and maybe even include it in parking_lot to see how well it works?

I don't really think this belong in parking_lot itself. As sfackler said in the linked thread, you can easily do this in your own library.

See my reply to sfackler on that thread.  Put simply, how do you get Arc<Mutex<_>> to work correctly?

@CAD97 Actually came up with better code in the other thread.  Reposting here in case anyone comes searching:
use std::sync::{Arc, Mutex};

#[inline]
fn pointer_as_usize<T>(p: *const T) -> usize {
    p as usize
}

fn main() {
    let my_mutex = Mutex::new(3);
    let my_mutex_ptr: *const Mutex<usize> = &my_mutex;
    let my_other_mutex_ptr = pointer_as_usize(&my_mutex);
    println!("my_mutex_ptr       = {:?}", my_mutex_ptr);
    println!("my_other_mutex_ptr = 0x{:x?}", my_other_mutex_ptr);

    let shared_mutex = Arc::new(my_mutex);
    {
        let borrowed_ptr: *const Mutex<usize> = &*shared_mutex;
        println!("borrowed_ptr   = {:?}", borrowed_ptr);
        println!("borrowed_ptr 2 = 0x{:x?}", pointer_as_usize(&*shared_mutex));
    }

    let shared_mutex_2 = shared_mutex.clone();
    {
        let borrowed_ptr: *const Mutex<usize> = &*shared_mutex_2;
        println!("borrowed_ptr   = {:?}", borrowed_ptr);
        println!("borrowed_ptr 2 = 0x{:x?}", pointer_as_usize(&*shared_mutex));
    }
}

Based on the fact that his suggestion is utterly trivial to implement, I humbly withdraw this feature request.


Compliance command failure

I am trying to run compliance test for the Pico core using my UVM ENV but facing issue while running compliance command
with reference to attached file.
Compliance Testing Failure using the below command as follow.docx
Please let me know if any switch is missed to add in my compliance command.

Clone this repo: https://github.com/InspireSemi/riscof_install_example_DUT
This repo is setup for using ACT to test a DUT vs Sail.  It has scripts to
install Sail and other dependencies needed by Sail/Riscof
There is a example_dut/ dir that has sample python scripts, plus DUT
environment headers.  You can use this as a template for your DUT.
You cannot just clone riscv-arch-test and run from there.  You need some
infrastructure around it that this repo provides.
If you have any questions about this repo email me and I can help you.
Marc
On Wed, Apr 10, 2024 at 7:23 AM T0288827 @.***> wrote:

I am trying to run compliance test for the Pico core using my UVM ENV but
facing issue while running compliance command
with reference to attached file.
Compliance Testing Failure using the below command as follow.docx
https://github.com/riscv-non-isa/riscv-arch-test/files/14931382/Compliance.Testing.Failure.using.the.below.command.as.follow.docx
Please let me know if any switch is missed to add in my compliance command.
—
Reply to this email directly, view it on GitHub
https://github.com/riscv-non-isa/riscv-arch-test/issues/452, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AD72ZMZARMK2Q7AP67L6IZDY4UOL3AVCNFSM6AAAAABGAH5NGOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZTKMZWGA4TGNQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
/****************
Marc Karasek
ASM T648
Herder of Cats
****************/

Did you try this fix?
IF yes, did this fix your problem?
IF yes, please close this issue
IF no, please describe what errors you get when following Marc's advice
If no description is following, I'd advise the maintainer is to close this proactively in a couple of weeks.

Thanks for the reply,but for my project Riscof  is not the usage. Can you let me know is there any infrastructure to handle the test.S
Because I could see CVA6 and few more IPs are running without Riscof platform.

Sorry, but the arch-test sigs use the arch-test framework, which is riscof.
IF you don't use riscof, these tests won't help at all (since they are not self checking, and require running Sail and comparing the results)
There are also a set of spike tests that might be more appropriate for your use case:
https://github.com/riscv-software-src/riscv-tests
Caveat: they only support the configurations that Spike supports, and they don't have a lot of coverage.


Edited to make Django1.9 compatible

@tabo Any idea of the timeline to get this merged in, or is there anything I could do to speed that up?
I could definitely use Django 1.9 support!

FYI, there's a bug here https://github.com/tabo/django-treebeard/blob/master/treebeard/templatetags/admin_tree.py#L84
in django 1.9 display_for_field() has an additional parameter empty_value_display
https://github.com/django/django/blob/8ab58b80529c5206654c1042a4ddcf2da364f8ec/django/contrib/admin/utils.py#L383

@tabo thanks for the release :+1:


Fix param annotation in server_builder.h

This fixes the documentation for the AddListeningPort() function, which fails to display the |creds| parameter properly:
https://grpc.io/grpc/cpp/classgrpc_1_1_server_builder.html#a5bf2d8c40e6b4ca170b9ee927d4db326

this is ok to test

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences


loadable components is pre-loading all the route chunks from start

Hi,
I'm not sure if this is expected behavior in development, a bug or a missconfiguration. I have the following loadable routes:
import loadable from 'loadable-components'

// Component split-code (lazy load)
export const Dashboard = loadable(() => import('./Dashboard'))
export const SignIn = loadable(() => import('./SignIn'))

export const PasswordReset = loadable(() => import('./PasswordReset'))
export const PasswordResetEdit = loadable(() => import('./PasswordResetEdit'))

export const Users = loadable(() => import('./Users'))
export const User = loadable(() => import('./User'))
export const EditUser = loadable(() => import('./EditUser'))
export const NewUser = loadable(() => import('./NewUser'))

And they are imported and used with react router v4 the following way:
// We only need to import the modules necessary for initial render
import React from 'react'
import PropTypes from 'prop-types'
import { Switch, Route } from 'react-router-dom'
import PrivateRoute from 'components/PrivateRoute'
import * as LoadableRoutes from './routes'

export const Routes = (props) => {
  return (
    <Switch>
      <Route exact path='/sign-in' render={routeProps => <SignIn {...routeProps} persistor={props.persistor} />} />
      <Route exact path='/passwords/new' component={LoadableRoutes.PasswordReset} />
      <Route exact path='/passwords/edit' component={LoadableRoutes.PasswordResetEdit} />
      <PrivateRoute exact path='/' component={LoadableRoutes.Dashboard} persistor={props.persistor} />
      <PrivateRoute exact path='/users' component={LoadableRoutes.Users} persistor={props.persistor} />
      <PrivateRoute exact path='/users/new' component={LoadableRoutes.NewUser} persistor={props.persistor} />
      <PrivateRoute exact path='/users/:id' component={LoadableRoutes.User} persistor={props.persistor} />
      <PrivateRoute exact path='/users/:id/edit' component={LoadableRoutes.EditUser} persistor={props.persistor} />
    </Switch>
  )
}

Routes.propTypes = {
  persistor: PropTypes.object.isRequired
}

export default Routes

This <Switch> component is imported from the main AppContainer like:
import { PersistGate } from 'redux-persist/integration/react'
import { Router } from 'react-router-dom'
import Routes from 'routes'

class AppContainer extends Component {

... [code ommited for brevity]...

<Provider store={store}>
            <PersistGate loading={null} persistor={persistor}>
              <div style={{ height: '100%' }}>
                <ReduxToastr
                  timeOut={toastrDefaultTimeout}
                  newestOnTop={newToastrAlwaysOnTop}
                  preventDuplicates
                  position='top-right'
                  transitionIn='fadeIn'
                  transitionOut='fadeOut'
                  progressBar />
                <Router history={history}>
                  <CoreLayout {...this.props} >
                    <Routes persistor={persistor} />
                  </CoreLayout>
                </Router>
              </div>
            </PersistGate>
          </Provider>
}

export default AppContainer

And here you can see how all the chunks are loaded right from the start (cache disabled):

Is this the expected behaviour and it will work different in production ? I'm using webpack v4.
Thanks!

@neoziro yes I was using rhl. Thanks for your quick response!


max_requests_per_connection=1 causes gRPC connections reset

Title: max_requests_per_connection=1 reset gRPC connections
Description:
We have a simple upstream which is a simple helloworld gRPC server.
We set up a simple envoy proxy in front of the server with the config (see attached). One thing special is max_requests_per_connection=1
When we use a simple client that starts N go routines, each go routines sends M sequential requests, however, the many requests fail due to connection reset
"code = Unavailable desc = upstream connect error or disconnect/reset before headers. reset reason: connection termination"
If "max_requests_per_connection=1" is removed, it works fine.
Repro steps:
Source:
https://github.com/bakins/cloud-run-grpc-concurrency-test

start envoy with the attached config

start the server:
go run ./server/

start the client:
go run ./client/ --iterations 5 --workers 5  --url http://<IP_ADDRESS>:9090
2019/10/30 21:17:52 could not greet: 2 1 rpc error: code = Unavailable desc = upstream connect error or disconnect/reset before headers. reset reason: connection termination
...

Config:
static_resources:
  listeners:
  - name: listener_0
    address:
     socket_address:
        address: <IP_ADDRESS>
        port_value: 9090
    filter_chains:
    - filters:
      - name: envoy.http_connection_manager
        config:
          stat_prefix: ingress_http
          generate_request_id: false
          codec_type: AUTO
          route_config:
            name: local_route
            virtual_hosts:
            - name: local_service
              domains:
                - "*"
              routes:
              - match:
                  prefix: "/"
                route:
                  cluster: upstream
          http_filters:
          - name: envoy.router
            config:
              suppress_envoy_headers: true
  clusters:
  - name: upstream
    connect_timeout: 5s
    max_requests_per_connection: 1
    protocol_selection: USE_DOWNSTREAM_PROTOCOL
    type: STRICT_DNS
    lb_policy: ROUND_ROBIN
    hosts:
      - socket_address:
          address: <IP_ADDRESS>
          port_value: 8080

Unfortunately this is "by design" with the current H2 connection pool implementation. The implementation only allows for a primary and draining connection, and if the primary goes to draining, the draining will be terminated. This is why you are seeing resets.
We have talked about making the entire connection pool implementation more flexible but only minimal work has started yet. cc @conqerAtapple @alyssawilk @antoniovicente

Thanks for the quick answer!
I wonder why the problem goes away when I unset max_requests_per_connection ?

@mattklein123 we are working on making H2 connection pool a bit more flexible (policy driven). We have a working patch which we have been busy testing in our  environment. Next steps is to address the PR comments  on https://github.com/envoyproxy/envoy/pull/7852.

Thanks! Let me try to confirm my understanding.
When max_requests_per_connection is set 1, because of H2, single upstream connection can still carry multiple H2 streams, so there can be multiple gRPC requests sent over the the same connection?
I am still trying to understand:

"...implementation only allows for a primary and draining connection", what does draining connection mean? does it mean:
a. envoy creates a primary connection
b. for some reason, envoy needs to create a new connection
c. envoy drains the old primary connection
d. envoy creates a new connection

is it because max_requests_per_connection is set to 1, the draining happens more often? As envoy needs to drain the last connection first, which also kills the other gRPC requests multiplexed in the old connection?

And according to https://github.com/envoyproxy/envoy/pull/7852, envoy only has one H2 upstream connection, so why would the value of  max_requests_per_connection make a difference?

So I found the logs:
[2019-10-31 21:45:16.746][202635][debug][pool] [third_party/envoy/src/source/common/http/http2/conn_pool.cc:200] [
C6] moving primary to draining
[2019-10-31 21:45:16.746][202635][debug][connection] [third_party/envoy/src/source/common/network/connection_impl.
cc:104] [C5] closing data_to_write=0 type=1
[2019-10-31 21:45:16.746][202635][debug][connection] [third_party/envoy/src/source/common/network/connection_impl.
cc:193] [C5] closing socket: 1
[2019-10-31 21:45:16.746][202635][debug][client] [third_party/envoy/src/source/common/http/codec_client.cc:86] [C5
] disconnect. resetting 2 pending requests
[2019-10-31 21:45:16.746][202635][debug][client] [third_party/envoy/src/source/common/http/codec_client.cc:109] [C
5] request reset
[2019-10-31 21:45:16.746][202635][debug][pool] [third_party/envoy/src/source/common/http/http2/conn_pool.cc:236] [
C5] destroying stream: 1 remaining
[2019-10-31 21:45:16.746][202635][debug][router] [third_party/envoy/src/source/common/router/router.cc:911] [C0][S
16253906521127660216] upstream reset: reset reason connection termination
[2019-10-31 21:45:16.746][202635][debug][http] [third_party/envoy/src/source/common/http/conn_manager_impl.cc:1323
] [C0][S16253906521127660216] Sending local reply with details upstream_reset_before_response_started{connection t
ermination}
[2019-10-31 21:45:16.746][202635][debug][upstream] [apphosting/envoy/pod/filters/http_header_scrubber/http_header_
scrubber_filter.cc:113] setting the upstream execution end time
[2019-10-31 21:45:16.746][202635][debug][http] [third_party/envoy/src/source/common/http/conn_manager_impl.cc:1521
] [C0][S16253906521127660216] encoding headers via codec (end_stream=true):
':status', '200'
'content-type', 'application/grpc'
'grpc-status', '14'
'grpc-message', 'upstream connect error or disconnect/reset before headers. reset reason: connection termination'
'date', 'Fri, 01 Nov 2019 04:45:16 GMT'
'server', 'envoy'

But for some reasons, I tried setting "x-envoy-retry-grpc-on" to "unavailable" doesn't seem to retry?
https://www.envoyproxy.io/docs/envoy/v1.9.1/configuration/http_filters/router_filter#x-envoy-retry-grpc-on

nvm, solution is https://github.com/envoyproxy/envoy/issues/7413#issuecomment-506689327
Even with retry turned on, it doesn't eliminate the reset errors ...

We understand the implementation details now. No further action needed. Thanks everyone!


feat: Avalonia Properties Page

What does the pull request do?

Add Properties Page to project properties in VS.

Compiling

EnableAvaloniaXamlCompilation
AvaloniaXamlIlVerifyIl
~AvaloniaUseExternalMSBuild~
AvaloniaUseCompiledBindingsByDefault
~AvaloniaAccessUnstablePrivateApis~

Debug

AvaloniaXamlIlDebuggerLaunch
AvaloniaXamlReportImportance

Name Genenrator

AvaloniaNameGeneratorIsEnabled
AvaloniaNameGeneratorDefaultFieldModifier
AvaloniaNameGeneratorFilterByPath
AvaloniaNameGeneratorFilterByNamespace
AvaloniaNameGeneratorViewFileNamingStrategy

What is the current behavior?

What is the updated/expected behavior with this PR?

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

Checklist

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

Breaking changes

Obsoletions / Deprecations

Fixed issues

This is really neat! I never knew this could be done

This is really neat! I never knew this could be done

You are right, and it is possible to add the controls to the Toolbox but currently only Winform and WPF are supported.
I'd like to try to implement the Toolbox for the VS Avalonia extension, but I'm waiting for the VS Code extension to be made public.

You can test this PR using the following package version. 11.0.999-cibuild0038502-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0038534-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0038593-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

@maxkatz6 Should i made other changes?

LGTM, but I don't know if we want to merge it now or later for 11.1 or to a special 11.1 branch @kekekeks

better merge now and provide better tooling for users on 11.0 too

I realize the focus is on bug-fixes and stabilization only for now. But this PR doesn't change anything code-related and only makes these project properties easier to discover and configure. There should be no ill-effect and will even help new users. Seems like a good candidate to merge sooner rather than later.

You can test this PR using the following package version. 11.0.999-cibuild0038882-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0038894-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

When I try out the latest nightly build, which contains these changes, I get an endless parade of binding errors. It turns out that in each project, the new property page has AvaloniaUseCompiledBindingsByDefault checked.
This feature isn't enabled by default in 11.0.4. This seems like an unintentional change.

@TomEdwardsEnscape  Thanks for the feedback, I'll look into it.


Moving github.com/zededa/shared to pillar

This moves the content of what matters in github.com/zededa/shared to pillar proper.
Note that this patch is missing the tests and the history of that repo. The reason for that is secret leaks.
At this point, I propose we consider this patch and gradually move the tests here as well. For now, though, the tests stay in github.com/zededa/shared which means that THAT repo will have to be modified to import from github.com/zededa/eve/pkg/pillar/zedUpload. This is not a big deal, but we have to keep that in mind anytime code in pkg/pillar/zedUpload is modified.
Obviously cloud itself will also have to import from pkg/pillar/zedUpload

Btw @deitch @nordmark @kalyan-nidumolu -- I have a similar patch fro pulling api into eve -- but that I'll send tomorrow (since there's still a few teaks remaining).
api repo, of course, will be imported with all its history


Node.js 9: Сrash when trying to install a new project (bug)

Hello. OS Ubuntu 16.04
How to reproduce this bug:

I installed foundation by the guide
Starts new project
Try to start next project and app crashed

What should happen:
Installer must create files for new project
What happened instead:
Installer crushed. Terminal output:
usesa@pinkya-spot:/var/www/udemy-electron$ foundation new myApp
? What are you building today? A web app (Foundation for Apps)
? What's the project called? (no spaces) styles

           /|
          | |  /| ,
     .  /\|  \/ |/|
     |\/          |       Thanks for using ZURB Foundation for Apps!
     ||\__/\____/||       -------------------------------------------
  ___|| ======== ||___    Let's set up a new project.
 /___||  O    O  ||___\   It shouldn't take more than a minute.
     ||  ______, ||
     /|          |\
    /_/\\/\  /\//\_\
        \/\\//\/
           \/

Downloading the project template...
Done downloading!

Installing dependencies...

/usr/local/lib/node_modules/foundation-cli/node_modules/npm/node_modules/tar/lib/entry.js:165
  ;["path", "linkpath"].forEach(function (p) {
                        ^

TypeError: Cannot use 'in' operator to search for '0' in arguments_marker
    at forEach (<anonymous>)
    at Entry._setProps (/usr/local/lib/node_modules/foundation-cli/node_modules/npm/node_modules/tar/lib/entry.js:165:25)
    at new Entry (/usr/local/lib/node_modules/foundation-cli/node_modules/npm/node_modules/tar/lib/entry.js:46:8)
    at Extract.Parse._startEntry (/usr/local/lib/node_modules/foundation-cli/node_modules/npm/node_modules/tar/lib/parse.js:241:11)
    at Extract.Parse._process (/usr/local/lib/node_modules/foundation-cli/node_modules/npm/node_modules/tar/lib/parse.js:131:12)
    at BlockStream.<anonymous> (/usr/local/lib/node_modules/foundation-cli/node_modules/npm/node_modules/tar/lib/parse.js:47:8)
    at emitOne (events.js:125:13)
    at BlockStream.emit (events.js:221:7)
    at BlockStream._emitChunk (/usr/local/lib/node_modules/foundation-cli/node_modules/npm/node_modules/block-stream/block-stream.js:145:10)
    at BlockStream.resume (/usr/local/lib/node_modules/foundation-cli/node_modules/npm/node_modules/block-stream/block-stream.js:58:15)

Browser(s) and Device(s) tested on:
OS Ubuntu 16.04
Foundation Version(s) you are using:
Foundation CLI version 2.2.5

What is your npm and Node.js version?

Possibly related: https://github.com/nodejs/node/issues/16781

@DanielRuf , yes i have 9 version of node. Ok, I'll try what you suggest to me now. But first time project installed w/o any errors.

Great. So it seems there is a bug in Node.js 9. We should track this one.

It seems 9.5.0 has this fix.
https://github.com/nodejs/node/commit/6ddba2e08eaa7431609e66f36568a77d52447e18
https://github.com/nodejs/node/blob/v9.5.0/deps/v8/src/flag-definitions.h
Can you verify this?

turbo_inline_array_builtins

The last release which had this flag enabled was 9.1.0.
9.2.0 was the first release which contains the fix and should work.
https://github.com/nodejs/node/blob/v9.1.0/deps/v8/src/flag-definitions.h
https://github.com/nodejs/node/blob/v9.2.0/deps/v8/src/flag-definitions.h

NodeJS v 9.5.0
You're all set!

 ✓ New project folder created.
 ✓ Node modules installed.
 ✓ Bower components installed.

Now run foundation watch while inside the myapp2 folder.

Looks all fine. I thought I installed version 9.0.0 with apt-update. nvm is really awesome tool. Thanks one more time!


NOM looking for package.json

Thank you for taking the time & effort to make this. Unfortunately, I am unable  to get it running. First off I have node V14.17 on an up to date RPi 3B. when I issue the command npm start, I Get the following response:
npm ERR! syscall open
npm ERR! path /home/pi/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2021-05-26T16_13_08_108Z-debug.log
2021-05-26T16_13_08_108Z-debug.log
It seems it is looking for package.json. I am attaching the log file.
BTW While installing I had to a command like npm audit-fix - I don't know if it is relevant but thought I would mention it.
Edit: Title should read "NPM looking for package.json"

I just installed this myself on an RPI with touchscreen.  When you clone from Git, you should have a directory called pi-weather-station.  You want to cd into that and then run npm start.  That's where the package.json is to get it started I believe.


how to add nodes and edges in RDB without a cypher query so that it will be same as cypher query

How to manually add nodes and edges in RDB so that it's looks like nodes or edges added through a cypher query

In order for you to add nodes and edges in a Relational Database without a cypher query, you need to modify the tables that represents the graph's structure
eg:
SELECT * FROM ag_label; provides you with the table containing all your nodes, edges and relationships.
You can display the table of all the vertices in a particular graph by performing this query;
SELECT * FROM demo._ag_label_vertex;, where demo is my graph and ag_label_vertex contains the vertices in my demo graph
You should see something like this;
        id        |                properties
------------------+------------------------------------------
<PHONE_NUMBER>10657  | {"name": "Pete"}
<PHONE_NUMBER>10659  | {"name": "Mike"}
<PHONE_NUMBER>685249 | {"city": "New York", "name": "Pete"}
<PHONE_NUMBER>685250 | {"city": "Toronto", "name": "Mike"}
<PHONE_NUMBER>685251 | {"city": "Vancouver", "name": "Clint"}
<PHONE_NUMBER>685252 | {"city": "Dallas", "name": "Jane"}
<PHONE_NUMBER>685253 | {"city": "San Francisco", "name": "Tom"}
<PHONE_NUMBER>395906 | {"city": "Houston", "name": "Hugh"}
(8 rows)

Now you can manually add nodes and edges to a graph without a cypher query by running the query;
INSERT INTO demo._ag_label_vertex(id, properties) VALUES ('2533274790395907', '{"name": "Mark"}');
If you run SELECT * FROM demo._ag_label_vertex; again, you notice that the {"name": "Mark"} has been added to the table.
        id        |                properties
------------------+------------------------------------------
<PHONE_NUMBER>10657  | {"name": "Pete"}
<PHONE_NUMBER>10659  | {"name": "Mike"}
<PHONE_NUMBER>395907 | {"name": "Mark"}
<PHONE_NUMBER>685249 | {"city": "New York", "name": "Pete"}
<PHONE_NUMBER>685250 | {"city": "Toronto", "name": "Mike"}
<PHONE_NUMBER>685251 | {"city": "Vancouver", "name": "Clint"}
<PHONE_NUMBER>685252 | {"city": "Dallas", "name": "Jane"}
<PHONE_NUMBER>685253 | {"city": "San Francisco", "name": "Tom"}
<PHONE_NUMBER>395906 | {"city": "Houston", "name": "Hugh"}
(9 rows)

If you run the regular cypher query;
demo=# SELECT * FROM cypher('demo', $$
demo$# MATCH (u)
demo$# RETURN u
demo$# $$) as (u agtype);
                                                      u
-------------------------------------------------------------------------------------------------------------
 {"id":<PHONE_NUMBER>10657, "label": "", "properties": {"name": "Pete"}}::vertex
 {"id":<PHONE_NUMBER>10659, "label": "", "properties": {"name": "Mike"}}::vertex
 {"id":<PHONE_NUMBER>395907, "label": "employer", "properties": {"name": "Mark"}}::vertex
 {"id":<PHONE_NUMBER>685249, "label": "worker", "properties": {"city": "New York", "name": "Pete"}}::vertex
 {"id":<PHONE_NUMBER>685250, "label": "worker", "properties": {"city": "Toronto", "name": "Mike"}}::vertex
 {"id":<PHONE_NUMBER>685251, "label": "worker", "properties": {"city": "Vancouver", "name": "Clint"}}::vertex
 {"id":<PHONE_NUMBER>685252, "label": "worker", "properties": {"city": "Dallas", "name": "Jane"}}::vertex
 {"id":<PHONE_NUMBER>685253, "label": "worker", "properties": {"city": "San Francisco", "name": "Tom"}}::vertex
 {"id":<PHONE_NUMBER>395906, "label": "employer", "properties": {"city": "Houston", "name": "Hugh"}}::vertex
(9 rows)

You can still find {"name": "Mark"} in the output.

This is not supported nor recommended behavior. Internal representation of a graph in AGE can change and anything relying on a particular format can break. You should be using existing commands to manipulate the graph data.

I also will not recommend the manual insertion of nodes and edges into graph tables, because the node's id is automatically generated and inserting an id manually could lead to loss of graph integrity.

As nodes and relationships are stored in tables, therefore you can use SQL's INSERT INTO statement to insert node or edges. But this approach is not recommended because you need to ensure that the inserted nodes and their relationships are consistent with the existing graph structure other wise it may destroy the overall structure and integrity of the graph.

You can manually add by simply adding using SQL insert queries, but this may result into overall inconsistency in relationships with the existing structure, that's why it is not recommended


Join forces to get better sparkpost API wrapper for ruby

First I tried https://github.com/SparkPost/ruby-sparkpost gem and then I found simple_spark and it looks more advanced and more ruby-idiomatic. I suggest you guys to join forces and build one, but better sparkpost API wrapper.
Lets find the way to join forces on https://github.com/SparkPost/ruby-sparkpost/issues/42
PS. I'm not related to the sparkpost, I just want to make the OSS better.

Due to SP deciding to discontinue their gem, simple_spark has been pushed to version 1.0 as it has now been stable some time in production. It’s probably not as well tested as I would like, but as it’s now the best Ruby option there’s not much choice for us Ruby users.

@jakcharlton thanks for noticing! Great that it happened, better to have just 1 gem that everyone is using and supporting...


Ability to globally define the scms block (v0.17+)

Is your feature request related to a problem?
Looking at the new syntax of updatecli manifest for version 0.17.0 and above like in this PR, we can see the block scms is repeated word for word in every manifest.
Describe the solution you'd like
I'd like the ability to define it globally so we don't have to repeat it on every manifest needing a pull request.
Describe alternatives you've considered
N/A
Additional context
N/A

I have been thinking about this issue quite a lot recently and it will require some refactoring anyway.
At the moment everything is defined per pipeline where a pipeline matches an updatecli configuration file.
I am thinking to have something like:
.draft.yaml
scms: # Moving the SCM configuration at this level
  scm;
    kind: github
pipelines:
  specDirectory: "./updatecli.d" # So we can read all configuration from a directory like we do now
  spec:
    - name: Bump updatecli file
      specFile: "updatecli.yaml" ## So we can reference existing updatecli configuration without having to copy them here
    - name: Bump go version
      spec: ## So we can insert a pipeline configuration here
        title: Bump golang version
        sources:
            ...
        conditions:
            ...
         targets:
            ...

Something that I couldn't really decide is if If we need uniq source/condition/targets or if we need uniq "pipeline"

We might consider using viper for these, to allow specifying in a standard format either throug env vars, CLI flags or config files.
I vote for only reworking the SCM first as there is a need for it expressed by @lemeurherve in this issue (while having a top level wrapper config file could prove interesting but it not asked by a user for now)

Even if it's an interesting idea that could solve the problem, I have concerns with the viper approach as it introduces a new mechanism for the configuration.
What about having a new flag --base-config that we would use like updatecli diff --base-config base.yaml --config updatecli.d --values values.yaml and so we would do a deep merge between base.yaml and each of values under updatecli.d
base.yaml could contain any valid updatecli config.
We already have the ability to merge values files so we could have the same approach for config files as well.
https://github.com/updatecli/updatecli/blob/b527434e4f72a3a6a8a6c6489bb375723c86d3e9/pkg/core/config/template.go#L148

I don't see any arguments against your proposal of a base config: it seems legit if it fixes the issue "As a end user, I don't want to maintain 1 copy of my SCM block for each pipeline, without changing my user experience".
I'm concerned by us, trying to re-invent a configuration mechanism with merge (that are note deep merge: which defeats the whole purpose of the configuration that could be overloaded): if we do not do deep merge, then we should allow any map/dictionnary in the manifests that could be defined on different locations, such as scm.
Switching to viper might not feel easy but it will immediatly underline the flaws of our configuration model and point at these flaws so we can fix it one time for all.
But it could be interesting to specify the new "base config": you should not have to break the exisint configuration model: viper provides you with the attribute config, you don't have to care if it comes from an ENV var UPDATECLI_CONFIG, or from a config flag --config or from the attribute config: in the base config file (or all of them with merging).

I am considering working on the current issue as It could simplify the autodiscovery manifest by not having to specify scm or action configuration.
Right now I see two ways to solve
1. New top level key "global" in existing manifest
We could have a new top level key named "global" such as
scms:
    default1:
        kind: git
        spec:
             ...
global:
    scms:
        default2:
            kind: git
            spec:
                 ...

Resources defines in a global section would be available to any pipeline as long as a pipeline do not specify a key such as "default2" in this example
2. New cli flag
Similarly to my idea explained in https://github.com/updatecli/updatecli/issues/430#issuecomment-1000703155
We could have a flag name "--gobal-config" or "--base-config", or "--default-global" that would work similarly to "--config" and would allow us to specify any Updatecli manifest as the default config.
Regarding the deep-merge topic, my guts tell me to avoid that rabbit hole but I don't have strong opinion

I'm not sure about the 1. New top level key "global" in existing manifest. As a user, it seems confusing: which YAML manifest file holds the global? What if I got 2 different files? etc.
The 2nd one looks really promising!

Thanks for your feedback, I am also more in favor of the second approach. I'll try to find some time to dig into it


fix#73: Fix accidentally overwriting webprefs

If preferences.browserOverrides.webPreferences was included, it overwrote the defaultWebPreferences since Object.assign() only does a shallow clone. This would mean the preload script wouldn't be set if webPreferences were included this way, and we see the error #73 .
This should fix that issue.

Thanks @lacymorrow
Was indeed a scenario I didn't think about.
Candidate for our first unit test ;)

@lacymorrow FYI, created a patch release for this: 2.3.1

Yep this one was my bad!
Shot myself in the foot.

Fix #73


chore: fix kubevirt file naming

The colon in the file name breaks Go imports. This updates the kubevirt examples to not include any colons in file names.
Fixes:

https://github.com/GoogleContainerTools/kpt-config-sync/issues/552

Context:

https://github.com/GoogleContainerTools/kpt-config-sync/issues/4
https://github.com/GoogleContainerTools/kpt-config-sync/pull/8
https://github.com/GoogleContainerTools/kpt-config-sync/pull/297

/lgtm

looks like both failures are metrics flakes
/retest


feat(oui-progress): progress component upgrade

UU-842
Upgraded progress component according to latest Specs
Staging link: http://feature_oui_progress_build.ui-kit.ovh/#!/oui-angular/progress
Linked To:
https://github.com/ovh-ux/ovh-ui-angular/pull/192
https://github.com/ovh-ux/ovh-ui-kit-documentation/pull/112

Hello @ganeshkumar1989,
Your pull request is now closed due to inactivity.
Feel free to re-open it if you have any update.
Anna Bot for OVH UX <3


support --filter-ip and --filter-port

Right now pwru only supports:
      --filter-dst-ip string        filter destination IP addr
      --filter-dst-port uint16      filter destination port
[...]
      --filter-src-ip string        filter source IP addr
      --filter-src-port uint16      filter source port

But when tracing packets through the stack, they can get DNAT'ed or SNAT'ed or both.
Maybe libpcap-like expression could even be used here, and converted to eBPF insns (e.g. inline asm blob), at least basic primitives to define an expression with ips & ports combined with logical and/or.

It's interesting to compile libpcap-like expression to JIT'ed eBPF insns, and make them work with pwru existing eBPF insns.

Yeah, in my spare time I am working on a small tcpdump-like syntax compiler to eBPF. Instead of bpf_tail_call() the plan is to use bpf2bpf calls.

@brb  How is it going?

Instead of bpf_tail_call() the plan is to use bpf2bpf calls.

After some researching, bpf2bpf + freplace is perfect for this case.

@Asphaltt Hey, this is still WIP. ACK on bpf2bpf + freplace.


libman.json : error LIB000: An unknown exception occurred after upgrading from Microsoft.Web.LibraryManager.Build from 2.0.96 to 2.1.50

Build fails on Docker image mcr.microsoft.com/dotnet/core/sdk:3.1-buster after package upgrade from 2.0.96 to 2.1.50 because one or more libman libraries failed to restore
Current libman.json:
{
  "version": "1.0",
  "defaultProvider": "cdnjs",
  "libraries": [
    {
      "provider": "cdnjs",
      "library"<EMAIL_ADDRESS>      "destination": "wwwroot/lib/twitter-bootstrap/",
      "files": [
        "css/bootstrap.css",
        "js/bootstrap.js"
      ]
    },
    {
      "provider": "cdnjs",
      "library"<EMAIL_ADDRESS>      "destination": "wwwroot/lib/popper.js/",
      "files": [
        "umd/popper.js"
      ]
    },
    {
      "provider": "cdnjs",
      "library"<EMAIL_ADDRESS>      "destination": "wwwroot/lib/jquery/",
      "files": [
        "jquery.js"
      ]
    }
  ]
}

Build Error:
2020-04-15T23:10:24.2235627Z   Restore operation started...
2020-04-15T23:10:24.6515837Z libman.json : error LIB000: An unknown exception occurred [/src/NewsletterCurator.Web/NewsletterCurator.Web.csproj]
2020-04-15T23:10:24.6522938Z
2020-04-15T23:10:24.6524619Z   One or more libraries failed to restore

I get the same after upgrading in an azure devops pipeline. Build-restore works fine in visual studio.
Our build pipeline is public so if it helps you can find the build logs here: https://dev.azure.com/stryker-mutator/Stryker/_build/results?buildId=4273&view=results

I was able to repro this when using the DotNetCoreCLI@2 task to build a solution, but not when using VSBuild@1.  (Thanks @Mobrockers for the sample, that saved some time for sure).  Still investigating, but just wanted to let you know I'd verified the issue.

Just to give you some more context, in my case I am using this Dockerfile and the error is generated during dotnet publish "NewsletterCurator.Web.csproj" /p:Version=$VERSION -c Release -o /app/publish.
This is my libman.json
If you need additional information, tell me

Same issue here with Azure DevOps

Heya,
same situation here using dotnetCLI.
Reverting to 2.0.96 fixed this.

This should be fixed by #575, just waiting now on our release process to publish the updated package.

2.1.76 is live now.


ModuleNotFoundError: No module named 'findatapy'

after install findatapy, i still can't run the line "from findatapy.market import Market, MarketDataRequest, MarketDataGenerator"

It means findatapy is not on your Python path

i found the 'findatapy' path under my Python path, but dunno why it can't load up inside my jupyter notebook or  PyCharm as well.


the method of woe computing is not safe enough

Issue Type
Bug
Source
binary
Secretflow Version
all
OS Platform and Distribution
max
Python version
3.8
Bazel version
No response
GCC/Compiler version
No response
What happend and What you expected to happen.
i think the method of woe computing is not safe enough,it leaks unnecessary info to others

Reproduction code to reproduce the issue.
the preprocessing script :preprocessing/binning/vert_woe_binning.py

bins_positive = self.secure_device(spu_work)(
                    secure_label, bin_select.to(self.secure_device)
                ).to(device)
* i think it's not safe enough when you reveal bin_positive info to the device which doesn't hold the label.it will leak postive label count info.
if a feature has only two bins and has big correlation with label,maybe the adversary can guess the label?
* anyway,this method of computing woe leak unnecessary info in this script.
* i think the best way is to computing woe in whole encrypted until get final result,so the good_rate、bad_rate and ln(good_rate/bad_rate) should be computed in secret sharing mode.how do you think?

and the problem also exists when computing woe in HEU device method?

Hi, this is a great question!
The definition of secure mpc is that we reveal nothing except the final results.
However, in practive, we need to notice that anything can inferred by the final results is also revealed automatically,
In this case, let's consider what the feature holder will know:

WOE and iv for each bin will be revealed (becaue those are final results).
In addition, the total count of samples (= total_labels) and the total count of samples for each bin are also known.

From the above information, the bins_positive can be easily inferred.
Note any one bin's woe, iv are known.
bin_total = bin_positives + bin_negatives
total_labels = total_positives + total_negatives
bin_woe = log((bin_positives / total_positives) / (bin_negatives / total_negatives))
bin_iv = ((bin_positives / total_positives) - (bin_negatives / total_negatives)) * bin_woe
The italic variables are known. We can surely solve a system of nonlinear equations.
To be more specific, (skip the following part if you know how to solve the above equations) let's calculate bin_positives.
e^{bin_woe} = (bin_positives / total_positives) / (bin_negatives / total_negatives)
denote
bp = bin_positives / total_positives
bn = bin_negatives / total_negatives
and from above we have
bp = e^{bin_woe} bn
then
bin_iv = (bp - bn) * bin_woe  = ( e^{bin_woe} - 1) bn *bin_woe
hence
bn = bin_iv /( e^{bin_woe} - 1)/bin_woe
then
bp = bin_iv /( e^{bin_woe} - 1)/bin_woe *  e^{bin_woe}
Now we have
bin_total = bin_positives + bin_negatives
total_labels = total_positives + total_negatives
bin_positives / total_positives = bin_iv /( e^{bin_woe} - 1)/bin_woe *  e^{bin_woe}
bin_negatives / total_negatives = bin_iv /( e^{bin_woe} - 1)/bin_woe
so
total_positives = bin_positives / (bin_iv /( e^{bin_woe} - 1)/bin_woe *  e^{bin_woe} )
(bin_total - bin_positives)/ (total_labels - total_positives) = bin_iv /( e^{bin_woe} - 1)/bin_woe
By substitute total_positives , we can solve for bin_positives.
We can conclude that from the woe final results, we can infer bin_positives.
Since bin_positives will be known anyways, we can surely reveal it early anyways.
Hence there is no security loss for the current approach.
Delay revealing bins_positive will cost more unnecessary computations.
And the same applies for HEU device method.

thanks for your deduction!
firstly, i think bin_iv can be keep encrypted in the party which doesn't hold label. sometimes we only need iv of the feature,but not iv of bin.
when bin_woe and  feature_iv were cacluated, we can only use bin_woe to transform data.and bin_iv can be ignored.
then,when bin_num>2,i think you can't get bins_positive without bin_iv, may be i am wrong?
lastly,i metion this question is that is another federated learning framework(FATE),they didn't leak positive counts to adversary,and they didn't return bin_iv to the party without label.
whatever,thanks for you answer.

 It's a great idea.
We will provide the option to calculate featrure_iv only in later release, and therefore will protect bins_positive in that option!

Thanks again for bringing this issue up. This issue will be resolved in our next release, so I am closing this issue now.


[NV24] F3 activation epoch

Post NV24 (~2 weeks) after the NV24 upgrade on mainnet, F3 is supposed to be activated. It's not yet clear what the solution will look like. Likely hard-coding the epoch (with some environmental variables) will be the solution both in Lotus and Forest. The issue is that the initial power table needs to be stored somewhere and we cannot read past 2000 epochs.

[ ] F3 activation epoch is set (and configurable via an environmental variable),
[ ] There's an option to opt-out from F3 if need be (currently it's opt-in, we may need to inverse that logic).

@hanabi1224 Could you please coordinate with the FilOz team on this? I believe there will be some testing on Butterflynet next week. Also, we tentatively scheduled F3 activation to 1 day after the calibnet upgrade.

See https://github.com/filecoin-project/lotus/pull/12552

Will do.

Determine the number for calibnet and mainnet.

Update on release process. We will need to make a patch release right after F3 activation (on calibnet and mainnet respectively) to include the initial power table cid to avoid late F3 participation issue.

@LesnyRumcajs Yes, it will be a one-liner change to hard code the initial power table for F3, to workaround late participation issue described in https://github.com/filecoin-project/go-f3/issues/477


Review when crossword data is fetched

The overall site will be built with Gatsby, because it's based on React, it generates fast sites, and I've worked with it before. However, the crossword data could be fetched at either build time or runtime.
In the former case, a source plugin would fetch the data and create a node for each crossword. Then Gatsby would create corresponding static pages from a template. This should result in faster page loads, and it would be easier to extend, for example by adding pages for each crossword type or setter. On the other hand, there are about 18K crosswords in total, which may result in long build times and/or an app that costs more to host. I'd also have to trigger daily builds using something like Netlify's build hooks and Zapier, and I'm not sure whether hosting the crossword data meets the Guardian's Open Licence Terms.
Otherwise, a route like crosswords/prize/28117 would fetch the data on the client. Given that my short term goal for the project is to practice using Redux, I think it's a better fit. If it feels clunky, I can always change tack.

Now that I think about it, the runtime approach is a blatant example of CORS, and I'd prefer not to try and work around it. Build time it is!


Implement DexVerify and LTD

IMPORTANT:

I don't intend to get this work merged as is. This is a review/RFC PR.
Please read the LTL_work.md document for more details.
This commit implements Expect(var, value) -- this will be replaced with
a full program state command.
The --verbose option doesn't output very useful info for DexVerify. The
Heuristic class needs a lot of work before I can do anything here (I have
some stashed work on this).
The result is only pass or fail -- the model either holds or it does not.

DexVerify is a dexter command which can be used to verify a proposition about the
program trace.
A proposition can be made up of atomic propositions (assertions about what
the program state) and propositions connected and operators. The operators can
be boolean or temporal. The terminology and theory behind this is explained in
the document LTL_word.md included with this commit.
The term LTD is used to describe the DexVerify subcommands which are based on
Linear Temporal Logic (LTL).

I intend for the dexter/examples/ directory to contain examples but for this work I've been using it as a sort of regression test set.

The proposition (p After q) literally means "p holds after q holds". Because of the prefix notation, After(p, q) reads as "after p holds, q holds" - to me at least - which is of course incorrect (it is actually "after q, p holds").
I've kept the operands in this order to match the other temporal binary operators.
I think there's a serious case for swapping all the binary operator operands to make parsing the prefix
notation easier (for humans). The downside is that this could really confuse people who regularly see
prefix notation and those who know LTL well already.

I'll avoid updating this with my up to date changes until #31 is accepted.

I'm closing this because it's now quite out of date. I'll put up another PR soon.


[SMALLFIX]Modify due to #478

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2966/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2968/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2969/
Test FAILed.


EqualToXmlPattern considers non-equal XMLs as exactly equal

WireMock's EqualToXmlPattern considers <DangerousOperation>X</DangerousOperation> and <SafeOperation>X</SafeOperation> or
Hello
 and  as identical XML documents, but this comparison style is very lax and could cause confusing behavior in large test suites.
WireMock version: 2.17.0
Unit test:
import com.github.tomakehurst.wiremock.matching.EqualToXmlPattern;
import com.github.tomakehurst.wiremock.matching.MatchResult;
import org.junit.Test;

import static org.hamcrest.CoreMatchers.equalTo;
import static org.hamcrest.CoreMatchers.not;
import static org.junit.Assert.assertThat;

public class WiremockXmlEqualityTest {

    @Test
    public void testXmlEquality() throws Exception {
        final EqualToXmlPattern pattern = new EqualToXmlPattern("<DangerousOperation>X</DangerousOperation>");
        final MatchResult matchResult = pattern.match("<SafeOperation>X</SafeOperation>");

        assertThat(matchResult.isExactMatch(), equalTo(false));
        assertThat(matchResult.getDistance(), not(equalTo(0.0)));
    }

    @Test
    public void testXmlEquality2() throws Exception {
        final EqualToXmlPattern pattern = new EqualToXmlPattern("
Hello
");
        final MatchResult matchResult = pattern.match("");

        assertThat(matchResult.isExactMatch(), equalTo(false));
        assertThat(matchResult.getDistance(), not(equalTo(0.0)));
    }

}

This is due to the way DiffBuilder.compare is configured, in particular:
    private static List<ComparisonType> COUNTED_COMPARISONS = ImmutableList.of(
        SCHEMA_LOCATION,
        NO_NAMESPACE_SCHEMA_LOCATION,
        NODE_TYPE,
        NAMESPACE_URI,
        TEXT_VALUE,
        PROCESSING_INSTRUCTION_TARGET,
        PROCESSING_INSTRUCTION_DATA,
        ELEMENT_NUM_ATTRIBUTES,
        ATTR_VALUE,
        CHILD_NODELIST_LENGTH,
        CHILD_NODELIST_SEQUENCE,
        CHILD_LOOKUP,
        ATTR_NAME_LOOKUP
    );

...

    .withDifferenceEvaluator(IGNORE_UNCOUNTED_COMPARISONS)

which is hard-coded and not configurable.

Wow, that's a bit of an omission isn't it! Thanks for reporting, I'll add the ELEMENT_TAG_NAME comparison into the next release.


Remove blocks runtime when building with libdispatch

The blocks runtime is already contained in libdispatch
so removing this 2nd copy from libFoundation removes duplicate
code.

The libdispatch version is also slightly more optimal as it
doesnt compile functions only needed when HAVE_OBJC is defined.

This is also needed to avoid duplicate symbol errors when statically linking Foundation using https://github.com/apple/swift-corelibs-foundation/pull/873
Also see discussion about blocks runtime in https://github.com/apple/swift-corelibs-foundation/pull/874
An alternative, which I did test, is just to remove data.c and runtime.c although this means libdispatch always has to be linked in and Im not sure if it is guaranteed to always be a dependancy.

@swift-ci please test

@parkera Can this be merged now?

Sure; let me kick off another test since it's been a while.

@swift-ci test and merge


auto-build master commits

Whenever a new commit is pushed to master (TBD: Or maybe some other trigger like setting a tag???), automatically do a minor version release, with associated version bumping and whatnot.
desired actions:

validate we are on master
run tests (again)
bump package version (in multiple places) from 1.2.3-rc to 1.2.3
~check git tag matches in-code version~
do poetry build, smoke test on artifact, then poetry publish
add git tag (and implied github release)
bump package version to 1.2.4-rc for continued development

Ideas for a trigger:

X create an issue by me, with a specifically formatted subject, or special label
X use a deployment ?? Not sure that makes conceptual sense
do a release. That's back to front though, I feel.
X also rely on the workflow_run:completed event for a dependent workflow
create a tag. this is identical to creating a release, really.
-->> manually run the workflow https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow

one method that might work:

use a script to bump version strings and add tag, and push upstream
have a workflow that listens for the tag and does the rest

Done at last 🥳


process/scheduler missing functions?

Hey, I had a look at the scheduler and process system and have a couple of questions:

Is it possible to get a feedback from the scheduler about the exit status?
1.1. e.g. if any of the processes fails, someone could implement a generic cleanup or whatever
1.2. I did it for e.g. fail, by coping the scheduler code and implemented it over the emitter, so you could connect to the fail signal
How can you get a reference to an instantiated process instance?
2.1. This is sometimes needed to do some bookkeeping.
2.2. At the moment I'm passing a pointer over the ctor of the process and in the ctor I'm assigning this (lethal XD)
Would it be possible to have something like: https://taskflow.github.io/taskflow/ConditionalTasking.html
3.1. This mechanic is really useful, if someone tries to build more complex flows
3.2. I found this https://github.com/skypjack/entt/wiki/Crash-Course:-graph, but I didn't understand how to use it, to be honest + I didn't find any link to the process/scheduler here
Is it possible to make a loop?
4.1. e.g. a process fails and the scheduler starts again from a specific process.

Thanks.

Is it possible to get a feedback from the scheduler about the exit status?

It's possible to know in which state a process is or is landing, then react accordingly.

1.1. e.g. if any of the processes fails, someone could implement a generic cleanup or whatever

You can do this in the process itself by implementing failed.

How can you get a reference to an instantiated process instance?

You can't. Probably the continuation can return it though. No idea why you're assigning this btw nor what problem it's meant to solve, so I can't really help here probably.

Would it be possible to have something like: https://taskflow.github.io/taskflow/ConditionalTasking.html

So, just a conditional continuation? Like yeah, I'm done but please ignore my children?

It's possible to know in which state a process is or is landing, then react accordingly.

How? Do you mean over the process entry points?
It would be nice to have some kind of final process, which is executed regardless if all the processes in the chain were successful or not. This handler would also get the exit code to act accordingly.

You can do this in the process itself by implementing failed.

see previous comment (would be nice if someone wouldn't have to implement a generic logic in each and every process, even if the code would be the same for all of them).

You can't. Probably the continuation can return it though. No idea why you're assigning this btw nor what problem it's meant to solve, so I can't really help here probably.

Would be good if that would be accessible... That's what I meant and how I did it:
struct FailSignalingScheduler : entt::process<FailSignalingScheduler, tasks_delta_type>
{
    FailSignalingScheduler(FailSignalingScheduler** ppSched)
    {
        if(ppSched)
            *ppSched = this;
    }
}

FailSignalingScheduler* pSched;
tasks.attach<FailSignalingScheduler>(&pSched);
doStuffWith(pSched);

So, just a conditional continuation? Like yeah, I'm done but please ignore my children?

I mean some mechanic to control the process flow. They do it over a return code which tells the scheduler which process to call next (if I understood it correct), further down, they also emulate a switch behavior.
Background: I would like to use the scheduler/process to handle network requests in a distributed system.
If a new request is received, multiple processes with multiple steps are scheduled. If the above features are supported, this logic could be easily used:
event1 -> some condition true -> do some thing -> do more -> other condition -> whatever
event1 -> some condition false -> do other thing -> restart
if any process fails, either send error back or retry operation (based on a condition)

How? Do you mean over the process entry points?

Yeah, I mean if using the failed() or aborted() functions and so on.

It would be nice to have some kind of final process, which is executed regardless if all the processes in the chain were successful or not.

Technically speaking, it's easy to implement on top of what you've already.
Just share a common context across all processes and trigger it when the counter is 0.

see previous comment (would be nice if someone wouldn't have to implement a generic logic in each and every process, even if the code would be the same for all of them).

Well, C++ supports inheritance and therefore common base classes to share logic. You don't have to reimplement it again and again. I strongly suspect that I need more context to understand your issue because so far it really sounds as an xy-problem.

Would be good if that would be accessible... That's what I meant and how I did it:

I see, although you don't have to do it either. If your type is movable, just create it in the user space, do your stuff with it, then pass-move it (as in std::move) to attach and you're done. No need to do tricky things with a self pointer.

I mean some mechanic to control the process flow.

Sounds interesting but it's definitely something to implement. It's not supported yet. I'm sorry.

Usually, things go the other way around 🙂 can you provide a working example to reproduce your error, so that I can tell you what's wrong?


Adapt it for nuxt3

The project is awesome.
Just a little request as I'm not that familiar with nuxt nor vue. But could it be adapted to nuxt3?

The plan to support the nuxt version has been planned for a long time, but due to time and energy issues, I can only continue to postpone it, because there are other things that need to be done 🤗

It can be seen that you are very interested, or you can transform this project https://github.com/xiaoxian521/pure-admin-thin into nuxt3

Thanks, I'll give it a look


Adding member via @tryghost/admin-api does not send subscribe or signup email

Issue Summary
I am using Ghost as a Headless CMS with a NextJS front-end. I have been using @tryghost/admin-api to build out UI to allow readers to subscribe to the site using the members api. Unfortunately the members api is undocumented, though I have been able to navigate the repositories to string this together:
import GhostAdminApi from '@tryghost/admin-api'

const api = new GhostAdminApi({/* config */})
const member = { email<EMAIL_ADDRESS>}
const options = { send_email: true, email_type: 'subscribe' }

// ...

await api.members.add(member, options)

This gets me 90% of the way there. Triggering the above code will fire off a POST request to:
/ghost/api/v3/admin/members/?send_email=true&email_type=subscribe
And because I am also supplying the send_email and email_type options, I expect to have an email sent to the reader, and the content of that email to be the subscribe.js email template. Unfortunately, every request I make generates a signin.js email template only.

I've done some digging on this and have managed to (I think) find the flow of logic that leads to a potential problem:

Call api.members.add from @tryghost/admin-api
This triggers a handler function to process the request
Because send_email: true is supplied as a request option, the membersService.api.sendEmailWithMagicLink function is executed. It receives the email of the newly added member and the email_type (renamed to requestedType)
This conditional passes since the options.forceEmailType argument is not supplied, and is defaulting to false
This conditional passes since a member was generated a few steps prior

Now I don't have full context of Ghost's services, but it would seem that in order for the admin-api to properly allow for other email templates to be utilized other than 'signin', this execution site of sendEmailWithMagicLink needs to "force" the email type. If it passed in options.forceEmailType: true, the email_type option to the request would be respected.
To Reproduce

Call the api.members.add function from @tryghost/admin-api with an email to add and the options { email_type: 'subscribe', send_email: true }
Notice that the email you receive is the 'signin' email

Technical details:

Ghost Version: 4.10.2
Node Version: 12.18.3
Browser/OS: Chrome
Database: default Ghost DB (not sure)

I can confirm this is an issue I have experienced as well. Maybe this is because the membership API is still in canary.

Fixed here https://github.com/TryGhost/Ghost/commit/c45afc7f2614483b40b467d47f9bc484ebe37281


Allow skipping typekit font loading using options or global variable

If anyone is not interested in using Adobe fonts, this will prevent loading them.
In this case the browser will decide the replacement font.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/15098/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15098/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15098/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15098/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15098/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15098/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15098/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15098/merge#BCU1XR#0

Visualization tests for WebGPU (Experimental)
Important - these might fail sporadically. This is an optional test.
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15098/merge/testResults/webgpuplaywright/index.html


[Character Sheet // Inventory] Support marking items' damage state

Basic support for tracking item damage states. See Item Maintenance in Core Rulebook, p.89.

Tracking this in the Inventory 2.0 work in #2.


[stable/metabase] Upgrade metabase to 0.34.3

Signed-off-by: Albert Wang<EMAIL_ADDRESS>Is this a new chart
No
What this PR does / why we need it:
Upgrades metabase from 0.34.0 to 0.34.3. There's numerous bug fixes all documented in https://github.com/metabase/metabase/releases
Which issue this PR fixes

fixes #21136

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @pmint93

/ok-to-test

/lgtm


OpenSSH install error

d64-virtualbox: Downloading OpenSSH from https://www.mls-software.com/files/setupssh-7.5p1-1.exe...
d64-virtualbox: Installing OpenSSH...
d64-virtualbox: Installing the default vagrant insecure public key...
d64-virtualbox:
d64-virtualbox: ERROR: NewItemIOError
d64-virtualbox: ERROR: at <ScriptBlock>, C:\Windows\Temp\script.ps1: line 109 ERROR: at <ScriptBlock>, <No file>: line 1
d64-virtualbox:
d64-virtualbox: Sleeping for 60m to give you time to look around the virtual machine before self-destruction...

VirtualBox Version - 5.1.26r117224
PowerShell Version - 5.0
Packer Version - 1.0.4

I'll try to get some more info and potentially a fix in as soon as possible

it was my the last commit that broke that. I've reverted it at https://github.com/rgl/windows-2016-vagrant/commit/af8ffb1eef53de9171ca96e5fd7a006ae47b1a5b. try again. thx for the heads up!


Android: notification appears blank

Hi everyone and thanks for this great package!
I successfully managed to install react-native-notifications on iOs and Android, and to send the device token back to my server (Parse Server 3.3.0). Everything works fine on the iOs side of things; however, I am experiencing several issues on Android.
The notification appears blank (no title, no body, just a white notification). When logging my notification on my Android Device, I can access data, though it is a string rather than an object. I guess the above issue comes from the fact that data is as a string rather than an object.
I am using my Parse-Server to send the notifications (guide here)
Notifications work fine in our production app, which is not using react-native-notifications.
Here is the data received by our android clients:
{data: '{"badge":1,"alert":{"title":"OuiRun t\'invite à rejoindre un run !","body":"Rejoins les autres runners de Test Run"},"payload":{"runId":"FIYtqEY192","routeName":"RunDetails"},"title":"OuiRun invites you to a run!","body":"Join the other runners of Test Run"}',
 push_id: 'iZhJKahxmR',
'google.original_priority': 'high',
'google.ttl': 2419200,
google.sent_time':<PHONE_NUMBER>762,
 'google.delivered_priority': 'high' }

I managed to make the notification title and body appear by setting a duplicate in our Parse Server code: data is used by iOs, and notification by Android. Is there a way to avoid this?
Parse.Push.send({  where: query,                    data: {  alert: { title: title, body: message },                        title: title,                        body: message,                         badge: options.badge ? options.badge : "Increment",                        sound: options.sound,                        payload: options.payload                    },                    notification: {                         alert: { title: title, body: message },                         title: title,                         body: message,                          badge: options.badge ? options.badge : "Increment",                         sound: options.sound,                         payload: options.payload                     }                }, { useMasterKey: true });
Many thanks!

Same issue with AWS Pinpoint. Token is generated, and the message arrives, but there's no title/body/media.

you can use it
{
"registration_ids":["Your id's"],
"notification":
{
"title": "Title",
"text": "Your Text",
"sound": "default",
"badge": "1",
"color": "#0072B6"
},
"data": {
"title": "Title",
"body": "Your Text"
}
}
in that way i can see the title and message when app is in background and when it's open

try using
{
    "registration_ids":["Your id's"],
     "notification":
    {
        "title": "Title",
        "text": "Your Text",
        "sound": "default",
        "badge": "1",
        "color": "#0072B6"
    },
    "data": {
        "title": "Title",
        "body": "Your Text"
    }
}
in that way i can see the title and message when app is in background and when it's open

I have to same issue as @shauns. Using remote notifications from AWS, but on Android they appear blank. iOS is working fine.
Anyone who can help me out?

Any solution for this?


Deploying multiple artifacts failing

Hi,
first of all thanks for a great plugin. Using it on our CI/CD server, but have run into an issue. Not sure if it's related to our config or not but the problem arises when there are multiple staging repositories.
I'm getting this error message
Execution failed for task ':lib:closeRepository'.
> Wrong number of received repositories in state 'open'. Expected 1, received 2

It says there are two repositories in state open, however one of them is closed/released. Support for dropping, #17 , would solve the problem, but maybe there's something else we can do to fix this?
Thanks,
Håkon

':lib:closeRepository' is suspicious in your quotation. gradle-nexus-staging-plugin should be executed exactly once when all artifacts have been uploaded. Can you release/drop all the repositories in Nexus via GUI, move apply to the root project and call it (closeAndPromoteRepository) after the upload?

Thanks for replying. There is only one artefact being uploaded. With all repositories in Nexus released and dropped, running uploadArchives and closeAndPromoteRepository from project root works just fine.
But in our case the project is being built on every commit, so in some cases a build is triggered before the previous has been automatically dropped by nexus, and this is when I get the error above.
You can find our project here https://github.com/wireapp/wire-android-translations and the gradle file here https://github.com/wireapp/wire-android-translations/blob/master/lib/build.gradle should you have a moment to take a look.

It looks good in general. Unfortunately I don't have any remedy for that now. There is on my todo list a research if there is a way to correlate artifacts uploading by Gradle with a staging repository which would be helpful in those situations. Gradle doesn't provide that information and I'm not sure if there is any in Gradle plugins internals to get.
Btw, a small suggestion regarding your build.gradle. Defining group on the project itself should make redundant doing it 3 times (1, 2, 3).

Btw, you can subscribe to #29 to get information when/if it is investigated.

Thanks for your reply, I'll keep an eye on #29 and #17 for now then. Feel free to close this issue.

yeah, we should close this ticket.  I annotated #29 with a potential solution that I think will work for all these cases as each build would open it's own staging before uploading to that staging location.


⚠ SceneTime has degraded performance

In d1b71ed, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1286 ms

Resolved: SceneTime performance has improved in 974d20b after 14 minutes.


Document HyperGraph Capabilities

I noticed in this issue https://github.com/microsoft/GraphEngine/issues/245 that GraphEngine is able to support HyperGraph structures.  I can't find the documentation on these features.  This SO Post shows that people cannot find a good HG engine.

@buddha314 The Graph Engine does not directly support HyperGraphs by default while the default model mode of the GE is "PropertyGrpah"; however, you can model HyperGraph(s) directly using TSL. This is a significant capability as the GE will code generate typed DSL of the model - that means that you don't have to write any logic for accessing the graph. All of the low-level networking is anchored from the TSL generated coded workflow up to HTTP/RCP service endpoint. This one of the big differences between the traditional, conventional, and even contemporary Graph Databases.
As the GE is a general purposed advanced Graph-powered compute engine, you can use TSL to model many types of Graph data models and algorithms.  You can start with LIKQ for search and exploration processing, and then you can roll your indexing scheme, semantic reasoning, and typical and or advanced search algorithms.  The GE is very extensible as well as you can adorn interfaces for indexing, property-labeling, semantic marking and more; you can even use LIKQ to use rules for Adjancey List processing of Edges and  Vertices. There's not a lot of documentation w.r.t advanced Graph implementations but you can model just about any type of Graph. I am working on creating documentation so as to teach and demonstrate how to use TSL to model Graphs and what the implementation of the algorithms looks like.
Quick Example:
The basic idea of the Hypergraph concept is to consider such a generalization of a graph in which any subset of a given set may be an edge rather than two-element subsets.
We can define a HyperGraph like this:

Let X = {x1, x2, x3, x4, xn} be a infinite set, and let D = {D1, D2, D3, Dm} be a family of subsets of X

The Pair H =(X, D) is called a hypergraph with the vertex set X also denote V(H), and with edge set D also denoted by D(H)

GE TSL HyperGraph Model
What we need:

HyperNodes
HyperEdges
HyperVertices
Weights

I'll plug-in the TSL source code here:

@buddha314 I'll get around to posting the code on how to model HyperGraph in TSL later today or tomorrow; I'm currently working a couple of Graph Engine bugs.

@buddha314 Hey Brain - I've been off working to resolve a few critical Graph Engine issues in the Service Fabric area, but I am getting back to this. I'm off the next week but will generate content to demonstrate multiple Graph algorithms and theories when I return in the week of October the 5th.

That would be wonderful, thanks!

@buddha314 Hey Brian, I'm just getting back to this area of work, and with CoVID-19 changing so much of my day-to-day, things have slowed down a lot! I've authored a few white papers w.r.t Graph Data Schema modeling with Graph TSL and I'll post them next week,

@buddha314 Hey Brian, I'm just getting back to this area of work, and with CoVID-19 changing so much of my day-to-day, things have slowed down a lot! I've authored a few white papers w.r.t Graph Data Schema modeling with Graph TSL and I'll post them next week,

I got busy with coding for two start-ups; I will get back to doing this.

Hey guys I finally have time to generate this type of content: https://github.com/InKnowWorks/RDF-Graph-and-HyperGraph
[HyperGraph]
cell struct RDFGraph
{
    List<CellId> RDFNodes;
    List<CellId> RDFHyperEdges;
}

[HyperGraph]
cell struct RDFNode
{
    string NodeId;
    List<CellId> OutgoingRDFHyperEdges;
    List<CellId> IncomingRDFHyperEdges;
    List<string> OutgoingPredicates;
    List<string> OutgoingObjects;
    List<string> IncomingPredicates;
    List<string> IncomingSubjects;
}

[HyperGraph]
cell struct RDFHyperEdge
{
    [HyperEdge]
    List<CellId> IncidentRDFNodes;
    string Predicate;
    string Object;
}


Cow: Watch qatartravelinfo.com

Cow requests the watch of the watch_keyword qatartravelinfo\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Dragonrage in Charcoal HQ

qatartravelinfo\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.


Align Callout on Reference page with changes on Documentation page

This PR brings the callout on \docs in line with the canges to \doc made in #1388.

Use https for "Visual Git Cheat Sheet" link
Divider between cheat sheets uses regular text

I tried to keep the change as minimal as possible, but that means that there are some differences between this file and the doc-file:

Single quotes instead of double quotes for HTML attributes
a tags instead of <%= link_to

Should these be unified? If so, in which direction?

Thanks, I think this looks nicer. It's probably worth unifying the syntactic bits, just because it will make it easier to adjust them together if we ever need to do so again in the future. I'd say that link_to is probably preferred.

Looks good, thanks!


Fixing async error swallowing

You can read about ES6 error swallowing here.
I've encountered this, while using the package. Runtime errors which aren't detected in webpack build, cause the server run to fail without displaying any errors.
This is caused by the promise of wait-for-file in server.js. Adding a catch cb easily fixes this, mine just prints the error stack to stderr.

Oh, so that's what they were talking about.
https://github.com/halt-hammerzeit/universal-webpack/issues/7

<EMAIL_ADDRESS>


turns verify tests back on

:+1: this looks like a test regression from https://github.com/chef/chef-dk/pull/920, yeah?

yes @btm. It passed on travis because the embedded gitbin path did not actually exist there and the unit tests in chef verify were off so it wasn't caught.

:+1:

👍
ROCK MORE
ROLL MORE
TEST MORE
BUILD BOT IS LOVING IT


utils updating

utils.py needs to be updated.
To Add:

Functions to be analyzed
Functions to perform analysis
functions to send alerts

How:

Define the email settings
Set a threshold for failed login attempts
Add a utility function to log a new security event
Could add function to manually log a failed login attempt for testing

Issue should be fixed now with new utils update.


glm2glm converter failed to record schedule information

Problem description
When using gridlabd to merge multiple glm files onto one single glm file, the load schedule information is not written onto the merged glm file.
Steps to reproduce

Set the following global file-save parameters:
#set glm_save_options=ORIGINAL
#set filesave_options=ALLINITIAL
Using the following command to convert onto one single glm file
gridlabd BU0001_glmfile_ts.glm -o merged.glm
The schedules of load_shape_A, load_shape_B,... are not written onto merged.glm

Expected behavior
The schedule information should be recorded in merged glm file.
System information

GridLAB-D version:
HiPAS GridLAB-D 4.2.1-200527 (develop) Linux
(using GridLAB-D docker)

Attachments
The glm model file and output file
BU0001.zip

A simple model (4-node system) is uploaded to demonstrate the issue.
IEEE-4node.zip

Please use the option #set glm_save_options=LEGACY to include the schedules.


add C++17 allocation functions

This has been implemented, although without yet switching to building as C++17 instead of C++14 by default.


How do I refresh the view of a remote directory's contents?

I created a new file on my remote system with 'cp' and when I went to edit my new file in VSCode, I couldn't get it to show up. I eventually quit and restarted VSCode which worked.
In other remote editing tools I've used (such as Remote System Explorer in Eclipse), you could right-click on a folder and choose "Refresh" from the context menu to pick up new files that were created remotely.
Can something like that be added to vscode-remote-fs? Or is it there and I'm not finding it?

How do you refresh the view of a local directory?

@liximomo
It makes sense to refresh the view of remote dir.
Why can't it sync bidirectionally?


return restriction site indices in cooler digest

add an option to return genome-wide and chromosome-wide genome indices in cooler digest. This allows to calculate the number of (undigested) restriction sites between two fragments

Done.


Add missing options

Some options are missing in the SDK.
May you add them @emilevictorportenart?
(Marker.io SDK) unknown param "silent" (need to upgrade?)
(Marker.io SDK) unknown param "source" (need to upgrade?)
(Marker.io SDK) unknown param "ssr" (need to upgrade?)

Hi @paavo, sorry for the long waiting time. These parameters are now all supported in version 0.11.0
Thanks!


MIA worst case score

Description
Please include a summary of the change, motivation and which issue is fixed. Any dependencies changes should also be included.
Fixes # (issue)
Type of change
Please check all relevant options.

[ ] Improvement (non-breaking)
[ ] Bug fix (non-breaking)
[x] New feature (non-breaking)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Testing
Please describe the tests that you ran to verify your changes. Consider listing any relevant details of your test configuration.

[ ] Test A
[ ] Test B

Test Configuration:

OS
Python version
ART version or commit number
TensorFlow / Keras / PyTorch / MXNet version

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Codecov Report

Merging #1709 (03d0abd) into dev_1.11.0 (697d745) will decrease coverage by 49.67%.
The diff coverage is 29.54%.

@@               Coverage Diff               @@
##           dev_1.11.0    #1709       +/-   ##
===============================================
- Coverage       88.09%   38.41%   -49.68%
===============================================
  Files             259      260        +1
  Lines           21349    21391       +42
  Branches         3789     3796        +7
===============================================
- Hits            18807     8217    -10590
- Misses           1598    12813    +11215
+ Partials          944      361      -583

Impacted Files
Coverage Δ

art/metrics/privacy/worst_case_mia_score.py
27.90% <27.90%> (ø)

art/metrics/privacy/__init__.py
100.00% <100.00%> (ø)

art/evaluations/evaluation.py
0.00% <0.00%> (-100.00%)
:arrow_down:

art/estimators/object_detection/utils.py
0.00% <0.00%> (-100.00%)
:arrow_down:

art/evaluations/security_curve/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

art/attacks/poisoning/perturbations/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...essing/expectation_over_transformation/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...rmation/natural_corruptions/contrast/tensorflow.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...formation/natural_corruptions/zoom_blur/pytorch.py
0.00% <0.00%> (-93.94%)
:arrow_down:

...mation/natural_corruptions/zoom_blur/tensorflow.py
0.00% <0.00%> (-93.55%)
:arrow_down:

... and 156 more


feat: support retry-after header in retry middleware

Adds :use_retry_after_header option to allow the client to align its retry strategy with server-side rate limiting

Let me know if there's any feedback you have on the proposed change - thanks!

🚀 💜


Sequencer: Process BatchPeriodEndMsg

Process BatchPeriodEndMsg and reorg the blocks not confirmed by schduler. And store the schduler signature in BatchPeriodEndMsg into the local block header

Messages all in one #338