Add in User class privilege features

In addition to being able to confirm a User, there needs to be a way to use the User's privy to access certain modes of information.

that could be done by give the user a certain interface with limited admin options

I've uploaded a User class.
With the exception of a couple of formatting issues, it should work at the moment.


Recommended production settings

This PR adds a page with cluster topology, clock synchronization, and file descriptor limit recommendations for production deployments.
This aims to fix #53 and is a start for #436.
HTTP version available here: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/7ccfa14b230bce596d6aaa73ccc78761ea1e015c/recommended-production-settings.html

This change is

@BramGruneir, as you'll see, the File Descriptor Limit section is very light right now. I need your help conveying the appropriate limits and context.
@bdarnell, are there other limits or recommendations we should add to this page?

Review status: 0 of 3 files reviewed at latest revision, 2 unresolved discussions.

recommended-production-settings.md, line 13 [r1] (raw file):

## Cluster Topology

Put each node on a different machine. Since CockroachDB [replicates](configure-replication-zones.html) across nodes, placing more than one node on a single machine increases the risk of data unavailability when a machine fails.

This is true, but simplistic. "Put each node on a different machine" will sound very obvious to most of our target audience. Try this instead: "Run one node per machine. If a machine has multiple disks or SSDs, it's better to run one node with multiple store flags instead of one node per disk, because this informs CockroachDB about the relationship between the stores and ensures that data will be replicated across different machines instead of being assigned to different disks of the same machine."

recommended-production-settings.md, line 21 [r1] (raw file):

## File Descriptor Limit (Max Open Files)

For each CockroachDB node, the max file descriptor limit must be at least XXX. If the limit is below this threshold, the node will fail.

The minimum is 512 (the node will fail to start if this minimum is not available), but the recommendation is at least 10000. (it's actually 5000 + 5000 * number of stores per node).

Comments from Reviewable

Would like to merge this now to have the page in place for this week's release notes. I'll open a separate PR with explicit instructions for increasing the file descriptor limit per OS.

Review status: 0 of 3 files reviewed at latest revision, 2 unresolved discussions.

Comments from Reviewable

LGTM


[Question] - Receipts and Auto-renewing Subscriptions

Version of react-native-iap
4.4.9
Version of react-native
0.62.2
Platforms you faced the error (IOS or Android or both?)
iOS
Expected behavior (using TestFlight)

When a user subscribes to a subscription I save the receipt in my database.
When I start up my app, I grab the receipt from the database, validate it and check if the subscription date is still valid.

This all works even when the subscription auto-renews.  When I pull the receipt from my database and validate it, the new subscription data is there and it all looks great!  It's all working with the original receipt from the original purchase.
Is it supposed to work this way?  I thought each renewal of a subscription had a new receipt.
It's working great in TestFlight, but I want to make sure this is how it works in production as well.  I just worry that in production things will stop working when the subscription auto-renews.
Actual behavior
(See above)
Tested environment (Emulator? Real Device?)
Real device
Steps to reproduce the behavior
(see  above)

I found out the answer to this from Apple.  And what I described above is working that way by design and should work fine in production.  They did caution me against using client validation though, and that longer term it's more secure to move receipt validation to your secure server. That's on the backlog, so I should be good.

Hey @the-dut could you please help me with the Auto Renewable subscriptions?
Issue: My Transactions are not getting finished. i got alert box "Purchase completed successfully", but when i restart app and go to Subscription Page, purchaseUpdatedListener again getting called. I am receiving receipt again.
Please man, will appreciate it, been stuck for over 10 days :(
Apple documentation are not clear
Here is my code
import { View, Text, Button, Alert } from 'react-native';
import * as RNIap from 'react-native-iap';
import { get } from 'lodash';

let purchaseUpdateSubscription;
let purchaseErrorSubscription;
export default class PremiumMembership extends React.Component {

  constructor(props) {
    super(props);
    this.state = {
      subscription: {},
      receiept: false
    }
  }

  componentDidMount() {
    this.getSubscriptions();

    purchaseUpdateSubscription = RNIap.purchaseUpdatedListener(
      async purchase => {
        const receipt = purchase.transactionReceipt;
        if (receipt) {
          console.log('receipt', receipt);
          try {
            if (Platform.OS === 'ios') {
              const finishTransactionIOS = await RNIap.finishTransactionIOS(
                purchase.transactionId,
              );
              console.log("FinishTransactionIOS: ", finishTransactionIOS)
              Alert.alert('finishTransactionIOS', finishTransactionIOS);
            }
          } catch (ackErr) {
            Alert.alert('ackErr', ackErr);
          }
          this.setState({receipt});
        }
      },
    );

    purchaseErrorSubscription = RNIap.purchaseErrorListener(error => {
      console.log('purchaseErrorListener', error);
      Alert.alert('purchaseErrorSubscription error:', JSON.stringify(error));
    });
  }

  componentWillUnmount() {
    if (purchaseUpdateSubscription) {
      purchaseUpdateSubscription.remove();
      purchaseUpdateSubscription = null;
    }
    if (purchaseErrorSubscription) {
      purchaseErrorSubscription.remove();
      purchaseErrorSubscription = null;
    }
    RNIap.endConnection();
  }

  async getSubscriptions() {
    try {
      await RNIap.initConnection();
      const subscriptions = await RNIap.getSubscriptions(['test_subscription']);
      console.log("Subscription: ", subscriptions);
      this.setState({subscription: subscriptions[0]});
    } catch (error) {
      console.log("Unable to get Subscriptions...", error);
    }
  }

  async onSubscribe() {
    try {
      await RNIap.requestSubscription('test_subscription', true);
    } catch (error) {
      console.log("Unable to subscribe...", error);
    }
  }

  render() {
    return (
      <View style={{flex: 1, justifyContent: 'center', alignItems: 'center'}}>
        <Text>Subscription Screen</Text>
        <Text>Subscription Name: {get(this.state,'subscription.title', null)}</Text>
        <Text>Price: {get(this.state, 'subscription.localizedPrice', null)}</Text>
        <Text>Receiept: {get(this.state, 'receipt', false)  ? 'true' : 'false'}</Text>
        <Button title={'Subscribe'} onPress={() => this.onSubscribe()}/>
      </View>
    )
  }
}
`


[FLINK-10662][network] Refactor the ChannelSelector interface for single selected channel

What is the purpose of the change
In ChannelSelector#selectChannels, it would return an array for selected channels. But considering specific implementations, only BroadcastPartitioner would select all the channels, and other implementations will select one channel.
So we can simple this interface to return single channel index for benefiting performance, and specialize the BroadcastPartitioner in a more efficient way.
Brief change log

Refactor the selectChannel method in ChannelSelector interface
Adjust the related processes in RecordWriter
Fix the related tests because of interface change

Verifying this change
This change is already covered by existing tests, such as OutputEmitterTest and RecordWriterTest.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (yes)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

cc @pnowojski :)

Thanks for your reviews! @pnowojski
I would consider your above suggestions and double check the travis failure.


add readonly mount option to entitlement volume

Customer is facing below issue
error running subprocess: remounting "/var/tmp/buildah1281177773/mnt/rootfs/etc/pki/entitlement" in mount namespace with flags 0x0 instead of 0x1: permission denied
by default rw permissions are set when passing the directory as volume without specifying the permissions
however the entitelement secret is mounted as readonly and hence the issue
fixing this by passing the volume mount as readonly on buildah script
Reproducer
---
apiVersion: v1
kind: Secret
metadata:
  name: etc-pki-entitlement
type: Opaque
data:
  entitlement.pem: ZHVtbXkgY2VydGlmaWNhdGUgZGF0YQ==
  entitlement-key.pem: ZHVtbXkga2V5IGRhdGE=

---
apiVersion: v1
kind: ConfigMap
metadata:
  name: dockerfile-config
data:
  Dockerfile: |
    FROM registry.access.redhat.com/ubi9/ubi-minimal:latest

    RUN microdnf \
        --enablerepo="ubi-9-appstream-rpms" \
        --enablerepo="rhel-9-for-x86_64-baseos-rpms" \
        install -y python39

---
apiVersion: tekton.dev/v1beta1
kind: TaskRun
metadata:
  name: entitled-build-test
spec:
  taskRef:
    resolver: cluster
    params:
    - name: kind
      value: task
    - name: name
      value: buildah
    - name: namespace
      value: openshift-pipelines
  params:
    - name: IMAGE
      value: "example-image:latest"
    - name: DOCKERFILE
      value: "./Dockerfile"
    - name: CONTEXT
      value: "."
    - name: FORMAT
      value: "docker"
    - name: STORAGE_DRIVER
      value: "vfs"
    - name: ADDITIONAL_CREDENTIAL_MIXING
      value: "true"
    - name: REGISTRY_INSECURE
      value: "false"
  workspaces:
    - name: source
      configMap:
        name: dockerfile-config
    - name: dockerconfig
      secret:
        secretName: quay-secret
    - name: rhel-entitlement
      secret:
        secretName: etc-pki-entitlement
        items:
          - key: entitlement.pem
            path: etc/pki/entitlement/entitlement.pem
          - key: entitlement-key.pem
            path: etc/pki/entitlement/entitlement-key.pem
            ```

/retest-required

/retest-required

/test osp-114-ocp-416-e2e


couple of things I am puzziling through

Here is a the command I am running:
sudo sdm --customize --network:"netman=nm|wifissid=Netgear96|wifipassword=xxxx|wificountry=US|noipv6" --L10n --restart --disable piwiz --regen-ssh-host-keys --user trg --password-user xxxx --password-same y --autologin --xmb 2048 --plugin copyfile:"filelist=/home/alan/Documents/raspios/filestore/trg/filelist.txt" 2023-05-03-raspios-bullseye-armhf-lite.img
two things are happening

the wlan0 and dhcpcd do not seem to be setup so when I first log in, the pi zero has no network access.
the other is autologin does not seem to be working and there is also a user labeled pi on the system after it boots up as well as the trg user.

I am pretty sure this has got to be something I am misunderstanding about the sdm so I added the command above in hopes you can educate me.

In your command line you have netman=nm. This means use Network Manager instead of dhcpcd. So, dhcpcd will not be configured. Since you're using a Bullseye V11 (I presume) IMG, replace netman=nm with netman=dhcpcd and see what happens. This should bring your network online assuming your wifi ssid and password are correct.
As far as the user pi being there, that is correct. --user creates a new user. If you want to replace the user pi with user trg, you can use --rename-pi. Note that the user pi doesn't have a password, so it can't be logged into.
Personally, I create my new user with a userid and gid that I use across all my Linux systems so that files on NFS network shares have correct ownership. (This is a very poor man's network directory!)
Every one of my systems has a pi user on it, but with no password, so the account can't be logged into.

Just realized that I neglected to address the autologin question.
I'll have a look at that tomorrow.

Just realized that I neglected to address the autologin question.
I'll have a look at that tomorrow.

Autologin was not handled correctly in this case. Will fix in the next update.

V9.1.1 is released and the autologin issue with CLI is corrected. The NetworkManager support has been improved, but I will admit that most of the testing I did on it was with bookworm. That said, I can't think of a reason that it won't work for you.
HOWEVER, users are handled differently now. For details please review https://github.com/gitbls/sdm/blob/master/Docs/Plugins.md#user
Please test and verify that your issues are corrected on V9.1.1, close this issue if they are, or update with V9.1.1-based details.

Closing issue since no further activity. Please re-open if you're still having a problem with this.


How do you mount sub-containers volumes from a CI server container ?

Hi,
I an using docker for my dev environment: I have a dev image and I mount my source files as a volume. It works perfectly and it's awesome ;)
But then I wanted to do the same on my continuous integration server (gitlab ci) and I carefully read @jpetazzo https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/ but the solution of bind-mounting docker's unix socket makes impossible mounting volumes from a container.
So basically my question is how would you solve this (given I am in a docker ci server/runner): I need to run the following command from a container (a gitlab runner).

$ git clone ... my-sources && cd my-sources
$ docker run my-dev-image -v $PWD:$PWD -w $PWD gcc main.c

Because obviously, the volume is taken from docker's "native" host and not the current container.
Related: http://stackoverflow.com/questions/31381322/docker-in-docker-cannot-mount-volume
Thanks

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see CONTRIBUTING.md.
You don't have to include this information if this is a feature request
(This is an automated, informational response)

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Don't use volumes-from. Instead use "named" volumes for important data that you need to share.
Closing as this isn't really an issue.


Use elasticsearch-py to communicate with elasticsearch

The native client provides some benefits for us and requests does not, so let's use elasticsearch.

Also, the current implementation supports only one elasticsearch host for establishing connections. In our architecture there are one or more (1 or 3) elasticsearch endpoints which are for services and they on their own handle re-connections. It is what elasticsearch-py provides out of the box.


Update use of session.resolveProxy() with a Promise instead of passing a callback (for Electron 9 PR)

Requirements for Contributing a Bug Fix (from template, click to expand):

Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
The pull request must only fix an existing bug. To contribute other changes, you must use a different template. You can see all templates at https://github.com/atom/.github/tree/master/.github/PULL_REQUEST_TEMPLATE.
The pull request must update the test suite to demonstrate the changed functionality. For guidance, please see https://flight-manual.atom.io/hacking-atom/sections/writing-specs/.
After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see https://github.com/atom/.github/tree/master/CONTRIBUTING.md#pull-requests.

Identify the Bug

https://github.com/atom/atom/pull/21926#issuecomment-776195670
For the Electron 9 PR: https://github.com/atom/atom/pull/21777
Description of the Change

Don't pass a callback to session.resolveProxy(), move the "callback" code to after an await instead.
Why? This Electron API call returns a Promise now, and as of Electron 7, it doesn't run callbacks passed to it.
For documentation of this change, see: https://github.com/electron/electron/blob/v9.4.3/docs/api/modernization/promisification.md
Alternate Designs

None.
Possible Drawbacks

None.
Verification Process

CI passes when this change is done on master branch: CI run. (It doesn't cause any new failures on the Electron 9 PR branch, either: CI link.)
(Using this Electron API call with Promises was optionally supported as of Electron 6, so master branch works with this change. It's only mandatory to use Promises starting in Electron 7 or newer.)
Release Notes

N/A

I'm closing this PR. @sadick254 has added this to the Electron 9 PR as commit https://github.com/atom/atom/pull/21777/commits/684b690a1d227b5904e40e1e99ca7fd5d687e20c.
(Note for @aminya: async/await was used.)


Support graceful stop

Currently, mvnd --stop will stop all background tasks.
We should, like ssh -O option's behavior:

use mvnd --stop as  "request the master to stop accepting further request"
use mvnd --exit as "request the master and tasks to exit"

There's no master process controlling all daemons but mvnd uses a file registry.
What could be doable is to send a graceful stop request to all daemons. This would require a new Message to be sent and received.  If you're fancy working on a PR I can give you some pointers...


Switch KH to Input registers as a test

See: #505

I'm probably not going to merge this -- I'd rather do something intelligent using the manager version if we do get confirmation that input registers are gone for good on the KH.

@canton7 agree, hold off until I hear back to from Fox, if they fix it in the next version this patch isn't needed. I will update you.

Apparently Fox are working on a fix.

@williamjeccles give that a try, see if it re-enables min/max soc, max charge/discharge current and work mode

@canton7 appears to not work, all my values are unavailable and I see the following in the logs:
This error originated from a custom integration.
Logger: custom_components.foxess_modbus.modbus_controller
Source: custom_components/foxess_modbus/modbus_controller.py:221
Integration: FoxESS - Modbus (documentation, issues)
First occurred: 17:42:58 (1 occurrences)
Last logged: 17:42:58
tcp://<IP_ADDRESS>:502 247 - 5 failed poll attempts: now not connected. Last error: Error reading registers. Type: RegisterType.HOLDING; start: 41000; count: 8; slave: 247 from tcp://<IP_ADDRESS>:502: Exception Response(131, 3, IllegalAddress)

Are you comfortable using modpoll? If so, can you try reading register 41000 on its own, and as part of a block of registers?
We've found that some holding registers on the H3 can only be read 1-by-1, so maybe that's what's happening here.

@canton7 can you confirm the modpoll command?
I'm using:
`c:\Users\willi\Downloads>modpoll.exe -m tcp -p 502 -a 247 -r 41000 <IP_ADDRESS>
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.
Protocol configuration: MODBUS/TCP, FC3
Slave configuration...: address = 247, start reference = 41000, count = 1
Communication.........: <IP_ADDRESS>, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, output (holding) register table
Can't reach server/slave! Check TCP/IP and firewall settings.`

That suggests the ipsaddress is wrong, or your modbus adapter is offline? Or maybe HA is connected to it, and is tying it up?

@canton7 any better?
c:\Users\willi\Downloads>modpoll.exe -m tcp -p 502 -a 247 -r 41000 <IP_ADDRESS>
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.
Protocol configuration: MODBUS/TCP, FC3
Slave configuration...: address = 247, start reference = 41000, count = 1
Communication.........: <IP_ADDRESS>, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, output (holding) register table
-- Polling slave... (Ctrl-C to stop)
Illegal Data Address exception response!
-- Polling slave... (Ctrl-C to stop)
Illegal Data Address exception response!
-- Polling slave... (Ctrl-C to stop)
Illegal Data Address exception response!
-- Polling slave... (Ctrl-C to stop)
Illegal Data Address exception response!
-- Polling slave... (Ctrl-C to stop)
Illegal Data Address exception response!
-- Polling slave... (Ctrl-C to stop)
Illegal Data Address exception response!
-- Polling slave... (Ctrl-C to stop)

That looks more promising...
Can you try with -0 -1 -t 3 and -0 -1 -t 4? If either of those works, add in -c 2, see if it still works.

@canton7 Results:
`c:\Users\willi\Downloads>modpoll.exe -m tcp -p 502 -a 247 -0 -1 -t 3 -r 41000 <IP_ADDRESS>
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.
Protocol configuration: MODBUS/TCP, FC4
Slave configuration...: address = 247, start reference = 41000 (PDU), count = 1
Communication.........: <IP_ADDRESS>, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table
-- Polling slave...
[41000]: 0`
`c:\Users\willi\Downloads>modpoll.exe -m tcp -p 502 -a 247 -0 -1 -t 4 -r 41000 <IP_ADDRESS>
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.
Protocol configuration: MODBUS/TCP, FC3
Slave configuration...: address = 247, start reference = 41000 (PDU), count = 1
Communication.........: <IP_ADDRESS>, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, output (holding) register table
-- Polling slave...
[41000]: 0`
`c:\Users\willi\Downloads>modpoll.exe -m tcp -p 502 -a 247 -0 -1 -t 4 -c2 -r 41000 <IP_ADDRESS>
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.
Protocol configuration: MODBUS/TCP, FC3
Slave configuration...: address = 247, start reference = 41000 (PDU), count = 2
Communication.........: <IP_ADDRESS>, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, output (holding) register table
-- Polling slave...
Illegal Data Address exception response!`

Interesting that it's available to read as an input register. Can you try with -t 3 -c 2?
It lokos like we can read those registers 1-by-1 as holding registers, but the USR-W610 will really struggle to do that many individual polls.

Actually, mind trying to read 41007 with -c 2, and both -t 3 and -t 4? The problem might be that registers 41001 (which is TBD in their spec) is unreadable.

@canton7
c:\Users\willi\Downloads>modpoll.exe -m tcp -p 502 -a 247 -0 -1 -t 3 -c 2 -r 41007 <IP_ADDRESS>
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.
Protocol configuration: MODBUS/TCP, FC4
Slave configuration...: address = 247, start reference = 41007 (PDU), count = 2
Communication.........: <IP_ADDRESS>, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table
-- Polling slave...
Invalid frame error!
c:\Users\willi\Downloads>modpoll.exe -m tcp -p 502 -a 247 -0 -1 -t 4 -c 2 -r 41007 <IP_ADDRESS>
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.
Protocol configuration: MODBUS/TCP, FC3
Slave configuration...: address = 247, start reference = 41007 (PDU), count = 2
Communication.........: <IP_ADDRESS>, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, output (holding) register table
-- Polling slave...
Illegal Data Address exception response!

So, looks like they can be read as input or holding registers, but they have to be read 1-by-1.
It's probably the same as the H3 in that respect. Have a try with that latest update, see if that works.

@canton7 bingo, dino dna

My inverter stopped responding 2 days ago
./modpoll  -m tcp -p 502 -a 247 -t 3 -0 -1 -c 16 -r 11000  <IP_ADDRESS>
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: MODBUS/TCP, FC4
Slave configuration...: address = 247, start reference = 11000 (PDU), count = 16
Communication.........: <IP_ADDRESS>, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave...
Invalid frame error!

It works with 3100 only now:
./modpoll  -m tcp -p 502 -a 247 -t 3 -0 -1 -c 16 -r 31000  <IP_ADDRESS>
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: MODBUS/TCP, FC4
Slave configuration...: address = 247, start reference = 31000 (PDU), count = 16
Communication.........: <IP_ADDRESS>, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave...
[31000]: 1
[31001]: 0
[31002]: 0
[31003]: 0
[31004]: 0
[31005]: 0
[31006]: 0
[31007]: 0
[31008]: 0
[31009]: 0
[31010]: 0
[31011]: 0
[31012]: 0
[31013]: 0
[31014]: 0
[31015]: 0

Released in the beta v1.10.0b3.
(It'll be a little while before I can get a proper release out, as we're in the middle of figuring out force charge/discharge).


WAN Load Balancing doesn't work

After rolling out to half a dozen sites, each one complained about the JSON parameters not being supported.
This appears to be firmware specific:
  "load-balance": {
    "group": {
      "wan_failover": {
        "flush-on-active": "enable",
        "lb-local-metric-change": "disable",
        "lb-local": "disable",
        "interface": {
          "eth2": {
            "route-test": { "type": { "ping": { "target": "<IP_ADDRESS>" }, "initial-delay": "30", "interval": "30"} },
            "count": { "failure": "3", "success": "3" }, "weight": "{{ eth2_percent }}"
          },
          "eth3": {
            "route-test": { "type": { "ping": { "target": "<IP_ADDRESS>" }, "initial-delay": "30", "interval": "30"} },
            "count": { "failure": "3", "success": "3" }, "weight": "{{ eth3_percent }}"
          }
        },
        "sticky": { "dest-addr": "enable", "dest-port": "enable", "source-addr": "disable" }
      }
    }
  },

Suggest removing this block entirely.

Deploying now works, no issues.


fix(schema): support softbreaks in lists - I187

Issue #187
Support for softbreaks in a list_item
Changes

Allow for list_items to be a paragraph, not just text or links
Allow softbreaks in a list

Flags

N/A

Related Issues

N/A

The current state of this code run in TSv2 still results in a parse error.


Fixing compilation with nginx>=1.9.1

@msva Yes, like that. But you'd better ensure empty lines around your #if, #else, and #endif for aesthetic reasons.

here it is ;)

@msva I think you need to short-circuit the "tv" variable declaration for nginx 1.9.1+ too. It is never used in that code path.
Also, again: you'd better ensure empty lines around your #if, #else, and #endif for aesthetic reasons.
@PiotrSikora ?

will it be okay in that way?

Although, I'd like to put declaration even inside if (u->state && u->state->response_sec) {

@msva No, putting the variable declaration inside the if block also violates the nginx coding style (well, I didn't invent that style).

Uhm.. But according to that: http://wiki.nginx.org/CodingStyle (although, there is struct, but not plain variables) it is okay... But ok, I'll think about it ;)

Uhm... Did I misunderstood you about what exactly violating style, or do NginX team violates style theyself?
http://hg.nginx.org/nginx/file/6893a1007a7c/src/http/ngx_http_request.c#l204

@msva Regarding the empty lines around macro directives, either way is fine. That's why I said it was for aesthetic reasons. For example,
http://hg.nginx.org/nginx/file/6893a1007a7c/src/http/ngx_http_request.c#l1833

So, is it okay now? :)

@msva Looking good to me now :)

@PiotrSikora ping? :(

@msva No worries. I'll look into this.

@msva I'm getting the following compilation error on Linux (Fedora 22, gcc 5.1.1) using your branch:
/home/agentzh/git/postgres-nginx-module/src/ngx_postgres_util.c: In function ‘ngx_postgres_upstream_finalize_request’:
/home/agentzh/git/postgres-nginx-module/src/ngx_postgres_util.c:71:33: error: assignment makes integer from pointer without a cast [-Werror=int-conversion]
         u->state->response_time = ngx_timeofday()->msec - u->state->response_time;
                                 ^
cc1: all warnings being treated as errors

Maybe you should use ngx_current_msec instead of ngx_timeofday()->msec here?

@msva Never mind, I've committed a slightly modified version of your patch to master. Thanks for your contribution!


Display exception notes when raising ClickException

Since 3.11 Python supports adding notes on exceptions. Basically this is completion of the exception message, and it can be useful to add context.
Notes are currently not displayed when ClickException are raised:
import click

@click.command()
def foobar():
    exc = click.ClickException("foo")
    exc.add_note("bar")
    raise exc

if __name__ == '__main__':
    foobar()

$ python foobar.py
Error: foo

I suggest to display the notes in addition to the main message.
What do you think?

What would be in these notes that wouldn't go in the message directly? The example in the docs is for errors raised elsewhere and caught, but that can also be done with raise New("") from old. And I don't think these errors are expected to be caught and modified either way.

What would be in these notes that wouldn't go in the message directly?

For sure this would not bring anything click can't already do. This would just be for convenience.
After having used add_note a bit, I would have naively expected click exception display to behave a bit like uncatched python exception display, i.e. to display the notes.
For the record, the situations where I find it useful is to re-raise an exception with more context:
try:
    something_dangerous()
except ClickException as exc:
    exc.add_note("additional context")
    raise exc


Front end should add eslint  and husky

Eslint + husky should be added to ensure the quality workflow of GIT code submission.

Fixed by: https://github.com/casdoor/casdoor/pull/875


Swarmkit cannot be builded with golang 1.6.3

Error
michel@homebox ~/go/src/github.com/docker/swarmkit $ make binaries
🐳 bin/swarmd
# github.com/docker/swarmkit/vendor/github.com/docker/docker/client/transport
vendor/github.com/docker/docker/client/transport/tlsconfig_clone.go:10: c.Clone undefined (type *tls.Config has no field or method Clone)
# github.com/docker/swarmkit/api
api/dispatcher.pb.go:1574: p.cluster undefined (type *raftProxyDispatcherServer has no field or method cluster)
api/dispatcher.pb.go:1581: p.connSelector.Conn undefined (type raftselector.ConnProvider has no field or method Conn)
api/dispatcher.pb.go:1593: p.connSelector.Reset undefined (type raftselector.ConnProvider has no field or method Reset)
Makefile:89: recipe for target 'bin/swarmd' failed
make: *** [bin/swarmd] Error 2

Go Version
michel@homebox ~/go/src/github.com/docker/swarmkit $ go version
go version go1.6.3 linux/amd64

I believe this was recently fixed in the transport package, and revendoring it will fix compilation with Go 1.6.x.

@aaronlehmann how do that revendoring?

got it.  this is here:
https://github.com/docker/docker/commit/128cefc3bdfc458ac84ae6602d6484c79f479795

@aaronlehmann i think here is bug. the vendor is not update for the fix on upstream docker/docker

Clone bug is fixed with revendor the docker/docker/client/transport .
now here is another error:
# github.com/docker/swarmkit/api
api/dispatcher.pb.go:1574: p.cluster undefined (type *raftProxyDispatcherServer has no field or method cluster)
api/dispatcher.pb.go:1581: p.connSelector.Conn undefined (type raftselector.ConnProvider has no field or method Conn)
api/dispatcher.pb.go:1593: p.connSelector.Reset undefined (type raftselector.ConnProvider has no field or method Reset)
make: *** [bin/swarmd] Error 2

i guess the protobuf's version is not corrent.

in macos,  brew upgrade --devel protobuf to install 3.0 beta protobuf

let me recap the action to resolve the problem:

revendor the transport package to swarmkit repo

gvt fetch github.com/docker/docker/client/transport

upgrade macos protobuf to 3.0

brew upgrade --devel protobuf

make generate to rebuild the proto file

make generate

bingo!

make all

When https://github.com/docker/docker/pull/26436 is merged, we'll revendor the relevant packages and this should no longer be an issue.
cc @stevvooe

Thanks @aaronlehmann and @xiaods
The issue was split into two parts. The first part was the missing revendoring.
The second part was the protobuf which was still version 2.5. It might make sense to add this package to the build requirements list?

@xiaods

brew upgrade --devel protobuf
Actually, proto 3 is now stable so you don't need the development version anymore. brew upgrade protobuf (without --devel) should install 3.0.2 now.

@michelvocks

The second part was the protobuf which was still version 2.5. It might make sense to add this package to the build requirements list?

Yes it definitely makes sense - I think we shouldn't put OS specific details (e.g. brew install etc) but rather just say that it requires protobuf 3.x and link to the protobuf instructions.


delete messages

Great library. Thanks. How do we delete messages?

It's not possible just yet, though feel free to help implement that :)

#7


SUPPORTED_PLATFORMS not include macosx, watchsimulator and appletvsimulator

Hello,
I'm trying to make a multi-platform framework with Alamofire from cocoapods, but when I compile I get several alerts and the library is not imported.

Target 'Alamofire' of project 'Pods' was rejected as an implicit dependency for 'Alamofire.framework' because it doesn't contain platform 'macosx' in its SUPPORTED_PLATFORMS 'iphonesimulator, iphoneos'
Target 'Alamofire' of project 'Pods' was rejected as an implicit dependency for 'Alamofire.framework' because it doesn't contain platform 'watchsimulator' in its SUPPORTED_PLATFORMS 'iphonesimulator, iphoneos'
Target 'Alamofire' of project 'Pods' was rejected as an implicit dependency for 'Alamofire.framework' because it doesn't contain platform 'appletvsimulator' in its SUPPORTED_PLATFORMS 'iphonesimulator, iphoneos'

Alamofire does not support multi-platform frameworks to allow it to work seamlessly with CocoaPods AND Carthage with the same Xcode project. If you are attempting to make a new podspec that attempts to create a multi-platform framework and are having issues, please open an issue with the CocoaPods project. You'll receive much better assistance there.

Thanks a lot for the info


Query on preprocessing steps

Hi,
Its me again :)
I have been checking out the data pre-processing steps and have following queries:

During training, I can see that batch sampler DataBaseSamplerV2 removes ground truth objects with less than 5 points. And this removal is done only for the objects that are copy-pasted from other frames. But the objects in the current frame are still not removed if they have less than 5 points. Not sure if I am missing something in the data pre-processing steps?
After copy-pasting ground truth objects point-cloud, I can see that the original points in that space are not removed remove_points_after_sample=False. Won't this impact training, or is it expected that the network should still be able to identify the points that belong to the objects and ignore the ones from background even though they are present in the same space very nearby?

I would highly appreciate if you could clarify these please.
Thank You.
Best Regards,
Anuj

For 1 this is expected because we are required to detect all objects with at least one lidar point. The filtering for gt augmentation is to ensure we get a high quality object to paste into other frame. Like, if it is a single point. Pasting it into a new frame may not be realistic.
For 2, your reasoning is right. I never time this parameter and I guess it doesn't matter too much as in visualization there is not much background points higher than the surface in the roads.

Thanks for the quick reply. Indeed, it makes sense to augment with only good boxes :+1:


Methods and Lambda Expressions

Issue tracking new topic at https://github.com/dotnet/docs/blob/master/docs/csharp/methods-lambda-expressions.md

@tdykstra
It looks like this topic has been hanging for long time?
Could I take this work and propose to create content for this lambda expressions?
If I'm assigned for this, do you want to have a lambda expression technical guidance with sample or to use a leaning/tutorial model?

@BillWagner See proposal from @eriawan

@eriawan It would be fantastic if you would take this on.
I'd like to see you build a sample that shows a design idiom where lambda expressions provide a good solution. That could be something related to LINQ, or a different functional algorithm.
I often find good samples in the F# Guide: https://docs.microsoft.com/en-us/dotnet/articles/fsharp/language-reference/functions/ These enable me to contrast the syntax for C# and F#.
Finally, now that lambdas have been supported by C# for more than a decade, I think it's much more important to concentrate on the idioms and algorithms supported by lambda expressions than it is to explain that lambdas are implemented as compiler generated anonymous delegates. The later should be stated, but not the focus.

@BillWagner
Ok, thanks for your reply!
Could you elaborate on this statement:

I can't assign this to you, as your GitHub ID is not a member of the team. I've assigned it to me, just so on one else works on it.

I admit I'm not a full time MS employee, but as far as I know this repo should be open to anyone that wish to contribute, and also to submit a PR, and to me it's closed since I'm not a part of the team. Please correct me if I'm wrong.
That being said, then how to contribute to this repo? Do I have to be part of this team repo? If I have to, how do I apply to be member of this repo's team?

@eriawan We do accept pull requests from anyone. (I see you're working with @cartermp on some F# content). This content would work the same: start writing, open a PR, and we'll review. When ready, we'll merge it in.
However, GitHub only supports assigning issues to people that have direct commit access.
So, as a workaround, when someone says the will work on something, we assign it to one of the maintainers so we don't have multiple people working on the same content. It's not the best solution, but it works. (And we've asked for new features.)

@BillWagner
Ok, I understand it now. 👍
I was thinking that in order to have contributions, I have to be member of the team based on your previous comments.
I think I'll also submit comments on this C# lambda as well 😄
Thanks for clearing my confusion, @BillWagner !

@rpetrusha Are you working on this at the moment?

@BillWagner No. I worked on the revision to the lambda expressions overview. At the moment, I'm working on an inheritance tutorial.

@rpetrusha Thanks. I was concerned that you and @eriawan might be working on the same content. Glad I was wrong.

I think to close this one we should just remove this topic: https://github.com/dotnet/docs/blob/master/docs/csharp/methods-lambda-expressions.md
We have a topic on methods and lambda expressions.


Add python async example for hellostreamingworld using generator

Following of the issue #24603 .
The problem was a missing example not a bug in the gRPC implementation, so here is an example of async Unary Stream call using the already present hellostreamingworld.proto definition.
It uses a message async generator out of the object to provide an example for that kind of usage.
@yashykt

@lidizheng this example looks great to me!  definately something I would have liked to have when I was exploring the examples for the first time.

Just waiting for a review. Anyone available?

@mickours The sanity checks can be fixed by running:
tools/distrib/yapf_code.sh
tools/distrib/isort_code.sh

You can also check for pylint errors locally: tools/distrib/pylint_code.sh

I've apply the auto-format and lint scripts. Chould be OK now.

Known failure: https://github.com/grpc/grpc/issues/28483


Simplify building process for p256k1.

Note: current building process affects all customers of p256k1. The proposal is to move a part of building.rs which generates bindings to as a separate utility project (Rust script). The script should

[x] clone the latest secp256k1 C library,
[ ] apply patches,

[ ] remove static from C source code for some selected functions.
[ ] add external include to a header file with prefixes.

[x] generate bindings.

We will commit the patched C source code and generated bindings to Git.
We can split the issue into two tasks:
### Tasks
- [ ] https://github.com/Trust-Machines/p256k1/issues/43
- [ ] https://github.com/Trust-Machines/p256k1/issues/44
- [ ] https://github.com/Trust-Machines/p256k1/issues/46

The first task should fix https://github.com/Trust-Machines/core-eng/issues/188

@xoloki should we create another repo for utility tools to get rid of mono repo?

@xoloki should we create another repo for utility tools to get rid of mono repo?

It's fine for now, let's focus on other work.  We can do this later once we're not in time crunch.

@xoloki should we create another repo for utility tools to get rid of mono repo?

It's fine for now, let's focus on other work. We can do this later once we're not in time crunch.

Sure, but feel free to shoot ideas into comments.


Debuggers not enabled under current context keys should not provide debug configurations

Testing https://github.com/microsoft/vscode/issues/133146

Have a debugger disabled via its when clause
In a folder without a launch.json, run "create a launch.json file"
The disabled debugger can still provide configurations

While there might be some edge use cases for this, I think it should be disabled.

I think duplicate of https://github.com/microsoft/vscode/issues/133957


Full Update of a resource instance

$ curl -i -v http://malmo.lizenn.net:8080/collections/user/Merle
...
HTTP/1.1 200 OK
...
category: user; scheme="http://example.org/occi/test#"; class="kind"
x-occi-attribute: blog.user.name="Merle"
x-occi-attribute<EMAIL_ADDRESS>x-occi-attribute: occi.core.id=87254351
$ curl -i -v http://malmo.lizenn.net:8080/collections/user/Merle -X PUT -H 'Content-Type: text/occi' -H 'X-OCCI-Attribute: occi.core.title="Merle"'
...
HTTP/1.1 409 Conflict
...
Why 409 is returned?

PUT verb "creates a new or replace an existing".
My interpretation is that entity id must be the same, which is not the case in your request:
1st one: occi.core.id=87254351
2nd one: (empty)
The problem in the spec is an entity id is not clearly defined: it may be the URL and/or the occi.core.id attribute.
Due to the ambiguity of the spec, I would say my implementation is correct but the spec should be clearer.
See also:
https://www.ogf.org/pipermail/occi-wg/2016-April/003743.html


dart2js: switch to the new RTI by default

We need to flip the default. Implementation is practically done, but we need to triage and fix a few test failures before we can enable it by default.

CL to flip it and add to CHANGELOG is ready,  but we are fixing a few remaining test failures:

missing type information on native types that are folded into the parent chain
missing subtype information on some bounds

@fishythefish is currently looking.

@fishythefish fixed all the remaining issues, and the flag was flipped by default as of d735f1f12d1faf45fcee599f1541f87bfbd6b893
woohoo!


Update domain name references and shorten page titles

This PR:

updates domain name references to https://technical-architecture.service.justice.gov.uk from https://ministryofjustice.github.io/technical-architecture to support a custom domain in GitHub Pages
shortens page titles from "Technical Architecture at the Ministry of Justice" to "Technical Architecture" for improved readability

@jennyd I think you're right - let's review how the Security Guidance does their crest and name in another PR 🎊


Persist react-native-router-flux scene

On android, when I schedule background job with alwaysRunning: true, fold app into background and press on notification tile it opens app on initial scene instead of last active scene. Not sure if it's an issue or I'm doing something wrong

That is part of the implementation. I just fire up the app using the start intent. There's probably a way to get it to resume instead, this is the part where the intent is defined if someone wants to do a stab at it: https://github.com/vikeri/react-native-background-job/blob/8538d0033d0b068337bd5efdbbe7fb5bdad65d3d/android/src/main/java/com/pilloxa/backgroundjob/HeadlessService.java#L92-L114

@vikeri I'll try to come up with PR for this. I'm not android developer so it may take a while. If you have some ideas please share :)
In the end I think it should be another option for schedule.

@josephbuchma If you get a PR working I think you should replace the current behavior with this that you are suggesting 👍


Closses #22 Integration with OpenAir.

:white_check_mark: Build mentorbot 1.0.69-olvtnwjr completed (commit https://github.com/MentorSource/mentorbot/commit/1a0767f5b4 by @rosenkolev)

Codecov Report

Merging #23 into master will decrease coverage by 1.94%.
The diff coverage is 90.83%.

@@            Coverage Diff             @@
##           master      #23      +/-   ##
==========================================
- Coverage   94.33%   92.39%   -1.95%
==========================================
  Files          14       20       +6
  Lines         424      933     +509
==========================================
+ Hits          400      862     +462
- Misses         24       71      +47

Impacted Files
Coverage Δ

...entorBot.Functions/Services/HangoutsChatService.cs
100% <ø> (ø)
:arrow_up:

...ions/Connectors/Base/GoogleBaseServiceExtension.cs
0% <0%> (ø)

...MentorBot.Functions/Processors/OpenAirProcessor.cs
100% <100%> (ø)

src/MentorBot.Functions/App/ServiceLocator.cs
100% <100%> (ø)
:arrow_up:

.../MentorBot.Functions/Processors/RepeatProcessor.cs
100% <100%> (ø)
:arrow_up:

...MentorBot.Functions/Connectors/OpenAirConnector.cs
81.55% <81.55%> (ø)

...ctions/Connectors/OpenAir/OpenAirClient{Models}.cs
81.92% <81.92%> (ø)

...rBot.Functions/Connectors/HangoutsChatConnector.cs
89.18% <84.31%> (-8.04%)
:arrow_down:

src/MentorBot.Functions/Services/StorageService.cs
96.15% <96.15%> (ø)

...rBot.Functions/Connectors/OpenAir/OpenAirClient.cs
99.22% <99.22%> (ø)

... and 6 more

Continue to review full report at Codecov.

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


Clearer API documentation?

Syntax differences without concise API documentation (what the actual API is, not sample code using a portion of it) make it hard to figure out what is allowed. For example, the readme has this example:
mount(MainLayout, {
  content: () => (<WelcomeComponent name="Arunoda" />)
});

And the sample repo has this:
mount(AuthCheckCtx, {
   LayoutDefault, content: () => (<Simplest title="Template..."/>)
});

...one has the layout component inside the object with another auth component outside and the other just outside. So can the object have nested components or just one and either way what args can and can't be inside and/or the object optionally or required?
Thanks

Agree. Can the documentation also show example pure js React component in use.
Great job btw!

please some examples, need this 4 production THX


add repository:SyntaxError: Unexpected token < in JSON at position 0

env:
bitnami/monocular-ui:v0.5.4
add public repository throw exception:
name: monocular
url: https://kubernetes-helm.github.io/monocular
source: https://github.com/kubernetes-helm/monocular/tree/master/charts

How do I solve this problem? orz....

I've solved this problem,my ingress server is offline.


RSS size keeps on increasing when using sharpen

Question about an existing feature
What are you trying to achieve?
I'm using sharpen with sigma: 100 on a png image(attached below). While doing this operation the RSS size keeps on increasing after which the process is OOM Killed. The OOM Kill is understandable as I've restricted the container's memory to 1.5GB. How can I fix this?
When you searched for similar issues, what did you find that might be related?
I'm running on Alpine Linux with musl libc. I found out that this could be an issue with the underlying memory allocator, hence changed the default memory allocator to mimalloc. I've also confirmed that NodeJs process is using mimalloc, with the following commands:
cat /proc/1/smaps | grep malloc:
7f3465bf1000-7f3465bf6000 r--p 00000000 ca:01 125829539                  /lib/libmimalloc.so.2.0
7f3465bf6000-7f3465c0b000 r-xp 00005000 ca:01 125829539                  /lib/libmimalloc.so.2.0
7f3465c0b000-7f3465c11000 r--p 0001a000 ca:01 125829539                  /lib/libmimalloc.so.2.0
7f3465c11000-7f3465c13000 r--p 0001f000 ca:01 125829539                  /lib/libmimalloc.so.2.0
7f3465c13000-7f3465c15000 rw-p 00021000 ca:01 125829539                  /lib/libmimalloc.so.2.0

ldd $(which node) | grep malloc :
/lib/libmimalloc.so => /lib/libmimalloc.so (0x7fb7ea34b000)

I also tried this test with jemalloc on Debian, but the same results.
I'm running on c4.8xlarge EC2 instance, with sharp concurrency as 36.
I know that lowering the concurrency could help because I tested it with concurrency 20 and it worked. However, I don't believe that is a robust solution because I assume it could then break for a larger image.
Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this question
The test I'm running:
const sharp = require("sharp");
const fs = require("fs");

async function run() {
    const ipBuf = fs.readFileSync("playground-default-transformed.png");

    const opBuf = await sharp(ipBuf).sharpen({ sigma: 100 }).toBuffer();

    console.log("[DONE]");
}

function logMemory() {
    const formatMemoryUsage = (data) =>
        `${Math.round((data / 1024 / 1024) * 100) / 100} MB`;

    const memoryData = process.memoryUsage();

    const memoryUsage = {
        rss: `${formatMemoryUsage(
            memoryData.rss
        )} -> Resident Set Size - total memory allocated for the process execution`,
        heapTotal: `${formatMemoryUsage(
            memoryData.heapTotal
        )} -> total size of the allocated heap`,
        heapUsed: `${formatMemoryUsage(
            memoryData.heapUsed
        )} -> actual memory used during the execution`,
        external: `${formatMemoryUsage(
            memoryData.external
        )} -> V8 external memory`,
    };

    console.log("*".repeat(50), "\n", memoryUsage, "\n", "*".repeat(50));
}

const intr = setInterval(logMemory, 100);

run()
    .then(console.log, console.log)
    .finally(() => clearInterval(intr));

I log the memory usage at regular intervals. The tests starts with this:
{
  rss: '228.13 MB -> Resident Set Size - total memory allocated for the process execution',
  heapTotal: '8.32 MB -> total size of the allocated heap',
  heapUsed: '4.46 MB -> actual memory used during the execution',
  external: '1.43 MB -> V8 external memory'
}

...and ends here:
{
  rss: '1363.3 MB -> Resident Set Size - total memory allocated for the process execution',
  heapTotal: '8.57 MB -> total size of the allocated heap',
  heapUsed: '5 MB -> actual memory used during the execution',
  external: '1.44 MB -> V8 external memory'
}
 **************************************************
Killed

Also, here's the output of npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp:
  System:
    OS: Linux 5.4 Alpine Linux
    CPU: (36) x64 Intel(R) Xeon(R) CPU E5-2666 v3 @ 2.90GHz
    Memory: 49.50 GB / 58.94 GB
    Container: Yes
    Shell: 1.35.0 - /bin/ash
  Binaries:
    Node: 14.21.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 6.14.17 - /usr/local/bin/npm
  npmPackages:
    sharp: ^0.30.7 => 0.30.7

Please provide sample image(s) that help explain this question

Hi, thanks for reporting this. I can reproduce using vips at the command line, and it look like memory consumption for this operation (a relatively large Gaussian-based convolution) is a function of concurrency.
Downloading the test file:
$ curl -Os https://user-images.githubusercontent.com/13717006/211210991-13a20ac3-e099-4813-bf2b-894d6be414cf.png
$ file 211210991-13a20ac3-e099-4813-bf2b-894d6be414cf.png
211210991-13a20ac3-e099-4813-bf2b-894d6be414cf.png: PNG image data, 1140 x 760, 8-bit colormap, non-interlaced

Running with default concurrency (4 in this example):
$ /usr/bin/time -f "%M" vips sharpen 211210991-13a20ac3-e099-4813-bf2b-894d6be414cf.png out.png --sigma 100
389724

Running with a forced concurrency of 36:
$ /usr/bin/time -f "%M" vips sharpen 211210991-13a20ac3-e099-4813-bf2b-894d6be414cf.png out.png --sigma 100 --vips-concurrency 36
1342504

Running with a concurrency of 4 via callgrind:
$ valgrind --tool=callgrind vips sharpen 211210991-13a20ac3-e099-4813-bf2b-894d6be414cf.png out.png --sigma 100

produces the following output:
19,781,701,012 (49.19%)  ../libvips/convolution/convi.c:vips_convi_gen'2 [/usr/local/lib/x86_64-linux-gnu/libvips.so.42.16.1]
 6,058,376,730 (15.07%)  ../libvips/conversion/extract.c:vips_extract_band_buffer [/usr/local/lib/x86_64-linux-gnu/libvips.so.42.16.1]
 5,367,557,000 (13.35%)  ../libvips/convolution/convi.c:vips_convi_gen [/usr/local/lib/x86_64-linux-gnu/libvips.so.42.16.1]
 5,047,828,724 (12.55%)  ../libvips/conversion/bandjoin.c:vips_bandjoin_buffer [/usr/local/lib/x86_64-linux-gnu/libvips.so.42.16.1]
 1,230,624,509 ( 3.06%)  ../libvips/colour/XYZ2Lab.c:vips_col_XYZ2Lab_helper [/usr/local/lib/x86_64-linux-gnu/libvips.so.42.16.1]
   443,024,820 ( 1.10%)  ../libvips/colour/LabQ2sRGB.c:vips_col_scRGB2XYZ [/usr/local/lib/x86_64-linux-gnu/libvips.so.42.16.1]

Running with a concurrency of 36 via callgrind:
$ valgrind --tool=callgrind vips sharpen 211210991-13a20ac3-e099-4813-bf2b-894d6be414cf.png out.png --sigma 100 --vips-concurrency 36

seems to deadlock, but produces the following partial output:
32,025,615,852 (48.15%)  ../libvips/convolution/convi.c:vips_convi_gen'2 [/usr/local/lib/x86_64-linux-gnu/libvips.so.42.16.1]
10,105,677,820 (15.19%)  ../libvips/conversion/extract.c:vips_extract_band_buffer [/usr/local/lib/x86_64-linux-gnu/libvips.so.42.16.1]
 8,949,432,372 (13.46%)  ../libvips/convolution/convi.c:vips_convi_gen [/usr/local/lib/x86_64-linux-gnu/libvips.so.42.16.1]
 8,419,897,704 (12.66%)  ../libvips/conversion/bandjoin.c:vips_bandjoin_buffer [/usr/local/lib/x86_64-linux-gnu/libvips.so.42.16.1]
 2,052,771,009 ( 3.09%)  ../libvips/colour/XYZ2Lab.c:vips_col_XYZ2Lab_helper [/usr/local/lib/x86_64-linux-gnu/libvips.so.42.16.1]
   738,997,560 ( 1.11%)  ../libvips/colour/LabQ2sRGB.c:vips_col_scRGB2XYZ [/usr/local/lib/x86_64-linux-gnu/libvips.so.42.16.1]

So this looks a bit like over-computation based on increased concurrency.
@jcupitt Do you have any insights here?

Wow sigma 100 on sharpen seems a lot. I think 1.5 is probably the highest value that would make sense (in my experience). It's not really designed to scale to values that high.
Could you explain why you need such a huge sigma?

I tried this with your test image:
$ for i in {1..100}; do echo -n "$i, "; /usr/bin/time -f %M vips sharpen sharp.png x.png --sigma $i; done
1, 184648
2, 184532
3, 186916
4, 211740
5, 207288
6, 232888
7, 251220
...
98, 1398548
99, 1467968
100, 1497140

So yes, RSS does get hilariously out of control for large values. It looks like it's slightly worse than linear:

Thanks @jcupitt, would it make sense to reduce the accepted range for sigma in libvips? Currently 0.000001 to 10000:
https://github.com/libvips/libvips/blob/b00a4a80d6e9bcca8f2a3e02e3fcdff68e646538/libvips/convolution/sharpen.c#L333

Yes, maybe 0.001 to 10 would be better?
(sigma is related to display resolution -- you need about 0.5 for an 80 DPI display (typical desktop screen), or 1.5 for 300 DPI (typical high quality print))

@kleisauke something for your backlog :)

Commit https://github.com/lovell/sharp/commit/081debd055257426ad355049e212e524cc63ddfb reduces the maximum sigma to 10 in sharp. I've left the existing minimum as-is for now.
I'll open a separate PR for libvips (for 8.15 as it'll be a breaking change).

v0.32.0 now available with this new limit.


Add tests for file uploader

The tests are failing ... I think invalid needs to be made optional 😬

The invalid property is included in my previous PR which just got merged (#786), should I include it in my test as well?


Allow weighted items within Category in GradebookNG

This is a must-have for us @ rutgers.
Many users will set a category to be a percentage but also have different items within that category weighted differently.

This was discussed in https://github.com/sakaiproject/sakai/pull/689.


Is there a way to force 24 hours time format in time scale?

I'm using XYPlot with xType={'time'} and Russian locale as described in documentation, is there a way to pass 24h time format to d3-scale?

Instead of "03 AM" I need something like "03:00".

I am also interested in the answer to this

I'd recomment using MomentJS
or just Date().parse() https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/parse

I deal with the same issue. The change of the locale does not switch to 24-hour format. Also the usage of tickFormat doesn't give me the flexible time display on XAxis according to number of values.

I gave up on react-vis. It is too buggy, not enough features. I ended up going to recharts but now I'm thinking about chartJS.


Fixes warnings in .NET architecture ebooks (#25392)

Updated heading and title

Updated tiles in toc yaml

Fixed broken link

Reverted file name changes

Fixed build warnings

Updated key takeways file

Apply suggestions from code review

Co-authored-by: David Pine<EMAIL_ADDRESS>Summary
Describe your changes here.
Fixes #Issue_Number (if available)

Attention @gewarren  - related https://github.com/dotnet/docs/pull/25392#issuecomment-902802522


fix(go_to_definition)

fixes #130

In case there are two models starting with the same prefix ( e.g. Hello and HelloWorld) and the Hello model is below the definition of HelloWorld model , when wanting to go to the definition of relation Hello, it would jump to the model HelloWorld`.
Why?
Since there is no parser right now, it would just look at the first index of ('model  Hello'). This is now fixed by adding a whitespace after the modelname -> first index of ('model Hello ') is unique.


Migrate from Python Social Auth to Split Social

https://github.com/omab/python-social-auth/blob/master/MIGRATING_TO_SOCIAL.md

The migration path for this module is really terrible. Tried following the instructions above, they don't work. End up with missing migrations:
python-social-auth/social-app-django#28

Somehow, the table social_auth_partial already exists in the db, can't immediately see where from. So, fake the last migration with python manage.py migrate social_django 0006 --fake. Then, we can go ahead and apply the actual migrations with python manage.py migrate.

Done in #361


Fix issues related to ChangeLog and versions

Fix version / CHANGELOG.md that are out of sync

@pshao25 FYI.  @pshao25, could you add yourself to the CODEOWNERS file for Synapse, please?


SPFx building ListViewCommandSet step "write-manifests" cannot find manifest.json

Category

[x] Question
[ ] Typo
[x] Bug

Description
After updating the ListViewCommandSet from 1.9.1 to 1.10.0 gulp bundle and gulp serve stop working in the step [write-manifests].
Please help me fixing this.
Expected or Desired Behavior
SPFx ListViewCommandSet is bundled completely.  gulp bundle is working and gulp serve is working
Observed Behavior
After using gulp serve or gulp bundle (with or without --ship) the process works until the [write-manifests] part. After a minute or so the process stopped without a finished bundle.
After using the --verbose parameter I get the following message (over 1000 times):
[write-manifests] Unable to get "manifests.json" file for project in ".". We'll try to get each manifest separately
I tried to solve the issue with the solution pointed in #5535 but with no success.
complete gulp serve log:
 C:\Projekte\CP\ListViewCommand\FrontendTLK> gulp bundle --verbose
Build target: DEBUG
Found config file: copy-assets.json
Found config file: write-manifests.json
Found config file: serve.json
Found config file: deploy-azure-storage.json
Found config file: package-solution.json
[08:51:42] Using gulpfile C:\Projekte\CP\ListViewCommand\FrontendTLK\gulpfile.js
[08:51:42] Starting gulp
[08:51:42] Starting 'bundle'...
[08:51:42] Starting subtask 'configure-sp-build-rig'...
[08:51:42] [configure-sp-build-rig] Found config file: config.json
[08:51:42] Finished subtask 'configure-sp-build-rig' after 65 ms
[08:51:42] Starting subtask 'pre-copy'...
[08:51:42] Finished subtask 'pre-copy' after 120 ms
[08:51:42] Starting subtask 'copy-static-assets'...
[08:51:42] Starting subtask 'sass'...
[08:51:44] Finished subtask 'copy-static-assets' after 1.64 s
[08:51:45] Finished subtask 'sass' after 2.56 s
[08:51:45] Starting subtask 'tslint'...
[08:51:45] [tslint] Examining C:\Projekte\CP\ListViewCommand\FrontendTLK\tsconfig.json
[08:51:45] [tslint] Found tsconfig.extends property<EMAIL_ADDRESS>It appears to be a relative path. Resolved to<EMAIL_ADDRESS>[08:51:45] [tslint] Examining<EMAIL_ADDRESS>[08:51:45] [tslint] Found tsconfig.extends property ./tsconfig-base.json. It appears to be a relative path. Resolved to<EMAIL_ADDRESS>[08:51:45] [tslint] Examining<EMAIL_ADDRESS>[08:51:45] [tslint] Found rush-stack compiler at<EMAIL_ADDRESS>[08:51:47] [tslint] tslint version: 5.12.1
[08:51:47] Starting subtask 'tsc'...
[08:51:47] [tsc] typescript version: 3.3.4000
[08:52:01] Finished subtask 'tslint' after 16 s
[08:52:03] Finished subtask 'tsc' after 16 s
[08:52:03] Starting subtask 'post-copy'...
[08:52:03] Finished subtask 'post-copy' after 516 μs
[08:52:03] Starting subtask 'collectLocalizedResources'...
[08:52:03] [collectLocalizedResources] 1 localized resources defined.
[08:52:03] [collectLocalizedResources] Found file "lib/extensions/tlkCommands/loc/en-us.js", identified as locale "en-us"
[08:52:03] Finished subtask 'collectLocalizedResources' after 340 ms
[08:52:03] Starting subtask 'configure-webpack'...
[08:52:06] [configure-webpack] 1 entries specified.
[08:52:06] [configure-webpack] 20 externals specified.
[08:52:06] [configure-webpack] 1 localized resources specified.
[08:52:06] Finished subtask 'configure-webpack' after 2.95 s
[08:52:06] Starting subtask 'webpack'...
[08:52:16] Finished subtask 'webpack' after 10 s
[08:52:16] Starting subtask 'configure-webpack-external-bundling'...
[08:52:16] [configure-webpack-external-bundling] No localized resources specified, nothing to do.
[08:52:16] Finished subtask 'configure-webpack-external-bundling' after 1.62 ms
[08:52:16] Starting subtask 'copy-assets'...
[08:52:17] Finished subtask 'copy-assets' after 535 ms
[08:52:17] Starting subtask 'write-manifests'...
[08:52:17] [write-manifests] Using debug locale: en-US
[08:52:17] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\decorators". We'll try to get each
manifest separately
[08:52:17] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\tslib". We'll try to get each manifest separately
[08:52:17] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\gulp". We'll try to get each manifest separately
[08:52:17] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-core-library". We'll try to get
each manifest separately
[08:52:17] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-lodash-subset". We'll try to get each manifest separately
[08:52:17] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@types\lodash". We'll try to get each manifest separately
[08:52:17] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@types\webpack-env". We'll try to get each manifest separately
[08:52:17] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\node-core-library". We'll try to get each manifest separately
[08:52:17] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-module-interfaces". We'll try to get each manifest separately
[08:52:17] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@types\es6-promise". We'll try to get each manifest separately
[08:52:18] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-dialog". We'll try to get each manifest separately
[08:52:18] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-dialog\node_modules\@microsoft\office-ui-fabric-react-bundle". We'll try to get each manifest separately
[08:52:18] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@types\react". We'll try to get each manifest
separately
[08:52:18] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@uifabric\icons". We'll try to get each manifest separately
[08:52:18] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-dialog\node_modules\office-ui-fabric-react". We'll try to get each manifest separately
[08:52:18] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\react". We'll try to get each manifest separately
[08:52:18] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\react-dom". We'll try to get each manifest separately
[08:52:18] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\load-themed-styles". We'll try to get each manifest separately
[08:52:18] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-application-base". We'll try to
get each manifest separately
[08:52:18] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-component-base". We'll try to get each manifest separately
[08:52:18] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-diagnostics". We'll try to get each manifest separately
[08:52:18] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-dynamic-data". We'll try to get
each manifest separately
[08:52:18] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-http". We'll try to get each manifest separately
[08:52:19] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\microsoft-graph-client". We'll try
to get each manifest separately
[08:52:19] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@types\adal-angular". We'll try to get each manifest separately
[08:52:19] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\adal-angular". We'll try to get each manifest
separately
[08:52:19] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\msal". We'll try to get each manifest separately
[08:52:19] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-polyfills". We'll try to get each manifest separately
[08:52:19] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\es6-collections". We'll try to get each manifest separately
[08:52:19] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-polyfills\node_modules\es6-promise". We'll try to get each manifest separately
[08:52:19] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-polyfills\node_modules\whatwg-fetch". We'll try to get each manifest separately
[08:52:19] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\whatwg-url". We'll try to get each manifest separately
[08:52:19] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-build-web". We'll try to get each manifest separately
[08:52:19] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\whatwg-fetch". We'll try to get each manifest
separately
[08:52:20] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-component-base\node_modules\@microsoft\sp-loader". We'll try to get each manifest separately
[08:52:20] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\loader-raw-script". We'll try to get each manifest separately
[08:52:20] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-component-base\node_modules\@microsoft\office-ui-fabric-react-bundle". We'll try to get each manifest separately
[08:52:20] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-component-base\node_modules\office-ui-fabric-react". We'll try to get each manifest separately
[08:52:20] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-odata-types". We'll try to get each manifest separately
[08:52:20] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-component-base\node_modules\@microsoft\sp-page-context". We'll try to get each manifest separately
[08:52:20] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@types\react-dom". We'll try to get each manifest separately
[08:52:20] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@types\requirejs". We'll try to get each manifest separately
[08:52:20] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-component-base\node_modules\@uifabric\utilities". We'll try to get each manifest separately
[08:52:20] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\exports-loader". We'll try to get each manifest separately
[08:52:21] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\raw-loader". We'll try to get each manifest separately
[08:52:21] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\requirejs". We'll try to get each manifest separately
[08:52:21] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-extension-base". We'll try to get each manifest separately
[08:52:22] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-extension-base\node_modules\@microsoft\sp-loader". We'll try to get each manifest separately
[08:52:22] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-extension-base\node_modules\@microsoft\office-ui-fabric-react-bundle". We'll try to get each manifest separately
[08:52:22] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-extension-base\node_modules\office-ui-fabric-react". We'll try to get each manifest separately
[08:52:22] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-extension-base\node_modules\@microsoft\sp-page-context". We'll try to get each manifest separately
[08:52:22] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-extension-base\node_modules\@uifabric\utilities". We'll try to get each manifest separately
[08:52:22] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-application-base\node_modules\@microsoft\sp-loader". We'll try to get each manifest separately
[08:52:22] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-application-base\node_modules\@microsoft\office-ui-fabric-react-bundle". We'll try to get each manifest separately
[08:52:22] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-application-base\node_modules\office-ui-fabric-react". We'll try to get each manifest separately
[08:52:22] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-application-base\node_modules\@microsoft\sp-page-context". We'll try to get each manifest separately
[08:52:22] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-application-base\node_modules\@uifabric\utilities". We'll try to get each manifest separately
[08:52:23] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-search-extensibility". We'll try to get each manifest separately
[08:52:23] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-search-extensibility\node_modules\@microsoft\sp-loader". We'll try to get each manifest separately
[08:52:23] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-search-extensibility\node_modules\@microsoft\office-ui-fabric-react-bundle". We'll try to get each manifest separately
[08:52:23] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-search-extensibility\node_modules\office-ui-fabric-react". We'll try to get each manifest separately
[08:52:23] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-search-extensibility\node_modules\@microsoft\sp-page-context". We'll try to get each manifest separately
[08:52:23] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-search-extensibility\node_modules\@uifabric\utilities". We'll try to get each manifest separately
[08:52:23] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-dialog\node_modules\@microsoft\sp-webpart-base". We'll try to get each manifest separately
[08:52:23] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-dialog\node_modules\@microsoft\sp-webpart-base\node_modules\@microsoft\load-themed-styles". We'll try to get each manifest separately
[08:52:23] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-dialog\node_modules\@microsoft\sp-loader". We'll try to get each manifest separately
[08:52:24] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-dialog\node_modules\@microsoft\sp-page-context". We'll try to get each manifest separately
[08:52:24] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-dialog\node_modules\@microsoft\sp-loader\node_modules\@uifabric\utilities". We'll try to get each manifest separately
[08:52:24] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-dialog\node_modules\@microsoft\sp-property-pane". We'll try to get each manifest separately
[08:52:24] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\teams-js". We'll try to get each manifest separately
[08:52:24] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@types\office-js". We'll try to get each manifest separately
[08:52:24] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-listview-extensibility". We'll try to get each manifest separately
[08:52:24] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-listview-extensibility\node_modules\@microsoft\sp-page-context". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@microsoft\sp-page-context". We'll try to get
each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@pnp\common". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@pnp\graph". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@pnp\logging". We'll try to get each manifest
separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@pnp\odata". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@pnp\sp". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@pnp\sp-clientsvc". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@pnp\sp-taxonomy". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\@pnp\telemetry-js". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\gulp-messenger". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\gulp-run". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\gulp-spsync-creds". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\moment". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\node-sppkg-deploy". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\office-ui-fabric-react". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in "C:\Projekte\CP\ListViewCommand\FrontendTLK\node_modules\typescript-string-operations". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in ".". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in ".". We'll try to get each manifest separately
[08:52:25] [write-manifests] Unable to get "manifests.json" file for project in ".". We'll try to get each manifest separately
...

@andrewconnell edited to make the above readable... please review your issue after submitting it... the way it was posted was impossible to read

Environment details (if applicable)

OS: Windows 10
Target Environment: SharePoint Online
Framework: Node 10.18.0
Tooling: VS Code | SPFx v1.10.0
Additional details:

package-solution:
{
  "name": "ListViewCommand",
  "version": "0.0.1",
  "private": true,
  "main": "lib/index.js",
  "engines": {
    "node": ">=0.10.0"
  },
  "scripts": {
    "build": "gulp bundle",
    "clean": "gulp clean",
    "test": "gulp test",
    "preversion": "node ./tools/pre-version.js",
    "postversion": "gulp dist"
  },
  "dependencies": {
    "@microsoft/decorators": "1.10.0",
    "@microsoft/sp-core-library": "1.10.0",
    "@microsoft/sp-dialog": "1.10.0",
    "@microsoft/sp-listview-extensibility": "1.10.0",
    "@microsoft/sp-page-context": "^1.10.0",
    "@pnp/common": "^1.3.11",
    "@pnp/graph": "^1.3.11",
    "@pnp/logging": "^1.3.11",
    "@pnp/odata": "^1.3.11",
    "@pnp/sp": "^1.3.11",
    "@pnp/sp-clientsvc": "^1.3.11",
    "@pnp/sp-taxonomy": "^1.3.11",
    "@pnp/telemetry-js": "^2.0.0",
    "@types/es6-promise": "0.0.33",
    "@types/react": "16.8.8",
    "@types/react-dom": "16.8.3",
    "@types/webpack-env": "1.13.1",
    "gulp-messenger": "^0.28.2",
    "gulp-run": "^1.7.1",
    "gulp-spsync-creds": "^2.3.8",
    "moment": "^2.25.3",
    "node-sppkg-deploy": "^1.2.1",
    "office-ui-fabric-react": "^7.83.1",
    "react": "16.8.5",
    "react-dom": "16.8.5",
    "typescript-string-operations": "^1.3.2",
    "url": "^0.11.0"
  },
  "resolutions": {
    "@types/react": "16.8.8"
  },
  "devDependencies": {
<EMAIL_ADDRESS>"0.3.5",
    "@microsoft/sp-build-web": "1.10.0",
    "@microsoft/sp-module-interfaces": "1.10.0",
    "@microsoft/sp-tslint-rules": "1.10.0",
    "@microsoft/sp-webpart-workbench": "1.10.0",
    "@types/chai": "3.4.34",
    "@types/mocha": "2.2.38",
    "@types/react": "^16.9.17",
    "ajv": "~5.2.2",
    "gulp": "~3.9.1",
    "gulp-sequence": "1.0.0",
    "lodash": "^4.17.15"
  }
}

tsconfig
{
"extends"<EMAIL_ADDRESS>"compilerOptions": {
"target": "es5",
"forceConsistentCasingInFileNames": true,
"module": "esnext",
"moduleResolution": "node",
"jsx": "react",
"declaration": true,
"sourceMap": true,
"experimentalDecorators": true,
"skipLibCheck": true,
"outDir": "lib",
"inlineSources": false,
"strictNullChecks": false,
"noUnusedLocals": false,
"typeRoots": [
"./node_modules/@types",
"./node_modules/@microsoft"
],
"types": [
"es6-promise",
"webpack-env"
],
"lib": [
"es6",
"dom",
"es2015.collection"
],
"allowSyntheticDefaultImports": true,
"esModuleInterop": true
},
"include": [
"src/**/*.ts"
],
"exclude": [
"node_modules",
"lib"
]
}

Since you're using new NPM packages, I'd suggest the following:

try this first:

delete the node_modules folder
reinstall all dependencies with npm install
now try gulp bundle

if that doesn't work

delete package-lock.json
repeat the steps above

If neither of those work, can you share the project somewhere (public GH repo) as I'm unable to repro this.

Hi @andrewconnell,
I tried your suggestions before I wrote this ticket. Nothing worked.
I fixed the problem, setting up a new projekt. Copy all the neccessary files (without package.json) and install one module after another.
The final package solution looks like this:

{
  "name": "ListViewCommand",
  "version": "0.0.1",
  "private": true,
  "main": "lib/index.js",
  "engines": {
    "node": ">=0.10.0"
  },
  "scripts": {
    "build": "gulp bundle",
    "clean": "gulp clean",
    "test": "gulp test"
  },
  "dependencies": {
    "@microsoft/decorators": "1.10.0",
    "@microsoft/sp-core-library": "1.10.0",
    "@microsoft/sp-dialog": "1.10.0",
    "@microsoft/sp-listview-extensibility": "1.10.0",
    "@microsoft/sp-office-ui-fabric-core": "^1.10.0",
    "@pnp/common": "^1.3.11",
    "@pnp/graph": "^1.3.11",
    "@pnp/logging": "^1.3.11",
    "@pnp/odata": "^1.3.11",
    "@pnp/sp": "^1.3.11",
    "@pnp/sp-clientsvc": "^1.3.11",
    "@pnp/sp-taxonomy": "^1.3.11",
    "@pnp/telemetry-js": "^2.0.0",
    "@types/es6-promise": "0.0.33",
    "@types/webpack-env": "1.13.1",
    "gulp-messenger": "^0.28.2",
    "gulp-spsync-creds": "^2.3.8",
    "moment": "^2.26.0",
    "node-sppkg-deploy": "^1.2.1",
    "typescript-string-operations": "^1.3.2"
  },
  "devDependencies": {
    "@microsoft/sp-build-web": "1.10.0",
    "@microsoft/sp-tslint-rules": "1.10.0",
    "@microsoft/sp-module-interfaces": "1.10.0",
    "@microsoft/sp-webpart-workbench": "1.10.0",
<EMAIL_ADDRESS>"0.3.5",
    "gulp": "~3.9.1",
    "@types/chai": "3.4.34",
    "@types/mocha": "2.2.38",
    "ajv": "~5.2.2"
  }
}

After that the project builds again (serve and bundle).
The difference:
Not installed dependencies:
"@microsoft/sp-page-context": "^1.10.0",
"office-ui-fabric-react": "^7.83.1",
"react": "16.8.5",
"react-dom": "16.8.5",
"@types/react": "16.8.8",
"@types/react-dom": "16.8.3",
"gulp-run": "^1.7.1",

new dependencies
"@microsoft/sp-office-ui-fabric-core": "^1.10.0",

I dont know which package(s) were responsible for the buildung problem,
Thanks for your help.

Thanks for following up that you got it resolved.


Do not force seed to be script

Problem

I have a seed script for Prisma but I want to re-use it for testing, keeping some seed utilities for granular seeding per test groups.
Right now prisma/seed is assumed to be a script. This means as a user I need to configure my project to have two things: the module with my seed helpers and the script Prisma will execute.
I don't want to be forced to have two modules when one would be good enough.
Suggested solution

Only treat seed.ts as a script if there are no exports treat as a script

If there are ANY exports then do not treat as a script. Instead treat as a module interface. If user exports a run function call that. Maybe default too? Maybe other names? Also allow the module name/export name to be customized on cli like —seed foo:bar which would look for foo file and run bar function export.

Pass in useful info to the seed! For example an a schema AST so users can reflect on it to generate fake data more automatically. I’m sure lots of little nice things we could do there.

If the user does not export the correctly names function but it IS in the conventional disk place with the conventional file name probably we should warn because probably that is user error
This setup would allow best of both worlds: migrate run workflow integration + module API for use in other places like tests

Alternatives

Additional context

Internal Discussion
From another GH thread:
https://github.com/prisma/prisma/issues/5161

I don't consider this an alternative as I agree with Brandon about confusion etc. here.

See 2.23.0 release notes for how to use an export when using seed https://github.com/prisma/prisma/releases/tag/2.23.0
Open a new issue or GitHub discussion if you need to report something/give feedback 😉


GLES2 Batching - Builtins prevent baking in unshaded shaders

Builtins that should prevent baking colors and vertex positions were incorrectly only active in shaders that were not unshaded. This was a terminology misunderstanding on my part :blush: - unshaded materials can still use shaders so should have the same test to prevent baking.
Fixes #38664.

Thanks!


Fixed "cannot tree shake icons fonts" when building in release mode

Just adding a "const" to choices_empty does the trick.

Hi @mauriziopinotti, I'm sorry, I didn't see your pull request, Thanks for contributing


Redesign upload file for student/researcher

📋 Description

Redesign upload file for student/researcher

✅ Checklist
Before submitting the PR, please make sure you have completed the following:

[x] I have followed all the guidlines mentioned in CONTRIBUTING.md.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation (if applicable).
[x] I have tested it locally and it works fine.
[x] Any dependent changes have been merged and published in downstream modules.

🏷 Types of Changes
What type of changes does your code introduce? (Check all that apply)

[ ] Bug fix (non-breaking change which fixes an issue) 🐛
[ ] New feature (non-breaking change which adds functionality) ✨
[x] UI enhancement (non-breaking change which enhances UI) 🎨
[ ] Documentation update 📚

📸 Screenshots (if applicable)

Fixes #378
Thank you for contributing to Research Nexus! We look forward to reviewing your PR and getting it merged!

Not satisfied with the changes


Logo design

Hi. I am a graphic designer. I volunteer to design a logo for open source projects. I can design it for you to use it in the readme file. What dou you say?

Hey @Batarian711, i would be glad if you did!
I don't have much to return in terms of exposure, but i sure will credit you where i use the provided logos.
Thanks.

Inspired by the old game console, I designed a minimalist logo. Is there anything you want to add ?

Thanks for the logo @Batarian711!


Mutex unlock can potentially overflow the stack. Provide an async unlock to allow users to avoid the issue.

Reading the code of unlock for the async_mutex, my understanding is that if there's a long list of awaiters currently for the mutex, the mutex's holder's call to unlock will call resume() the first awaiter, whose unlock call will call resume() of the next awaiter and so on and so on, potentially running out of stack space.
This potential situation might be avoided by use of an asynchronous unlock, by which co_await mutex.unlock() would suspend the lock holder, schedule it in some way for later resumption and make the first awaiter be resumed immediately by the symmetric return mechanism of await_suspend(...). Thus there would be chained calls to resume() consuming the stack.

I am unsure whether this problem actually exists.
The resume call you are referring to in https://github.com/andreasbuhr/cppcoro/blob/e86216e4fa6145f0184b5fef79230e9d4dc3aa77/lib/async_mutex.cpp#L85 is the last statement in that function. It seems to me that no destructors have to be called at the end of this function. I would guess the compiler can do tail-call optimization, thus not needing extra stack space for the call.
It would be very interesting to see whether one can create that stack overflow you are describing.


SDMMD_lockssl_handshake: SSL handshake fatal lower level error 5 when using iOS 10 beta

Seems that Apple changed something in iOS 10 beta 4, up to beta 3 everything worked fine
./iOSConsole -l
Currently connected devices: (1)
SDMMD_lockssl_handshake: SSL handshake fatal lower level error 5: (null).
SDMMD_AMDeviceStartSession: Could not start session with device 581: kAMDInvalidResponseError

Interesting, not much can be done until the official iOS 10 release, if you want to research and contribute a fix that would be awesome -- I am not planning on installing any of the betas.

I'm not into SSL but I could follow the error to
SSL *SDMMD_lockssl_handshake(uint64_t socket, CFTypeRef hostCert, CFTypeRef deviceCert, CFTypeRef hostPrivKey, uint32_t num)
in SDMMD_AMDevice.c
The Line
						result = SSL_do_handshake(ssl);
results -1 which means a

The TLS/SSL handshake was not successful because a fatal error occurred either at the protocol level or a connection failure occurred

(due to https://www.openssl.org/docs/manmaster/ssl/SSL_do_handshake.html)
The line
							uint32_t err = SSL_get_error(ssl, result);
returns a SSL_ERROR_SYSCALL which means

Some I/O error occurred

(due to https://www.openssl.org/docs/manmaster/ssl/SSL_get_error.html)
As result is 0 here we are now at

If ret == 0, an EOF was observed that violates the protocol

which brings me to the end of my debugging skill.
Hope this helps
Maybe an issue with the openssl version which is added (openssl-0.9.8zg) or Apple changed something on their implementation

This would require looking at the lockssl_handshake function in MobileDevice.framework to see if there are auth changes to that code, if so then the library needs to be updated. I find it unlikely to have a major change without a version check first. if it works with existing iTunes or Xcode versions without an update then it is unlikely there was a change. Much of the auth exchange is immutable as it would cause breakages across all the old devices too.

With this in mind I've also checked macOS 10.12 beta and it seems that with this beta the same issue also occurs using iOS 9 (and also 10 beta)
It seems that apple is currently touching this on every OS

It seems that apple now requires tls seems to cause the problems here
https://developer.apple.com/library/prerelease/content/releasenotes/General/WhatsNewIniOS/Articles/iOS10.html

The contents of the developer SDK don't apply to the private frameworks, I would like to see a new version of the MobileDevice framework and disassembly to see the differences in the function I mentioned.

Someone was able to provide me with a copy of the MobileDevice.framework from the latest beta, from a cursory examination, i don't see very much if any difference in the auth procedure. I do notice that this like (https://github.com/samdmarshall/SDMMobileDevice/blob/master/Framework/MobileDevice/Device Types/AMDevice/SDMMD_AMDevice.c#L164) is SSLv23_method() instead of SSLv3_method(). You could try that change in your own code and see if that works.

Also, error 5 is:
# define SSL_ERROR_SYSCALL               5/* look at error stack/return
                                           * value/errno */

so this should be able to be something you can debug if you build and set breakpoints and check those values after attempting to connect.

It seems apple dropped support for ssl3 and requires tls instead. Using beta 4 and tls works fine. It seems this changes from beta to beta the best would be waiting for the final release and set the connection method appropriately.

It solved my problem for 10.0.1 version
Thanks

@kapil0408 I would ask that you please refrain from posting into closed issues, it alerts all people that have previously posted in the issue and doesn't add any new dialogue about the issue. Thanks.

Ok, I will not post in any things in closed issues.